Conflicts Identification among Non-functional Requirements using Matrix Maps
Conflicts identification among non-functional requirements is often identified intuitively which impairs conflict analysis practices. This paper proposes a new model to identify conflicts among non-functional requirements. The proposed model uses the matrix mechanism to identify the quality based conflicts among non-functional requirements. The potential conflicts are identified through the mapping of low level conflicting quality attributes to low level functionalities using the matrices. The proposed model achieves the identification of conflicts among product and process requirements, identifies false conflicts, decreases the documentation overhead, and maintains transparency of identified conflicts. The attributes are not concomitantly taken into account by current models in practice.
[1]. L. Chung and B. Nixon, "Dealing with Nonfunctional Requirements:
Three Experimental Studies of a Process-Oriented Approach," Proc.
17th Int-l Conf. Software Eng., Apr. 2000, pp. 24-28.
[2]. L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, "Non-Functional
Requirements in Software Engineering", Kluwer Academic Publisher,
London, 1999.
[3]. K. K. Breitman, J. C. S. P. Leite, and A. Finkelstein, "The World-s
Stage: A Survey on Requirements Engineering Using a Real-Life Case
Study," The Brazilian Computer Soc., July 1999, vol. 6, no. 1, pp. 13-
38.
[4]. D. R. Lindstrom, "Five Ways to Destroy a Development Project,"
IEEE Software, Sept. 1993, vol. 10, no. 5, pp. 55-58.
[5]. A. Finkelstein and J. Dowell, "A Comedy of Errors: The London
Ambulance Service Case Study," Proc. Eighth Int-l Workshop
Software Specification and Design, 1996, pp. 2-5.
[6]. F. P. Brooks Jr., "No Silver Bullet: Essences and Accidents of
Software Engineering", IEEE Computer, Apr. 1987,vol. 20, no. 4, pp.
10-19.
[7]. L. M. Cysneiros and J. C. S. P. Leite, "Integrating Non-Functional
Requirements into Data Modeling," Proc. Fourth Int-l Symp.
Requirements Engineering Ireland, , June 1999, pp. 162-171
[8]. A. Davis, "Software Requirements: Objects, Functions and States."
Prentice Hall, ed. 2, 1993.
[9]. R. Malan, D. Bredemeyer, "Defining the non-functional requirements",
Bredemeyer Consulting, Bloomington, 2001
[10]. N. A. Ernst, Y. Yijun and J. Mylopoulos "Visualizing non-functional
requirements" First Int. workshop on Requirements Engineering
Visualization REV- 06, Sept. 2006, pp.2,
[11]. P. Morris, "Counting non-functional requirements when they are
implemented as software", Total Metrics, version 2.2, 2006
[12]. J. Musa, A. Lannino, and K. Okumoto, "Software Reliability:
Measurement, Prediction and Application." McGraw-Hill Inc., New
York, 1989.
[13]. N. E. Fenton and S. L. Pfleeger, "Software Metrics: A Rigorous and
Practical Approach", International Thomson Computer Press, ed. 2,
1996
[14]. H. In "Conflict Identification and Resolution for Software Attribute
Requirements", PhD Thesis, Faculty of Graduate School, University of
Southern California, 1998
[15]. V. Sandana and X. F. Liu, "Analysis of Conflicts Among Nonfunctional
Requirements using Integrated Analysis of Functional and
Non-functional requirements" 31st IEEE Annual International
Computer Software and Applications Conference, Beijing, 2007
[16]. A. Egyed and P. Grunbacher "Identifying Requirements Conflicts and
Cooperation: How Quality Attributes and Automated Traceability Can
Help", IEEE Software, , 2004, vol. 21, no. 6, pp. 50-58
[17]. S. C. Bertagnolli and M. L. B. Lisboa "The FRIDA Model" 2000
[18]. E. R. Poort and P. H. N. deWith, "Resolving Requirement Conflicts
through Non-Functional Decomposition" Proc. Fourth Working
IEEE/IFIP Conference on Software Architecture (WICSA-04), IEEE
Computer Society, 2004
[19]. B. Boehm and H. In, "Software Cost Option Strategy Tool (S-COST)"
COMPSAC96, Seoul, Korea: IEEE Comp. Society Press, 1996
[20]. H. In, C. H. Kim, U. Yun and S. S. Yau, "Q-MAR: A QoS resource
Conflict Identification Model for Situation-Aware Middleware" Proc.
9th IEEE Workshop on Future Trends of Distributed Computing
Systems (FTDCS-03), IEEE Computer Society, 2003
[1]. L. Chung and B. Nixon, "Dealing with Nonfunctional Requirements:
Three Experimental Studies of a Process-Oriented Approach," Proc.
17th Int-l Conf. Software Eng., Apr. 2000, pp. 24-28.
[2]. L. Chung, B. Nixon, E. Yu, and J. Mylopoulos, "Non-Functional
Requirements in Software Engineering", Kluwer Academic Publisher,
London, 1999.
[3]. K. K. Breitman, J. C. S. P. Leite, and A. Finkelstein, "The World-s
Stage: A Survey on Requirements Engineering Using a Real-Life Case
Study," The Brazilian Computer Soc., July 1999, vol. 6, no. 1, pp. 13-
38.
[4]. D. R. Lindstrom, "Five Ways to Destroy a Development Project,"
IEEE Software, Sept. 1993, vol. 10, no. 5, pp. 55-58.
[5]. A. Finkelstein and J. Dowell, "A Comedy of Errors: The London
Ambulance Service Case Study," Proc. Eighth Int-l Workshop
Software Specification and Design, 1996, pp. 2-5.
[6]. F. P. Brooks Jr., "No Silver Bullet: Essences and Accidents of
Software Engineering", IEEE Computer, Apr. 1987,vol. 20, no. 4, pp.
10-19.
[7]. L. M. Cysneiros and J. C. S. P. Leite, "Integrating Non-Functional
Requirements into Data Modeling," Proc. Fourth Int-l Symp.
Requirements Engineering Ireland, , June 1999, pp. 162-171
[8]. A. Davis, "Software Requirements: Objects, Functions and States."
Prentice Hall, ed. 2, 1993.
[9]. R. Malan, D. Bredemeyer, "Defining the non-functional requirements",
Bredemeyer Consulting, Bloomington, 2001
[10]. N. A. Ernst, Y. Yijun and J. Mylopoulos "Visualizing non-functional
requirements" First Int. workshop on Requirements Engineering
Visualization REV- 06, Sept. 2006, pp.2,
[11]. P. Morris, "Counting non-functional requirements when they are
implemented as software", Total Metrics, version 2.2, 2006
[12]. J. Musa, A. Lannino, and K. Okumoto, "Software Reliability:
Measurement, Prediction and Application." McGraw-Hill Inc., New
York, 1989.
[13]. N. E. Fenton and S. L. Pfleeger, "Software Metrics: A Rigorous and
Practical Approach", International Thomson Computer Press, ed. 2,
1996
[14]. H. In "Conflict Identification and Resolution for Software Attribute
Requirements", PhD Thesis, Faculty of Graduate School, University of
Southern California, 1998
[15]. V. Sandana and X. F. Liu, "Analysis of Conflicts Among Nonfunctional
Requirements using Integrated Analysis of Functional and
Non-functional requirements" 31st IEEE Annual International
Computer Software and Applications Conference, Beijing, 2007
[16]. A. Egyed and P. Grunbacher "Identifying Requirements Conflicts and
Cooperation: How Quality Attributes and Automated Traceability Can
Help", IEEE Software, , 2004, vol. 21, no. 6, pp. 50-58
[17]. S. C. Bertagnolli and M. L. B. Lisboa "The FRIDA Model" 2000
[18]. E. R. Poort and P. H. N. deWith, "Resolving Requirement Conflicts
through Non-Functional Decomposition" Proc. Fourth Working
IEEE/IFIP Conference on Software Architecture (WICSA-04), IEEE
Computer Society, 2004
[19]. B. Boehm and H. In, "Software Cost Option Strategy Tool (S-COST)"
COMPSAC96, Seoul, Korea: IEEE Comp. Society Press, 1996
[20]. H. In, C. H. Kim, U. Yun and S. S. Yau, "Q-MAR: A QoS resource
Conflict Identification Model for Situation-Aware Middleware" Proc.
9th IEEE Workshop on Future Trends of Distributed Computing
Systems (FTDCS-03), IEEE Computer Society, 2003
@article{"International Journal of Information, Control and Computer Sciences:59257", author = "Abdul H and Jamil A and Imran U", title = "Conflicts Identification among Non-functional Requirements using Matrix Maps", abstract = "Conflicts identification among non-functional requirements is often identified intuitively which impairs conflict analysis practices. This paper proposes a new model to identify conflicts among non-functional requirements. The proposed model uses the matrix mechanism to identify the quality based conflicts among non-functional requirements. The potential conflicts are identified through the mapping of low level conflicting quality attributes to low level functionalities using the matrices. The proposed model achieves the identification of conflicts among product and process requirements, identifies false conflicts, decreases the documentation overhead, and maintains transparency of identified conflicts. The attributes are not concomitantly taken into account by current models in practice.
", keywords = "Conflict Identification, Matrix Maps, Non-functional Requirements, Requirements Analysis, Software Engineering", volume = "4", number = "8", pages = "1287-6", }
