Elicitation of Non-functional Requirement Preference for Actors of Usecase from Domain Model

  • G. S. Anandha Mala
  • G. V. Uma
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4303)


Requirement engineering plays a vital role in the development of the software. The quality of the software being developed depends on the non-functional requirements, which are still not derived effectively due to the conflicts between them. This paper presents an approach to identify the non-functional requirements for a given usecase description from the domain model such as Unified Modelling Language class diagram and goal based questionnaires. This approach makes use of the domain model to find out the behaviour of the system and possible constraints for actors in the system. The non-functional requirement taxonomy and the user preferences are used to analyse the conflicts, which is resolved based on trade-off analysis by prioritizing the preference. The prioritization depends on the dominating non-functional requirements from the inference engine.


Domain Model Requirement Engineering Functional Requirement Inference Engine State Chart 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Nick, M., Althoff, K.-D., Tautz, C.: Facilitating the Practical Evaluation of Organizational Memories Using the Goal-Question-Metric Technique. In: KAW 1999 – Twelfth Workshop on Knowledge Acquisition, Modeling and Management (1999)Google Scholar
  2. 2.
    Cleland-Huang, J., Settimi, R., BenKhadra, O., Berezhanskaya, E., Christina, S.: Goal-Centric Traceability for Managing Non-Functional Requirements. In: ACM ICSE 2005, May 15–21 (2005)Google Scholar
  3. 3.
    Anton, A.I., Potts, C.: The Use of Goals to Surface Requirements for Evolving Systems. In: 20th International Conference on Software Engineering (ICSE 1998), April 1998, pp. 157–166 (1998)Google Scholar
  4. 4.
    Cysneiros, L.M., Leite, J.C.S.d.P.: Nonfunctional Requirements: From Elicitation to Conceptual Models. IEEE Transactions On Software Engineering 30(5) (May 2004)Google Scholar
  5. 5.
    Liu, X.F., Yen, J.: An Analytic Framework for Specifying and Analyzing Imprecise Requirements. In: Proceedings of 18th International Conference on Software Engineering (ICSE-18), Berlin, Germany, March 25-30, pp. 60–69 (1996)Google Scholar
  6. 6.
    Glinz, M.: Rethinking the Notion of Non-Functional Requirements. In: Proceedings of the Third World Congress for Software Quality (3WCSQ 2005), Munich, Germany, vol. II, pp. 55–64 (2005)Google Scholar
  7. 7.
    Cortellessa, V., Goseva-Popstojanova, K., Guedem, A.R., Hassan, A., Elnaggar, R., Abdelmoez, W., Ammar, H.H.: Model-Based Performance Risk Analysis. IEEE Transactions On Software Engineering 31(1) (January 2005)Google Scholar
  8. 8.
    Kaiya, H., Osada, A., Kaijiri, K.: Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems. In: Proceedings of the 12th IEEE International Requirements Engineering Conference (RE 2004), IEEE, Los Alamitos (2004)Google Scholar
  9. 9.
    Yen, J., Tiao, W.A., Yin, J.: STAR: A Tool for Analyzing Imprecise Requirements. In: Proceedings of 1998 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE 1998), Anchorage, Alaska, May 4-9, pp. 863–868 (1998)Google Scholar
  10. 10.
    Gregoriades, A., Sutcliffe, A.: Scenario-Based Assessment of Nonfunctional Requirements. IEEE Transactions On Software Engineering 31(5) (May 2005)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • G. S. Anandha Mala
    • 1
  • G. V. Uma
    • 1
  1. 1.Department of Computer Science and Engineering, College of EngineeringAnna University, GuindyChennaiIndia

Personalised recommendations