Skip to main content

Task-Driven Requirements in Object-Oriented Development

  • Chapter
Perspectives on Software Requirements

Abstract

There is no accepted method today that integrates requirements engineering and object-oriented development for user interface and information-intensive systems. In this paper we present the major issues such a method has to deal with and illustrate them with examples from our method TORE (Task and Object-oriented 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 84.99
Price excludes VAT (USA)
  • Available as EPUB and 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
Hardcover Book
USD 109.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.

References

  1. Armour, F., Miller, G. Advanced Use Case Modeling. New York: Addison-Wesley, 2000.

    Google Scholar 

  2. Atkinson, C., Bayer, J., Bunse, Ch., Kamsties, E., Laitenberger, O., Laqua, R., Muthig, D., Paech, B., Wüst, J., Zettel, J. Component-based product Line Engineering with UML. New York: Addison Wesley, Component Software Series, 2002.

    Google Scholar 

  3. Beyer, H., Holtzblatt, K. Contextual Design: Defining Customer Centered Systems. London: Morgan Kaufmann Publishers, 1998.

    Google Scholar 

  4. Booch, G. Object-Oriented Analysis and Design with Applications. San Mateo, California: Benjamin Cummings, 1994.

    Google Scholar 

  5. Chung, L., Nixon, B.A., Yu, E., Mylopoulos, J. Non-Functional Requirements in Software Engineering. Boston: Kluwer Academic Publishers, 2000.

    MATH  Google Scholar 

  6. Cockburn, A. Writing Effective Use Cases. New York: Addison Wesley, 2001.

    Google Scholar 

  7. Coleman D., Arnold P., Bodoff S., Dollin C., Gilchrist, H., Hayes F., and Jeremaes P. Object-oriented Development: The Fusion Method. Englewood Cliffs, NJ: Prentice Hall, 1994.

    Google Scholar 

  8. Constantine, L., Lockwood, L. Software For Use. New York: Addison Wesley, 1999.

    Google Scholar 

  9. Diaper, D. Task analysis for human-computer interaction. Chichester, UK: Ellies Horwood, 1989.

    Google Scholar 

  10. Dray, S., Mrazek, D. “A day in the life: Studying context across cultures”. In International User Interfaces, Nielsen, del Galdo, eds. New York: John Wiley & Sons, 1996.

    Google Scholar 

  11. Downs, E., Clare, P., Coe, I. Structured Systems Analysis and Design Method: Application and Context. Hertfordshire, UK: Prentice Hall, 1992.

    Google Scholar 

  12. DeMarco, T. Structured Analysis and System Specification. New York: Yourdon Press, 1978.

    Google Scholar 

  13. Hackos, J.T., Redish, J.C. User and Task Analysis for Interface Design. New York: John Wiley & Sons, 1998.

    Google Scholar 

  14. Jacobson I. Object-Oriented Software Engineering. Reading, MA: Addison-Wesley, 1992.

    MATH  Google Scholar 

  15. Jacobson, I, Booch G., Rumbaugh J. The Unified Software Development Process. New York: Addison Wesley, 1999.

    Google Scholar 

  16. Jacobson, I., Ericsson, M., Jacobson, A. The Object Advantage: Business Process Reengineering with Object Technology. New York: Addison-Wesley, 1994.

    Google Scholar 

  17. Kohler, K., Paech, B. Requirement Documents that Win the Race, Not Overweight or Emaciated but Powerful and in Shape. Proceedings of TCRE’02, First Workshop for Time Constrained Requirements Engineering; 2002, Septermber 9; Essen, Germany.

    Google Scholar 

  18. Kovitz, B.L. Practical Software Requirements. A Manual of Content and Style. Greenwich: Manning Publications Co., 1998.

    Google Scholar 

  19. Kruchten, P. B. The Rational Unified Process: An Introduction. New York: Addison-Wesley, 2000.

    Google Scholar 

  20. van Lamsweerde, A., Darimont, R., Massonet, P. Goal-directed elaboration of requirements for a meeting scheduler: problems and lessons learnt. Proceedings of RE’95, Int. Symp. on Requirements Engineering. 1998 March 27–29; York, UK. IEEE Computer Society Press.

    Google Scholar 

  21. Lauesen, S. Software Requirements — Styles and Techniques. New York: Addison Wesley, 2002.

    Google Scholar 

  22. Lauesen, S., Harning, S. Virtual Windows: Linking User Tasks, Data Models and Interface Design. IEEE Software 2001; 18(4):67–75.

    Article  Google Scholar 

  23. Macaulay, L.A. Requirements Engineering. Springer Verlag Series on Applied Computing, 1996.

    Book  MATH  Google Scholar 

  24. Moynihan, T. Objects versus Functions in User-Validation of Requirements: Which Paradigm Works Best?. Proceedings of OOIS’94, International Conference on Object Oriented Information Systems; 1994 December 19–21; London, UK. Springer, 1995.

    Google Scholar 

  25. Oestereich, B., Objektorientierte Softwareentwicklung: Analyse und Design mit der Unified Modeling Language. Oldenbourg Wissenschaftsverlag GmbH, 2001.

    Google Scholar 

  26. OMG, “The Unified Modeling Language”, http://www.omg.org/uml/

  27. Paech, B. Aufgabenorientierte Softwareentwicklung- Integrierte Gestaltung von Unternehmen, Arbeit und Software. Springer Verlag, 2000.

    MATH  Google Scholar 

  28. Rudd, J., Stern, K., Isensee, S. Low vs. High Fidelity Prototyping Debate. Interactions 1996;2(1):76–85.

    Article  Google Scholar 

  29. Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F. and Lorensen, W. Object-Oriented Modeling and Design. Englewood Cliffs, NJ: Prentice Hall International, 1991.

    Google Scholar 

  30. Scheer, A. ARTS — Business Process Frameworks, Business Process Modeling. Springer-Verlag, 1999.

    Book  Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2004 Springer Science+Business Media New York

About this chapter

Cite this chapter

Paech, B., Kohler, K. (2004). Task-Driven Requirements in Object-Oriented Development. In: do Prado Leite, J.C.S., Doorn, J.H. (eds) Perspectives on Software Requirements. The Springer International Series in Engineering and Computer Science, vol 753. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-0465-8_3

Download citation

  • DOI: https://doi.org/10.1007/978-1-4615-0465-8_3

  • Publisher Name: Springer, Boston, MA

  • Print ISBN: 978-1-4613-5090-3

  • Online ISBN: 978-1-4615-0465-8

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics