UML, the Universal Modeling Language, was the first programming language designed to fulfill the requirement for "universality." However, it is a software-specific language, and does not support the needs of engineers designing from the broader systems-based perspective. Therefore, SysML was created. It has been steadily gaining popularity, and many companies, especially in the heavily-regulated Defense, Automotive, Aerospace, Medical Device and Telecomms industries, are already using SysML, or are plannning to switch over to it in the near future. However, little information is currently available on the market regarding SysML. Its use is just on the crest of becoming a widespread phenomenon, and so thousands of software engineers are now beginning to look for training and resources. This book will serve as the one-stop, definitive guide that provide an introduction to SysML, and instruction on how to implement it, for all these new users.
- SysML is the latest emerging programming language--250, 000 estimated software systems engineers are using it in the US alone!
- The first available book on SysML in English
- Insider information! The author is a member of the SysML working group and has written sections of the specification
- Special focus comparing SysML and UML, and explaining how both can work together
Inhaltsverzeichnis
1;Front Cover;1 2;Systems Engineering with Sysml/UML;4 3;Copyright Page;5 4;Contents;6 5;Foreword;10 6;Author Biography;13 7;CHAPTER 1 Introduction;14 7.1;1.1 Preliminaries;14 7.1.1;1.1.1 Is This Book for Me?;16 7.1.2;1.1.2 What Will I Get from This Book?;16 7.1.3;1.1.3 What Motivated This Book? And Thanks!;17 7.1.4;1.1.4 How Do I Read This Book?;18 7.1.5;1.1.5 What Next?;18 7.2;1.2 Systems Engineering;19 7.2.1;1.2.1 What Is Systems Engineering?;20 7.2.2;1.2.2 Systems Engineering Processes;23 7.2.3;1.2.3 The Systems Engineer;25 7.2.4;1.2.4 Systems Engineering History;26 7.2.5;1.2.5 International Council on Systems Engineering;27 7.2.6;1.2.6 Systems Engineering versus Software Engineering;28 7.2.7;1.2.7 Marginal Notes;28 7.3;1.3 The OMG SysML™ and UML™ Languages;29 7.4;1.4 Book Context;30 7.4.1;1.4.1 Autosar;31 7.4.2;1.4.2 Capability Maturity Model Integration;31 7.4.3;1.4.3 BPM;32 7.4.4;1.4.4 ISO/IEC 15288;32 7.4.5;1.4.5 MATLAB/Simulink;33 7.4.6;1.4.6 The Requirement Interchange Format;33 7.4.7;1.4.7 Statemate;34 7.4.8;1.4.8 Step;34 7.4.9;1.4.9 Specification and Description Language;35 7.4.10;1.4.10 V-Model XT;35 8;CHAPTER 2 The Pragmatic SYSMOD Approach;36 8.1;2.1 Case Study;37 8.1.1;2.1.1 Describe Project Context;41 8.2;2.2 Determining Requirements;46 8.2.1;2.2.1 Identify Stakeholders;47 8.2.2;2.2.2 Collect Requirements;51 8.3;2.3 Modeling the System Context;58 8.3.1;2.3.1 Identify System Actors;58 8.3.2;2.3.2 Model System/Actor Information Flow;67 8.3.3;2.3.3 Identify System Interaction Points;72 8.4;2.4 Modeling Use Cases;76 8.4.1;2.4.1 Identify Use Cases;78 8.4.2;2.4.2 Describe Use Case Essences;88 8.4.3;2.4.3 Describe System Processes;93 8.4.4;2.4.4 Model Use Cases Without Redundancies;97 8.4.5;2.4.5 Model Use Case Flows;101 8.4.6;2.4.6 Model Object Flows;107 8.5;2.5 Model Domain Knowledge;115 8.6;2.6 Create Glossary;120 8.7;2.7 Realizing Use Cases;123 8.7.1;2.7.1 Model System/Actor Interaction;125 8.7.2;2.7.2 Derive System Interfaces;127 8.7.3;2.7
.3 Model System Structures;129 8.7.4;2.7.4 Desire State Model;138 8.8;2.8 Marginal Notes;141 8.8.1;2.8.1 Variant Management;142 8.8.2;2.8.2 Model Simulation;143 8.8.3;2.8.3 Testing;144 8.8.4;2.8.4 The System of Systems;147 8.8.5;2.8.5 Modeling Patterns;148 8.8.6;2.8.6 Model Views;152 9;CHAPTER 3 UMLUnified Modeling Language;156 9.1;3.1 History;157 9.2;3.2 Structure and Concepts;159 9.3;3.3 The Class Diagram;161 9.3.1;3.3.1 Class;162 9.3.2;3.3.2 Attribute;164 9.3.3;3.3.3 Operation;166 9.3.4;3.3.4 Association;167 9.3.5;3.3.5 Aggregation and Composition;168 9.3.6;3.3.6 Dependency;170 9.3.7;3.3.7 Abstraction Dependency;171 9.3.8;3.3.8 Generalization;171 9.3.9;3.3.9 Interface;173 9.3.10;3.3.10 Signal;174 9.3.11;3.3.11 Data Types;175 9.3.12;3.3.12 Association Class;176 9.4;3.4 The Composite Structure Diagram;177 9.4.1;3.4.1 Role;178 9.4.2;3.4.2 Connector;180 9.4.3;3.4.3 Port;180 9.5;3.5 The Use Case Diagram;181 9.5.1;3.5.1 Use Case;181 9.5.2;3.5.2 Actor;183 9.5.3;3.5.3 Include Relationship;186 9.6;3.6 The Activity Diagram;186 9.6.1;3.6.1 Activity;187 9.6.2;3.6.2 Action and PIN;190 9.6.3;3.6.3 Parameter Set;192 9.6.4;3.6.4 Activity Edge;195 9.6.5;3.6.5 Initial and Final Nodes;195 9.6.6;3.6.6 Decision and Merge Nodes;198 9.6.7;3.6.7 Fork and Join Nodes;199 9.6.8;3.6.8 Interruptible Activity Region;202 9.6.9;3.6.9 Expansion Region;203 9.6.10;3.6.10 Activity Partition;204 9.7;3.7 The State Machine Diagram;205 9.7.1;3.7.1 State Machine;205 9.7.2;3.7.2 State;206 9.7.3;3.7.3 Transition;208 9.7.4;3.7.4 Trigger and Event;210 9.7.5;3.7.5 Initial and Final States;211 9.7.6;3.7.6 Pseudostate;212 9.8;3.8 Interaction Diagrams;216 9.8.1;3.8.1 Interaction;217 9.8.2;3.8.2 Lifeline;218 9.8.3;3.8.3 Message;219 9.8.4;3.8.4 Combined Fragment;220 9.8.5;3.8.5 Interaction Use;223 9.8.6;3.8.6 State Invariant;224 9.8.7;3.8.7 Time Constraints;225 9.9;3.9 The Package Diagram;227 9.9.1;3.9.1 Package;227 9.10;3.10 Other Model Elements;227 9.10.1;3.10.1 Diagram Frame;228 9.10.2;3.10.2 The Stereotype Ex
tension Mechanism;229 9.10.3;3.10.3 Information Item and Information Flow;231 9.10.4;3.10.4 Comment;233 9.10.5;3.10.5 Constraint;233 10;CHAPTER 4 SysMLThe Systems Modeling Language;236 10.1;4.1 History;237 10.2;4.2 Structure and Concepts;238 10.3;4.3 The Requirement Diagram;239 10.3.1;4.3.1 Requirement;240 10.3.2;4.3.2 The Derive Requirement Relationship;242 10.3.3;4.3.3 Namespace Containment;243 10.3.4;4.3.4 Satisfy Relationship;244 10.3.5;4.3.5 Copy Relationship;246 10.3.6;4.3.6 Verify Relationship;247 10.3.7;4.3.7 Test Case;248 10.3.8;4.3.8 Refine Relationship;248 10.3.9;4.3.9 Trace Relationship;249 10.3.10;4.3.10 Table Notation;250 10.4;4.4 Allocation;251 10.4.1;4.4.1 Allocation;253 10.4.2;4.4.2 Allocate Activity Partition;254 10.4.3;4.4.3 Table Notation;255 10.5;4.5 Block Diagrams;255 10.5.1;4.5.1 Block;256 10.5.2;4.5.2 Distribution Definition;260 10.5.3;4.5.3 Value Type;260 10.5.4;4.5.4 Unit and Dimension;261 10.5.5;4.5.5 Flow Port;263 10.5.6;4.5.6 Item Flow;265 10.5.7;4.5.7 Association Block;265 10.5.8;4.5.8 Data Types;266 10.6;4.6 The Parametric Diagram;267 10.6.1;4.6.1 Constraint Block;267 10.7;4.7 The Use Case Diagram;269 10.8;4.8 The Activity Diagram;270 10.8.1;4.8.1 Activity Composition (Function Tree);271 10.8.2;4.8.2 Control Operator;271 10.8.3;4.8.3 Rate;274 10.8.4;4.8.4 Special Object Node Properties;274 10.8.5;4.8.5 Probability;277 10.9;4.9 The State Machine Diagram;277 10.10;4.10 Interaction Diagrams;278 10.11;4.11 General Modeling Elements;278 10.11.1;4.11.1 Rationale;279 10.11.2;4.11.2 Diagram Frame;279 10.11.3;4.11.3 Model View and Viewpoint;281 10.11.4;4.11.4 Problem;283 11;CHAPTER 5 Systems Engineering ProfileSYSMOD;284 11.1;5.1 Actor Categories;284 11.2;5.2 Discipline-Specific Elements;287 11.3;5.3 Extended Requirement;288 11.4;5.4 Essential Activity;289 11.5;5.5 Domain Block;290 11.6;5.6 Weighted Requirement Relationships;291 11.7;5.7 Continuous and Secondary Use Cases;292 11.8;5.8 Stakeholders;294 11.9;5.9 Systems and Subsystems;295 11.10;5
.10 System Context Elements;296 11.11;5.11 System Processes;296 12;Glossary;298 12.1;A;298 12.2;B;299 12.3;C;299 12.4;D;300 12.5;E;300 12.6;F;301 12.7;G;301 12.8;H;301 12.9;I;301 12.10;J;302 12.11;L;302 12.12;M;302 12.13;N;302 12.14;O;303 12.15;P;303 12.16;R;304 12.17;S;304 12.18;T;305 12.19;U;306 12.20;V;306 12.21;W;306 12.22;X;306 13;References;308 14;Index;312 14.1;A;312 14.2;B;313 14.3;C;313 14.4;D;314 14.5;E;314 14.6;F;315 14.7;G;315 14.8;H;315 14.9;I;315 14.10;J;316 14.11;K;316 14.12;L;316 14.13;M;316 14.14;N;316 14.15;O;316 14.16;P;317 14.17;R;317 14.18;S;318 14.19;T;319 14.20;U;320 14.21;V;320 14.22;W;320 14.23;X;320 14.24;Z;320