Model-Based Systems Eng. & Requirements Definition • Dennis Hansen & Jorge Orellana • GOTO 2026

2026-05-28 · Source: GOTO Conferences · Field: Technology & Digital — Software Development & Engineering, Robotics & Autonomous Systems, Cybersecurity & Data Privacy · Depth: Intermediate, long

Summary

Dennis Hanson's book, "Model Based System Engineering and Requirements Definition," distills over 60 years of experience, including 40 years as chief system engineer at L3 Harris on projects like the GOES-R ground system. The book presents a structured approach to system definition, guiding readers through a document development flow from mission and capabilities to technical requirements and system specifications, transitioning from SysML to UML viewpoints. It introduces an "onion analogy" for layered system definition, advocating for sequential development to prevent faulty requirements. Hanson details a comprehensive OV-1 high-level system overview using true UML modeling, moving beyond simplistic graphics. The book integrates NIST SP 800-53 compliance early in the design process to mitigate accreditation issues. It emphasizes iterative modeling, viewing modeling tools as databases for tracking system function and requirements, and highlights the importance of collaboration and model sustainment for long-term system integrity.

Key takeaway

For Systems Engineers and Program Managers overseeing complex projects, adopting a structured Model-Based Systems Engineering approach is crucial. You should prioritize defining mission and capabilities upfront, then iteratively develop system layers to prevent faulty requirements and costly rework. Integrate security compliance, like NIST SP 800-53, into your models from the initial design phase to streamline accreditation and ensure long-term system integrity.

Key insights

Model-Based Systems Engineering (MBSE) provides a structured, iterative, and collaborative approach to define complex systems, ensuring consistency and compliance.

Principles

• Define mission and capabilities first.
• Develop system layers sequentially.
• Integrate security compliance early.

Method

The book outlines a document development flow: define mission/capabilities, then activities, leading to Technical Requirements Documents (TRD), system specifications (SysML), and subsystem specifications (UML).

In practice

• Use SysML for system-level views.
• Transition to UML for software design.
• Document requirements within modeling tools.

Topics

• Model-Based Systems Engineering
• Requirements Definition
• SysML
• UML
• NIST SP 800-53
• System Architecture
• Program Management

Best for: AI Architect, Software Engineer, Director of AI/ML

Related on AIssential

• Development of a Structured Approach for Establishing Mission Engineering Requirements — A structured approach defines mission requirements and assesses technology impact without explicit customer input.
• Beyond the cleanup job: Redefining application security for the modern enterprise — Proactive application security requires board-level accountability, cultural integration, and a formalized operating model.
• Introducing the AI Security Maturity Model (AISMM) — The AISMM provides a structured path for enterprises to mature their security programs for AI adoption.
• Key Strategies for Building Effective Machine Learning Systems — Effective ML system development prioritizes iterative refinement, data quality, and appropriate model complexity for robust, real-world performance.
• MCPThreatHive: Automated Threat Intelligence for Model Context Protocol Ecosystems — MCPThreatHive automates threat intelligence for agentic systems using a new taxonomy and AI-driven analysis.
• Model Hacking: Why Your Validated Models Still Surprise You — Model validation must shift from statistical conformance to adversarial "model hacking" to uncover hidden business-critical vulnerabilities.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by GOTO Conferences.