KAOS (software Development)
   HOME

TheInfoList



OR:

KAOS, is a goal-oriented
software requirements Software requirements for a system are the description of what the system should do, the service or services that it provides and the constraints on its operation. The IEEE Standard Glossary of Software Engineering Terminology defines a requirement ...
capturing approach in
requirements engineering Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering. The first use of the term ''requirement ...
. It is a specific
Goal modeling A goal model is an element of requirements engineering that may also be used more widely in business analysis. Related elements include stakeholder analysis, context analysis, and scenarios, among other business and technical areas. Principles Go ...
method; another is i*. It allows for requirements to be calculated from goal diagrams. KAOS stands for ''Knowledge Acquisition in automated specification'' or ''Keep All Objectives Satisfied''. The University of Oregon and the University of Louvain (Belgium) designed the KAOS methodology in 1990 by Axel van Lamsweerde and others.A KAOS Tutorial
It is taught worldwide at the university level for capturing software requirements. There is lack of evidence that KAOS is used in the industry and as of February 2023, the only tool supporting it i
Objectiver
written by the same group behind the KAOS methodology, with the latest release 3.0c47 dated at March 9th, 2012.


External links


A KAOS TutorialGoal-Oriented Requirements Engineering: An Overview of the Current ResearchEvaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method


References

{{DEFAULTSORT:Kaos (Software Development) Software requirements Systems analysis