Home

SysML Plugin User Guide

1. 4 The selected ports will then be displayed on the part symbol Figure 64 i Porti o Portz lt block partib Blocks Figure 64 Example of Ports Displayed iii Edit Compartment Property shortcut menu You can customize element s to be displayed in the various compartments of a part Such compartments include Constraints Tagged Values Default Value Structure etc To customize a compartment of a part 1 Right click a part and select Edit Compartment on the shortcut menu 2 Select a compartment to be customized Figure 65 The Compartment Edit dialog will open Figure 66 ayy ricyh NAL 9N144 Nir n NANIA Fafa Copyright 2006 2011 No Magic Inc On SysML Diagrams m seblock gt roy part property B Specification Enter i Symbolist Properties Alt Enter Go To d Refactor Select in Containment Tree Alt E Related Elements Stereotype I Constraints Show Stereotypes Tagged Values Show Owner Default Value Wrap Words Structure Show Tagged values d properties Show Default value references Show Slot Type parks Suppress Structure Males SysML Internal Properties Compartments d anaa Context Specific values d operations Type d Context Specific Value w Unspecified Figure 65 Property Shortcut Menu to Customize Part Compartments 3 In the Compartment Edit dialog move an element from the All to the Selected box to dis play the element
2. Generate Code Framework Chrl 6 Check Syntax Find Modules Generate Report ParaMagic f i E E g bdd Package Satelltelnstancel Coni satellitesystem cont lns1 satellitesystem ins Frol satellitesystem prot Psy1 satellitesystem psy1 Weight Poon 2000 Power 1000 Weon 400 Winsy 3000 blocks Pins 2700 Para 4e00 Wins 2700 wpro 4500 Validate Add default causalities Browse Create Cx5_heading Create CXI_heading Figure 42 ParaMagic Shortcut Menu Util 8 Right click the Satellitelnstance02 package in the browser and select ParaMagic gt Browse to open the ParaMagic browser Figure 43 Copyright 2006 2011 No Magic Inc SysML Diagrams iN ParaMagic 1M 1 16 0 Satellitelnstance0 2 Symbol C SatelliteSystem E Cont o hu Pron Ll weon Insi e Pns i Wins Prot Fpro Lo Wpro Feyi r Power i Winsy i weight Type SatelliteSystem Control REAL REAL Instruments REAL REAL Propulsion REAL REAL FowerSystem REAL REAL REAL Causality undefined 000 undefined 400 undefined undefined 2 100 2 100 undefined undefined 4 800 4 800 undefined 1 000 undefined 3 000 undefined TPTY Values Collapse All root f SatelliteSystem 4 Update to SvshML Relation Weight Proi Wprot Ins1 Wins Conl Wwicont Psy 1 Wosy poner W o E Local ai m Figure 43 ParaMagic Bro
3. 4 For example if you select the Renumber button the requirements under the package selected in the browser on the left hand side of the dialog will be renumbered using the pre defined Numbering Style Prefix and Separator as shown in Figure 140 e SysML Plugin provides two numbering styles to number requirement IDs i Consecutive previously called normal style and ii Multi Levels previously called nested style i Using the Consecutive numbering style each requirement ID is numbered with a prefix followed by numbers without any separator ii Using the Multi Levels numbering style each requirement ID is numbered with a prefix followed by numbers A separator is used to separate each level of number The level will be increased by the containing level of the requirement e You can use a character or a symbol excluding number as a Separator SysML Diagrams B7 Requirement ID Numbering E E Data Requirements Et ia HSUYModel FQ Explanations Mame o B E HSL Analysis mi Capacity i H E HSUY Behavior 2 C Eco Friendiness E HSU Requirements 3 CA Ergonomics ob Sm Specificatio 4 C Qualification i CE PowerSourceManagement E 2 Performance i EE d 1 Regenerativebraking i C d 2 Range i C d 4 Power i E MaxAcceleration T Lama Max Acceleration B E HSU Structure Recursive Renumber abe ie Figure 140 Renumbering Requirements IDs e Numbering Style Prefix and Separator
4. LLI UniverseContext lt block gt UniverseContext parts u Universe UCU z Lo OOo s lt block UcC u Universe Baan a WE ut 3 t7 UC ut2 zablock u Universe seblock O ssblock gt gt m UC u t1 Thing UC u t2 Thing t1 Thing Uti l UC u ti l UC u t2 l t2 Thing Utz me lt block zazblock ssblock gt gy ssblock gt Ey UC u t1 1 Location UC u t2 1 Location ti Thing t2 Thing x ny y fy parts parts Location T I Location T I lt block gt zablock l Location l Location wales wales x Real 0 x Real 0 y Real 0 y Real 0 z Real 0 z Real 0 Weare Unive ie Conte ag Weare Unie ee Conte ag x mgm x Y 4 Il man I m I 4 Il Figure 233 BDD Value Propagate In the UniverseContext package only the value of x of a Location is reconfigured to 3 in the UniverseCon text context The values of y and z are not set by the selected context Since the value propagation is enabled the next context Universe is considered In the Universe context the value of z is set to 2 However the value of y is still missing therefore the next context Thing is considered In the Thing context the value of y is set to 7 Now all attributes of the Location are set as follows ex 3 ey 7 ez 2 For more information on Value Propagation see http training nomagic com 184 Copyright 2006 2011 No Magic Inc Context Specific Value Com
5. Make Default Figure 228 Symbol s Properties DialogSymbol s Properties Dialog Suppress Context Specific Values ii Using the Part Shortcut Menu To display a compartment using the part shortcut menu e On the shortcut menu clear the Suppress Context Specific Values option under the Context Specific Values group Figure 229 To suppress a compartment using the part shortcut menu e On the shortcut menu select the Suppress Context Specific Values option under the Context Specific Values group Figure 229 Context Specific Value Compartments Specification Enter lt block Universe Symbol s Properties Alk Enter parts t1 Thing UH G0 To i fe Thing Ute Select in Containment Tree Alk B Related Elements b s block ti Thing J Convert To b parts Stereotype b l Location T I A Ne Aubosize Edit Compartment b Show Stereotypes z Real 0 l Show Owner b vaines Unive re O Wrap Words Y m H ae Show Classifier Show Tagged Values b Show Default Value Show Slot Type b Suppress Structure Suppress Conkext Specific Values Context d Figure 229 Shortcut Menu for Suppress Context Specific Values 8 3 4 Selecting the Context of Context Specific Value Compartments The properties values shown in the Context Specific Value Compartment of a part and the compartment label will change according to the selected context For exam
6. The activity has at least one streaming param eter The streaming and nonstreaming stereo types cannot be applied to the same element at the same time The activity has no streaming parameter Must be satisfied by an operation or a behavior Must be satisfied by a port connector item flow and or a constraint property Must be satisfied by a value property Must be satisfied by a block or a part Directly Derived specified from OMG in OMG SysML SysML spec spec T3323 16 3 2 1 16 3 2 1 16 3 2 1 16 3 2 1 16 3 2 1 16 3 2 3 16 3 2 3 16 3 2 5 C 1 2 C 1 2 C 1 2 C 2 2 C 2 2 C 2 2 C 2 2 Feature based Compartments Constraint PropertySpecific 1 Type non active PropertySpecific 2 Type non active PropertySpecific A Type non active PropertySpecific B Type non active Constraint Description Directly Description excerpts have been taken from the OMG specified SysML Specifications 1 2 with permission in OMG SysML spec A classifier to which the PropertySpecific 8 3 2 7 Type stereotype is applied must be refer enced as the type of one and only one property The name of a classifier to which a Proper 8 3 2 7 tySpecificType is applied must be missing The name attribute of the NamedElement metaclass must be empty Classifiers with the PropertySpecificType stereotype are owned by the block which owns the property which has the property specific type
7. is broken If the solu tion suggested by the Active Validation feature in this case Remove all other redundant Copy dependency s is selected the correctness of the model will be satisfied as shown in Fig ure 217 zsreguiement CF _ Requirement 2 S lt COpye gt s lt requirement gt CF Requirement 1 Select in Validation Results Figure 216 Selection of the First Solution ssrequirement gt CE Requirement 2 s lt requirement gt CE Requirement 1 E lt lt copy gt gt s lt requirement CF Requirement 3 Figure 217 Valid Elements Each implemented constraint has its own appropriate solutions The Active Validation feature ensures that SysML modeling is consistent with OMG SysML Specifications 6 1 1 Active Validation Options You can customize the Active Validation feature using the five options in Figure 218 Validation L Pro ject Options E General project options General project options E4 Diagram Info H Symbols properties styles Es Default model properties ged Code Engineering Validation scope Data Exclude elements from read only modules true Mark in tree and diagrams true Ignored validation suites Parameters Synchronizat Minimal severity A warning UML Standar Ignored validation suites Reset to Defaults Figure 218 Project Option Dialog 1 Validation scope default data use this option to limit the scope of elements to be actively validated 2 E
8. Architecture Made s Simpie SYSML PLUGIN version 17 0 1 user guide No Magic Inc 2011 All material contained herein is considered proprietary information owned by No Magic Inc and is not to be shared copied or reproduced by any means All information copyright 2006 2011 by No Magic Inc All Rights Reserved CONTENTS SYSML PLUGIN FOR MAGICDRAW 6 1 Introduction 6 2 Installation 6 3 System Engineer Perspective 6 4 Working with SysML Projects 8 4 1 Creating Blank SysML Project 8 4 2 Creating New SysML Project from Specified Template 9 4 3 Using OMG SysML Style 10 4 4 Using QUDV Model Library 13 4 5 Using Quick Search Dialog 13 5 SySML Diagrams 13 5 1 SysML Block Definition Diagrams BDD 14 5 1 1 SysML BDD Metamodel and Elements 14 9 1 2 SysML BDD Toolbar 17 5 1 3 SysML BDD Specific Features 20 5 1 4 Creating Instances of Blocks with Complex Structure 28 5 1 5 Using SysML BDD Elements 45 5 1 6 Converting Data Types to SysML Value Types 47 5 1 7 SysML Callout Box 50 5 2 SySML Internal Block Diagrams IBD 53 5 2 1 SysML IBD Metamodel and Elements 53 9 2 2 SySML IBD Toolbar 55 5 2 3 SySML IBD Specific Features 56 5 2 4 Displaying Structures of Blocks in Compartments or in IBDs 73 5 2 5 Extract Structure 77 5 2 6 Using SysML IBD Elements 82 5 3 SySML Package Diagrams 88 5 3 1 SySML Package Diagram Metamodel and Elements 89 5 3 2 SySML Package Diagram Toolbar 90 5 3 3 Using SysML Package Diagram Elements 91 5 4 Sys
9. C IFS_EPC E3 IFS_ICE ef 3 IFS_TRSM a ICEData HT Figure 73 Select Interface Dialog Case 2 If the port is not typed the Select Port Type menu will then display Figure 74 if Pro vided is selected and Figure 75 if Required is selected SysML Diagrams Ay Select Port Type Port type must be specified Please select one of the Following options Create dummy port type automatically Select or create port type manually Ay Select Port Type Pork type must be specified Please select one of the Following options Select or create port type manually Figure 75 Select Port Type Menu Required Interface Cancel Figure 74 Select Port Type Menu Provided Interface You can then select e For Provided Interface only Set provided interface as port type The Select Interface dialog Figure 73 will then open In the dialog you can either choose an existing interface or create a new one to be used as the Provided Interface and the type of the port e Create dummy port type automatically The Select Interface dialog Figure 73 will then open In the dialog you can either choose an existing interface or create a new one to be used as the Provided or Required Interface as selected in Figure 72 of the port In addition a dummy classifier realizing for Provided or using for Required the interface will be automatically created and used as the type
10. EF HSUY Structure A Selected objects BPS HSU Interfaces Smf elected objects E ICE Type 4 l E SuperFuel H5UVModel HSU pe HSU internalc HSU internal FE HSU internal Add FE HSU internalic E HSU internalic FE HSU internalic E HSU internalic HSU internalic E HSU internal FE HSU internalic E HSU internal HSU internal SuperFuel H E Accelerator Add All dd Rercursively Remove Figure 35 Changing Slot Value of fuelReturn Property 3r Copyright 2006 2011 No Magic Inc SysML Diagrams bdd Package ICE Type A St Instance of the InternalCambustionEngine lt block HSU internalCombustionEngine InternalCombustionEngine fi HSU internalCombustionEnginefi 1 HSL internalCombustionEngine i Z HSU internalCombustionEngine fi 3 HSL internalCombustionEngine fi 4 fil HSL internalCombustionEngine t1 fiz HSU internalCombustionEngine te fis HSL internalCombustionEngine tis fid HSL internalCombustionEngine t4 fra HSU internalCombustionEngine tra TuelSupply HSL internalCombustionEngine tuelSupply iceEfficiency lt lt block gt ry s lt lt block gt lt lt block gt HSU HSU HSU internalCombustionEng internalCombustionEn internalCom ine fuelReturn Fuel qine ftuelSup Fuel bustionEngi ne fil fuelPressure TuelPressure Fuellnjector pressure Yunit psi pressure unit psi i i fuelDemand dimension Pressure dimension Pres
11. Icon Description Test Case Activity StateMachine Interaction SysML a4 A test case is a method for verifying a requirement SysML Diagrams Icon bdd Model Data ES Requirement relationships MetaModel lt metachss Abstraction lt lt stereclypes gt trace Abstraction A pat Pa a costerectypes lt lt sterectypes lt lt sterectyper gt lt lt stereotype Satisty Verify DerweReqt Copy Abstraction Abstraction Abstraction Sbetraction Figure 133 Requirement Relationship Metamodel Description Trace UML A Trace relationship is a dependency that provides a general purpose relationship between a requirement and any other model elements Satisfy SysML A Satisfy relationship is a dependency between a requirement and a model element that fulfills that requirement As with other dependencies the arrow direction points from the satisfying client model element to the Supplier requirement that is satisfied Verify SysML A Verfiy relationship is a dependency between a requirement and a test case ora model element that can determine whether the system fulfills the requirement As with other dependencies the arrow direction points from the client test case to the Sup plier requirement Derive SysML A Derive relationship is a dependency between two requirements a derived require ment and a source requirement where the derived requirement is generated or
12. O 1 Select parts E E Data E HSU Model fa Explanations 3 Select a diagram 2 E HSUY Analysis E B HS5UY Behavior H fF aes HE 2 Select a package Select a package to hold instance specifications to be o created Ei HSL UseCases a D HSU Views ModelingTips et E Stereotypes a SysML 1 1 Specification texts E Eg ModelingDomain Profile Model Figure 31 Automatic Instantiation Wizard Step 2 Select a package For example to create the package named ICE Type A owned by HSUV Structure you need to e Select the HSUV Structure package in the tree and click the Create button A list of packages will open e Choose a package from the list The package specification dialog will open e Type ICE Type A in the name attribute and click the Close button The ICE Type A package will be available in the tree e Select the package and click the Next button to proceed to Step 3 Figure 32 SysML Diagrams p Automatic instantiation Wizard O 1 Select parts E E Data EP HSU Model 2 Select a package 1 5 Explanations C 3 Select a diagram 2 E HSU Analysis Eis HSU Behavior AE HSU Requirements Select a package to hold B E HSU Structure instance specification s to be created PS HSU Interfaces H E HSU UseCases H E HSU views 3 BL ModelingTips H E Stereotypes 2 SysML 1 1 Specification texts Figure 32 Automatic Instantiation Wizard Step 2 S
13. See Annex C 5 Model Library for Quantities Units Dimensions and Values QUDV in OMG SysML specifica tions 1 2 for more detail 13 3 Creating New Quantity Kind Unit or Value Type in QUDV Library 13 3 1 Creating New Quantity Kind For the quantity kind you can create a new quantity kind by creating an InstanceSpecification whose classifier is one of QuantityKind subtype i e SimpleQuantityKind DerivedQuantityKind and SpecializedQuantityKind You can create a quantity kind using either Browser Shortcut Menu or Diagram Toolbar of BDD Open the quantity kind s specification dialog and then change its slot value s according to the QUDV specification To create for example the celsius TemperatureQK quantity kind in the SI Definitions model library 1 Create a Quantity Kind using either Browser Shortcut Menu or Diagram Toolbar of BDD 2 Since there is another temperature quantity kind thermodynamic TemperatureQkK already defined in the SI Definitions model library the newly created quantity kind can be derived from such quantity kind Thus choose the DerivedQuantityKind to be the base classifier of the newly created quantity kind 3 If not already exist create a new InstanceSpecification thermodynamic Temperature 1QKF having QuantityKindFactor as its base classifier in order to define the quantity kind factor to be used in the newly created quantity kind Open the InstanceSpecification s
14. SysML Diagrams 2 Et New Relation P SysML Matrices i SysML Allocation Matrix GP i Class Diagram SysML Satisfy_Requirement Matrix E E Specification Enter Rj Use Case Diagram SysML Verify_Requirement Matrix HE Use Case Numbering Communication Diagram E z Requirement ID Numbering ta Sequence Diagram ban CaTa State Machine Diagram Select in Structure Tree Protocol State Machine Diagram S E Related Elements E Activity Diagram Figure 262 SysML Matrices Menu in Browser 2 In the shortcut menu select New Diagram gt SysML Matrices and select a SysML Editable Matrix that you want to create on the submenu 3 Type the name of the matrix in the Containment Tree 4 Press Enter to finish 10 3 5 Building Matrices The matrices you have created in Section 10 3 4 Creating SysML Editable Matrices are empty matrices To build a complete matrix you must also provide the row and column scopes of the matrix All valid elements in the selected scope will be used to build the matrix To select the row and column scopes of a matrix 1 Click the button next to the Row Scope in the matrix pane Figure 263 The Scope dialog will open Figure 264 A AlloMatrixi x b E Row Element Type Transition Actor Column Element Type Transition Actor Row Scope Lo Row Added Removed Element Column Added Removed Element HERE Ee w amp Figure 263 Scope Button DNA Anvright APNNB I9N1I7 Nio Magice
15. AggregationKind and is typed by a SysML Value Type Value Properties are displayed in the values compartment bdd Model Data St SysML properties ao metaclass gt Property ol c zsstereotype gt zsstereotype gt DistributedProperty ConstraintProperty Property Property Figure 57 SysML Properties Metamodel Icon Description Constraint Property SysML A Constraint Property is a property that specifies the constraints of other properties in its containing Block Every Constraint Property has composite AggregationKind and is typed by a Constraint Block Constraint Properties are displayed in the constraints compartment SysML Diagrams Icon Description Distributed Property SysML c A Distributed Property is a property of a Block or a Value Type used to apply a proba bility distribution to the values of the property Specific distributions can be defined by applying a subclass of the DistributedProperty stereotype to the property bdd Model Data g Flow Fort ssmetaclass Port scsterectypes gt FlowPort Port Figure 58 Flow Port Metamodel Icon Description Flow Port SysML A Flow Port is a port that specifies the input and output items that can flow between a Block and its environment Flow Ports are interactions points through which data mate rial or energy can enter or leave the owning Block The specification of what can flow is achieved b
16. Figure 97 SysML Diagrams e Select the kind of extracted classifier from the Classifier kind box by clicking the arrow button The classifier kind can be a Class Block or Subtype of Block Figure 97 e Specify the owner of the extracted classifier by selecting a Package Model or Profile in the Classifier owner tree You can also click the Create button to create a new Package Model or Profile or click the Clone button to clone the selected Package Model or Profile Figure 97 e Select the diagram type that will show the internal structure of the extracted classifier from the Diagram Type box by clicking the arrow button The diagram type can be a SysML Internal Block Diagram SysML Parametric Diagram or Composite Structure Diagram If you do not want to create any diagram select None e Click either Next to proceed to the next step or Finish to finish extracting a structure Figure 97 P Extract Structure ooi lassifi Kame Type Connector Client Supplier i reata a trsm spline dif trsm 2 Select port s fw rightWheel Ey Frontwheel e i Frontwheel fe eftwheel LJ Frontyheel ee Frontheel O 3 Create a property Check a checkbox in Front of a pork to recreate the port on the new classifier and reconnect connecting connector s iF any Uncheck a checkbox in Front of a pork to maintain the existing connectors connected to the portis of the refactored propertyties Figure 9
17. an Association Block Figure 21 Association Block Button in BDD Diagram Toolbar v Creating a SysML Internal Block Diagram Using the Smart Manipulator Button To create a SysML Internal Block diagram for a Block 1 Select the Block symbol The smart manipulator menu will appear Figure 23 2 Click the SysML Internal Block diagram button The SysML Internal Block diagram will then be created to be owned by the selected block 3 The name of created SysML Internal Block diagram will be the same as the owner block The hyperlink to the created diagram will be added to the selected block SysML Diagrams al 4 k Z YUHANNA SN 7 7 k 7 7 Jal wel x mh i Cul CE Cl Cil C CEI SysML Internal Block Diagram Figure 23 Smart Manipulator Menu for Creating IBD 5 1 4 Creating Instances of Blocks with Complex Structure Creating instances for a complex model can be quite difficult especially since instances are frequently used in SysML unlike in UML in particular when assembling systems Starting with version 16 5 a new feature has been included Automatic Instantiation The purpose of this feature is to provide a wizard for automatic instantiation of the composite structures of a system or system parts Instances are widely used in simulation environments for example Paramagic and also for defining different system configurations and test cases The following two samples will describe how to
18. e Scope there are two types of scope i row scope and ii column scope You can select diagrams UML elements and or SysML elements as a scope e Dependency criteria include UML relationships SysML relationships semantic dependencies dependency through property and relationships through tags Cells in a dependency matrix show where the elements in the selected scope are associated with or related to one another A dependency matrix allows you to visualize the many to many traceability of elements from dif ferent diagrams particularly for elements interconnected in a large system A dependency matrix helps you e Quickly visualize dependency criteria e Compactly visualize the relationships of a large system which cannot be easily represented by a diagram on a single sheet of paper because of the diagram complexity e Visualize domain specific relationships through your own matrix templates for such domains e Understand relationships from a particular scope by filtering the unimportant kinds of model elements e Display relationships that cannot be represented in diagrams such as representations classes by lifeline behavior representations in other diagrams operation representations by Call Behavior Actions etc 10 1 Opening Dependency Matrix A matrix element in a model is similar to a diagram element When created the new matrix will appear in the Browser as a model element To open the matrix pane double click th
19. Constraint Block Figure 126 Select Parameters Dialog zaconatraint Constraint Block parameters parameters parameter Figure 127 Constraint Property with its Constraint Parameters 5 4 4 Using Parametric Diagram Elements Constraint Blocks Constraint blocks can only be defined on a BDD or a package diagram A constraint block typically contains one or more constraint parameters which are bound to properties of other blocks in a surrounding context where the constraint is used SysML Diagrams All properties of a constraint block are constraint parameters with the exception of constraint properties that hold the internally nested usages of other constraint blocks Constraints are specified only in an informal lan guage but a more formal language such as OCL or MathML could also be used Constraint blocks can only be defined on a BDD or a SysML package diagram Binding Connectors Binding connectors enable you to bind each constraint block parameter to the property of another block in the surrounding context of that constraint block Binding connectors are the only connectors allowed to bind con straint parameters to the properties of other blocks To create a binding connector 1 Click either i the Binding Connector button on the Parametric diagram toolbar or ii the Binding Connector icon on the smart manipulator of a constraint parameter or a part prop erty Figure 128 and Fig
20. Decelerate Car Reservoir BrakeSystem LossOfFluid _______ OffRoadCapabilty DeriveReqt Power 36 2 1 Test and procedure conditions Martine Maenan M aamut Mea v Da ea ha mwa mmn mnt Mam ivana a nt Figure 276 Example of Requirement Table B Report Report Wizard and Template 12 2 4 Requirement Report Use the Requirement Report template to generate a requirement report of the selected requirement elements A Requirement Report template will show the properties of all selected requirements Figure 277 hybrid cportutilt vehlole Requirement Re port Date July 45 2009 Revision 10 HSUV Requirements HSUV Specification 1 Eoo Frendiness L1 Emlsslon 4 Tie IKE fhallmee et Utaka Boks bens vekile stacks Verted By sy ES PFelEquomyTest 2 Performance The Hybrid SU Shall have th Drak lig aoce B ration aid OTF road Capa lik of a typealSuy Bet lave dramatically beter tel ecomomy 2 1 Braking The Hybrid SU Shall kaw th brak hg Capability ofa tpkal SUW Cer ved U Regenerate b rakli Cenved Requirements m Ai Reese rate Braklic 2 2 Puel Econom y The Hybrid HSU skall kaw dramatically beter tiel ecowonty tai atpkal SUY Problem a Power Wee ckd Tor aoce Bath otal S rE mace amp Cane capacity comet wht Te eon Cerlved i Regenerative B rakli CO PowerSource Mae meat W Rake Cerved Requirements LH dd Rege ke rative Braklig d 2 Rage CO 3 Powe once Management 2 3 OttRoadCapabllty The Hybrid SU Shall kaw
21. Figure 78 D N Anr ricyh Cc NAL 9N44 Nir n NANIA Fafa Copyright 2006 2011 No Magic Inc SysML Diagrams lt lt block gt Pang Enter Specification Alt Enker Symbols Properties Go To d Refactor b Select in Containment Tree Related Elements b Stereotype b Edit Conmpartment b Reset Labels Fositions Show Stereotypes Show Tagged Values o Show Provided Interfaces _ Show Required Interfaces Tre Figure 77 Port Shortcut Menu to Display Provided or Required Interface s ghblocke O Specification Enter Symbols Properties Alt Enter 0 To Refactor Select in Containment Tree Select in Structure Tree Stereotype Edit Compartment Reset Labels Positions Show Name Show Stereotypes Alt B d d Display Paths Display Related Elements Display Provided Required Interfaces Used By Depends On Ctrl AlE U Ctrl 4lk D Figure 78 Port Shortcut Menu to Display Provided and Required Interface s 2 The Required Provided Interfaces will be displayed on the port in the form of ball socket lolli pop notation Figure 79 SysML Diagrams ibd Block 4 sembly Fal Assembly lt lt block gt Figure 79 IBD with Required and Provided Interfaces Displayed The model in Figure 79 corresponds to the model in Figure 80 ecblock gt echlock gt gt Part
22. HSU HSU internalCom internalCom internalCom internalcom bustionEngi bustionEngi bustionEngi SEEM ne fif ne fi 3 ne fi 4 ne fra Fuelinjector Fuelinjector Fuelinjector FuelRail fuelDemand fuelbemand fuelDemand Figure 34 Example of Instance Created by Automatic Instantiation Wizard 11 You can reassign some values for example if you like to use SuperFuel for fuelReturn instead then reassign the fuelReturn slot in the HSU internalCombustionEngine Internal CombustionEngine instance specification Figure 34 to SuperFuel a Fuel kind with a specific fuelPressure Figure 35 The newly created diagram will look like the one in Figure 36 SysML Diagrams E Ad Instance Specification HSU internalCombustionEngine T m fate iE gt History HSU internalCombustionEngine H5UModel HSUY Structure Internal HSU internalCombustionEngine HSU H E Documentation Hyperlinks Usage in Diagrams 2 Deployed Artifacts H E InternalCombustionEngine PORET E Uel f crtl Inner Elements i fi HSU internalCombustionEngin Relations i fil HSU internalCombustionEngi Tags i fi2 HSU internalCombustionEngi Constraints i f3 HSU internalCombustionEngi i S fid HSU internalCombustionEngi L J Fp FS_ICE i OH Fr FuelReguilator S fra HSU internalCombustionEng i CE Fe FuelTank ssembly A FuelFitting Fuel i CE FuelReturn Fuel Property p7 Select Elements
23. HSUVModel HSUY Structure Interna default value fi4 HSUY Model HSUY Structure FuelInjector H5Uv Model HSU Structure Interna press SHIFT and click to HSUYModel HSU Structure HSUY Interfaces FS_ICE HSUVModel HSU Struc select recursively H HSUVModel sHSUY Structure FuelRegulator H5UYModel H5UY Structure Interr wl iiil gt Instantiated properties Type O Fuelinjector HSU Model HSU Structure Value Figure 27 Removing Instance Value 4 You can change the instance specification type to be created for any selected property by changing the Type property in the Instantiated properties table Generally the possible classifi ers are subtypes of the type of that particular property unless the type is an Interface If the type is an Interface the options in the drop down list will be elements which realize the Interface Figure 28 31 Copyright 2006 2011 No Magic Inc SysML Diagrams Automatic Instantiation Wizard 1 Select parts O 2 Select a package 3 Select a diagram Select partis propertyts to be instantiated You can change type of the selected part to another subky pe using the drop down list box below the tree 4 part with an abstract type cannot be selected unless changing its type to one of the subtype of the abstract type Default values iF existed will be used new instance will mot be created For a park with default value ipress SHIFT and click to sele
24. Ins1 Satellite Instruments Satellite Satellitesystem Cal Pins SysML Profile Blocks Real Satellite Instruments Value 2100 Cal Wins SysML Profile Blocks Real Satellite Instruments Value 2100 powerl Satellite PowerBalance Satellite Satellikesysterm Prol Satellite Propulsion Satellite Satellite Systern Cal Ppro SysML Profile Blocks Real Satellite Propulsion Value 4800 Ca Woro SysML Profile Blocks Real Satellite Propulsion Value 4800 Psy1 Satellite PowerSystem Satellite Satellitesystern Ca Power SvsML Profile Blocks Real Satellite PowerSystem Value 1000 met wWosy SyvsML Profile Blocks Real Satellite Powersystem Value 3000 Weight SysML Profile Blocks Real Satellite Satellitesysterm weighti Satellite WweightBalance Satellite SatellitesSystem Instantiated properties Type a E Real SysML Profile Blocks lt Back Figure 38 Automatic Instantiation Wizard Step 1 Select parts 3 In Step 2 Select a package create a new package named Satellitelnstance02 Figure 39 and click Next Copyright 2006 2011 No Magic Inc SysML Diagrams ie Automatic Instantiation Wizard 1 Select parts Ela Data G E Satellite 2 Select a package E SatelliteInstanceli O 3 Select a diagram a satelliteInstancel2 Select a package to hold instance specification s to be created 0 Satellit
25. M C8 fra HSUYModel HSU Structure FuelRail HSUVModel HSUY Structure InternalCon press SHIFT and click to E ft HSUYModel sHSUY Structure FuelTankAssembly HSUYModel sHSUY Structure Ir select recursively HH P fuelFitting H5UYModel HSU Structure Fuel HSUYModel HS5UY Structure Interne v lt im gt O Fuelinjector HSUVModel H5U Structure Figure 26 Adding More Instance Values 30 Copyright 2006 2011 No Magic Inc SysML Diagrams Ad Automatic Instantiation Wizard 1 Select parts El InternalCombustionEngine HSU Model H50 Structure 2 Select a package 7 P tertl HSUYModel HSUY Structure InternalCombustionEngine CE Fi HSUY Model HSU Structure Fuellnjector 4 HS0 Model HS5UY Structure Inl BM 2 WJ WJA 3 Select a diagram Select part s propertyis to be instantiated You can change type of the selected part to another subby pe using the drop down list box below the tree A part with an abstract type cannot be selected unless changing its type to one of the subtype of the abstract type Default tH fil H50 Model HSUY Structure FuelInjector HSUVModel HSU Structure Interna values iF existed will be i fiz HSUYModel HSUY Structure FuelInjector HSUVModel HSUY Structure Interna used new instance will not be created For a part with ig Hi3 HSUVModel H5UY Structure FuelInjector
26. Non normative Extensions You can define your own quantity and unit using the QuantityKind and Unit blocks defined in QUDV Library 13 1 QUDV Model Library in SysML Plugin QUDV Model Library is available for use in every new SysML project created from SysML plugin 16 8 or newer The library located in lt md install dir gt modelLibraries directory consists of four sub libraries e QUDV e SI Definitions e SI Specializations e SI Value Type Library 13 1 1 QUDV The QUDV library QUDV mdzip consists of the main definitions of the new units and quantity kinds system as specified in OMG SysML specifications 1 2 e g SimpleUnit SimpleQuantityKind DerivedUnit DerivedQuanti tyKind AffineConversionUnit UnitFactor QuantityKindFactor etc For more detail on these definitions see Annex C Non normative Extensions in OMG SysML specifications 1 2 13 1 2 SI Definitions The SI Definitions library SIDefinitions mdzip consists of predefined units and quantity kinds in QUDV system for using in your model You can use them in your customized units and value types 13 1 3 SI Specializations The SI Specializations library SISpecializations mdzip consists of a diagram and Blocks demonstrating how to extend the current QUDV system Model Library for Quantities Units Dimensions and Values QUDV 13 1 4 SI Value Type Library MagicDraw SysML provides the model library that contains the pre defined value types You can use th
27. Objective Function 94 Opaque Action 135 Output Expansion Node 136 Output Pin 138 P Package 89 90 152 Element Import 91 Model 90 Package Import 91 System Boundary 152 View 89 Package Import 91 Part Property 54 95 Performance Requirement 100 perspective 6 system engineer 6 Physical Requirement 101 Pin Input Pin 138 Output Pin 138 Value Pin 138 Port 18 56 96 Creating a New Provided Required Interface s 64 Displaying a Provided Required Interface s 67 Flow Port 18 55 Projects Specified Template 9 SysML 8 Property Constraint Property 54 Context Specific Value Compartments 175 Display Ports 58 Display Suppress Structure Compartment 69 Distributed Property 55 Edit Compartment 59 Extract Structure 77 Feature based Compartments 171 moe 94 Nested Part 56 Part Property 54 Reference Property 54 Shared Property 54 Show Default Value 61 Show Slot Type 62 Value Property 54 Q Quantity Kind 16 R Refactor Changing Requirement Type 104 Extract Structure 77 Reference Property 54 95 Refine 103 Report Wizard 208 Allocation Report Templates 226 Requirement Report Templates 213 Requirement Dependencies Report 221 Requirement Diagram 214 Requirement Report 216 Requirement Table Type A 214 Requirement Table Type B 215 Requirement Table Diagram Report 225 Templates 208 Requirement 100 Business Requirement 101 Changing Requirement Type 104 Copy 102 Derive 102 Design Constraint 101 Extended Requiremen
28. Performance E Performance erequirement Performance a srequirement requirements requirement requirement FuelEconomy Braking Acceleration OffRoadCapability cl Se ae Id 21 d 2 4 W 2 Gee Test The Hybrid Texst The Hybrid SUY Text The Hybrid SUY Text The Hybrid SIY HSUY shall have shall have the braking shall have the shall have the off road dramatically better fuel capability of a typical acceleration of a typical capability of a typical economy than a typical Sy Sy SY SUW Figure 137 SysML Requirement Diagram for Sub requirements 5 5 4 Numbering Requirement IDs Numbering requirements IDs is a trivial time consuming task in particular when working with a large SysML project Starting with version 16 5 SysML Plugin provides an additional feature to facilitate such a task Requirement ID Numbering This feature consists of three functionalities i Manual Numbering ii Auto matic Numbering and iii Suggested Solutions for Invalid Requirement s ID i Manual Numbering This functionality refers to the use of the Requirement ID Numbering dialog to number requirements IDs To number requirements IDs manually using the Requirement ID Numbering dialog 1 Open the Requirement ID Numbering dialog by selecting the Requirement ID Numbering option on e the diagram shortcut menu of the package containing the requirement s for example the HSUV Specification package in Figure 138
29. Property which is typed by the PropertySpeci ficType should be owned by block or subtypes of block 7 Feature based Compartments Derived from OMG SysML spec 8 3 2 7 8 3 2 7 SysML Plugin feature based compartments allow you to display additional compartments in internal properties There are six feature based compartments e values parts e references e constraints e properties formerly UML properties e operations For any given property these compartments will show information from the classifier of the property Fig ure 221 right hand side in conformity with SysML specifications outlined in the Compartment on Internal Properties section Feature based Compartments e lt block gt BallBoxu fim fertes stress StressType Pa Enes cubes Cube 0 cylinders Cylinder 0 constraints volEg gt YolumeEquation lt block box BallBox Ue ties stress Stress Type FeFe Eyes cubes Cube 0 cylinders Cylinder 0 parts balls Ball 0 WolEG YolumeEquation operations testStrese maxStress Real Boolean festatress masstress Real Boolean Figure 221 Compartments in a Block vs Feature based Compartments in an Internal Property For any property typed by a Block feature based compartments will contain the same information as that of the compartments on the Block symbol such as values parts references constra
30. Requirement Type Owner Source Risk Verify Method Customize Column Figure 170 Table Column Drop Down Menu for SysML Requirements Table Check a column name to display that column on the table or uncheck a column name to hide that column To customize displayed columns select Customize Column in Figure 170 The Select Custom Requirement Columns dialog will then display Figure 171 Select Custom Pet Mee eee Select search for or create elements Search for an element by using list or tree views To find an element type text or wildcard into the Search by name input field Search elements by their qualified names or use camel case when searching if the appropriate mode is enabled Type text or wildcard 7 to search fe Tree List _28 matohes found Master Requirement SysML Profile Requirements Requirement RealizingElements Element 0 MD Customization For SysMLi customizations For traceability Properti RealizingRequirements Class 0 MD Customization For SwsML customizations For traceability Prope RefinedBy NamedElement SvsML Profile Requirements Requirement RefinedByRequirements Class 0 MD Customization for SysML customizations For traceability Propl RefineRegquirements Class 0 MD Customization for SysMLi customizations For traceability Properti ReqDerive Class 0 MD Customization for SysML customizations For
31. Validation y OARS a a a Ja m 4 4 a Inset Hew Extension Point Figure 199 Use Case Smart Manipulator gt laa Specification Enter E Symbols Properties Alt Enter Mew Diagram G0 To Refactor Select in Containment Tree Related Elements Stereotype Use Case Numbering Aubosize Edit Compartment d Show Stereotypes Show Constraints Show Tagged Values Show Owner fo Wrap Words Suppress Extension Points Insert New Extension Point Chrl Alk E Figure 200 Use Case Shortcut Menu 6 Validation MagicDraw provides the Validation functionality to validate user created models against a set of constraints Use SysML validation suite SysML ValSuite in SysML Plugin with this MagicDraw functionality to validate SysML models see MagicDraw User Manual for more information on this MagicDraw functionality SysML ValSuite includes seven validation suites Validation 1 SysML ValSuite Activities This suite contains SysML constraints on the following elements Control Operator Control Value Discrete noBuffer Optional Probability and Rate 2 SySML ValSuite Blocks This suite contains SysML constraints on the following elements Binding Connector Block Distributed Property Part Property Reference Property Shared Property Value Property and Value Type 3 SysML ValSuite Constraint Blocks This suite contains SysML constraints on the following elements Constraint Block and Co
32. and properties compartments Figure 18 SysML Diagrams ants drivinglonditions Environment HSU gt Aybridsu y parts vehiclelarga Baggage acl Accelerator AutomotiveDomain ba alsa part Corse iis tuelF low gt FuelF lios bp BatteryPack properties bus CAM Bus driver Driver aa maintainer Maintainer dif Differential passenger Passenger em ElectricMotorGenerator allocatedFroam a4 epc ElectricalPoyrerController jallocatedFram a3 ft FuelTank Assembly fuelSupply Fuel gi Torque FuelTankAssembly iZ ElectricCurrent parts ice InternalcombustionEngineiallocatedF rom a2 fp FuelFump ecu PovrerControllnittallacatedFrom al fuelReturn Fuelidirection out ti Torque fuelSupply FueltreadOnly direction in t2 Torque trm Transmission fete Ente s bkp BrakePedal 1 Wales fuelFeturn Fuel fuelFlow Rate Real ee live gt Fronteyvheel 1 THEN veIght Feal rfwy Frontyvhieel 1 SysML Compartments parts references values constraints properties wheelHubsAssy YvheelHubAssembly 2 FT Figure 18 SysML Block Compartments Table 1 SysML Block Compartments Displayed Elements Part Properties properties which are typed by Blocks or subtypes of Block except Constraint Block having composite aggregation kind Shared Properties and Reference Properties properties which are typed by Blocks or subtypes of Block except C
33. cate dependency in a SysML project OMG SysML Specifications recommend Allocation dependencies to be depicted in tables which facilitate auto mated verification and validation V amp V and gap analysis The tables generally contain information on allo cate dependencies their clients and suppliers and also on the types of the clients and suppliers You can generate an Allocation report using the whole project or some elements selected from the Report Wizard dia log There are three available template styles NR ONA4 nannurinht A ONN C O p yr gni ZUU0 ZU j J J N No O lan 11 No Magic Inc Report Wizard and Template 12 3 1 Allocation Table Type A 12 3 2 Allocation Table Type B 12 3 3 Allocation Table Type C 12 3 1 Allocation Table Type A This table shows a summary of the allocate dependencies with their properties including the supplier types and names as well as the client types and names Figure 292 Allocation Table Type Name End Relation End Call Behavior Action a1 ProportionPower Call Behavior Action a ProvideGasPower P ice Call Behavior Action a3 ControlElectricPower Fart Property Call Behavior Action a4 ProvideElectncPower Part Property Figure 292 Example of Allocation Table A Report 12 3 2 Allocation Table Type B This table differs from Type A in that it shows allocate dependencies with their properties in another format that in
34. hot key Test Case Activity StateMachine Interaction See Section 5 5 1 for description a4 Ee 5 5 3 SySML Requirement Diagram Specific Features i Changing the Requirement Type Use this feature to change one or several requirement types to another requirement type To change one or more requirement types to another requirement type 1 Right click a requirement s whose type s you would like to change and select Refactor gt Convert To Figure 134 ppeextendedrequireme a Specificati Ent E pecification prEN LF Symbol s Properties Alk Enter New Diagram GoTo Refactor Convert To b cal artifact Select in Containment Tree Alt B Replace With 3 Component Related Elements m Data Type Stereotype CA Enumeration Requirement ID Numbering 3 Interface Edit Compartment CA Primitive Type Presentation Options More General b More Specific b businessRequirement design Constraint FunctionalRequirement Create Instance Risk verify Method interfaceRequirement performanceRequirement physicalRequirement mf LA E mi m Cu usabilityRequirement Figure 134 Change Requirement Type Shortcut Menu More Specific SysML Diagrams apeextendedrequirement ra eee Specification Enter Symbols Properties Alt Enter Mew Diagram P a0 To P Refactor Convert To r Artifact Select in Containment Tree Alt B Replace With Compo
35. i An Interface Requirement is a requirement that specifies the ports for connecting sys tems and parts of a system Optionally it may include the items that flow across the connector and or the Interface constraints Performance Requirement SysML Cr A Performance Requirement refers to a requirement that quantitatively measures the extent to which a system or a system part satisfy a required capability or condition SysML Diagrams Icon Description Physical Requirement SysML A Physical Requirement specifies the physical characteristics and or physical con straints of a system or a system part Design Constraint SysML C A Design Constraint is a requirement that specifies a constraint on the implementation of a system or on part of it Business Requirement MDSysML A Business Requirement is a requirement that specifies characteristics of the business process that must be satisfied by the system Usability Requirement MDSysML Ci A Usability Requirement specifies the fitness for use of a system for its users and other actors bdd Model Data B TestCase Metamodel bdd Model Data Requirement related MetaModel sametaclazs zametaclazs s2metaclasss gt Operation Aehavior NantedFlanant s sterecty pes TestCase Behavior Operation RequirementRelated Verifies Requirement emedelement Figure 131 Test Case Metamodel s sterectypes gt Figure 132 Requirement related Metamodel
36. one of the relations Refine Derive Copy Ownership The All Realizing Requirements property of a Requirement shows how the Requirement Is directhyindirectly realized by other Requirement s in all lower levels of abstraction The following table demonstrates leaf Requirements coverage by other requirements where a leat Requirement refers to the Requirement which does not own any Requirement Leaf Requirements Realizing Requirements All Realizing Requirements cH 94 CH d4 Power ae caw HSUVModel HSUV le vMo Requirements Cal d4 Power Require ments HSUW Specification Performa nce rh 9 4 CH d4 Regenerative Braking HSUVModel HSUV Require ments Braking HSUVModel H g IJ V Requirements HSUV opeciication Perorma Figure 283 Sample of Appendix B Coverage Analysis 12 2 6 Requirement Dependencies Report Use the Requirement Dependencies template to generate reports showing the properties of the related require ment elements in a specific scope The properties are Master Derived From Refined By Satisfied By Traced To and Verified By The content in this kind of report contains i Dependency Table ii Appendix for Requirements Text Table 221 Copyright 2006 2011 No Magic Inc Report Wizard and Template iii Appendix for Captured Diagram Images iv Hyperlinks in Generated Reports i Dependency Table They will be categorized in the table of related dependencies The requ
37. qo Ergonomics H 4 2 Performance H H 2 4 Acceleration d 2 1 Braking HS5U H 2 2 FuelEconomy 4 Qualification ita Max Acceleration 2 i MaxAcceleration Ma d 4 Power s CA PowerSourceManage CE d 2 Range i CE d 1 RegenerativeBraking 3 A Max cceleration SS Figure 257 SySML Verify_Requirement Matrix 10 3 4 Creating SysML Editable Matrices You can create SysML matrices by using either the i main toolbar ii main menu or iii Containment Tree i To create a SysML Editable Matrix using the main toolbar 1 Click the icon of the editable matrix that you want to create on the main toobar Figure 258 A SysML Allocation Matrix SysML Satisfy Requirement Matrix v SysML Verify Requirement Matrix The Create Diagram dialog will open Figure 259 Figure 258 SysML Matrices Toolbar 201 Copyright 2006 2011 No Magic Inc Dependency Matrix Create Diagram Create a new SysML Satisfy Requirement Matrix Type diagram name and select package in which a new diagram will be created Type SysML Satisfy Requirement Matrix name pntited1 owner for diagram E E HSUYModel HER MO Customization For SysML MD customization For SyshML orr ARS ModelingDomain HER QUBY Library MB customization For SyshMLmdzip ER UML Standard Profile UML Standard Profile xml 7 Ep Matrix Templates Profile Matrix_Termpla
38. value If the FlowPort is nonatomic and if all of the Flow Properties of the Flow Specification typing the port have in direction the FlowPort direc tion will be in or out if isConjugated true If all the Flow Properties are out the FlowPort direction will be out or in if isConju gated true If the Flow Properties are both in and out the direction will be inout A FlowPort can be connected via connectors to one or more flow ports that have matching Flow Properties There are three options in matching Flow Properties e 1 Type Matching The type being sent is the same type or a sub type of the type being received e 2 Direction Matching If the connector connects two parts that are external to one another then the direction of the Flow Properties must be opposite or at least one of the ends should be inout If the connector is internal to the owner of one of the flow ports then the direction should be the same or at least one of the ends should be inout e 3 Name Matching If the type and direction match several Flow Properties at the other end the property that has the same name at the other end is selected If there is no such property then the connection will then be ambiguous ill formed The default direction of the atomic FlowPort should be set to inout when creating a new atomic FlowPort or changing nonatomic to atomic type A Fl
39. 2 Right click the property and select Related Elements gt Display Internal Structure from the shortcut menu Figure 90 Each IBD having either the type or a supertype of the type of the property as its context will be available for you to select For example in Figure 90 the Front WheelsAssembly IBD is available Select it to display the structure of FrontWheelsAssembly block in the property Figure 91 s lt block frontWheelsAssembly FrontWheelsAssembt Specification Enter Symbol s Properties Alt Enter d d G0 To Refactor Select in Containment Tree Related Elements b Stereotype b Display Parts Autosize Edit Compartment Display Internal Structure Front heelsAssembly b Used By Ctrl Alt U Show Constraints Ei Frontwheels4ssenbly Depends On Crrl 4lk D Show CW mer F Wrap words yw Show Classifier Show Tagged Values b Figure 90 Display Structure Block Shortcut Menu SysML Diagrams s lt block gt frontWheelsAssembly FrontWheelsAssembly leftivvheel Frontyvheel E fw FrontWheel 1 E lettHaltshatt t aii spline ti Torque dif Differential tram rightHaltShaft right heel gt Frantyyheel Figure 91 Sample of Structure Displayed in Property 3 You can also display the structure in a new blank IBD having the FrontWheelsAssembly block or a subtype of the FrontWheelsAssembly block Figure
40. 8 3 2 Using Context Specific Value Compartments 177 8 3 3 Displaying Context Specific Value Compartments 178 8 3 4 Selecting the Context of Context Specific Value Compartments 180 8 3 5 Customizing Context Specific Value Compartment Display 181 8 3 6 Value Propagation 183 9 Structure Browser 186 9 1 Opening Structure Browser 186 9 2 Customizing Structure Browser Display 187 9 2 1 Structure Browser Shortcut Menu 187 9 2 2 Structure Browser Toolbar 187 9 3 Display Options 188 9 3 1 Display as Plain List 188 9 3 2 Show Inherited Structure 189 9 3 3 Show Full Type in Browser 190 9 3 4 Show Applied Stereotypes in Browser 190 9 3 5 Show Auxiliary Resources 191 9 3 6 Filter 191 9 4 Additional Structure Browser Menus 191 9 4 1 Go To gt Type lt name gt in Structure Tree Menu 192 9 4 2 Go To gt Owner Menu 192 9 5 Additional Diagram Menu 193 9 5 1 Select in Structure Tree Menu 193 10 Dependency Matrix 195 10 1 Opening Dependency Matrix 195 10 2 Working with Dependency Matrix Templates 197 10 3 SysML Editable Matrices 198 10 3 1 SysML Allocation Matrix 198 10 3 2 SysML Satisfy_ Requirement Matrix 199 10 3 3 SysML Verify_Requirement Matrix 200 10 3 4 Creating SysML Editable Matrices 201 10 3 5 Building Matrices 204 10 3 6 Editing Matrix 205 11 Teamwork 207 11 1 Working with Teamwork Project 207 12 Report Wizard and Template 208 12 1 Report Wizard 208 12 2 Requirement Report Templates 213 12 2 1 Requirement Diagram 214 12 2 2 Requirement Tab
41. E Element Import 91 Enumeration 17 18 Environmental Effect 151 Exception Handler 137 Expansion Region 137 Extend 153 Extended Requirement 100 External 15 Using External 46 External System 151 Extract Structure 77 F Feature based Compartments 171 Flow Final 137 Flow Port 18 55 96 Using Flow Port 82 Flow Property 56 96 Flow Specification 16 Using Flow Specification 47 Fork Join Fork Join Horizontal 137 Fork Join Vertical 137 Fork Join Horizontal 137 Fork Join Vertical 137 Functional Requirement 100 G Generalization 19 153 IBD 53 Include 152 Initial Node 137 Input Expansion Node 136 Input Pin 138 installation 6 Instance 18 Link 18 Quantity Kind 16 Unit 16 Interface 16 18 Creating a New Provided Required Interface s 64 Displaying a Provided Required Interface s 67 Flow Specification 16 Interface Realization 18 Interface Realization 18 Interface Requirement 100 Item Property 56 97 L Link 18 Loop Node 137 M Measure of Effectiveness 94 Merge 137 Migrating Old project 207 Model 90 System Boundary 152 modeling language SysML 6 UML 6 moe 94 N Nested Part 56 Node Activity Final 137 Activity Parameter Node 136 Conditional Node 137 Data Store 136 Flow Final 137 Initial Node 137 Input Expansion Node 136 Loop Node 137 Object Node 135 Output Expansion Node 136 Sequence Node 138 Structured Activity Node 137 Numbering Requirement IDs 106 O Object Flow 136 Object Node 135 136
42. Element alue P fuelFitting HSUvModel HSUY Structure Fuel HSUvModel Expression CA fuelReturn HSU Model HSU Structure Fuel HSUVModel Instance Value CA fuelSupply HSUVModelsHSUY Structure Fuel HSUYModet Literal Boolean press SHIFT and click to p i ice fficiency SysML Profile Blocks Real HSUYModel HSL Bad Literal Integer select recursively je J ICEFuelFitting HSUYModel HSUIY Structure HSUY Interfaced E Literal Null iii Literal String Instantiated properties Type value Literal Unlimited Matural Opaque Expression Time Expression Time Interval Figure 30 Changing Value Specificaotion Type for Slot Value 33 Copyright 2006 2011 No Magic Inc SysML Diagrams 6 Click Next to proceed to the next step once all the required properties have been selected 7 In step 2 Select a package either select an existing package or create a new package to be used to hold instance specifications which will be created after you click the Finish button Click Next e To select an existing package click on the package e To create a new package select the package owner in the tree and click the Create button A list of packages will open Choose a package Package Profile or Model from that list A package will be created and its specification dialog will open for you to customize for example assigning the package name Figure 31 p Automatic instantiation Wizard
43. Essential SysML profiles and model libraries will be used in the created SysML project Specify a project name select a location to store the project and then press OK L a Project location lt User hbome gt MD_projects SysML UML Guide to sii sa ogee _ Create directory for project and related data he F Froject Use Case from Existing Project Source Code Figure 3 New Project Dialog Ag Open Associated Perspective This kind of project is associated with the System Engineer perspective Do you want to open this perspective now Figure 4 Open Associated Perspective dialog 4 2 Creating New SysML Project from Specified Template To create a new SysML project from a specified template 1 You can i click File gt New Project on the MagicDraw menu ii click the New Project button on the main toolbar or iii press CTRL N The New Project dialog will open Figure 5 2 Click the Project from Template icon Figure 5 3 Enter the file name in the Name box Copyright 2006 2011 No Magic Inc Working with SysML Projects 4 Click the button to locate where to store the newly created project 5 Select the SysML template from the Select template t
44. Figure 66 Click OK when done 60 Copyright 2006 2011 No Magic Inc SysML Diagrams p Compartment Edit onstraints Tagged Values Default value Structure properties o l references parts values constraints Il operations Selected constraint Constraint Block Cancel Figure 66 Compartment Edit Dialog iv Show Default Value and Show Slot Type Property shortcut menus Use a Show Default Value to display the default value of a part If the default value is an Instance Specifica tion the defaultValue compartment containing the Instance Specification slot s will be displayed on the part instead In this case you can use b Show Slot Type to display the type s of the slot s in the compartment a Show Default Value To display the default value of a part property 1 Right click a part or property and select Show Default Value if it already has a default value on the shortcut menu Figure 67 NOTE If the property has no default value drag an instance with slot s to the property symbol The instance will then be assigned as the default value for this property and its slots with values will be displayed inside the property symbol Figure 68 SysML Diagrams eeblocke gt ss reference property Block m part prop Specification Enter fe TER Symbol s Properties Alk Enter GoTo Refactor Select in Containment Tree Alt B Related Elements j
45. Inc SysML Diagrams Open Requirement ID Nurbering dialog Ignore srequirements srequirements Ry Select in Validation Results E g 4 LL Text HHN ig 5 la Text Wout Figure 147 Suggested Solution for Assign New Number iv Finding a Requirement To find a requirement in Containment Tree and Tree of Requirement ID Numbering dialog e Select tree in the containment browser or the tree in Requirement ID Numbering dialog e To search for a requirement by its ID type the ID of the requirement The matched requirement will be selected if found El E Data ng Relations E ia HSU Model H 7 Relations i BL Explanations ef HSU Analysis H E HSU Behavior HSU Requirements GE Relations i FP HSU Specification C PowerSourceManagement CH 2 Performance CA 2 2 FuelEconormy CA 2 3 OFFRoadCapability CA 2 4 Acceleration 1 Braking Figure 148 Finding requirement by ID in Containment Tree e To search for a requirement by its name type followed by the name of the requirement The corresponding requirement will be selected if found 114 Copyright 2006 2011 No Magic Inc 115 SysML Diagrams l I ae z Search For OFFRoadCapability E Relations EFS HSUvModel Ee Relations H Explanations H E HSU Analysis H E HSU Behavior E9 HSUY Requirements fe Relations E E HSU Specification i fg PowerSourceManagement 3 CH 2 Performance LH 2 2 FuelE
46. Ine L 04 C Opy Igi il UU O LUIIN O M a g IC i C Dependency Matrix Ad Sco pe E Data H HSUYModel E Ep MD Customization for SysML H Fo ModelingDomain E Ep SysML Profile L Ep UML Standard Profile press SHIFT and click to select individually Figure 264 Scope Dialog 2 Select the check box es in front of the packages models or profiles that will be the row scope 3 Click OK to close the Scope dialog 4 Click the button next to the Column Scope in the matrix pane Figure 263 The Scope dia log will open Figure 264 5 Select the check box es in front of the packages models or profiles that will be the column scope 6 Click OK to close the Scope dialog 7 Click the Rebuild button 10 3 6 Editing Matrix You can create or remove dependencies directly in an editable matrix Double click on an empty rectangle in the matrix to create a new dependency or double click an existing dependency in the matrix to remove it i Creating New Dependencies You can create a corresponding dependency of each matrix directly in the matrix by double clicking on the intersection of the row and column elements The row and column elements will become the client and supplier elements of the created dependency respectively Another way to create a dependency is by right clicking on the intersection of the row and column elements Then select New Relation gt Outgoing and select the dependency you
47. Internal Properties Compartments To expand a feature based compartment e Set the value of the corresponding symbol property to false by clearing the check box For example to show values and parts compartments clear the Suppress values and Suppress parts check boxes To suppress a feature based compartment e Set the value of the corresponding symbol property to true by selecting the check box For example to hide properties and operations compartment select the Suppress properties and Suppress operations check boxes Feature based Compartments ii Using the Property Shortcut Menu The submenus for suppressing or expanding feature based compartments are listed inside the SysML Internal Properties Compartments option on the property shortcut menu Figure 224 a s lt block gt E box BallBox Specification Enter ao pevties stress stress Type Symbol s Properties alt Enter FE Fe ees SNS CF ed eee eT cubes Cube 0 Go To cylinders Cylinder 0 Refactor p part balls Ball 0 GR Select in Containment Tree Alt 6 mias Related Elements p depth m 1 0 height m 1 0 Stereotype b width m 1 0 Edik Compartment constraints See ea a eee vleg VolumnEquation Show Stereotypes b aperntions estStress maxstress Real 1 Show Owner d e pe wrap Words Show Tagged Values Show Default value Show Slot Type Suppress Structure SysML Internal Properties Compartments Expa
48. Pendulum System Id FRI Text The inverted pendulum system can control the l nmen pendulum upright by move the cart horizontally even An inverted pendulum also though the disturbance is applied to the pendulum called a cart and pole moreover the user can change the controller gain of the consists of a thin rod attached feedback controller to meet the required response at its bottom to a moving cart Whereas a normal pendulum 1S stable when hanging downwards a vertical inverted pendulum is inherently Pendulum Unstable and must bhe actively balanced in order to remain Compute Upright typically by moving the A i cart horizontally as part of a Motor feedback system The inverted pendulum is a classic problem in dynamics and control theory and widely used as benchmark for testing control algorithms Tendon Mechanism Figure 280 Image Object Anchored to the Comment Element of Requirement Report Wizard and Template InverttedPendulum Requirement Report Date July 17 2009 Revision 1 0 FR1 Inverted Pendulum System The inverted pendulum system can control the pendulum upright by move the cart horizontally even though the disturbance is applied to the pendulum moreover the user can change the controller gain of the feedback controller ta meet the required response Comment An inverted pendulum falso called a cart and pole consists of a thin rod attached at ts bottom to a moving cart Whereas a normal p
49. Profile and MD Customization for SysML Profile Both profiles have their corresponding API classes com nomagic magicdraw sysml util SysMLProfile and com nomagic magicdraw sysml util MDCustomizationForSysMLProfile respectively Each class allows you to e Get a string constant for each property of stereotype tag e Get a stereotype element e Check if an element is stereotyped See index html in SysMLProfileJavaDoc zip located at plugins com nomagic magicdraw sysml openapi docs for the JavaDoc for the two API classes 15 1 1 SysML Profile You need to import com nomagic magicdraw sysml util SysMLProfile to use this API class a Get a string constant for each property of stereotype tag Usage includes SysMLProfile S7EREOTYPE_PROPERTY_NAME For example SysMLProfile ALLOCATED_ALLOCATEDFROM_PROPERTY returns a string of allocatedFrom b Get a stereotype element Usage includes e SysMLProfile getInstance project gefStereotype where project refers to the project which uses SysML Profile e SysMLProfile getInstance element getStereotype where element refers to the element in the project which uses SysML Profile For example SysMLProfile getInstance project getBlock returns the reference to the lt lt Block gt gt stereotype object c Check if an element is stereotyped Usage includes SysMLProfile sStereotype amp Elem where Elem is the element you would like to check For examp
50. Publish to server C Empty text Select server Custom text INA s No Upload isl Display in viewer after generating report Figure 273 Report Wizard Dialog Output Options 6 Specify the report file name report file format and image file format Figure 273 It is recom mended to use RTF as the report file format 7 Click Generate to create the report Figure 273 Your report will then be generated Once gen erated it will automatically open in the default document editor See the MagicDraw Report Wizard user guide for more information on this Report Wizard dialog 12 2 Requirement Report Templates Use a Requirement Report template to generate a Requirement report that provides a summary of the require ment modeling in a SysML project You can generate a Requirement report on the whole project or on some specific elements selected from the Report Wizard dialog There are six built in Requirement Report tem plates 12 2 1 Requirement Diagram 12 2 2 Requirement Table Type A 12 2 3 Requirement Table Type B 12 2 4 Requirement Report 12 2 5 Coverage Analysis 12 2 6 Requirement Dependencies Report 12 2 7 Requirements Table Diagram Report Copyright 2006 2011 No Magic Inc Report Wizard and Template 12 2 1 Requirement Diagram Use this report template to generate basic reports for SysML requirements Requirement Diagram reports pro vide Requirement diagrams and tables describing the
51. Refactor Select in Containment Tree Select in Structure Tree Stereotype Edit Compartment Reset Labels Positions l Show Name Show Stereotypes L Show Constraints Show Tagged values Show Type Type Convert to Object Continuous Discrete MoBuffer Oyerarite jv Steam Figure 183 Context menu on Pin 5 6 4 Using Activity Diagram Elements Activity Decomposition Hierarchy Wizard You can decompose activities using the Activity Decomposition Hierarchy Wizard which makes it possible to convert activities into Class Diagrams or into SysML BDDs and represent analyze or document activity hierar chies in a diagram structure To decompose activities using the Activity Decomposition Hierarchy Wizard 1 Select either e Activity Decomposition Hierarchy Wizard on the SysML Activity Diagram shortcut menu Figure 184 e Diagrams gt Diagram Wizards gt Activity Decomposition Hierarchy Wizard on the main menu or e Analyze gt Model Visualizer on the main menu The Model Visualizer dialog will then be displayed Select the Activity Decomposition Hierarchy Wizard from the dialog SysML Diagrams act Activity Activity Diagram E Activity Diagram Action name e Behavior n CallOperation Specification Diagram Properties Shift Enter Show Diagram Frame Show Diagram Info BLOCK operation S Show Owner 0 To Select in Containment Tree Alt E Find in Dia
52. Specify attributes name visibility and aggregation of the new property to by typed by the newly created classifier instep 1 Figure 99 Step 3 Create a property Pane 5 Step 3 Create a property e The selected parts will be replaced by a new property which is typed by the classifier in Step 1 Enter the name visibility and aggregation of the new property Figure 99 e Specify the name of the new property in the Name box Figure 99 e Select the visibility of the new property from the Visibility box Figure 99 e Select the aggregation kind of the new property from the Aggregation box Figure 99 e Click Finish to finish extracting a structure Figure 99 6 Figure 100 shows the IBD after the structure was extracted Since it preserves the diagram space of the previous structure the original diagram will have minimal distortion and the exist ing layout will remain SysML Diagrams dif t2 Torque lt lt block gt frontWheelsAssembly FrontWheelsAssembly lettivwhieel Front yheel spline Pi ock t1 Torque fi Fuetinjector 4 trem CEFuelFitting fuelSupply Fuel Figure 100 Internal Block Diagram After Extracting a Structure 7 You can check how the automatically created new Block looks like by right clicking the part and select Go To gt Type lt name gt to select the Block in the browser Figure 101 Specification Enter Symbolis Properties Alt Enter Usage in Diagram
53. SysML Diagrams Ag Item Flow Item Property Select or create elements those will represent conveyed information circulating From source to target in given direction Item Flow Direction From pb To pe From pb To pc Conveyed Classifiers pc To pb Item Property Figure 110 Item Flow Item Property Dialog Direction Selection 6 Click the browse button next to the Conveyed Classifiers box The Select Conveyed Classi fier dialog will open Figure 111 7 Select a classifier to be used as the Conveyed Classifier and click OK Ay Select Conveyed Classifiers Search By Mame m lt UNSPECIFIED gt B E Data GH FP UML Standard Profile UML Standard Prof Number of elements 164 Multiple Selection gt gt gt Figure 111 Select Conveyed Classifiers Dialog 8 Click the browse button next to the Item Property box The Select Item Property dialog will open Figure 112 9 Select a part property to be used as the Item Property and click OK 87 Copyright 2006 2011 No Magic Inc SysML Diagrams LAW Select Item Property Figure 112 Select Item Property Dialog 10 Click OK in the Item Flow Item Property dialog An Item Flow having the selected property as its Item Property will then be created on the connector You can create a new conveyed classifier on either a n
54. SysML blocks can be used to define relationships between parts or other properties of the same containing block Non Normative Blocks MagicDraw SysML proposes five block subtypes Domain A Domain is a set of objects with a specific context and specific elements containing resources that are relevant to the objects A domain should be used to manage those resources SysML Diagrams External a An External is a block that interacts directly with the system to be modeled It helps the system modeler identify the system of interest relative to its environment System A System is an artifact created by humans and consisting of blocks that pursue a common goal that cannot be achieved by the system s individual elements 1 SysML supports the specifica tions analysis designs verifications and validations of a broad range of complex systems These systems may include hardware software information processes personnel and facili ties Subsystem A Subsystem is a system block that in turn represents an independent system This is often the case in a large system Systems of Systems SoS 1 A subsystem is typically represented by a set of logical or physical parts in a Block Definition Diagram These parts realize one or more system operations System Context A System Context is a virtual wrapper around the entire system and its actors 1 A system context refers to a defined usage of a block It describes some of the top
55. TestCase streaming streaming non Streaming nonStreaming functionalRequire ment interfaceRequire ment performanceRe quirement designConstraint Constraint Description Description excerpts have been taken from the OMG SySML Specifications 1 2 with permission An Action appearing in an AllocateActivityParti tion will be the client from end of an allocate dependency The element that represents the AllocateActivityPartition will be the supplier to end of the same allocate dependency A Copy dependency may only be created between two classes that have the require ment stereotype or a subtype of the require ment stereotype applied The text property of the client requirement is constrained to be a copy of the text property of the supplier requirement A requirement cannot copy more than one requirement Copy dependencies should not form a cyclic graph If the supplier requirement has sub require ments copies of the sub requirements are made recursively in the context of the client requirement Copy dependencies are created between each sub requirement and the associ ated copy A nested classifier of a class that is stereo typed by requirement must also be stereo typed by requirement A Requirement ID must be unique The type of return parameter of the stereo typed model element must be VerdictKind Note this is consistent with the UML Testing Profile
56. a car 1 151 Aggregation UML An Aggregation is a special form of Association that specifies a part whole relationship from an aggre gate whole source to a component part target Creating an Aggregation will also create a Shared Property typed by the component part in the aggregate and a Reference Property typed by the aggregate in the component part The aggregation values of the target and source ends are shared and none respectively 19 Any Action UML This element is introduced in order to maintain any other desirable action element with an appropriate metaclass stereotype applied 136 Association UML An Association represents a semantic relationship between two classifiers It is used for referencing two Blocks with one another thus creating two Reference Properties at both ends The aggregation values of the both ends of an Association are none 19 Association Block SysML An Association Block is an Association Class a kind of Association stereotyped by Block Like any other Block an Association Block can own properties and connectors 18 Binding Connector SysML A Binding Connector is a connector which specifies that the properties at both ends of the con nector have equal values If the properties at both ends of a binding connector are typed by DataTypes or ValueTypes it means that the instances of the properties at both ends must hold equal values recursively
57. a classifier 18 Interface UML An Interface specifies operations or signals If an Interface is provided to a port the external parts may call operations or send signals to the Block owning the port via that port If an Interface is required for a port the Block owning the port may call operations or send signals to its environment via that port 16 Interface Realization UML An Interface Realization is a specialized Realization relationship between a Classifier and an Interface This relationship signifies that the realizing classifier conforms to the contract specified by the Interface 18 Interface Requirement SysML An Interface Requirement is a requirement that specifies the ports for connecting systems and parts of a system Optionally it may include the items that flow across the connector and or the Interface constraints 100 Item Property SysML An optional property that relates the flowing item to the instances of the connector s enclosing block This property is applicable only for item flows assigned to connectors The multiplicity is zero if the item flow is assigned to an Association 56 Link UML A Link is a connection between two objects 18 Loop Node UML A Loop Node is a structured activity node that represents a loop with the setup test and body sections 137 Merge UML A Merge is a control node that brings together multiple alternate flows It is not used to synchronize concur rent flows but to accept
58. a package can import either individual members of other packages or all the members of other packages View SysML Pay A view is a representation of a whole system from the perspective of a single viewpoint A view can only own element import package import comment and constraint ele ments bdd Model Data Sh ViewPoint MetaMocdel sometaclass Class lt lt sterectpe gt Viewpoint Class Figure 114 Viewpoint Metamodel SysML Diagrams Icon Description ViewPoint SysML m A viewpoint is a specification of the conventions and rules for constructing and using a view for the purpose of addressing a set of stakeholder concerns The languages and methods for specifying a view can reference methods and languages in another view point They specify the elements expected to be represented in the view that may be formally or informally defined bdd Model Data a conform MetaMocdel zame taclazs Dependency szgteregtype Conform Dependency Figure 115 Conform Metamodel Icon Description Conform SysML a JA Conform relationship is a dependency between a view and a viewpoint The view conforms to the rules and conventions specified in the viewpoint 5 3 2 SysML Package Diagram Toolbar Button hot Element key Package See Section 5 3 1 for description P Model UML Ea A Model is a special kind of Package It contains a hierarchical set of ele ments that describe th
59. an Association Block can own proper ties and connectors SysML Diagrams Button Element hot key Association UML An Association represents a semantic relationship between two classifiers It is Fi used for referencing two Blocks with one another thus creating two Reference Properties at both ends The aggregation values of the both ends of an Associ S ation are none Directed Association UML A Directed Association is a one direction Association which references from a Fa Block to another Block thus creating one Reference Property typed by the tar get Block in the source end The aggregation value of the target end of a Directed Association is none Aggregation UML An Aggregation is a special form of Association that specifies a part whole rela o tionship from an aggregate whole source to a component part target Creating an Aggregation will also create a Shared Property typed by the com A ponent part in the aggregate and a Reference Property typed by the aggre gate in the component part The aggregation values of the target and source ends are shared and none respectively Directed Aggregation UML A Directed Aggregation is a one direction Aggregation relationship which refer a ences from a Block aggregate to another Block component part thus cre ating one Shared Property typed by the component part in
60. and output items that can flow between a Block and its envi ronment Flow Ports are interaction points through which data material or energy can enter or leave the owning Block The specification of what can flow is achieved by typing the Flow Port with a specification of things that flow This can include typing an atomic Flow Port with a single type Block Value Type Data Type or Signal representing the items that flow in or out or typing a non atomic Flow Port with a Flow Specification which lists multiple items that can flow In general Flow Ports are intended to be used for asynchronous broadcast or send and forget interactions Note that only non atomic Flow Ports can be conjugated Once conjugated all the directions of the typing Flow Specification s items will be negated 18 Flow Property A FlowProperty signifies a single flow element that can flow to from a block Flow properties are defined directly on blocks or flow specifications that are those specifications which type the flow ports Flow properties enable item flows across connectors connecting parts of the corresponding block types either directly in case of the property is defined on the block or via flowPorts A flow property s values are either received from or transmitted to an external block 56 Flow Specification SysML A Flow Specification specifies inputs and outputs that can flow through a port in terms of Flow properties Flow Specifications are used by F
61. connecting parts of the corresponding block types either directly in case of the property is defined on the block or via flowPorts A flow property s values are either received from or transmitted to an external block Port UML A Port defines an interaction point on a Block or a part allowing you to specify ja what can flow in out of the Block part or what services the Block part requires expects from or provides offers to its environment Ports are connected by SHIFT R connectors to other parts or ports Flow Port SysML See Section 5 2 1 for description Connector UML A connector is used to bind two ports together representing a relationship between those ports A connector can be typed by an association A logical connector can be allocated to a more complex physical path depicting a set of parts ports and connectors refer to allocation Item Property SysML An optional property that relates the flowing item to the instances of the con ki nector s enclosing block This property is applicable only for item flows assigned to connectors The multiplicity is zero if the item flow is assigned to an Association 5 2 3 SysML IBD Specific Features The SysML IBD specific features include i Display Parts Diagram shortcut menu ii Display Ports Property shortcut menu iii Edit Compartment Property shortcut menu SysML Diagrams iv Show Default Value and Show Slot Type Property shortcut men
62. display e In the menu select Replace primitive DataType with equivalent ValueType Figure 47 ROMEO Fe BZR bL Be The type of a value property must be a value type m i Integer A FA warning Yalue Property 4 an b Boolean A Ignore Move bo Search Results J E x E eaS A 1 all diagrams contaimng tn Figure 47 Active Validation Results Window Showing Invalid Value Properties e The the selected property ies will then be typed by the equivalent SysML Value Types Figure 48 48 Copyright 2006 2011 No Magic Inc SysML Diagrams bdd Model Data Untitled Type value Types SysML Frofile Blocks Boolean zblocks A Wales b Boolean a i Integer Type evalue Types SSML Profile Blocks Integer Figure 48 Valid Value Properties ii Convert Data Type To Value Type Simply apply the ValueType stereotype to the Data Types which type Value Properties in your SysML project bdd Model Data Main BDD adata Types Type Di alata lypesD1 eblocks A enumeration Type literali enumeration E literalz Figure 49 Value Properties Typed By Data Types SysML Diagrams bdd Model Data Main BOC N avalueTypes Type Di evalue Types Di eblocks A Wales di O1 el E1 O eValuelTypes ay N FA Type literal evalue TypesE1 literal Figure 50 Converted Value Properties You can specify each Value Type s Unit and Qu
63. it SysML Diagrams To disable Dynamic Centerlines e Click the Show Centerlines button Figure 181 on the activity diagram toolbar or e Press C or e Select Options gt Environment on the main menu The Environment Options dialog will then open Clear the Show centerlines in flow diagrams option under the Diagram gt Display group of the Environment Options dialog Mot i moe act Activity ACTI B E 61 abe Text Box E Anchor _ Dependency Image Shape Separator FE SysML Activity Diag Figure 181 Show Centerlines Button v Streaming Parameter Right click on the Activity Parameter Node or Pin which has a parameter Figure 182 and Figure 183 Check or uncheck the Stream menu for setting the value of isStream of the corresponding parameter to true or false respectively SysML Diagrams N Parameter value value Real Specification Enter ieam Symbolis Properties Alt Enter Go To Refactor Select in Containment Tree Alt E Select in Structure Tree Stereotype Aubosize Edit Compartment Show Stereotypes Show Constraints Show Tagged Values Show Owner Wrap Words Show Classifier Show State Type Select Activity Parameter Continuous Discrete NoBuFFer Overwrite Figure 182 Context menu of Activity Parameter Node SysML Diagrams Parameter argument Po ii Action Specification Enter Symbol s Properties Alt Enter 0 To
64. model invalidity problem s To see the list of appropriate solution s for an invalid element you can either e Right click the invalid element in the Active Validation Results window Figure 213 if you have open this window before Or e Click the warning symbol after you have clicked the invalid element in the diagram Figure 214 After clicking for example solutions will then be displayed Figure 215 A Remove all other redundant Copy dependency s T Remove Copy dependency Ignore Select in Validation Results Figure 215 Proposed Solutions for the Invalid Copy Dependency Validation 5 The Active Validation Results window includes the following icons If you click the icon Select in Containment Tree you will be redirected to the selected invalid element in the Containment Tree e icon Select Rule in the Containment Tree you will be redirected to the broken constraint of the selected invalid element in the Containment Tree containing the selected invalid element will then be displayed icon Solve you can either ignore the selected element which will thus not be considered in the next validation process or select one of the solutions provided to resolve the invalidity e icon Active Validation Options the Project Options dialog will then open for you to customize all the options listed under Active Validation 6 In the example below Figure 216 a constraint referenced as Copy A
65. of the port e Select or create port type manually The Select Port Type dialog Figure 76 will then open You can then choose a classifier to be used as the type of the port Click OK the Select Interface dialog Figure 73 will then open In the dialog you can either choose an existing interface or create a new one to be used as the Provided or Required Interface as selected in Figure 72 of the port In addition a Realization or Usage dependency will be automatically created from the port type to the Provided or Required Interface of the port SysML Diagrams Ad Select Port Type Model Search By Mame H E FS_ICE E FS_TRSM H E FuelFlow l C3 FuelTankFitting gt tetas H TICEData A LIEPCCmd H TIEPCData A ILTRSMCmd H 1TRSMData l IF5_EPC mE IFS_ICE IFS_TRSM H E ICEData l Figure B 20 Interfaces Typing Standard Figure B 21 Intially Defining Flow Specifi z Lal T Arralar aknr gt Figure 76 Select Port Type Dialog for Provided Required Interface b Displaying Existing Provided Required Interface s Using the Port Shortcut Menu To display the existing Provided Required Interface s of a port 1 Right click a port to open its shortcut menu Then either e select Show Required Interfaces or Show Provided Interfaces Figure 77 or e select Related Elements gt Display Provided Required Interfaces
66. on how to work with perspectives see Perspectives Selection and Customization in the Getting Started section in the MagicDraw User Manual 4 Working with SysML Projects Depending on whether you want to 4 1 Creating Blank SysML Project Creating New SysML Project from Specified Template Using OMG SysML Style Using QUDV Model Library or Using Quick Search Dialog SET N N 4 2 4 3 4 4 4 5 you will have to follow different procedures 4 1 Creating Blank SysML Project To create a new workspace for a blank project 1 You can i click File gt New Project on the MagicDraw menu ii click the New Project button on the main toolbar or iii press CTRL N keyboard shortcut The New Project dialog will open Figure 3 2 Click the SysML Project icon Figure 3 3 Enter the file name in the Name box 4 Click the button to locate where to store the newly created project 5 Click OK If the current perspective is not set to System Engineer perspective the Open Associated Per spective dialog will open Figure 4 Select Yes to set the current perspective to System Engi neer to start model SysML Working with SysML Projects New Project Create a new blank SysML project Systems Modeling Language SysML is designed for systems engineering applications Creating a new SysML project will switch MagicDraw to SysML graphical user interface System Engineer perspective
67. requirement subtype elements 5 5 6 SySML Requirements Table As requirements are text based it is more convenient to enter text using spreadsheet like tabular format i e SysML Requirements Table instead of limited size boxes in a diagram This table is consistent with OMG SySML specifications SysML Requirements Table contains requirements Each row in the table represents a requirement When cre ating such table it will consist of 9 columns 4 of them visible representing the properties of each requirement in the table Table 5 below lists the name and description of each column With this table you can e Create new requirements directly in the table or import the existing ones from your model to the table e Directly edit the properties of the requirements in the table e Directly generate requirement reports renumber requirements IDs or export the table into CSV or HTML format Table 5 SysML Requirements Table Default Columns Column Name Visible by Description default Y Row number ID Y Requirement ID Name Y Requirement name Text Y Requirement text Requirement Type N Type of requirement e g business requirement design constraint etc Owner N Requirement owner Source N For extendedRequirement and its subtypes only source of the requirement Risk N For extendedRequirement and its subtypes only level of risk of the requirement See Table 4 for more information Verify Method N For extendedR
68. similar to IBDs except that the only connectors allowed are binding connectors each having at least one end connected to a constraint parameter SysML Diagrams A Parametric diagram includes the usage of a constraint block to constrain the properties of another block It contains constraint properties and constraint parameters as well as other properties from within that internal block context All properties displayed other than the constraints themselves must either be bound directly to a constraint parameter or contain a property that is bound to a constraint parameter through any number of containment levels A constraint block generally contain many constraints each of them containing many con straint parameters Constrained properties typically have simple value types that can also carry units quantity kinds and probabil ity distributions This allows for a value property that may be deeply nested within a containing hierarchy to be referenced at the outer containing level The context for the usages of constraint blocks must also be specified in a parametric diagram to maintain the proper namespaces for the nested properties The state of the system can be specified in terms of the values of some of its properties A change in state will result in a different set of constraint equations to be recalculated This can be accommodated by specifying constraints that are conditioned on the value of the property with state Parametric diag
69. stereotype of the partProperty is Action Figure 193 Applied stereotype Allocated Action a M allocatedTo CA HartProperty Figure 192 An Action allocated to a partProperty lt lt hlock gt Block parts artProperty BLOCK allocatedFram Action Applied Stereotype Cel PartProperty z Allocated H allocatedF rom Action Figure 193 A partProperty Allocated from an Action 5 7 SysML Use Case Diagrams The purpose of a Use Case Diagram is to give a graphical overview of the functionalities provided by a system in terms of actors their goals represented as use cases and any dependencies among those use cases A Use Case Diagram describes the usage of a system The associations between actors and use cases repre sent the communications that occur between the actors and the subjects to accomplish the functionalities asso ciated with the use cases The subject of a use case can be represented through a system boundary The use cases enclosed in the system boundary represent the functionalities performed by behaviors activity diagrams sequence diagrams and state machine diagrams SysML Diagrams Actors may interact either directly or indirectly with the system They are often specialized so as to represent a taxonomy of user types or external systems The only relationship allowed between actors in a use case dia gram is generalization This is useful in defining overlapping ro
70. the aggregate The aggregation value of the target end of a Directed Aggregation is shared Composition UML A Composition is a special form of Aggregation which requires that a part of a a Block instance be included in at most one composite object at a time The composite object is responsible for the creation and destruction of its parts In F other words a Composition specifies a strong part whole relationship from a composite whole source to a composite part target Creating a Composi tion will also create a Part Property typed by the composite part in the com posite and a Reference Property typed by the composite in the composite part The aggregation values of the target and source ends are composite and none respectively Directed Composition UML A Directed Composition is a one direction Composition relationship which ref a erences from a Block composite to another Block composite part thus creating one Part Property typed by the composite part in the composite The aggregation value of the target end of a Directed Composition is compos ite Generalization UML A Generalization is a taxonomic relationship between a more general classifier Pai and a more specific one Each instance of the specific classifier is also an indi rect instance of the general classifier Thus the specific classifi
71. the connector smart manipulator menu or e iii drag the property to be used as the item property and drop it to the connector 2 The Item Flow Item Property dialog will then open Figure 108 SysML Diagrams Ag Item Flow Item Property Select or create elements those will represent conveyed information circulating From source to target in given direction Item Flow Direction From pb To p Conveyed Classifiers Item Property Cis L Figure 108 Item Flow Item Property Dialog 3 The existing item flows on the selected connector can be selected for setting the item property using the Item Flow drop down menu The item flows whose realizing connector property con tains the selected connector will be listed in this drop down menu Figure 109 Ad Item Flow Item Property Select or create elements those will represent conveyed information circulating From source to target in given direction Item Flow Direction Conveyed Classifiers Item Property Number of elements 2 Figure 109 Item Flow Item Property Dialog Item Flow Selection 4 You can also create a new item flow by selecting lt NEW gt in the drop down menu 5 In the Item Flow Item Property dialog you can also choose the direction of the Item Flow from the Direction drop down menu Figure 110 86 Copyright 2006 2011 No Magic Inc
72. the invocation of the associated behavior The argument values of the action are available to the execution of the invoked behavior 135 Composition UML A Composition is a special form of Aggregation which requires that a part of a Block instance be included in at most one composite object at a time The composite object is responsible for the creation and destruction of its parts In other words a Composition specifies a strong part whole relationship from a composite whole source to a composite part target Creating a Composition will also create a Part Property typed by the composite part in the com posite and a Reference Property typed by the composite in the composite part The aggregation values of the target and source ends are composite and none respectively 19 Conditional Node UML A Conditional Node is a structured activity node that represents an exclusive choice among alter natives 137 Conform SysML A Conform relationship is a dependency between a view and a viewpoint The view conforms to the rules and conventions specified in the viewpoint 90 Connector UML A connector is used to bind two ports together representing a relationship between those ports A con nector can be typed by an association A logical connector can be allocated to a more complex physical path depicting a set of parts ports and connectors refer to allocation 56 Constraint Block SysML C
73. the offroad capability of a tipkal SUY Cen yad Co Power Cerlved Requirements Conlderdal Wo Magla rec Figure 277 Sample of Requirement Report Template The content in this kind of report contains e i Category of Information Generated from Requirements e ii Requirements Sort in Reports e iii Anchored Elements of Requirement iv Appendix A for Captured Diagram Images e v Hyperlinks in Generated Reports Report Wizard and Template i Category of Information Generated from Requirements Information generated from each selected requirement can be categorized into five sections e a Heading section e b Text description section b e c Documentation section e d Requirement properties section e e e Requirement related element section a Heading section This section contains a requirement heading that consists of a requirement ID number and name b Text description section This section contains a text property that describes the requirement c Documentation section This section consists of documentation hyperlinks and texts of anchored elements to the requirement d Requirement properties section This section will contain properties such as Master Risk Source VerifyMethod and also additional tags of user defined requirement stereotypes e Requirement related element section This section will show model elements that are related to the requirement ii Requirements
74. through any nested properties within the connected properties If the properties at both ends of a binding connector are typed by Blocks it means that the instances of the properties must refer to the same block instance As with any connector owned by a SysML Block each end of a binding connector may be nested within a multi level path of properties accessible from the owning Block The NestedConnectorEnd stereotype is used to represent such nested ends just as for nested ends of other SysML connectors 95 Block SysML Blocks provide a general purpose capability to describe the architecture of a system and represent the sys tem hierarchy in terms of systems and subsystems Blocks describe not only the connectivity relationships within between a system and its subsystems but also quantitative values as well as other information about that system for example doc umentation 14 Boundary System A Boundary System is a special external system that serves as medium between another system and the system under development without having its own interests in the communication For example Bus system or Commu nication system 1 151 Business Requirement MDSysML A Business Requirement is a requirement that specifies characteristics of the business process that must be satisfied by the system 101 Call Operation Action UML A Call Operation Action is an action that transmits an operation call request to the target object where it may cause
75. traceability Properties descrip ReqDerivedFrom Class 0 MD Customization For SysMLiscustamizations For traceability Properties c RegRetineBy Class 0 MD Customization For SysMLi customizations For traceability Properties desc RegRetines Class 0 MB Customization For SysML customizations For traceability Properties descri ReqTracedFrom Class 0 MD Customization for SysML customizations for traceability Properties de ReqTracedto Class 0 MOD Customization For SysML customizations For traceability Properties desc SatisfiedBy NamedElement SyvsML Profile Requirements Requirement im flaaadeooaoaooadaal Figure 171 Select Custom Requirement Columns Dialog 133 Copyright 2006 2011 No Magic Inc SysML Diagrams Select a property tag to be displayed as a new column of the Requirement Table and then press OK The new column will then display on the table To be able to select multiple properties tags to be displayed use the Multiple Selection button Figure 177 m Export You can also export a SysML Requirements Table to an HTML or CSV file by clicking the Export icon on the table toolbar Table 6 All requirements in the table will be exported to a file of the selected file format 5 6 SysML Activity Diagrams Activity diagrams describe control input and output flows among actions They represent the system business a
76. unlocked Report Wizard and Template For more information on Teamwork Server see the MagicDraw TeamWork User Guide 12 Report Wizard and Template This section contains only introductory information about the Report Wizard and SysML report templates For detailed information on how to use the Report Wizard engine see the MagicDraw Report Wizard user guide 12 1 Report Wizard To launch Report Wizard 1 Click Tools gt Report Wizard on the main menu Figure 268 The Report Wizard dialog will open Figure 269 Hyperlinks Project Merge Report Wizard Figure 268 Report Wizard Menu 2 The following nine built in SysML report templates will appear in the Report Wizard dialog Fig ure 269 e Requirement Diagram e Requirement Table Type A e Requirement Table Type B e Requirement Report e Coverage Analysis e Requirement Dependencies Report e Requirements Table Diagram Report e Allocation Table Type A e Allocation Table Type B e Allocation Table Type C Report Wizard and Template Report Wizard Select a report template Select a report template from which you would like to generate a report In this page you can also create new templates or edit delete open cone import export existing templates Select Template H Other Documents E E Allocation Table Type A i E Allocation Table Type B i Allocation Table Type C Coverage Analysis Requirement De
77. use the Automatic Instantiation feature i To automatically instantiate a Block 1 Right click a Block and select Create Instance on the shortcut menu Figure 24 The Auto matic Instantiation Wizard dialog will open Figure 25 Note that SysML sample projects are available in the lt md install dir gt samples SysML directory The hybrid sport utility vehi cle mdzip sample is used to demonstrate how this feature works SysML Diagrams 29 PEF uelF iting FuelFloy block InternalCombustionEngine i Fuelinjector 4 fil Fuellnjector fi Fuelinjector fid Fuellnjector fi4 gt Fuelinjector fr FuelRequlator ft FuelTankAssembly iceEfficiency Real fra FuelRailjallacatedFrom tdist aN ee Po ee bee fuelReturn Fuelreadonly direction int fuelSupply Fuelidirection out Flow Specifications FuelFlow sho ae Po pert y fuelReturn FueljreadOnly direction int fuelSuplly FuelreadOnly direction out Enter Specification Symbol s Properties Alt Enter Mew Diagram 0 To Refactor Select in Containment Tree Select in Structure Tree Select in Inheritance Tree Related Elements Tools Stereotype Autosize Edit Compartment Insert Mew Port Create Instance 7 Figure 24 Create Instance Shortcut Menu Automatic Instantiation Wizard O 2 Select a package 3 Select a diagram Select partis be instantiate change type of the selected part to anot
78. 2 1 Braking HSU H 2 2 FuelEconomy H 2 3 OffRoadCapa 4 Qualification Ho SafetyTest H H d 4 Power HSU qo PowerSourceM lq d 2 Range HSU qo Ergonomics H dq Eco Friendines F1 2 1 Emissions Wee i a I i ia I Lu oO aa Ch a _ CL m m I a ee 7 CE CA H 4 2 FuelCapacity 4 PassengerCap i E ICEFuelFitting H InteriorSubsystem s E InternalCombustionEngine E LightingSubsystem n E Power E PowerContralUnit 2 O PowerSubsystem a i O Transmission a Interior Subsystem Figure 256 SysML Satisfy_ Requirement Matrix 10 3 3 SysML Verify_Requirement Matrix The SysML Verify_Requirement matrix consists of e Row Named element which can be the client element of Verify dependency e Column Requirement Element which can be the supplier element of Verify dependency 200 Copyright 2006 2011 No Magic Inc Dependency Matrix V Verify Matrix x 1 gt o Row Element Type lificationAction kms Column Element Type Requirement sues Row Scope ASUV Behavior Column Scope ISUV Behavior Row Added Removed Element ee Column Added Removed Element E BAA R oe oe H 2 3 OffRoadCapa H SafetyTest H Ho d 4 Power HSLY J PowerSourceM q d 2 Range HSU qo Capacity HSU 4 4 1 CargoCapacit H 4 2 FuelCapacity J PassengerCap j Eco Friendines 4 R1 2 1 Emissions
79. 32 1264070354546 490 Symbol Bounds java awt Rectangle x S7 4 y 147 width 19 w Name Description Apply Style Default I Make Default Figure 55 Symbol Properties Dialog of Callout Box SysML Diagrams The new callout notation applies to all types of SysML diagrams 5 2 SysML Internal Block Diagrams IBD Internal Block Diagrams are based on UML composite structure diagrams and include restrictions and exten sions as defined by SysML An Internal Block Diagram captures the internal structure of a Block in terms of properties and connections among properties A Block includes properties so that its values parts and refer ences to other blocks can be specified However whereas an Internal Block Diagram created for a Block as an inner element will only display the inner elements of a classifier parts ports and connectors an Internal Block Diagram created for a package will display additional elements shapes notes and comments All properties and connectors that appear inside an Internal Block Diagram belong to are owned by a Block whose name is written in the diagram heading That particular Block is the context of the diagram SysML per mits any property part shown in an Internal Block Diagram to display compartments within the property or part symbol 5 2 1 SysML IBD Metamodel and Elements bdd Model Data ES Magicbrayy SyeML Properties ametaclasss Property esterectypes Afock Propert
80. 8 Step 2 Select port s Pane 4 Step 2 Select port s All the ports available to be defined on the Classifier to be created are listed in the table as shown in Figure 98 If you do not need a port remove it by clearing the check box in front of the port name If you clear any of the ports check boxes the connectors will be directly con nected to the structure inside the extracted classifier e In the first column select the ports which you want to create for the connectors that are connected to the elements outside the extracted classifier The connectors which are shown in the Connector column will be reconnected to these ports instead of being connected to the selected structures Figure 98 e You can change the port name in the Name column Figure 98 e You can change the port type using the drop down list in the Type column Figure 98 e The Connector column shows the name of the connector which is connected to the created port after a structure has been extracted Figure 98 e The Client and Supplier columns show the client and supplier elements of the connectors defined in the Connector column Figure 98 SysML Diagrams e Click either Next to proceed to the next step or Finish to finish extracting a structure Figure 98 P Extract Structure O 1 Create a classifier Name FrontWheelsAssembly 2 Select port s visibility public 3 Create a property i Aggregation composite ww
81. 92 as its context using the IBD shortcut menu Figure 93 The structure will be as in Figure 94 s lt block gt FrontWheelsAssembly Pree Tes live gt Frontvvheel 1 ri Fronteyvhneet 1 parts dif Ditterential O OO A Specification Enter o Symbol s Properties Alt Enter Mew Diagram d SysML Internal Block Diagram O akhna E en as m Go To SysML Parametric Diagram Refactor T SysML Activity Diagram Select in Containment Tree Alt E SvsML State Machine Diagram Select in Inheritance Tree SysML Sequence Diagram Related Elements d SysML Block Definition Diagram Tools Figure 92 Creating an IBD for the Subtype of the FrontWheelsAssembly Block SysML Diagrams ModitiedFvvA Specification Diagram Properties ShiFk Enter Alt Entei iy Show Diagram Frame Show Diagram Info Show Oner 0 To d Select in Containment Tree Alt B Find in Diagram Ctrl ShiFk D Fit in Window Cer hy Display Parks ol Zoom In Ctrl NurmPad Display Ports El Zoom Gut Ctrl MumP ad E Display Internal Structure Figure 93 IBD Shortcut Menu to Display Structure Spline rightHaltshatt a Y rfw FrontWheel 1 Figure 94 Sample of Structure Displayed in IBD 4 You can also display the structure of the FrontWheelsAssembly block in the structure com partment of the block itself SysML Diagrams 5 2 5 Extract Structure Extract Structure is the first advanced au
82. DataType InstanceSpecitication Figure 13 Value Type Unit and Quantity Kind Metamodels Icon Description Value Type SysML m A Value Type is a type which defines values that can be used to provide information on a system but cannot be identified as the target of any reference These values may be used to type properties operation parameters or potentially other elements within SYSML Quantity Kind SysML ta A Quantity Kind in SysML 1 0 and 1 1 called Dimension is a kind of quantity that can be measured using defined and unrestricted units of measurement For example length a quantity kind may be measured by meter kilometer or foot units Unit SysML A Unit is a particular value that can be used to specify a quantity of a dimension A unit often relies on precise and reproducible measuring techniques For example a unit of length such as meter may be specified as a multiple of a particular wavelength of light A unit can also use less stable or precise ways to express some values such as costs expressed in some currencies or a severity rating measured by a numerical scale SysML Diagrams Description Data Type UML A Data Type is a type whose instances are identified only by their values A typical use of Data Types would be to represent the primitive types of the programming language used For example integer and string types are often treated as data types Enumeration UML An En
83. Department OF Motor vehic 4ssaciation HsUVModel Driver H5Uv Model sHSLy amp ssaciation HsUvModel Driver HSUYModel sHSLYy be 4ssaciation HsUvModel Driver HSU Model HSUy be 4ssociation HsUvModel Driver HSUYModel HSL be g Association HSUModel sHybridSUy bsHSUY Model be ef Association HSUModel sHybridSUy bk HSUVMode be g Association HsSU Model sHybridSUY c H5LvModel Le A Ae enristinn HEL Wadak Hubhrid S M 2 HS Medel I Figure 160 Create Diagram Dialog 2 Type in the name for the SysML Requirements Table to be created and select its owner in the element tree Figure 160 3 Click OK Mame H E Data iG Relations H E HSL Model GE FP ModelingDornain F Index with explanations Figure 161 Blank SysML Requirements Table 124 Copyright 2006 2011 No Magic Inc SysML Diagrams b To create a SysML Requirements table using the main menu 1 Click Diagram gt SysML Diagrams gt SysML Requirements Table on the main menu Fig ure 162 The SysML Requirements Table dialog Figure 163 will open I TN class Diagrams Ctrl 1 Communication Diagrams Ctrl 3 Protocol State Machine Diagrams Ctrl 6 Implementation Diagrams Cbrl 6 Composite Structure Diagrams Ctrl 9 Interaction Overview Diagrams Ctrl 0 Custom Diagrams SysML Matrices SysML Activity Diagrams C 7 SysML Block Definition Diagrams Diagram Wizards SysML Interna
84. Description Block SysML Blocks provide a general purpose capability to describe the architecture of a system and represent the system hierarchy in terms of systems and subsystems Blocks describe not only the connectivity relationships within between a system and its sub systems but also quantitative values as well as other information about that system for example documentation SysML Diagrams Icon bdd Model Data ES Block Definition Diagram Icon Description Domain A Domain block represents an entity a concept a location or a person from the real world domain A domain block is part of the system knowledge 1 External An External block is a block that represents an actor It facilitates a more detailed mod eling of actors like ports or internal structures 1 System A System is an artificial artifact consisting of blocks that pursue a common goal which cannot be achieved by the system s individual elements A block can be a software hardware a person or an arbitrary unit 1 Subsystem A Subsystem is a typically large encapsulated block within a larger system 1 System Context A System context element is a virtual container that includes the entire system and its actors 1 bdd Model Data g Flow Specification zsmetaclazs gt Interface zsme tacl ass Class c lt sterectypes gt Block Class T szgteregtype FlowSpecification EF Int
85. Do you want bo switch bo the System Engineer perspective mow Figure 1 Launching MagicDraw with SysML Plugin Message Dialog ii To switch to the System Engineer perspective from any other perspectives 1 Click Options gt Perspectives gt Perspectives on the MagicDraw main menu 2 Select System Engineer from the Select Perspectives dialog and click Apply Figure 2 Select Perspective Choose MagicDraw perspective Choosing perspective will switch MagicDraw to the graphical user interface designed for a specific role business system analyst architect etc DoDAF Architect Full Featured Quick Start Software Architect System Analyst Current system Engineer Cee If the Expert bow is checked the interface will be complex and have all details exposed Un check Expert if you are a new user Non expert mode only exposes important common options and data in the user interface Expert mode can be changed for a project at any time Description Perspective provides set of features dedicated to system engineers SysML support is accessible Requirements elicitation and modeling features are highlighted Configuration is modeling oriented UML modeling features code engineering transformations and other non system modeling related features are hidden Figure 2 Select Perspectives Dialog r Copyright 2006 2011 No Magic Inc Working with SysML Projects For more information
86. Figure 80 BDD with Parts Ports and Interfaces vi Display Suppress Structure Compartment Property shortcut menu OMG SysML specifications allow properties to have structure compartments so that their internal properties structures can be shown To display the structure compartment of a property 1 Right click a propterty and clear the Suppress Structure option on the shortcut menu Fig ure 81 do the opposite to suppress the structure compartment SysML Diagrams s lt bloack reference prd oD Specification Enter shl Symbolist Properties Alt Enter part prop defi Go To b value prope Refactor reference p part prope Select in Containment Tree Alt E Related Elements pii Stereotype I Edit Compartment Show Stereotypes b Show Owner b Wrap Words Show Tagged Values b Show Default Value Show Slot Type Suppress Structure SysML Internal Properties Compartments I Context 5pecific Values p Type I Figure 81 Property Shortcut Menu to Display Structure Compartment 2 The structure compartment of the property will be displayed Figure 83 Otherwise the prop erty will look like in Figure 82 zsblock reference property Block aa eeblocks oe reference property Block lt lt block gt Bii part property Block oe defauhtValue value property S21 reference property instance part property instance Figure 82 Part without Struct
87. Highlighted after Validation 8 Place your mouse pointer on the warning icon to display the error message corresponding to the broken constraint Figure 207 srequirements reguirements K OfRoadCapability FuelEconomy Id 2 Fos alee a Text The Hybrid Text The Hybrid DA SJV shall hawe the i off road capability of dramatically e a typical SUW better fuel fa economy than a ae typical SU Figure 207 Error Message Displayed by the Warning Symbol 9 Click the warning icon to display a menu Then select either Ignore or Select in the Validation Results Figure 208 e If you select Ignore the invalid element will then be excluded from the next validation process e f you select Select in the Validation Results the element will then be selected in the Validation Results window This option helps identify the invalid element instantly especially when there are a number of invalid elements displayed in the Validation Results window A reguiement FuelEconony Ignore Select in Validation Resulks eae A Text The Hybrid A EHS shall have dramatically aT better fuel Pa economy than a a typical SUW El m Pa Figure 208 Invalid Element Validation Options 10 The Validation Results window includes the following icons If you click the Validation icon Select in Containment Tree you will be redirected to the selected invalid element in the Containment Tree e icon Select
88. However you could use instead SysML PropertySpecificlype strategy which is a set of on the fly exten sions subtypes of each Block used in a complex assembly hierarchy to afford a point of redefinition of the Part Properties and their Value Properties as required See the PropertySpecificType section in OMG SysML spec ifications For more information on Deep Reconfiguration see http training nomagic com 8 3 Context Specific Value Compartments The purpose of Context specific Value Compartments is to show various values as a result of a reconfigured selected context In the FuelTank example see 8 1 Progressive Reconfiguration above the capacity of a FuelTank in a Vehicle context is reconfigured to 46 litres In the WheelHubAssembly example see 8 2 Deep Reconfiguration above the diameter of the Tire Tire Bead and Rim the inflationPressure of the WheelAssembly etc in a Truck context will be reconfigured to suit the truck This section contains the following subsections 8 3 1 Advantages of Context Specific Value Compartments 8 3 2 Using Context Specific Value Compartments 8 3 3 Displaying Context Specific Value Compartments 8 3 2 8 3 3 8 3 4 Selecting the Context of Context Specific Value Compartments 8 3 5 Customizing Context Specific Value Compartment Display 8 3 6 8 3 6 Value Propagation You can see a sample of a Deep Reconfiguration project by opening context specific values mdzip i
89. Inserk New Attribute Insert New SysML Property value Property Insert Mew Operation Ctrl 4lk o Part Property Chel alka Insert Mew Signal Reception CErl Alk R Shared Property Insert New Port Reference Property Create Instance Constraint Property Flow Property Figure 14 Shortcut Menu for Property and Operation Insertion b To create a new SysML property using the Block Smart Manipulator menu either 1 Click the small orange circle on a Block The sub menu will open Figure 15 2 Select a property type for example Part Property or 1 Bring your pointer to a Block The Smart Manipulator menu will open Figure 16 2 Select one of the very last six icons yellow rectangle on the menu to create a SysML property In order for those icons to be displayed on the menu you must be in the Expert mode SysML Diagrams Distributed Property Reference Property Shared Property Value Property Constraint Property Flow Property Figure 15 Block Smart Manipulator for SySML Property Figure 16 Block Smart Manipulator II for SySML Property For further information on SysML properties see the SysML Internal Block Diagrams IBD section You can also use the Block shortcut menu to create a new UML property or UML operation For more informa tion see MagicDraw User Manual If you just create a new stereotype as a subtype of Block e g CustomBlock and use it
90. L Diagrams El Search Results HE From loaded diagrams 0 B E From model 13 Search in active diagram only Load diagrams and autoloadable modules Case sensitive Match whole words only Search data unused in diagrams Orphaned proxies only Java regular expression Clear previous results Figure 151 Finding requirement by name using Find dialog To find the requirement using the Quick Find dialog e You can either select Edit gt Quick Find in the main menu or press Ctrl Alt F to open the Quick Find dialog e To search for a requirement by its ID type the ID of the requirement into the combo box Type Name in the Quick Find dialog Type Mame 1 patch Pound ma 2 2 FuelEconomy HSUVModel sHSUY Requirements Performance Figure 152 Finding requirement by ID using Quick Find dialog 117 Copyright 2006 2011 No Magic Inc SysML Diagrams e To search for a requirement by its name type before the name of the requirement in the combo box Type Name Type Name FuelCapacity 1 makeh Found mi 4 2 FuelCapacity HSUVModel HSUY Reguirements HSUY Specific Figure 153 Finding requirement by name using Quick Find dialog 5 5 5 Using SysML Requirement Diagram Elements Requirement a Using Requirements A requirement specifies a capability or a condition that a system must or should satisfy The default interpreta tion of a compound requ
91. ML Parametric Diagrams 93 5 4 1 SysML Parametric Diagram Metamodel and Elements 94 9 4 2 SysML Parametric Diagram Toolbar 95 5 4 3 SysML Parametric Diagram Specific Features 97 5 4 4 Using Parametric Diagram Elements 98 5 5 SySML Requirement Diagrams 99 5 9 1 SySML Requirement Diagram Metamodel and Elements 100 5 5 2 SySML Requirement Diagram Toolbar 103 5 5 3 SySML Requirement Diagram Specific Features 104 5 5 4 Numbering Requirement IDs 106 5 5 5 Using SysML Requirement Diagram Elements 118 5 5 6 SySML Requirements Table 122 5 6 SysML Activity Diagrams 134 5 6 1 SysML Activity Diagram Metamodel and Elements 134 5 6 2 SysML Activity Diagram Toolbar 135 5 6 3 SysML Activity Diagram Specific Features 138 5 6 4 Using Activity Diagram Elements 144 5 7 SySML Use Case Diagrams 149 5 7 1 SySML Use Case Diagram Metamodel and Elements 150 5 7 2 SySML Use Case Diagram Toolbar 152 5 7 3 SySML Use Case Diagram Specific Features 153 5 4 Using SysML Use Case Diagram Elements 155 6 Validation 156 CONTENTS 6 1 Active Validation 161 6 1 1 Active Validation Options 164 6 2 SysML Constraints 167 7 Feature based Compartments 171 7 1 Expanding and Suppressing Feature based Compartments 172 7 2 Displaying Options in Feature based Compartments 175 8 Context Specific Value Compartments 175 8 1 Progressive Reconfiguration 175 8 2 Deep Reconfiguration 176 8 3 Context Specific Value Compartments 177 8 3 1 Advantages of Context Specific Value Compartments 177
92. Name to display the qualified names of the element types Context Specific Value Compartments Ad Properties z a Show Tagged Values On Shape Show Tagged Values Stere true Show Qualified Names For P False gt Show Default Value False Suppress Structure False Show Slot Type Symbal ID S Symbol Bounds El Suppress UML properties False Suppress references False x Tunn arce marke C Falera Show Slot Type Show slot types in default values compartment Figure 231 Symbol s Properties Dialog Show Slot Type ii Using the Part Shortcut Menu To display or hide element type s using the part shortcut menu e Right click the part to open its shortcut menu select Show Slot Type and then select a display mode Figure 232 182 Copyright 2006 2011 No Magic Inc Context Specific Value Compartments Specification Enter Symbol s Properties Alt Enter a0 To Select in Containment Tree Related Elements convert To Stereotype Aubosize Edit Compartment Show Stereotypes Show Constraints Show Oner Wrap Words Show Classifier Show Tagged Values Show Default value Show Slot Type Suppress Structure Name SysML Internal Properties Compartments Qualified Name Context Specific values Type Unspecified 0 Mone Shared Composite Figure 232 Shortcut Menu Show Slot Type 8 3 6 Value Propagation The Value Propagation mechanism e
93. Replace with a new QUDV simple unit When this suggested solution is selected a new QUDV simple unit will be created It is an InstanceSpecification whose classifier is the SimpleU nit that defined in QUDV library This instance will be applied with the lt lt unit gt gt stereotype The name and the quantity kind of the newly created QUDV simple unit will be the same as the name and the quantity kind of the obsoleted unit After create a new QUDV simple unit for replacing the obsoleted one the unit attribute of all value types which are defined with this obsoleted unit will be replaced with the new one Traceability 2 Replace with a new QUDV derived unit This suggested solution is similar to the previous suggested solution except the classifier of the created InstanceSpecification is the DerivedUnit instead of SimpleUnit 3 Replace with the selected QUDV unit This suggested solution allows you to selected the existing QUDV unit for replacing the obsoleted one Suggested solutions for obsoleted quantity 1 Replace with a new QUDV simple quantity This suggested solution will create anew QUDV simple quantity which is an InstanceSpecification whose classifier is the SimpleQuantity that defined in QUDV library This instance will be applied with the lt lt quantity gt gt stereotype The name of the new QUDV simple quantity will be the same as the name of the obsoleted quantity After create a new QUDV simple quantity the quantity kin
94. Rule in the Containment Tree you will be redirected to the broken constraint of the selected invalid element in the Containment Tree e icon Open all diagrams containing the selected element any diagram containing the selected invalid element will then be displayed e icon Solve you can either ignore the selected element which will thus not be considered in the next validation process or select one of the solutions provided to resolve the invalidity al e icon Run validation with current settings the validation process will be executed immediately using the previous setting icon Run validation with a new settings the Validation Suite Packages Selection dialog will open You can then change the settings and re validate your model again For more information on the Validation feature see the Model Analysis in the Validation section in the MagicDraw User Manual 6 1 Active Validation This feature enables you to check at once if a model is correct and complete Unlike the regular Validation fea ture in the Validation section above Active Validation will instantly display any errors in the model and suggest appropriate solutions To validate a SysML model SysML ActiveValSuite package contains six active validation suites 1 SysML_activeValSuite Activities This suite contains SysML constraints on the following elements Discrete and noBuffer 2 SysSML_activeValSuite Blocks This suite contains
95. Sort in Reports Requirements in reports will be arranged in the requirements hierarchy starting with the package that contains the selected requirements The heading section which contains sub packages and requirements will be labeled with the package name The requirements in the same level will be sorted by their ID numbers iii Anchored Elements of Requirement Notes and comments which are anchored to a selected requirement will also be shown in the generated report Comment elements will be grouped by the applied stereotype for example Rationale or Problem Report Wizard and Template lt lt requirement FuelEconony Id 2 Text The Hybrid HSL off road performance amp cargo shall have dramatically capacity conflicts with fuel better fuel economy than a EEO RENIY tipical SUW lt lt Problem Power needed for acceleration Figure 278 Fuel Economy Requirement Anchored by Problem Element 2 2 FuelEconomy The Hybrid HSUY shall have dramatically better fuel economy than atypical SU Problems Power needed for acceleration off road performance amp cargo capacity conflicts with fuel economy Figure 279 Generated Text of Problem Element in the Report An image object which is anchored to the anchored comment element of the requirement will be captured into the report document under the anchored comment element text pkg requirement Inverted Pendulum Syster E index pka ssreguirement Inverted
96. Stereotype H Edit Compartment b Show Stereotypes b Show Owner b Wrap Words Show Tagged Values b L Show Slot Type Suppress Structure SysML Internal Properties Compartments d Conkext Specific Values b Type b 2 22O Figure 67 Property Shortcut Menu to Show Default Value 2 The default value of the property will be displayed If the default value is an Instance Specifica tion the defaultValue compartment containing the Instance Specification slot s will be dis played instead Figure 68 a A or s lt block reference property Block lt lt block Eg part property Block defaultValue value property S21 reference property instance part property instance Figure 68 defaultValue Compartment b Show Slot Type Use the Show Slot Type shortcut menu to display the slot types in the defaultValue compartment of a property having an Instance Specification as its default value SysML Diagrams To display the slot types of a part 1 Right click a property and select Show Slot Type on the shortcut menu Three Show Slot Type options will be available on the shortcut menu Figure 69 i None no type slot will be displayed ii Name and ili Qualified Name Pa a a E 7 s lt block O reference property Block eT lt lt bloc x ar prone Specification Enter defau Symbolist Properties Alt Enter value prope me reference prop EN part property Refactor VEE S
97. SysML constraints on the following elements Binding Connector Block Distributed Property and Value Type 3 SysML_activeValSuite Constraint Blocks This suite contains SysML constraints on the following elements Constraint Block and Con straint Property 4 SysML_activeValSuite Non normative Extensions This suite contains SysML constraints on the following elements nonStreaming Streaming Design Constraint Functional Requirement Interface Requirement and Performance Require ment 5 SysSML_activeValSuite Port and Flows This suite contains SysML constraints on the following elements Flow Port Flow Property Flow Specification and Item Flow 6 SysML_activeValSuite Requirements This suite contains SysML constraints on the following elements Copy Requirement and Test Case To turn on the Active Validation feature 1 Click Analyze gt Validation gt Enable Active Validation making sure that Enable Active Vali dation is selected Figure 209 The Active Validation engine will validate in real time the model Validation you are working on whenever the need arises for example when a project is loaded or an ele ment of a model changed Model Visualizer Metrics Compare Projects Dependency Matrix b Validation Validation Validation Options Active Validation Options Enable Active validation Figure 209 Enable Active Validation Menu The following example a simple S
98. Validation Ld Validation Validation Validation Suite Diagram Merge UML Standard Profile MagicDraw Profile Merge nadae ra Fy Diagram Merge UML Standard Profile MagicDraw Profile Merge Orphaned Proxies UML Standard Frofile validation Profile Minimal Severity Parameters Synchronization UML Standard Profile Validation Profile ET Fy Relations Ownership UML Standard Profile validation Profile Fa Shape Ownership UML Standard Profile alidation Profile Spelling UML Standard Profile alidation Profile me SYSML ValSuite MD Customization for SysMbli SysML constraints E SysML ValSuibe Activities MD Customization For SysMLi SysML qSysML YalSuite Figure 202 validation Suite Package Selection To limit the scope of the constraints to be validated against select another smaller vali dation suite for example SysML ValSuite Blocks to validate against the constraints in OMG SysML specifications chapter 8 Blocks This is useful because generally a user has a limited scope of concerns Business Analysts for example only concern themselves with Requirements thus SysML ValSuite Requirements should be cho sen 4 In the Validate For drop down list select either e Whole Project to validate the entire SysML project Figure 203 or e Validation Selection to validate only specific elements in that SysML project Figure 203 a Validation Ed Validation Validation Suite Fa Sy sML Y
99. Value T E Time Modelingbomain Auk Real k Value Te Pal Vel eladelinalincrnasine i karnie sli Tur sa IIli Figure 28 Selecting Type to Instantiate You cannot select any property typed by an Abstract Class or an Interface You must first use the drop down list to change the type of the instance specification to be created for that property 32 5 For any selected property you can also directly assign the value to the slot by using Value property in the Instantiated properties table For the value properties you can type the value into table directly Figure 29 For the complex structure you can selected the existing instance specification to be the instance value Moreover any value specification can be created and assigned to be slot value of selected property by right click on the cell Value in the table then the context menu for edit delete and create a various type of value specification will be popped up Figure 30 Copyright 2006 2011 No Magic Inc SysML Diagrams p Automatic instantiation Wizard 1 Select parts El InternalCombustionEngine H5UY Model HSU Structure 2 Select a package P tertl HSUYModel HSUY Structure InternalCombustionEngine CA Fi HSUVModel sHSUY Structure FuelInjector 4 HSUVModel sHSUY Structure Inkeri CA fil HSUVModel sHSUY Structure FuelInjector HSUVModel HSUY Structure Interna CH Fi2 HSUYModel sHSUY Structure FuelInjector HSUvModel sHSU
100. Y Structure Fuel HSUYModel HSUY Structure Interne CA fuelReturn HSU Model HSUY Structure Fuel HSU Model HSU Structure Intern CA fuelSupply HSUVModels sHSUY Structure Fuel HSY Model sHSUY Structure Intern Ca iceEfficiency SysML Profile Blocks Real HSUVModel HSUY Structure InternalCom be PP 4 1CEFuelFitting HSUYModel HSUY Structure HSUY Interfaces FuelFlow HSUVMode ka gt Crews rah Cr ee Figure 25 Automatic Instantiation Wizard Step 1 Select Parts Copyright 2006 2011 No Magic Inc SysML Diagrams The Automatic Instantiation Wizard dialog contains three steps i Select parts ii Select a package and iii Select a diagram Figure 25 2 In Step 1 Select parts select a check box in front of a property to assign the value of the slot representing the property with instance specifications or values In other words if the property has no default value and has a type assigned an instance specification of the assigned type will be created and assigned as the value of the slot representing the property 3 The slot for the property with multiplicity greater than 1 0 4 1 5 can contain more than one instance value You can add more instance values to the slot of this property by right click ing the property and select Add parallel part Figure 26 A new node with the index of the instance value to be created will
101. Y Structure Interna CA fia HSUVModel HSUY Structure FuelInjector HSUvModel sHSUY Structure Interna Cel Fid HSUVModel sHSUY Structure sFuelInjector HSUVModel HSUY Structure Interna P p HSUYModel HSU Structure HSU Interfaces FS_ICE HSUyvModel HSU Struc fr HSUY Model sHSUY Structure FuelRegulator HSUVModel HSU Structure Interr Ce fra HSUYModel HSU Structure FuelRail HSUYModel HSUY Structure InternalCon ft HSUY Model sHSUY Structure FuelTankassembly HSUYModel sHSUY Structure Ir P fuelFitting HSUYModel sHSUY Structure Fuel HSUYModel HSUY Structure Interne fuelReturn HSUYModel HSU Structure Fuel HSUYModel HSU Structure Intern Cel fuelSupply HSUYModel HSU Structure Fuel HSUVModel sHSUY Structure Interne 3 Select a diagram Select part s properbyis to be instantiated You can change type of the selected part ho another subby pe using the drop down list box below the tree A part with an abstract type cannot be selected unless changing its type to one of the subtype of the abstract type Default values iF existed will be used new instance will not be created For a park with default value press SHIFT and click to a mig iceEfficiency SysML Profile Blocks Real HSU Model HSU Structure InternalCorr select recursively ie J HICEFuelFitting HSUYModel HSU Structure HSUY Interfaces FuelFlow HSUWVMode M mi gt Instantiate
102. addtion to including their supplier types and names client types and names as in Type A also displays the Allocation names Figure 293 Allocation Table Allocated From Source Allocated To Target a1 ProportionPower Call Behavior Action peu a2 ProvideGasPower Call Behavior Action a3 ControlElectricPower Call Behavior Action a4 ProvideElectncPower Call Behavior Action Figure 293 Example of Allocation Table B Report 12 3 3 Allocation Table Type C This table differs from Type A and B in that it shows allocate dependencies with their properties in another format that in addtion to including their names and their supplier types and names client types and names as in Type A and B also display their client and supplier type icons Figure 294 You can further customize a report by opting whether to include information from the model or not It is optional to include element documentation and empty sections Model Library for Quantities Units Dimensions and Values QUDV Allocation Table Name Allocated From Source Allocated To Target ame pegu O OOOO O OO a1 ProportionPower a2 ProvideGasPower a3 ControlElectricPower a4 ProvideElectricPower Figure 294 Example of Allocation Table C Report 13 Model Library for Quantities Units Dimensions and Values QUDV SysML specifications v 1 2 define the model of the quantities units and dimensions quantity kind in the Annex C
103. al a port flow port should be defined in a BDD However you can also create a flow port on a part in an IBD by using the IBD toolbar button 82 Copyright 2006 2011 No Magic Inc SysML Diagrams To create a flow port on a part 1 Click the Flow Port button either e on the IBD toolbar or e in the smart manipulator of the part Figure 104 ri ia lt lt block Parti koi From Pon Figure 104 Part Smart Manipulator Flow Port 2 If you click the Flow Port button on the IBD toolbar select a part where the flow port will be cre ated Figure 105 If you clicked the smart manipulator of the part go directly to step 3 ibd Block Block Fa Block zsblock partia part a part4a Block lt lt block partib Block3 s lt block part3a part4da Block Figure 105 Flow Port Created on a Part 3 Select a port type in the Select Port Type dialog Figure 106 The flow port will then be cre ated having an inout direction SysML Diagrams Ad Select Port Type lt none gt B E Data E Relations H EA ME Customization For SysML ME customization For 5 HEA UML Standard Profile UML Standard Profile xml Ermer SysML Profile SysML Profile mdzip EG Assembly H E Block H E Block H E Blocks H E Blocks i E Block5 H E Parti H E Part aS FE Portz eel il Figure 106 Select Port Type Dialog 4 You can change its direction using the po
104. alSuite MD Customization For SysMLi SyshL constraints w Validate For Whole Project ha Minimal r whole Project inimal Severity Validation Selection Exclude elements From read only modules Validation Options Figure 203 Validation Element Selection 5 If you have selected Validation Selection click the browse button to open the Select Ele ments dialog Add elements to to the Selected objects pane using buttons in the middle of the dialog Figure 204 Only the element s listed in the Selected objects pane will then be vali dated Figure 204 When all required elements are selected click OK 158 Copyright 2006 2011 No Magic Inc Validation LAW Select Elements Selected objects Selected objects H E HSU Model FA matrix templates me EBA MD Customization Fou HI ModelingDomain Ep UML Standard Protile A sample profile a SYSML Profile SysML y Uselase Description E editor E SysML1 0 E test Aa Fine m Cancel Figure 204 Select Elements Dialog 6 Click the Validate button in the Validation dialog Figure 203 once elements have been selected to be validated When the validation process is completed the results of the validation will be displayed in the Validation Results window usually located at the bottom of the MagicDraw window Figure 205 e Mark Exclude elements from read only modules to ignore the elements in read only modu
105. amodel and Elements bdd Model Data aa Requirement metamodel o Metachss Class Le sssterectype Requirement Class i LE s lt sterestype gt gt extendedRequirement Class A LF Lu Lil FH ssstereotype lt lt sterectype gt gt lt sterectype gt lt lt sterectype gt performanceRequirement usabilityRequirement interfaceRequirement physicalRequirement Class Class Class Class LE C LF ssstereotype lt lt sterectype gt gt businessRequirement designConstraint Class Class lt lt stereclype gt gt functionalRequirement Class Figure 130 Requirement Metamodel Icon Description Requirement SysML Cs A Requirement specifies a capability or a condition that must or should be satisfied Requirements are used to establish a contract between the customer or other stake holders and those responsible for designing and implementing the system A require ment can also appear on other diagrams to show its relationship to other modeling elements Extended Requirement SysML C An Extended Requirement adds some properties to the requirement element These properties are important for requirement management Specific projects should add their own properties Functional Requirement SysML Cf A Functional Requirement is a requirement that specifies a behavior that a system or part of a system must perform Interface Requirement SysML
106. an have objects or data passing along 4 it An object flow models the flow of values to or from the object nodes SHIFT F Control Flow UML A Control Flow is an edge that starts an activity node after the previous one is EE finished Objects and data cannot pass along the control flow edge F F Send Signal Action UML A Send Signal Action is an action that creates a signal instance from its inputs gt and transmits it to the target object where it may trigger the state machine transition or the execution of an activity SHIFT S Accept Event Action UML An Accept Event Action is an action that waits for the occurrence of an event that meets the conditions specified Accept event actions handle event occur rences detected by the object owning the behavior E Time Event UML A Time Event specifies a point of time with an expression which may be abso lute or might be relative to some other points of time SysML Diagrams Button Element hot key Initial Node UML An Initial Node is a starting point for executing an activity It has no incoming amp edges T Activity Final UML An Activity Final is a node that stops all flows in an activity Di Flow Final UML A Flow Final refers to the final node that terminates a flow and destroys all E tokens that arrive at it It has no impact on other flows in the activity Decision UML A Decision is a control node that chooses between outgoing flo
107. anguages in another viewpoint They specify the elements expected to be represented in the view that may be formally or informally defined 90 B Index A Accept Event Action 136 Action 135 Accept Event Action 136 Any Action 136 Behavior 139 Call Operation Action 135 Name Display Mode 138 Opaque Action 135 Send Signal Action 136 Active Validation 161 Options 164 SysML Constraints 167 Activity Decomposition Hierarchy Wizard 144 Activity Final 137 Activity Parameter Node 136 Actor 151 152 Actuator 151 Boundary System 151 Environmental Effect 151 External System 151 Sensor 151 User System 151 Actuator 151 Aggregation 19 Directed Aggregation 19 Any Action 136 Association 19 153 Aggregation 19 Association Block 18 Composition 19 Directed Aggregation 19 Directed Association 19 Directed Composition 19 Association Block 18 Creating an Association Block 26 Automatic Block Structure Display 73 Automatic Instantiation 28 B BDD 14 Binding Connector 95 Using Binding Connector 99 Block 14 17 Association Block 18 Constraint Block 15 Context Specific Value Compartments 175 Creating Instances 28 Display Parts 57 Display Ports 58 Displaying Structure 73 Domain 15 External 15 Feature based Compartments 171 Inserting a New SysML Diagram 23 Inserting a New SysML Property 20 Sorting properties into SysML style Compartments 23 Structured Block 17 Subsystem 15 System 15 System Context 15 Using Block 45 Boundary System 151 Brows
108. antity Kind later if necessary 5 1 7 SysML Callout Box To create a callout box showing the attributes constraints and tag values of an element 1 Either e Created an the anchored Note to the symbol of element on the diagram using the anchor button in smart manipulator or e Create Note by using the diagram toolbar and create anchor line to the symbol of element 2 Either e Click Edit compartment of anchored Note using the smart manipulator button on Note Figure 51 or e Select the context menu items in Edit Compartment menu group Figure 52 a Edit Compartment Figure 51 Edit Compartment Manipulator Button SysML Diagrams j Symbolis Properties Alt Enter block Block Aukosize HTML Text Edit Compartment o h Element Properties Show Stereotypes Constraints Text Display Mode Tagged Values Show Element Properties Show Constraints Constraint Text Mode Show Tagged Values a Wrap Words Figure 52 Edit Compartment Context Menu Group 3 The Compartment Edit dialog will pop up Figure 53 p7 Compartment Edit Element Properties Constraints Tagged Values All Se lecked isEncapsulated true allocatedFrom Element connector 1 allacatedTo porti parti Figure 53 Compartment Edit dialog 4 Select the element properties Constraints and tagged values which you want to show in the callout box Then click OK to close the dialog 5 Select Sh
109. applied to the swimlane header in order to allocate activity actions in the swimlane to the property in the header To stereotype a swimlane lt allocate gt 1 Open the Swimlane Header shortcut menu and select Allocated Activity Partition Fig ure 189 The swimlane will then be automatically stereotyped the stereotype allocate will appear as the swimlane header Figure 190 Specification Insert Swimlane b F Insert Inner Swimlane Ctr Alt I m Delete Swimlane 0 To Refactor Select in Containment Tree Related Elernents Stereokype Edit Compartment Show Tagged Values Name Display Mode Show Full Represented Element Signature Allocated Activity Partition Figure 189 Swimlane Header Shortcut Menu Allocated Activity Partition BS O Figure 190 Allocate Stereotype Applied on Swimlane Header 2 Drag a property for example partProperty BLOCK to the stereotyped swimlane header Figure 191 SysML Diagrams act Activity AllocatedActivity Fp AllocatedActivity zzalocate gt partProperty BLOCK Start Figure 191 partProperty Allocated to the Stereotyped Swimlane If you create an action for example Action in the stereotyped swimlane the action will be allocated to the property This means that e The value of the allocatedTo tag under the Allocated stereotype of the Action is partProperty Figure 192 e The value of the allocatedFrom tag under the Allocated
110. be listed under the selected property You can also remove the instance value by right clicking the node of the instance value and select Remove parallel part Figure 27 p Automatic instantiation Wizard 1 Select parts El x InternalCombustionEngine H5UModel H5U Structure 2 Select a package s P tertl HSUYModel HSUY Structure InternalCombustionEngine 1 fi HSUYModel HSU Structure Fuelinjector 4 HS 3 Select a diagram o 4dd parallel part a0 Select partis propertyts to 2 W 2 be instantiated You can o 3 change type of the selected Pi part to another subbype W 4 using the drop down list box vw fil HSUYModel sHSUY Structure FuelInjector HSUVModel HSUY Structure Interna below the tree A part with an abstract type cannot be fiz HSUVModel sHSUY Structure FuelInjector HSUYModel sHSU Structure Interna selected unless changing its M GB fi3 HSUVModel HSUY Structure FuelInjector HSUYModel HSUY Structure Interna type to one of the subtype of the abstract type Default Ce Fid HSUYModel sHSUY Structure Fuelinjector HSUYModel HSU Structure Interna values if existed will be s h Fp HSUYModel HSU Structure H5U Interfaces FS_ICE HSUVModel HSUY Struc used new instance will mot be created For a part with E fr H5UYModel HSUY Structure FuelRegulator HSUVModel HSU Structure Interr default value H
111. can be defined at a package or a top level requirement A requirement is considered to be top level only if it is directly owned by a package model or profile A requirement owned by another requirement is NOT considered as a top level requirement A top level requirement ID cannot contain any separator e The Numbering Style Prefix and Separator values defined in an upper level node package model profile will be overridden by the values defined in a lower level node package model profile top level requirement e The Data package contains the default Numbering Style Prefix and Separator values defined for your project Numbering Style Multi Levels Prefix and Separator 5 In Figure 140 the requirements in the HSUV Specification package under Data gt HSUV Model gt HSUV Requirements were renumbered Since there is no Numbering Style Prefix and Separator values defined in the HSUV Specification HSUV Requirements and HSUV Model packages the values defined in the Data package default will be used instead Num bering Style Multi Levels Prefix and Separator as shown in Figure 141 SysML Diagrams Ag Requirement ID Numbering E HSL Model bE Explanations FE HSU Analysis FES HSU Behavior HSU Requirements FES SUY Specification CA 1 Capacity CA 1 1 FuelCapacity be LA 1 2 Passengerlapacity i C 1 3 CargoLapacit
112. cks Real i C payvloadCapacity SysML Profile Blocks i C yehicleDry Weight SysML ProFile Block i C position SysML Profile Blocks Real i C IN String H E InteriorSubsystem H E InternalCombustionEngine tu Figure 244 Structure Browser Displaying Full Type of Classifiers 9 3 4 Show Applied Stereotypes in Browser Use the Show Applied Stereotypes in Browser option to show or hide the applied stereotypes of the elements in the browser 190 Copyright 2006 2011 No Magic Inc Structure Browser 9 3 5 Show Auxiliary Resources Use the Show Auxiliary Resources option to show or hide auxiliary resources e g SySML Profile in the Struc ture browser 9 3 6 Filter Use the Filter option to customize the display of elements in the Structure browser Mark the check box in front of the element you would like to display Clear the checkbox to hide the element ie ltems Filter General C Eleman f A Abstraction C i 4bstractReferenceProperty 2 F Accept Call Action C Accept Event Action 2 Action Execution Specification C Action Input Fin Activity Activity Final Mode z C Activity Parameter Node z C M Activity Partition Actor O Si actuator Add Structural Feature value Action press SHIFT and click to select recursively Select All Clear All Figure 245 Items Filter Dialog for Customizing Elements Display in Structure Browser 9 4 Additio
113. communicating with it directly For example Temperature or Humidity 1 SysML Diagrams 5 7 2 SySML Use Case Diagram Toolbar Element Actor See Section 5 7 1 for description Actuator See Section 5 7 1 for description Boundary System See Section 5 7 1 for description Environmental Effect See Section 5 7 1 for description External System See Section 5 7 1 for description Sensor See Section 5 7 1 for description User System See Section 5 7 1 for description Use Case UML A Use Case is a kind of behavior related classifier that represents a declara tion of an offered behavior Each use case specifies a particular behavior pos sibly including the variants that the subject can perform in collaboration with one or more actors The subject of a use case could be a physical system or any other element that may initiate a behavior such as a component a sub system or a class Package UML A Package is a namespace for its members and it can contain other pack ages Only packageable elements can be owned by members of a package By virtue of being a namespace a package can import either individual mem bers of other packages or all the members of other packages System Boundary UML A System Boundary is another kind of representation of a package A system boundary element consists of use cases related by Exclude or Include uses relationships which are visually located inside the system boundar
114. conomyy 2 3 OFFRoadCapability CA 2 4 Acceleration CA 2 1 Braking Figure 149 Finding requirement by name in Containment Tree NOTE This type of search cannot find an element if the element is not shown in browser when searching To find the requirement using the Find dialog e You can either select Edit gt Find in the main menu or press Ctrl F to open the Find dialog e To search for a requirement by its ID select the tab for searching element by tag value in the Find dialog In Name combo box type Id and then type the ID of the requirement into the Value combo box Click Find button Copyright 2006 2011 No Magic Inc SysML Diagrams E Search Results Search element by tag value 5 From loaded diagrams 2 Name E E From model 1 2 vale H 4 1 Cargolapacity un Type C Scope C Search in active diagram only _ Load diagrams and autoloadable modules Case sensitive Match whole words only _ Search data unused in diagrams _ Orphaned proxies only Java regular expression Clear previous results Figure 150 Finding requirement by ID using Find dialog e To search for a requirement by its name select the tab for searching element by name Type the name of requirement into the Name combo box Then click browse button after the Type text field and select the Requirement Finally click Find button 116 Copyright 2006 2011 No Magic Inc SysM
115. ct recursively El InternalCombustionEngine HSU Model HSU Structure s C P ertl HSUYModel HSUY Structure InternalCombustionEngine CA Fi HSUY Model HSU Structure Fuelinjector 4 HSUVModel HSUY Structure Inter CA fil HSUVModel sHSUY Structure FuelInjector HSUvModel HSUY Structure Interna CA Fi2 HSUYModel sHSUY Structure sFuelInjector HSUvModel HSUY Structure Interna CA f3 HSUYModel sHSUY Structure FuelInjector HSUvModel HSUY Structure Interna CA Fid HSUVModel sHSUY Structure FuelInjector HSUVModel HSUY Structure Interna P fp HSUyModel HSU Structure HSUY Interfaces FS_ICE HSUYModel HSUY Struc E fr HSU Model sHSUY Structure FuelRegulator HSUVModel HSU Structure Interr v fra HSUYModel HSU Structure FuelRail HSUYModel HSU Structure InternalCon ft HSU Model sHSUY Structure FuelTankAssembly HSUYModel sHSUY Structure Ir PP fuelFitting HSUYModel HSUY Structure Fuel HSUYModel HSUY Structure Interne Ce fuelReturn HSUYModel HSU Structure Fuel HSUVModel HSU Structure Intern CA fuelSupply HSUVModel sHSUY Structure Fuel HSUYModel sHSUY Structure Intern mB ticeEfficiency SysML Profile Blocks Real HSUYModel sHSUY Structure InternalCom wt TH TOCO alCiteien 6 OT hA A l POST Sher eb ATL Takar seai Di else PUSLA nA 1i Instantiated properties Type Value Temp ModelingDomain Automotive
116. cted parts in the IBD Figure 60 ii Display Ports Property shortcut menu If you have already defined the port s flow port s of a Block you can then display the port s flow port s on any part typed by the Block To display ports flow ports on a part on an IBD 1 You can either i select Related Elements If the type classifier of the part owns at least one port flow port the Display Ports option will be enabled for you to select Select this option Fig ure 61 or ii click the icon on the Smart Manipulator menu of the part as shown in Figure 62 Specification Enter Symbol s Properties Alt Enter a0 To b d Refactor Select in Containment Tree Related Elements b ia ar Stereotype Display Ports Edit Compartment Show Stereotypes Show Cw mer Used By CErl 4lE L Wrap words Depends On Cerl Alk 0 Show Tagged Values Figure 61 Property Shortcut Menu to Display Ports SysML Diagrams ja zeblock partib Blocks fH o g N E OSET Display Forts Figure 62 Property Smart Manipulator Menu to Display Ports 2 All ports including flow ports will then be listed in the Select Ports dialog Figure 63 3 Click OK Figure 63 to view the selected checked port s on the part symbol X Select Ports Select Ports P i Porti Block3 P o Port Block3 Figure 63 Select Ports Dialog
117. d Add Existing Delete From Table Delete Up Down Unnest Requirement Nest Requirement Report ID Numbering Show Columns Export Keyboard Shortcut Insert Ctrl on MAC Alt Insert Alt on MAC Ctrl Insert Ctrl E on MAC Delete Ctrl D Ctrl Open Bracket Ctrl Close Bracket n a n a n a n a n a n a You can either click the Add New icon on the table toolbar or press Insert Table 6 to add a new requirement which will then be automatically added to the table If you click the icon the available requirement types will be listed in the drop down menu Figure 166 If you have created your own custom requirement types they will appear under the Custom Requirements group in SysML Diagrams the menu e g myRequirement in Figure 166 Then select a requirement type that you want to create from the drop down menu A requirement of the selected type will then be created and added to the table NOTE e The owner of the newly created requirement will be similar to the owner of the table e To select a different owner hold Shift and then select a requirement type from the drop down menu The Select Owner dialog will then open enabling you to choose a different owner e If a table row is selected the requirement in that row will be selected in the Select Owner dialog automatically e f the selected owner is a requirement then you are creating a new neste
118. d Package ICE Type A St Instance of the InternalCambustionEngine lt block HSU internalCombustionEngine InternalCombustionEngine fi HSU internalCombustionEnginefi 1 HSL internalCombustionEngine fi 2 HSU internalCombustionEngine fi 3 HSL internalCombustionEngine fi 4 fil HSU internalCombustionEngine t1 fiz HSU internalCombustionEngine tle fis HSL internalCombustionEngine tis fid HSL internalCombustionEngine tl4 fra HSU internalCombustionEngine tra fTuelReturn HSL internalCombustionEngine tuelRetum TlelSupply HSLinternalCombustionEngine tuelSupply iceEfficiency lt lt block gt s lt block gt lt lt block gt HSU HSU _ HSU internalCombustionEng internalCombustionEng internalCom ine fuelReturn Fuel ine ftuelSu Fuel bustionEngi ne fil fuelPressure fuelPressure Fuellnjector pressure Yunit psi pressure unit psi dimension Pressure dimension Pressure fuelDemand temperature unit F temperature unit F dimension Temperature dimension Temperature lt lt block O zablock zablock sablock HSU HSU HSU HSU internalCom internalCom internalCom internalCom bustionEngi bustionEngi bustionEngi bustionEngi nefi ne tis nefit netii Fuelinjector Fuelinjector Fuelinjector Fuelinjector fuelDemand fuelbemand ftuelDemand fuelDemand lt bhlock gt e lt block gt eeblocks oO e lt block gt Ey HSU HSU
119. d Block SysML A Structured block is a Block element that contains an Internal Block Diagram and a hyperlink to it 17 Subsystem UML A Subsystem is treated as an abstract single unit It groups model elements by representing the behav ioral unit in a physical system 152 Subsystem A Subsystem is a typically large encapsulated block within a larger system 1 15 Swimlanes UML Swimlanes are used to organize actions and sub activities according to the class allocated to each swim lane header and partition an activity diagram 138 System Boundary UML A System Boundary is another kind of representation of a package A system boundary element consists of use cases related by Exclude or Include uses relationships which are visually located inside the system boundary rectangle 152 System Context A System context element is a virtual container that includes the entire system and its actors 1 15 System A System is an artificial artifact consisting of blocks that pursue a common goal which cannot be achieved by the system s individual elements A block can be a software hardware a person or an arbitrary unit 1 15 Test Case Activity StateMachine Interaction SysML A test case is a method for verifying a requirement 101 Time Event UML A Time Event specifies a point of time with an expression which may be absolute or might be relative to some other points of time 136 Trace UML A Trace relationship is a
120. d attribute of all value types and units which are defined with this obsoleted quantity will be replaced with the new one 2 Replace with a new QUDV derived quantity This suggested solution is similar to the previ ous suggested solution except the classifier of the created InstanceSpecification is the DerivedQuantity instead of SimpleQuantity 3 Replace with the selected QUDV quantity This suggested solution allows you to selected the existing QUDV quantity for replacing the obsoleted one Suggested solutions for value types that use obsoleted units and quantities There are two validation rules detects the value types that have defined units or quantities with the obsolted units and quantities defined in the SI Value Type Library model library one for detecting the using of obsoleted unit and another for detecting the using of obsoleted quantity When the value type is detected the following suggested solution will be provided for solving the problem 1 Replace with recommend unit This suggested solution will replace the using of the obsoleted unit which are defined in SI Value Type Library with the equivalent QUDV unit defined in SIDef inition library 2 Replace with reccomment quantity This suggested solution will replace the obsoleted quan tity with the equivalent QUDV quantity that defined in SlDefinition library 14 Traceability Traceability includes new derived properties Relation Map etc Relation Map is a very p
121. d properties Type Ca Real SysML Profile Blocks Figure 29 Assigning Value Property Aq Automatic Instantiation Wizard 1 Select parts El pe E InternalCombustionEngine HSUvModel HSUY Structure 2 Select a package 5 C P tertl HSUYModel HSUY Structure InternalCombustionEngine CA Fi HSUYModel HS5UY Structure Fuellnjector 4 HSUVModel H5UY Structure Interi CA fil HSUYModel sHSUY Structure Fuel njector HSU Model HSUY Structure Interna CA fiz HSUYModel HSY Structure Fuel njector HSUVModel HSUY Structure Interna CA fia HSUYModel sHSUY Structure Fuel njector HSUYModel HSUY Structure Interna CE P 3 Select a diagram Select partis propertyts to be instantiated ou can change type of the selected part to another subtypet using the drop down list box below the tree 4 park with an abstract type cannot be selected unless changing its type to one of the subtype of the abstract type Default values iF existed will be used new instance will not be created For 4 part with default value i HSUY Model HSU Structure Fuelinjector HSUYModel HS u Sbri hiran Tokarnia HSUModel HSUY Structure HSU Interfaces F5_ICE Pa Mee iink E fr HSUvModel HSUY Structure FuelRegulator H5UvModel d SE Duration wv fra HSUVModel sHSUY Structure FuelRail HSUYModel H5UY Duration Interval 0 f ts HSU Model HSUY Structure FuelTankAssembly HSLvMo FAD
122. d requirement If you press the buttons a requirement will be created promptly You can then change the type of the newly cre ated requirement directly in the table HSUV Requirement Table O Add New i Add Existing 4 qin Requirement Name Business Requirement Design Constraint Extended Requirement Functional Requirement Interface Requirement Performance Requirement Physical Requirement a Eee fl ee Ble Usability Requirement H myRequirement Figure 166 Requirement Type Drop Down Menu for SysML Requirements Table b Add Nested When a requirement is highlighted in the table you can either click the Add Nested icon on the table toolbar or press Alt Insert Table 6 to add a new nested requirement owned by the highlighted requirement to the table Like Add New if you click the icon the available requirement types will be listed in the drop down menu Then select a requirement type that you want to create from the drop down menu A nested requirement of the selected type will then be created being owned by the requirement highlighted in the table c Add Existing To add requirement s already existed in your model to a SysML Requirements Table 1 Click the Add Existing icon on the table toolbar or press Ctrl Insert Table 6 The Select Requirement dialog will open Figure 167 SysML Diagrams select Requirement Select search for or create elements Search for an e
123. dation Options Enable Active Validation Used Bw Depends On CErl Alk D Figure 219 Active Validation Options 2 Go to the General project options pane and select Active Validation gt Ignored validation suites Figure 218 To ignore some unused or unimportant active validation suites 1 Click the Browse L button The Select Suites dialog will open Figure 220 Aq Select Suites C E Orphaned Proxies UML Standard Profile Validation Profile Parameters Synchronization UML Standard Profile Validation Profile C Ea Shape Ownership UML Standard Profile Validation Profile F SySML_activeValSuite Activities MD Customization for SysMLi SysML constraints 5 me SysML_activevalSuite Blocks MD Customization For SysMLi SyvsML constraints Sys F SysML_activevalSuite Constraint Blocks MD Customization for SysML SysML const Fo SysML_activeValSuite Mon normative Extensions MO Customization for SysML Sys F SySML_activevalSuite Ports and Flows MO Customization For SysML SysML constr Fo SysML_activeValSuite Requirements ME Customization for SysMLiSyshL constrain Apply Clear All Figure 220 Select Suites Dialog 2 Select the check boxes in order to ignore the active validation suites and then click Apply In this example three validation suites will be excluded from the validation process Figure 220 Additional validation rules constraints can be added and grouped
124. dd Model Datal E BDC lt block lt block sblock Location Thing 3 5 sshlogk NIVEr se Uti Thing ans Location T1o oc lt block l Location lt block lt block wakes l ti Thing t2 Thing x Real 0 i i parts parts y Real 0 I Location T l Location T z Real 0 wees Ting y sal LLI t2 Thing U t2 lt lt block gt lt lt block gt l Location Location Te HAH Selsee gt wales wales x Real 0 x Real 0 y Real 0 y Real 0 e lt bloack gt g zZ Real 0 z Real 0 Li Location valves Universe Y Aj vaes iUniverse ssblock y 4 i Te Ut E Thing T ai LLI UniverseConte xt lt block gt UniverseContext lt lt block gt UC u Universe parts r u Universe UC uy tl E t2 UC ute e lt block gt u Universe lt lt block gt ES lt lt bloack UC u t1 Thing ut Thin t1 Thing Ut l l UC u ti l t2 Thing Ut2 l UC utz s block z blo ck s2block gt ti Thing t2 Thing s block a UC u t1 1 Location UC u t2 1 Location Location T l Location T lt lt block gt e lt block gt Location Location Wee wakes x Real 0 x Real 0 y Real 0 y Real 0 z Real 0 z Real 0 uC g vaes Unive re Conte rt vaines Unive se Conte rt Y ae eh Figure 227 Block Definition Diagram 8 3 3 Displaying Conte
125. dependency that provides a general purpose relationship between a requirement and any other model elements 102 Unit SysML A Unit is a particular value that can be used to specify a quantity of a dimension A unit often relies on precise and reproducible measuring techniques For example a unit of length such as meter may be specified as a multiple of a particular wavelength of light A unit can also use less stable or precise ways to express some values such as costs expressed in some currencies or a severity rating measured by a numerical scale 16 Usability Requirement MDSysML A Usability Requirement specifies the fitness for use of a system for its users and other actors 101 Usage UML A Usage is a dependency in which one element the client requires the presence of another element the supplier for its correct functioning or implementation 19 Use Case UML A Use Case is a kind of behavior related classifier that represents a declaration of an offered behavior Each use case specifies a particular behavior possibly including the variants that the subject can perform in collaboration with one or more actors The subject of a use case could be a physical system or any other element that may initiate a behavior such as a component a subsystem or a class 152 User System An User System is a special external system that serves as medium between a user and the system without having its own interests in the communication For exampl
126. e Input Device or Display 1 151 Value Pin UML A Value Pin is an input pin that provides a value to an action that does not come from an incoming object flow edge 138 Value Property MDSysML A Value Property is a property that specifies the quantitative property of its containing Block Every Value Property is typed by either a SysML Value Type or UML Data Type Value Properties are displayed in the val ues compartment 54 Value Type SysML A Value Type is a type which defines values that can be used to provide information on a system but cannot be identified as the target of any reference These values may be used to type properties operation parameters or potentially other elements within SysML 16 Verify SysML A Verfiy relationship is a dependency between a requirement and a test case or a model element that can determine whether the system fulfills the requirement As with other dependencies the arrow direction points from the cli ent test case to the supplier requirement 102 View SysML A view is a representation of a whole system from the perspective of a single viewpoint A view can only own element import package import comment and constraint elements 89 ViewPoint SysML A viewpoint is a specification of the conventions and rules for constructing and using a view for the pur pose of addressing a set of stakeholder concerns The languages and methods for specifying a view can reference methods and l
127. e 8 Select Diagrams Dialog Applying OMG SysML Style to Diagrams 12 Copyright 2006 2011 No Magic Inc SysML Diagrams 9 Select the SysML diagram s the OMG SysML style will be applied to and then press OK In the Project Options dialog press OK Applying OMG SysML style to existing SysML diagrams might distort the look of those diagrams For quick diagram look modification use the Layout feature in MagicDraw available in the main menu 4 4 Using QUDV Model Library QUDV model library is introduced in Annex C Non normative Extensions OMG SysML Specifications 1 2 This model library is designed in such a way that extensions to the ISQ and SI can be represented as well as any alternative systems of quantities and units See 13 Model Library for Quantities Units Dimensions and Values QUDV for more detail on the model library in SysML plugin 4 5 Using Quick Search Dialog To open the Quick Search dialog using a keyboard shortcut 1 Press Crtl Alt F to open the Quick Search dialog Figure 9 Type Name JP aoe j uma tart arowolocornd i ii te cosrechn WOME LEAL OY Wolo fo i Do Seo Class or Interface 2 Any Classifier Any Element Diagram Figure 9 Quick Search Dialog 2 Either i enter the name of the element or diagram sought or ii select the element or diagram from the drop down list box 3 The diagram will open or the corresponding element will open in the Conta
128. e 86 71 Copyright 2006 2011 No Magic Inc SysML Diagrams ibd Block Black Fag Block scblack gt E Partia Part2a Part4a Block5 Figure 86 IBD of Block1 and the Selected Nested Properties ibd Block Block fai Block s lt block gt Partta Part2a Part4a Block45 lt lt block gt Figure 87 Creating a New Property 4 Here is another example If a property of Block1 block part1b typed by Block3 is placed on Block of the IBD Figure 87 select the Select Nested Part button on the IBD toolbar and place it on the part1b Block3 symbol The following Select Element dialog will open Fig ure 88 SysML Diagrams ibd Block Black fa Black X Select Element lt lt hlock gt Partta Part2a Part4a BlockS BE Blocks Et CH Fart3a Block4 i CE EE EE Blocks zeblock Partib Block Figure 88 Placing the newly created Property on the IBD as a Neste Part 5 In this last example the dialog in Figure 88 shows all parts properties nested inside Block3 If part4a typed by Block5 is selected the result will be as in Figure 89 ibd Block Block1 fj Block1 zablock Partla Part a Part4a Block5 lt lt block gt Partib Block zeblock Part3a Part4a BlockS Figure 89 The Selected Nested Part Displayed As these examples show the Select Nested Part button allows you to display a deep nested part wi
129. e Font Arial 11 Specify properties For symbols of model elements Name Description Figure 187 Activity Decomposition Hierarchy Wizard Dialog Specify Symbols Properties 6 The Class Diagram will then be generated Figure 188 class HSM sarrple Decomposition of Acti ity Accelerate ProvidePow er Monitor Traction Orving ProvideGa zaag thy ity gt Accelerate pr oy idePovy er lt actwity ProvidePower 4b 34 al s lt actyity lt atti ity s lt actwity s ac thy ity Contro lEle ctricPo wer Provide GasPo wer ProportionPower Provide HectricPower zzattiy iy Ssactivity s lt ac thy ty gt Sa cth ity Monitor Traction Turn Key To On Dr ving Behavior Figure 188 Class Diagram of the Decomposed Activities SysML Diagrams Swimlane Allocations I IE An Activity Diagram or a SysML Activity Diagram can be organized using swimlanes each swimlane being separated from the neighboring ones by vertical or horizontal solid lines on both sides Swimlanes provide a view of the behaviors invoked in the activities Each swimlane must have a swimlane header assigned to a property Drag the property over the swimlane header to have the property assigned to the swimlane The Allocation relationship can provide an effective means for navigating the model by establishing cross rela tionships and ensuring the various parts of the model are properly integrated The lt allocate gt stereotype can be
130. e Specification zx ParaMagic Profile C Cee gt ret eea ree Figure 39 Automatic Instantiation Wizard Step 2 Select a package 4 In Step 3 Select a diagram type SatiInstanceO02BDD in the Type diagram name box and select BDD as the diagram type Figure 40 41 Copyright 2006 2011 No Magic Inc SysML Diagrams 42 p Automatic Instantiation Wizard O 1 Select parts O 2 Select a package 3 Select a diagram Check the Create a new diagram checkbox if wou want to create 4 new diagram to display instance specification s Check the Create link between instances checkbox iF you also want to display linkis among those instance specification s Create a new diagram Create link between instances Type diagram name SatInstanceOZBDD Select diagram type SysML Block Definition Diagram we Select owner For diagram B E Data B Satellite H H SatelliteInstanced1 SatelliteInstanced2 H E SatelliteSpecification O Control CXS heading Instruments d PowerBalance PowerSystem O Propulsion O Satellitesystem ht rest coe Cr Figure 40 Automatic Instantiation Wizard Step 3 Select a diagram 5 Click Finish The SatinstanceO2BDD diagram will be created Figure 41 Copyright 2006 2011 No Magic Inc SysML Diagrams bdd Package Satelltelnstancel2 Instance of the Satell
131. e general classifier 1 Stereotypes taken from the SYSMOD process http www sysmod de by Tim Weilkiens oose Innova tive Informatic GmbH 5 7 3 SySML Use Case Diagram Specific Features The SysML Use Case diagram specific features include i Use Case Numbering ii Use Case Dependency Matrix Template i Use Case Numbering To number the use cases in a Use Case diagram 1 Select Use Case Numbering on the diagram shortcut menu Figure 195 A Question dialog will open indicating that this feature requires UseCase Description Profile and ask if you would like to use it You can also select Use Case Numbering on e Use Case shortcut menu e Package shortcut menu SysML Diagrams Specification Diagram Properties Shift Enter Use Case Numbering j Show Diagram Info Show Diagram Frame Show Owner a0 To b Select in Containment Tree Alt E Find in Diagram Ctel 5hift E Grid b Print Active Diagram Show Diagrams in Full Screen Fil Figure 195 Use Case Diagram Shortcut Menu Numbering 2 Click Yes The Change Use Cases Numbering dialog will open Figure 196 p Change Use Cases Numbering B E HSU sample A Use Cases Use Cases Owners Eb FS HSU Model acy ee E F Behavior Operate the Vehicle E F Configuration amp Insure thevehicle F Requirements gt Register thewehicle E Structure J Maintain the Vehicle E Test 7 Uselases Es BEI H E Views H E matrix te
132. e matrix name in the Browser All func tions that can be performed with diagrams can also be performed with matrices You can open a Dependency matrix from any of the following e Diagrams main menu Figure 250 e Analyze main menu Figure 251 e Package shortcut menu in the browser Figure 252 e Custom Diagrams toolbar Figure 253 Dependency Matrix Class Diagrams Ctrl 1 Ctrl 3 Communication Diagrams Sequence Diagrams trl 4 State Machine Diagrams Ctrl 5 Protocol State Machine Diagrams Ctrl 6 Implementation Diagrams Ctrl 8 Ctrl 9 Composite Structure Diagrams Interaction Overview Diagrams Ctrl 0 _ Custom Diagrams P LS Free Form Diagrams SysML Diagrams d Time Diagrams Customize Diagram Wizards Ctrl H Alt Lett Previous Diagram Figure 250 Opening Dependency Matrix from Diagrams Main Menu Model Visualizer Metrics Compare Projects FT Create Blank Matrix Validation A Matrix Templates Display Paths Display Related Elements Used By Ctrl Alk U Depends On Ctrl Alk o Figure 251 Opening Dependency Matrix from the Analyze Main Menu Mew Element SysML Diagrams Class Diagram Open in New Tab Communication Diagram Specification Enter Sequence Diagram Use Case Numbering State Machine Diagram Protocol State Machine Diagram G0 To Relat
133. e physical system being modeled A model owns or imports all the elements needed to represent a complete physical system according to its purpose SysML Diagrams Button hot Element key View See Section 5 3 1 for description m ViewPoint See Section 5 3 1 for description Conform 7 See Section 5 3 1 for description Package Import UML A Package Import is defined as a directed relationship that identifies a pack age whose members are to be imported by a namespace Element Import UML An Element Import is defined as a directed relationship between an importing E namespace and a packageable element The name of the packageable ele ment or its alias are to be added to the namespace of the importing namespace 5 3 3 Using SysML Package Diagram Elements Package B You can display the name of a package either on top of it or on its tab To display a package name 1 Right click a package and select Header Position on the shortcut menu Figure 116 SysML Diagrams Package Name Specification Enter Symbol s Properties Alt Enter New Diagram o Go To Refactor Select in Containment Tree o Related Elements Tools Stereotype Requirement ID Numbering Edit Compartment Shi Stereotypes v show Tagged Values Show Owner Wrap Words Show Elements List Header Position r lily Figure 116 Package Shortcut Menu Header Position 2 Select either i Top t
134. ecute in case the specified excep tion occurs during the execution of the protected node 137 Expansion Region UML An Expansion Region is a structured activity region that executes multiple times corresponding to the elements of an input collection 137 Extend UML An Extend is a relationship from an extending use case to an extended use case specifying how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case The extension takes place at one or more specific extension points defined in the extended use case Choose a different Extend direction from the toolbar to draw a line with an opposite arrow end 153 Extended Requirement SysML An Extended Requirement adds some properties to the requirement element These prop erties are important for requirement management Specific projects should add their own properties 100 External System An External System is a system that interacts with the system under development For example Informa tion server or Monitoring system 1 151 External An External block is a block that represents an actor It facilitates a more detailed modeling of actors like ports or internal structures 1 15 Flow Final UML A Flow Final refers to the final node that terminates a flow and destroys all tokens that arrive at it It has no impact on other flows in the activity 137 Flow Port SysML A Flow Port is a port that specifies the input
135. ed Elements Interaction Overview Diagram Free Form Diagram Tools Stereotype Content Diagram Rename Figure 252 Opening Dependency Matrix from the Package Shortcut Menu in the Browser 196 Copyright 2006 2011 No Magic Inc Dependency Matrix Dependency Matrix Figure 253 Dependency Matrix Button on the Custom Diagram Toolbar 10 2 Working with Dependency Matrix Templates Dependency Matrix x Flow Element Type 3 Column Element Type Row Scope Column Scope Row Added Renoved Element Column Added Removed Element Dependency Criteria HE BE A Figure 254 Dependency Matrix View Matrix properties and filter configurations are stored in MagicDraw The matrix configuration is called a matrix template It is used for storing the configuration of a dependency matrix filters and matrix properties indepen dently of a project The configuration stored in a matrix template can then be used later or shared with your col leagues e To create a new matrix template it is easier for you to start with a pre defined template e The matrix template can be imported and exported as a file You can open a built in matrix template by using either i the Analyze menu in the main menu or ii the Load Matrix Template button in a dependency matrix view i To open a built in matrix using the Analyze menu on the main menu 1 Click Analyze gt Dependency Matrix gt Matrix Templat
136. ed in terms of more basic con straints such as primitive mathematical operators In general you should define constraints in constraint blocks in a Block Definition Diagram first and then use a Parametric Diagram to bind constraint parameters to properties Quantity Kind A Quantity Kind formerly Dimension in SysML 1 0 and 1 1 specifications is a kind of quantity that may be stated by means of defined units For example the quantity kind of length can be measured by units of meters kilometers or feet A The only valid use of a Quantity Kind instance is to be referenced by the quantity kind property of a Value Type or Unit stereotype Unit A Unit is a quantity in terms of which the magnitudes of other quantities that have the same quantity kind can be stated A unit often relies on precise and reproducible ways of measuring the unit For example a unit of length such as meter may be specified as a multiple of a particular wavelength of light A unit may also specify less SysML Diagrams stable or precise ways to express some value such as a cost expressed in some currency or a severity rating measured by a numerical scale aN The only valid use of a Unit instance is to be referenced by the unit property of a Value Type stereotype Value Type A Value Type is defined as a stereotype of UML Data Type to establish a more neutral term for system values that may never be given a concrete data representation A Val
137. ehavior 4 MeasurevehicleConditions HSU Model Behavior a4 ProvideclectricPower HSU Model Behavior a4 ProvideGasPower HSU Model Behavior a T Select Activities those structures will be 2 2 2 a4 Enable on Brake Pressure gt O HSL Model Behawi 1 1 0 0 0 0 0 0 decomposed a4 ProportionPower HSU Madel Behavior 4 Measurevehiclevelocity HSU Model Behawior aa Driving HSUY Model Behavior Operate Car a4 Monitor Traction HSUY Model Behavior Operate C a4 Behavior best decomposition aa Behavior test decomposition aa Turn key To On HSUY Model Behavior Operate Car KRU SOSORXOOUOU Search recursively Add contained Object Nodes Figure 186 Activity Decomposition Hierarchy Wizard Dialog Select Structure 5 Step 3 Specify symbols properties Customize the symbol properties of the diagram s to be created Figure 187 If you clicked Finish in Step 2 Step 3 will be skipped A ON SysML Diagrams p Activity Decomposition Hierarchy Wizard O 1 Specify name and package Specify symbol properties For diagram elements Association Be Aj BS EE O 2 Select structure i E 7 3 Specify symbols properties Fill Color RGB 255 255 Use Fill Color _ False Pen Color W FSE 0 0 0 Text Color E FSE 0 0 0 Font Arial 11 Line Width 1 Rounded Corn False Constraint Te Expression Stereotype Color W RGB 0 0 0 Stereotyp
138. elect a Package Ag Automatic Instantiation Wizard Create a new diagram 1 Select parts Create link between instances Select a package 2 Select k 3 Select a diagram Type diagram name Instance of the InternalCombustionEngine Select diagram type Check the Create a new diagram checkbox iF you wank fo create a new S sML Block Definition Diagram diagram to display instance specification s Select owner For diagram Check the Create link PS Do e between instances 7 B vE HSUV UseCases checkbox if you also want o B A H5UY Views to display link si among ff ModelingTips those instance E Stereotypes specitication s SysML 1 1 Specification texts B E Test H E wheel hgt Figure 33 Automatic Instantiation Wizard Step 3 Select a Diagram 8 In Step 3 Select a diagram select the Create shape on new diagram check box to create a new diagram to display instance specifications Figure 33 NOTE Select the Create link between instances check box to also create links among instances 9 Type the diagram name and select the type only static diagrams are allowed to hold instance specifications and owner select one from the tree 10 Click Finish to create the instance specifications and diagram Figure 33 The Instance spec ifications will be created and displayed in the chosen diagram Figure 34 Q Ql Copyright 2006 2011 No Magic Inc SysML Diagrams bd
139. elect in Containment Tree Alt E Related Elements Stereokype I Edit Compartment b Show Stereotypes b Show Owner Wrap Words Show Tagged Values y Show Default Value Show Slot Type w None Suppress Structure Mame SysML Internal Properties Compartments b Qualified Mame Context Specific Values Type f Figure 69 Property Shortcut Menu to Show Slot Types 2 If you select Name or Qualified Name the slot types will be displayed Figure 70 zsblock reference property BLOCK zeblock part Block defaultValue reference property BLOCK instance part property BLOCK instance value property ValueType 321 Figure 70 defaultValue Compartment with Slot Types v Provided Required Interfaces Port shortcut smart manipulator menu Provided Required Interfaces help identify compatible ports that can be connected together in an IBD On a port you can either a create a new Provided Required Interface s using the port specification dialog or SysML Diagrams b display an existing Provided Required Interface s using the port shortcut menu a Creating New Provided Required Interface s Using the Port Specification Dialog To create new Provided Required Interface s of a port 1 Either e Right click a port to open its shortcut menu and then select Specification to open the Specification dialog Then select the Provided Required Interfaces gro
140. elements in the diagrams Figure 274 Requirements Figure 16 3 Requirements Derivation Safety Test Description none req a Figure 165 hipiai Deri Sate Tes anepi ASTM RIFI idea MHT id i5 Toei Tha road en Surface produces of peak Waking COoOeTICIEn of paved auflaces Pras Le Lies an Amenta Soria ae Toging and reference leet bre biondina with ASTM Mathgd E radia fpg 1337 60 i 3r oe Text a ET 5 E 140 Fh 100 Cel Fi fh Tepi punere PFC i dl bel pg Figure 1 Figure 16 3 Requirement Derivation Safety Test List of Requirement m A SABER AST R 1337 90 S0 2 1 Pavement fiction S7 42 Vehicle conditons S 4 Adhesion utlizaton Si 4 3 Test and procedure conditons A 242417 ASTM R1337 90 Text This test method cowers the measurement of peak braking coetident Figure 274 Example of Requirement Diagram Report 12 2 2 Requirement Table Type A Use this report template to generate basic SysML Requirement reports in a tabular format Each table shows the requirements with their properties including the requirement ID Name and Text Figure 275 This table shows only the requirements with their properties including the requirement ID requirement name and requirement text Report Wizard and Template Requirement Table D Name Te gt o E E i OOOSOSOSSCCSCSCSCSSSSSTSOCOCTCSCSCSCSCS EZ 242 47 ASTM R1337 90 T
141. em for typing the value properties in your SysML model These value types are using the units and quantity kinds defined in the QUDV model library Table 8 New SI Value Type Library QUDV based ampere SimpleUnit electricCurrentQK SimpleQuantityKind Am amperePerMeter DerivedUnit magneticFieldStrength DerivedQuantityKind A m amperePerSquareMeter Derive currentDensity DerivedQuantityKind dUnit Ba becquerel DerivedUnit radionuclideActivity DerivedQuantityKind coulomb DerivedUnit electricChargeQK DerivedQuantityKind ed candela SimpleUnit luminousIntensityQK SimpleQuantityKind cd m candelaPerSquareMeter Derive luminance DerivedQuantityKind dUnit F farad DerivedUnit capacitance DerivedQuantityKind Hey Deventer Hef Doresu owe Deea energyQK DerivedQuantityKind kevin Sicint __emodanenpoeCKSeOaGa et ebenei Cac Deresan tg Nba Spt ras Sree im uve Doveint eu FANOK Dereden DR Deine ao Deer m meter SimpleUnit lengthQK SimpleQuantityKind meterPerSecond DerivedUnit velocityQK DerivedQuantityKind meterPerSecondSquared Derive accelerationQK DerivedQuantityKind dUnit mol mole SimpleUnit amountOfSubstanceQK SimpleQuantityKind molePerCubicMeter DerivedUnit amountOfSubstanceConcentration DerivedQuantity Kind m squareMeter DerivedUnit areaQK DerivedQuantityKind moo cubicMeter DerivedUnit m reciprocaleter DerivedUrit waveNumber k Dervedavan
142. ement dialog Figure 167 click e OK to add all requirements in the Selected elements pane to the table or e Cancel to cancel the operation d Delete From Table To remove requirement s from a SysML Requirements Table 1 Select the row s of the requirement s you want to remove 2 Click the Delete From Table icon on the table toolbar or press Delete Table 6 3 The selected requirement s will then be removed from the table NOTE Requirement s removed from the table still exist s in your model To remove requirements from your project see Section e Delete below SysML Diagrams e Delete To remove requirement s from your model 1 Select the row s of requirement s you want to remove 2 Click the Delete icon on the table toolbar or press Ctrl D Table 6 3 The selected requirement s will then be removed from the table and from your project f Up To move the selected row of requirement up either click the Up icon on the table toolbar or press Ctrl Open Bracket Table 6 g Down To move the selected row of requirement down either click the Down icon on the table toolbar or press Ctrl Close Bracket Table 6 h Unnest Requirement When a nested requirement is selected in the Requirements Table you can click the Unnest Requirement to move the selected requirement to be owned by the owner of the current one The requirement s id will be changed accordingly Unnest Requirement also suppo
143. endulum is stable when hanging downwards a vertical inverted pendulum is inherently unstable and must be actively balanced in order to remain upright typically by moving the cart horizontally as part of a feedback system The inverted pendulum is a classic problem in dynamics and control theory and widely used as benchmark for testing control algorithms Pendulum Computer Molor Tendon Mechanism Figurel nverted Pendulum System Image Figure 281 Generated Report with Generated Image Object iv Appendix A for Captured Diagram Images If the elements generated in the document have hyperlinks to diagrams the diagrams will be captured and given in Appendix A Diagrams Report Wizard and Template hybrid sport utility vehicle Date July 15 2009 Requirement Report Revision 1 0 Appendix A Diagram Figure B 12 Establishing Derived Requirements and Rationale from Lowest Tier of Reqquirements Hierarchy rag Package HEUY Recreate E Fiia 5 12 Establishing Derived Reiremanls and Falidnal trom Liwest Tier of Regguirenents Hierarci 1 E afre Seah ere Index Figure B 15 saigi man Braking ae fag Lr oaMeris Booeieratrn fats speien Hen Al EE a a arag Lireient s requirement _ftoadCapabity a te y sy Mae sy J ceperiveRect zener eRe EEE NENEIE RENET l i f Tey i F ao s sader Ragi i osdinjveftegt secerheRedes
144. enerated in the document is a requirement element a hyperlink for navigating to the section that contains the information of the related requirement in Appendix A will be created In the appendix if the requirement has an active hyperlink to the diagram the hyperlink text will be generated and will navigate to the captured image of the diagram in Appendix B of the document 12 2 7 Requirements Table Diagram Report Use the Requirements Table Diagram template to generate a requirement report document in the tabular style of the SysML Requirements Table diagram The generated table will consist of 8 columns a ID Report Wizard and Template f Risk g Source and h Verify Method Requirements in the table will be sorted by the requirement ID This template will be used to generate require ment reports from the Requirements Table diagrams hybrid sport utility vehide Tabular Requirements Diagram Report Date July 15 2009 Revision Revision 1 0 Name Requrement Type T Eco Friendiness meguikamart MHSUY Specification HS Ut Model sHSUy Requirements Emissions The vehicle shall meet Utra Requirement lows Emissions vehicle standards O Eco Friendinezs HSU Model H504 Requirements HSUy Specification z CA Performance The Hybrid SUW shall hawe the Performance feo ge braking acceleration and off Requirement con orbit i road capability of a typical a ae SUV but have dramatically Requirements better fuel econ
145. eotype applied and returns false otherwise A Glossary Accept Event Action UML An Accept Event Action is an action that waits for the occurrence of an event that meets the conditions specified Accept event actions handle event occurrences detected by the object owning the behavior 136 Action UML An action is a named element that is the fundamental unit of an executable functionality The execution of an action represents some transformations or processing in the modeled system When the action is to be executed or what its actual inputs are is determined by the concrete action and the behaviors in which it is used 135 Activity Final UML An Activity Final is a node that stops all flows in an activity 137 Activity Parameter Node UML An Activity Parameter Node is an object node for inputs and outputs to the activities The Activity parameters are object nodes at the beginning and end of the flows to accept inputs to an activity and provide out puts from it 136 Actor UML Actors represent roles played by human users external hardware and other subjects An actor does not nec essarily represent a specific physical entity but merely a particular facet i e the role of some entities that are relevant to the specifications of its associated use cases 151 Actuator An Actuator is a special external system that influences the environment of the system under development For example Heater assembly or Central locking system of
146. equirement and its subtypes only method to verify a requirement See Table 4 for more information SysML Diagrams The Hybrid SUV shall have the braking acceleration and off road capability of a typical SUV but have dramatically better fuel economy The Hybrid SUV shall have the acceleration of a typical SUV S sls ta oo b Ea ae E E a Ee a RENGEN 3 a zgje 22 g I t i 5 ra i Figure 158 SySML Requirements Table i Creating a SysML Requirements Table You can create a SysML Requirements Table using the a main toolbar b main menu or c Containment Tree a To create a SysML Requirements Table using the main toolbar 1 Click the SysML Requirements Table icon on the main toolbar Figure 159 The Create Dia gram dialog will open Figure 160 Figure 159 Main Toolbar 123 Copyright 2006 2011 No Magic Inc SysML Diagrams P Create Diagram Create a new SysML Requirements Table Type diagram name and select package in which a new diagram will be created Type SysML Requirements Table name FP HSUYModel HER MD Customization For SysML MD customization For E E ModelingDomain HER QUBY Library MD customization For SyshLomdzip BEA UML Standard Profile UML Standard Profile xml H EA Matrix Templates Profile Matrix Templates Profile H EA SysML Profile SysML Profile mdzip E ER UML Profile For Schedulabilty Performance and Time 4ssaciation HsUvModel
147. er Structure Browser 186 Business Requirement 101 C Call Operation Action 135 Select Operation 140 Component Subsystem 152 Composition 19 Directed Composition 19 Conditional Node 137 Conform 90 Connector 56 95 96 Binding Connector 95 Constraint Block 15 Display Parameters 97 Objective Function 94 Using Constraint Block 46 98 Constraint Parameter Binding Connector 95 Constraint Property 54 95 Display Parameters 97 Objective Function 94 Context Specific Value Compartments 175 Value Propagation 183 Control Flow 136 Copy 102 Using Copy 122 D Data Store 136 Data Type 17 Enumeration 17 Quantity Kind 16 Unit 16 Value Type 16 Decision 137 Dependency Matrix 195 SysML Dependency Matrices 197 SysML Allocation Matrix 197 SysML Editable Matrices 198 SysML Allocation Matrix 198 SysML Satisfy Requirement Matrix 199 SysML Verify __Requirement Matrix 200 SysML Refine_Requirement Matrix 198 SysML Satisfy Requirement Matrix 198 SysML Verify_Requirement Matrix 198 Use Case 155 Derive 102 Using Derive 121 Design Constraint 101 diagrams 13 14 53 88 93 99 134 149 sysml 13 SysML Activity Diagram 134 SysML Block Definition Diagram 14 SysML Internal Block Diagram 53 SysML Package Diagram 88 SysML Parametric Diagram 93 SysML Requirement Diagram 99 SysML Use Case Diagram 149 Directed Aggregation 19 Directed Association 19 Directed Composition 19 Distributed Property 55 96 Domain 15 Using Domain 45 Dynamic Centerlines 141
148. er indirectly has G the features of the general classifier Usage UML A Usage is a dependency in which one element the client requires the pres N ence of another element the supplier for its correct functioning or implementa tion U 1 Stereotypes taken from the SYSMOD process http www sysmod de by Tim Weilkiens OOSE SysML Diagrams 5 1 3 SysML BDD Specific Features SySML BDD specific features includes i Inserting a New SysML Property Using One of the Block Menus ii Inserting a New SysML Diagram Using the Block Shortcut Menu iii SysML Style Compartments iv Creating an Association Block OU A v Creating a SysML Internal Block Diagram Using the Smart Manipulator Button i Inserting a New SysML Property Using One of the Block Menus You can create a new SysML property from the a Block shortcut menu Figure 14 b Block Smart Manipulator menu Figure 15 and 16 a To create a new SysML property using the Block shortcut menu 1 Right click a block and select Insert New SysML Property from the shortcut menu Figure 14 2 Select a SysML property that will be created 3 Enter the name of the newly created property SysML Diagrams Specification Enter Syrmibal s Properties Alt Enter Mew Diagram 0 To Refactor Select in Containment Tree Select in Structure Tree Select in Inheritance Tree Stereotype Aubosize Edit Compartment Presentation Options SysML Compartments
149. erface s sterectypes gt ConstraintBlock a Class Figure 12 Flow Specification Metamodel Figure 11 Constraint Block Metamodel Description Constraint Block SysML Constraint Blocks provide a mechanism to integrate engineering analysis such as per formance and reliability models with other SysML models Constraint Blocks can be used to specify a network of constraints representing mathematical expressions which constrain the physical properties of a system Constraint Blocks are generally defined in Block Definition Diagrams and then used in Parametric diagrams SysML Diagrams Icon Description Flow Specification SysML A Flow Specification specifies inputs and outputs that can flow through a port in terms of Flow properties Flow Specifications are used by Flow Ports to specify what items can flow via those ports Interface UML a An Interface specifies operations or signals If an Interface is provided to a port the external parts may call operations or send signals to the Block owning the port via that port If an Interface is required for a port the Block owning the port may call operations or send signals to its environment via that port bdd Model Data ah YalueType ametaclhass DataType ametaclass InstanceSpeciication Lo Lu Lal gmetaclassy Stereotypes stereotypes stereotypes Enumeration ValueType Unit QuantityKind DataType DataType Instancespecitication
150. ering Dialog 3 In the Requirements pane select the requirement s Use the Edit Create Remove Increase Decrease or Renumber button to number the selected requirements IDs N nanpvyriaht 2006 2011 No Maaie Ine U 7 C O p y I j g I l ZU U O E U II V O M a g IC 5 I C j tw w SysML Diagrams These five buttons are used to add edit remove the IDs of the requirements directly owned by the package or the requirement of interest Selected in the browser on the left hand side of the Requirement ID Numbering dialog only Button Edit Create Remove Increase Decrease Renumber Table 3 Requirement ID Numbering Buttons Multiple Enable Criteria Selection Support N Enabled when select a requirement with non empty ID Y Create button is enabled when all selected requirement s has have no ID s Otherwise Remove but ton is enabled Y Enabled when all selected require ment s has have ID s b Enabled when all selected require ment s has have ID s n a Always enabled Function To arbitrarily number the ID of a requirement To assign or unassign ID s to the selected requirement s To increase the ID s of the selected requirement s by one To decrease the ID s of the selected requirement s by one To renumber all the requirements appeared in the Requirements pane on the right hand side of the Requirement ID Numbering dialog starting from 1
151. es eValueTy pes Real dwalue Typex unit yard Quantity Kind GDY Librar SIDefinitions length k emodelLibrary s SIDefinitions Units eliuantity Kind yard lengthQk fquantityKind lengthQk Figure 296 Value Type with the New Unit and the Existing QuantityKind in S Definiton Model Library 13 3 3 3 Create a new Value Type using new Unit and Quantity Kind 1 Create a new Quantity Kind from the diagram toolbar of Block Definition Diagram 2 Create a new Unit from the diagram toolbar of Block Definition Diagram Then assign the Quantity Kind in step 1 to the newly create Unit 3 Create a new Value Type and specify the unit and quantity kind attributes with the Unit and Quantity Kind from step 2 and step 1 respectively Model Library for Quantities Units Dimensions and Values QUDV allie pes m s vwalye Type Unit Go CubicMeterFerSecond Quantity Kind Tips and Tricks WYalue Type Unit and QuantitvEind twith QUDV FlowRate Units elivantity Kinds CubicMeterPerSecond FlowRate IquantityKind FlowF ate Figure 297 Value Type with the New Unit and QuantityKind 13 3 3 4 Create a new ValueType which is specialized the Quantity value type in QUDV 1 Create a new ValueType with one of the steps described above without any generalization rela tionship 2 Make the newly created ValueType to be specialized of the Quantity by creating a generaliza tion relationship from the newly created Va
152. es on the main menu The Depen dency Matrix Templates dialog will open 2 Select a built in matrix template and then click OK ii To open a built in matrix using the Load Matrix Template button in a dependency matrix view 1 You must have a dependency matrix open 2 Click the Load Matrix Template button in the dependency matrix view The Load Matrix Template dialog will open 3 Select a built in matrix template and then click OK SysML Plugin provides four different dependency matrix templates e SysML Allocation Matrix template This template is used for creating a matrix to show Allocation dependencies between clients in rows and suppliers in columns Allocations can be used early in a design as precursors to more Dependency Matrix detailed rigorous specifications and implementations Allocation dependencies provide effective means for navigating your model by establishing cross relationships and ensuring the various parts of your model are properly integrated SysML Refine_Requirement Matrix template This template is used for creating a matrix to show Refine dependencies describing how a model element or a set of elements refine a requirement For example a use case or activity diagram may be used to refine a text based functional requirement Alternatively it may be used to show how a text based requirement refines a model element In this case some elabo rated text could be used to refine a less fine g
153. est HSUv Model Test Specification Eco Friendiness Acceleration HSUVModel HSUV Requirements HSUV 4 amp 3 Max Acceleration HSUV Model HSU Requirements Specification Perfor mance B3 Max Acceleration HSU VModel HSUY Requirements Figure 289 Verify Table 224 Copyright 2006 2011 No Magic Inc Report Wizard and Template ii Appendix for Requirements Text Table All requirements shown in the table of requriement dependencies will be given in the requirement table in Appendix A Requirement The table will contain text that describes each requirement hybrid sport utility vehicle Requirement Dependencies Report Date July 16 2005 Revision Reviion 1 0 Appendix A Requirement Text Table Mame Text EG ht Emissions The vehicle shell mest Lt low Emissions vehicle senders vehicle shall meet Utr slow Emissions vehicle standards O pes a SUY but have cramatically better fuel econo my 21 fE Baa The The Hybrid SUV shall have the braking capability ofa typical SUW SUY shall have the braking capability of atypical SUW C Gr ee ee C D acl C e a ic ak Corfidertial No Magic Inc T Figure 290 Appendix A Requirement Text Table iii Appendix for Captured Diagram Images If the elements generated in the document have hyperlinks to the diagrams the diagrams will be captured and given in Appendix B Diagrams iv Hyperlinks in Generated Reports If the text of a related element g
154. ew item flow or on the existing item flow by dragging a classifier and dropping it to the connector or association The dropped classifier will be a conveyed classifier of the item flow 5 3 SysML Package Diagrams Package diagrams typically enable you to organize models by partitioning model elements into packageable elements and establishing dependencies between packages and or model elements within these packages Since Package diagrams are used to organize models in packages and views they can include a wide array of packageable elements A package is a construct that enables you to organize model elements such as use cases or classes into groups Packages define namespaces for packageable elements Model elements from one package can be imported and or accessed by another package This organizational principle is intended to help establish unique naming of the model elements and avoid overloading a particular model element s name Packages can also be shown on Block Definition diagrams or Requirements diagrams SysML Diagrams 5 3 1 SysML Package Diagram Metamodel and Elements bdd Model Data ea view Metalocdel lt Metaclass gt Package Pa s lt sterectypes gt View Package Figure 113 View Metamodel Icon Description Package UML Fy A package is a namespace for its members and it can contain other packages Only packageable elements can be owned by members of a package By virtue of being a namespace
155. ex physical path depicting a set of parts ports and connec tors Binding Connector SysML A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values If the properties at both ends of a binding connector are typed by DataTypes or ValueTypes it means that the instances of the properties at both ends must hold equal values recursively through any nested properties within the connected properties If the properties at both ends of a binding connector are typed by Blocks it means that the instances of the properties must refer to the same block instance As with any connector owned by a SysML Block each end of a binding con nector may be nested within a multi level path of properties accessible from the owning Block The NestedConnectorEnd stereotype is used to represent such nested ends just as for nested ends of other SysML connectors 5 4 2 SysML Parametric Diagram Toolbar Button Element hot key Value Property MDSysML A Value Property is a property that specifies a quantitative property of its con taining Block Every Value Property is typed by either a SysML Value Type or Lu UML Data Type Value Properties are displayed in the values compartment Part Property MDSysML A Part Property is a property that specifies a part with strong ownership and coincidental lifetime of its containing Block It describes a local usage or role t of the typing Block in the co
156. flow in out of the Block part or what services the block part requires expects from or provides offers to its environment Ports are connected by connectors to other parts or other ports 18 Quantity Kind SysML A Quantity Kind in SysML 1 0 and 1 1 called Dimension is a kind of quantity that can be mea sured using defined and unrestricted units of measurement For example length a quantity kind may be measured by meter kilometer or foot units 16 Reference Property MDSysML A Reference Property is a property that specifies a reference of its containing Block to another Block Every Reference Property has none AggregationKind and is typed by a block Reference Properties are dis played in the references compartment 54 Refine UML A Refine relationship is a dependency intended to describe how a model element or a set of elements are used to further refine a requirement Alternatively it can be used to show how a text based requirement refines a model ele ment 103 Requirement SysML A Requirement specifies a capability or a condition that must or should be satisfied Requirements are used to establish a contract between the customer or other stakeholders and those responsible for designing and implementing the system A requirement can also appear on other diagrams to show its relationship to other modeling ele ments 100 Satisfy SysML A Satisfy relationship is a dependency between a requirement a
157. gram So To Interaction Overview Diagram HE SysML Requirements Table Related Elements Custom Diagrams a S5SysML Sequence Diagram Tools aysML Matrices Sal SysML State Machine Diagram Stereotype Re S sML Use Case Diagram Rename Figure 164 Creating SysML Requirements Table Using Containment Tree 2 Click New Diagram gt SysML Diagrams gt SysML Requirements Table Figure 164 3 Type in the name for the SysML Requirements Table in the Containment Tree and then press Enter a ia P E 7 WAAC ANAA Nias NAiana min la m F IIN DAN 111 NI lanin aia C O p y TiQ nt ZUUO0 ZUTT INO M agic INC J J J A SysML Diagrams ii SysML Requirements Table Toolbar D add New RR Add Nested 2 Add Existing EG Delete From Table fi Delete 7 Up 4 Down dim Unnest Requirement Fis Nest Requirement Report ID Numbering jh Show Columns Export Figure 165 SysML Requirements Table Toolbar The SysML Requirements table toolbar Figure 165 is located on the main toolbar There are 13 Requirements table icons on the Requirements table toolbar a Add New b Add Nested c Add Existing d Delete From Table e Delete f Up g Down h Unnest Requirement i Nest Requirement j Report k ID Numbering m Export and 1 Show Columns SysML Diagrams Icon ak ok ok gt E ah ok ok gt a8 a Add New Table 6 SysML Requirements Table Toolbar Icons Name Add New Add Neste
158. gram Chrl ShiFk Activity Decomposition Hierarchy Wizard Grid Figure 184 Activity Decomposition Hierarchy Wizard Shortcut Menu 2 Follow the three steps in the Activity Decomposition Hierarchy Wizard dialog Figure 185 3 Step 1 Specify name and package Enter the name type SysML BDD or Class Diagram and select or create the owner of the diagram to be created Figure 185 p Activity Decomposition Hierarchy Wizard Type diagram name Decomposition of Activity pActivityNameg Select diagram type Class Diagram T Type diagram name and choose or create Laer lia a the package that will contain the created EysML Block Definition Diagram diagram 1 Specify name and package O 2 Select structure ESgHSL sample pan EAI HSU Model a EER matrix templates matrix _btermplates module mdzip EEA MD Customization For SysML MD customization for SysML mdzip H A ModelingDomain Ep UML Standard Profile UML_Standard_Profile xml sample profile Ep SysML Profile SysML Profile mdzip E editor E SysML1 0 a best H EE tips Figure 185 Activity Decomposition Hierarchy Wizard Dialog Specify Name and Package 4 Step 2 Select structure Select the activities to be decomposed e Mark the activity ies to be decomposed Figure 186 R Anr rpcy bl Cc NAL 9N44 Nir n ANINA lnn 145 Copyright 2006 2011 No Magic Inc SysML Diagrams e Select Add all structures into one diagram to add all
159. guages currently used by system engineers the same way Unified Modeling Language UML is used in the software industry to unify the modeling languages used by software engineers SysML supports the specifications analysis designs verifications and validations of a broad range of complex systems In addition to supporting all SysML diagrams Block Definition Internal Block Package Parametric Require ment Activity and Use Case diagrams SysML Plugin also makes it possible for MagicDraw to support addi tional specifications analysis designs and validations on a broader range of systems and system integrations SysML sample projects are available in the lt md install dir gt samples SysML directory 2 Installation To install SysML Plugin either i follow the manual installation instructions if you have already downloaded the plugin or ii use Resource Plugin Manager in MagicDraw to download and install the plugin i To install SysML Plugin following the manual installation instructions on all platforms 1 Download the SysML_Plugin_ lt version number gt zip file 2 Exit the MagicDraw application currently running 3 Extract the content of SysML_Plugin_ lt version number gt zip file to the directory where your MagicDraw is installed i e lt md install dir gt 4 Restart the MagicDraw application ii To install SysML Plugin using Resource Plugin Manager 1 Click Help gt Resource Plugin Manager on t
160. he MagicDraw main menu The Resource Plugin Manager will appear and prompt you to check for available updates and new resources Click Check for Updates gt Check NOTE Specify HTTP Proxy Settings for connection to start MagicDraw updates and resources 2 Select the SysML Plugin check box and click Download Install 3 Restart the MagicDraw application 3 System Engineer Perspective In keeping with SysML unifying purpose the System Engineer perspective was created to unify the diverse modeling languages currently used by system engineers All the features dedicated to SysML are accessible What you will have to do to access the System Engineer perspective depends on whether you are i launching MagicDraw for the first time after SysML Plugin has been installed or System Engineer Perspective ii switching to the System Engineer perspective from any other perspectives i If you are launching MagicDraw for the first time 1 The following message dialog will open Figure 1 2 Click Yes to switch to the System Engineer perspective supporting SysML diagrams Question SYSML plugin has been successfully installed Take a look at SyvsML diagram samples located in the samples SysML Folder To start working with a SysML model create a project From the SysML template File Wew Project SySML diagrams are accessible From the System Engineer perspective Options gt Perspectives
161. heir values A typical use of Data Types would be to represent the primitive types of the programming language used For example integer and string types are often treated as data types 17 Decision UML A Decision is a control node that chooses between outgoing flows A decision node has one incoming edge and multiple outgoing activity edges 137 Derive SysML A Derive relationship is a dependency between two requirements a derived requirement and a source requirement where the derived requirement is generated or inferred from the source requirement 102 Design Constraint SysML A Design Constraint is a requirement that specifies a constraint on the implementation of a sys tem or on part of it 101 Directed Aggregation UML A Directed Aggregation is a one direction Aggregation relationship which references from a Block aggregate to another Block component part thus creating one Shared Property typed by the component part in the aggregate The aggregation value of the target end of a Directed Aggregation is shared 19 Directed Association UML A Directed Association is a one direction Association which references from a Block to another Block thus creating one Reference Property typed by the target Block in the source end The aggregation value of the tar get end of a Directed Association is none 19 Directed Composition UML A Directed Composition is a one direction Composition relations
162. her subkype using the drop down list box below the tree 4 park with an abstract type selected unless changing its type to one of the subtype of the abstract t values iF exis used new ins created For a default value press SHIFT and click to select recursively El x E InternalCormbustionEngine H5Uy Model HSU Structure Ca fil propertyis to d You can Prrrrrery cannot be ype Default ted will be tance will not be part with Type Value CA fiz Co fia Fi4 P p r fra C ft HSUY Model HSUY Structure KSU Model HSUY Structure HSUvModel HSU Structure HSUvModel HSU Structure HSU Model HSU Structure HSUvModel HSU Structure HSU Model HSU Structure HSUYModel HSU Structure Instantiated properties ba P tertl HSUYModel HSUY Structure InternalCombustionEngine CA Fi HSUY Model sHSUY Structure Fuellnjector 4 HSUVModel sHSUY Structure Inter FuelInjector HSUVModel HSU Structure Interna FuelInjector HSUYModel sHSUY Structure Interna FuelInjector HSU Model sHSUY Structure Interna FuelInjector HSUVModel HSU Structure Interna HSU Interfaces FS_ICE HSUVModel HSUY Struc FuelRegquiator HSUYModel sHSUY Structure Interr FuelR ail H50 Model HSU Structure InternalCon FuelTankassembly HSUYModel sHSUY Structure Ir PP fuelFitting HSUYModel HSU
163. hip which references from a Block composite to another Block composite part thus creating one Part Property typed by the composite part in the composite The aggregation value of the target end of a Directed Composition is composite 19 Distributed Property SysML A Distributed Property is a property of a Block or a Value Type used to apply a probability dis tribution to the values of the property Specific distributions can be defined by applying a subclass of the DistributedProperty stereotype to the property 55 Domain A Domain block represents an entity a concept a location or a person from the real world domain A domain block is part of the system knowledge 1 15 Element Import UML An Element Import is defined as a directed relationship between an importing namespace and a packageable element The name of the packageable element or its alias are to be added to the namespace of the importing namespace 91 Enumeration UML An Enumeration is a kind of Data Type whose instances may be any of the user predefined enumera tion literals It is possible to extend the set of applicable enumeration literals to other packages or profiles 17 Environmental Effect An Environmental Effect is an influence on the system from the environment without communicating with it directly For example Temperature or Humidity 1 151 Exception Handler UML An Exception Handler is an element that specifies a body to ex
164. his test method covers the measurement of peak braking coefficient of paved surfaces using a Standard reference test tire SRTT as described In specification E1136 that represents current technology passenger car radial ties SS E 1 eapacity SOiCOOSOSOSOSOSOSOCOOCOCSCSCSC Ss SSSSSSCSCSCSCSC i E i eargoCapacty OSOSCSCSSC SC CSSSSSSOSSCSCS ____ eargoCapacty OO ______ ecoFriendiness OOOO _____ EcoFriendiness OOSOSOSOCCSCSSSTTC S R1 2 1 Emissions The vehicle shall meet Ultra Low Emissions Wehicle standards Emissions The vehicle shall meet Ultra Low Emissions Vehicle standards Figure 275 Example of Requirement Table A Report 12 2 3 Requirement Table Type B Use this report template to generate SysML Requirement reports in another specific tabular format Each table shows the requirements and their dependency relationships with other requirements Figure 276 This table is similar to the one in OMG SysML specifications Requirement Table ID Name Relation_ Supplier Name Supplier Type OOO Acceleration O O fDerveRe Power o Acceleration S DeriveRegt Power E E Maclean o Acceleration Reine Accelerate Acceleration Verify MaxAcceleration Pavement friction RegenerativeBraking Power Range FuelEconamy Range sl Eo S FuelEconamy Reg enerativeBraking E _____ FuelEconamy PowerSourceManagement Sata 55 4 1a LossOfFluid m Part Property
165. i f ia Serequiremert Regenerative br ak ling J lt P Ober Power needed tor acceleration offtosd perionmance amp cargo capaciy conficta wih fuel eToro Refined B A HSU Operational States xiereehente is ocftestionsle s Poseg dakan must Pamper Ei Ta A carequiremanl dinsted control of gas end sleti Power Source Management SANA of gas end slectic motors Seat Hye Degn udare Figure B 12 Establishing Derived Requirements and Rationale from Lowest Tier of Regquirements Hierarchy Figure 282 Sample of Appendix A Diagrams v Hyperlinks in Generated Reports If the text of related elements generated in the document is a requirement element a hyperlink will be created for navigating to the section that contains the information of the related requirement For a non requirement ele ment that has an active hyperlink to a diagram a hyperlink text will be generated for the element and will navi gate to the captured image of the diagram in the appendix As for the generated text of an hyperlink that links to a diagram the diagram will be captured as an image and given in the appendix of the generated document Then the hyperlink text is then generated to navigate to the captured image of the diagram 12 2 5 Coverage Analysis This report lists the elements for coverage analysis at higher and lower levels of abstraction Coverage analysis is indicated by traceability properties pointing to higher level of abs
166. icDraw SysML Actor subtypes metamodel SysML Diagrams Icon Description Actor UML Actors represent roles played by human users external hardware and other subjects An actor does not necessarily represent a specific physical entity but merely a particu lar facet i e the role of some entities that are relevant to the specifications of its associated use cases External System An External System is a system that interacts with the system under development For example Information server or Monitoring system 1 Sensor A Sensor is a special external system that forwards information from the environment to the system under development For example Temperature sensor 1 Boundary System A Boundary System is a special external system that serves as medium between another system and the system under development without having its own interests in the communication For example Bus system or Communication system 1 User System An User System is a special external system that serves as medium between a user and the system without having its own interests in the communication For example Input Device or Display 1 Actuator An Actuator is a special external system that influences the environment of the system under development For example Heater assembly or Central locking system of a car 1 Environmental Effect An Environmental Effect is an influence on the system from the environment without
167. ideGas Figure 266 Dependency List Dialog 206 Copyright 2006 2011 No Magic Inc Teamwork 11 Teamwork 11 1 Working with Teamwork Project MagicDraw Teamwork Server allows you to work simultaneously on the same project a teamwork project using multiple workstations Teamwork Server also provides you with a user access control mechanism together with versioning ability Once a teamwork project is stored on Teamwork Server it can be shared with multiple MagicDraw applications at the same time e To use Teamwork Server with MagicDraw SysML the Teamwork Server version must be the same as the MagicDraw version e To be able to completely work with a teamwork project you must obtain a permission either System level Edit model permission or Project level Edit model permission for that project To work with a Teamwork project 1 Select Login on the Teamwork main menu to log in to Teamwork Server Figure 267 Teamwork Ctrl ShiFk L Figure 267 TeamWork Main Menu 2 Enter your Username Password and the Teamwork Server name IPaddress portNumber or just IPaddress if the port number is 1100 default in the Login dialog 3 Create or open a Teamwork project 4 Lock for edit elements before editing or deleting them 5 Commit the changed project Before committing a project select the locked elements to com mit the change The elements that are committed will be automatically
168. ies Code Engineering ig Code Generation Lan Reverse i Java Language Options id C Language Options i a Ca Language Options i CORBA IDL 3 0 language opt i DDL Language Options project options ai General a BZ El Modules path Enable dot notation for associations Change ownership of non navigable assa Qualified name display style Suto synchronize Parameters and Argum EMF UML output location Validation scope Exclude elements From read only modules Mark in tree and diagrams Ignored validation suites Minimal severity El Propagate SysML Values Enable Auto Requirement s ID Numbering lt project dir gt lt install root gt profiles lt install root gt modelLibraries False true Absolute true Data true true Parameters Synchronization UML Standarc A warning UML Standard Profile Validatia False true Enable Auto Requirement s ID Numbering Enable 4uto Requirement s ID Numbering Cancel Reset to Defaults Figure 144 Automatic Requirement Numbering in Project Options Dialog 2 Under the SysML group make sure that the Enable Auto Requirement s ID Numbering option is selected selecting the check box means true Figure 144 3 The IDs of any newly created requirements will now be numbered automatically with the Num bering Style Prefix and Separator which are defined in the requirement owner Automatic Numbering will NOT modify any existi
169. igure 287 Satisfy Table e Trace Table The Trace table shows requirements and the elements to which they trace The requirements in this table will be sorted by the requirement ID in the first column There are three columns in this table a ID b Name and c Traced To respectively e a ID This column shows the ID of the requirement which is the supplier of the Trace dependency e b Name This column shows the name of the requirement the supplier of the Trace dependency e c Traced To This column shows the elements to which the requirement is traced the client of the Trace dependency Traced To Acceleration HSUV Model HSUY Requirements HSUY Specification Performance E Power HSUYModel HSUY Structure Figure 288 Trace Table f Verify Table The verify table shows the requirements and the elements which verify them The requirements in this table will be sorted by the requirement ID There are three columns in this table a ID b Name and c Verified By respectively e a ID This column shows thelD of the requirement which is the supplier of the Verify dependency e b Name The column shows the name of the requirement the supplier of the Verify dependency e c Verified By The column shows the elements which verify the requirement the client of the Verify dependency Verify Yerified By Emissions HSUYModel HSUY Requirements HSUY l T EAPFuelEconomyT
170. ill be performed through systematic exercising of the applicable item under appropriate conditions with instrumentation to measure the required parameters and the collection analysis and evaluation of quantitative data to show that the measured parameters are equal to or exceed the spec ified requirements A The type of return parameter Direction return of a Test Case element must be VerdictKind an enumer ation Requirement Relationships Pu F inconclusive error Figure 157 VerdictKind Enumeration Derive Relationship Dependency As with other dependencies the arrow direction points from the derived client requirement to the supplier requirement from which it is derived D The supplier and the client of a Derive dependency must be requirement elements or requirement subtype elements 2 3 Satisfy Relationship Dependency A The supplier must be a requirement element or one requirement subtype SysML Diagrams AN Copy Relationship Dependency A Copy dependency created between two requirements maintains a master slave relationship between the two elements for the purpose of requirements reuse in different contexts When a Copy dependency exists between two requirements the requirement text of the client requirement is a copy of the requirement text of the requirement at the supplier end of the dependency AN The supplier and the client of a Copy dependency must be requirement elements or
171. in your model e g C When clicking the small orange button the block smartmanipu lator menu Figure 15 will not be displayed unless you save and restart your project first bdd Model Data Untitled1 stereotypes a D Block oD adome F rl Class isEncapsulated Boolean 0 1 J x Insert SyshiL Property astereotypes CustomBlock Class SysML Diagrams ii Inserting a New SysML Diagram Using the Block Shortcut Menu To create a SysML diagram to be owned by a Block 1 Right click a block and select New Diagram from the shortcut menu 2 Select one of the diagrams in the expanded sub menu Figure 17 E block Specification Enter Block Symbol s Properties Alt En nter m New Diagram HI ga SysML Internal Block Diagram Go To b Ea SysML Parametric Diagram Refactor T SysML Activity Diagram Select in Containment Tree Alt E T SysML State Machine Diagram Select in Structure Tree Sy sML Sequence Diagram Select in Inheritance Tree SysML Block Definition Diagram Related Elements b Tools Stereotype b Aubosize Edit Compartment Presentation Options a Figure 17 Inserting SysML Diagram from the Shortcut Menu iii SysML Style Compartments SYSML specifications allow Blocks to have multiple compartments SysML plugin provides five independent collpasible block compartments i e parts references values constraints
172. inferred from the source requirement Copy SysML A Copy relationship is a dependency between a supplier requirement master and a client requirement slave specifying that the client requirement text is a read only copy of the supplier requirement text SysML Diagrams 5 5 2 SysML Requirement Diagram Toolbar Button hot key Requirement See Section 5 5 1 for description Extended Requirement See Section 5 5 1 for description Business Requirement See Section 5 5 1 for description Usability Requirement See Section 5 5 1 for description Functional Requirement See Section 5 5 1 for description Interface Requirement See Section 5 5 1 for description Performance Requirement See Section 5 5 1 for description Physical Requirement See Section 5 5 1 for description Design Constraint See Section 5 5 1 for description 4 es x CF eT 7M Satisfy See Section 5 5 1 for description Derive See Section 5 5 1 for description Copy See Section 5 5 1 for description Trace See Section 5 5 1 for description Verify See Section 5 5 1 for description Refine UML A Refine relationship is a dependency intended to describe how a model ele ment or a set of elements are used to further refine a requirement Alterna tively it can be used to show how a text based requirement refines a model element 103 Copyright 2006 2011 No Magic Inc SysML Diagrams Button Element
173. inment Tree 5 SysML Diagrams SysML Plugin supports the following SysML diagrams e SysML Block Definition Diagrams BDD e SysML Internal Block Diagrams IBD e SysML Package Diagrams e SysML Parametric Diagrams e SysML Requirement Diagrams e SysML Activity Diagrams e SysML Use Case Diagrams SysML Diagrams e SysML Sequence Diagrams similar to UML s one e SysML StateMachine Diagrams similar to UML s one For more information on how to work with SysML diagrams see the Working with Diagrams section in the MagicDraw User Manual 5 1 SysML Block Definition Diagrams BDD A Block Definition Diagram defines the features of a block and any relationships between blocks such as asso ciations generalizations and dependencies in terms of properties operations and relationships for example a system hierarchy or a system classification tree Block Definition Diagrams are based on UML class diagrams and include restrictions and extensions as defined by SysML They are generally used to display systems of blocks or show a system dictionary and or extensions 5 1 1 SysML BDD Metamodel and Elements bdd Model Data Ei Block definition diagram zsmetaclazs Class gt Block Eg s lt sterectypes lt lt stereotype gt a a a Subsystem Domain System External System context Class Class Class Class Class Figure 10 Block Element and MagicDraw SysML Block Subtypes Metamodel Icon
174. install root gt modelLibraries 5 Select QUDV model library 6 To also use SI Definitions SI Specializations and or SI Value Type Library model library ies repeat step 2 to 4 Then select the required model library 13 2 2 Replacing Modifying Existing Value Types Next you should substitute your existing Value Types with ones from the SI Value Type Library model library If any Value Type is missing from the SI Value Type Library model library you can either i create a new Value Type by following the instructions in Section 13 3 3 Creating New Value Type or ii modify the existing Value Type in your project by modifying its unit and quantity kind to be consistent with QUDV specification see Section 13 2 3 Model Library for Quantities Units Dimensions and Values QUDV 13 2 3 Modifying Units and Quantity Kinds of Existing Value Types Since SysML plugin version 16 6 units and quantity kinds base classes can be either DataType standard style or InstanceSpecification QUDV style To adopt QUDV in your SysML project user defined units and quantity kinds should be changed from DataType to InstanceSpecification To do that you must replace each existing unit and quantity kind defined as a DataType with a new one defined as an InstanceSpecification See section 13 3 2 Creating New Unit and 13 3 1 Creating New Quantity Kind on how to create a new Instanc eSpecification based unit and quantity kind respectively
175. into an active valida tion suite in a newly created one or in an existing one For more information on the Active Validation feature see the Model Analysis in the Validation section in the MagicDraw User Manual 166 Copyright 2006 2011 No Magic Inc Validation 6 2 SysML Constraints SysML constraints implementation for SysML validation suites and active validation suites include Constraint Binding Connector Block Block Block BlockProperty ValueProperty DistributedProperty Value Type ValueType FlowPort Constraint Description Directly Derived Description excerpts have been taken from the OMG specified from OMG SysML Specifications 1 2 with permission in OMG SysML SysML spec spec The two ends of a Binding Connector must 8 3 2 1 have either the same type or types that are compatible so that equality of their values can be defined Within an instance of a SysML Block the 8 3 2 2 instances of properties with composite aggre gation must form an acyclic graph Any classifier which specializes a Block must 8 3 2 2 also have the Block stereotype applied If isEncapsulated of a block is true then the 8 3 2 2 block is treated as a black box A part typed by this black box can only be connected to its ports or directly to its outer boundary The block s properties must be applied with the matching stereotype e Part property which is the property that is typed by Bl
176. ints UML properties and opera tions compartments 7 1 Expanding and Suppressing Feature based Compartments You can expand or suppress feature based compartments using either i the Symbols Properties dialog or ii the property shortcut menu i Using the Symbol s Properties Dialog of an Internal Property To expand or suppress a feature based compartment s using the Symbol s Properties dialog 1 Either right click the property symbol and select Symbol s Properties Figure 222 or select the property and press Alt Enter The Properties dialog will open E zsblock a bo i Specification Enter stress Stresa Symbol s Properties Alt Enter cubes Cube a0 To cylinders Cyl Refactor b balls Ball 0 Select in Containment Tree Alt B Related Elements b depth m 1 height m 1 Stereotype b width m 1 0 R TT Tn y Edit Compartment b YoIE Volum Show Stereotypes Heststressr Show Owner I Wrap Words Figure 222 Symbol s Properties Shortcut Menu Feature based Compartments 2 The symbol properties for expanding or suppressing feature based compartments will be listed under SysML Internal Properties Compartments Figure 223 Ad Pro perties Suppress properties Suppress references Suppress iparts Suppress values Suppress constraints Suppress operations Context Specific Yalues Apply Style Default Make Default Figure 223 Symbol s Properties Dialog SysML
177. irement unless stated differently by the compound requirement itself is that all its sub requirements must be satisfied for the compound requirement to be satisfied Subrequirements can be accessed through the nestedClassifier property of a class When a requirement nests other requirements all the nested requirements apply as part of the container requirement the requirement that contains all the nested requirements Deleting the container requirement will thus delete all the nested requirements it contains a functionality inherited from UML b Showing Requirement Tagged Values Use Show Tagged Values to select a displaying mode for a text and ID requirements either displaying them on shapes in compartments or not displaying them at all To select one of the displaying modes 1 Right click a requirement and select Presentation Options gt Show Tagged Values The 3 displaying modes will appear Figure 154 SysML Diagrams pisextendedrequirement gt Specification Enter Symbolis Properties Alt Enter Mew Diagram j Go To Refactor Select in Containment Tree Related Elements Stereotype Requirement ID Numbering Edit Compartment Presentation Options b s Show Stereotypes Show Owner wrap words Show Tagged Values a On Shape Show Members Tn Compartment Suppress Attributes ka Dio Mot Display Create Instance Risk verify Method
178. irement Dependencies template can generate six tables a Copy Table b Derive Table c Refine Table d Satisfy Table e Trace Table f Verify Table a Copy Table The Copy table shows the requirement and its master requirement The table consists of three columns a ID b Name and c Master respectively Requirements in this table will be sorted by the requirement ID e a ID This column shows the requirement ID of the copied requirement which is the client of the Copy dependency e b Name This column shows the name of the copied requirement the client of the Copy dependency e c Master This column shows the requirement that is the supplier of the Copy dependency Master CopiedPerformance HSUVModel HSUY Cl 2 Performance HSUYModel HSUY Requirements HSUY Specification Requirements Copied Requirements Figure 284 Copy Table b Derive Table The Derive table shows the relationship between the requirements that are related and the deriveReqt depen dency There are three columns in this table a ID b Name and c Derived From respectively Require ments in this table will be sorted by the requirement ID e a ID This column shows the requirement ID of the derived requirement which is the client of the deriveReqt dependency e b Name This column shows the name of the derived requirement the client of the deriveReqt dependency e c Derived From This column shows the
179. iteBDD Specification Enter Symbol s Properties Alk Enter New Diagram Go To Refactor Select in Containment Tree Select in Inheritance Tree Related Elements Tools Stereotype Aubosize Edit Compartment Presentation Options Make Sub Tree Make Generalization Set Tree Insert New UML Property Insert New SysML Property d Insert New Operation Ctrl alk a Figure 37 Create Instance Shortcut Menu 2 In Step 1 Select parts select the required properties as shown in Figure 38 and set the value for each value property of the instantiate classifier Click Next Copyright 2006 2011 No Magic Inc SysML Diagrams 40 p Automatic instantiation Wizard 1 Select parts O 2 Select a package 3 Select a diagram Select part s propertyis to be instantiated You can change type of the selected part ho another subkypet using the drop down list box below the tree A part with an abstract type cannot be selected unless changing its type to one of the subtype of the abstract type Default values iF existed will be used new instance will not be created For a park with default value ipress SHIFT and click to select recursively po El Satellitesystem Satellite Conl Satellite Control Satellite SatelliteSystem Cal Pron SysML Profile Blocks Real Satellite Control Value 2000 Cal Wicon SysML Profile Blocks Real Satellite Control Value 400
180. iw Suppress Operations P Suppress Signal Receptions Signal Receptions Sort Mode Suppress Structure Suppress Ports Forts Sort Mode Figure 154 Displaying Mode of text and ID 2 Select one of the displaying modes The result is shown in Figure 155 esextendedRequirement scextendedRequirement ISO 9000 ISO 9000 ld 4 Id scextendedRequirement sis Tai Gute Text Text ofthe ee equirement requirement On shape In compartment Do not display Figure 155 Different Displays of Requirement Elements c Creating Your Own Requirement Type Subtype You can define an additional requirement type by creating a new stereotype that generalizes the requirement stereotype Figure 156 SysML Diagrams bdd Model Data St Additional Requirement subtype i LJ LF cstereotypes gt Requirement Class i s lt sterectypes gt Hew Requirement Class Figure 156 New Requirement Type Requirement Subtypes A A Functional Requirement L is satisfied by an operation or a behavior A An Interface Requirement L is satisfied by a port connector item flow and or a constraint property A A Performance Requirement is satisfied by a value property A A Physical Requirement is satisfied by a structural element A A Design Constraint L is satisfied by a block or a part The following table provides the definitions of the non normative enumerations that are
181. l Block Diagrams SysML Package Diagrams S SML Parametric Diagrams sys Diagrams CS El imal Ehl Load All Diagrams S SML Requirements Diagrams SysML Requirements Table Es SysML Sequence Diagrams SysML State Machine Diagrams SysML Use Case Diagrams Figure 162 Creating SysML Requirements Table Using Main Menu SysML Diagrams SySML Requirements Tables SysML Requirements Tables 7 R I ke Create anew SysML Requirements Table Open a samana diagram by choosing it from the list of SysML namana Requirements Tables available within a project Owner me HSUVModel HSUY Reguireme Figure 163 SySML Requirements Table Dialog 2 Click the Add button The Create Diagram dialog Figure 160 will open 3 Type in the name for the SysML Requirements Table to be created and select its owner in the element tree Figure 160 4 Click OK c To create a SysML Requirements table using the Containment Tree 1 Right click the element which will be the owner of the SysML Requirements table in the Con tainment Tree SysML Activity Diagram Class Diagram Sy sML Block Definition Diagram Communication Diagram SvsML Internal Block Diagram Specification Protocol State Machine Diagram SyvsML Package Diagram Use Case Numbering Ja Implementation Diagram SvsML Parametric Diagram Requirement ID Numbering Composite Structure Diagram SysML Requirements Dia
182. lass Of pacthode s lt sterectype gt csosterectypes gt c lt sterectypes gt Optional Rate Probability Parameter ActivitvEdge Objectlode Parameter ActivitvEdge ParameterSet c lt sterectypes gt c lt sterectypes gt Discrete Continuous ActivityEdge ObjectNode Parameter ActivityEdge Objecthode Parameter Figure 174 Rate Optional Probability Discrete and Continuous Metamodel Icon Description Object Node UML An Object Node is an abstract activity node that is part of defining object flow in an activity Object nodes can be used in a variety of ways depending on where objects are flowing from and to 5 6 2 SysML Activity Diagram Toolbar Element Action UML An action is a named element that is the fundamental unit of an executable functionality The execution of an action represents some transformations or processing in the modeled system When the action is to be executed or what its actual inputs are is determined by the concrete action and the behaviors in which it is used Call Operation Action UML A Call Operation Action is an action that transmits an operation call request to the target object where it may cause the invocation of the associated behav ior The argument values of the action are available to the execution of the invoked behavior Opaque Action UML An Opaque Action is an action that introduces discipline to implement specific actions or to be used as a temporary
183. lay Figure 241 Structure Browser Plain List Display 9 3 2 Show Inherited Structure The Structure browser can show the properties that are inherited from the generalization classifier bdd Model Data E eeblock Block lt bloack gt block gt lt bhlack gt e lt block BodySubsystem BrakeSubsystem ElectricMotorGenerator Figure 242 Four Specialization Classifiers of Blocks 189 Copyright 2006 2011 No Magic Inc Structure Browser o BodySubsystem LO 58 ID AS BrakeSubsystern LO 5 ID d chassisSubsystem LG 5N 1 ID AS ElectricMotorSenerator E C generatorEfficiency Real E C motorEfficiency Real E 5N ID Ae 3 Hybrids H CH oe E CA b Body Subsystem E CE pi Pee ale GF r PChassieSuihsvstenm r Figure 243 Inherited Structures of Blocks 9 3 3 Show Full Type in Browser You can also see the full type of the classifiers that type the properties of the classifier in the Structure browser 0 BodySubsystem Erake5ubsystem H E ChassisSubsystem H E ElectricMotorGenerator aoe Hy bridsu E CA l HSU Model Tesk LightingSubsyster E CA b H5UY Model Test Body Subsystem E CE p H5UY Model Testy PowerSubsysterr E CE c H5UY Model Test ChassisSubsyste E CE i H5UY Model Testy InkeriorSubsysten EH CA bk H5UY Model Test Brake5ubsysten i C mpg S sML Frofile Blo
184. lay options 9 3 1 Display as Plain List 9 3 2 Show Inherited Structure 9 3 3 Show Full Type in Browser 9 3 5 Show Auxiliary Resources 9 3 6 Filter OE m m A 9 3 4 Show Applied Stereotypes in Browser 9 3 1 Display as Plain List The classifiers of structure in your model will be normally displayed in a Package Model or Profile hierarchy Use the Display as Plain List option to show all classifiers of the structure in the model in the same level with Structure Browser out consideration of their owner When you select the Display in Plain List option the classifiers will be sorted by their name EA p i Y rE Body Subsystem eE BrakeSubsystem H E ChassisSubsystem wE ElectricMotorGenerator H A Hybrids pL InteriorSubsystem fg InternalCombustionEngine E LightingSubsystern H E PowerSubsystem O Transmission l EJ AccelerationEquation O Accelerator E SeroDragEquation H E AutomotiveDomain nE Baggage LJ BalanceWeight l O BatteryPack H E Block nE Body Subsystem Bassey B 63 Data EPS HSUvModel H Explanations H E HSU Analysis H E HSU Behavior ARPS HSU Requirements El HSU Structure H E HSUY Interfaces E Accelerator E E AutomotiveDomain J BatteryPack E Eody Subsystem E BrakePedal AG Brake Subsystem E CAN_Bus AS Chassissubsysterm E Differential L E ElecPower H E ElectricalPowerController we Figure 240 Structure Browser Normal Disp
185. le Type A 214 12 2 3 Requirement Table Type B 215 12 2 4 Requirement Report 216 12 2 5 Coverage Analysis 220 4 Copyright 2006 2011 No Magic Inc CONTENTS 12 2 6 Requirement Dependencies Report 221 12 2 7 Requirements Table Diagram Report 225 12 3 Allocation Report Templates 226 12 3 1 Allocation Table Type A 227 12 3 2 Allocation Table Type B 227 12 3 3 Allocation Table Type C 227 13 Model Library for Quantities Units Dimensions and Values QUDV 228 13 1 QUDV Model Library in SysML Plugin 228 13 1 1 QUDV 228 13 1 2 SI Definitions 228 13 1 3 SI Specializations 228 13 1 4 SI Value Type Library 229 13 2 Migrating Existing SysML Project To Use QUDV Model Library 230 13 2 1 Using QUDV Model Library in SysML Project 230 13 2 2 Replacing Modifying Existing Value Types 230 13 2 3 Modifying Units and Quantity Kinds of Existing Value Types 231 13 3 Creating New Quantity Kind Unit or Value Type in QUDV Library 231 13 3 1 Creating New Quantity Kind 231 13 3 2 Creating New Unit 232 13 3 3 Creating New Value Type 232 13 4 Validation Rules for Detecting the Using of Obsoleted Units and Quantities 234 14 Traceability 235 15 Open API 236 15 1 Stereotype Usage 236 15 1 1 SysML Profile 236 15 1 2 MD Customization for SysML Profile 236 A Glossary 238 B Index 245 5 Copyright 2006 2011 No Magic Inc SYSML PLUGIN FOR MAGICDRAW 1 Introduction Systems Modeling Language SysML is designed to unify the diverse modeling lan
186. le given an element Elem SysMLProfile isBlock Elem returns True if the element Elem has lt lt Block gt gt stereotype applied and returns false otherwise 15 1 2 MD Customization for SysML Profile You need to import com nomagic magicdraw sysml util MDCustomizationForSysMLProfile to use this API class Open API a Get a string constant for each property of stereotype tag Usage includes MDCustomizationForSysMLProfile S7EREOTYPE_PROPERTY_NAME For example MDCustomizationForSysMLProfile NUMBEROWNER_PREFIX_PROPERTY returns a string of prefix b Get a stereotype element Usage includes e MDCustomizationForSysMLProfile getInstance project getStereotype where project refers to the project which uses MD Customization for SysML Profile e MDCustomizationForSysMLProfile getInstance element getStereotype where element refers to the element in the project which uses MD Customization for SysML Profile For example MDCustomizationForSysMLProfile getInstance project getPartProperty returns the reference to the lt lt PartProperty gt gt stereotype object c Check if an element is stereotyped Usage includes MDCustomizationForSysMLProfile sStereotype amp Elem where Elem is the element you would like to check For example given an element Elem MDCustomizationForSysMLProfile isValueProperty Elem returns True if the element Elem has lt lt ValueProperty gt gt ster
187. lement by using list or tree views To find an element type text or wildcard inte Search by name input field Search elements by their qualified names or use camel case when searching if the appropriate mode is enabled Search by name Selected elements ype text or wildcard 7 to search CE 4 2 FuelCapar Es Tree E List r i a BE BS BS 18 matches found Elf Data 2 matches EF HSUY Specification 74 maiohes Add Rect Remove en Remove ia 7 maies Ill CA 4 2 FuelCapacity c PassengerCapacity iH 4 1 Cargolapacity E CA Eco Friendiness J ma o i CH Ergonomics H Ce Qualification 2 ma o HSUVModel sHSUY Requirements 18 ma ohes f Add Figure 167 Select Requirement Dialog Add Existing Requirements to Table r i 2 Select the requirement element s which you want to add to the table e Use the Add button in Figure 167 to add a requirement selected in the element tree to the Selected elements pane e Use the Add Recursively button in Figure 167 to add all requirements listed under the requirement selected in the element tree and the selected requirement itself to the Selected elements pane e Use the Remove button in Figure 167 to remove the selected requirement from the Selected elements pane e Use the Remove All button in Figure 167 to remove all requirements from the Selected elements pane 3 In the Select Requir
188. les between actors Actors are connected to use cases through communication paths each represented by a relationship There are four use case relationships i communication ii include iii extend and iv generalization i Communication A communication path represents an association between two Deployment Targets It connects actors to use cases ii Include An include relationship provides a mechanism for factoring out a common functionality that is shared among multiple use cases and is always performed as part of the base use case iii Extend An extend relationship provides an optional functionality which extends the base use case at defined extension points under specified conditions iv Generalization A generalization relationship provides a mechanism to specify variants of the base use case Use cases are often organized into packages with the corresponding dependencies among the use cases included in the packages 5 7 1 SysML Use Case Diagram Metamodel and Elements For more information on notation elements see the Use Case Diagram in the UML Diagrams section of the MagicDraw User Manual uc Model Data Use Case zsametaclass Actor oO Eal gt zsstereotype gt zsstereotype External system Environmental effect K s lt stereotype s lt stereotype s lt sterectypes lt lt sterectpe gt Sensor Boundary system User system Actuator Actor Actor Actor Actor Figure 194 Mag
189. les from the validation process e Validation may take several minutes if your model is large amp Validation Results Validation Results fe OME OF OE BG tte Ord vier va O Binding connectors should be used to bind each parameter of the constraint block to a property in the surrounding context Binding connectors should be used to bind each parameter of m Y1 Yol HSUYModel sHSUY Analysis CapacityEquation Cii info ConstraintBlock 4 P 2 Yol HSUYModel sHSUY Analysis CapacityEquation D info ConstraintBlock 4 the constraint block to a property in the surrounding context la cea sci bk A 7 ate i nat ding i nte i Figure 205 Validation Results Window 7 The Validation Results window will show the elements that do not conform to some con straints in the selected validation suite These elements are called invalid elements and are highlighted If a highlighted invalid element is selected for example the Loss of Fluid require ment element a warning will appear Figure 206 159 Copyright 2006 2011 No Magic Inc Validation srequirements requirements A OffRoadCapability FuelEcononry An Id 2 S Id 2 A Text The Hybrid Text The Hybrid a SUWY shall have the PHS shall have off road capability of dramatically at a typical SUM better fuel ra economy than a ae typical SUW ug Lad Figure 206 Invalid Elements
190. level entities in the overall enterprise and their relationships by establishing system boundaries and top level use cases It depicts each of the constraint blocks or equations that will be used for the analysis and the key relationships between them A system context can be seen as an interface between systems and their external environments These block subtypes are generally used to provide more information on the block usage and or block context Constraint Block Constraint blocks provide a mechanism for integrating engineering analysis such as performance and reliability models with other SysML models Constraint blocks can be used to specify a network of constraints that repre sent mathematical expressions such as F m a and a dv dt which constrain the physical properties of a system Such constraints can also be used to identify critical performance parameters and their relationships to other parameters which can be tracked throughout the system life cycle A constraint block includes con straints such as F m a and their parameters such as F m and a Constraint blocks define generic forms of constraints that can be used in multiple contexts Reusable constraint definitions can be specified on Block Definition Diagrams and packaged into general pur pose or domain specific model libraries Such constraints can be arbitrarily complex mathematical or logical expressions The constraints can be nested to enable a constraint to be defin
191. low Ports to specify what items can flow via those ports 16 Fork Join Horizontal UML To help control parallel actions 137 Fork Join Vertical UML To help control parallel actions 137 Functional Requirement SysML A Functional Requirement is a requirement that specifies a behavior that a system or part of a system must perform 100 Generalization UML A Generalization is a taxonomic relationship between a more general classifier and a more specific one Each instance of the specific classifier is also an indirect instance of the general classifier Thus the specific classifier indirectly has the features of the general classifier 19 Include UML An Include uses relationship from use case A to use case B indicates that an instance of the use case A will also contain the behavior as specified by B 152 Initial Node UML An Initial Node is a starting point for executing an activity It has no incoming edges 137 Input Expansion Node UML An Input Expansion Node is an object node used for indicating a flow across the boundary of an expansion region A flow into a region contains a collection that is broken into its individual elements inside the region which is executed once per element 136 Input Pin UML An Input Pin is a pin that holds input values to be consumed by an action Input pins are object nodes that receive values from other actions through object flows 138 Instance UML To create an instance specification of
192. lueType to the Quantity QUDV Library QUDV 3 Create a new property of the newly created ValueType It will be redefined property of the Quantity value This property will be named value and typed by the subtype of Number Real Complex Integer 4 Create a new static property of the created ValueType It will be redefined property of Quan tity unit The created property will be named unit and typed by a Unit The multiplicity of this static property is 0 1 and the default value of this property will be set to the InstanceSpecifica tion which is the unit of the created ValueType 5 Create a new static property of the created ValueType It will be redefined property of Quan tity quantityKind The created property will be named quantityKind and typed by QuantityKind The multiplicity of this static property is 0 1 and the default value of this property will be set to the InstanceSpecification which is the quantity kind of the created ValueType 13 4 Validation Rules for Detecting the Using of Obsoleted Units and Quantities Since MagicDraw SysML plugin version 17 0 1 the validation rules for detecting the using of unit and quantities which are data types are added These validation rules detect the units and quantities which are data type as the invalid elements as obsoleted unit and quantity The suggested solutions will be provided to help you solv ing the problems Suggested solutions for obsoleted unit 1
193. mplates matrix _templates_module rm H E MD Customization For SysML MO customization H E ModelingDomain H E UML Standard Profile UML Standard Profile x H E sample profile fea SysML Profile SysML Profile mdzip a Ea Leal aca Darcrrinbinn DreaFile M lea ara Drailla 53 i Decrease Renumber 4 ii gt Cancel Figure 196 Change Use Cases Numbering Dialog 3 Click Create to automatically number the selected use case Each use case number will be increased by increments of one For example if the Operate theVehicle use case is numbered 1 Figure 196 select the Insure theVehicle use case and then click the Create button to number the use case to 2 Figure 197 154 Copyright 2006 2011 No Magic Inc SysML Diagrams Ag Change Use Cases Numbering HSU sample a Use Cases Use Cases Owners z E HSUY Model mae e BPS Behavior rs gt Operate theVehicle Configuration Insure thevehicle F Requirements gt Register theVehicle E3 Structure lt gt Maintain the Vehicle EJ Test 7 Fa UseCases agesiHybrid SUY H E views fH G matrix templates matrix _templakes_module rr E Fo MO Customization For SysML MB customization H E ModelingDomain H E UML Standard Profile UML Standard Profile H a sample profile fea SysML Profile SysML Profile mdzip b tee 7 _ 3 3 ac Dacerinkian DraFila ay ac Edit Remove Increase Decrease Renumber i Cancel Help Figure 197 Example of U
194. n Specification Enter Symbol s Properties alt Enter Bate EE Relations H E data H E MD Customization For SysML MD_customization _For_5 H E UML Standard Profile UML_Standard_Frofile xml H Ep SysML Profile SysML Profile mdzip p Assembly H E BLOCK 60 To Select in Containment Tree Related Elements Stereotype Edit Compartment Show Stereotypes Show Tagged Values Show Qualified Mame For Operation Show Owner Select Operation Figure 178 Call Operation Action Shortcut for Select Operation Figure 179 Select Operation Dialog iv Dynamic Centerlines This feature will display a horizontal or vertical centerline to make it easier for you to align a newly created shape or an existing one that is being shifted around with one or two existing shapes in a SysML Activity Dia gram Figure 180 This centerline however will only be displayed in situations where the center of the newly created or shifted shape coincides with the horizontal or vertical axis of the shape s with which it is being aligned regardless of how close to or remote from that shape it is act Activity Activity Diagram H Activity Diagram CallOperation BLOCK eration OpaqueAction a Figure 180 Dynamic Vertical Centerline Dynamic Centerlines is enabled by default So if you do not want to have an horizontal or vertical centerline displayed in your diagram you need to disable
195. n SUV Behavior Row Added Removed Element E BAA sl fo E E HSU Behavior aA Acceleratet transModecmd 3 El ProvidePowerf transMo Co al ProportionPower DO a2 ProvideGasPower D a3 ControlElectricPo D 44 ProvideclectricPa EES HSU Structure H A PowerSubsystem CA emg HSUVModel sHSU CA epc HSUVModel sHSU CH ice HSUYModel HSU CA pcu HSUVModel sHSU o at C 5 mi o p cL T m I Column Scope Column Element Type Column Added Removed Element Q a2 ProvideGasPo Q a3 ControlElectric Q a4 Provideclectric Boe IE emg HSUyMode Boe efh epc HSUYModel Boe IG ice HSUVModel wye e ef E pcu HSUYModel y y Figure 255 SysML Allocation Matrix 10 3 2 SysML Satisfy Requirement Matrix SysML Satisfy Requirement Matrix consists of ificationAction g ISUV Behavior e Row a named element that can be the client element of the Satisfy dependency e Column a Requirement Element that can be the supplier element of the Satisfy dependency 199 Copyright 2006 2011 No Magic Inc Dependency Matrix S Satisfy Matrix x 1em Row Element Type tion Usage Us Column Element Type Requirement Row Scope UseCases Na Column Scope UseCases Na Row Added Removed Element Column Added Removed Element E B AE Gl oe oe q 2 Performance H 4 2 4 Acceleration d
196. n 3 To find out the reason why an element is invalid you can either e Click the warning symbol on the status bar Figure 211 The Active Validation Results window will then open usually at the bottom of the screen displaying the element s that does not conform to some constraint s in the active validation suite s and the reason for the invalidity Figure 213 Active Validation Results Active Validation Results l pall 0 MEO FO fe x BD rer Not Ignored E Copr Reguirement1 Requirement a warning Copy 4 4 requirement cant copy more than one requirement A Copy Reguirement Requirements Wwarnin Copy a A requirement cant copy aa Copy Reg q A a prLA more than one requirement Figure 213 Active Validation Results Or e Select a highlighted invalid element in the diagram copy in the example Figure 210 Once a highlighted invalid element has been selected in the diagram a warning symbol will appear Figure 214 Place your pointer on the warning symbol to see the error message related to the constraint for instance A requirement can t copy more than one requirement Figure 214 lt lt requirement gt CF _ Requirement 2 Scop ye gt s lt requirement gt CE Requirement 1 Requirement 3 Figure 214 Invalid Copy Dependency Usage 4 Unlike the Validation feature in the Validation section this Active Validation feature will in most cases also suggest solution s to fix
197. n straint Property 4 SysML ValSuite Model Elements This suite contains SysML constraints on the following elements View and Viewpoint 5 SySML ValSuite Non normative Extensions This suite contains SysML constraints on the following elements nonStreaming Streaming Design Constraint Functional Requirement Interface Requirement and Performance Require ment 6 SysML ValSuite Port and Flows This suite contains SysML constraints on the following elements Flow Port Flow Property Flow Specification and Item Flow 7 SysML ValSuite Requirements This suite contains SysML constraints on the following elements Copy DeriveReqt Require ment and Test Case lf you use SysML ValSuite as the validation criteria your model will be validated against all seven SysML validation suites at the same time To validate a SysML project 1 Click Analyze gt Validation gt Validation on the main menu Figure 201 Model Visualizer Metrics oe Dependency Matrix b Validation Validation Validation Options Compare Projects Active Validation Options Enable Active validation Figure 201 Validation Menu 2 The Validation dialog will open Figure 202 3 Select a validation suite for example SysML ValSuite MD Customization for SysML SysML constraints in the Validation Suite drop down list to validate your model against a set of SysML constraints in this example all of them Figure 202
198. n Output Pin is a pin that holds output values produced by an action Output pins are object nodes that deliver values to other actions through object flows 138 Package UML A package is a namespace for its members and it can contain other packages Only packageable ele ments can be owned by members of a package By virtue of being a namespace a package can import either individual members of other packages or all the members of other packages 89 Package Import UML A Package Import is defined as a directed relationship that identifies a package whose members are to be imported by a namespace 91 Part Property MDSysML A Part Property is a property that specifies a part with strong ownership and coincidental lifetime of its containing Block It describes a local usage or a role of the typing Block in the context of the containing Block Every Part Property has composite AggregationKind and is typed by a Block Part Properties are displayed in the parts compart ment 54 Performance Requirement SysML A Performance Requirement refers to a requirement that quantitatively measures the extent to which a system or a system part satisfy a required capability or condition 100 Physical Requirement SysML A Physical Requirement specifies the physical characteristics and or physical constraints of a system or a system part 101 Port UML A Port defines an interaction point on a Block or a part allowing you to specify what can
199. n the lt md install dir gt samples SysML directory 8 3 1 Advantages of Context Specific Value Compartments Context Specific Value Compartments allow you to e create different configurations for the same structure and display them directly in IBD diagram s e have different values for the same part in different contexts e assign a different initial value to an inherited property 8 3 2 Using Context Specific Value Compartments A Context Specific Value Compartment is a part symbol compartment Only part symbols can have Context Specific Value compartments A Context Specific Value compartment displays the values of the properties parts reconfigured in a selected context Progressive or Deep Reconfiguration An example of Progressive Reconfiguration is when the values of y and z of a Location are reconfigured to 7 in the Thing context Thus the values Thing compartment in the I Location part in the Thing package will display 7 as the values of y and z Figure 227 Context Specific Value Compartments An example of Deep Reconfiguration is when the value of x of a Location in the UniverseContext package is reconfigured to 3 in the UniverseContext context Thus the values UniverseContext compartment in the Location part in the t1 Thing part in the UniverseContext package will display 3 as the value of x If Uni verseContext is selected the value of z instead of x will be reconfigured to 2 Figure 227 b
200. nables values that are not overridden by the values from the selected con text in a Context Specific Value Compartment to be displayed Assuming the property and the Value Propagation options are enabled the value available in the next context will be used to reconfigure the property if there is no value in the selected context to reconfigure the property However if there is no value available in any context the class level default value will be displayed in the Con text Specific Value Compartment indicating that the property is not reconfigured at all See Figure 233 for an example of the Context specific Values Compartments having the Value Propagation enabled Context Specific Value Compartments bdd Model Data ECC zablock Location parts Location T I COC zablock l Location wales x Real 0 y Real z Real 0 vee Thing x pa H I aji H zablock T i Location n si lig Malio zablock Thing zablock Universe zablock Uti Thing J t1 l zablock U t1 1 Location 7 oo ti Thing U t1 t2 Thing Utz zablock ti Thing parts Location T I lt block gt t2 Thing parts Location T I lt block gt eS Location wales x Real 0 y Real 0 z Real 0 vales x Real 0 y Real z Real 0 zablock U t2 Thin Were Unive re x 0 a LLI I ea Were Unive re x d LLI Zz
201. nal Structure Browser Menus The Structure browser provides two menus to perform some additional actions 9 4 1 Go To gt Type lt name gt in Structure Tree Menu 9 4 2 Go To gt Owner Menu To open the Go To menu in the Structure browser 1 Right click a property in the Structure browser 2 Click Go To and select the option you want from the submenu Structure Browser 9 4 1 Go To gt Type lt name gt in Structure Tree Menu Click Go To gt Type lt name gt in Structure Tree to navigate in the Structure browser to the classifier node of the classifier that types the property of the selected property node The result of the selection is the classifier node in the Structure tree For example after selecting Type WheelHubAssembly in Structure Tree in Fig ure 246 the WheelHubAssembly block will then be selected in the Structure browser ERS Hybrids El Cl c ChassisSubsystem New Element New Relation mpg Real payloadCapac yvehicleDry ei Refactor Usage in Diagrams Owned Diagrams position Real Select in Containment Tree Alt 6 E Type WheelHubAssembly Pk Cal IN String Related Elements ICEFuelFitting Hyperlinks 2 Inflationvalve Stereotype EJ Type WheelHubAssembly in Structure Tree 2 InteriorSubsystern H E InternalCombustion if LightingSubsystem Copy Ctrl C H E LugBoltJoint Copy as URL Rename Fz Find Generate Report Figure 246 Go To gt Type Shortcut Me
202. nd All Context Specific Values Suppress All Type Suppress properties Unspecified Suppress references i 0 Suppress parks O 1 Suppress values Gat Suppress constraints 1 Suppress operations Figure 224 SysML Internal Properties Compartments Shortcut Menu To suppress a feature based compartment e Select the submenu for that compartment To expand a feature based compartment e Clear the submenu for that compartment To suppress all feature based compartments e Select Suppress All To expand all feature based compartments e Select Expand All Context Specific Value Compartments 7 2 Displaying Options in Feature based Compartments Elements displayed in the feature based compartments of a property can be customized using the symbol properties listed under SysML Internal Attributes and SysML Internal Operations in the Symbol s Proper ties dialog of each property Figure 225 To customize the display of the elements in the feature based compartments e Select or clear any of the check boxes as shown in Figure 225 Ly Properties Part lt lt PartProperty gt gt SysML Internal Block Diagram Show Attribute visibility False Show Attribute Type true Show Attribute Stereotype False Show Attribute Properties true Show Attribute Constraints False Show Attribute Default value true Show Operation Signature true Show Operation Visibility False Show Operation Stereot
203. nd a model element that fulfills that requirement As with other dependencies the arrow direction points from the satisfying client model element to the sup plier requirement that is satisfied 102 Select Nested Part Click this button to display a nested part inside a given context For more information see Section 5 2 3 SysML IBD Specific Features vii Select Nested Part 56 Send Signal Action UML A Send Signal Action is an action that creates a signal instance from its inputs and transmits it to the target object where it may trigger the state machine transition or the execution of an activity 136 Sensor A Sensor is a special external system that forwards information from the environment to the system under develop ment For example Temperature sensor 1 151 Sequence Node UML A Sequence Node is a structured activity node that executes its actions in order 138 Shared Property MDSysML A Shared Property is a property that specifies a shared part of its containing block Every Shared Property has shared Aggregationkind and is typed by a block Shared Properties are displayed in the references compartment 54 Structured Activity Node UML A Structured Activity Node is an executable activity node that may have an expansion into the subordinate nodes The structured activity node represents a structured portion of the activity that is not shared with any other structured node except for nesting 137 Structure
204. nd operational work flows They capture actions and display their results They are typically used for business process modeling and used in situations where all or most of the events represent the completion of internally generated actions Though Activity diagrams are often classified alongside interaction diagrams they actually focus on the flows driven by internal processes as opposed to external events SysML extends control in Activity diagrams and provides extensions that might be very loosely grouped under the term continuous but are generally applicable to any distributed flow of information and physical items through a system It also introduces probability concepts to activities 5 6 1 SysML Activity Diagram Metamodel and Elements For more information on notation elements see the Activity Diagram in the UML Diagrams section of the MagicDraw User Manual bdd Model Data 64 Control Operator bdd Model Data St NoButter Overl tite zzmetaclazs zsmetaclazs metaclass Hehavior Operation Of jecthode scSterectypes gt sestereotype gt lt sterectyper gt ControlOperator HoBuffer Overwrite Behavior Operation Objecthode Objecthode Figure 172 Control Operator Metamodel Figure 173 No Buffer and Overwrite Metamodel SysML Diagrams bdd Model Data Gh rate optional probability zametaclass zametaclaszs zametaclass Parameter Activity Edge ParameterSet lt lt metac
205. ndency e c Refined By This column shows the elements that refine the requirement the client of the Refine dependency Refine Refined By Acceleration HSU Model HSUY Requirements HSU Acclerate HSUVModel HSUY UseCases Hybridge SUV Specification Performance l PowerSource Management HSUWModel HSUW 4 HSUY Operational States HSUVModel HSUYV Behavior Requirements Figure 286 Refine Table d Satisfy Table The Satisfy table shows requirements and the elements which satisfy them The requirements in this table will be sorted by the requirement ID There are three columns in this table a ID o Name and c Satisfied By respectively e a ID This column shows the ID of the requirement which is the supplier of the Satisfy dependency e b Name This column shows the name of the requirement the supplier of the Satisfy dependency e c Satisfied By This column shows the elements that satisfy the requirement the client of the Satisfy dependency 223 Copyright 2006 2011 No Magic Inc Report Wizard and Template Satisfy Satisfied By Ca Cargo Ca pacity HSUVM odel HSUY E Baggage HSU Model Requirements HSUY Specification Capacity C8 SafetyTest HSUVModel HSUY Requirements HSUV eee EURT EE E ExternalObject HSU VMode Specification Qualification Power HSUVModel HSUY Requirements E Powe rsubsystem HSUVModel HSUY Structure F
206. nder Liner of the MEP classifier will then be selected in the Structure browser Figure 249 Structure Browser ibd System Context MEF aj seconstraint l l _ Cross Section Equation se Valle yple gt 7 aie area 0 25 PPidiameter 2 car engine cylinderLiner diameter m E Specification Enter Symbol s Properties Alt Enter Go To d Refactor Select in Containment Tree Alt B saW alueTypes Select in Structure Tree car engine crankShaft strokeLength m Related Elements b Stereotype b Autosize ee 7 Edit Compartment Car engine torque Hm Show Stereotypes Show Constraints Show Owner b Wrap Words Show Classifier Sino oe Y B E MEF i C Prep Pa H CE Car Car l CE engine Engine H CE cylinderLiner Cylinder Liner Some diameter cylinderHead Cylinder Head t intakeValves Intake Valve 8 texhaustValves Exhaust Valve pistons Piston 4 starterMotor Starter Motor tinjectionNozzles Injection Mozzl t distributor Distributor sparkPlugs Spark Plug 4 t canmiShark Cam Shaft t crankShart Crank Shaft tdynamo Dynama i Figure 249 Select in Structure Tree Menu Example of Result 194 Copyright 2006 2011 No Magic Inc Dependency Matrix 10 Dependency Matrix Dependency Matrix enables you to visualize and represent your particular model in a tabular form depending on the scopes and dependency criteria you have selected
207. nent Related Elements Data Type Stereotype Enumeration Requirement ID Murmbering Interface Edit Compartment Primitive Type Presentation Options More General e J oy Requirement More Specific Create Instance Risk verify Method Figure 135 Change Requirement Type Shortcut Menu More General 2 Select More Specific Figure 134 More General Figure 135 or Other The requirement type options will be displayed 3 Select a new requirement type from the options The type s of the selected requirement s will then be changed ii Creating a SysML Requirement Diagram for Sub requirements MagicDraw SysML provides an easy way to create a SysML requirement diagram for sub requirements of the selected requirement symbol To create SysML requirement diagram for sub requirements 1 Click on the requirement symbol in which you want to create the SysML requirement diagram for its sub requirements 2 Click the Create diagram for sub requirements button from the smart manipulator Figure 136 Y 4 7 J oy 4 4 im requirements Performance af O Al T Fij w E Create diagram for sub requirements Figure 136 Smart Manipulator Buttons on the Requirement Symbol 3 The new SysML requirement diagram for the sub requirements will then be created Fig ure 137 with the same name as that of the selected requirement SysML Diagrams req requirement
208. ng ID Thus requirements with IDs will NOT participate in Automatic Numbering iii Suggested Solutions for Invalid Requirement s ID When the ID of an requirement element is invalid with respect to the validation constraint Requirement A Requirement s ID must be unique the requirement with invalid ID will be highlighted When select such requirement the requirement smart manipulator menu will also propose the suggested solutions Figure 145 Figure 147 SysML Diagrams 1 Open Requirement ID Numbering dialog Figure 145 this solution will open the Require ment ID numbering dialog The selected requirement will be shown in the requirements list on your right hand side The owner of the selected requirement will be selected on the tree in the panel on your left hand side Figure 146 A Pa Assign new number A sir Ignore reguirements requirements A Rx Ry j Select in Validation Results F a 1 Ad 1 T T ext HHN Fij g E Figure 145 Suggested Solution for Open Requirement ID Numbering Dialog p7 Requirement ID Numbering Requirements requirements Recursive Renumber lear Figure 146 Requirement ID Numbering Dialog 2 Assign New Number Figure 147 you can also use this solution to automatically re assign the new requirement s ID to the selected requirement The first available correct ID will be assigned to the requirement automatically 113 Copyright 2006 2011 No Magic
209. ng New Extension Points 155 Use Case Numbering 153 Use Case Numbering 153 User System 151 V Validation Active Validation 161 Validation 156 Value Pin 138 Value Propagation 183 Value Property 54 95 Value Type 16 Using Value Type 47 Verify 102 View 89 Conform 90 Using View 93 ViewPoint 90 ViewPoint 90 Conform 90 Using ViewPoint 93 W Working with Teamwork Project 207
210. ntext of the containing Block Every Part Property has composite AggregationKind and is typed by a Block Part Properties are displayed in the parts compartment Shared Property MDSysML A Shared Property is a property that specifies a shared part of its containing block Every Shared Property has shared Aggregationkind and is typed by a block Shared Properties are displayed in the references compartment Reference Property MDSysML A Reference Property is a property that specifies a reference of its containing Block to another Block Every Reference Property has none AggregationKind Lil and is typed by a block Reference Properties are displayed in the refer ences compartment Constraint Property SysML A Constraint Property is a property that specifies the constraints of other prop erties in its containing Block Every Constraint Property is typed by a Con straint Block Constraint Properties are displayed in the constraints compartment SysML Diagrams Button Element hot key Distributed Property SysML A Distributed Property is a property of a Block or a Value Type used for apply ing a probability distribution to the values of the property Specific distributions ol can be defined by applying a subclass of the DistributedProperty stereotype to the property Select Nested Part Click this button to display a nested part inside a given context For m
211. nu 9 4 2 Go To gt Owner Menu Click Go To gt Owner Figure 247 to navigate to the classifier node of the classifier that is the owner of the property of the selected property node The result of the selection is the classifier node in the Structure tree Structure Browser Mew Element p PowerSubsystem b BodySubsystem bk BrakeSubsystem i Interior Subsystem LightingSubsyste TEN mpg Real a Owned Diagrams payvloadCapacity yehicleDry weight 2 position Real Select in Containment Tree Alt B i Ol VIN String Related Elements H ICEFuelFitting HE Inflationvalve fo InteriorSubsystem Rename AG InternalConmbustionEnging ee LightingSubsystem H E LugBalk Joint Copy as URL New Relation Refactor Usage in Diagrams Stereotype Ctrl Find Generate Report Figure 247 Go To gt Owner Shortcut Menu 9 5 Additional Diagram Menu 9 5 1 Select in Structure Tree Menu Use the Select in Structure Tree menu on the part shortcut menu Figure 248 on Internal Block Parametric or Composite Structure diagram to select in the Structure browser the structure node corresponding to the selected part symbol For instance in Figure 248 the context of the IBD is MEP When using the Select in Structure Tree menu with the diameter m car engine cylinderLiner diameter m part the corresponding diameter m node under car Car gt engine Engine gt cylinderLiner Cyli
212. o display the package name on top Figure 117 or ii In Tab to display it in the tab Figure 118 Package Name Package Name Figure 117 Package Name on Top Figure 118 Package Name in Tab You can also show a list of elements owned by a package To show an element list 1 Right click a package and select Show Elements List on the shortcut menu Figure 119 2 The element s owned by the package will then be displayed in the package Figure 120 If the package owns no element the package will look like in Figure 121 SysML Diagrams Specification Enter l Symbols Properties Alt Enter New Diagram d na To d Refactor Select in Containment Tree Alt B Related Elements Tools b Stereotype d Requirement ID Numbering Edit Compartment Show Stereotypes Show Tagged Values Show Owner b Wrap Words Show Elements List Header Position Figure 119 Package Shortcut Menu Show Elements List Figure 121 Element List is not Shown Figure 120 Element List is Shown View and Viewpoint m The Viewpoint of a View is derived from the supplier of the conform dependency whose client is the View itself A A view can only own element imports package imports comments and constraint elements A A viewpoint cannot own any operation nor attribute 5 4 SysML Parametric Diagrams Parametric diagrams can be defined as restricted forms of IBDs They are
213. o the Select Element Scope pane You can then change the report scope using this pane e The Built in report data in the Select Report Data pane of Report Wizard must be selected in order to generate a report from this table See Section 12 Report Wizard and Template for more information on report generation Generate Report SysML Requirement Table Type A Output options This page allows you to configure report files e g to select the report files output location and image format etc Click Generate button to start generating the report Output Options Report file Report image format Joint Photographic Experts Group jpg Auto image size Fit image to paper large only Display empty value as Publish to server Empty text Select server Custom text none No Upload Display in viewer after generating report Figure 169 Generate Report Dialog SysML Requirements Table k ID Numbering You can activate the Numbering Requirement IDs feature from a SysML Requirements Table by clicking the ID Numbering icon on the table toolbar Table 6 To edit the ID of a requirement select the requirement in the table and click the ID Numbering icon on the table toolbar 1 Show Columns To show hide columns in the table click the Show Columns icon on the table toolbar Table 6 The Table Col umn drop down menu will then display Figure 170 SysML Diagrams a 1D ra Name i Tex
214. ock and has composite aggregation must be applied with PartProperty e Shared property which is the property that is typed by Block and has shared aggregation must be applied with SharedProperty e Reference property which is the property that is typed by Block and has none aggregation must be applied with ReferenceProperty e Value property which is the property that is typed by value type must be applied with ValueProperty The type of a value property must be a value 8 3 2 2 type The DistributedProperty stereotype may be 8 3 2 4 applied only to properties of classifiers stereo typed by Block or Value Type Any classifier which specializes a ValueType 8 3 2 10 must also have the ValueType stereotype applied If a value is present for the unit attribute the 8 3 2 10 quantity kind attribute must be equal to the value of the quantity kind attribute of the refer enced unit A FlowPort must be typed by a Flow Specifica 9 3 2 3 tion Block Signal or Value Type Validation Constraint FlowPort FlowPort FlowPort FlowPort non active FlowPort FlowProperty FlowProperty FlowSpecification ItemF low Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 2 with permission If the FlowPort is atomic isAtomic True the direction must be specified has a value and isConjugated must not specified has no
215. omy 2 1 CA Braking The Hybrid U shall have the Performance Performance ai ng capability of a typical Requirement HS UVModel HSLIV Requirements HSW Specification FyelEconomy The Hybrid HSU shall have Performance E Performance dramatically better fuel Requirement HSU Model HSL th typical SUW Halles Seen eae Requirements HSU Specification O offRoadCapability The Hybrid SU shall have the Performance a offfoad capability of a typical Requirement oo ae SUY THSUyModel HSU Requirements HS Uy Specification 24 o Accaeration The Hybrid SUW shall hawe the Performance C Performance acceleration of atypical SUY Requirement HSUVMadel HSLIY olla Requirements H5Ly Specification Confidential Mo Magic Inc 7 Figure 291 Report Generated Using SysML Requirements Table Diagram Template i Appendix for Captured Diagram Images If the requirements generated in the document have active hyperlinks to the diagrams the diagrams will be captured and given in Appendix A Diagrams ii Hyperlinks in Generated Reports For a requirement that has an active hyperlink to the diagram a hyperlink text will be generated for the name of the requirement in the Name column The hyperlink will navigate to the captured image of the diagram in Appendix A of the document 12 3 Allocation Report Templates Use Allocation Report Templates to generate Allocation reports each report providing a summary of the allo
216. on element is a Flow Property For more information on the flow port and the flow properties please refer to the SysML Internal Block Dia grams IBD section below 5 1 6 Converting Data Types to SysML Value Types SysML specification 1 2 suggests to use Value Type as the type of every value property Therefore every Data Type typing a Value Property should be either i replaced by another Value Type or ii converted to be a Value Type SysML Diagrams i Replacing UML Primitive Data Type with SysML Value Type Every Value Property typed by a Primitive Data Type e g Integer String Boolean etc will break a validation constraint Figure 46 You can replace such Primitive Data Type usage with a corresponding Value Type easily using the suggested solution Replace primitive DataType with equivalent Value Type when available bdd Model Data Untitled4 Type primitives UML Standard Profile JML WMetamodel Auxiliar onstructs Primitive Types Boolean zblock A A RnneEAN Type primitives UML Standard Profile UML WMetamodel Auxiliar onstructs Primitive Types Integer Figure 46 Invalid Value Properties To replace Primitive Data Type with equivalent Value Type e In Active Validation Results window select the property ies which is are typed by Primitive Data Type s See 6 1 Active Validation for more detail on such window e Right click on the selected element s e The shortcut menu will
217. one among several alternate flows 137 Model UML A Model is a special kind of Package It contains a hierarchical set of elements that describe the physical system being modeled A model owns or imports all the elements needed to represent a complete physical system accord ing to its purpose 90 moe SysML moe measure of effectiveness represents a parameter whose value is critical for achieving the desired cost effectiveness mission 94 Object Flow UML An Object Flow is an activity edge that can have objects or data passing along it An object flow models the flow of values to or from the object nodes 136 Object Node UML An Object Node is an abstract activity node that is part of defining object flow in an activity Object nodes can be used in a variety of ways depending on where objects are flowing from and to 135 Objective Function SysML An Objective Function also known as optimization or cost function is used for determining the overall value of an alternative in terms of weighted criteria and or moe s 94 Opaque Action UML An Opaque Action is an action that introduces discipline to implement specific actions or to be used as a temporary placeholder before some other actions are chosen 135 Output Expansion Node UML An Output Expansion Node is an object node used for indicating a flow out of a region that combines individual elements into a collection for use outside the region 136 Output Pin UML A
218. onfiguration For more information on Progressive Reconfiguration see http training nomagic com 8 2 Deep Reconfiguration Deep Reconfiguration enables you to configure deep nested part s with context specific value s Consider for example the case of a truck reusing a complex WheelHubAssembly for three pairs of wheels each with differ ent characteristics Although the basic WheelHubAssembly might be suitable for a range of vehicles a car touring car and minivan it is not nearly suitable for a large truck Some of the WheelHubAssembly parts and subparts required for a truck are larger and must be stronger to handle heavy loads They include e the diameter of the Tire TireBead and Rim will be larger e the inflationPressure value of the WheelAssembly will be higher e the LugBoltJoint will be subject to greater torque and boltTension Context Specific Value Compartments e the LugBoltThreadedHole will have larger lugBoltSize and threadSize In this case Progressive Reconfiguration will fail because the new configuration requirements cascade throughout the entire complex WheelHubAssembly from the outermost context to the deepest part Since no Progressive Reconfiguration approach can handle this deep reconfiguration of complex assemblies you need to use Deep Reconfiguration You can start with a completely new TruckWheelHubAssembly that configures a completely new Truck WheelAssembly right down to a TruckLugBoltJoint
219. onstraint Block having shared and none aggregation kind respectively Value Properties properties which are typed by Value Types or subtypes of Value Type always having composite aggregation kind Constraints and Constraint Properties Constraint Properties properties which are typed by Constraint Blocks or subtypes of Constraint Block always hav ing composite aggregation kind All other properties which cannot be classified into the previous compart ments In addition three SysML compartments are provided for displaying the Constraint Blocks properties i e con straints others and parameters compartments Figure 19 SysML Diagrams SysML Compartments constraints others parameters constraints PowerEquation Corsets itp shlpvr fodty CPT ty f parameters whlipwer gt Horsepwriunit hg i Real Cd Real CT Real tw Weightiunit lb tg Horsepwriunit ng Y Veliunit mgh Figure 19 SysML Constraint Block Compartments Table 2 SysML Constraint Block Compartments Displayed Elements Constraints and Constraint Properties Constraint Properties properties which are typed by Constraint Blocks or subtypes of Constraint Block always hav ing composite aggregation kind All other properties which cannot be classified into the previous compart ments Constraint Parameters reusing the ports compartment of Class To suppres
220. onstraint Blocks provide a mechanism to integrate engineering analysis such as performance and reliability models with other SysML models Constraint Blocks can be used to specify a network of constraints repre senting mathematical expressions which constrain the physical properties of a system Constraint Blocks are generally defined in Block Definition Diagrams and then used in Parametric diagrams 15 Constraint Property SysML A Constraint Property is a property that specifies the constraints of other properties in its con taining Block Every Constraint Property is typed by a Constraint Block Constraint Properties are displayed in the con straints compartment 54 Control Flow UML A Control Flow is an edge that starts an activity node after the previous one is finished Objects and data cannot pass along the control flow edge 136 Copy SysML A Copy relationship is a dependency between a supplier requirement master and a client requirement slave specifying that the client requirement text is a read only copy of the supplier requirement text 102 Data Store UML A Data Store node is a central buffer node for a non transient information A data store keeps all tokens that enter it copies them when they are chosen to move downstream Incoming tokens containing a particular object replace any tokens in the object node containing that object 136 Data Type UML A Data Type is a type whose instances are identified only by t
221. or of the requirement you would like to number or e the browser shortcut menu of the package containing the requirement s or of the requirement you would like to number or e the diagram shortcut menu SysML Diagrams Specification Enter Symbol s Properties Alt Enter Mew Diagram b a0 To b Refactor lt requiremen Select in Containment Tree Alt 6 Ergonomic ld Related Elements Id Text H n ll Tools Vee Stereotype b aguirement H Aubosize sngerCapacity FuelCapacity Edit Compartment b 5 Id 4 aaa un Tewt Show Stereotypes d Show Constraints Figure 138 Requirement ID Numbering Shortcut Menu 2 The Requirement ID Numbering dialog will open Figure 139 Select for example the HSUV Specification package in the browser on the left hand side of the dialog The requirements owned by the package will appear in the Requirements pane on the right hand side of the dia log Figure 139 p7 Requirement ID Numbering EG Data Eb HSUVModel B B Explanations B E HSU Analysis m ma Capacity B E HSU Behavior C Eco Friendiness HSL Requirements CA Ergonomics ob Ey Ee A Qualification be CA PowerSourceManagement l E 2 Performance i CE d 1 RegenerativeBraking i C d 2 Range i C d 4 Power i E8 MaxAcceleration Lui Max Acceleration B E HSU Structure Numbering Style Prefix Separator Renumber Figure 139 Requirement ID Numb
222. ore infor mation see Section 5 2 3 SysML IBD Specific Features vii Select Nested Part Flow Property SysML A FlowProperty signifies a single flow element that can flow to from a block Flow properties are defined directly on blocks or flow specifications that are those specifications which type the flow ports Flow properties enable item flows across connectors connecting parts of the corresponding block types either directly in case of the property is defined on the block or via flowPorts A flow property s values are either received from or transmitted to an external block Moe See Section 5 4 1 for description Objective Function See Section 5 4 1 for description Cal Port UML A Port defines an interaction point on a Block or a part allowing you to specify what can flow in out of the Block part or what services the block part requires F expects from or provides offers to its environment Ports are connected by connectors to other parts or ports Flow Port SysML A Flow Port is a port that specifies the input and output items that can flow between a Block and its environment Flow Ports are interactions points through which data material or energy can enter or leave the owning Block The specification of what can flow is achieved by typing the Flow Port with a specification of things that flow This can include typing an atomic Flow Port with a single type Block Value Type or Signal represen
223. ow Tagged Values in the context menu of Note symbol to show the selected tagged values in callout box Figure 54 51 Copyright 2006 2011 No Magic Inc SysML Diagrams allocatedFrom eblocksElement eltonnectorsElement4 connmectort allocatedTo eblocks eatamicFlowPortsElement3 portt Block Patt Elament4 partt Figure 54 Callout Box with the SysML Callout Style 6 You can customize the display of the callout box using Symbol s Properties dialog of Note symbol Figure 55 e SysML Callout Style symbol property can be used to switch between MagicDraw standard callout style and the SysML callout style By default this property is set to true for the SysML project With SysML callout style the element types e g block connector atomicFlowPort part will be shown instead of the icon of the tagged values which are the model elements e SysML Element Type symbol property can be used to show or hide the element types in the callout box when it is displayed with SysML callout style Ly Symbol Properties Mote f SysML Block Definition Diagram HTML Text true Text Display Mode Do nok show Show Line Between Compartments true Show Documentation Stereotypes true Show Tagged Values Stereotypes true Show Qualified Names for Properties Values False Show Element Properties true Show Stereotypes Shape Image and Text SysML Callout Style true SysML Element Type true Symbol IL 16 Sbeta 175304
224. owPort can only be applied to a port which is owned by a Block or its subtype FlowProperties must be typed by a ValueType Block or a Signal A Flow Property must have its direction speci fied and the default value of the direction should be inout A FlowSpecification can be used as a type of a FlowPort only An ItemFlow itemProperty must be typed by a Block or by a ValueType Directly Derived specified from OMG in OMG SysML SysML spec spec 9 3 2 3 9 3 2 3 9 3 2 3 9 3 2 3 9 3 2 3 9 3 2 4 9 3 2 4 9 3 2 5 9 3 2 6 Validation Constraint Constraint Description Directly Derived Description excerpts have been taken from the OMG specified from OMG SysML Specifications 1 2 with permission in OMG SysML SysML spec spec ltemFlow 3 An ItemProperty must be a property of the 9 3 2 6 block that owns the source and the target ltemFlow 4 The type of itemProperty should be the same 9 3 2 6 or a subtype of the conveyedClassifier ltemFlow 5 An Item property cannot have a value if there is 9 3 2 6 only one association between the source and the target of the InformationFlow ltemFlow 7 Ifan ItemFlow has an itemProperty its name 9 3 2 6 should be the same as the name of the item flow ltemFlow A The conveyed classifiers must be the same or 9 3 2 6 subtype of classifier that type flow property of flow specification ConstraintBlock 1 A ConstraintBlock cannot own any structural or 10 3 2 1 behavioral elemen
225. owerful tool for visual izing traceability select Analyze gt Create Relation Map in the main menu The main feature of this feature is traceability between different levels of abstraction which makes it possible to find more specific and realizing elements usually not from the same view This allows for handy specification and realization discovery and navigation The effectiveness of traceability across a whole project is supported by the following MagicDraw capabilities e Relation Maps for the analysis of traces among multiple levels of abstraction see Introduction to SysML mdzip located in lt md install dir gt samples SysML directory for sample use e Traceability Reports for coverage analysis see Coverage Analysis e Dependency Matrices for the analysis of traces between any two levels of abstraction two matrices for traceability are provided SysML Traceability Requirement All Specifying Elements Matrix and SysML Traceability Requirement All Realizing Elements Matrix See section 10 Dependency Matrix for more detail on how to use such matrices Open API Traceability solution is based on recent DSL improvements in MagicDraw for extendable metamodels with derived properties and two level properties groups For more detail on the Traceability feature visit http www magicdraw com newandnoteworthy sysml 15 Open API 15 1 Stereotype Usage Standard stereotypes in SysML plugin are defined in SysML
226. partments To enable the value propagation mechanism 1 Click Options gt Project on the main menu Figure 234 to open the Project Options dialog Figure 235 Project Modules Environment Perspectives Figure 234 Project Options Menu 2 Select General project options gt SysML 3 Select the Propagate SysML Values check box and click OK Figure 235 Ad Pro ject Options ae ee Sener al project options pai E Diagram Info B E Symbols properties styles General project options EF EZ B E Default Default El i EF Shapes lt project dir gt Paths Modules path lt install rook gt profiles Fey Diagram uk Stereotypes i E Default model properties l Code Engineering i ran ae Code Generation oes ar Reverse poe aoi gd Java Language Options oe C Language Options Ei ogi C Language Options Ei e CORBA IDL 3 0 language of Ei iE DOL Language Options E Enable dot notation For associations Change ownership of non nawigabl Qualified name display style Auto synchronize Parameters and Validation scope Exclude elements From read only m Mark in tree and diagrams Ignored validation suites Minimal severity Propagate SysML Values lt install root modelLibr aries False true Absolute true Data true true Parameters Synchronization A warning UML Standard Prof true Figure 235 Project Options Propagate S
227. pecification dialog and then assign the following values to its slots e quantityKind QuantityKind thermodynamic TemperatureQK e exponent Rational 1 1 means 1 1 or 1 where Rational is of the format numerator Integer denominator Integer which refers to a rational number numerator denominator A quantity kind using such factor thermodynamic Temperature 1QKF actually refers to the same dimension as thermodynamic TemperatureQK quantity kind 4 Open the newly created quantity kind specfication dialog 5 Assign the name of the quantity kind to be celsius TemperatureQk 6 Select the Slots property group and then assign the corresponding slot values e name String mandatory Celsius temperature e factor QuantityKindFactor thermodynamic Temperature 1 QKF See Annex C 5 Model Library for Quantities Units Dimensions and Values QUDV in OMG SysML specifica tions 1 2 for more detail Model Library for Quantities Units Dimensions and Values QUDV 13 3 2 Creating New Unit To create a new unit you have to create an InstanceSpecification whose classifier is one of Unit subtype i e SimpleUnit DerivedUnit GeneralConversionUnit AffineConversionUnit LinearConversionUnit and PrefixUnit You can create a unit using either Browser Shortcut Menu or Diagram Toolbar of BDD Open the unit s speci fication dialog and then change its slot value s according to
228. pendencies Report mm Requirement Diagram Requirement Report a Requirement Table Type A lim Requirement Table Type B 4 E Requirements Table Diagram Report H 3 Traceability Figure 269 Report Wizard Dialog Template Selection To create a report using a SysML report template 1 Select a report template and click Next in the Report Wizard dialog Figure 269 The Select Report Data pane will open You can then select a pre defined report data for the selected tem plate default Built in in Figure 270 209 Copyright 2006 2011 No Magic Inc Report Wizard and Template N Report Wizard Select a report data Select a report data a collection of report variables e g Author Publisher etc which you would like to be induded in the generated report A builtin report data is provided for every predefined template Select Report Data Been Pre defined report data for this template Figure 270 Report Wizard Dialog Pre defined Report Data Selection 2 You can modify the introductory information of a report i e Variables formerly called User Defined Fields by clicking the Variable button on the Select Report Data pane Figure 270 The Variables dialog will then display Figure 271 You can then add modify the variableof the report to be generated such as author company name company address report purpose report scope etc This information will appear in the
229. placeholder before some other actions are chosen Button hot key S SysML Diagrams Button Element hot key Any Action UML This element is introduced in order to maintain any other desirable action ele 7 ment with an appropriate metaclass stereotype applied Object Node See Section 5 6 1 for description co SHIFT B Data Store UML A Data Store node is a central buffer node for a non transient information A g data store keeps all tokens that enter it copies them when they are chosen to move downstream Incoming tokens containing a particular object replace any SHIFT D tokens in the object node containing that object Activity Parameter Node UML An Activity Parameter Node is an object node for inputs and outputs to the activities The Activity parameters are object nodes at the beginning and end of the flows to accept inputs to an activity and provide outputs from it Input Expansion Node UML An Input Expansion Node is an object node used for indicating a flow across tm the boundary of an expansion region A flow into a region contains a collection st that is broken into its individual elements inside the region which is executed once per element Output Expansion Node UML An Output Expansion Node is an object node used for indicating a flow out of a region that combines individual elements into a collection for use outside the region Object Flow UML An Object Flow is an activity edge that c
230. ple if the selected context is A then the compartment label will be values A To select a context using the shortcut menu e Right click the part and select Context Specific Values gt Context Figure 230 Context Specific Value Compartments lt lt block gt Universe pants t1 Thing U t1 t2 Thing U t2 zablock ti Thing pants Location TI s block gt l Location Vee s Universe x 0 Y 4 LL T vad Specification Symbol s Properties Select in Containment Tree Related Elements Aubosize Edit Compartment Show Stereotypes Show Constraints Show Owner Wrap Words qll Show Classifier Show Tagged Values Show Default Value Enter Alt Enter Suppress Context Specific values Thing Context i Figure 230 Shortcut Menu Select Context 8 3 5 Customizing Context Specific Value Compartment Display You can display or hide the elements types in the Context Specific Value Compartment of a part using either i the Symbol s Properties dialog or ii the part shortcut menu i Using the Symbol s Properties Dialog To display or hide element type s using the Symbol s Properties dialog 1 Right click the part and select the Symbol s Properties option 2 Three display modes are available in the Symbol s Properties dialog Figure 231 e None to hide types e Name to display the names of the element types e Qualified
231. rained model element SysML Satisfy_Requirement Matrix template This template is used for creating a matrix to show Satisfy dependencies between require ments and model elements that fulfill the requirements Each arrow direction points from the satisfying client model element to the satisfied Supplier requirement SysML Verify_Requirement Matrix template This template is used for creating a matrix to show Verify dependencies between requirements and named elements that can determine whether the systems fulfill the requirements Each arrow direction points from the client named element to the Supplier requirement For more information on the Dependency Matrix feature see the Model Analysis in the Dependency Matrix section in the MagicDraw User Manual 10 3 SysML Editable Matrices Starting from version 16 6 of SysML Plugin three of SysML matrix templates are editable Beside display of dependencies between elements you can add delete dependency ies directly in the editable matrices There fore SysML provides three different matrices SysML Allocation Matrix SysML Satisfy __ Requirement Matrix and SysML Verify_ Requirement Matrix 10 3 1 SysML Allocation Matrix The SysML Allocation Matrix consists of e Row a named element that can be the client element of the Allocate dependency e Column a named element that can be the supplier element of the Allocate dependency Dependency Matrix ificationActio
232. raint Block re uses the ports compartment of Class Consequently you can suppress or expand the parameters compartment by using the symbol property for suppress ports compartment iv Creating an Association Block To create an Association Block on a Block Definition Diagram either 1 Select Association Block on the diagram toolbar Figure 21 2 Select a Block on the diagram to be used as the source of the Association Block to be created 3 To select the target of the Association Block either select an existing Block on the diagram to be used or click on empty space on the diagram to create such target Block 4 An Association Block will then be created between the source and target Blocks or SysML Diagrams 1 Select the Association Block icon in the Smart Manipulator menu of a Block to be used as the source of the Association Block Figure 22 2 To select the target of the Association Block either select another Block or click on an empty space on the diagram to create such a target Block 3 An Association Block will then be created between the source and target Blocks ES Block Definition Diag Ce Value Type T Ce Enumeration Signal Instance Interface Flow Specification a Port P Interface Realiz Link Directed Associa 4 Directed Aggreg as Directed Compo Generalization 7 ath Usage 7 Figure 22 Block Smart Manipulator to Create
233. rams can be used to support trade off analysis A constraint block can define an objective func tion to compare alternative solutions 5 4 1 SysML Parametric Diagram Metamodel and Elements For the description of the SysML properties MagicDraw SysML properties and flow port metamodels refer to the SysML Internal Block Diagrams IBD section bdd Model Data S Parametric elements bdd Model Data R Binding Connector lt smetaclass sametaclass Property Connector sometaclass gt sceterectypes gt Class InvisibleStereotype Element e Lel costerectypes gt sosterectypes gt moe objectiveFunction Property Class Property lt lt stereotypes gt BindingConnector Connector Figure 122 moe and Objective Function Metamodel Figure 123 Binding Connector Metamodel Icon Description Moe SysML moe measure of effectiveness represents a parameter whose value is critical for achieving the desired cost effectiveness mission Objective Function SysML a An Objective Function also Known as optimization or cost function is used for deter mining the overall value of an alternative in terms of weighted criteria and or moe s SysML D Icon lagrams Description Connector UML A connector is used for binding two ports together demonstrating relationship between those ports A connector can be typed by an association A logical connector can be allocated to a more compl
234. reating New SySML Project from Specified Template 2 On the main menu select Options gt Project 3 The Project Options dialog will then display 4 Select Symbols properties styles node on the left and then select the OMG SysML style in the Symbols properties styles panel on the right as displayed in Figure 6 5 Press Make Default button and then press OK 6 The OMG SysML style is now used as default in your SysML project 10 Copyright 2006 2011 No Magic Inc Working with SysML Projects L Pro ject Options Symbols properties styles Symbols properties styles Default Default Default Default OMG SysML style E Paths Stereotypes GO OMG SysML style Make Default H E Default model properties A Code Engineering Apply bg Code Generation E Java Language Options i C Language Options Head C Language Options eE CORBA IDL 3 0 languag ba DDL Language Options Cancel Figure 6 Project Options Dialog Set Symbol Properties Style To apply OMG SysML style to an existing SysML project 1 Open the SysML project 2 On the main menu select Options gt Project 3 The Project Options dialog will then display 4 Select Symbols properties styles node on the left as displayed in Figure 6 5 In the Symbols properties styles panel on the right if the OMG SysML style is not avail able press Import button The Open dialog will then open Figure 7 In the dialog selec
235. ree and click OK Figure 5 New Project Create a new project from a template A project created from a template will contain a predefined project structure and customized graphical user interface Specify a project name select a location to store the newly created project choose a project template and click OK General Purpose Modeling 2 a Name Untitled3 a Le UML Guide to Project UML Diagrams Project ih ZI Select template Project location lt User home gt MD_projects SysML Create directory for project and related data from Existing Project Froject Use Case mA RUF SysML Source Code AES ys Business Process Modeling fa i Use Case modeling Other Template description me a 48 44 Use this template to create anew SysML project using SysML profile re Ls Also load SI ValueType and QUDV model libraries Project Process from Template Guide Project Figure 5 Selecting SysML Template For more information on how to work with a new project see the Working with Projects section in the MagicDraw User Manual 4 3 Using OMG SysML Style SySML plugin provides the visual style of OMG SysML specifications OMG SysML style for using with your SysML model Such style is available with every new SysML project created by SysML 16 8 or newer To use OMG SysML style in a new SysML project 1 Create a new SysML project see 4 1 Creating Blank SysML Project or 4 2 C
236. report generated 210 Copyright 2006 2011 No Magic Inc Report Wizard and Template N Report Variable Manage report variables Create modify delete variables or set values for them Variable Author lt Author name gt CompanyName No Magic Inc CompanyAddress 7304 Alma Drive Suite 600 Plano TX 7 Purpose lt This document provides requirement Scope lt Provide a short description of the sys Overview Describe what the document contain Footer Confidential DocumentTitle Requirement Report Revisions true Figure 271 Report Wizard Dialog Variable 3 Click OK to return to the Select Report Data pane Figure 270 In the Select Report Data pane click Next The Select Element Scope pane will then display Figure 272 211 Copyright 2006 2011 No Magic Inc Report Wizard and Template Report Wizard Select element scope Select one or more elements to be used as the scope of the generated report Select Element Scope All data Selected objects EE Selected objects EF HSU Model ra Explanations PS HSU Analysis H E HSU Behavior E9 HSU Instance Values 7 E HSUY Requirements Add Recursively H E HSUY Structure 7 E HSUY UseCases HPS HSUY views ModelingTips i Stereotypes SysML 1 1 Specification ty OF Mm DR n E Generate Recursively Show Auxiliary Resources Show Only Package Element Figure 272 Report Wi
237. requirements that are the suppliers of the deriveReqt dependency whose client is the derived requirement represented by the requirement ID and name Report Wizard and Template Derive Derived From Ca RegenerativeBraking HSU VModel HSU C8 2 1 Braking HSU Y Model HSUY Require ments HSUY Requirements Specification Perfor mance Y Requirements HSUY Ra nge HSU YModel HSUY Requirements Y Requirements HSU Specification Capacity PowerSource Management HSUVMadel HSUV 2 2 FuelEconomy HSUvModel HSUV Requirements HSUY Requirements Specification Performance C8 d 4 Power HSUYModel HSUY Requirements Ca Power HSUVMadel HSUV Requirements 2 3 OffRoadCapability HSUYModel HSUY Require ments HSUY Specification Performance C8 2 4 Acceleration HSUVModel HSUY Requirements HSUY Specification Performance C8 3 3 Cargo Capacity HSUYModel HSU Y Require ments HSUV Specification Capacity Figure 285 Derive Table c Refine Table The Refine table shows requirements and the elements that refine them The requirements in this table will be sorted by the requirement ID There are three columns in this table a ID b Name and c Refined By respectively e a ID This column shows the ID of the requirement which is the supplier of the Refine dependency e b Name This column shows the name of the requirement the supplier of the Refine depe
238. rt shortcut menu Figure 107 Note that without a direction the flow port will be just like a normal port it will not enforce any direction on the item s flowing in out of the port 84 Copyright 2006 2011 No Magic Inc SysML Diagrams lt block gt Partib Blocks lt block g Part3a Part4a Block5 lowpart wale Type Specification Symbol s Properties 0 To Refactor Select in Containment Tree Related Elements Stereotype Edit Compartment Show Stereotypes Show Tagged Values Show Provided Interfaces Show Required Interfaces Type public protected package private Direction Is Conjugated Enter Alt Enter Figure 107 Flow Port Shortcut Menu Flow Port Direction amp The Flow Port direction must be defined ItemProperty Item Property is the only attribute of Item Flow An Item Flow describes the flow of items across a connector or an association If an Item Flow is assigned to a connector in general you can specify this optional attribute ltem Property to relate the flowing item to the instances of the connectors enclosing block In general Item Flows and Item Property are defined on connectors in IBDs To create an Item Flow having the Item Property tag initialized on a connector 1 Either e i click the Item Property button on the IBD diagram toolbar and then select the connector or e ii click the Item Property icon on
239. rts for the multiple selection of the nested requirements which are owned by the same owner i Nest Requirement You can select a requirement in the Requirements Table and then click on the Nest Requirement to move the selected requirement to be owned by the requirement in the previous row Nest Requirement also support for the multiple selection of the requirements j Report The SysML Requirements Table allows you to generate a requirement report directly from the table The default report template used is Requirement Table Type A To generate a report click the Report icon on the table toolbar Table 6 The template drow down menu will then open Figure 168 port ID Numbering 4 Show Columns Expor SysML Requirement Table Type A SysML Requirement Dependencies Report SysML Requirement Report Heh wile SysML Requirement Table Type B Ei SysML Coverage Analysis Figure 168 Template Drow down Menu SysML Diagrams Select the report template you would like to use The Generate Report dialog will then open Figure 169 Choose the report output filename and then click Generate to instantly generate the report e All requirements in the table will be used as the scope of the generated report e To change the scope of the report activate Report Wizard by clicking the Wizard button in the Generate Report dialog Figure 169 Click the Next button in the Report Wizard twice to proceed t
240. s aoe Fr onDihanisAsnem Refactor d Type FrontwheelsAssembly Select in Containment Tree AlE B SESE Bani Related Elements Stereotype Aubosize Edit Compartment b Show Stereotypes b Show Constraints Show Owner wrap Words Show Classifier Show Tagged Values b Show Default value Chew Slak Ture k Figure 101 Go To gt Type Function 8 Open the created IBD to display the structure which was recently extracted Figure 102 The structure view will be ready Figure 103 SysML Diagrams E Relations EHE wheel O i BE Hub lt ti AE HSU Structure H E HSU Interfaces F lt Relations eel4ssermbly O Balancew eight D E FrontwWheelAssembly E Relations cal Frontyh ip Ersim u rightWheel Front i H eftwheel Frontw iuu EE lf Frontw heel 1 i CE dif Differential i EE rf Front heel 1 i CE t Torque i CE t1 Torque G0 To e_r t2 Torque spline t1 Torque trem tren lettHaltshatt rightHaltShaft o Y rfw FrontWheel 1 Mew Relation b Open in Mew Tab Specification Refactor Select in Structure Tree Related Elements b Common E Note abe Text Box A E5 Problem E E5 Rationale E Anchor 7 Containment bi Al Dernen Een right wheel Fro gel Figure 103 Displayed Extracted Structure 5 2 6 Using SysML IBD Elements Flow Port In gener
241. s expects from or provides offers to its environment Ports are connected by connectors to other parts or other ports Flow Port SysML A Flow Port is a port that specifies the input and output items that can flow between a Block and its environment Flow Ports are interaction points through which data material or energy can enter or leave the owning Block The specification of what can flow is achieved by typing the Flow Port with a specifi cation of things that flow This can include typing an atomic Flow Port with a single type Block Value Type or Signal representing the items that flow in or out or typing a non atomic Flow Port with a Flow Specification which lists mul tiple items that can flow In general Flow Ports are intended to be used for asynchronous broadcast or send and forget interactions Note that only non atomic Flow Ports can be conjugated Once conjugated all the directions of the typing Flow Specification s items will be negated T Interface Realization UML An Interface Realization is a specialized Realization relationship between a P Classifier and an Interface This relationship signifies that the realizing classi fier conforms to the contract specified by the Interface Link UML A Link is a connection between two objects FA SHIFT L Association Block SysML An Association Block is an Association Class a kind of Association stereo typed by Block Like any other Block
242. s class level default value For a vehicle however the generic capacity of its FuelTank is 46 liters An abstract Vehicle block will thus configure its tank FuelTank part property by initializing it with a new capacity value This can be done with Progressive Reconfiguration that will assign the instance specification tank FuelTank to the property tank FuelTank of the Vehicle block Fig ure 226 bdd Model Vehicle ae Vehicle bdd HOWTO define property specific default values progressive configuration FuelTank lt Ar planation gt Vehicle p The static class level rt meet default value will be parts capacity L 40 0 unit Litre Be tank FuelTank 1 tank ee i overridden In MD SysML you can drag n drop ssinitialisation gt Fii InstanceSpecificatians ftom the browser onto parts in an IED to assjgn property specific default initial values initial walues y fe ee oor lt lt initialises gt 5 rou may optionally organise the illustration only tank Fuel Tank InstanceSpecifications that carry capacity 46 0 unit Litre your property specific values in a stereotyped Model lt Rationale gt gt The property specific default values a k a property specific initial values for each part are defined using the Slots of an InstanceSpecification of matching type The Magicdraw UML 3ysML plugin structure and value HOWTO guide Vehicle E hoe Figure 226 Progressive Rec
243. s and Values QUDV in OMG SysML specifica tions 1 2 for more detail 13 3 3 Creating New Value Type 13 3 3 1 Create a new Value Type using existing Unit and Quantity Kind in the SlDefinition model library 1 Create a new Value Type using diagram toolbar of SysML Block Definition Diagram or Contain ment browser context menu New Elements gt SysML Values gt ValueType 2 Specify the Unit and Quantity Kind attributes of this Value Type with a Unit and the correspond ing Quantity Kind in SlDefinition model library 3 Optional Create a new Value Type specializing another Value Type e g Quantity Real Com plex etc Model Library for Quantities Units Dimensions and Values QUDV eValueT ypes m Real ecvalue Types Unit Go metre Valuel ypes Real Quantity Kind GWDY Library SIDetinitions lengthak emodelLibrar y s SIDefinitions Units metre fquantitvEind length k eGiuantity kind lengthOK Figure 295 Value Type with the Existing Unit and QuantityKind in S Definiton Model Library 13 3 3 2 Create a new Value Type using a new Unit and an existing Quantity Kind in the SIDefinition model library 1 Create a new Unit from the diagram toolbar of Block Definition Diagram Then assign a Quan tity Kind in the SIDefinition model library to the newly create Unit 2 Create a new Value Type and specify the unit and quantity kind attributes with the Unit and Quantity Kind in step 1 a Yp
244. s or expand SysML Block Contraint Block compartment s of a Block Constraint Block 1 Right click on the Block Constraint Block symbol and select SysML Compartments group 2 To suppress or expand all SysML compartments at once you can click on Suppress All or Expand All respectively 3 You can suppress or expand single SysML compartment by check or uncheck respectively the context menu item whose label is starting with Suppress followed by the compartment name e g Suppress Parts for suppress expand the parts compartment Figure 20 SysML Diagrams Specification Enter Symbol s Properties Alt Enter Mew Diagram fo To Refactor Select in Containment Tree Alt 6 Select in Structure Tree Select in Inheritance Tree Related Elements Stereotype Edit Compartment Presentation Options oo SysML Compartments 2 Expand all Suppress All Insert Mew Attribute Suppress Constraints Insert Mew SysML Property d Suppress Parts Insert Mew Operation Ctrl alk o Suppress Properties Insert New Signal Reception CtrH alk R Suppress References Insert Mew Pork Suppress Values Create Instance Figure 20 Context menu for suppression expansion of SysML compartments NOTE e Each expanded compartment will be shown when it contains at least one properties If the compartment contains no property it will not be displayed even already expanded e The parameters compartment of each Const
245. se Case Numbers E EH m 4 Click Remove Increase or Decrease to subsequently remove increase by one or decrease by one a use case number previously ascribed 5 Click Edit to arbitrarily create a new number or change an existing number to another number Once selected the Type Number dialog will open Figure 198 Ag Type Number Figure 198 Type Number Dialog for Editing Use Case Number ii Use Case Dependency Matrix Template MagicDraw provides a use case dependency matrix template This template shows Use Case implementations with behavioral diagrams state activity sequence and communication Behavior diagrams are grouped by Behaviors State Machine Activity and Interaction For more information on this feature see the Dependency matrix in the Model Analysis section of the MagicDraw User Manual and the Dependency Matrix section in this manual 5 7 4 Using SysML Use Case Diagram Elements Inserting New Extension Points Use Insert New Extension Point to insert new extension points in a SysML Use Case diagram To insert a new extension select any of the following e Select Insert New Extension Point on the Use Case smart manipulator Figure 199 e Select Insert New Extension Point on the Use Case shortcut menu Figure 200 or e Press Ctrl Alt E A NAAA A 201 No M Anr rinht A NA 111 lann Copyright 2006 2011 lagic Inc J J J On Ql
246. set Windows Configuration Cbrl shiFt iy Close All Diagrams But Current Ctrl Shifk F4 Close All Diagrams Crl 4lt F4 Figure 237 Opening Structure Browser from Main Menu 9 2 Customizing Structure Browser Display You can customize the display of the Structure browser by using 9 2 1 Structure Browser Shortcut Menu 9 2 2 Structure Browser Toolbar 9 2 1 Structure Browser Shortcut Menu You can customize the display of the Structure browser by right clicking its background to open its shortcut menu and then mark clear display option s on the menu Display as Plain List 5 Show Inherited Structure v Show Full Types in Browser e Show Applied Stereotypes in Browser Show Auxiliary Resources Filter Figure 238 Opening Structure Browser from Context Menu 9 2 2 Structure Browser Toolbar You can also customize the display of the Structure browser by clicking the icons on its toolbar tS Gee T Figure 239 Structure Browser Toolbar Structure Browser Table 7 The Structure Browser Toolbar Icons Icons Function To display the browser as a plain list of classifi ers To show inherited structures To show full type in the browser To show applied stereotypes in the browser a a a a o o To show auxiliary resources in the browser To filter type s of elements to be shown in the browser 9 3 Display Options You can select to customize the Structure browser in six disp
247. sure fuelDemand temperature unit F temperature unit F dimension Temperature dimension Temperature ssplock gt Ey SuperFuel Fuel fuelPressure 30 lt lt block lt block gt eS lt block lt lt block HSU HSU HSU HSU internalCom internalCom internalCom internalCom bustionEngi bustionEngi bustionEngi bustionEngi nefi ne tis ne ti4 ne fif 1 Fuelinjector Fuelinjector Fuelinjector Fuelinjector fuelDemand fuelbemand TuelDemand fuelDemand lt bhlock gt O lt lt block gt eeblock g e lt block gt EJ HSU HSU HSU o E internalCom internalCom internalCom internalcom bustionEngi bustionEngi bustionEngi bustionEnal ne fi ne fi 3 ne fi 4 ne fra Fuelinjector Fuelinjector Fuelinjector FuelRail fuelDemand fuelDemand fuelDemand Figure 36 Resulting Instances After Changing Slot Value of fuelReturn Property ii To automatically instantiate a Block to be used with Paramagic Plugin 1 Right click a block and select Create Instance on the shortcut menu Figure 37 The Auto matic Instantiation Wizard dialog will open Figure 38 Note that Paramagic sample projects are available in the lt md install dir gt samples ParaMagjic directory after you installed Paramagic Plugin The Satellite mdzip sample is used to demonstrate how this feature works SYSML PLUGIN FOR MAGICDRAW SysML Diagrams 39 age Satellite E Satell
248. t 100 Functional Requirement 100 Interface Requirement 100 Numbering Requirement IDs 106 Performance Requirement 100 Physical Requirement 101 Refine 103 Requirements Table 122 Satisfy 102 Tabular Diagram 122 Test Case 101 Trace 102 Usability Requirement 101 Using Requirement 118 Using Requirement Subtypes 120 Verify 102 Requirements Table 122 S sample 6 Satisfy 102 Using Satisfy 121 search 13 Select Nested Part 56 71 96 Send Signal Action 136 Sensor 151 Sequence Node 138 Shared Property 54 95 Structure Browser 186 Structured Activity Node 137 Structured Block 17 Subsystem 15 152 Using Subsystem 46 Swimlanes 138 Swimlane Allocations 148 SysML 6 SysML project 8 System 15 Using System 46 System Boundary 152 System Context 15 Using System Context 46 T Teamwork 207 Migrating Old project 207 Working with Teamwork Project 207 Templates Report Wizard 208 Allocation Report Templates 226 Requirement Report Templates 213 Requirement Dependencies Report 221 Requirement Diagram 214 Requirement Report 216 Requirement Table Type A 214 Requirement Table Type B 215 Requirement Table Diagram Report 225 SysML Dependency Matrices 197 SysML project 9 Use Case Dependency Matrix Template 155 Test Case 101 Using Test Case 121 Time Event 136 Trace 102 U UML 6 Unit 16 Using Unit 46 Usability Requirement 101 Usage 19 Use Case 152 Dependency Matrix Template 155 Extend 153 Include 152 Inserti
249. t OMG SysML style stl located in lt md install dir gt templates SysML directory and then press Open Select the style in the Symbols properties styles panel OR If the OMG SysML style is available in the Symbols properties styles panel Figure 6 just select it 11 Copyright 2006 2011 No Magic Inc Working with SysML Projects 2 CEI OMG SysML style stl ia My Recent Documents My Documents My Computer l File name OMG SysML style stl pen m CF necro canes Figure 7 Open Dialog Importing OMG SysML Style 6 Press Make Default button and then press OK 7 The OMG SysML style is now used as default in your SysML project However such style will be applied only to new SysML diagrams yet to be created 8 If you would like to also apply such style to existing SysML diagram s open the Project Options dialog Figure 6 again select the style in the Symbols properties styles panel and then press Apply button The Select Diagrams dialog will then display Figure 8 Ly Select Diagrams ray Figure 6 2 Defining w E fal Figure 6 19 Internal OHSU Struck E Figure 6 33 Behavior CHSUY Beha kaii Figure 6 17 Internal eHybrid Sy es Figure 6 35 Detailed CHSUY Beha kaii Figure 6 22 Consolid n HSUY Struct Ea Modeling tips ModelingTips Ea Explanations Explanations i Figure 6 16 Defining ASU Struck Ea Figure 6 18 Defining ASU Struck Select All Clear All Figur
250. teSystem blocks tem Satellite Con satellitesystem coant Insi satellitesystem ins Frol satelliteSystem prot Psyl satellitesystem psy1 Weaight block blocks satelliteSyst satellteSyst F em cont ee Control m Poon 2000 Power 1000 Woon 400 Wasy S000 eblocks eblacks satellteSyst satellteSyst em ins1 em prot Instruments Propulsion Pins 2700 Fpro 4800 Wins 2700 wipro 4800 Figure 41 Example of Instance Created by Automatic Instantiation Wizard with Initialized Slots 6 Right click the Satellitelnstance02 package in the browser and select ParaMagic gt Util gt Cre ate CXI_heading Figure 42 7 Right click again and select ParaMagic gt Util gt Add default causalities The package will then be ready for ParaMagic Plugin SysML Diagrams 44 jap catellitatnstancen l bla l l m Common p Dat All E Note cam ME uistomiatian For SysML T Problem B B Satellite p o H Relations E Rationale 09 SatelliteInstancedl abe Text Box 7 _ Ela Mew Element Mew Diagram Mew Relation Open in Mew Tab Specification Use Case Numbering Requirement ID Numbering He 5 0 To mo Rodina oF Refactor Mess Select in Structure Tree Related Elements Tools Stereotype Rename F2 Copy Ctrl c Copy as URL Paste Ctrl V Cut Ctrl Delete Delete Create Symbol Cbrl ShiFk
251. tes Profile xml H Eg SysML S sML Profile mdzip H EA UML Profile For Schedulabilty Performance and Time Specifica J ssociation HSU Model Department OF Motor Vehicle HSU be 4ssociation HSUVModel Driver HSUYModel HSU UseCases be 4ssociation HSUVModel Driver HSUYModel HSU UseCases be 4ssociation HSUVModel Driver HSUYModel HSU UseCases be 4ssociation HSUVModel Driver HSUYModel HSU UseCases a Association HSUModel HybridSUY b HSUY Model HSU Str a Association HSU Model HybridSUY bk HS5UYModel HSU St a Association HSU Model HybridSUY ciHSUY Model HSL Str i Al Aeenristinn HE WM edol Hukhrid S WY SMe dol HS I be I Figure 259 Create Diagram Dialog 2 Type the name of the editable matrix you want to create and select its owner from the element tree 3 Click OK ii To create a SysML Edtiable Matrix using the main menu 1 Click Diagram gt SysML Matrices on the main menu Figure 260 2 Select a SysML Edtiable Matrix that you want to create from the submenu Figure 260 202 Copyright 2006 2011 No Magic Inc Dependency Matrix ms Options Tools Analyze Teamwork Window Help Class Diagrams Ctrl 1 S Al eS BS e te SS RS Communication Diagrams Ctrl 3 al E E fia E fied E R l E z n Protocol State Machine Diagrams Ctrl 6 fl eel Bel EH 5 all T Implementation Diagrams Ctrl 8 hh AE ie Composite S
252. that executes its actions in order Input Pin UML An Input Pin is a pin that holds input values to be consumed by an action Input pins are object nodes that receive values from other actions through object flows Output Pin UML An Output Pin is a pin that holds output values produced by an action Output pins are object nodes that deliver values to other actions through object flows Value Pin UML A Value Pin is an input pin that provides a value to an action that does not come from an incoming object flow edge Swimlanes UML Swimlanes are used to organize actions and sub activities according to the class allocated to each swimlane header and partition an activity diagram 5 6 3 SysML Activity Diagram Specific Features SYSML Activity Diagram specific features include i Name Display Mode Action shortcut menu ii Behavior Action shortcut menu ili Select Operation Call Operation Action shortcut menu iv Dynamic Centerlines v Streaming Parameter i Name Display Mode Action shortcut menu Button hot key eh ered m SHIFT 1 jo SHIFT O mM SHIFT V E SHIFT W Select Name Display Mode on the action shortcut menu Figure 175 to show a the name of the action b the behavior name of the action or c both Figure 176 SysML Diagrams T Action name Behavior af i 7 Specification Enter Symbol s Properties Alt Enter Mew Diagram 0 To Refac
253. the QUDV specification To create for example the celsius Temperature unit in the SI Definitions model library 1 Create a Unit using either Browser Shortcut Menu or Diagram Toolbar of BDD 2 Since there is another temperature unit already defined in the SI Definitions model library i e kelvin and the conversion from kelvin to celsius is of the format defined in Annex 3 5 2 1 AffineConversionUnit in OMG SysML specifications 1 2 choose the AffineConversionUnit to be the base classifier of the newly created unit 3 Open the unit specfication dialog 4 Assign the name of the unit to be celsius Temperature 5 Select the corresponding Quantity Kind e g celsius TemperatureQk or thermodynamic Tem peratureQk 6 Select the Slots property group and then assign the corresponding slot values e name String mandatory celsius temperature e quantityKind QuantityKind mandatory celsius TemperatureQK e isInvertible Boolean true always true for AffineConversionUnit e symbol String degree C e referenceUnit Unit kelvin e factor Rational 1 1 means 1 1 or 1 e offset Rational 273 15 1 means 273 15 1 or 273 15 where Rational is of the format numerator Integer denominator Integer which refers to a rational number numerator denominator see Annex C 5 Model Library for Quantities Units Dimension
254. the activities into the diagram you want to create If you do not select this option one diagram will be created for each activity selected Figure 186 e Then click Next if you want to customize the symbol properties of the diagram s to be created step 3 below Otherwise click Finish Figure 186 e The Children Count column Figure 186 upper right hand side shows the number of behaviors included plus the number of object nodes owned if the Add contained Object Nodes option is selected e The Add contained Object Nodes option is selected by default This option will display the types of the object nodes and connect them to the composition with activities containing object nodes e The number of behaviors included also depends on the Search recursively option selected by default If not selected the search will be conducted at only one level of the activity ies selected If selected the search will be conducted for each activity selected and for those activities invoked by call behavior actions in the selected activity recursively Activity Decomposition Hierarchy Wizard 0 1 specif d k Add all structures into one diagram Specify name and package 2 Select structure H 3 Accelerate HSUY Model Behavior Fo O 3 Specify symbols properties am ProvidePower HSUY Model Behavior 3 a4 Figure 11 10 Continuous system example 1 Opera a4 DecomposeMe test decomposition a4 ControlelectricPower HSU Model B
255. thout hav ing to display its parent s first 5 2 4 Displaying Structures of Blocks in Compartments or in IBDs MagicDraw Composite Structure diagrams will not let you display the already defined internal structures of Blocks reused as parts in other structures deep nested structures The same problem exists when you need to modify extend existing structures in subtypes Composite Structure diagrams will only let you display e parts e ports on the frame e ports on every part and SysML Diagrams e paths for every part and port Thus to redisplay an internal structure in another structure you have to recreate the internal structure manu ally The graphical layout must also be applied manually making it a time consuming activity With the Display Internal Structure feature you can copy and paste display an existing structure diagram defining a Block Class in either e the structure compartment of that Block a subtype of that Block a part typed by that Block ora part typed by a subtype of that Block or e another diagram defining either a subtype of that Block or that Block itself With this feature you can now display the already defined internal structures of Blocks reused as parts in other structures deep nested structures To redisplay a Block structure already defined in at least one structure diagram 1 Suppose there is the FrontWheelsAssembly IBD having the FrontWheelsAssembly block as its context
256. ting the items that flow in or out or typing a non atomic Flow Port with a Flow Specification which lists multiple items that can flow In general Flow Ports are intended to be used for asynchronous broadcast or send and forget interactions Note that only non atomic Flow Ports can be conjugated Once conjugated all the direc tions of the typing Flow Specification s items are negated Connector See Section 5 4 1 for description P Binding Connector See Section 5 4 1 for description Fa SysML Diagrams Button Element hot key Item Property SysML An optional property that relates the flowing item to the instances of the con ki nector s enclosing block This property is applicable only for item flows assigned to connectors The multiplicity is zero if the item flow is assigned to an Association 5 4 3 SysML Parametric Diagram Specific Features SysML Parametric Diagram features include Display Parameters and the other seven specific features similar to IBD These are i Display Parts Diagram shortcut menu ii Display Ports Property shortcut menu iii Edit Compartment Property shortcut menu iv Show Default Value and Show Slot Type Property shortcut menus v Provided Required Interfaces Port shortcut smart manipulator menu vi Display Suppress Structure Compartment Property shortcut menu vii Select Nested Part For more information on these features see the SysML IBD Specific Features sec
257. tion i Display Parameters Property shortcut menu This feature enables you to display the constraint parameters of a constraint block on a Constraint Property typed by the Constraint Block To display constraint parameters 1 Either i select Display Parameters on the property shortcut menu Figure 124 or ii click the Display Parameters icon on the property smart manipulator Figure 125 l E r 1 saconstraint Specification Enter Symbol s Properties Alk Enter d d 50 To Refactor Select in Containment Tree Alt B Related Elements i Stereotype d Display Parameters Edit Compartment Show Stereotypes Show Owner Used By Cbrl Alk U Wrap Words Depends On Cerl Alk o Show Tagged Values b Figure 124 Shortcut Menu for Displaying Constraint Parameters SysML Diagrams lt constraint Constraint Block Display Parameters Figure 125 Smart Manipulator for Displaying Constraint Parameters 2 The Select Parameters dialog will open and the constraint parameter s owned by the type of the constraint property will be listed in the dialog Figure 126 3 Select constraint parameters to be shown on the constraint property symbol The selected con straint parameters will be displayed as small square boxes Figure 127 p Select Parameters P parameteri Constraint Block P parameter2 Constraint Block P parameter3
258. tiyknd NO pomon Dervedumt rss DervedOuaniykind Pa pasoal Deredunt pressureOK i Dervedavariy nd rad eian DevedUnt lanl Derkedouantiykind Model Library for Quantities Units Dimensions and Values QUDV Quantity Kind a m ooo S semers Dorvedunt deaieConducianeeQK Daveauntvind sf sieraden Deedee Dervectuariprd Sv seven Deed dos uvatOK DervesOuanibind vo volt DerivedUnit electricPotentialDifferenceQK DerivedQuantityKind watt DerivedUnit powerQK DerivedQuantityKind Wb weber DerivedUnit DerivedUnit magneticFluxQK DerivedQuantityKind DerivedQuantityKind E stacterwne aa e ane a DerivedQuantityKind sionUnit Q ohm DerivedUnit electricResistanceQK DerivedQuantityKind 13 2 Migrating Existing SysML Project To Use QUDV Model Library If your SysML project was created by an older version of SysML Plugin or by the SysML without QUDV tem plate QUDV is not used in your project yet To migrate your SysML project to use QUDV model library e Using QUDV Model Library in SysML Project e Replacing Modifying Existing Value Types e Modifying Units and Quantity Kinds of Existing Value Types 13 2 1 Using QUDV Model Library in SysML Project To use QUDV model library in your SysML project 1 Open your SysML project 2 Select File gt Use Module on the main menu 3 The Use Module dialog will then open 4 In step 1 Select module select From predefined location radio button and then select lt
259. tomated refactoring method in our newly introduced promising Refactoring tools group Extract Structure allows you to easily select a portion of an existing system structure and transform it into another reusable Block or Subsystem which may then be used as parts in many other structures In addition this Extract Structure feature can also play a move or decompose role when a structure becomes too complex and requires to be decomposed into several smaller reusable parts Recursive decomposition of structure and behavior is an important aspect of the iterative development process This feature is particularly useful for the automotive aerospace and defense communities for modeling com plex systems of systems and building reusable components To extract a new structure from an existing structure in a classifier 1 In an Internal Block Diagram or a structure compartment Figure 95 right click a portion of the internal structure part s which you want to move or reuse see the red selection rectangle These selected symbols must be owned by the same Classifier TRSMCmed 9 w ICECmds it om lt lt block gt fi Fuelinjector 4 ICED ata EEF uelF iting fuelDelivery fuelSupply Fuel Figure 95 Internal Block Diagram Before Extracting a Structure SysML Diagrams dif l v Show Diagram Frame 2 Torque BO Z eee Hw FrontWheel 1 Show Owner Pit Toro
260. tor Select in Containment Tree Related Elements Stereotype Edit Compartment Show Stereotypes Show Tagged Values Show Owner Wrap Words Show Action Mame Show Behavior Name El Show Both Figure 175 Action Shortcut Menu for Name Display Mode fa Fa Action name Behavior h Action el P Behavior J i Show Action name Show Behavior name Show both Figure 176 Name Display Modes You can also change the Name Display Mode of an action in the action Symbol Proper ties dialog ii Behavior Action shortcut menu Select Behavior from the action shortcut menu to choose the Behavior of the action Figure 177 SysML Diagrams Specification Enter Symbol s Properties Alt Enter Mew Diagram Go To Select in Containment Tree Related Elements Stereotype Edit Compartment Show Stereotypes Show Tagged Values Show Owner Wrap Words Name Display Mode lt UNSPECIFIED gt a4 Activity Diagram a4 Behavior Activity Diagram Figure 177 Action Shortcut Menu for Behavior Selection You can also change the behavior of an action in the action Specification dialog iii Select Operation Call Operation Action shortcut menu Click Select Operation on the Call Operation Action shortcut menu Figure 178 to select an operation for that Call Operation Action Figure 179 SysML Diagrams F CallOperation Select Operation BLOCK operatio
261. traction Specification and lower level of abstraction Realization elements providing visibility of other related elements This section allows you to visu alize and verify that Analysis Design and Implementation model elements are well covered Report Wizard and Template Coverage Analysis The report section lists the elements for coverage analysis at higher and lower levels of abstraction Not covered parts for verification of implementation completeness and redundant artifacts are indicated in this report Coverage analysis is indicated by traceability properties pointing to higher level of abstraction Specification and lower level of abstraction Realization elements providing visibility of other relater elements The main objective of this report is to visualize and verity that Analysis Design and Implementation model elements are all covered For example all requirements are covered with at least one test case to verify them Note MagicDraw can automatically create advanced tables presenting the impact of a change ona set of artifacts at any level in the development process Forward Traceability Realization Forward traceability ensures that all specified requirements are implemented Realizing Requirements for Leaf Requirements The Realizing Requirements property of a Requirement shows how the Requirement is directly realized by other Requirement s in lower level of abstraction Requirements are connected through
262. tructure Diagrams Ctrl 9 Interaction Overview Diagrams Ctrl 0 Custom Diagrams SysML Diagrams el A SysML Allocation Matrices Customize cy SysML Satisty_Requirement Matrices Diagram Wizards vV SysML Verify_Requirement Matrices Previous Diagram Alt Let Next Diagram Alt Right Load All Diagrams Figure 260 SysML Matrices Menu 3 A dialog of the selected matrix will open For example select SysML Allocation Matrices the SysML Allocation Matrix dialog will then open Figure 261 Click the Add button in the dialog SysML Allocation Matrices Create a new SysML Allocation Matrix Open a diagram by choosing it from the list of SysML Allocation Matrices available within a project 8 Allocation Matrix me HU iode Coss Figure 261 SySML Allocation Matrix Dialog 203 Copyright 2006 2011 No Magic Inc Dependency Matrix 4 The Create Diagram dialog will open Figure 259 Type the name of the editable matrix you want to create and select its owner from the element tree 5 Click OK iii To create a SysML Editable Matrix using the Containment Tree 1 Right click the element which will be the owner of the SysML Editable Matrix in the Contain ment Tree The element shortcut menu will then display Figure 262 lt gt Ms siti dy be PE Le A AS C Pred _ t H g E E a New Element Z E I OO EE O NewDiagam S
263. ts beyond e constraint parameters e constraint properties that hold internal usages of constraint blocks e binding connectors between its internally nested constraint parameters e constraint expressions that define an interpretation for the constraint block e general purpose model management and crosscutting elements ConstraintBlock 2 Any classifier which specializes a Constraint 10 3 2 1 Block must also have the ConstraintBlock stereotype applied ConstraintBlock A Binding connectors are used to bind each 10 3 2 1 parameter of the constraint block to a property in the surrounding context ConstraintProperty 1 A property to which the ConstraintProperty 10 3 2 2 stereotype is applied must be owned by a SysML Block Discrete 1 The discrete and continuous stereotypes 11 3 2 3 cannot be applied to the same element at the same time non active NoBuffer 1 The nobuffer and overwrite stereotypes 11 3 2 4 cannot be applied to the same element at the same time Overwrite 1 The overwrite and nobuffer stereotypes 11 3 2 5 cannot be applied to the same element at the same time AllocateActivityParti A The represented element of the activity parti 19 0 2 tion tion which is applied with AllocateActivityPar tition stereotype should be the Property Validation Constraint AllocateActivityParti tion Copy Copy Copy Copy Copy Requirement Requirement
264. ue Pract structure _ Refactor torqueOut Torque spline Show Diagram Info torqueln Torque ce InternalCombustionEngine Find in Diagram Related Elements lt eblock gt m fi Fuellnjector 4 E E Fitin Window ti T H E ie zoom In dist Zoom uk Di Port ICEFuelFitting zoom To Selection Grid Print Active Diagram fuelSupply Fuel Prink Selected Layout Figure 96 Shortcut Menu Extract Structure Refactoring 2 Select Refactor gt Extract Structure Figure 96 The Extract Structure wizard dialog will open listing the three steps to extracts a structure i Create a classifier ii Select part s and iii Create a property Figure 97 p7 Extract Structure 1 Create a classifier Classifier name 2 Select port s FrontWheelAssembly 0000 Speake OLODETER Classifier kind reate a property Block Class SyvsML Profile Blocks Specify attributes of the new classifier bo move selected O Data parts properties E HSUvModel beg Explanations H E HSU Analysis H E HSU Behavior H E HSUY Requirements EF HSU Structure H E HSU Interfaces o Accelerator Diagram Type SysML Internal Block Diagram we Figure 97 Create a Classifier Step 3 Step 1 Create a classifier e Specify the name of the classifier you want to create and use for holding the structure to be extracted called extracted classifier in the Classifier name box
265. ue Type adds an ability to carry a unit of measure of a quantity kind associated with the value If these additional characteristics are not required then UML Data Type may be used it is however not recommended by SysML 1 2 specification In general define quantity kinds first followed by units and their quantity kinds After that define value types and their units and quantity kinds However users often forget to enter the corresponding quantity kind of a value type with unit SysML Plugin provides an active validation constraint for filling the correct quantity kind to a value type with unspecified quantity kind by selecting the Apply valid quantity kind to the Value Type option See the Validation section below for more details N Units LiWantity Kind Gal evalleTYPE engthak metre SimpleUnit name metre evalue Types quantitvKind lengthak unit Col metre symbol m Figure 44 Value Type Example Figure 45 Unit Example NOTE SysML Plugin contains a model library that holds more than 80 units and quantity kinds of SI system to be used as references of Value Type elements Flow Specification A Flow Specification specifies inputs and outputs as a set of flow properties It has a flowProperties compart ment that lists the flow properties A flow specification is used to type Flow Ports in order to specify items which can flow via the ports A The only valid attribute of a Flow Specificati
266. umeration is a kind of Data Type whose instances may be any of the user pre defined enumeration literals It is possible to extend the set of applicable enumeration literals to other packages or profiles 5 1 2 SysML BDD Toolbar Button hot key Block See Section 5 1 1 for description A Structured block is a Block element that contains an Internal Block Diagram and a hyperlink to it B Structured Block SysML SHIFT B Constraint Block See Section 5 1 1 for description Domain See Section 5 1 1 for description External See Section 5 1 1 for description Subsystem See Section 5 1 1 for description System See Section 5 1 1 for description System Context See Section 5 1 1 for description Value Type See Section 5 1 1 for description Data Type See Section 5 1 1 for description Quantity Kind See Section 5 1 1 for description 17 Copyright 2006 2011 No Magic Inc SysML Diagrams Button Element hot key Unit See Section 5 1 1 for description Enumeration See Section 5 1 1 for description cay K Instance UML To create an instance specification of a classifier E SHIFT O Interface See Section 5 1 1 for description 5 1 Flow Specification See Section 5 1 1 for description Port UML A Port defines an interaction point on a Block or a part allowing you to specify what can flow in out of the Block part or what services the block part require
267. up to open the Provided Required Interfaced pane Figure 72 OR Figure 71 Port Smart Manipulator Menu Provided Required Interfaces e Click a port in a diagram to open its smartmanipulator menu and then select the Provided Required interfaces icon to open the Provided Required Interfaced pane Figure 72 History P trsm HSUvModel sHSUY Structure FowerControll 4 P trsm Provided Required Interfaces ae Documentation Hyperlinks Ba ai mt Bs Usage in Diagrams T ui Template Parameters E Inner Elements I ICECmds Provided Relations Tags Constraints Language Properties Provided Required Figure 72 Port Specification Dialog Provided Required Interfaces Group Only typed ports can realize use interfaces 2 Click Add Figure 72 and then select either i Provided or ii Required 64 Copyright 2006 2011 No Magic Inc SysML Diagrams Case 1 If the port is typed the Select Interface dialog will open Figure 73 You can then either e select any of the existing interfaces and flow specifications to be used as the Provided Required Interface of the port or e click Create to create a new interface The interface specification dialog will then be displayed prompting you to type in its name The new interface will then be used as the Provided Required Interface of the port X Select Interface H 9 I ICECmds E IIEPCCmd E IIEPCData E ITRSMCmd H ITRSMData
268. ure 129 respectively s lt constraint gt Constraint Block parameters parameter2 param Pinding Connector Figure 128 Constraint parameter smart manipulator E 2oValue Ty pe ry value property Value Type me Gl E Figure 129 Smart manipulator of a part 2 If you have clicked i the Binding Connector button on the toolbar select a part as the con nector s origin but if you clicked ii the Binding Connector icon from the smart manipulator go directly to step 3 3 Select a part constraint parameter as the connector s destination 5 5 SysML Requirement Diagrams SysML Requirement Diagrams provide modeling constructs to represent text based requirements and relate them to other modeling elements These requirement modeling constructs are intended to provide a bridge between traditional requirement management tools and other SysML models Requirement diagrams display requirements packages other classifiers test cases rationales and relation ships Possible relationships available for Requirement diagrams are containments deriveReaqt and require ment dependencies Copy Refine Satisfy Trace and Verify The callout notation can also be used to reflect the relationships of other models Requirements can also be shown on other diagrams to illustrate their relationships to other modeling elements SysML Diagrams 5 5 1 SysML Requirement Diagram Met
269. ure Compartment Figure 83 Part with Structure Compartment NOTE Regarding a typed property with its structure compartment displayed you can also drag a Classifier to the compartment to create a new property part typed by that classifier SysML Diagrams vii Select Nested Part Use the Select Nested Part button on the IBD toobar to display a nested part inside a given context We will demonstrate how to use the button using the example in Figure 84 bdd Package data aa BOD lt block e lt block lt lt block gt s lt block gt lt lt block Block Block Blocks Block4 Block4S fares fats part parts O Pattla Block Part2a Block4 Part3a Block Partda Blocks eae BIOCKs ee a Figure 84 BDD with Blocks and Their Properties To display a nested part 1 Click the Select Nested Part button on the IBD toolbar 2 Click on the diagram pane The Select Element dialog will appear showing all parts proper ties nested inside the context of the IBD for example Block1 Figure 85 ibd Block Block fij Block ie Select Element Model B E Block H CE Partla Block Part2a Block4 0 Blocks H CH Partib Block Park3a Block4 i CE Part a Block Figure 85 Select Element Dialog 3 Select a part and click OK If Part4a typed by Block5 is selected the following part will be dis played Figur
270. us vi Display Suppress Structure Compartment Property shortcut menu v Provided Required Interfaces Port shortcut smart manipulator menu vii Select Nested Part i Display Parts Diagram shortcut menu If you have already defined the part s property ies of a Block you can then display the part s on any IBD having the Block as its context To display parts in an IBD 1 Right click an IBD and select Related Elements gt Display Parts Figure 59 All the parts selected will be listed in the Select Parts dialog Figure 60 Specification Diagram Properties Shift Enter Show Diagram Frame Show Diagram Info Show Owner 0 To Select in Containment Tree Alt E Find in Diagram Chrl ShiFk D Related Elements b l Grid Display Parts a Print Active Diagram Show Diagrams in Full Screen Fil Close Diagram Ctrl F4 Close All Diagrams Buk Current Ctrl Shift F4 Close All Diagrams Ctrl Alk F4 Figure 59 Diagram Shortcut Menu to Display Parts Properties of the Context of IBD SysML Diagrams p Select Parts Select Parts constraint property Constraint Block Block part property BLOCK Block reference property BLOCK Block shared property BLOCK Block amp UML property Class Block 4 value property ValueType Block Figure 60 Select Parts Dialog 2 Select parts and click OK to show the sele
271. used to type the proper ties of the requirement subtypes Table 4 Non normative Enumeration for Requirements Enumeration Enumeration Literals Function RiskKind High To indicate an unacceptable level of risk Medium To indicate an acceptable level of risk Low To indicate a minimal level of risk or no risk Verification Analysis To indicate that verification will be performed by techni MethodKind cal evaluation using mathematical representations charts graphs circuit diagrams data reduction or other representative data Analysis also includes the requirement verification under conditions which are simulated or modeled where results are derived from the analysis of the results produced by the model SysML Diagrams Enumeration Test Cases Enumeration Literals Demonstration Inspection Test a A Function To indicate that verification will be performed by the operation movement or adjustment of the item under specific conditions to perform the design functions with out the record of quantitative data Demonstration is typically considered the least restrictive verification type To indicate that verification will be performed by exam ining the item reviewing descriptive documentation and comparing the appropriate characteristics with a predetermined standard to determine conformance to the requirements without the use of special laboratory equipment or procedures To indicate that verification w
272. would like to create Figure 265 Dependency Matrix aS ControlElectric Q at ProvideElectric ajm HSU Behavior Ea Acceleratei transModecmd E ProvidePowert transMo m e el al ProportionPow m me ele emg HSUvMode Be efi epc H5LvModel Be BIG peu H5UvModel Soe e eB at ProvideGasPo Co al ProportionPower O a2 ProvideGasPower elati E l O a3 ControlElectricPa Delete Relation a4 ProvideElectricPa EF HSU Structure A A PowersSubsystem i OF emg HSUVModel HSU Cal epe HSUVModel HSU CA pcu HSUVModel sHSU Dependency List Figure 265 Editable Matrix Context Menu ii Removing Existing Dependencies You can also remove an existing dependency of each matrix by double clicking on that particular dependency that you want to remove Another way to remove a dependency is by right clicking on the intersection of the row and column elements Then select Delete Relation and select the dependency you would like to delete Figure 265 iii Dependency List You can view a list of dependencies associated with a cell in an editable matrix by right clicking on the cell and then select Dependency List from the context menu Figure 265 The Dependency List dialog will then dis play Figure 266 Dependency List Dependency List Dependency Name Row Element Name Direction Column Element El oe Alocate HsU ai ProportionF D aZ Prov
273. ws A decision afi node has one incoming edge and multiple outgoing activity edges G Merge UML A Merge is a control node that brings together multiple alternate flows It is not ai used to synchronize concurrent flows but to accept one among several alter nate flows G Fork Join Horizontal UML To help control parallel actions K Fork Join Vertical UML To help control parallel actions u SHIFT K Exception Handler UML An Exception Handler is an element that specifies a body to execute in case Fa the specified exception occurs during the execution of the protected node Structured Activity Node UML A Structured Activity Node is an executable activity node that may have an r expansion into the subordinate nodes The structured activity node represents a structured portion of the activity that is not shared with any other structured node except for nesting ig Expansion Region UML I An Expansion Region is a structured activity region that executes multiple times corresponding to the elements of an input collection Conditional Node UML A Conditional Node is a structured activity node that represents an exclusive i if choice among alternatives Loop Node UML A Loop Node is a structured activity node that represents a loop with the setup test and body sections Se a f k SysML Diagrams Element Sequence Node UML A Sequence Node is a structured activity node
274. wser 9 You can then use this browser to calculate the values of the properties For more information on how to use this browser see Paramagic User Manual 5 1 5 Using SysML BDD Elements SYSML blocks can be used throughout all phases of system specification and design and can be applied to many different kinds of systems These include modeling either the logical or physical decomposition of a sys tem and the specification of software hardware or human elements A Block is a modular unit that describes the structure of a system or an element It may include both structural and behavioral features such as properties and operations that represent the state of the system and behavior that the system may exhibit Some of these properties may hold parts of a system which can also be described by blocks A block may include a structure of connectors between its properties to indicate how its parts or other properties relate to one another Any reusable form of description that may be applied to a system or a set of system characteristics can be described by a block Such reusable descriptions for example may be applied to purely conceptual aspects of a system design such as relationships that hold between parts or properties of a system Parts properties in these systems can interact by many different means such as software operations discrete state transitions flows of inputs and outputs or continuous interactions Connectors owned by
275. xclude elements from read only modules default true if this option is selected select ing the check box means true read only modules for example read only profiles will not be actively validated 3 Mark in tree and diagrams default true if this option is selected selecting the check box means true invalid elements will be marked with small icons in the Containment Tree and highlighted in the diagrams 4 Ignored validation suites you can enter the active validation suite s you would like to exclude from the Active Validation process 5 Minimal severity you can specify the minimal severity level of the constraints to be validated against There are five levels of severities e gt debug All constraints will be included in the active validation e gt info Constraints with infos warnings errors or fatal severities will be included e gt warning default Constraints with warnings errors or fatal severities will be included e gt error Constraints with error or fatal severities will be included e Fatal Only constraints with fatal severities will be included To open the Active Validation Options dialog 1 Click Analyze gt Validation gt Active Validation Options Figure 219 The Project Options dialog will open Figure 218 Validation Model visualizer Metrics Compare Projects Dependency Matrix Validation Validation Validation Options Active Vali
276. xisting values with the values of the selected node Figure 143 X Question The Packaged was customized with the different numbering Format Do you want to overwrite the existing numbering Format of Packaged vee To All Mo To All Figure 143 Question Dialog Recursive Numbering Confirmation 8 You can click the Clear button under the Separator box to remove the Package specific Num bering Configuration For example select the HSUV Specification package in the browser Fig ure 142 and click the Clear button The Package specific Numbering Configuration of the HSUV Specification package will then be removed Thus the available numbering configura tion in an owning package will be used instead which is in this case the Data package 9 Click OK Figure 140 to update the renumbered requirement IDs to your model or click Can cel Figure 140 to ignore the requirement IDs numbered using this dialog SysML Diagrams ii Automatic Numbering Once this functionality is turned on the IDs of the newly created requirements will be numbered automatically To number requirement IDs automatically 1 Click Options gt Project on the main menu The Project Options dialog will open Figure 144 Ag Project Options Ej General p i oject options HE9 Diagram Info E Symbols properties styles A Default Default H Shapes E Paths Fe ph Diagram o Stereotypes H E Default model propert
277. xt Specific Value Compartments You can display or suppress the Context Specific Value Compartment of a part using either i the Symbol s Properties dialog or ii the part shortcut menu i Using the Symbols Properties Dialog X N Co Copyright 2006 2011 No Magic In Context Specific Value Compartments To open the Symbol s Properties dialog e Either right click the part symbol and select Symbol s Properties or select the part symbol and press Alt Enter To display a compartment using the Symbol s Properties dialog e In the Symbol s Properties dialog set the value of the Suppress Context Specific Values symbol property under the Context Specific Values group to false by clearing the check box Figure 228 To suppress a compartment using the Symbol s Properties dialog e In the Symbol s Properties dialog set the value of the Suppress Context Specific Values symbol property under the Context Specific Values group to true by selecting the check box Figure 228 Ad Pro perties Part f lt lt PartProperty gt gt Show Operation Signature true Show Operation visibility true Show Operation Stereotype true Show Operation Properties true Show Operation Constraints False Show Operation Parameter False Suppress Context Specific true Context of Context Specifi EQ Suppress Context Specific alues Suppress Context Specific values compartment Apply Style Default nal
278. y l 2 Eco Friendiness hu 2 1 Emissions a C 3 Ergonomics 4 Qualification io CE 4 1 SafetyTest Mumbering Style Separator Figure 141 Example of Numbered Requirements gt Il Prefix 6 You can change the Numbering Style Prefix and Separator values defined in the HSUV Specification package called Package specific Numbering Configuration to renumber the requirements in this package Figure 142 110 Copyright 2006 2011 No Magic Inc SysML Diagrams Ag Requirement ID Numbering gt a HSUY Model HE Explanations H E HSU Analysis H E HSU Behavior ARR HSU Requirements Bee Eee ECR REO 1 Capacity beC REQ 1 1 FuelCapacity C REQ 1 2 PassengerCapacity he REQ 13 CargoCapacity l REQ 2 Eco Friendiness LOW REQ 2 1 Emissions oe C REQ 3 Ergonomics C REQ 4 Qualification i CA REQ 4 1 SafetyTest w Prefix Separator I k Figure 142 Customizing Numbering Style Prefix and Separator Values Defined for a Package hI 7 You can click the Recursive Renumber button to renumber all requirements that are recur sively contained inside the selected node The Numbering Style Prefix and Separator which are defined in the selected node will be used for recursive renumbering If the Package specific Numbering Configuration of the lower level nodes exists then a message box will open to ask whether to replace the e
279. y Property i stereotypes AbstracthefererncePropaearty Property OOO O LEl Ls L Fl Lu Stereotypes stereotypes stereotypes stereotypes PartProperty SharedProperty ReferenceProperty ValueProperty Property Property Property Property Figure 56 MagicDraw SysML Properties Metamodel SysML Diagrams Icon Description Part Property MDSysML Cr A Part Property is a property that specifies a part with strong ownership and coinciden tal lifetime of its containing Block It describes a local usage or a role of the typing Block in the context of the containing Block Every Part Property has composite Aggrega tionKind and is typed by a Block Part Properties are displayed in the parts compart ment Shared Property MDSysML A Shared Property is a property that specifies a shared part of its containing block Every Shared Property has shared Aggregationkind and is typed by a block Shared Properties are displayed in the references compartment Reference Property MDSysML CH A Reference Property is a property that specifies a reference of its containing Block to another Block Every Reference Property has none AggregationKind and is typed by a block Reference Properties are displayed in the references compartment Value Property MDSysML ca A Value Property is a property that specifies the quantitative property of its containing Block Every Value Property has composite
280. y rectangle Subsystem UML A Subsystem is treated as an abstract single unit It groups model elements by representing the behavioral unit in a physical system Include UML An Include uses relationship from use case A to use case B indicates that an instance of the use case A will also contain the behavior as specified by B Button hot key F E Pa mi Ki pel t SysML Diagrams Button Element hot key Extend UML An Extend is a relationship from an extending use case to an extended use A case specifying how and when the behavior defined in the extending use case can be inserted into the behavior defined in the extended use case The E extension takes place at one or more specific extension points defined in the extended use case Choose a different Extend direction from the toolbar to draw a line with an opposite arrow end Association UML An Association represents a semantic relationship between two classifiers It ye is used for referencing two Blocks with one another thus creating two Refer ence Properties at both ends The aggregation values of both ends of an S Association are none Generalization UML A Generalization is a taxonomic relationship between a more general classifier and a more specific one Each Instance of the specific classifier is also an indirect Instance of the general classifier Thus the specific classifier indirectly G has the features of th
281. y typing the Flow Port with a specification of things that flow This can include typing an atomic Flow Port with a single type Block Value Type or Signal rep resenting the items that flow in or out or typing a non atomic Flow Port with a Flow Specification which lists multiple ttems that can flow In general Flow Ports are intended to be used for asynchronous broadcast or send and forget interactions Note that only non atomic Flow Ports can be conjugated Once conjugated all the directions of the typing Flow Specification s items are negated 5 2 2 SySML IBD Toolbar Button Element hot key Value Property See Section 5 2 1 for description C Part Property See Section 5 2 1 for description CF SysML Diagrams Button Element hot key Shared Property See Section 5 2 1 for description Reference Property See Section 5 2 1 for description Ci Constraint Property See Section 5 2 1 for description Distributed Property See Section 5 2 1 for description Co Select Nested Part Click this button to display a nested part inside a given context For more infor mation see Section 5 2 3 SysML IBD Specific Features vii Select Nested Part Flow Property SysML A FlowProperty signifies a single flow element that can flow to from a block Flow properties are defined directly on blocks or flow specifications that are those specifications which type the flow ports Flow properties enable item flows across connectors
282. ype true Show Operation Properties true Show Operation Constraints False Show Operation Parameters Direction Kind False Show Attribute Type Show attribute type in internal properties compartments Apply Style Default we Make Default Figure 225 Symbol s Properties Dialog SysML Internal Attributes and Operations 8 Context Specific Value Compartments 8 1 Progressive Reconfiguration Progressive Reconfiguration enables MagicDraw SysML to handle a wide range of systems engineering config uration tasks Progressive Reconfiguration continuously applies the following values 179 Copyright 2006 2011 No Magic Inc Context Specific Value Compartments e Static class level default values e Inherited Property specific initial values e Redefined Property specific initial values e Property specific initial values Property specific initial values are specific to the usage of a Block as a Part Property in a higher context i e another structured block or assembly If there are many Part Properties of the same type these Part Proper ties may have different property specific default values and will then be initialized differently Property specific initial values are managed by the higher context structured block which owns the Part Prop erties that initialize or configure their possibly different values on instantiation For example the generic capacity of a FuelTank not any particular one is 40 liter
283. ysML Values Clear the Propagate SysML Values check box to disable the Value Propagation mech anism Copyright 2006 2011 No Magic Inc Structure Browser 9 Structure Browser The Structure browser allows you to browse for deep nested structures of the structure classifier in your model The property nodes which are shown inside the property node the parent property node are the properties of the classifier that type the parent property node In Figure 236 the node diameter m represents the property diameter m of the classifier Cylinder Liner and also the property cylinderLiner Cylinder Liner is the prop erty of the classifier Engine J Brake System E Cam Shaft EG car l CE engine Engine 3 cylinderLiner Cylinder Liner diameter m cylinderHead Cylinder Head t intakeValves Intake Valve 8 texhaustValves Exhaust Valve pistons Piston 4 starterMoator Starter Motor tinjectionNozzles Injection Nozel t distributor Distributor sparkPlugs Spark Plug 4 camShaft Cam Shaft jiii Figure 236 Structure Browser 9 1 Opening Structure Browser You can open the Structure browser by clicking Window gt Structure on the main menu Figure 237 186 Copyright 2006 2011 No Magic Inc Structure Browser window Messages Window Ctrl M Te Containment fe Structure Inheritance Diagrams Model Extensions Search Results Documentation oom Properties Re
284. ysML project with three requirements and a Copy depen dency illustrates how this Active Validation feature works Figure 210 s lt requirement gt CE _ Requirement 2 COpYyE screquirement gt CE Requirement 1 s lt requirement E lt lt COpY Requirement 3 Figure 210 Invalid Elements Detected by the Active Validation The model in this project was designed so that Requirement 1 copies Requirement 2 and Requirement 3 at the same time However one of the constraints of a Copy dependency is that a requirement cannot copy more than one requirement at a time Thus this model is invalid since some elements are invalid against the constraint 2 Whenever an element is invalid it will be highlighted in the diagram copy in the example Figure 210 On the status bar at the bottom of the screen Figure 211 and 212 e a notification symbol info warning or error and e number s and severity ies of invalid element s will be displayed For example amp 4 W in Figure 211 means that there are 4 invalid elements violating constraint s of the warning severity o amp 1 E 7 W 92 I in Figure 212 means that there are 1 7 and 92 invalid elements violating constraint s of the error warning and info severities respectively AAW Bee 7 Qig7wzi aC 7 Figure 211 Status Bar with Warning Symbol Figure 212 Status Bar with Error Symbol Validatio
285. zard Dialog Select Element Scope 4 In the Select Element Scope pane e Use the Add button in Figure 272 to add an element selected in the element tree to the Selected objects pane e Use the Add All button in Figure 272 to add all elements directly owned by the element selected in the element tree to the Selected objects pane e Use the Add Recursively button in Figure 272 to add all elements listed under the element selected in the element tree to the Selected objects pane e Use the Remove button in Figure 272 to remove the selected element from the Selected objects pane e Use the Remove All button in Figure 272 to remove all selected elements from the Selected objects pane NOTE To add all elements under a package to the report select the package in the element tree and then click Add Recursively Figure 272 5 After the scope of the report is defined click Next to proceed to the Output Options pane Fig ure 273 212 Copyright 2006 2011 No Magic Inc Report Wizard and Template Report Wizard Output options This page allows you to configure report files e g to select the report files output location and image format etc Click Generate button to start generating the report Output Options Report file C Document and Settings username My Documents WM RequirementReport rtt Report image format Joint Photographic Experts Group jpg Auto image size Fit image to paper large only Display empty value as

SysML Plugin User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents