Skip to main content
SpringerLink
Log in

Is object-oriented requirements engineering of interest?

  • Viewpoints
  • Published:
Requirements Engineering Aims and scope Submit manuscript

Abstract

Different communities deal with the use of object-oriented (O-O) ideas for requirements engineering. Their views are different and many misunderstandings are around. Although O-O approaches are the most widely used in practice apart from pure natural language, there does not seem to be much interest in the scientific treatment of open issues in this regard. This article argues for taking such issues up (again).

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

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Fig. 1

Similar content being viewed by others

Notes

  1. ACM SIGPLAN conferences on object-oriented programming, systems, languages, and applications; for the upcoming conference see http://www.oopsla.org/2004/.

  2. IEEE international requirements engineering conferences; for the upcoming conference see http://www.re04.org/.

  3. Annual symposia of the international council on systems engineering; see http://www.incose.org/.

  4. Journals named Requirements Engineering (see http://rej.co.umist.ac.uk/) and Systems Engineering (see http://www3.interscience.wiley.com/cgi-bin/jhome/39084.)

  5. See http://oopsla.acm.org/oopsla2001/fp/tech/TuesPM.html.

  6. See http://www.incose.org/symp2004/.

  7. At the time of this writing, the specification of UML is available at http://www.omg.org.

References

  1. Davis AM (1993) Software requirements: objects, functions, and states. Prentice Hall, Englewood Cliffs, New Jersey

    Google Scholar 

  2. Davis AM, Hickey AM (2001) Requirements researchers: do we practice what we preach? Requirements Eng 7(2):107–111

    Article  Google Scholar 

  3. Jacobson I, Booch G, Rumbaugh J (1999) The unified software development process. Addison-Wesley, Reading, Massachusetts

    Google Scholar 

  4. Kaffenberger R (2003) Will object-oriented systems-engineering reshape requirements engineering? In: Proceedings of the 13th annual international symposium of the international council on systems engineering (INCOSE 2003), Arlington, Virginia, July 2003, pp 583–595

  5. Kaindl H (1997) A practical approach to combining requirements definition and object-oriented analysis. Ann Software Eng 3:319–343

    Article  Google Scholar 

  6. Kaindl H (1999) Difficulties in the transition from OO analysis to design. IEEE Softw 16(5):94–102

    Article  Google Scholar 

  7. Kaindl H (2001) A design process based on a model combining scenarios with goals and functions. IEEE Transact Syst Man Cybern (SMC) Part A 30(5):537–551

    Article  Google Scholar 

  8. Larman C (2001) Applying UML and patterns: an introduction to object-oriented analysis and design and the Unified Process, 2nd edn. Prentice Hall, Englewood Cliffs, New Jersey

    Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Institute of Computer Technology, Vienna University of Technology, Vienna, Austria

    Hermann Kaindl

Authors
  1. Hermann Kaindl
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Hermann Kaindl.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Kaindl, H. Is object-oriented requirements engineering of interest?. Requirements Eng 10, 81–84 (2005). https://doi.org/10.1007/s00766-004-0197-1

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s00766-004-0197-1

Keywords

Search

Navigation