AGORA: Attributed goal-oriented requirements analysis method

Proceedings of the IEEE International Conference on Requirements Engineering

Volumn 2002-January, Issue , 2002, Pages 13-22

  Kaiya, Haruhiko ^a   Horai, Hisayuki ^b   Saeki, Motoshi ^b  

^a SHINSHU UNIVERSITY   (Japan)

^b TOKYO INSTITUTE OF TECHNOLOGY   (Japan)

Author keywords

Goal Oriented Analysis; Quality Metrics; Requirements Elicitation

Indexed keywords

REQUIREMENTS ENGINEERING;

CONTRIBUTION VALUES; GOAL ORIENTED REQUIREMENTS ANALYSIS; GOAL-ORIENTED ANALYSIS; QUALITY METRICS; REQUIREMENTS CHANGE; REQUIREMENTS ELICITATION; REQUIREMENTS SPECIFICATIONS; STRUCTURAL CHARACTERISTICS;

QUALITY CONTROL;

EID: 17044381781     PISSN: 1090705X     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICRE.2002.1048501     Document Type: Conference Paper

References (17)

1. IEEE Recommended Practice for Software Requirements Specifications, 1998. IEEE Std. 830-1998.
2. A. Anton and C. Potts. The use of goals to surface requirements for evolving systems. In Proc. of 20th International Conference on Software Engineering, pages 157-166, 1998.
3. B. Boehm, P. Bose, E. Horowitz, and M. Lee. Software Requirements Negotiation Aids: A Theory-W Based Spiral Approach. In Proc. of 17th International Conference on Software Engineering, pages 243-253, 1995.
4. J. P. Cavano and J. A. McCall. A Framework for the Measurement of Software Quality. In Proc. of ACM Software Quality Assurance Workshop, pages 133-139, 1978.
5. L. Chung, B. Nixon, E. Yu, and J. Mylopoulos. Non-Functional Requirements in Software Engineering. Academic Publishers, 1999.
6. 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.
7. R. J. Costello and D.-B. Liu. Metrics for Requirements Engineering. System Software, 29:39-63, 1995.
8. A. Dardenne, A. van Lamsweerde, and S. Fickas. Goaldirected Requirements Acquisition. Science of Computer Programming, 20:3-50, 1993.
9. A. Davis. Software Requirements. Prentice-Hall, 1990.
10. GRL homepage. http://www.cs.toronto.edu/km/ GRL/.
11. I∗ homepage. http://www.cs.toronto.edu/km/ istar/.
12. KAOS homepage. http://www.info.ucl.ac.be/ research/projects/AVL/ReqEng.html.
13. J. Karlsson and K. Ryan. A Cost-Value Approach for Prioritizing Requirements. IEEE Software, 14(5):67-74, Sep./Oct. 1997.
14. F. Moisiadis. A Framework for Prioritizing Use Cases. In Proceedings of the Fifth Doctoral Consortium at the Conference of Advanced Information Systems Engineering, Jun. 1998.
15. J. Mylopoulos, L. Chung, and E. Yu. From Object-Oriented to Goal-Oriented Requirements Analysis. Communications of the ACM, 42(1):31-37, Jan. 1999.
16. C. Rolland, G. Grosz, and R. Kla. Experience with Goal-Scenario Coupling in Requirements Engineering. In Proc. of RE'99, pages 7-11, Jun. 1999.
17. A. van Lamsweerde, R. Darimont, and P. Massonet. Goal-Directed Elaboration of Requirements for a Meeting Scheduler: Problems and Lessons Learnt. In Proc. of 2nd IEEE International Symposium on Requirements Engineering, pages 194-203, 1995.