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

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn , Issue , 2004, Pages 112-121

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

^a SHINSHU UNIVERSITY   (Japan)

Author keywords

GQM; Non Functional Requirements (NFR); Requirements Elicitation; Stakeholders and their Preferences; Use Case Diagrams

Indexed keywords

MULTI AGENT SYSTEMS; PROJECT MANAGEMENT; QUALITY ASSURANCE; SOFTWARE ENGINEERING; STANDARDS;

GQM; NON-FUNCTIONAL REQUIREMENTS (NFR); REQUIREMENTS ELICITATION; STAKEHOLDERS AND THEIR PREFERENCES; USE CASE DIAGRAMS;

REQUIREMENTS ENGINEERING;

EID: 17044404282     PISSN: 1090705X     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (21)

1. IEEE Guide for Developing System Requirements Specifications, Dec. 1998. IEEE Std 1233-1998, ISBN 0-7381-0337-3 SH94654 (Print).
2. AL-Mail32. http://www.almail.com/. Japanese page only.
3. I. Alexander and S. Robertson. Understanding Project Sociology by Modeling Stakeholders. Software, 21(1):23-27, Jan./Feb. 2004.
4. V. R. Basili and D. M. Weiss. A Methodology for Collecting Valid Software Engineering Data. IEEE Transactions on Software Engineering, SE-10(6):728-738, Nov. 1984.
5. B. Boehm, P. Grunbacher, and R. O. Briggs. Developing Groupware for Requirements Negotiation: Lessons Learned. IEEE Software, 18(3):46-55, May/Jun. 2001.
6. L. Chung, B. A. Nixon, E. Yu, and J. Mylopoulos. Nonfunctional Requirements in Software Engineering. Kluwer Academic Publishers, 2000.
7. A. Cooper. The Inmates Are Running the Asylum. SAMS, 1999.
8. S. L. Cornford, M. S. Feather, J. C. Kelly, T. W. Larson, B. Sigal, and J. D. Kiper. Design and Development Assessment. In Proceedings of the Tenth International Workshop on Software Specification and Design (IWSSD'00), 2000.
9. M. Fowler and K. Scott. UML Distilled, Applying the Standard Object Modeling Language. Addison-Wesley, 1st edition, 1997.
10. X. Franch and J. P. Carvallo. Using Quality Models in Software Package Selection. Software, 20(1):34-33, Jan./Feb. 2003.
11. M. Glinz. A Lightweight Approach to Consistency of Scenarios and Class Models. In 4th International Conference on Requirements Engineering, pages 49-58, 2000.
12. International Standard ISO/IEC 9126-1. Software engineering - Product quality - Part 1: Quality model, 2001.
13. H. Kaiya, H. Horai, and M. Saeki. AGORA: Attributed Goal-Oriented Requirements Analysis Method. In IEEE Joint International Requirements Engineering Conference, RE'02, pages 13-22, Sep. 2002.
14. J. Kato, M. Saeki, A. Ohnishi, M. Nagata, H. Kaiya, S. Komiya, S. Yamamoto, H. Horai, and K. Watahiki. PAORE: Package Oriented Requirements Elicitation. In Proceedings of 10th Asia-Pacific Software Engineering Conference (APSEC 2003), pages 17-26, Chiang Mai, Thailand, Dec. 2003. IEEE Computer Society Press.
15. L. A. Macaulay. Requirements Engineering. Applied Computing. Springer, 1996.
16. B. Nuseibeh, J. Kramer, and A. Finkelstein. A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification. IEEE Transations on Software Engineering, 20(10):760-773, Oct 1994.
17. M. Saeki and H. Kaiya. Transformation Based Approach for Weaving Use Case Models in Aspect-Oriented Requirements Analysis. In The 4th AOSD Modeling With UML Workshop, Oct. 2003. Joint workshop of UML 2003, http://www.cs.iit.edu/ ~oaldawud/AO-M/index.httn.
18. T. Systa. Understanding the Behavior of Java Programs. In Seventh Working Conference on Reverse Engineering, pages 214-223, 2000.
19. S. Szejko. Requirements Driven Quality Control. In COMP-SAC'2002, pages 125-130, 2002.
20. The Mutt E-Mail Client, http://www.mutt.org/.
21. The RAND MH Message Handling System UCI version 6.8.3. http://www.ics.uci.edu/%7Emh/.