Muutke küpsiste eelistusi

E-raamat: Practical Guide to SysML: The Systems Modeling Language

3.97/5 (80 hinnangut Goodreads-ist)
(Architecture Modeling Specialist, The MathWorks, Ltd.), (Independent Consultant, San Diego, California), (MBSE Consultant)
  • Formaat: EPUB+DRM
  • Sari: The MK/OMG Press
  • Ilmumisaeg: 22-Nov-2011
  • Kirjastus: Morgan Kaufmann Publishers In
  • Keel: eng
  • ISBN-13: 9780123852076
Teised raamatud teemal:
  • Formaat - EPUB+DRM
  • Hind: 45,68 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
Practical Guide to SysML: The Systems Modeling LanguageSuurem pilt
  • Formaat: EPUB+DRM
  • Sari: The MK/OMG Press
  • Ilmumisaeg: 22-Nov-2011
  • Kirjastus: Morgan Kaufmann Publishers In
  • Keel: eng
  • ISBN-13: 9780123852076
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

This book is the bestselling, authoritative guide to SysML for systems and software engineers, providing a comprehensive and practical resource for modeling systems with SysML. Fully updated to cover newly released version 1.3, it includes a full description of the modeling language along with a quick reference guide, and shows how an organization or project can transition to model-based systems engineering using SysML, with considerations for processes, methods, tools, and training. Numerous examples help readers understand how SysML can be used in practice, while reference material facilitates studying for the OMG Systems Modeling Professional (OCSMP) Certification Program, designed to test candidates' knowledge of SysML and their ability to use models to represent real-world systems.
  • Authoritative and comprehensive guide to understanding and implementing SysML
  • A quick reference guide, including language descriptions and practical examples
  • Application of model-based methodologies to solve complex system problems
  • Guidance on transitioning to model-based systems engineering using SysML
  • Preparation guide for OMG Certified Systems Modeling Professional (OCSMP)



A general purpose graphical modeling language used to specify, analyze, and design systems that may include hardware, software, and personnel, SysML is now being adopted by companies across a broad range of industries, including aerospace and defense, automotive, and IT system developers. This book is the bestselling, authoritative guide to SysML for systems and software engineers, providing a comprehensive and practical resource for modeling systems with SysML. Fully updated to cover newly released version 1.3, it includes a full description of the modeling language along with a quick reference guide, and shows how an organization or project can transition to model-based systems engineering using SysML, with considerations for processes, methods, tools, and training. Numerous examples to help readers understand how SysML can be used in practice, while reference material facilitates studying for the OMG Systems Modeling Professional (OCSMP) Certification Program, designed to test candidates' knowledge of SysML and their ability to use models to represent real-world systems.

  • Authoritative and comprehensive guide to understanding and implementing SysML
  • A quick reference guide, including language descriptions and practical examples
  • Application of model-based methodologies to solve complex system problems
  • Guidance on transitioning to model-based systems engineering using SysML
  • Preparation guide for OMG Certified Systems Modeling Professional (OCSMP)

Arvustused

"SysML is the new industry-standard language designed specifically to support modern systems engineering. I cannot imagine a better way to learn SysML than to read about it from the masters: Friedenthal, Moore, and Steiner led the design of this important new language and now cap that effort with this comprehensive and highly readable guide for both novices and experts."

-Bran Selic, Malina Software Corporation

"This book is just the ticket you need to get started on the road to adopting standards-based, model-based systems engineering (MBSE) methods. The authors have done an outstanding job in providing detailed coverage of the SysML language and semantics supported through worked examples."

-Jeff Estefan, Principal Engineer, NASA's Jet Propulsion Laboratory

"The authors of this book have been invovlded in SysML development since its inception, and have the understanding necessary to explain it clearly. In particular, the activity diagrams chapter accurately and concisely describes the SysML extensions to UML for functional flow modeling."

-Conrad Bock, OMG Lead for Activity Modeling in SysML

Preface xvii
Acknowledgments 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(4)
1.4 Multidisciplinary Systems Engineering Team
9(1)
1.5 Codifying Systems Engineering Practice through Standards
10(3)
1.6 Summary
13(1)
1.7 Questions
14(1)
Chapter 2 Model-Based Systems Engineering
15(14)
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(6)
2.2.1 Model and MBSE Method Definition
21(1)
2.2.2 The Purpose for Modeling a System
21(1)
2.2.3 Establishing Criteria to Meet the Model Purpose
22(3)
2.2.4 Model-Based Metrics
25(1)
2.2.5 Other Model-Based Metrics
26(1)
2.3 Summary
27(1)
2.4 Questions
27(2)
Chapter 3 Getting Started with SysML
29(22)
3.1 SysML Purpose and Key Features
29(1)
3.2 SysML Diagram Overview
29(2)
3.3 Introducing SysML-Lite
31(13)
3.3.1 SysML-Lite Diagrams and Language Features
31(3)
3.3.2 SysML-Lite Air Compressor Example
34(4)
3.3.3 SysML Modeling Tool Tips
38(6)
3.4 A Simplified MBSE Method
44(3)
3.5 The Learning Curve for SysML and MBSE
47(1)
3.6 Summary
48(1)
3.7 Questions
48(3)
Chapter 4 An Automobile Example Using the SysML Basic Feature Set
51(36)
4.1 SysML Basic Feature Set
51(1)
4.2 Automobile Example Overview
51(1)
4.2.1 Problem Summary
52(1)
4.3 Automobile Model
52(30)
4.3.1 Package Diagram for Organizing the Model
53(2)
4.3.2 Capturing the Automobile Specification in a Requirement Diagram
55(2)
4.3.3 Defining the Vehicle and Its External Environment Using a Block Definition Diagram
57(1)
4.3.4 Use Case Diagram for Operate Vehicle
58(2)
4.3.5 Representing Drive Vehicle Behavior with a Sequence Diagram
60(1)
4.3.6 Referenced Sequence Diagram to Turn On Vehicle
60(2)
4.3.7 Control Power Activity Diagram
62(2)
4.3.8 State Machine Diagram for Drive Vehicle States
64(1)
4.3.9 Vehicle Context Using an Internal Block Diagram
64(3)
4.3.10 Vehicle Hierarchy Represented on a Block Definition Diagram
67(2)
4.3.11 Activity Diagram for Provide Power
69(1)
4.3.12 Internal Block Diagram for the Power Subsystem
69(4)
4.3.13 Defining the Equations to Analyze Vehicle Performance
73(2)
4.3.14 Analyzing Vehicle Acceleration Using the Parametric Diagram
75(1)
4.3.15 Analysis Results from Analyzing Vehicle Acceleration
75(2)
4.3.16 Defining the Vehicle Controller Actions to Optimize Engine Performance
77(1)
4.3.17 Specifying the Vehicle and Its Components
78(1)
4.3.18 Requirements Traceability
79(2)
4.3.19 View and Viewpoint
81(1)
4.4 Model Interchange
82(1)
4.5 Summary
82(1)
4.6 Questions
83(4)
Part II Language Description
Chapter 5 SysML Language Architecture
87(16)
5.1 The OMG SysML Language Specification
87(1)
5.2 The Architecture of the SysML Language
88(5)
5.2.1 The General-Purpose Systems Modeling Domain
89(1)
5.2.2 The Modeling Language (or Metamodel)
90(1)
5.2.3 The System Model (or User Model)
91(1)
5.2.4 Model Interchange
92(1)
5.3 SysML Diagrams
93(7)
5.3.1 Diagram Frames
94(1)
5.3.2 Diagram Header
95(1)
5.3.3 Diagram Description
96(1)
5.3.4 Diagram Content
96(3)
5.3.5 Additional Notations
99(1)
5.4 The Surveillance System Case Study
100(1)
5.4.1 Case Study Overview
100(1)
5.4.2 Modeling Conventions
100(1)
5.5 Organization of Part II
101(1)
5.5.1 OCSMP Certification Coverage and SysML 1.3
101(1)
5.6 Questions
102(1)
Chapter 6 Organizing the Model with Packages
103(16)
6.1 Overview
103(1)
6.2 The Package Diagram
104(1)
6.3 Defining Packages Using a Package Diagram
104(2)
6.4 Organizing a Package Hierarchy
106(1)
6.5 Showing Packageable Elements on a Package Diagram
107(2)
6.6 Packages as Namespaces
109(1)
6.7 Importing Model Elements into Packages
109(3)
6.8 Showing Dependencies between Packageable Elements
112(2)
6.9 Specifying Views and Viewpoints
114(1)
6.10 Summary
115(1)
6.11 Questions
116(3)
Chapter 7 Modeling Structure with Blocks
119(66)
7.1 Overview
119(2)
7.1.1 Block Definition Diagram
120(1)
7.1.2 Internal Block Diagram
121(1)
7.2 Modeling Blocks on a Block Definition Diagram
121(2)
7.3 Modeling the Structure and Characteristics of Blocks Using Properties
123(19)
7.3.1 Modeling Block Composition Hierarchies Using Part Properties
123(7)
7.3.2 Modeling Relationships between Blocks Using Reference Properties
130(2)
7.3.3 Using Associations to Type Connectors between Parts
132(5)
7.3.4 Modeling Quantifiable Characteristics of Blocks Using Value Properties
137(5)
7.4 Modeling Flows
142(5)
7.4.1 Modeling Items That Flow
143(1)
7.4.2 Flow Properties
143(1)
7.4.3 Modeling Flows between Parts on an Internal Block Diagram
144(3)
7.5 Modeling Block Behavior
147(5)
7.5.1 Modeling the Main Behavior of a Block
148(1)
7.5.2 Specifying the Behavioral Features of Blocks
148(2)
7.5.3 Modeling Block-Defined Methods
150(1)
7.5.4 Routing Requests Across Connectors
151(1)
7.6 Modeling Interfaces Using Ports
152(15)
7.6.1 Full Ports
153(1)
7.6.2 Proxy Ports
154(3)
7.6.3 Connecting Ports
157(8)
7.6.4 Modeling Flows between Ports
165(1)
7.6.5 Using Interfaces with Ports
165(2)
7.7 Modeling Classification Hierarchies Using Generalization
167(9)
7.7.1 Classification and the Structural Features of a Block
169(1)
7.7.2 Classification and Behavioral Features
170(1)
7.7.3 Modeling Overlapping Classifications Using Generalization Sets
171(1)
7.7.4 Modeling Variants Using Classification
172(1)
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(2)
7.9 Deprecated Features
178(2)
7.9.1 Flow Ports
179(1)
7.10 Summary
180(2)
7.11 Questions
182(3)
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
188(2)
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(2)
8.7 Capturing Values in Block Configurations
195(1)
8.8 Constraining Time-Dependent Properties to Facilitate Time-Based Analysis
195(2)
8.9 Using Constraint Blocks to Constrain Item Flows
197(1)
8.10 Describing an Analysis Context
198(2)
8.11 Modeling Evaluation of Alternatives and Trade Studies
200(2)
8.12 Summary
202(1)
8.13 Questions
203(2)
Chapter 9 Modeling Flow-Based Behavior with Activities
205(46)
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(4)
9.4.1 Specifying Input and Output Parameters for an Activity
209(2)
9.4.2 Composing Activities Using Call Behavior Actions
211(2)
9.5 Using Object Flows to Describe the Flow of Items between Actions
213(7)
9.5.1 Routing Object Flows
213(3)
9.5.2 Routing Object Flows from Parameter Sets
216(3)
9.5.3 Buffers and Data Stores
219(1)
9.6 Using Control Flows to Specify the Order of Action Execution
220(4)
9.6.1 Depicting Control Logic with Control Nodes
220(2)
9.6.2 Using Control Operators to Enable and Disable Actions
222(2)
9.7 Handling Signals and Other Events
224(1)
9.8 Structuring Activities
225(3)
9.8.1 Interruptible Regions
225(1)
9.8.2 Using Structured Activity Nodes
226(2)
9.9 Advanced Flow Modeling
228(3)
9.9.1 Modeling Flow Rates
228(1)
9.9.2 Modeling Flow Order
229(1)
9.9.3 Modeling Probabilistic Flow
230(1)
9.10 Modeling Constraints on Activity Execution
231(3)
9.10.1 Modeling Pre- and Post-conditions and Input and Output States
231(2)
9.10.2 Adding Timing Constraints to Actions
233(1)
9.11 Relating Activities to Blocks and Other Behaviors
234(6)
9.11.1 Linking Behavior to Structure Using Partitions
234(2)
9.11.2 Specifying an Activity in a Block Context
236(3)
9.11.3 Relationship between Activities and Other Behaviors
239(1)
9.12 Modeling Activity Hierarchies Using Block Definition Diagrams
240(3)
9.12.1 Modeling Activity Invocation Using Composite Associations
240(1)
9.12.2 Modeling Parameter and Other Object Nodes Using Associations
240(2)
9.12.3 Adding Parametric Constraints to Activities
242(1)
9.13 Enhanced Functional Flow Block Diagram
243(1)
9.14 Executing Activities
243(5)
9.14.1 The Foundational UML Subset (fUML)
244(1)
9.14.2 The Action Language for Foundational UML (Alf)
245(1)
9.14.3 Primitive Actions
246(1)
9.14.4 Executing Continuous Activities
247(1)
9.15 Summary
248(1)
9.16 Questions
249(2)
Chapter 10 Modeling Message-Based Behavior with Interactions
251(26)
10.1 Overview
251(1)
10.2 The Sequence Diagram
252(1)
10.3 The Context for Interactions
252(2)
10.4 Using Lifelines to Represent Participants in an Interaction
254(2)
10.4.1 Occurrence Specifications
255(1)
10.5 Exchanging Messages between Lifelines
256(5)
10.5.1 Synchronous and Asynchronous Messages
256(2)
10.5.2 Lost and Found Messages
258(1)
10.5.3 Weak Sequencing
259(1)
10.5.4 Executions
259(2)
10.5.5 Lifeline Creation and Destruction
261(1)
10.6 Representing Time on a Sequence Diagram
261(3)
10.7 Describing Complex Scenarios Using Combined Fragments
264(6)
10.7.1 Basic Interaction Operators
265(1)
10.7.2 Additional Interaction Operators
266(2)
10.7.3 State Invariants
268(2)
10.8 Using Interaction References to Structure Complex Interactions
270(1)
10.9 Decomposing Lifelines to Represent Internal Behavior
270(3)
10.10 Summary
273(1)
10.11 Questions
274(3)
Chapter 11 Modeling Event-Based Behavior with State Machines
277(26)
11.1 Overview
277(1)
11.2 State Machine Diagram
278(1)
11.3 Specifying States in a State Machine
278(3)
11.3.1 Region
278(2)
11.3.2 State
280(1)
11.4 Transitioning between States
281(6)
11.4.1 Transition Fundamentals
281(3)
11.4.2 Routing Transitions Using Pseudostates
284(3)
11.4.3 Showing Transitions Graphically
287(1)
11.5 State Machines and Operation Calls
287(1)
11.6 State Hierarchies
288(9)
11.6.1 Composite State with a Single Region
289(1)
11.6.2 Composite State with Multiple (Orthogonal) Regions
290(2)
11.6.3 Transition Firing Order in Nested State Hierarchies
292(1)
11.6.4 Using the History Pseudostate to Return to a Previously Interrupted State
293(2)
11.6.5 Reusing State Machines
295(2)
11.7 Contrasting Discrete and Continuous States
297(2)
11.8 Summary
299(1)
11.9 Questions
300(3)
Chapter 12 Modeling Functionality with Use Cases
303(14)
12.1 Overview
303(1)
12.2 Use Case Diagram
303(1)
12.3 Using Actors to Represent the Users of a System
304(1)
12.3.1 Further Descriptions of Actors
305(1)
12.4 Using Use Cases to Describe System Functionality
305(5)
12.4.1 Use Case Relationships
307(2)
12.4.2 Use Case Descriptions
309(1)
12.5 Elaborating Use Cases with Behaviors
310(4)
12.5.1 Context Diagrams
310(1)
12.5.2 Sequence Diagrams
310(1)
12.5.3 Activity Diagrams
311(2)
12.5.4 State Machine Diagrams
313(1)
12.6 Summary
314(1)
12.7 Questions
315(2)
Chapter 13 Modeling Text-Based Requirements and Their Relationship to Design
317(26)
13.1 Overview
317(1)
13.2 Requirement Diagram
318(2)
13.3 Representing a Text Requirement in the Model
320(2)
13.4 Types of Requirements Relationships
322(1)
13.5 Representing Cross-Cutting Relationships in SysML Diagrams
322(3)
13.5.1 Depicting Requirements Relationships Directly
323(1)
13.5.2 Depicting Requirements Relationships Using Compartment Notation
324(1)
13.5.3 Depicting Requirements Relationships Using Callout Notation
324(1)
13.6 Depicting Rationale for Requirements Relationships
325(1)
13.7 Depicting Requirements and Their Relationships in Tables
326(2)
13.7.1 Depicting Requirement Relationships in Tables
326(1)
13.7.2 Depicting Requirement Relationships as Matrices
327(1)
13.8 Modeling Requirement Hierarchies in Packages
328(1)
13.9 Modeling a Requirements Containment Hierarchy
328(1)
13.9.1 The Browser View of a Containment Hierarchy
329(1)
13.10 Modeling Requirement Derivation
329(2)
13.11 Asserting That a Requirement is Satisfied
331(1)
13.12 Verifying That a Requirement is Satisfied
332(3)
13.13 Reducing Requirements Ambiguity Using the Refine Relationship
335(3)
13.14 Using the General-Purpose Trace Relationship
338(1)
13.15 Reusing Requirements with the Copy Relationship
338(1)
13.16 Summary
339(1)
13.17 Questions
340(3)
Chapter 14 Modeling Cross-Cutting Relationships with Allocations
343(26)
14.1 Overview
343(1)
14.2 Allocation Relationship
343(2)
14.3 Allocation Notation
345(2)
14.4 Types of Allocation
347(2)
14.4.1 Allocation of Requirements
347(1)
14.4.2 Allocation of Behavior or Function
347(1)
14.4.3 Allocation of Flow
348(1)
14.4.4 Allocation of Structure
348(1)
14.4.5 Allocation of Properties
348(1)
14.4.6 Summary of Relationships Associated with the Term "Allocation"
349(1)
14.5 Planning for Reuse: Specifying Definition and Usage in Allocation
349(3)
14.5.1 Allocating Usage
350(1)
14.5.2 Allocating Definition
351(1)
14.5.3 Allocating Asymmetrically
351(1)
14.5.4 Guidelines for Allocating Definition and Usage
351(1)
14.6 Allocating Behavior to Structure Using Functional Allocation
352(6)
14.6.1 Modeling Functional Allocation of Usage
354(1)
14.6.2 Modeling Functional Allocation of Definition
354(3)
14.6.3 Modeling Functional Allocation Using Allocate Activity Partitions (Allocate Swimlanes)
357(1)
14.7 Connecting Functional Flow with Structural Flow Using Functional Flow Allocation
358(3)
14.7.1 Options for Functionally Allocating Flow
358(1)
14.7.2 Allocating an Object Flow to a Connector
358(1)
14.7.3 Allocating Object Flow to Item Flow
359(2)
14.8 Modeling Allocation between Independent Structural Hierarchies
361(3)
14.8.1 Modeling Structural Allocation of Usage
362(1)
14.8.2 Allocating a Logical Connector to a Physical Structure
362(1)
14.8.3 Modeling Structural Allocation of Definition
363(1)
14.9 Modeling Structural Flow Allocation
364(2)
14.10 Evaluating Allocation across a User Model
366(1)
14.10.1 Establishing Balance and Consistency
366(1)
14.11 Taking Allocation to the Next Step
366(1)
14.12 Summary
367(1)
14.13 Questions
367(2)
Chapter 15 Customizing SysML for Specific Domains
369(24)
15.1 Overview
369(4)
15.1.1 A Brief Review of Metamodeling Concepts
370(3)
15.2 Defining Model Libraries to Provide Reusable Constructs
373(1)
15.3 Defining Stereotypes to Extend Existing SysML Concepts
374(5)
15.3.1 Adding Properties and Constraints to Stereotypes
376(3)
15.4 Extending the SysML Language Using Profiles
379(2)
15.4.1 Referencing a Metamodel or Metaclass from a Profile
380(1)
15.5 Applying Profiles to User Models in Order to Use Stereotypes
381(1)
15.6 Applying Stereotypes when Building a Model
382(6)
15.6.1 Specializing Model Elements with Applied Stereotypes
384(4)
15.7 Summary
388(1)
15.8 Questions
389(4)
Part III Modeling Examples
Chapter 16 Water Distiller Example Using Functional Analysis
393(38)
16.1 Stating the Problem - The Need for Clean Drinking Water
393(1)
16.2 Defining the Model-Based Systems Engineering Approach
394(1)
16.3 Organizing the Model
394(2)
16.4 Establishing Requirements
396(13)
16.4.1 Characterizing Stakeholder Needs
396(3)
16.4.2 Characterizing System Requirements
399(1)
16.4.3 Characterizing Required Behaviors
400(6)
16.4.4 Refining Behavior
406(3)
16.5 Modeling Structure
409(8)
16.5.1 Defining Distiller's Blocks in the Block Definition Diagram
409(3)
16.5.2 Allocating Behavior
412(2)
16.5.3 Defining the Ports on the Blocks
414(1)
16.5.4 Creating the Internal Block Diagram with Parts, Ports, Connectors, and Item Flows
414(3)
16.5.5 Allocation of Flow
417(1)
16.6 Analyze Performance
417(3)
16.6.1 Item Flow Heat Balance Analysis
417(3)
16.6.2 Resolving Heat Balance
420(1)
16.7 Modify the Original Design
420(9)
16.7.1 Updating Behavior
420(1)
16.7.2 Updating Allocation and Structure
421(4)
16.7.3 Controlling the Distiller and the User Interaction
425(1)
16.7.4 Developing a User Interface and a Controller
426(1)
16.7.5 Startup and Shutdown Considerations
427(2)
16.8 Summary
429(1)
16.9 Questions
429(2)
Chapter 17 Residential Security System Example Using the Object-Oriented Systems Engineering Method
431(92)
17.1 Method Overview
431(6)
17.1.1 Motivation and Background
431(1)
17.1.2 System Development Process Overview
432(3)
17.1.3 OOSEM System Specification and Design Process
435(2)
17.2 Residential Security Example Overview
437(1)
17.2.1 Problem Background
437(1)
17.2.2 Project Startup
437(1)
17.3 Applying OOSEM to Specify and Design the Residential Security System
438(80)
17.3.1 Setup Model
439(5)
17.3.2 Analyze Stakeholder Needs
444(9)
17.3.3 Analyze System Requirements
453(12)
17.3.4 Define Logical Architecture
465(7)
17.3.5 Synthesize Candidate Physical Architectures
472(29)
17.3.6 Optimize and Evaluate Alternatives
501(6)
17.3.7 Manage Requirements Traceability
507(6)
17.3.8 OOSEM Support to Integrate and Verify System
513(2)
17.3.9 Develop Enabling Systems
515(3)
17.4 Summary
518(1)
17.5 Questions
519(4)
Part IV Transitioning To Model-Based Systems Engineering
Chapter 18 Integrating SysML into a Systems Development Environment
523(34)
18.1 Understanding the System Model's Role in the Broader Modeling Context
523(7)
18.1.1 The System Model as an Integrating Framework
523(1)
18.1.2 Types of Models and Simulations
523(3)
18.1.3 Using the System Model with Other Models
526(4)
18.2 Tool Roles in a Systems Development Environment
530(5)
18.2.1 Use of Tools to Model and Specify the System
530(1)
18.2.2 Use of Tools to Manage the Design Configuration and Related Data
531(3)
18.2.3 Use of Tools to View and Document the Data
534(1)
18.2.4 Verification and Validation Tools
535(1)
18.2.5 Use of Project Management Tools to Manage the Development Process
535(1)
18.3 An Overview of Information Flow between Tools
535(7)
18.3.1 Interconnecting the System Modeling Tool with Other Tools
535(1)
18.3.2 Interface with Requirements Management Tool
536(2)
18.3.3 Interface with SoS/Business Modeling Tools
538(1)
18.3.4 Interface with Simulation and Analysis Tools
538(1)
18.3.5 Interface with Verification Tools
539(1)
18.3.6 Interface with Development Tools
539(1)
18.3.7 Interface with Documentation & View Generation Tool
540(1)
18.3.8 Interface with Configuration Management Tool
540(2)
18.3.9 Interface with Project Management Tool
542(1)
18.4 Data Exchange Mechanisms
542(6)
18.4.1 Considerations for Data Exchange
542(2)
18.4.2 File-Based Exchange
544(2)
18.4.3 API-based Exchange
546(1)
18.4.4 Performing Transformations
547(1)
18.5 Data Exchange Applications
548(5)
18.5.1 SysML to Modelica (bidirectional transformation)
548(4)
18.5.2 Interchanging SysML Models and Ontologies
552(1)
18.5.3 Document Generation from Models (unidirectional transformation)
552(1)
18.6 Selecting a System Modeling Tool
553(1)
18.6.1 Tool Selection Criteria
553(1)
18.6.2 SysML Compliance
554(1)
18.7 Summary
554(1)
18.8 Questions
555(2)
Chapter 19 Deploying SysML into an Organization
557(8)
19.1 Improvement Process
557(6)
19.1.1 Monitor and Assess
558(1)
19.1.2 Plan the Improvement
559(1)
19.1.3 Define Changes to Process, Methods, Tools, and Training
559(1)
19.1.4 Pilot the Approach
560(1)
19.1.5 Deploy Changes Incrementally
561(2)
19.2 Summary
563(1)
19.3 Questions
563(2)
Appendix A 565(30)
References 595(4)
Index 599
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.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97801238520766e.html
Märksõnad: