KAOS (software development) explained

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]

External links

References

  1. http://www.cs.utoronto.ca/~alexei/pub/Lapouchnian-Depth.pdf 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. [Axel van Lamsweerde|A. van Lamsweerde]
  4. http://www.objectiver.com/fileadmin/download/documents/KaosTutorial.pdf A KAOS Tutorial
  5. List of universities teaching KAOS include Michigan State (lectures), Pace (lectures), Louvain (lectures), Coimbra and others.
  6. Web site: Is KAOS goal modeling used in the industry? . . 5 February 2023.
  7. Web site: Respect-IT technology . Objectiver homepage . 5 February 2023.
  8. Web site: Objectiver releases . Objectiver homepage . 5 February 2023.

This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "KAOS (software development)".

Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.