METHODOLOGY FOR REQUIREMENTS ENGINEERING TECHNIQUES SELECTION (MRETS)

Method EngineeringFiona Gelink3153061Group 3

INTRODUCTION

The method Advantages of the method Related literature PDD Steps of the method References

THE METHOD

The selection of suitable RE techniques appropriate use of RE techniques leads to

high quality requirements specifications, which in turn results in high quality software products.

The method is developed by: Dr. L. Jiang, Dr. A. Eberlein, Dr. B.H. Far, & Dr. M. Mousavi.

ADVANTAGES

It aids requirements engineers in establishing a link between the attributes of the project and the attributes of RE techniques.

based on the detailed analysis and comparison of RE techniques.

The objective function used in the approach provides an effective decision support mechanism for the selection of RE techniques.

RELATED LITERATURE

High frequency of errors in requirements activities (Ambrióso et al., 2009).

Identify what techniques are needed to avoid failure (Macaulay, 1996).

Attributes effect quality and cost of a project (Jiang et al., 2008b).

Limitations of RE techniques for Geographical distribution (Ahmad et al., 2011)

Requirements engineering techniques could be used to generate policy (Callele & Wnuk, 2011) .

STEPS

1st

• Score the attributes of the given project

2nd

• Derivate the initially recommended RE techniques.

3rd

• Analyze RE techniques using the clustering method.

4th

• Analyze the techniques and construction of the recommendation space.

5th

• Calculations based on the objective function.

6th

• Refinement of the recommended techniques selection.

PROCESS-DELIVERABLE DIAGRAM

EXAMPLE

Score the attributes of the given project.

Project attributes

Project size

Project complexity

Requirement volatility

Organization and customer relationship

Team size

Degree of knowledge of requirements

EXAMPLE

Derivate the initially recommended RE techniques.

Initially recommended set of techniques

Interview

JAD

Viewpoint-based analysis

Goal-based analysis

Scenario-based analysis

OO analysis

AHP

Viewpoint definition

Structured natural language specification

Viewpoint validation

Formal requirement inspection

EXAMPLESelected technique attributes Weight of the attributes

Ability to help get domain knowledge 4

Ability to help identify stakeholders 4

Ability to help identify non-functional requirements 4

Ability to help model and understand requirements 5

Ability to help analyze non-functional requirements 5

Ability to help model interface requirements 5

Ability to help requirements verification 4

Ability to help get implicit knowledge 4

Ability to help write unambiguous and precise requirements by using the notations

4

Ability to help write complete requirements 5

Ability to help with requirements management 4

Ability to help identify interactions (ambiguous, inconsistency, conflict)

3

Maturity of supporting tools 5

EXAMPLE

Analyze RE techniques using the clustering method.

Clusters

Cluster 1 Cluster 2 Cluster 3

Interview Evolutionary prototypes Viewpoint-based documentation

Contextual inquiry Exploratory prototypes (throw-away prototypes)

Structured natural language specification

Brain-storming eXtreme programming (XP) eXtreme programming (XP)

Viewpoints-based elicitation

EXAMPLE

Analyze the techniques and construction of the recommendation space.Technique recommendation space

Initially recommendation techniques

Functionally comparable techniques

Functionally complementary techniques

EXAMPLE

Calculations based on the objective function.Technique combination

No. Technique combination

Elicitation technique

Analysis & Negotiation Technique

Documentation Technique

Verification & validation Technique

Sum of ability scores

1. Interview, Focus Group,Ethnography.

Viewpoint-based analysis,AHP

Structured natural language specification

Viewpoint validation

12,6

2. Interview, Focus Group,Ethnography

OO Analysis,AHP

Viewpoint-based definition

Formal requirements specification

14,6

3. Interview, Focus Group,Ethnography

Scenario-based analysis,AHP

Structured natural language specification

Formal requirements inspections

13,6

4. Interview, Focus Group,Ethnography

Viewpoint-based analysis,AHP

Viewpoint-based definition

Formal requirements inspections

15,6

EXAMPLE

Refinement of the recommended techniques selection.

Final recommendation space

Categories Initial recommendation Final recommendation Final decision

ElicitationTechnique

Interview, JAD Focus Group, Interview, Ethnography

Focus Group, Interview, Ethnography

Analysis & Negotiation technique

Viewpoint-based analysis, Scenario- based analysis,AHP

Viewpoint-based analysis, AHP Viewpoint-based analysis

Documentation technique Viewpoint-based definition, Structured natural language specification

Viewpoint-based definition Viewpoint-based definition

Verification & Validation technique

Viewpoint validation, Formal requirements inspection

Formal requirements inspection Formal requirements inspection

REFERENCES Ahmad, A., Shahzad, A., Padmanabhuni, V.K., Mansoor, A., Joseph, S., & Arshad, Z. (2011). Requirements Priorization with

Respect to Geographically Distributed Stakeholders. International Conference on Computer Science and Automation Engineering (CSAE), Shanghai, China, 290-294.

Ambrióso, B.G., Braga, J.L., & Resende-Filho, M.A. (2010). Modeling and scenario simulation for decision support in management of requirements activities in software projects. Journal of softwaremaintenance and evolution: research and practice, 23, 35-50.

Berkovich, M., Hoffmann, A., Leimeister J.M., & Krcmar, H. (2011). Analysis of Requirements Engineering Techniques for IT-enables Product Service Systems. Workshop on Requirements Engineering for Systems, Services and Systems of-Systems(RES 4), Trento, Italy, 50-58.

Callele, D., & Wnuk, K. (2011). More than Requirements: Applying Requirements Engineering Techniques to the Challenge of Setting Corporate Intellectual Policy, An Experience Report. 4th International Workshop on Requirements Engineering and Law, Trento, Italy, 35-42.

Jiang, L. (2005). A Framework for the Requirements Engineering Process Development. 19th Australian Software Engineering Conference, Calgary, Alberta, 507-516.

Jiang, L., Eberlein, A., & Far, B.H. (2008). A methodology for the selection of requirements engineering techniques. Software System Model, 7, 303-328.

Jiang L., Eberlein, A., & Far, B.H. (2008b). A case study validation of a knowledge-based approach for the selection of requirements engineering techniques. Requirement Engineering, 13, 117-146.

Kausar, S., Tariq, S., Riaz, S., & Khanum, A. (2010). Guidelines for the Selection of Elicitation Techniques. 6th International Conference on Emerging Technologies (ICET), Islamabad, Pakistan, 265-269.

Macaulay, A. (1996). Requirements for Requirements Engineering Techniques. Proceedings of ICRE '96, 157-164. Seyff, N., Graf, F., & Maiden, N. (2010). Using mobile RE Tools to Give End-Users their Own Voice. 18th IEEE International

Requirements Engineering Conference, London, UK, 37-46. Veerappa, V., & Letier, E. (2011). Understanding Clusters of Optimal Solutions in Multi-Objective Decision Problems. 19th

International Requirements Engineering Conference, Trento, Italy, 89-98. Zawedde, A.S., Klabbers, M.D., Williams, D., & Brand, M.G.J. (2011). Understanding the Dynamics of Requirements Process

Improvements: A New Approach. Lecture Notes in Computer Science, 6759, 276-290.

QUESTIONS?