Systems engineering with SysML/UML modeling, analysis, design
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. Theref...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Amsterdam ; Boston :
Morgan Kaufmann OMG Press/Elsevier
c2007.
|
| Edición: | 1st edition |
| Colección: | MK/OMG Press
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009627537806719 |
Tabla de Contenidos:
- Front 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
- 1.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
- 2.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
- 2.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
- 3.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
- 3.10 Other Model Elements
