Systems Engineering with SysML/UML: Modeling, Analysis, Design
Regular price
21.500 KD
inc. VAT
Couldn't load pickup availability
Table of contents
- Cover
- Contentsv
- Forewordix
- Author Biographyxii
- CHAPTER 1 Introduction1
- 1.1 Preliminaries1
- 1.1.1 Is This Book for Me?3
- 1.1.2 What Will I Get from This Book?3
- 1.1.3 What Motivated This Book? And Thanks!4
- 1.1.4 How Do I Read This Book?5
- 1.1.5 What Next?5
- 1.2 Systems Engineering6
- 1.2.1 What Is Systems Engineering?7
- 1.2.2 Systems Engineering Processes10
- 1.2.3 The Systems Engineer12
- 1.2.4 Systems Engineering History13
- 1.2.5 International Council on Systems Engineering14
- 1.2.6 Systems Engineering versus Software Engineering15
- 1.2.7 Marginal Notes15
- 1.3 The OMG SysML™ and UML™ Languages16
- 1.4 Book Context17
- 1.4.1 Autosar18
- 1.4.2 Capability Maturity Model Integration18
- 1.4.3 BPM19
- 1.4.4 ISO/IEC 1528819
- 1.4.5 MATLAB/Simulink20
- 1.4.6 The Requirement Interchange Format20
- 1.4.7 Statemate21
- 1.4.8 Step21
- 1.4.9 Specification and Description Language22
- 1.4.10 V-Model XT22
- CHAPTER 2 The Pragmatic SYSMOD Approach23
- 2.1 Case Study24
- 2.1.1 Describe Project Context28
- 2.2 Determining Requirements33
- 2.2.1 Identify Stakeholders34
- 2.2.2 Collect Requirements38
- 2.3 Modeling the System Context45
- 2.3.1 Identify System Actors45
- 2.3.2 Model System/Actor Information Flow54
- 2.3.3 Identify System Interaction Points59
- 2.4 Modeling Use Cases63
- 2.4.1 Identify Use Cases65
- 2.4.2 Describe Use Case Essences75
- 2.4.3 Describe System Processes80
- 2.4.4 Model Use Cases Without Redundancies84
- 2.4.5 Model Use Case Flows88
- 2.4.6 Model Object Flows94
- 2.5 Model Domain Knowledge102
- 2.6 Create Glossary107
- 2.7 Realizing Use Cases110
- 2.7.1 Model System/Actor Interaction112
- 2.7.2 Derive System Interfaces114
- 2.7.3 Model System Structures116
- 2.7.4 Desire State Model125
- 2.8 Marginal Notes128
- 2.8.1 Variant Management129
- 2.8.2 Model Simulation130
- 2.8.3 Testing131
- 2.8.4 The System of Systems134
- 2.8.5 Modeling Patterns135
- 2.8.6 Model Views139
- CHAPTER 3 UML„Unified Modeling Language143
- 3.1 History144
- 3.2 Structure and Concepts146
- 3.3 The Class Diagram148
- 3.3.1 Class149
- 3.3.2 Attribute151
- 3.3.3 Operation153
- 3.3.4 Association154
- 3.3.5 Aggregation and Composition155
- 3.3.6 Dependency157
- 3.3.7 Abstraction Dependency158
- 3.3.8 Generalization158
- 3.3.9 Interface160
- 3.3.10 Signal161
- 3.3.11 Data Types162
- 3.3.12 Association Class163
- 3.4 The Composite Structure Diagram164
- 3.4.1 Role165
- 3.4.2 Connector167
- 3.4.3 Port167
- 3.5 The Use Case Diagram168
- 3.5.1 Use Case168
- 3.5.2 Actor170
- 3.5.3 Include Relationship173
- 3.6 The Activity Diagram173
- 3.6.1 Activity174
- 3.6.2 Action and PIN177
- 3.6.3 Parameter Set179
- 3.6.4 Activity Edge182
- 3.6.5 Initial and Final Nodes182
- 3.6.6 Decision and Merge Nodes185
- 3.6.7 Fork and Join Nodes186
- 3.6.8 Interruptible Activity Region189
- 3.6.9 Expansion Region190
- 3.6.10 Activity Partition191
- 3.7 The State Machine Diagram192
- 3.7.1 State Machine192
- 3.7.2 State193
- 3.7.3 Transition195
- 3.7.4 Trigger and Event197
- 3.7.5 Initial and Final States198
- 3.7.6 Pseudostate199
- 3.8 Interaction Diagrams203
- 3.8.1 Interaction204
- 3.8.2 Lifeline205
- 3.8.3 Message206
- 3.8.4 Combined Fragment207
- 3.8.5 Interaction Use210
- 3.8.6 State Invariant211
- 3.8.7 Time Constraints212
- 3.9 The Package Diagram214
- 3.9.1 Package214
- 3.10 Other Model Elements214
- 3.10.1 Diagram Frame215
- 3.10.2 The Stereotype Extension Mechanism216
- 3.10.3 Information Item and Information Flow218
- 3.10.4 Comment220
- 3.10.5 Constraint220
- CHAPTER 4 SysML„The Systems Modeling Language223
- 4.1 History224
- 4.2 Structure and Concepts225
- 4.3 The Requirement Diagram226
- 4.3.1 Requirement227
- 4.3.2 The Derive Requirement Relationship229
- 4.3.3 Namespace Containment230
- 4.3.4 Satisfy Relationship231
- 4.3.5 Copy Relationship233
- 4.3.6 Verify Relationship234
- 4.3.7 Test Case235
- 4.3.8 Refine Relationship235
- 4.3.9 Trace Relationship236
- 4.3.10 Table Notation237
- 4.4 Allocation238
- 4.4.1 Allocation240
- 4.4.2 Allocate Activity Partition241
- 4.4.3 Table Notation242
- 4.5 Block Diagrams242
- 4.5.1 Block243
- 4.5.2 Distribution Definition247
- 4.5.3 Value Type247
- 4.5.4 Unit and Dimension248
- 4.5.5 Flow Port250
- 4.5.6 Item Flow252
- 4.5.7 Association Block252
- 4.5.8 Data Types253
- 4.6 The Parametric Diagram254
- 4.6.1 Constraint Block254
- 4.7 The Use Case Diagram256
- 4.8 The Activity Diagram257
- 4.8.1 Activity Composition (Function Tree)258
- 4.8.2 Control Operator258
- 4.8.3 Rate261
- 4.8.4 Special Object Node Properties261
- 4.8.5 Probability264
- 4.9 The State Machine Diagram264
- 4.10 Interaction Diagrams265
- 4.11 General Modeling Elements265
- 4.11.1 Rationale266
- 4.11.2 Diagram Frame266
- 4.11.3 Model View and Viewpoint268
- 4.11.4 Problem270
- CHAPTER 5 Systems Engineering Profile„SYSMOD271
- 5.1 Actor Categories271
- 5.2 Discipline-Specific Elements274
- 5.3 Extended Requirement275
- 5.4 Essential Activity276
- 5.5 Domain Block277
- 5.6 Weighted Requirement Relationships278
- 5.7 Continuous and Secondary Use Cases279
- 5.8 Stakeholders281
- 5.9 Systems and Subsystems282
- 5.10 System Context Elements283
- 5.11 System Processes283
- Glossary285
- A285
- B286
- C286
- D287
- E287
- F288
- G288
- H288
- I288
- J289
- L289
- M289
- N289
- O290
- P290
- R291
- S291
- T292
- U293
- V293
- W293
- X293
- References295
- Index299
- A299
- B300
- C300
- D301
- E301
- F302
- G302
- H302
- I302
- J303
- K303
- L303
- M303
- N303
- O303
- P304
- R304
- S305
- T306
- U307
- V307
- W307
- X307
- Z307
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
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