Systems Engineering and Architecting

Systems Engineering and Architecting: Creating Formal Requirements presents formal requirements to help you accomplish key systems engineering and architecting activities more efficiently. The formal requirements—explicit, executable, verifiable instructions—explain how to model systems behavior, make decisions, establish natural language requirements, and improve your systems engineering and architecting processes.
Each chapter opens with case studies and lessons learned, which supply the real-world context for the formal requirements. Topics covered include how to use fuzzy logic and agents to model uncertainty and how to make decisions when confronted with ambiguity. The book also clarifies the differences between architecting and systems engineering.
Mathematical Tools for Systems Engineering and Architecting
Written in Mathematica®, each formal requirement provides a tool or serves as the algorithm for a more efficient implementation in another form. All of the requirements are available as an open source library for anyone to use, improve upon, or add to. Worked examples, illustrations, and example surveys help you apply the requirements to your own systems. The book also lists heuristics to guide you in those systems engineering or architecting activities that cannot yet be formally stipulated.
Bring More Consistency to Your Systems Development and Management
Acknowledging that much of the practice remains an art, this book brings as much scientific rigor as possible to the tasks performed by systems engineers and architects. Written by a director of engineering who led systems engineering or architecting efforts for the Space Shuttle Program, Space Control Architecture Development, and others, this book shows you how to develop more consistent processes for large-scale systems.

Laurence Bellagamba was director of engineering for Rockwell International, Northrop Grumman, and TASC. He has led systems engineering or architecting efforts for the Space Shuttle Program, Shuttle-C, Global Positioning System, Anti-satellite System, Ground Based Missile Defense, Airborne Laser, Space Based Laser, and Space Control Architecture Development. He was awarded the NASA Certificate of Appreciation. He received BSAE, MS, and PhD degrees from the School of Aeronautics and Astronautics at Purdue University.

Motivation, Objective, Definitions and ApproachMotivations and ObjectiveDefinitionsApproachSummaryAppendix: Mathematica in BriefModel Systems and Architecture BehaviorModel Systems and Architectures Using DiagramsModel Systems and Architecture Using MathematicsMathematically Model UncertaintyMonitoring System or Architecture Technical Performance MeasuresModeling HeuristicsMake DecisionsMake Good DecisionsMake Good Decisions by Specific MeansDecision HeuristicsAppendix: Results of Testing Mathematica’s Parameter Optimization RoutinesAppendix: Data for Fuzzy Logic Controller for RocketEstablish Natural Language RequirementsDefine Three Types of Natural Language Requirements: Functional, Performance, and SoughtWrite Good Natural Language RequirementsReduce Ambiguities in the Natural Language Requirement StatementDetermine the Natural Language RequirementsMaintain a Natural Language Requirement DatabaseVerify Requirements are Complied WithMeasure Requirements VolatilityRequirements HeuristicsImprove an Organization’s Ability to Do Systems Engineering and ArchitectingMeasure Systems Engineering or Architecting ProgressImprove Processes UsedImprove Process Product QualityImprove EfficiencyUse Surveys to Determine What Is Most Urgent to Improve at Any Point in a ProgramAppendix: System Engineering Effectiveness SurveyAppendix: Architecting Effectiveness SurveyChapters include references.