Sizing use cases: How to create a standard metrical approach

Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)

Volumn 2425, Issue , 2002, Pages 409-421

  Henderson Sellers, B ^a   Zowghi, D ^a   Klemola, T ^a   Parasuram, S ^a  

^a UNIVERSITY OF TECHNOLOGY SYDNEY   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

INFORMATION SYSTEMS; INFORMATION USE; SOFTWARE DESIGN;

CASE DESCRIPTION; EXTERNAL FEATURES; QUALITY OF COMMUNICATION; REQUIREMENTS ELICITATION; RESEARCH QUESTIONS; SOFTWARE DEVELOPMENT PROCESS; STANDARD FORMAT;

OBJECT ORIENTED PROGRAMMING;

EID: 84944065811     PISSN: 03029743     EISSN: 16113349     Source Type: Book Series    
DOI: 10.1007/3-540-46102-7_43     Document Type: Conference Paper

References (34)

1. Nuseibeh, B and Easterbrook, S., 2000, Requirements engineering: a roadmap., in Future of Software Engineering (22nd IEEE Int. Conf. on Software Engineering), 35-46
2. Davis, A. M., Jordan, K, and Nakajima, T., 1997, Elements underlying specifications of requirements, Annals of Software Engineering, 3, 63-100
3. Jacobson, I., Christerson, M., Jonsson, P. and Övergaard, G., 1992, Object- Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley
4. Constantine, L.L., 1997, The case for essential use cases, Object Magazine, 7(3), 72-70
5. Korson, T., 1998, The misuse of use cases (managing requirements), Object Magazine, 8(3), 18-20
6. Leffingwell, D., Widrig, D., 2000, Managing Software Requirements, A Unified Approach, Addison-Wesley
7. Kosters, G. et al., 2001, Coupling use cases and class models as a means for validation and verification of requirements specification, Req. Eng. Journal, 6(1), 3-17
8. Cockburn, A., 2000, Writing Effective Use Cases, Addison Wesley
9. Jacobson, I., 1994a, Basic use-case modeling. ROAD, 1(2), 15-19
10. OMG, 2001, OMG Unified Modeling Language Specification, Version 1.4, September 2001, OMG document formal/01-09-67 [Online]. Available http://www.omg.org
11. Jacobson, I., 1994c, Use cases and object, ROAD, 1(4), 8-10
12. Jacobson, I., 1994b, Basic use-case modeling (Continued), ROAD, 1(3), 7-9
13. Graham, I., 1998, Requirements Engineering and Rapid Development. An Object- Oriented Approach, Addison-Wesley
14. Simons, A.J.H. and Graham, I., 1998, 37 things that don’t work in objectoriented modelling with UML, BCS Obj.-Oriented Prog. Sys. Newsletter, 35 (eds. S Kent & R Mitchell)
15. Simons, A.J.H. and Graham, I., 1999, 30 Things that go wrong in object modeling with UML 1.3, chapter 16 in: Behavioral Specifications of Businesses and Systems, (Eds. H Kilov, B Rumpe and I Simmonds), Kluwer Academic Publishers, 237-257
16. Simons, A.J.H., 1999, Use cases considered harmful, Procs. TOOLS 29, (Eds. R. Mitchell, AC Wills, J Bosch and B Meyer), IEEE Computer Society, 94-203
17. Lilly, S., 1999, Use case pitfalls: top 10 problems from real projects using use cases, Procs. TOOLS 30 (eds. D. Firesmith, R. Riehle, G. Pour and B. Meyer), IEEE Computer Society Press, 174-183
18. Kruchten, Ph., 2000, The Rational Unified Process: An Introduction, Second edition, Addison Wesley
19. Regnell, B., 1996, Hierarchical use case modelling for requirements engineering, Report Number 120, Doctoral Thesis, Dept Communication Systems, Lund University, Sweden
20. Cockburn, A., 1997a, Goals and use cases, J. Obj.Oriented Progr., 10(5), 35-40
21. Cockburn, A., 1997b, Using goal-based use cases, J. Obj.Oriented Progr., 10(7), 56-62
22. Achour, C.B., Rolland, C., Maiden, N.A.M. and Souveyet, C., 1999, Guiding use case authoring: results of an empirical study, Procs. Fourth IEEE International Symposium on Requirements Engineering (RE99), University of Limerick, Ireland
23. Firesmith, D.G., 1999, Use case modeling guidelines, Procs. TOOLS 30 (eds. D. Firesmith, R. Riehle, G. Pour and B. Meyer), IEEE Computer Society Press, 184-193
24. Verner, J.M. and Tate, G., 1992, A software size model, IEEE Trans. Soft. Eng., 18(4), 265-278
25. Costello, R.J. and Liu, D.-B., 1995, Metrics for requirements engineering, Journal of Systems Software, 29, 39-63
26. Davis, A., 1993, Software Requirements Analysis and Specification (2nd ed.), Prentice Hall
27. Zowghi, D., Offen, R. and Nurmuliani, 2000, The impact of requirements volatility on the software development lifecycle, Procs Int Conf on Software, Theory and Practice (ICS2000), IFIP World Computer Conference, Beijing, China, August 2000
28. Gotel, O.C.Z and Finkelstein, A.C.W., 1994, An analysis of the requirements traceability problem, Procs. First Int. Conf. Requirements Engineering (ICRE94), 94-101
29. Schneider, G. and Winters, J.P., 1998, Applying Use Cases: A Practical Guide, Addison-Wesley
30. Constantine, L.L. and Lockwood, L.A.D., 1999, Software for Use, Addison- Wesley
31. Marchesi, M., 1998, OOA metrics for the Unified Modeling Language, Euromicro Conference on Software Maintenance and Reengineering
32. Whitmire, S.A., 1997, Object Oriented Design Measurement, John Wiley & Sons
33. Henderson-Sellers, B. and Unhelkar, B., 2000, OPEN Modeling with UML, Addison-Wesley
34. Fenton, N.E., 1994, Software measurement: a necessary scientific basis, IEEE Trans. Soft. Eng., 20, 199-206