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:48, 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. In KAOS, the requirements can be represented in the form of goals, which can be functional or non-functional.[2] For the representation of the goals are used five sub-models of which the two main ones are: the object model which uses the UML class diagram for the representation of domain vocabulary and the goal model for the determination of requirements to be satisfied by the system and of expectations with regard to the environment through a goals hierarchy.

As a result of KAOS, requirements can be structured methodically and logically, and problems can be solved by using graphical methods.

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.

Process of writing a requirement document using KAOS [4]

  1. Give a description of the problem
  2. Give a target model for the system (including which target model you have used)
  3. Give one of the responsibility models for the system(The responsibility model describes the requirements or expectations of each agent and the tasks assigned to him.)
  4. Give one of the object models of the system.(The object model is used to define and document relevant concepts in the application domain, presenting static constraints between concepts so as to satisfy design requirements. There are three types of objects that coexist in the object model, namely entities, agents and associations.)
  5. Give the operational process model for the main objects in the system.(The operational process model of Kaos describes the requirements that the agent needs to fulfill.)
  6. Give potential obstacles to the achievement of the system's objectives.(An obstacle is a situation that violates a goal, expectation or requirement. For a secure system, it is important to address potential barriers, which allows the analyst to address special situations that may occur during the requirements engineering phase, rather than coming to a solution when the system is running out of steam, thus ensuring the robustness of the system.)
  7. Write a requirements document for the system based on the IEEE standard template.

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)
  4. ^ "软件需求工程--KAOS建模_Jane-Young的博客-CSDN博客_kaos建模". blog.csdn.net. Retrieved 2023-01-13.
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Ipoxylari/KAOS_(software_development)&oldid=1133396237"