KAOS, is a goal-oriented software requirements capturing approach in requirements engineering. It is a specific Goal modeling method; another is i*. It allows for requirements to be calculated from goal diagrams.[1] KAOS stands for Knowledge Acquisition in automated specification[2] or Keep All Objectives Satisfied.[3]

The University of Oregon and the University of Louvain (Belgium) designed the KAOS methodology in 1990 by Axel van Lamsweerde and others.[4] It is taught worldwide at the university level[5] for capturing software requirements.

There is lack of evidence that KAOS is used in the industry[6] and as of February 2023, the only tool supporting it is Objectiver, written by the same group[7] behind the KAOS methodology, with the latest release 3.0c47 dated at March 9th, 2012.[8]

References

  1. ↑ Goal-Oriented Requirements Engineering: An Overview of the Current Research.
  2. ↑ A. Dardenne, A. van Lamsweerde and S. Fickas. Goal-Directed Requirements Acquisition. Science of Computer Programming, 20(1-2), April 1993.
  3. ↑ A. van Lamsweerde, E. Letier. From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering. Proc. Radical Innovations of Software and Systems Engineering, LNCS, 2003.
  4. ↑ A KAOS Tutorial.
  5. ↑ List of universities teaching KAOS include Michigan State (lectures), Pace (lectures), Louvain (lectures), Coimbra and others.
  6. ↑ "Is KAOS goal modeling used in the industry?". Software Engineering Stack Exchange. Retrieved 5 February 2023.
  7. ↑ "Respect-IT technology". Objectiver homepage. Retrieved 5 February 2023.
  8. ↑ "Objectiver releases". Objectiver homepage. Retrieved 5 February 2023.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.