03Mar

Losing Requirements in the First 10% of Design

Dan Taylor | 03 Mar, 2026 | Return|

Modern warships are software-heavy, system-of-systems machines—built from millions of parts and stitched together across C4ISR, networks, power, combat systems, and hull/mechanical domains. Yet early ship design still leans on processes born in a document-driven era, where requirements live in spreadsheets, specs, slide decks, and tribal knowledge—and when requirements change, the risk isn’t just rework, it’s losing the thread entirely.

A Winter 2025 NEJ technical paper argues that early-stage ship design can modernize by aligning traditional naval architecture workflows with systems engineering—and, ultimately, model-based systems engineering (MBSE). The authors walk through two dominant approaches: the classic point-based “design spiral,” which commits to a baseline early and iterates toward convergence, and set-based design, which explores ranges of solutions and narrows the space as unknowns collapse.

Both approaches can break down under today’s complexity, especially as interfaces multiply and requirements management becomes a full-time fight. The paper proposes a “meet-in-the-middle” method: combine bottom-up ship design expertise with top-down requirements rigor so every function and subsystem remains traceable back to a user need—no requirement left behind.

An MBSE digital model is the end state of that confluence: a connected, authoritative source of truth for requirements traceability, architecture views, analyses, and verification/validation. Instead of chasing inconsistencies across documents, teams define once, reuse across disciplines, assess change impacts quickly, and measure design progress with real metrics—not just document completion.

If you care about delivering capability faster with fewer surprises—and avoiding the kinds of early disconnects that haunt programs later—this paper is worth a close read.

Read the Winter 2025 NEJ issue / get access to the paper

ASNE members receive NEJ access as a core benefit. If you’re working ship defense, combat systems integration, autonomy, power/cooling, or next-gen survivability, this is the kind of analysis NEJ exists to publish.

About the Author

Related

Engineering Duty Officer: The Naval Career Path You've Probably Never Heard Of

Engineering Duty Officer: The Naval Career Path You've Probably Never Heard Of

What is a Navy Engineering Duty Officer? A guide to the EDO community — what these 1440 officers do...

Read More >
Marine Engineering Internships and Shipyard Internships: How to Find Them and Stand Out

Marine Engineering Internships and Shipyard Internships: How to Find Them and Stand Out

A practical guide to marine engineering internships at Navy commands, shipyards, and defense contrac...

Read More >
How to Become a Marine Engineer in the U.S.: Degrees, Credentials, and First Jobs

How to Become a Marine Engineer in the U.S.: Degrees, Credentials, and First Jobs

A step-by-step guide on how to become a marine engineer in the U.S. — degrees, internships, USCG an...

Read More >
CAD/CAM & Digital Engineering Updates

CAD/CAM & Digital Engineering Updates

Artificial intelligence is most useful when it connects design, manufacturing, inspection, and maint...

Read More >
The UK Hybrid Navy Comes into Focus: New Details Reveal a Fundamental Shift in Naval Warfare

The UK Hybrid Navy Comes into Focus: New Details Reveal a Fundamental Shift in Naval Warfare

The United Kingdom’s Hybrid Navy will replace the traditional one-for-one ship replacement model wi...

Read More >
Naval Architect vs. Marine Engineer: Which Career Path Is Right for You?

Naval Architect vs. Marine Engineer: Which Career Path Is Right for You?

Naval architect vs marine engineer: compare coursework, job roles, employers, licensing paths, and s...

Read More >