engineering

ISO/IEC 15288

ISO/IEC 15288 is a engineering 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 ISO/IEC 15288 rather than just read about it. In short: The ISO/IEC 15288 Systems and software engineering — System life cycle processes is a technical standard in systems engineering which covers processes and lifecycle stages, developed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). Planning for the ISO/IEC 15288:2002(E) standard started in 1994 when the need for a common systems engineering process…

Key takeaways

ISO/IEC 15288 belongs to engineering; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect ISO/IEC 15288 to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of ISO/IEC 15288 from memory before moving on to harder problems.

Reference excerpt

The ISO/IEC 15288 Systems and software engineering — System life cycle processes is a technical standard in systems engineering which covers processes and lifecycle stages, developed by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC). Planning for the ISO/IEC 15288:2002(E) standard started in 1994 when the need for a common systems engineering process framework was recognized. ISO/IEC/IEEE 15288 is managed by ISO/IEC JTC1/SC7, which is the committee responsible for developing standards in the area of Software and Systems Engineering. ISO/IEC/IEEE 15288 is part of the SC 7 Integrated set of Standards, and other standards in this domain include:

ISO/IEC TR 15504 which addresses capability ISO/IEC 12207 and ISO/IEC 15288 which address lifecycle and ISO 9001 & ISO 90003 which address quality

History The previously accepted standard MIL STD 499A (1974) was cancelled after a memo from the United States Secretary of Defense (SECDEF) prohibited the use of most U.S. Military Standards without a waiver (this memo was rescinded in 2005). The first edition was issued on 1 November 2002. Stuart Arnold was the editor and Harold Lawson was the architect of the standard. In 2004 this standard was adopted by the Institute of Electrical and Electronics Engineers as IEEE 15288. ISO/IEC 15288 was updated in 2008, then again (as a joint publication with IEEE) in 2015 and 2023.

ISO/IEC/IEEE 15288:2023, 16 May 2023 Revises: ISO/IEC/IEEE 15288:2015 (jointly with IEEE), 15 May 2015 Revises: ISO/IEC 15288:2008 (harmonized with ISO/IEC 12207:2008), 1 February 2008 Revises: ISO/IEC 15288:2002 (first edition), 1 November 2002

Processes The standard defines thirty processes grouped into four categories:

Agreement processes Organizational project-enabling processes Technical management processes Technical processes The standard defines two agreement processes:

Acquisition process (clause 6.1.1) Supply process (clause 6.1.2) The standard defines six organizational project-enabling processes:

Life cycle model management process (clause 6.2.1) Infrastructure management process (clause 6.2.2) Portfolio management process (clause 6.2.3) Human resources management process (clause 6.2.4) Quality management process (clause 6.2.5) Knowledge management process (clause 6.2.6) The standard defines eight technical management processes:

Project planning process (clause 6.3.1) Project assessment and control process (clause 6.3.2) Decision management process (clause 6.3.3) Risk management process (clause 6.3.4) Configuration management process (clause 6.3.5) Information management process (clause 6.3.6) Measurement process (clause 6.3.7) Quality assurance process (clause 6.3.8) The standard defines fourteen technical processes:

Business or mission analysis process (clause 6.4.1) Stakeholder needs and requirements definition process (clause 6.4.2) System requirements definition process (clause 6.4.3) Architecture definition process (clause 6.4.4) Design definition process (clause 6.4.5) System analysis process (clause 6.4.6) Implementation process (clause 6.4.7) Integration process (clause 6.4.8) Verification process (clause 6.4.9) Transition process (clause 6.4.10) Validation process (clause 6.4.11) Operation process (clause 6.4.12) Maintenance process (clause 6.4.13) Disposal process (clause 6.4.14) Each process is defined by a purpose, outcomes and activities. Activities are further divided into tasks.

See also Systems development life cycle System lifecycle Capability Maturity Model Integration (CMMI) ISO/IEC 12207 Concept of operations or CONOPS

References

Worked examples

Example 1 — a first encounter with ISO/IEC 15288

Start with the simplest possible case. Write down what ISO/IEC 15288 claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In engineering, 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 ISO/IEC 15288 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 ISO/IEC 15288 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 ISO/IEC 15288

In research: ISO/IEC 15288 appears in engineering 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 ISO/IEC 15288 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: ISO/IEC 15288 is common in secondary-school and first-year university syllabi. It links to neighbouring topics ISO/IEC JTC1/SC7 standards, ISO/IEC standards, Systems engineering, so understanding it makes those chapters shorter.
In everyday life: Look for ISO/IEC 15288 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.

Ask Teacher Smith questions about this articleOpens your AI tutor with a question about “ISO/IEC 15288” →

Affiliate

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

How to study ISO/IEC 15288 in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what ISO/IEC 15288 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 ISO/IEC 15288 out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is ISO/IEC 15288 in simple terms?

Why does ISO/IEC 15288 matter?

Because it connects several engineering 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 ISO/IEC 15288?

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 ISO/IEC 15288.