MBSE SysML 读书笔记
2022-02-22 18:15:33 1 举报AI智能生成
登录查看完整内容
SysML Distilled A Brief Guide to the Systems Modeling Language 读书笔记。主要是提取书中内容，转化成框架描述，并将相应标题与图片匹配，便于查阅。
作者其他创作
大纲/内容
a frame
a content area(canves)
diagram kind
Model element type
Model element name
Diagram name
header
General Diagram Concepts
elements of definition
element structural relationships
purpuse
When you perform MBSE activity
conjunction with other SysML diagrams to provide a complementary view
When should you create a BDD
element type
namespace
Part properties
Reference properties
Value properties
Constraint properties
standar ports
nonatomic flow ports
atomic flow ports
flow ports
Ports
structural feature
operation
reciption
behavioral feature
Block
Reference Associations
Composite associations
associations
generalizations
dependencies
RelationShip between Blocks
actor
String
Boolean
Integer
Real
primitive
composed of primitives
structured
enumerated
Value Type
Constraint Blocks
BDD Frame
Block definition diagram (BDD)
displays usages of blocks
convey additional information
purpose
IBDs and BDDs provide complementary views of a block.
A BDD letsyou first define a block and its properties. Then you can use an IBD to display a valid configuration of that block—a specific set of connections among the block’s properties.
When Should You Create an IBD
The only allowable model element type for an IBD is block.
IBD Frame
\u0007BDDs and IBDs: Complementary Views of a Block
IBD has the same meaning as a part property in the parts compartment of a block on a BDD
Part Properties
A reference property on an IBD has the same meaning as a reference property in the references compartment of a block on a BDD
Reference Properties
ChildTopic
Connector
Item Flow
Nested Parts and References
Internal block diagram (IBD)
concisely conveys a set of use cases
suited to serve as a system context diagram
Purpose
A use case diagram is an analysis tool and is generally created early in the system life cycle.
during the development of the system concept of operations (ConOps)
elicitation and specification stage
during the architectural design stage
The use case gathers those different scenarios together.
When Should You Create a Use Case Diagram?
An actor can be a person or an external system that interfaces with your system.
The actors that invoke a use case are called primary actors. The actors that participate in the use case are called secondary actors. A primary actor can also be a secondary actor.
Each use case should represent a primary actor’s goal. Write the use case name—the verb phrase—from the perspective of the actor and not your system.
The use case name does not convey a lot of information. You will create a use case specification for each use case to narrate how your system and its actors collaborate to achieve the use case goal.
What’s a Use Case?
Use Case Specifications
Use Cases
System Boundary
actors
You cannot create a composite association between an actor and a use case.
You cannot create an association (of any kind) between two actors.
You cannot create an association (of any kind) between two use cases.
Associating Actors with Use Cases
A base use case is any use case that is connected to a primary actor via an association relationship.
Base Use Cases
Included Use Cases
Extending Use Cases
The Use Case Diagram Frame
Use case diagram
An activity diagram is a kind of behavior diagram
One of its key advantages is its read ability; activity diagrams can express complex control logic better thansequence diagrams and state machine diagrams.
it often is the first kind of behavior diagram you turn to when you need tocommunicate with stakeholders and capture the expected behaviors of the system and its actors.
to communicate with other members of your team and capture the expected behaviors of the system’s internal parts
When Should You Create an Activity Diagram?
The only allowable model element type for an activity diagram is activity
object tokens
control tokens
Tokek Flow
An action is one kind of node that can exist within an activity
The notation for a basic action is a round-cornered rectangle (colloquially called a round-angle).
opaque expression
A pin is a specialized kind of object node.
Pins
Activity Parameters
NonStreaming
Streaming
Streaming versus Nonstreaming
call behavior actions
send signal actions
accept event actions
relative time
wait time actions
Kinds of Action
The activity that owns the action is currently executing.
A control token arrives on each of the incoming control flows
A sufficient number of object tokens arrive on each of the incoming object flows to satisfy the lower multiplicity of the respective input pin.
Start an action
Actions: The Basics
Activity Diagram Frame
Object Nodes
object flows
control flows
Edge
initial nodes
activity final nodes/flow final nodes
decision nodes
merge nodes
fork nodes
join nodes
Activity Partitions: Allocating Behaviors to Structures
Control Nodes
Activity diagram
presents a dynamic view of the system
sequences of behaviors and event occurrences over time
which structure invokes each behavior
specify the intended interactions between the systemof interest and the actors in its environment
These diagrams are useful early in the architectural design stage to specify the interactions between subsystems.
the end of architectural design to specify the interactions between components in preparation for the handoff to the teams producing detailed designs of components.
sequence diagrams as graphical test case specifications
you can potentially create a sequence diagram at any point in the system life cycle.
When Should You Create a Sequence Diagram?
The only allowable model element type for a sequence diagram is interaction.
slector expression
Message send occurrencesMessage receive occurrencesLifeline creation occurrencesLifeline destruction occurrencesBehavior execution start occurrencesBehavior execution termination occurrences
Leftline
A message represents a communication between a sending lifeline anda receiving lifeline.
Message Occurrences
and create messages
Message Types
Message
Destruction Occurrences
start occurrence
termination occurrence
Execution Specifications
Time Constraints
Duration Constraints
state invariants
Constraints
Opt Operator
Alt Operator
Loop Operator
Par Operator
Combined Fragments
Interaction Uses
The Sequence Diagram Frame
Sequence diagram
A state machine diagram is a kind of behavior diagram
it presents a dynamic view of a system.
how a structure within a system changes state in response to event occurrences over time
When Should You Create a State MachineDiagram?
States
Final States
signal events
call events
relative
absolute
time events
change events
Pseudostates
a trigger
a guard
an effect
external transitions
internal transitions
External Transitions versus Internal Transitions
Transitions
Regions
The State Machine Diagram Frame
State machine diagram
model equations and inequalities as constraint blocks
create parametric diagrams during any stage of the system life cycle.
When Should You Create a Parametric Diagram
The Parametric Diagram Frame
Constraint Properties
Constraint Parameters
Value Properties
Binding Connectors
Parametric diagram
A package diagram is the kind of diagram you create when you needto display the organization of the system model.
Package diagrams can display packages nested within pack-ages to convey the containment hierarchy of the model.
convey information about the structure of the model itself.
When Should You Create a Package Diagram?
The Package Diagram Frame
crosshair notation
nesting notation
qualified name string notation
Notations for Namespace Containment
Dependencies between Packages
Importing Packages
model
model library
profile
view
Specialized Packages
Package diagram
This diagram is particularly valuable when your target audienceneeds to see the traceability from the requirements to the elements inyour system model that are dependent on them.
Establishing requirements traceability
to display those relation-ships at any point during this work.
When Should You Create a Requirement Diagram?
Requirements
Requirements Relationships
Containment Relationships
Trace Relationships
Derive Requirement Relationships
refine Relationships
Satisfy Relationships
Verify Relationships
The Requirements Diagram Frame
Direct Notation
Compartment Notation
Callout Notation
Matrices
Tables
Notations for Requirements Relationships
Requirements diagram
SysML Diagram Overview
allocating requirements to structures
allocating behaviors to structures
allocating logical structures to physical structures
allocating resources to structures
insures consistency in theflow-down of design inputs
revisit those decisions efficientlyand systematically as the life cycle progresses
Behavioral Allocation
Structural Allocation
create a «satisfy» dependency from a block to a require-ment
Requirements Allocation
Uses for Allocation Relationships
Allocation Activity Partitions
Allocations:Cross-Cutting Relationships
SysML
MBSE -SysML Distilled A Brief Guide to the Systems Modeling Language
收藏
0 条评论
回复 删除
下一页
