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

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubDennis Hansen - Air Force Veteran, Chief Systems Engineer & Author of "Model-Based Systems Engineering and Requirements Definition"Jorge Orellana - Model Based Systems Engineer at IERUS Technologies & CEO & Founder at SCATTERBRAINSCheck out more here:https://gotopia.tech/episodes/445RESOURCESJorgehttps://www.linkedin.com/in/jorge-orellana-0b729129DESCRIPTIONDennis Hansen brings over six decades of systems engineering experience to this GOTO Book Club conversation — from Air Force airborne navigation technician to Chief Systems Engineer at L3Harris on programs including the complete rebuild of the GOES-R ground system for NOAA and NASA. His book argues that the fundamental failure mode in complex system development is the same every time: requirements are defined too loosely, too late, or across multiple model layers simultaneously. He structures the approach using an onion model — a layering framework he was taught by a Motorola engineer in 1961 — where each layer (mission, capabilities, activities, technical requirements, specifications) must be completed before the next is begun. Skipping layers or trying to do two at once invariably produces excess or faulty requirements that surface as expensive failures during system testing, or worse, after deployment.The second half of the conversation focuses on why modeling tools are databases, not drawing programs — a distinction Dennis considers critical. Every element in the model carries its associated requirements and the reasoning behind design decisions, which means that when you return to work after a weekend, you don't lose hours reconstructing your thinking. More importantly, when change requests arrive — and they always do — a maintained model lets you trace the impact backwards through the system and understand exactly what has to be modified, rather than slapping on a fix that creates five new problems. Dennis's closing advice is the thread that runs through the entire book: collaborate at every stage, every discipline working together rather than in silos, and define things properly upfront. Everything else follows from that.RECOMMENDED BOOKSDennis Hansen • Model-Based Systems Engineering and Requirements Definition • https://amzn.to/4e6IiqJKossiakoff, Seymour, Flanigan & Biemer • Systems Engineering Principles and Practice • https://amzn.to/4a7Elj9Dr. Bruce Powel Douglass • Agile Model-Based Systems Engineering Cookbook • https://amzn.to/4wYnj12BlueskyInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!