Analyzing user requirements by use cases: A goal-driven approach

IEEE Software

Volumn 16, Issue 4, 1999, Pages 92-101

  Lee, Jonathan ^a   Xue, Nien Lin ^b  

^a NATIONAL CENTRAL UNIVERSITY   (Taiwan)

^b NONE

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER SYSTEMS PROGRAMMING; FLOWCHARTING; LOGIC PROGRAMMING; REQUIREMENTS ENGINEERING;

GOAL-DRIVEN USE CASES (GDUC); USE-CASE MODELS;

SOFTWARE ENGINEERING;

EID: 0032638574     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/52.776956     Document Type: Article

References (19)

1. I. Jacobson, Object-Oriented Software Engineering, Addison Wesley Longman, Reading, Mass., 1992.
2. J. Rumbaugh, "Getting Started: Using Use Cases to Capture Requirements," J. Object-Oriented Programming, Vol. 7, No. 5, Sept. 1994, pp. 8-12.
3. T. Rowlett, "Building an Object Process around Use Cases," J. Object-Oriented Programming, Vol. 11, No. 1, Mar./Apr. 1998, pp. 53-58.
4. B. Dano, H. Briand, and F. Barbier, "Progressing towards Object-Oriented Requirements Specifications by Using the Use Case Concept," Proc. Int'l Conf. Requirements Eng., IEEE Computer Soc. Press, Los Alamitos, Calif., 1996, pp. 450-456.
5. K.S. Rubin and A. Goldberg, "Object Behavior Analysis," Comm. ACM, Vol. 35, No. 9, Sept. 1992, pp. 48-62.
6. K. Pohl, "The Three Dimensions of Requirements Engineering: A Framework and Its Applications," Information Systems, Vol. 19, No. 3, 1994, pp. 243-258.
7. P.A. Muller, Instant UML, Wrox Press Ltd., Olton, Birmingham, UK, 1997.
8. B. Regnell, M. Andersson, and J. Bergstrand, "A Hierarchical Use Case Model with Graphical Representation," Proc. IEEE Symp. and Workshop on Engineering of Computer-Based Systems, IEEE Computer Soc. Press, Los Alamitos, Calif., 1996, pp. 270-277.
9. A. Borgida, S. Greenspan, and J. Mylopoulos, "Knowledge Representation as the Basis for Requirements Specification," Computer, Apr. 1985, pp. 82-91.
10. A. Finkelstein and R.C. Waters, "Summary of the Requirements Elicitation, Analysis and Formalization Track," ACM Software Eng. Notes, Vol. 14, No. 5, 1989, p. 40.
11. M.P. Georgeff and A.L. Lansky, "Procedural knowledge." Proc. IEEE, Vol. 74, No. 10, Oct. 1986, pp. 1383-1398.
12. C. Potts, K. Takahashi, and A.I. Anton, "Inquiry-Based Requirements Analysis," IEEE Software, Mar. 1994, pp. 21-32.
13. A. Dardenne, A. van Lamsweerde, and S. Fickas, "Goal-Directed Requirements Acquisition," Science of Computer Programming, Vol. 20, 1993, pp. 3-50.
14. J. Mylopoulos, L. Chung, and B. Nixon, "Representing and Using Nonfunctional Requirements: A Process-Oriented Approach," IEEE Trans. Software Eng., Vol. 18, No. 6, 1992, pp. 483-497.
15. J. Lee and J.Y. Kuo, "New Approach to Requirements Trade-Off Analysis for Complex Systems," IEEE Trans. Knowledge and Data Eng., Vol. 10, No. 4, July/Aug. 1998, pp. 551-562.
16. A. Cockburn, "Goals and Use Cases," J. Object-Oriented Programming, Vol. 10, No. 7, Sept. 1997, pp. 35-40.
17. B. Boehm and H. In, "Identifying Quality-Requirement Conflicts," IEEE Software, Mar. 1996, pp. 25-35.
18. A. van Lamsweerde, R. Darimont, and P. Massonet, Goal-Directed Elaboration of Requirements for a Meeting Scheduler Problems and Lessons Learnt, Tech. Report RR-94-10, Universite Catholique de Louvain, Louvain-la-Neuve, Belgium, 1994.
19. J. Karlsson and K. Ryan, "A Cost-Value Approach for Prioritizing Requirements," IEEE Software, Sept./Oct. 1997, pp. 67-74.