IEICE Transactions on Information and Systems

IEICE Transactions on Information and Systems 2008 E91-D(4):897-906; doi:10.1093/ietisy/e91-d.4.897

This Article Abstract Full Text (PDF) Alert me when this article is cited Alert me if a correction is posted Services Email this article to a friend Similar articles in this journal Alert me to new issues of the journal Add to My Personal Archive Download to citation manager Request Permissions Google Scholar Articles by KAIYA, H. Articles by KAIJIRI, K. Social Bookmarking          What's this?

Copyright © 2008 The Institute of Electronics, Information and Communication Engineers

Special Section on Knowledge-Based Software Engineering -- Papers -- Software Engineering

Identifying Stakeholders and Their Preferences about NFR by Comparing Use Case Diagrams of Several Existing Systems

Haruhiko KAIYA¹, Akira OSADA¹ and Kenji KAIJIRI¹

¹ The authors are with the Graduate School of Science and Technology, Shinshu University, Nagano-shi, 380–8553 Japan. E-mail: kaiya{at}cs.shinshu-u.ac.jp

We present a method to identify stakeholders and their preferences about non-functional requirements (NFR) by using use case diagrams of existing systems. We focus on the changes about NFR because such changes help stakeholders to identify their preferences. Comparing different use case diagrams of the same domain helps us to find changes to be occurred. We utilize Goal-Question-Metrics (GQM) method for identifying variables that characterize NFR, and we can systematically represent changes about NFR using the variables. Use cases that represent system interactions help us to bridge the gap between goals and metrics (variables), and we can easily construct measurable NFR. For validating and evaluating our method, we applied our method to an application domain of Mail User Agent (MUA) system.

Key Words: non-functional requirements (NFR), GQM, stakeholders and their preferences, use case diagrams

---

Manuscript received July 2, 2007. Manuscript revised October 12, 2007.

Reference

[1] L.A. Macaulay, Requirements Engineering, Applied Computing, Springer, 1996.

[2] I. Alexander and S. Robertson, "Understanding project sociology by modeling stakeholders," Software, vol.21, no.1, pp.23–27, Jan./Feb. 2004.

[3] N. Rozanski and E. Woods, Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives, Addison Wesley, 2005.

[4] V.R. Basili and D.M. Weiss, "A methodology for collecting valid software engineering data," IEEE Trans. Softw. Eng., vol.SE-10, no.6, pp.728–738, Nov. 1984.

[5] "IEEE guide for developing system requirements specifications," Dec. 1998. IEEE Std 1233-1998, ISBN 0-7381-0337-3 SH94654 (Print).

[6] L. Chung, B.A. Nixon, E. Yu, and J. Mylopoulos, Non-functional Requirements in Software Engineering, Kluwer Academic Publishers, 2000.

[7] T. Systa, "Understanding the behavior of Java programs," Seventh Working Conference on Reverse Engineering, pp.214–223, 2000.

[8] M. Glinz, "A lightweight approach to consistency of scenarios and class models," 4th International Conference on Requirements Engineering, pp.49–58, 2000.

[9] M. Fowler and K. Scott, UML Distilled, Applying the Standard Object Modeling Language, 1st ed., Addison-Wesley, 1997.

[10] A. Cockburn, Writing Effective Use Cases, Addison-Wesley, 2000.

[11] International Standard ISO/IEC 9126-1, "Software engineering – Product quality - Part 1: Quality model," 2001.

[12] B. Potter, J. Sinclair, and D. Till, An Introduction to Formal Specification and Z, Prentice Hall International, 1991.

[13] The RAND MH Message Handling System UCI version 6.8.3, "http://www.ics.uci.edu/%7Emh/."

[14] AL-Mail32, "http://www.almail.com/." Japanese page only.

[15] The Mutt E-Mail Client, "http://www.mutt.org/."

[16] M. Saeki and H. Kaiya, "Transformation based approach for weaving use case models in aspect-oriented requirements analysis," 4th AOSD Modeling With UML Workshop, Oct. 2003. Joint Workshop of UML2003, http://www.cs.iit.edu/~oaldawud/AOM/index.htm

[17] B. Boehm, P. Grunbacher, and R.O. Briggs, "Developing groupware for requirements negotiation: Lessons learned," IEEE Softw., vol.18, no.3, pp.46–55, May/June 2001.

[18] S.L. Cornford, M.S. Feather, J.C. Kelly, T.W. Larson, B. Sigal, and J.D. Kiper, "Design and development assessment," Proc. Tenth International Workshop on Software Specification and Design (IWSSD'00), pp.105–114, 2000.

[19] H. Kaiya, H. Horai, and M. Saeki, "AGORA: Attributed goal-oriented requirements analysis method," IEEE Joint International Requirements Engineering Conference, RE'02, pp.13–22, Sept. 2002.

[20] J. Kato, M. Saeki, A. Ohnishi, M. Nagata, H. Kaiya, S. Komiya, S. Yamamoto, H. Horai, and K. Watahiki, "PAORE: Package oriented requirements elicitation," Proc. 10th Asia-Pacific Software Engineering Conference (APSEC 2003), pp.17–26, Chiang Mai, Thailand, IEEE Computer Society Press, Dec. 2003.

[21] M. Makino and A. Ohnishi, "A scenario generation method using a differential scenario," ICSOFT, pp.279–282, 2006.

[22] S. Szejko, "Requirements driven quality control," COMPSAC'2002, pp.125–130, 2002.

[23] X. Franch and J.P. Carvallo, "Using quality models in software package selection," Software, vol.20, no.1, pp.34–33, Jan./Feb. 2003.

CiteULike    Connotea    Del.icio.us    What's this?

This Article Abstract Full Text (PDF) Alert me when this article is cited Alert me if a correction is posted Services Email this article to a friend Similar articles in this journal Alert me to new issues of the journal Add to My Personal Archive Download to citation manager Request Permissions Google Scholar Articles by KAIYA, H. Articles by KAIJIRI, K. Social Bookmarking          What's this?