Muutke küpsiste eelistusi

Practical Guide to SysML: The Systems Modeling Language 3rd edition [Pehme köide]

3.97/5 (70 hinnangut Goodreads-ist)
(MBSE Consultant), (Independent Consultant, San Diego, California), (Architecture Modeling Specialist, The MathWorks, Ltd.)
  • Formaat: Paperback / softback, 630 pages, kõrgus x laius: 235x191 mm, kaal: 930 g
  • Sari: The MK/OMG Press
  • Ilmumisaeg: 24-Oct-2014
  • Kirjastus: Morgan Kaufmann Publishers In
  • ISBN-10: 0128002026
  • ISBN-13: 9780128002025
Teised raamatud teemal:
Practical Guide to SysML: The Systems Modeling Language 3rd editionSuurem pilt
  • Formaat: Paperback / softback, 630 pages, kõrgus x laius: 235x191 mm, kaal: 930 g
  • Sari: The MK/OMG Press
  • Ilmumisaeg: 24-Oct-2014
  • Kirjastus: Morgan Kaufmann Publishers In
  • ISBN-10: 0128002026
  • ISBN-13: 9780128002025
Teised raamatud teemal:
Püsilink: https://www.kriso.ee/db/9780128002025.html
Märksõnad:

A Practical Guide to SysML, Third Edition, fully updated for SysML version 1.4, provides a comprehensive and practical guide for modeling systems with SysML. With their unique perspective as leading contributors to the language, Friedenthal, Moore, and Steiner provide a full description of the language along with a quick reference guide and practical examples to help you use SysML.

The book begins with guidance on the most commonly used features to help you get started quickly. Part 1 explains the benefits of a model-based approach, providing an overview of the language and how to apply SysML to model systems. Part 2 includes a comprehensive description of SysML that provides a detailed understanding that can serve as a foundation for modeling with SysML, and as a reference for practitioners. Part 3 includes methods for applying model-based systems engineering using SysML to specify and design systems, and how these methods can help manage complexity. Part 4 deals with topics related to transitioning MBSE practice into your organization, including integration of the system model with other engineering models, and strategies for adoption of MBSE.

  • Learn how and why to deploy MBSE in your organization with an introduction to systems and model-based systems engineering
  • Use SysML to describe systems with this general overview and a detailed description of the Systems Modeling Language
  • Review practical examples of MBSE methodologies to understand their application to specifying and designing a system
  • Includes comprehensive modeling notation tables as an appendix that can be used as a standalone reference

Arvustused

"The primary goal of this book is to introduce model-based engineering through SysML, a graphical systems modeling language that is being promoted as an alternative to the unified modeling language (UML) to address systems engineering." --Computing Reviews

Muu info

The best-selling guide to SysML, fully updated for version 1.4
Preface xvii
Acknowledgements xxi
About the Authors xxiii
Part I Introduction
Chapter 1 Systems Engineering Overview
3(12)
1.1 Motivation for Systems Engineering
3(1)
1.2 The Systems Engineering Process
4(1)
1.3 Typical Application of the Systems Engineering Process
5(5)
1.4 Multidisciplinary Systems Engineering Team
10(1)
1.5 Codifying Systems Engineering Practice through Standards
11(3)
1.6 Summary
14(1)
1.7 Questions
14(1)
Chapter 2 Model-Based Systems Engineering
15(16)
2.1 Contrasting the Document-Based and Model-Based Approach
15(6)
2.1.1 Document-Based Systems Engineering Approach
15(1)
2.1.2 Model-Based Systems Engineering Approach
16(5)
2.2 Modeling Principles
21(7)
2.2.1 Model and MBSE Method Definition
21(1)
2.2.2 The Purpose for Modeling a System
22(1)
2.2.3 Model Validation
22(1)
2.2.4 Establishing Model Quality Criteria
23(3)
2.2.5 Model-Based Metrics
26(2)
2.2.6 Other Model-Based Metrics
28(1)
2.3 Summary
28(1)
2.4 Questions
29(2)
Chapter 3 Getting Started with SysML
31(22)
3.1 SysML Purpose and Key Features
31(1)
3.2 SysML Diagram Overview
32(1)
3.3 Introducing SysML-Lite
33(14)
3.3.1 SysML-Lite Diagrams and Language Features
33(3)
3.3.2 SysML-Lite Air Compressor Example
36(3)
3.3.3 SysML Modeling Tool Tips
39(8)
3.4 A Simplified MBSE Method
47(2)
3.5 The Learning Curve for SysML and MBSE
49(1)
3.6 Summary
50(1)
3.7 Questions
51(1)
Discussion Topics
51(2)
Chapter 4 An Automobile Example Using the SysML Basic Feature Set
53(34)
4.1 The SysML Basic Feature Set and SysML Certification
53(1)
4.2 Automobile Example Overview
53(2)
4.2.1 Problem Summary
54(1)
4.3 Automobile Model
55(25)
4.3.1 Package Diagram for Organizing the Model
55(2)
4.3.2 Capturing the Automobile Specification in a Requirement Diagram
57(1)
4.3.3 Defining the Vehicle and Its External Environment Using a Block Definition Diagram
58(1)
4.3.4 Use Case Diagram for Operate Vehicle
59(2)
4.3.5 Specifying Drive Vehicle Behavior with a Sequence Diagram
61(1)
4.3.6 Referenced Sequence Diagram to Turn On Vehicle
61(1)
4.3.7 Control Power Activity Diagram
61(3)
4.3.8 State Machine Diagram for Drive Vehicle States
64(1)
4.3.9 Vehicle Context Using an Internal Block Diagram
65(2)
4.3.10 Vehicle Hierarchy Represented on a Block Definition Diagram
67(1)
4.3.11 Activity Diagram for Provide Power
68(1)
4.3.12 Internal Block Diagram for the Power Subsystem
69(3)
4.3.13 Defining the Equations to Analyze Vehicle Performance
72(1)
4.3.14 Analyzing Vehicle Acceleration Using the Parametric Diagram
73(2)
4.3.15 Analysis Results from Analyzing Vehicle Acceleration
75(1)
4.3.16 Defining the Vehicle Controller Actions to Optimize Engine Performance
76(1)
4.3.17 Specifying the Vehicle and Its Components
76(1)
4.3.18 Requirements Traceability
77(2)
4.3.19 View and Viewpoint
79(1)
4.4 Model Interchange
80(1)
4.5 Summary
80(1)
4.6 Questions
80(1)
Discussion Topics
81(6)
Part II Language Description
Chapter 5 Viewing SysML Models with Diagrams
87(14)
5.1 Overview
87(1)
5.2 SysML Diagrams
87(6)
5.2.1 Diagram versus Model
88(1)
5.2.2 SysML Diagram Taxonomy
89(1)
5.2.3 Diagram Frames
90(1)
5.2.4 Diagram Header
90(2)
5.2.5 Diagram Description
92(1)
5.2.6 Diagram Content
92(1)
5.3 Diagram Notations
93(3)
5.3.1 Keywords
93(1)
5.3.2 Node Symbols
93(1)
5.3.3 Path Symbols
93(1)
5.3.4 Icon Symbols
94(1)
5.3.5 Note Symbols
94(1)
5.3.6 Other Symbols
95(1)
5.3.7 Symbol Style Options
96(1)
5.3.8 Diagram Layout
96(1)
5.4 Tabular, Matrix, and Tree Views
96(1)
5.5 General Purpose Model Elements
97(1)
5.5.1 Comment
97(1)
5.5.2 Element Group
97(1)
5.6 View and Viewpoint
98(1)
5.7 Summary
99(1)
5.8 Questions
99(1)
Discussion Topics
100(1)
Chapter 6 Organizing the Model with Packages
101(14)
6.1 Overview
101(1)
6.2 The Package Diagram
102(1)
6.3 Defining Packages Using a Package Diagram
102(2)
6.4 Organizing a Package Hierarchy
104(2)
6.5 Showing Packageable Elements on a Package Diagram
106(1)
6.6 Packages as Namespaces
107(1)
6.7 Importing Model Elements into Packages
108(3)
6.8 Showing Dependencies between Packageable Elements
111(1)
6.9 Summary
112(1)
6.10 Questions
112(1)
Discussion Topic
113(2)
Chapter 7 Modeling Structure with Blocks
115(70)
7.1 Overview
115(2)
7.1.1 Block Definition Diagram
116(1)
7.1.2 Internal Block Diagram
116(1)
7.2 Modeling Blocks on a Block Definition Diagram
117(2)
7.3 Modeling the Structure and Characteristics of Blocks Using Properties
119(19)
7.3.1 Modeling Block Composition Hierarchies Using Parts
119(7)
7.3.2 Modeling Relationships between Blocks Using Reference Properties
126(2)
7.3.3 Using Associations to Type Connectors between Parts
128(5)
7.3.4 Modeling Quantifiable Characteristics of Blocks Using Value Properties
133(5)
7.4 Modeling Flows
138(6)
7.4.1 Modeling Items That Flow
139(1)
7.4.2 Flow Properties
139(1)
7.4.3 Modeling Flows between Parts on an Internal Block Diagram
140(4)
7.5 Modeling Block Behavior
144(4)
7.5.1 Modeling the Main Behavior of a Block
145(1)
7.5.2 Specifying the Behavioral Features of Blocks
146(1)
7.5.3 Modeling Block-Defined Methods
147(1)
7.5.4 Routing Requests Across Connectors
148(1)
7.6 Modeling Interfaces Using Ports
148(16)
7.6.1 Full Ports
149(2)
7.6.2 Proxy Ports
151(2)
7.6.3 Connecting Ports
153(8)
7.6.4 Modeling Flows between Ports
161(1)
7.6.5 Using Interfaces with Ports
162(2)
7.7 Modeling Classification Hierarchies Using Generalization
164(12)
7.7.1 Classification and the Structural Features of a Block
165(1)
7.7.2 Classification and Behavioral Features
166(1)
7.7.3 Modeling Overlapping Classifications Using Generalization Sets
167(1)
7.7.4 Modeling Variants Using Classification
168(5)
7.7.5 Using Property-Specific Types to Model Context-Specific Block Characteristics
173(1)
7.7.6 Modeling Block Configurations as Specialized Blocks
173(3)
7.8 Modeling Block Configurations Using Instances
176(1)
7.9 Semantics of Blocks
177(2)
7.9.1 The Foundational UML Subset (fUML)
178(1)
7.10 Deprecated Features
179(1)
7.10.1 Flow Ports
180(1)
7.11 Summary
180(2)
7.12 Questions
182(1)
Discussion Topics
183(2)
Chapter 8 Modeling Constraints with Parametrics
185(20)
8.1 Overview
185(2)
8.1.1 Defining Constraints Using the Block Definition Diagram
185(1)
8.1.2 The Parametric Diagram
186(1)
8.2 Using Constraint Expressions to Represent System Constraints
187(1)
8.3 Encapsulating Constraints in Constraint Blocks to Enable Reuse
187(3)
8.3.1 Additional Parameter Characteristics
188(2)
8.4 Using Composition to Build Complex Constraint Blocks
190(1)
8.5 Using a Parametric Diagram to Bind Parameters of Constraint Blocks
191(2)
8.6 Constraining Value Properties of a Block
193(1)
8.7 Capturing Values in Block Configurations
194(1)
8.8 Constraining Time-Dependent Properties to Facilitate Time-Based Analysis
195(1)
8.9 Using Constraint Blocks to Constrain Item Flows
196(1)
8.10 Describing an Analysis Context
197(2)
8.11 Modeling Evaluation of Alternatives and Trade Studies
199(2)
8.12 Summary
201(2)
8.13 Questions
203(1)
Discussion Topics
203(2)
Chapter 9 Modeling Flow-Based Behavior with Activities
205(42)
9.1 Overview
205(1)
9.2 The Activity Diagram
206(2)
9.3 Actions-The Foundation of Activities
208(1)
9.4 The Basics of Modeling Activities
209(3)
9.4.1 Specifying Input and Output Parameters for an Activity
209(2)
9.4.2 Composing Activities Using Call Behavior Actions
211(1)
9.5 Using Object Flows to Describe the Flow of Items between Actions
212(6)
9.5.1 Routing Object Flows
213(2)
9.5.2 Routing Object Flows from Parameter Sets
215(1)
9.5.3 Buffers and Data Stores
216(2)
9.6 Using Control Flows to Specify the Order of Action Execution
218(3)
9.6.1 Depicting Control Logic with Control Nodes
218(2)
9.6.2 Using Control Operators to Enable and Disable Actions
220(1)
9.7 Handling Signals and Other Events
221(1)
9.8 Structuring Activities
222(3)
9.8.1 Interruptible Regions
223(1)
9.8.2 Using Structured Activity Nodes
224(1)
9.9 Advanced Flow Modeling
225(3)
9.9.1 Modeling Flow Rates
225(1)
9.9.2 Modeling Flow Order
226(1)
9.9.3 Modeling Probabilistic Flow
227(1)
9.10 Modeling Constraints on Activity Execution
228(2)
9.10.1 Modeling Pre- and Post-conditions and Input and Output States
228(1)
9.10.2 Adding Timing Constraints to Actions
229(1)
9.11 Relating Activities to Blocks and Other Behaviors
230(6)
9.11.1 Linking Behavior to Structure Using Partitions
230(2)
9.11.2 Specifying an Activity in a Block Context
232(3)
9.11.3 Relationship between Activities and Other Behaviors
235(1)
9.12 Modeling Activity Hierarchies Using Block Definition Diagrams
236(2)
9.12.1 Modeling Activity Invocation Using Composite Associations
236(1)
9.12.2 Modeling Parameter and Other Object Nodes Using Associations
237(1)
9.12.3 Adding Parametric Constraints to Activities
238(1)
9.13 Enhanced Functional Flow Block Diagram
238(1)
9.14 Executing Activities
239(4)
9.14.1 The Foundational UML Subset (fUML)
240(1)
9.14.2 The Action Language for Foundational UML (Alf)
240(1)
9.14.3 Primitive Actions
240(2)
9.14.4 Executing Continuous Activities
242(1)
9.15 Summary
243(1)
9.16 Questions
244(1)
Discussion Topic
245(2)
Chapter 10 Modeling Message-Based Behavior with Interactions
247(26)
10.1 Overview
247(1)
10.2 The Sequence Diagram
248(1)
10.3 The Context for Interactions
248(2)
10.4 Using Lifelines to Represent Participants in an Interaction
250(1)
10.4.1 Occurrence Specifications
251(1)
10.5 Exchanging Messages between Lifelines
251(7)
10.5.1 Synchronous and Asynchronous Messages
252(1)
10.5.2 Lost and Found Messages
253(1)
10.5.3 Weak Sequencing
254(1)
10.5.4 Executions
255(1)
10.5.5 Lifeline Creation and Destruction
256(2)
10.6 Representing Time on a Sequence Diagram
258(2)
10.7 Describing Complex Scenarios Using Combined Fragments
260(5)
10.7.1 Basic Interaction Operators
260(3)
10.7.2 Additional Interaction Operators
263(1)
10.7.3 State Invariants
264(1)
10.8 Using Interaction References to Structure Complex Interactions
265(2)
10.9 Decomposing Lifelines to Represent Internal Behavior
267(2)
10.10 Summary
269
10.11 Questions
27(244)
Discussion Topic
271(2)
Chapter 11 Modeling Event-Based Behavior with State Machines
273(22)
11.1 Overview
273(1)
11.2 State Machine Diagram
274(1)
11.3 Specifying States in a State Machine
275(2)
11.3.1 Region
275(1)
11.3.2 State
276(1)
11.4 Transitioning between States
277(5)
11.4.1 Transition Fundamentals
277(2)
11.4.2 Routing Transitions Using Pseudostates
279(3)
11.4.3 Showing Transitions Graphically
282(1)
11.5 State Machines and Operation Calls
282(1)
11.6 State Hierarchies
283(8)
11.6.1 Composite State with a Single Region
283(2)
11.6.2 Composite State with Multiple (Orthogonal) Regions
285(2)
11.6.3 Transition Firing Order in Nested State Hierarchies
287(1)
11.6.4 Using the History Pseudostate upon Return to a Previously Interrupted Region
288(1)
11.6.5 Reusing State Machines
289(2)
11.7 Contrasting Discrete and Continuous States
291(1)
11.8 Summary
292(1)
11.9 Questions
293(1)
Discussion Topic
294(1)
Chapter 12 Modeling Functionality with Use Cases
295(14)
12.1 Overview
295(1)
12.2 Use Case Diagram
295(1)
12.3 Using Actors to Represent the Users of a System
296(1)
12.3.1 Further Descriptions of Actors
297(1)
12.4 Using Use Cases to Describe System Functionality
297(4)
12.4.1 Use Case Relationships
298(3)
12.4.2 Use Case Descriptions
301(1)
12.5 Elaborating Use Cases with Behaviors
301(5)
12.5.1 Context Diagrams
302(1)
12.5.2 Sequence Diagrams
302(1)
12.5.3 Activity Diagrams
303(1)
12.5.4 State Machine Diagrams
304(2)
12.6 Summary
306(1)
12.7 Questions
306(1)
Discussion Topics
307(2)
Chapter 13 Modeling Text-Based Requirements and Their Relationship to Design
309(22)
13.1 Overview
309(1)
13.2 Requirement Diagram
310(2)
13.3 Representing a Text Requirement in the Model
312(2)
13.4 Types of Requirements Relationships
314(1)
13.5 Representing Cross-Cutting Relationships in SysML Diagrams
315(2)
13.5.1 Depicting Requirements Relationships Directly
315(1)
13.5.2 Depicting Requirements Relationships Using Compartment Notation
316(1)
13.5.3 Depicting Requirements Relationships Using Callout Notation
316(1)
13.6 Depicting Rationale for Requirements Relationships
317(1)
13.7 Depicting Requirements and Their Relationships in Tables
317(2)
13.7.1 Depicting Requirement Relationships in Tables
318(1)
13.7.2 Depicting Requirement Relationships as Matrices
318(1)
13.8 Modeling Requirement Hierarchies in Packages
319(1)
13.9 Modeling a Requirement Containment Hierarchy
320(2)
13.9.1 The Browser View of a Containment Hierarchy
320(2)
13.10 Modeling Requirement Derivation
322(1)
13.11 Asserting that a Requirement is Satisfied
323(1)
13.12 Verifying that a Requirement is Satisfied
324(1)
13.13 Reducing Requirements Ambiguity Using the Refine Relationship
325(2)
13.14 Using the General-Purpose Trace Relationship
327(1)
13.15 Reusing Requirements with the Copy Relationship
328(1)
13.16 Summary
329(1)
13.17 Questions
329(1)
Discussion Topics
330(1)
Chapter 14 Modeling Cross-Cutting Relationships with Allocations
331(26)
14.1 Overview
331(1)
14.2 Allocate Relationship
332(1)
14.3 Allocation Notation
333(2)
14.4 Kinds of Allocation
335(2)
14.4.1 Allocation of Requirements
335(1)
14.4.2 Allocation of Behavior or Function
335(1)
14.4.3 Allocation of Flow
335(1)
14.4.4 Allocation of Structure
336(1)
14.4.5 Allocation of Properties
336(1)
14.4.6 Summary of Relationships Associated with the Term "Allocation"
336(1)
14.5 Planning for Reuse: Specifying Definition and Usage in Allocation
337(3)
14.5.1 Allocating Usage
337(1)
14.5.2 Allocating Definition
338(1)
14.5.3 Allocating Asymmetrically
339(1)
14.5.4 Guidelines for Allocating Definition and Usage
339(1)
14.6 Allocating Behavior to Structure Using Functional Allocation
340(5)
14.6.1 Modeling Functional Allocation of Usage
341(1)
14.6.2 Modeling Functional Allocation of Definition
341(3)
14.6.3 Modeling Functional Allocation Using Allocate Activity Partitions (Allocate Swim Lanes)
344(1)
14.7 Allocating Behavioral Flows to Structural Flows
345(3)
14.7.1 Options for Allocating Flow
345(1)
14.7.2 Allocating an Object Flow to a Connector
345(1)
14.7.3 Allocating Object Flow to Item Flow
345(3)
14.8 Allocating between Independent Structural Hierarchies
348(3)
14.8.1 Modeling Structural Allocation of Usage
348(1)
14.8.2 Allocating a Logical Connector to a Physical Structure
349(1)
14.8.3 Modeling Structural Allocation of Definition
350(1)
14.9 Modeling Structural Flow Allocation
351(1)
14.10 Allocating Deeply Nested Properties
352(1)
14.11 Evaluating Allocation across a User Model
353(1)
14.11.1 Establishing Balance and Consistency
353(1)
14.12 Taking Allocation to the Next Step
353(1)
14.13 Summary
354(1)
14.14 Questions
354(1)
Discussion Topics
355(2)
Chapter 15 Customizing SysML for Specific Domains
357(30)
15.1 Overview
357(2)
15.2 The SysML Specification and Language Architecture
359(4)
15.2.1 Modeling Language Design
359(3)
15.2.2 SysML Language Specification and Architecture
362(1)
15.3 Defining Model Libraries to Provide Reusable Constructs
363(2)
15.4 Defining Stereotypes to Extend SysML Concepts
365(4)
15.4.1 Adding Properties and Constraints to Stereotypes
367(2)
15.5 Extending the SysML Language Using Profiles
369(1)
15.5.1 Referencing a Metamodel or Metaclass from a Profile
370(1)
15.6 Applying Profiles to User Models in Order to Use Stereotypes
370(2)
15.7 Applying Stereotypes when Building a Model
372(6)
15.7.1 Specializing Model Elements with Applied Stereotypes
376(2)
15.8 Defining and Using Viewpoints to Generate Views of the Model
378(3)
15.9 Summary
381(2)
15.10 Questions
383(1)
Discussion Topics
384(3)
Part III Examples Of Model-Based Systems Engineering Methods
Chapter 16 Water Distiller Example Using Functional Analysis
387(30)
16.1 Stating the Problem-The Need for Clean Drinking Water
387(1)
16.2 Defining the Model-Based Systems Engineering Approach
388(1)
16.3 Organizing the Model
388(1)
16.4 Establishing Requirements
389(11)
16.4.1 Characterizing Stakeholder Needs
390(3)
16.4.2 Characterizing System Requirements
393(1)
16.4.3 Characterizing Required Behaviors
394(5)
16.4.4 Refining Behavior
399(1)
16.5 Modeling Structure
400(6)
16.5.1 Defining the Distiller's Blocks in the Block Definition Diagram
400(2)
16.5.2 Allocating Behavior
402(1)
16.5.3 Defining the Ports on the Blocks
403(1)
16.5.4 Creating the Internal Block Diagram with Parts, Ports, Connectors, and Item Flows
404(1)
16.5.5 Allocation of Flow
405(1)
16.6 Analyze Performance
406(2)
16.6.1 Item Flow Heat Balance Analysis
406(1)
16.6.2 Resolving Heat Balance
407(1)
16.7 Modify the Original Design
408(7)
16.7.1 Updating Behavior
408(1)
16.7.2 Updating Allocation and Structure
409(1)
16.7.3 Controlling the Distiller and the User Interaction
410(2)
16.7.4 Developing a User Interface and a Controller
412(2)
16.7.5 Startup and Shutdown Considerations
414(1)
16.8 Summary
415(1)
16.9 Questions
415(2)
Chapter 17 Residential Security System Example Using the Object-Oriented Systems Engineering Method
417(90)
17.1 Method Overview
417(7)
17.1.1 Motivation and Background
417(1)
17.1.2 System Development Process Overview
418(4)
17.1.3 OOSEM System Specification and Design Process
422(2)
17.2 Residential Security Example Overview
424(1)
17.2.1 Problem Background
424(1)
17.2.2 Project Startup
424(1)
17.3 Applying OOSEM to Specify and Design the Residential Security System
425(78)
17.3.1 Setup Model
425(6)
17.3.2 Analyze Stakeholder Needs
431(10)
17.3.3 Analyze System Requirements
441(13)
17.3.4 Define Logical Architecture
454(6)
17.3.5 Synthesize Candidate Physical Architectures
460(28)
17.3.6 Optimize and Evaluate Alternatives
488(5)
17.3.7 Manage Requirements Traceability
493(6)
17.3.8 OOSEM Support to Integrate and Verify System
499(1)
17.3.9 Develop Enabling Systems
500(3)
17.4 Summary
503(1)
17.5 Questions
503(4)
Part IV Transitioning To Model-Based Systems Engineering
Chapter 18 Integrating SysML into a Systems Development Environment
507(36)
18.1 The System Model in the Broader Development Context
507(8)
18.1.1 The System Model as an Integrating Framework
507(1)
18.1.2 Kinds of Models in the Systems Development Environment
508(3)
18.1.3 Relating Data from Different Models
511(4)
18.2 Specifying an Integrated Systems Development Environment
515(11)
18.2.1 Tools in a Systems Development Environment
515(3)
18.2.2 Interfaces between the System Modeling Tool and Other Tools
518(4)
18.2.3 Using Configuration Management Tools to Manage Model Versions
522(4)
18.3 Data Exchange Mechanisms
526(6)
18.3.1 Considerations for Data Exchange
526(2)
18.3.2 File-Based Exchange
528(3)
18.3.3 API-Based Exchange
531(1)
18.3.4 Performing Transformations
531(1)
18.4 Data Exchange Examples based on Current and Emerging Standards
532(7)
18.4.1 Performing Transformations between SysML and Modelica Models
532(2)
18.4.2 Using OSLC and Linked Data to Support Data Exchange and Tool Integration
534(3)
18.4.3 Exchanging Data to Enable Co-Simulation
537(1)
18.4.4 Interchanging SysML Models and Ontologies
537(1)
18.4.5 Document and View Generation from Models
538(1)
18.5 Selecting a System Modeling Tool
539(1)
18.5.1 Tool Selection Criteria
539(1)
18.5.2 SysML Conformance
540(1)
18.6 Summary
540(1)
18.7 Questions
541(1)
Discussion Topics
541(2)
Chapter 19 Deploying SysML in an Organization
543(12)
19.1 Improvement Process
543(5)
19.1.1 Monitor and Assess
543(2)
19.1.2 Plan the Improvement
545(1)
19.1.3 Define Changes to Process, Methods, Tools, and Training
545(1)
19.1.4 Pilot the Approach
546(1)
19.1.5 Deploy Changes Incrementally
547(1)
19.2 Elements of a Deployment Strategy
548(5)
19.2.1 Organizational Deployment Strategies
549(2)
19.2.2 Project Deployment Strategies
551(2)
19.3 Summary
553(1)
19.4 Questions
554(1)
Discussion Topics
554(1)
Appendix A: SysML Reference Guide 555(30)
Reference 585(4)
Index 589
Sanford Friedenthal is an MBSE Consultant. He has been an advocate for model-based systems engineering and a leader of the industry team that developed SysML from its inception through its adoption by the OMG. Alan Moore is an Architecture Modeling Specialist at The MathWorks. He has extensive experience in the development of real-time and object-oriented methodologies and their application. Alan was co-chair of the OMG's Real-time Analysis and Design Working Group and served as the language architect during the development of SysML. Rick Steiner is an independent consultant focusing on pragmatic application of systems engineering modeling techniques. He culminated his 29 year career at Raytheon as an Engineering Fellow, Raytheon Certified Architect and INCOSE Expert Systems Engineering Professional (ESEP).Mr. Steiner has been an advocate, consultant, and instructor of model driven systems development for over 20 years. He has served as chief engineer, architect, or lead system modeler for several large scale electronics programs, incorporating the practical application of the OOSEM methodology and generation of Department of Defense Architecture Framework (DoDAF) artifacts from complex system models.Mr. Steiner has been a key contributor to both the original requirements for SysML and the development of SysML specification. While his main technical contribution has been in the area of allocations, requirements, and the sample problem, Mr. Steiner has also served as co-chair of the SysML Revision Task Force (RTF). He continues to provide frequent tutorials and workshops on SysML and model driven engineering topics at INCOSE events, NDIA conferences, and other corporate engagements.