Identifying stakeholders and their preferences about NFR by comparing use case diagrams of several existing systems

IEICE Transactions on Information and Systems

Volumn E91-D, Issue 4, 2008, Pages 897-906

  Kaiya, Haruhiko ^a   Osada, Akira ^a   Kaijiri, Kenji ^a  

^a SHINSHU UNIVERSITY   (Japan)

Author keywords

GQM; Non functional requirements (NFR); Stakeholders and their preferences; Use case diagrams

Indexed keywords

INFORMATION SCIENCE; SOFTWARE ENGINEERING;

EXISTING SYSTEMS; NONFUNCTIONAL REQUIREMENTS; STAKEHOLDERS AND THEIR PREFERENCES; SYSTEM INTERACTIONS; USE CASE DIAGRAM; USER AGENTS;

GRAPHIC METHODS;

EID: 68149171537     PISSN: 09168532     EISSN: 17451361     Source Type: Journal    
DOI: 10.1093/ietisy/e91-d.4.897     Document Type: Article

References (23)

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 InternationalWorkshop on Software Specification and Design (IWSSD'00), pp.105-114, 2000.
19. H. Kaiya, H. Horai, and M. Saeki, "AGORA: Attributed goaloriented 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.