|
|
|
|
|
|
 |
|
|
Systems Engineering and Architecting: Creating Formal Requirements
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Motivation, Objective, Definitions and Approach | Model Systems and Architecture Behavior | Make Decisions | Establish Natural Language Requirements | Improve an Organization’s Ability to Do 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.
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.
|
|
|
|
|
|
|
|
|
|
|
|
Engineering, Architecting, Executable
|
|
|
|
|
|
|
|
|
|
|
|
|
| | | | | |
|
For the newest resources, visit Wolfram Repositories and Archives »
;PopUp.focus())
