Skip to main content
  • 1357 Accesses

Abstract

We know that a conceptual schema defines the general knowledge required by an information system to perform its functions. But what are the functions of the information system, and what is the knowledge required to perform them? Currently, the answer to these questions is based on the use cases. Use cases define the functionality provided by an information system. The use cases of an information system are determined during requirements elicitation, one of the most important phases of requirements engineering.

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

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD 54.99
Price excludes VAT (USA)
  • Durable hardcover 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.

15.4 Bibliographical Notes

  • Adolph S, Bramble P (2003) Patterns for effective use cases. Addison-Wesley.

    Google Scholar 

  • Alexander IF, Maiden N (eds) (2004) Scenarios, stories, use cases through the systems development life-cycle. Wiley.

    Google Scholar 

  • Cockburn A (2001) Writing effective use cases. Addison-Wesley.

    Google Scholar 

  • Constantine LL, Lockwood LAD (1999). Software for use. Addison-Wesley.

    Google Scholar 

  • D’Souza DF, Wills AC (1999) Objects, components and frameworks with UML: The Catalysis approach. Addison-Wesley.

    Google Scholar 

  • Glinz M (2000) A lightweight approach to consistency of scenarios and class models. ICRE 2000:49–58.

    Google Scholar 

  • Insfrán E, Pastor O, Wieringa R (2002) Requirements engineering-based conceptual modelling. Requir. Eng. 7:61–72.

    Article  Google Scholar 

  • Jacobson I (2004) Use cases — yesterday, today and tomorrow. Software and Systems Modeling 3(3):210–220.

    Article  Google Scholar 

  • Larman C (2005) Applying UML and Patterns: An Introduction to object-oriented analysis and design and iterative development. 3rd edn. Prentice Hall.

    Google Scholar 

  • McMenamim SM, Palmer JF (1984) Essential systems analysis. Yourdon Press/Prentice Hall.

    Google Scholar 

  • Rolland C, Ben Achour C, Cauvet C, Ralyté J, Sutcliffe A, Maiden NAM, Jarke M, Haumer P, Pohl K, Dubois E, Heymans P (1998) A proposal for a scenario classification framework. Requir. Eng. 1:23–47.

    Google Scholar 

  • Sendall S, Strohmeier A (2000) From use cases to system operation specifications. UML 2000, LNCS 1939:1–15.

    Google Scholar 

Download references

Rights and permissions

Reprints and permissions

Copyright information

© 2007 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

(2007). Use Cases. In: Conceptual Modeling of Information Systems. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-39390-0_15

Download citation

  • DOI: https://doi.org/10.1007/978-3-540-39390-0_15

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-39389-4

  • Online ISBN: 978-3-540-39390-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics