A build is not a pile of parts — it's a system with a life cycle: requirements, architecture, integration, verification. We run that life cycle to the international standard written for exactly this — ISO/IEC/IEEE 15288 — and we're a member of the body that defines the field.
ONE METHOD — ELECTRIFICATION · CONTROLS · AUTOMATION & TEST · R&D. SYSTEMS ENGINEERING IS HOW THE FOUR BECOME ONE MACHINE.
We're a member of the International Council on Systems Engineering through its Wright Brothers Chapter, of SAE International, and of IEEE and its Computer Society. Membership keeps us current on the standards as they evolve.
The international subcommittee for Software and systems engineering — the group that writes the life-cycle, architecture and quality standards the whole field runs on.
ISO committee page →Formed in 1987 by merging ISO/TC 97 and IEC/TC 83, the subcommittee was renamed from Software Engineering to Software and Systems Engineering in 2000 — the moment “systems” became the point. Its scope: the processes, supporting tools and technologies for engineering software products and systems — spanning enterprise architecture, the engineering environment, the bodies of knowledge, and IT asset management.
SEBoK is the map; the six standards below are how we put it to work — life cycle, architecture and assessment — adapted to hardware, not paperwork for its own sake. Each links to its current edition.
The discipline's agreed map of what systems engineering knows — the ground the standards below stand on. Maintained by INCOSE, the IEEE Systems Council and Stevens Institute.
The backbone. A common framework for the whole life of a system — concept through retirement.
How an architecture is created, analysed and sustained — stakeholders, concerns, viewpoints, views.
15288's software twin — the life-cycle processes behind the embedded code that runs the machine.
Software's answer to SEBoK — the agreed body of knowledge our embedded and application work draws on.
How you measure whether a process is actually capable — not just documented. The 330xx family that replaced 15504.
15288/12207 right-sized for small teams — proof the standard scales down without becoming theatre.
Each phase is led by the discipline that owns it. The loop — sense, compute, actuate — is the cybernetic spine underneath.
The ones whose output touches what we build: