Advertisement

Constructing a Catalogue of Conflicts among Non-functional Requirements

  • Dewi Mairiza
  • Didar Zowghi
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 230)

Abstract

Non-Functional Requirements (NFRs) are recognized as a critical factor to the success of software projects because they address the essential issue of software quality. NFRs tend to interfere, conflict, and contradict with one another and this conflict is widely acknowledged as one of the key characteristics of NFRs. Several models of NFRs conflicts have been proposed and the interacting nature of NFRs has been characterized as either positive or negative inter-relationships among NFRs. Positive relationship represents a pair of NFRs that are supporting each other while negative relationship represents those NFRs that are conflicting with one another. Furthermore, as NFRs are also relative, the interpretation of NFRs may vary depending on many factors such as the context of the system being developed and the extent of stakeholders’ involvement. The multiple interpretations of NFRs may lead to positive or negative inter-relationships that are not always obvious. These relationships may change depending on the meaning of NFRs in the system being developed. Hence, the existing potential conflicts models remain in disagreement with one other. This paper presents the result of an extensive and systematic investigation of the extant literature over the notion of NFRs and the conflicts among them. Rigorous synthesis of the carefully reviewed literature has resulted in the construction of a catalogue of NFRs conflicts with respect to NFRs relative characteristic. The relativity of conflicts is characterized by three categories: absolute conflict; relative conflict; and never conflict. This comprehensive catalogue could assist software developers with identifying the NFRs conflicts, performing conflicts analysis, and suggesting potential strategies to resolve these conflicts.

Keywords

Non-functional requirements Relationship Conflict Relative Catalogue 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Yeh, R.T.: Requirements analysis - a management perspective. In: IEEE Computer Software and Applications Conference (COMPSAC 1982), Los Alamitos, pp. 410–416 (1982)Google Scholar
  2. 2.
    Mairiza, D., et al.: Managing conflicts among non-functional requirements. In: 12th Australian Workshop on Requirements Engineering (AWRE 2009), Sydney, Australia (2009)Google Scholar
  3. 3.
    Ebert, C.: Putting requirement management into praxis: dealing with nonfunctional requirements. Information and Software Technology 40, 175–185 (1998)CrossRefGoogle Scholar
  4. 4.
    Firesmith, D.: Using quality models to engineer quality requirements. Journal of Object Technology 2, 67–75 (2003)CrossRefGoogle Scholar
  5. 5.
    Chung, L., et al.: Non-functional requirements in software engineering. Kluwer Academic Publishers, Massachusetts (2000)CrossRefzbMATHGoogle Scholar
  6. 6.
    Mittermeir, R.T., et al.: Modern software engineering, foundations and current perspectives. Van Nostrand Reinhold Co, New York (1989)Google Scholar
  7. 7.
    Kotonya, G., Sommerville, I.: Non-functional requirements (1998)Google Scholar
  8. 8.
    Charette, R.N.: Applications strategies for risk analysis. McGraw-Hill, New York (1990)Google Scholar
  9. 9.
    Wiegers, K.E.: Software requirements, 2nd edn. Microsoft Press, Washington (2003)Google Scholar
  10. 10.
    Sommerville, I.: Software Engineering, 7th edn. Pearson Education Limited, Essex (2004)zbMATHGoogle Scholar
  11. 11.
    Breitman, K.K., et al.: The world’s a stage: a survey on requirements engineering using a real-life case study. Journal of the Brazilian Computer Society 6, 1–57 (1999)CrossRefGoogle Scholar
  12. 12.
    Finkelstein, A., Dowell, J.: A comedy of errors: the London ambulance service case study. In: Eigth International Workshop Software Specification and Design, pp. 2–5 (1996)Google Scholar
  13. 13.
    Boehm, B., In, H.: Identifying quality-requirements conflict. IEEE Software 13, 25–35 (1996)CrossRefGoogle Scholar
  14. 14.
    Boehm, B., In, H.: Aids for identifying conflicts among quality requirements. IEEE Software (March 1996)Google Scholar
  15. 15.
    Leveson, N.G., Turner, C.S.: An investigation of the Therac-25 accidents. IEEE Computer 26, 18–41 (1993)CrossRefGoogle Scholar
  16. 16.
    Grimshaw, D.J., Draper, G.W.: Non-functional requirements analysis: deficiencies in structured methods. Information and Software Technology 43, 629–634 (2001)CrossRefGoogle Scholar
  17. 17.
    Heumesser, N., et al.: Essential and requisites for the management of evolution - requirements and incremental validation. Information Technology for European Advancement, ITEA-EMPRESS Consortium (2003)Google Scholar
  18. 18.
    Yusop, N., et al.: The impacts of non-functional requirements in web system projects. International Journal of Value Chain Management 2, 18–32 (2008)CrossRefGoogle Scholar
  19. 19.
    Paech, B., Kerkow, D.: Non-functional requirements engineering - quality is essential. In: 10th International Workshop on Requirements Engineering: Foundation for Software Quality, pp. 27–40 (2004)Google Scholar
  20. 20.
    Lauesen, S.: Software requirements: styles and techniques. Addison-Wesley, Reading (2002)Google Scholar
  21. 21.
    Chung, L., et al.: Using non-functional requirements to systematically support change. In: The Second International Symposium on Requirements Engineering, York, pp. 132–139 (1995)Google Scholar
  22. 22.
    Chung, L., et al.: Dealing with change: an approach using non-functional requirements. Requirements Engineering 1, 238–260 (1996)CrossRefGoogle Scholar
  23. 23.
    Curtis, B., et al.: A field study of the software design process for large systems. Communication of the ACM 31, 1268–1287 (1988)CrossRefGoogle Scholar
  24. 24.
    Boehm, B., Egyed, A.: WinWin requirements negotiation processes: a multi-project analysis. In: 5th International Conference on Software Processes (1998)Google Scholar
  25. 25.
    Egyed, A., Boehm, B.: A comparison study in software requirements negotiation. In: 8th Annual International Symposium on Systems Engineering, INCOSE 1998 (1998)Google Scholar
  26. 26.
    Robinson, W.N., et al.: Requirements interaction management. ACM Computing Surveys 35, 132–190 (2003)CrossRefGoogle Scholar
  27. 27.
    Egyed, A., Grünbacher, P.: Identifying requirements conflicts and cooperation: how quality attributes and automated traceability can help. IEEE Software 21, 50–58 (2004)CrossRefGoogle Scholar
  28. 28.
    Krippendorff, K.: Content analysis: and introduction to its methodology, 2nd edn. Sage Publications, Inc., Thousand Oaks (2004)Google Scholar
  29. 29.
    Weber, R.P.: Basic content analysis. Sage Publications, Inc., Thousand Oaks (1989)Google Scholar
  30. 30.
    Stemler, S.: An overview of content analysis. Practical Assessment, Research & Evaluation 7 (2001)Google Scholar
  31. 31.
    Neuendorf, K.A.: The content analysis guidebook, 1st edn. Sage Publications, Inc., Thousand Oaks (2001)Google Scholar
  32. 32.
    Glinz, M.: Rethinking the notion of non-functional requirements. In: Third World Congress for Software Quality, Munich, Germany, pp. 55–64 (2005)Google Scholar
  33. 33.
    Glinz, M.: On non-functional requirements. In: 15th IEEE International Requirements Engineering Conference (RE 2007), pp. 21–26 (2007)Google Scholar
  34. 34.
    Mairiza, D., et al.: An investigation into the notion of non-functional requirements. In: 25th ACM Symposium On Applied Computing, Switzerland (2010)Google Scholar
  35. 35.
    Alexander, I., Maiden, N.: Scenarios, stories, use cases: through the systems development life-cycle. John Wiley & Sons, Ltd., Chichester (2004)Google Scholar
  36. 36.
    Robertson, S., Robertson, J.: Mastering the requirements process, 2nd edn. Addison-Wesley, Boston (2006)Google Scholar
  37. 37.
    Sadana, V., Liu, X.F.: Analysis of conflict among non-functional requirements using integrated analysis of functional and non-functional requirements. In: 31st International Computer Software and Applications Conference, COMPSAC 2007 (2007)Google Scholar
  38. 38.
    Brito, I., Moreira, A.: Integrating the NFR framework in a RE model. Presented at the Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design, Lancaster, UK (2004)Google Scholar
  39. 39.
    Moreira, A., et al.: Crosscutting quality attributes for requirements engineering. In: 14th International Conference on Software Engineering and Knowledge Engineering, Ischia, Italy (2002)Google Scholar
  40. 40.
    Mala, G.S.A., Uma, G.V.: Elicitation of non-functional requirements preference for actors of usecase from domain model. In: Hoffmann, A., Kang, B.-h., Richards, D., Tsumoto, S. (eds.) PKAW 2006. LNCS (LNAI), vol. 4303, pp. 238–243. Springer, Heidelberg (2006)CrossRefGoogle Scholar
  41. 41.
    Poort, E.R., de With, P.H.N.: Resolving requirement conflicts through non-functional decomposition. In: Fourth Working IEEE/IFIP Conference on Software Architecture, WICSA 2004 (2004)Google Scholar
  42. 42.
    Mairiza, D., et al.: Towards a catalogue of conflicts among non-functional requirements. In: Maciaszek, L.A., Loucopoulos, P. (eds.) ENASE 2010. CCIS, vol. 230, pp. 33–46. Springer, Heidelberg (2011)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Dewi Mairiza
    • 1
  • Didar Zowghi
    • 1
  1. 1.School of Software, Faculty of Engineering and Information TechnologyUniversity of Technology, Sydney (UTS)Australia

Personalised recommendations