LEADER 05564nam 2200721 a 450 001 9911006631303321 005 20200520144314.0 010 $a9786611189440 010 $a9781281189448 010 $a1281189448 010 $a9780080558318 010 $a0080558313 035 $a(CKB)1000000000412465 035 $a(EBL)331984 035 $a(OCoLC)437200363 035 $a(SSID)ssj0000078266 035 $a(PQKBManifestationID)11125921 035 $a(PQKBTitleCode)TC0000078266 035 $a(PQKBWorkID)10060609 035 $a(PQKB)10937676 035 $a(MiAaPQ)EBC331984 035 $a(CaSebORM)9780123742742 035 $a(OCoLC)319430621 035 $a(OCoLC)ocm319430621 035 $a(EXLCZ)991000000000412465 100 $a20071113d2007 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aSystems engineering with SysML/UML $emodeling, analysis, design /$fTim Weilkiens 205 $a1st edition 210 $aAmsterdam ;$aBoston $cMorgan Kaufmann OMG Press/Elsevier$dc2007 215 $a1 online resource (320 p.) 225 1 $aThe MK/OMG Press 300 $aDescription based upon print version of record. 311 08$a9780123742742 311 08$a0123742749 320 $aIncludes bibliographical references (p. 295-297) and index. 327 $aFront Cover; Systems Engineering with Sysml/UML; Copyright Page; Contents; Foreword; Author Biography; CHAPTER 1 Introduction; 1.1 Preliminaries; 1.1.1 Is This Book for Me?; 1.1.2 What Will I Get from This Book?; 1.1.3 What Motivated This Book? And Thanks!; 1.1.4 How Do I Read This Book?; 1.1.5 What Next?; 1.2 Systems Engineering; 1.2.1 What Is Systems Engineering?; 1.2.2 Systems Engineering Processes; 1.2.3 The Systems Engineer; 1.2.4 Systems Engineering History; 1.2.5 International Council on Systems Engineering; 1.2.6 Systems Engineering versus Software Engineering; 1.2.7 Marginal Notes 327 $a1.3 The OMG SysMLTM and UMLTM Languages1.4 Book Context; 1.4.1 Autosar; 1.4.2 Capability Maturity Model Integration; 1.4.3 BPM; 1.4.4 ISO/IEC 15288; 1.4.5 MATLAB/Simulink; 1.4.6 The Requirement Interchange Format; 1.4.7 Statemate; 1.4.8 Step; 1.4.9 Specification and Description Language; 1.4.10 V-Model XT; CHAPTER 2 The Pragmatic SYSMOD Approach; 2.1 Case Study; 2.1.1 Describe Project Context; 2.2 Determining Requirements; 2.2.1 Identify Stakeholders; 2.2.2 Collect Requirements; 2.3 Modeling the System Context; 2.3.1 Identify System Actors; 2.3.2 Model System/Actor Information Flow 327 $a2.3.3 Identify System Interaction Points2.4 Modeling Use Cases; 2.4.1 Identify Use Cases; 2.4.2 Describe Use Case Essences; 2.4.3 Describe System Processes; 2.4.4 Model Use Cases Without Redundancies; 2.4.5 Model Use Case Flows; 2.4.6 Model Object Flows; 2.5 Model Domain Knowledge; 2.6 Create Glossary; 2.7 Realizing Use Cases; 2.7.1 Model System/Actor Interaction; 2.7.2 Derive System Interfaces; 2.7.3 Model System Structures; 2.7.4 Desire State Model; 2.8 Marginal Notes; 2.8.1 Variant Management; 2.8.2 Model Simulation; 2.8.3 Testing; 2.8.4 The System of Systems; 2.8.5 Modeling Patterns 327 $a2.8.6 Model ViewsCHAPTER 3 UML-Unified Modeling Language; 3.1 History; 3.2 Structure and Concepts; 3.3 The Class Diagram; 3.3.1 Class; 3.3.2 Attribute; 3.3.3 Operation; 3.3.4 Association; 3.3.5 Aggregation and Composition; 3.3.6 Dependency; 3.3.7 Abstraction Dependency; 3.3.8 Generalization; 3.3.9 Interface; 3.3.10 Signal; 3.3.11 Data Types; 3.3.12 Association Class; 3.4 The Composite Structure Diagram; 3.4.1 Role; 3.4.2 Connector; 3.4.3 Port; 3.5 The Use Case Diagram; 3.5.1 Use Case; 3.5.2 Actor; 3.5.3 Include Relationship; 3.6 The Activity Diagram; 3.6.1 Activity; 3.6.2 Action and PIN 327 $a3.6.3 Parameter Set3.6.4 Activity Edge; 3.6.5 Initial and Final Nodes; 3.6.6 Decision and Merge Nodes; 3.6.7 Fork and Join Nodes; 3.6.8 Interruptible Activity Region; 3.6.9 Expansion Region; 3.6.10 Activity Partition; 3.7 The State Machine Diagram; 3.7.1 State Machine; 3.7.2 State; 3.7.3 Transition; 3.7.4 Trigger and Event; 3.7.5 Initial and Final States; 3.7.6 Pseudostate; 3.8 Interaction Diagrams; 3.8.1 Interaction; 3.8.2 Lifeline; 3.8.3 Message; 3.8.4 Combined Fragment; 3.8.5 Interaction Use; 3.8.6 State Invariant; 3.8.7 Time Constraints; 3.9 The Package Diagram; 3.9.1 Package 327 $a3.10 Other Model Elements 330 $aUML, 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 planning to switch over to it in the near future. However, little information is curr 410 0$aMK/OMG Press 606 $aSystems engineering 606 $aSysML (Computer science) 606 $aUML (Computer science) 615 0$aSystems engineering. 615 0$aSysML (Computer science) 615 0$aUML (Computer science) 676 $a620.001/171 700 $aWeilkiens$b Tim$0892219 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9911006631303321 996 $aSystems engineering with SysML$94388602 997 $aUNINA