Jump to content

User:Ipoxylari/KAOS (software development)

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Ipoxylari (talk | contribs) at 15:15, 13 January 2023. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

KAOS, is an acronym for Knowledge Acquisition in autOmated Specification. KAOS, has been designed by Axel van Lamsweerde, Anne Dardenn, and Stephen Fickas at the University of Oregon and the University of Louvain (Belgium)[1]

It is considered a goal-Oriented requirements engineering approach that is used in the requirements acquisition phase of the software lifecycle. The KAOS is used in a variety of fields, including mechanics, telecommunications, and healthcare. This method is based on the idea of building requirements models and is thought to be an efficient method for eliciting goal-oriented requirements. As a result of KAOS, requirements can be structured methodically and logically, and problems can be solved by using graphical methods.[2]Concepts relevant to the problem description can be defined by using KAOS.

Contents

1.Components 1.1 Conceptual model

Components[3]

Conceptual model

Conceptual models provide abstract representations of requirements models that need to be acquired. Therefore it is considered a meta-model. Ideally, it should allow the precise and natural capture of both functional and non-functional requirements for any kind of composite system.

Acquisition strategies

The acquisition strategy defines a coherent set of steps for acquiring components of the requirements model as instances of meta-model components. To put it another way, a strategy describes how the meta-model graph is traversed to acquire instances of its various nodes and links

The acquisition assistant

With the acquisition assistant, it is possible to follow one or more acquisition strategies using automated assistance. It is constructed around two repositories: a requirements database and a requirements knowledge base. They are both structured based on the meta-model components. It is the requirements database that maintains the requirements model that has been built gradually during the acquisition process.

References

  1. ^ Cite error: The named reference :0 was invoked but never defined (see the help page).
  2. ^ Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method
  3. ^ Dardenne, Anne; van Lamsweerde, Axel; Fickas, Stephen (1993-04). "Goal-directed requirements acquisition". Science of Computer Programming. 20 (1–2): 3–50. doi:10.1016/0167-6423(93)90021-g. ISSN 0167-6423. {{cite journal}}: Check date values in: |date= (help)
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Ipoxylari/KAOS_(software_development)&oldid=1133391124"