Skip to main content
SpringerLink
Log in

Sizing Use Cases: How to Create a Standard Metrical Approach

  • Conference paper
  • First Online:
Object-Oriented Information Systems (OOIS 2002)

Part of the book series: Lecture Notes in Computer Science ((LNCS,volume 2425))

Included in the following conference series:

Abstract

Use-case modelling provides a means of specifying external features of a system during requirements elicitation. In principle, use cases can be used to size the system about to be built but, for that, a standard format for their documentation is required. Furthermore, gathering use-case metrics requires a software development process that produces complete use-case descriptions in a repeatable way. Here, we set out the requirements for such a standardization so that use cases can be metricated. Once accomplished, it is possible to evaluate the important research questions of whether use-case attributes such as size and complexity can be controlled and whether use-case metrics are sufficiently rigorous for estimating effort. Finally, we note that this added rigour applied to use cases should improve the consistency and quality of communication between client and developer, helping to ensure that the right system is built.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 84.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 109.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  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

    Google Scholar 

  2. Davis, A. M., Jordan, K, and Nakajima, T., 1997, Elements underlying specifications of requirements, Annals of Software Engineering, 3, 63–100

    Google Scholar 

  3. Jacobson, I., Christerson, M., Jonsson, P. and Övergaard, G., 1992, Object-Oriented Software Engineering: A Use Case Driven Approach, Addison-Wesley

    Google Scholar 

  4. Constantine, L.L., 1997, The case for essential use cases, Object Magazine, 7(3), 72–70

    Google Scholar 

  5. Korson, T., 1998, The misuse of use cases (managing requirements), Object Magazine, 8(3), 18–20

    Google Scholar 

  6. Leffingwell, D., Widrig, D., 2000, Managing Software Requirements, A Unified Approach, Addison-Wesley

    Google Scholar 

  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

    Google Scholar 

  8. Cockburn, A., 2000, Writing Effective Use Cases, Addison Wesley

    Google Scholar 

  9. Jacobson, I., 1994a, Basic use-case modeling. ROAD, 1(2), 15–19

    Google Scholar 

  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

    Google Scholar 

  12. Jacobson, I., 1994b, Basic use-case modeling (Continued), ROAD, 1(3), 7–9

    Google Scholar 

  13. Graham, I., 1998, Requirements Engineering and Rapid Development. An Object-Oriented Approach, Addison-Wesley

    Google Scholar 

  14. Simons, A.J.H. and Graham, I., 1998, 37 things that don’t work in object-oriented modelling with UML, BCS Obj.-Oriented Prog. Sys. Newsletter, 35 (eds. S Kent & R Mitchell)

    Google Scholar 

  15. Simons, A.J.H. and Graham, I., 1999, 30 Things that go wrong in object modelling 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

    Google Scholar 

  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

    Google Scholar 

  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

    Google Scholar 

  18. Kruchten, Ph., 2000, The Rational Unified Process: An Introduction, Second edition, Addison Wesley

    Google Scholar 

  19. Regnell, B., 1996, Hierarchical use case modelling for requirements engineering, Report Number 120, Doctoral Thesis, Dept Communication Systems, Lund University, Sweden

    Google Scholar 

  20. Cockburn, A., 1997a, Goals and use cases, J. Obj.Oriented Progr., 10(5), 35–40

    Google Scholar 

  21. Cockburn, A., 1997b, Using goal-based use cases, J. Obj.Oriented Progr., 10(7), 56–62

    Google Scholar 

  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

    Google Scholar 

  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

    Google Scholar 

  24. Verner, J.M. and Tate, G., 1992, A software size model, IEEE Trans. Soft. Eng., 18(4), 265–278

    Google Scholar 

  25. Costello, R.J. and Liu, D.-B., 1995, Metrics for requirements engineering, Journal of Systems Software, 29, 39–63

    Google Scholar 

  26. Davis, A., 1993, Software Requirements Analysis and Specification (2nd ed.), Prentice Hall

    Google Scholar 

  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

    Google Scholar 

  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

    Google Scholar 

  29. Schneider, G. and Winters, J.P., 1998, Applying Use Cases: A Practical Guide, Addison-Wesley

    Google Scholar 

  30. Constantine, L.L. and Lockwood, L.A.D., 1999, Software for Use, Addison-Wesley

    Google Scholar 

  31. Marchesi, M., 1998, OOA metrics for the Unified Modeling Language, Euromicro Conference on Software Maintenance and Reengineering

    Google Scholar 

  32. Whitmire, S.A., 1997, Object Oriented Design Measurement, John Wiley & Sons

    Google Scholar 

  33. Henderson-Sellers, B. and Unhelkar, B., 2000, OPEN Modeling with UML, Addison-Wesley

    Google Scholar 

  34. Fenton, N.E., 1994, Software measurement: a necessary scientific basis, IEEE Trans. Soft. Eng., 20, 199–206

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. University of Technology, Sydney, P.O. Box 123, 2007, Broadway, NSW, Australia

    B. Henderson-Sellers, D. Zowghi, T. Klemola & S. Parasuram

Authors
  1. B. Henderson-Sellers
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. D. Zowghi
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. T. Klemola
    View author publications

    You can also search for this author in PubMed Google Scholar

  4. S. Parasuram
    View author publications

    You can also search for this author in PubMed Google Scholar

Editor information

Editors and Affiliations

  1. UMR 5506 CNRS LIRMM - Laboratoire d’Informatique, de Robotique et de Microélectronique de Montpellier, Université Montpellier II, 161, Rue Ada, 34392, Montpellier, France

    Zohra Bellahsène

  2. School of Computing, Information Systems and Mathematics Centre for Information and Organisation Studies, South Bank University, 103 Borough Road, SE1 0AA, London, UK

    Dilip Patel

  3. Panthéon Sorbonne Centre de Recherche en Informatique, Université Paris 1, 90 Rue de Tolbiac, 75634, Paris cedex 13, France

    Colette Rolland

Rights and permissions

Reprints and permissions

Copyright information

© 2002 Springer-Verlag Berlin Heidelberg

About this paper

Cite this paper

Henderson-Sellers, B., Zowghi, D., Klemola, T., Parasuram, S. (2002). Sizing Use Cases: How to Create a Standard Metrical Approach. In: Bellahsène, Z., Patel, D., Rolland, C. (eds) Object-Oriented Information Systems. OOIS 2002. Lecture Notes in Computer Science, vol 2425. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-46102-7_43

Download citation

  • DOI: https://doi.org/10.1007/3-540-46102-7_43

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-44087-1

  • Online ISBN: 978-3-540-46102-9

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics

Search

Navigation