computer science

KAOS (software development)

KAOS (software development) is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand KAOS (software development) rather than just read about it. In short: KAOS, is a goal-oriented software requirements capturing approach in requirements engineering. It is a specific Goal modeling method; another is i*.

Key takeaways

KAOS (software development) belongs to computer science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect KAOS (software development) to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of KAOS (software development) from memory before moving on to harder problems.

Reference excerpt

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. 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. 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 is 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 Tutorial Goal-Oriented Requirements Engineering: An Overview of the Current Research Evaluating the Effectiveness of a Goal-Oriented Requirements Engineering Method

References

Worked examples

Example 1 — a first encounter with KAOS (software development)

Start with the simplest possible case. Write down what KAOS (software development) claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to KAOS (software development) before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about KAOS (software development) ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of KAOS (software development)

In research: KAOS (software development) appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses KAOS (software development) in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: KAOS (software development) is common in secondary-school and first-year university syllabi. It links to neighbouring topics Software requirements, Systems analysis, so understanding it makes those chapters shorter.
In everyday life: Look for KAOS (software development) outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study KAOS (software development) in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what KAOS (software development) means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain KAOS (software development) out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is KAOS (software development) in simple terms?

KAOS, is a goal-oriented software requirements capturing approach in requirements engineering. It is a specific Goal modeling method; another is i*.

Why does KAOS (software development) matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study KAOS (software development)?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on KAOS (software development).