Home

SysML Plugin User Guide

1. gt a2 ProvideGasPower velat Ii F Allocate a3 ControlElectricPa Delete Relation D a4 ProvideclectricPa El FS HSU Structure A PowerSubsystem OF emg HSUVModel HSU Cal epe HSUVModel HSU CA pecu HSUVModel sHSU Dependency List Figure 10 Editable Matrix context menu 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 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 The Dependency List dialog will then display Dependency List Dependency List Dependency Name Row Element Name Direction Column Element El oe Alocate HsU a1 ProportionF a2 ProvideGas Figure 11 Dependency List dialog Predefined Relation Maps 3 3 Predefined Relation Maps The SysML plugin introduces a predefined set of Relation maps to increase traceability of system requirements and design elements There are three predefined relation maps e Structure Decomposition Map e Activity Decomposition Map e Instance Map The Relation map is a special kind
2. 2 Click Add and then select either Provided or Required Case Study 1 If the port is typed the Select Interface dialog will open You can 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 ARN i EIN MARR DAAA AA k ar tL N A NAA NIA f Pe P M f ADNI J f C ANNO LITA NIA MSONIC INA IUU CoOpyrgNt ZUU9 ZU TO INO Magic INC f Cw pw 2 Diagram Specific Procedures X Select Interface H LICECmds Ff IIEPCCmd E IIEPCData E ITRSMCmd H ILTRSMData IFS_EPC sE IFS_ICE IFS TRSM ICEData Figure 52 Select Interface dialog Case Study 2 If the port is not typed the Select Port Type menu will then display Ad Select Port Type Ad Select Port Type Port type must be specified Please select one of the Following options Port type must be specified Please select one of the Following options O Select or create port type manually Create dummy port type automatically Select or create port type manually Figure 53 Select Port Type menu Provided Interface Figure 54 Select Port Type menu Required Interface You can then select e Fo
3. zeblock Ey partib Block4 Figure 42 Property smart manipulator menu to display ports W o g TN E e Display Forts 2 All ports including flow ports will then be listed in the Select Ports dialog 3 Click OK to view the selected checked port s on the part symbol Diagram Specific Procedures p Select Ports Select Ports P i Porti Block3 P o Porte Block3 Figure 43 Select Ports dialog 4 The selected ports will then be displayed on the part symbol i Forti o Port zsblogck partib Block 5 2 2 4 NEW Displaying Direction Prefixes of Proxy and Full Ports Directions of Proxy and Full Ports can be identified with help of direction prefixes The Proxy Port direction prefixes are displayed e On Blocks 1 To hide the Proxy Port direction prefixes on the Block set the Show Proxy Port Direction in Compartment property value to fa se in the Symbol Properties dialog of that Block The Proxy and Full Port direction prefixes are displayed e In the Model Browser 2 e On the Port shape when its name is displayed inside the shape 3 For this open the Symbol Properties dialog of the Proxy or Full Port and select Name and Type Labels Inside or All Labels Inside as the Position of Labels property value To hide the direction prefix on the Port shape set the Show Direction Prefix Inside Port property value to fa se in the Symbol Properties dialog of that Port e On the ToolTip which op
4. Diagram Specific Procedures 74 SYySML Block Definition Diagram Procedures 74 Inserting a new SysML property 75 Inserting a new SysML diagram 76 Using SysML Style compartments 76 Creating an association block 77 Creating a SysML Internal Block Diagram 78 Representing association roles as block properties 78 Creating instances of blocks with complex structure 78 SYSML callout box 86 NEW Managing Interfaces of the Block 89 NEW Managing Block properties 90 SYySML Internal Block Diagram Procedures 92 Creating Ports 92 Displaying Parts 93 Displaying Ports 94 NEW Displaying Direction Prefixes of Proxy and Full Ports 95 NEW Displaying Combined Direction on Proxy Port 96 NEW Displaying Direction Prefixes of Flow Property 97 Using Edit Compartment 97 Show Default Value and Show Slot Type 98 Provided Required Interfaces 99 NEW Managing Interfaces of the Proxy Port 104 Create Directed Features and Specify Feature Directions 105 Displaying Structures of Blocks in Compartments and IBDs 105 Converting nested parts to dot notation 108 Extracting structure 109 Creating a flow port 112 SySML Package Diagram Procedures 116 Using package element 116 SySML Parametric Diagram Procedures 117 Displaying parameters 117 Creating automatic constraint parameters 118 Creating a binding connector 121 Requirements Diagram Procedures 122 Changing requirement type 122 Creating Requirements Diagram for sub requirements 122 Numbering requirement IDs 123 Us
5. E Ep UML Standard Profile rsively fa sample profile ea SYSML Profile 5ysML a9 LUselLase Description E editor E S sML1 0 E test Aa Fine i a Cancel Figure 3 Select Elements dialog 6 Click the Validate button in the Validation dialog 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 e Mark Exclude elements from read only modules to ignore the elements in read only modules from the validation process e Validation may take several minutes if your model is large 7 The Validation Results window will show the elements that do not conform to some constraints in the selected validation suite These elements are called invalid elements and are highlighted Ifa highlighted invalid element is selected for example the Loss of Fluid requirement element a warning will appear requirements requirements A OffRoadCapability FuelEcononry An Id 2 Id 2 E i Text The Hybrid Text The Hybrid re SUWY shall have the HHSUW shall have aj off road capability of dramatically PT a typical SUW better fuel m economy than a ae Figure 4 Invalid elements highlighted after Validation 8 Place your mouse pointer on the warning icon to display the error message corresponding to the broken constraint Validation e
6. E FuetTankAssembly E Reference Properties E Fuel H5 EJ FuelTankAssembly E Value Properties fuelFlowRate Real Sys EJ FuelTankAssembly fuelWeight a Real Sys O FuelTankAssembly Down Figure 38 Block Specification Column name Name Type Default Value Owner Button name Create Redefine O04 window Properties node Description Property name Property type Property default value Block name that contains the current property Description Opens the Specification window of the selected property Opens the list with the available to create properties Click to create the Connector property Part property Reference property Value property Constraint property Flow property Duplicates the selected item and marks its name in ascending order K A VY RAK rinht A DANNO INIAE Na Mian f NANNVrINNTF P 10 ITA NIO a f COpPpyngnt 2009 2015 No Magi J S a Diagram Specific Procedures Button name Delete Description Removes the selected item from the list 5 2 2 SysML Internal Block Diagram Procedures The SysML IBD specific features include Creating Ports Displaying Parts Displaying Ports NEW Displaying Direction Prefixes of Proxy and Full Ports NEW Displaying Combined Direction on Proxy Port NEW Displaying Direction Prefixes of Flow Property Using Edit Compartment show Default Value and Show Slot Type Provided Required Interfa
7. non active Discrete NoBuffer Overwrite AllocateActivityPartition AllocateActivityPartition Copy Copy Copy Copy Copy Requirement Requirement TestCase streaming streaming non Streaming nonStreaming functionalRequirement U Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 3 with permission A property to which the ConstraintProperty stereotype is applied must be owned by a SysML Block The discrete and continuous stereotypes cannot be applied to the same element at the same time The nobuffer and overwrite stereotypes cannot be applied to the same element at the same time The overwrite and nobuffer stereotypes cannot be applied to the same element at the same time The represented element of the activity partition which is applied with AllocateActivityPartition stereotype should be the Property An Action appearing in an AllocateActivityPartition 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 requirement stereotype or a subtype of the requirement stereotype applied The text property of the client requirement is constrained to be a copy of the text property of the supplier requireme
8. Architecture l Made s Simple SYSML PLUGIN 18 1 user guide No Magic Inc 2015 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 2015 by No Magic Inc All Rights Reserved System Engineer Perspective 7 SySML Diagrams 9 SYSML Block Definition Diagram BDD SYSML Internal Block Diagram IBD 10 SySML Package Diagram 12 SysML Parametric Diagram 12 Requirements Diagram 13 SYSML Activity Diagram 15 SySML Use Case Diagram 16 Views and Viewpoints Diagram 17 SYSML Sequence Diagram 18 SysML State Machine Diagram 18 Requirements Table 19 Dependency Matrix 27 SySML Editable Matrices 27 SySML Allocation Matrix 27 Satisfy Requirement Matrix 28 Verify Requirement Matrix 29 Refine Requirement Matrix 30 Derive Requirement Matrix 31 Creating Editable Matrices 32 Building Matrices 33 Editing Matrix 33 Predefined Relation Maps 35 SYSML Block Definition Diagram Elements 36 Block 36 Domain 37 External 37 System 37 Subsystem 38 System Context 38 Constraint Block 38 Interface Block 39 Flow Specification 39 Value Type 40 Quantity Kind 40 Unit 41 SYSML Internal Block Diagram Elements 41 Part Property 41 Shared Property 42 Reference Property 42 Value Property 42 Constraint Property 42 Distributed Property 43 Flow Port 43 Full Port 43 Proxy Port 44 Directed Feature 44 Views and Viewp
9. CA Range H LE Regenerative C SafetyTest C Capacity H5 ar a i T T kad kd lt lt CA Braking H EI HSUV Instance Values e Association testVehicle 1 HSUVModels HSUV E b HSUVModel HSUV St T bk HSUVModel HSUY a E cs HSUVModel HSUV St i E e HSUVModel HSUY St iQ EAPFuelEconomyTest ra j E i HSUVModel HSU Str j E ice HSUVModelHSUV j C ID E 1 HSUVModel HSUV Str Figure 7 Verify Requirement matrix 3 2 1 4 Refine Requirement Matrix The Refine Requirement matrix consists of e Row Named element which can be the client element of Refine dependency e Column Requirement Element which can be the supplier element of Refine dependency Dependency Matrix 4 gt T Delete Remove From Matrix Change Axes Export amp Criteria Row Element Type Package Column Element Type Requirement Select Row Scope HSUVModel a Select Column Scope HSUVModel Dependency Criteria Refine a Direction Row to column aa Et O HSUV Requirements HSUVModel E O HSUV Specification pemen El my El my 2 Performan E O 4 Capa CA 4 2 Fue CA 4 3 PassengerCapacity Cy 2 3 OFFRoadCapability CA 4 1 CargoCapacity ee 2 mi CA d 3 PowerSourceManagement on f ae D lw D Z D om D o Tj T El et HSUVModel a iE DeliverPower Behavior oo HSU Instance Values Bee
10. Invalid elements detected by 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 Validation 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 On the status bar at the bottom of the screen e a notification symbol info warning amp or error ai and e numbers and severities of invalid elements will be displayed For example o 4W means that there are 4 invalid elements violating constraint s of the warning severity e 1 7 W 921 in means that there are 1 7 and 92 invalid elements violating constraint s of the error warning and info severities respectively 3 To find out the reason why an element is invalid you can either e Click the warning symbol on the status bar 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 e Select a highlighted invalid element in the diagram Once a highlighted invalid element has been selected in the diagram a warning symbol will appear Place your pointer on
11. ibd Block PC SBC USB proxy prox yo proxy a Kproa ya pi USB p2 USB p3 USB a p USB Figure 40 Creating proxy port 5 2 2 2 Displaying Parts If you have already defined the parts properties of a Block you can then display the parts on any IBD having the Block as its context Diagram Specific Procedures To display parts in IBD 1 Right click IBD and select Related Elements gt Display Parts All the parts selected will be listed in the Select Parts dialog p Select Parts constraint property Constraint Block Block part property BLOCK Block reference property BLOCK Block shared property BLOCK Block amp UML property Class Block value property ValueType Block Select All Figure 41 Select Parts dialog 2 Select parts and click OK to show the selected parts on the IBD 5 2 2 3 Displaying Ports If you have already defined the port s flow port s of a Block you can then display the port s flow port s full port s proxy port s on any part typed by the Block To display ports flow ports on a part on an IBD 1 Do one of the following e 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 e Click the Display Ports icon on the Smart Manipulator menu of the part a P S
12. return of a Test Case element must be VerdictKind an enumeration bdd Model Data f inconclusive error Figure 93 VerdictKind enumeration Requirement Relationships a 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 The supplier and the client of a Derive dependency must be requirement elements or requirement subtype elements s gt Satisfy Relationship Dependency A The supplier must be a requirement element or one requirement subtype a Copy Relationship Dependency x CF 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 Diagram Specific Procedures 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 The supplier and the client of a Copy dependency must be requirement elements or requirement subtype elements 5 2 6 SysML Activity Diagram Procedures SySML Activity Diagram specific features include e Select Operation e Dynamic Centerlines e Decomposing activities 5 2 6 1 Select Operation Click Select Operation on the Call Operation Action shortcut menu to select an operation for that Call Operati
13. A InstanceSpecificatians ftom the browser onto parts in an IBD to assjgn property specific default initial values a lt lt initialises gt gt lt lt illustration only gt gt lt lt Rationale gt The property specific default values fa k a property specific initial values for each TIP part are defined using the Slots of an y aoo i ou may optionally organise the Instancespecification of matching type E aentaes carry Your property specific values in a stereotyped Model The Magicdraw UML 45 ML plugin structure and yalue HOWTO guide Vehicle lt lt re xi Figure 9 Progressive reconfiguration For more information about Progressive Reconfiguration see hitp training nomagic com 5 1 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 different 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 the diameter of the Tire TireBead and Rim will be larger the inflationPressure value of the WheelAssembly will be higher the LugBoltJoint wil
14. Item Property dialog will then open Diagram Specific Procedures ltem Flow ltem Property l 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 ItemProperty TG DE Figure 71 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 contains the selected connector will be listed in this drop down menu Ad Item Flow Item Property Select or create elements those will represent conveyed information circulating From source to target in given direction Item Flow ay ee ItemFlow g B pb Z pe Conveyed Classifiers Item Property Humber of elements 2 Figure 72 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 Diagram Specific Procedures 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 hoa From pb To pc Conveyed Classifiers
15. Requirements 14 This suite contains SysML constraints on the following elements Copy DeriveReqt Requirement and Test Case gt O O1 If 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 2 The Validation dialog will open 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 Validation Ld Validation Validation Validation Suite FQ Diagram Merge UML Standard Profile MagicDraw Profile Merge validate For FQ Diagram Merge UML Standard Profile Magicbraw Profile Merge Fa Orphaned Proxies UML Standard Profile validation Profile Minimal Severity EG Parameters Synchronization UML Standard Profile validation Profile E ata FQ Relations Ownership UML Standard Profile Validation Profile Fa shape Ownership UML Standard Profile Validation Profile Fo Spelling UML Standard Profile Validation Profile me SVSML ValSuite MD Customization for SysMbli SysML constraints Fo SysML valSuite Activities MD Customization For SysMLi SysML d SysML YalSuite Fee Figure 1 validation suite package selection To limit the scope of the
16. the warning symbol to see the error message related to the constraint for instance A requirement cant copy more than one requirement s lt requirement gt F _ Requirement 2 S lt COpye gt s lt requirement gt C Requirement 1 Requirement 3 Figure 8 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 model invalidity problem s To see the list of appropriate solution s for an invalid element you can do one of the following e Right click the invalid element in the Active Validation Results window if you have open this window before e Click the warning symbol after you have clicked the invalid element in the diagram After clicking for example solutions will then be displayed A Remove all other redundant Copy dependency s Remove Copy dependency Ignore Select in Validation Results 5 The Active Validation Results window includes the following icons If you click the e Select in Containment Tree you will be redirected to the selected invalid element in the Containment Tree e Select Rule in the Containment Tree you will be redirected to the broken constraint of the selected invalid element in the Containment Tree e Open all diagrams containing the selected element any diagram containing the selected invalid element will then be displayed Validation
17. Composite Structure Diagram in Magic Draw UserManual pdf Activity Diagram in Magic Draw UserManual pdf 5 2 Diagram Specific Procedures e SysML Block Definition Diagram Procedures e SysML Internal Block Diagram Procedures e SysML Package Diagram Procedures e SysML Parametric Diagram Procedures e Requirements Diagram Procedures e SysML Activity Diagram Procedures e SysML Use Case Diagram Procedures e SysML Sequence Diagram Procedures 5 2 1 SysML Block Definition Diagram Procedures SySML Block Definition Diagram specific features include e Inserting a new SysML property e Inserting anew SysML diagram e Using SysML Style compartments e Creating an association block Creating a SysML Internal Block Diagram e Representing association roles as block properties 72 Nananurinrht A ONN A XNAE Nan MAani Po 4 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures e NEW Managing Interfaces of the Block e NEW Managing Block properties 5 2 1 1 Inserting a new SysML property You can create a SysML property in the following ways e Block shortcut menu e Block Smart Manipulator menu To create a SysML property 1 Do one of the following e Select a block and from its shortcut menu select Insert New SysML Property e On a selected block click the Insert SysML property button 2 Select a SysML property you want to create Reference Property Value Property Constrain
18. MagicDraw provides the Validation functionality to validate user created models against a set of constraints Use SYySML 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 SySML ValSuite Activities 2 This suite contains SysML constraints on the following elements Control Operator Control Value Discrete noBuffer Optional Probability and Rate _ SyYSML 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 SYSML ValSuite Constraint Blocks 6 This suite contains SysML constraints on the following elements Constraint Block and Constraint Property 7 SySML ValSuite Model Elements 8 This suite contains SysML constraints on the following elements View and Viewpoint 9 SysML ValSuite Non normative Extensions 10 This suite contains SysML constraints on the following elements nonStreaming Streaming Design Constraint Functional Requirement Interface Requirement and Performance Requirement 11 SysML ValSuite Port and Flows 12 This suite contains SysML constraints on the following elements Flow Port Flow Property Flow Specification and Item Flow 13 SysML ValSuite
19. Model Library for Quantities Units Dimensions and Values QUDV SYSML Specifications define the model of the quantities units and dimensions quantity kind in Annex C Non normative Extensions You can define your own quantity and unit using the QuantityKind and Unit blocks defined in QUDV Model Library 6 1 1 QUDV Model Library QUDV Model Library is available for use in every new SysML project 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 6 1 1 1 QUDV QUDV Model Library QUDV mdzip consists of main definitions of new units and quantity kinds system as specified in OMG SysML Specifications for example SimpleUnit SimpleQuantityKind DerivedUnit DerivedQuantityKind AffineConversionUnit UnitFactor QuantityKindFactor and many more Full details of QUVD Library Model definitions are available in Annex C Non normative Extensions to OMG SysML specifications 6 1 1 2 SI Definitions The SI Definitions library SIDefinitions mdzip consists of predefined units and quantity kinds in QUDV system that you can use in your model You can customize the units and value types 6 1 1 3 SI Specializations The SI Specializations library SISpecializations mdzip consists of a diagram and Blocks It demonstrates how to extend the current QUDV system 6 1 1 4 SI Value Type Library MagicDraw SysML prov
20. Nested Port Action Trigger on Nested Port Related procedures SYSML Activity Diagram Procedures Transferring mathematical expressions from MATLAB source code into the model SySML Diagrams 2 1 7 SysML Use Case Diagram Description 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 represent the communications that occur between the actors and the subjects to accomplish the functionalities associated 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 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 diagram is generalization This is useful in defining overlapping roles between actors Actors are connected to use cases through communication paths each represented by a relationship There are four use case relationships e communication e include e extend e generalization Communication A communication pat
21. New Project dialog 5 1 2 Creating SysML Projects From Templates To create a SysML project from a template 1 Do one of the following e Click File gt New Project on the main menu e Click the New Project button on the main toolbar e Press CTRL N The New Project dialog opens 2 Click the Project from Template icon 3 Enter a filename in the Name box 4 Click the button to select a location for your new project 5 Select the SysML template from the Select template tree and click OK 53 Copyright 2009 2015 No Magic Inc Generic Procedures 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 Name Distiller_model Project location C Projects Create directory for project and related data Clone custom modules Project Unique prefix for module names Cloned_ from Template Use this template to create anew SysML project using SySML profile Also load S ValueType and QUDYV model libraries Figure 2 Selecting SysML template For more information on how to work with a new project see the Working with Projects section in the MagicDraw UserManual pdf 5 1 3 Using OMG SysML Style SySML plugin provides the visual style of OMG SysML Specifications OMG Sys
22. Properties desc SatisfiedBy NamedElement SysML Profile Requirements Requiremnent im Figure 4 Select Custom Requirement Columns dialog Select a property tag to be displayed as a new column of the Requirements Table and then click 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 Show Full Paths If you select an element in the table and click this icon the full path of the element will show Export You can also export a SysML Requirements Table to HTML CSV or Microsoft Excel xlsx spreadsheet by clicking the Export icon on the table toolbar All requirements in the table will be exported to a selected file format 26 Copyright 2009 2015 No Magic Inc Dependency Matrix 3 2 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 e Scope There are two types of scope row scope and 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
23. QUANTITYKIND DESCRIPTION PROPERTY description public static final String QUANTITYKIND SYMBOL_PROPERTY symbol public static final String UNIT STEREOTYPE Unit The following methods were moved from the com nomagic magicdraw sysml util SysMLProfile to the com nomagic magicdraw sysml util MDCustomizationForSysMLProfile getConstraintProperty getQuantityKind getUnit isQuantityKind isUnit isConstraintProperty The constant NESTEDCONNECTOREND_PROPERTYPATH_PROPERTY changed to ELEMENTPROPERTYPATH_PROPERTYPATH_PROPERTY SysML classes for open API 8 2 SysML classes for open API Classes which are available for open API are included in SysML plugin open API documentation Find these in lt SysML plugin installation directory gt openapi docs The com nomagic magicdraw sysml util SysMLUtilities class was added to the open APIs It provides utility methods for easier work with SysML projects Methods and classes marked as deprecated do not support the development of external plugins
24. Tips and Tricks Blocks Centril Cal diameter m Tips and Tricks Blocks Discharge Nozzle a efficiencyEquation Tips and Tricks Blocks Pump Efficiency Tips and Tricks Blocks E flowingFluid Tips and Tricks Blocks Fluid Tips and Tricks Blocks Centrifugal Pump 2 CA impeller Tips and Tricks Blocks Impeller Tips and Tricks Blocks Centrifugal Pump a Hubricant Tips and Tricks Blocks Lubricant Tips and Tricks Blocks Centrifugal Pun z oilrings Tips and Tricks Blocks Oil Ring 2 Tips and Tricks Blocks Centrifugal Pur 2 seal Tips and Tricks Blocks Seal Tips and Tricks Blocks sCentrifugal Pump z shaft Tips and Tricks Blocks Shaft Tips and Tricks Blocks Centrifugal Pump CA suction Tips and Ireke Blocks Suction Mozzle Tips and Tricks Blocks Centrifugal i Clear All Select All ibd Block Encapsulated Centrifugal Pump Encapsulated Centrifugal Pump bearings Bearing 3 discharge Fluid Flow discharge Discharge Nozzle impeller Impeller The nested part displayed with dot notation suction diameter m Dot notation Figure 59 Nested part property selected and shown with its class and dot notation Thus to redisplay an internal structure in another structure you have to recreate the internal structure manually The graphical layout must also be applied manually making it a time consuming activity Dia
25. a list of owned behaviors activities state machines interactions etc and buttons for creating or deleting them O PowerControlUnit Usage in Diagrams H E Documentation Hyperlinks E Allocated El Ports ProportionPower 4 Activity CG HSUV Behavior l Operations l Relations Signal Receptions Clone Delete Figure 100 Allocations in behavior Specification window Accept Change Structural Feature Event Action An Accept Change Structural Feature Event action is a UML Accept Change Event action applying the AcceptChangeStructuralFeatureEvent stereotype It can be used for handling the Change Structural Feature event which will occur when the value of a specified Structural feature is changed The Change Structural Feature event is a Change event applying the ChangeStructuralFeatureEvent stereotype It must be an Event element of the Accept Change Structural Feature Event action To create an Accept Change Structural Feature Event action 1 Select Accept Change Structural Feature Event Action from the SysML Activity Diagram toolbar Then click SysML Activity Diagram to specify the location of the newly created symbol of the action The Select Property dialog will open for selecting the structural feature Diagram Specific Procedures Aq Select Pro perty a Select search for or create an element a Search For an element by using list or tree views To Find an element type B text or wildcard 7 i
26. be assigned as the default value for this property and its slots with values will be displayed inside the property symbol 2 The default value of the property will be displayed If the default value is an Instance Specification the defaultValue compartment containing the Instance Specification slot s will be displayed instead s lt bloack reference property Block lt lt block gt Eg part property Block defaultValue value property 321 reference property instance part property instance Figure 48 defaultValue compartment Diagram Specific Procedures 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 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 e None no type slot will be displayed e Name e Qualified Name 2 If you select Name or Qualified Name the slot types will be displayed s lt block gt reference property BLOCK lt lt block gt part Block defaultValue value property YalueType 321 reference property BLOCK instance part property BLOCK instance Figure 49 defaultValue compartment with slot types 5 2 2 9 Provided Required Interfaces Provided
27. bk BrakeSubsysten bk O mpg Real a E payloadCapacity Real E Figure 8 Inherited Structures of blocks 5 1 7 Generating SysML reports 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 Generic Procedures To create a report using a SysML report template 1 Select a report template and click Next in the Report Wizard dialog The Select Report Data pane will open You can then select a predefined report data for the selected template default Built in 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 The Variables dialog will then display You can then add modify the variable of the report to be generated such as author company name company address report purpose report scope etc This information will appear in the report generated 3 Click OK to return to the Select Report Data pane In the Select Report Data pane click Next The Select Element Scope pane will then display 4 In the Select Element Scope pane Use the Add button to add an element selected in the element tree to the Selected objects pane Use the Add All button to add all elements directly owned by the element selected in the element t
28. created as a constraint parameter A new constraint parameter z will be created in the constraint block Sum Diagram Specific Procedures econstraint Figure 79 New parameter The following examples further illustrate how to create new constraint parameters with this new constraint parameters creation mechanism par Block Block1 Defined Constraint Expression econstraints Constraint 1 A a b c Select Parameter O a Integer bdd Package Sample HBE D b Integer O New c Integer C New bb Integer a Integer b Integer Figure 80 Binding connector connects to defined constraint expression constraint property In in the preceding figure the constraint parameter a Integer and b Integer have already been defined in the constraint block A However they are hidden on the constraint property Constraint 1 A If you select a Integer from the list the constraint parameter a Integer will appear on the constraint property Constraint 1 A Diagram Specific Procedures par Block Block 1 Defined Constraint Expression econstraints Constraint 1 A bb Integer a b c bdd Package Sample S BDD1 a Integer b Integer Figure 81 Connecting binding connector to existing constraint parameter If you choose to create a new constraint parameter for example select New c Integer from the list and MagicDraw SysML will create and add it into the constraint block A The name of the
29. e 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 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 a constraint referenced as Copy A is broken If the solution 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 s lt requirement F _ Requirement 2 A Remove all other redundant Copy dependencyts in oa A requirement can t copy more than one requirement a Ignore S lt Copye gt ssrequirement A Requirement 1 Select in Validation Results Figure 9 Selection of first solution ssrequirement gt CE Requirement 2 s lt requirement CE Requirement 1 E lt ecopy o J eerequirement gt C Requirement 3 Figure 10 Valid elements Each implemented constraint has its own appropriate solutions The Active Validation feature ensures that SysML modeling is consistent with OMG SysML Specifications Validation 7 1 1 1 Active Validation Options You can customize the Active Validation feature using the five options in the following figure Ad Pro ject Options Me seneral project options General project options E Diagra
30. ehicle H Structure lt gt Maintain the vehicle EJ Test DJ UseCases H E Hybrid H E views H E matrix templates matris templates module ru BERS MO Customization For SysML MO customization BERS ModelingDomain H E UML Standard Profile UML_Standard_Frofile x E ea sample profile E E S sML Profile SysML Profile mdzip EL Ba llea ara Geecrintinn DrenFila Mea ara Drailla a Renumber lt ti gt Figure 104 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 select the Insure theVehicle use case and then click the Create button to number the use case to 2 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 5 2 8 SySML Sequence Diagram Procedures The Sequence diagram focuses on the Message interchange between a number of Lifelines A sequence diagram shows the interaction information with an emphasis on the time sequence The diagram has two dimensions the vertical axis that represents time and the horizontal axis that represents the participating objects The time axis could be a
31. matrix 3 2 1 6 Creating Editable Matrices You can create matrices by using either the main toolbar main menu or Containment tree To create a matrix 1 In the Containment tree or on the diagram pane select an element that can be the owner of the matrix 2 Do one of the following e From the main menu select Diagrams gt Create Diagram In the opened Create Diagram dialog select a matrix type and press Enter e On the main toolbars click the Create Diagram button In the opened Create Diagram dialog select a matrix type and press Enter e Press Ctri N In the opened Create Diagram dialog select a matrix type and press Enter e Right click the element and from the shortcut menu select Create Diagram gt Requirement Diagrams or SysML Matrices and click a desired matrix type Dependency Matrix The newly created matrix opens on the right side of the application window 3 Type a matrix name 4 Select criteria and a scope to be represented in the matrix or simply drag desired elements from the Containment tree 3 2 1 7 Building Matrices The matrices you have created in Section 3 2 1 6 Creating 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 Click the button next to the Row Scope in the matrix pane The Sco
32. new parameter is c It will be typed by Integer because the opposite end of the binding connector is the value property typed by Integer par Block Block1 Defined Constraint Expression constraints Constraint 1 A bb Integer a b c bdd Package Sample BDD1 a integer b Integer c Integer Figure 82 Automatically created constraint parameter of defined constraint expression constraint property In the case that the constraint block typing the constraint property has no parameter and the constraint expression is undefined SysML will create a new constraint parameter using the name and the type of the property at the Diagram Specific Procedures opposite end of the binding connector The created constraint parameter will be visible on the selected constraint property with the binding connector attached par Block Block 1 Undefined Constraint Expression constraints P Constraint z B bdd Package Sample S BOD Figure 83 Binding connector connects to undefined constraint expression constraint property par Block Block1 Undefined Constraint Expression econstraints Constraint 2 6 bdd Package Sample BDD2 Figure 84 Automatically created constraint parameter of undefined constraint expression constraint property 5 2 4 3 Creating a binding connector Binding connectors enable you to bind each constraint block parameter to the property of another block in the surro
33. of diagram that automatically updates and renders an elements dependency tree according to predefined dependency criteria For more information about selecting and creating elements see section Manipulations in Relation Map in MagicDraw UserManual pdf 4 1 SysML Block Definition Diagram Elements 4 1 1 Block Description 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 subsystems but also quantitative values as well as other information about that system for example documentation You can use SysML blocks throughout all phases of system specification and design and apply them to many different kinds of systems These include modeling either the logical or physical decomposition of a system 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 anothe
34. press Alt Insert 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 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 The Select Requirement dialog will open Requirements Table select Requirement 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 Selected elements i Search by name 2 CA 4 2 FuelCapacity HSUVModel H5UY Rg ype text or wildcard 7 7 to esearch E Tree f List Pin a EE aE BGS G E Data 28 mafoies AYES HSUw Model sHSUY Requirements 18 ma ohes FF HSU Specification 24 maiohes ar f 3 a ais EEEE 3 matches Ad d Rec UrSsive ly CA 4 2 FuelCapacity i E PassengerCapacity ia Remove O 4 1 CargoLapacity Eco Friendiness 7 oto Remove All Ergonomics Qualification 2 ma o 2 Perf
35. requirement in the Containment tree or the Requirement ID Numbering dialog tree 2 To search for a requirement by its ID type the ID of the requirement A matching requirement will be selected if any Search for 2 1 E Data Ge Relations FF HSUvModel Ee Relations H A Explanations H E HSU Analysis H E HSU Behavior HSU Reguirements fe Relations E E HSU Specification i CH PowerSourceManagement C 2 Performance CA 2 2 FuelEconomy LH 2 3 OffRoadCapability CA 2 4 Acceleration 7 1 Braking Figure 87 Finding requirement by ID in Containment tree Diagram Specific Procedures 3 To search for a requirement by its name type followed by the name of the requirement A matching requirement will be selected if any Lee m m a Search for OrfRoadCapability F lt Relations H E HSUvModel Ee Relations Hg Explanations H E HSU Analysis H E HSU Behavior E9 HSUY Requirements fe Relations E E HSU Specification i CE PowerSourceManagement C 2 Performance blll 2 2 FuelEconomy 2 3 OFFRoadCapability CA 2 4 Acceleration fH 2 1 Braking Figure 88 Finding requirement by name in Containment tree This type of search for requirement will not work if the element is not shown in browser when searching To find the requirement using the Find dialog 1 You can either select Edit gt Find in
36. 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 Properties may have different property specific default values and will then be initialized differently Generic Procedures Property specific initial values are managed by the higher context structured block which owns the Part Properties that initialize or configure their possibly different values on instantiation For example the generic capacity of a FuelTank not any particular one is 40 liters 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 bdd Model Vehicle aa Wehicle bdd HOWTO define property specific default values pragressive configuration lt lt block gt lt lt blocks gt E FuelTank lt explanatian gt hil g alee The static class level capacity L 40 O0 unit Litre Getault value wall be overridden parts tank FuelTank 1 tank In MD SysML you can drag n drop s lt initialisatians
37. that are not provided must not have or inherit methods A FlowPort must be typed by a Flow Specification Block Signal or Value Type If the FlowPort is atomic isAtomic True the direction must be specified has a value and isConjugated must not specified has no 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 direction will be in or out if isConjugated true If all the Flow Properties are out the FlowPort direction will be out or in if isConjugated 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 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 e
38. the many to many traceability of elements from different 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 For more information on the Dependency Matrix feature see the Model Analysis in the Dependency Matrix section in the MagicDraw User Manual 3 2 1 SysML Editable Matrices You can edit three SysML matrix templates Not only can you display dependencies between elements but you can also add or delete dependency ies directly in the editable matrices The three editable matrices are e SysML Allocation Matrix e Satisfy Requirement Matrix e Verify Requirement Matrix e Refine Requirement Matrix e Derive Requirement Matrix 3 2 1 1 SysML Allocation Matrix The SysML Allocation Matrix consists of e Row a named element that can be the client element of the Allocate
39. y Real y Real m Real b Real Figure 20 Element name duplication with incremental number Generic Procedures lf m file contains multiple functions declarations only the first function is transfered into the model par Block Decoder Ra Decoder Rule Score Real constraint a Calculation Constraint 1 ix normedist z t Cumulative Frequency Real function x norm edist cl 2 506626 c2 0 3193615 e3 O 3565636 e4 1 7514 779 c5 1 821256 csi 33027947 W 1 if 220 w 1 end yelf 1it 0 25164194e ts e O 5 u 0 5 fexp ekefep foelpe dye cetyet cstya catty tt cot yecay eae Figure 21 Transferring m file with multiple functions declaration Use one of the following ways to transfer the mathematical expressions from MATLAB source code into the model e NEW Drag the m file directly to the diagram pane e Drag the m file onto the already existing element shape empty or full The Activity diagram does not support this way of transferring mathematical expressions e Use shortcut menu on the already existing element shape empty or full The Activity diagram does not support this way of transferring mathematical expressions NEW Drag the m file directly to the diagram pane to create one of the following e Constraint Block with its properties and parameters in the SysML Block Definition or UML Class diagrams e Constraint Property and Constraint Block in the SysML Internal Bloc
40. 015 No Magic Inc Diagram Specific Procedures X Automatic instantiation Wizard 91 Select parts E B Data E Satellite 2 Select a package o O 3 Select a diagram Select a package to hold instance specification s to be created Cees iets rah Cee ee Figure 29 Automatic Instantiation Wizard Step 2 Select a package 5 In Step 3 type SatInstance02BDD in the Type diagram name box and select BDD as the diagram type Diagram Specific Procedures p Automatic instantiation Wizard 1 Select parts Create a new diagram C 2 Select a package _ Create link between instances 3 Select a diagram Type diagram name Check the Create a new SatInstancel2BDD diagram checkbox iF you wank to create a new Select diagram type diagram to display SysML Block Definition Diagram x instance specification s Select owner For diagram Check the Create link between instances E E Data checkbox if you also want aga Satellite to display linkisi among B SatelliteInstancedl those instance a SatelliteInstanced2 specification s B E SatelliteSpecification bf Control J CxS heading O Instruments E PowerBalance Powersystem O Propulsion O Satellitesystem wt Figure 30 Automatic Instantiation Wizard Step 3 Select a diagram 6 Click Finish The SatIinstance02BDD diagram will be created Diagram Spe
41. Context Logical Flow allocatedTo allocatedTo zfullPortsDevice pp zfullPorts Device pp computer Computer printer Printer aproxys cproxys Lpl Data IF pl Data IF printer Printer fulls Ch pp USB IF allocatedFrom allocatedFrom aproxyPolts Device pl eproxyPotle Device pl Figure 2 SysML Internal block diagram Related elements Part Property Shared Property Reference Property Value Property Constraint Property Distributed Property Flow Port Full Port Proxy Port Directed Feature Related procedures SYSML Internal Block Diagram Procedures Transferring mathematical expressions from MATLAB source code into the model SySML Diagrams 2 1 3 SysML Package Diagram Description 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 na
42. Environments IDE ie If you skip integration process now you will be able to get back to it later Figure 1 Select Perspectives dialog pag For more information about how to work with perspectives see 1 inii Perspectives Selection and Customization in the Getting Started section in the MagicDraw User Manual pdf 1 SYSML DIAGRAMS 2 1 SysML Diagrams All diagrams are described in the following sections SYSML Block Definition Diagram BDD SYSML Internal Block Diagram IBD SysML Package Diagram SYSML Parametric Diagram Requirements Diagram SYSML Activity Diagram SySML Use Case Diagram Views and Viewpoints Diagram SysML Sequence Diagram SYSML State Machine Diagram 2 1 1 SysML Block Definition Diagram BDD Description A Block Definition Diagram defines the features of a block and any relationships between blocks such as associations 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 9 Copyright 2009 2015 No Magic Inc SYSML DIAGRAMS SySML Diagrams Sample bdd Model tem Flow End Compatibility tem Flow End Compatibility on e WaterDistiller Figure 1 Sy
43. From pe To pb Item Property SSS tL Figure 73 Item Flow Item Property dialog Direction selection 6 Click the browse button next to the Conveyed Classifiers box The Select Conveyed Classifier dialog will open 7 Select a classifier to be used as the Conveyed Classifier and click OK Ay Select Conveyed Classifiers Search By Mame F lt UNSPECIFIED gt B E Data a UML Standard Profile UML Standard Prof Multiple Selection gt gt gt Figure 74 Select Conveyed Classifiers dialog 8 Click the browse button next to the Item Property box The Select Item Property dialog will open 9 Select a part property to be used as the Item Property and click OK Diagram Specific Procedures AW Select Item Property Model none gt l E Data Aa Cel partE E Cel parbl C Figure 75 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 be created on the connector You can create a new conveyed classifier either on a new item flow or on an existing item flow by dragging the classifier to a connector or association The dragged classifier will be a conveyed classifier of the item flow 5 2 3 SysML Package Diagram Procedures e Using package element 5 2 3 1 Using package element You can display the name of a package either on top o
44. ItemFlow has an itemProperty its name should be the same as the name of the item flow The conveyed classifiers must be the same or subtype of classifier that type flow property of flow specification Directly Derived specified from inOMG OMG SysML SysML spec spec 9 3 2 8 9 3 2 8 9 3 2 8 9 3 2 8 9 3 2 9 9 3 2 9 9 3 2 9 9 3 2 10 9 3 2 10 9 3 2 10 9 3 2 10 9 3 2 11 9 3 2 11 9 3 2 11 9 3 2 11 9 3 2 11 9 3 2 11 Validation Constraint ProxyPort ProxyPort ProxyPort TriggerOnNestedPort TriggerOnNestedPort TriggerOnNestedPort TriggerOnNestedPort TriggerOnNestedPort ConstraintBlock ConstraintBlock ConstraintBlock ConstraintParameter Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 3 with permission Proxy ports cannot also be full ports This applies even if some of the stereotypes are on subset or redefined ports Proxy ports can only be typed by interface blocks Ports owned by the type of a proxy port must be proxy ports The port property of a stereotyped trigger must have exactly one value and the value cannot be a full port The values of the onNestedPort property must not be full ports The port at the first position in the onNestedPort property must be owned by a block in which the trigger is used The port at each successive position of the onNestedPort property following the first position mus
45. L Parametric Diagram Elements Sample eviews Introduction Creates View Lael f table viewpoints Grouping Viewpoint Table made from smart package 4 4 SysML Parametric Diagram Elements 4 4 1 Moe Description moe measure of effectiveness represents a parameter whose value is critical for achieving the desired cost effectiveness mission Sample amoes HSUValt1 fuelEconomy Real 4 4 2 Objective Function Description 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 Sample eobjectiveFunctions gt MyObjectiveFunction CE Sumlvwi P i 4 4 3 Binding Connector Description 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 connector may be nested within a multi level path of properties accessible from the owning Block The NestedConnect
46. ML style that you can use with your SySML model Such style is available with every new SysML project created by SysML 16 8 or later To use OMG SysML style in a new SysML project 1 Create a SysML project see Creating SysML Projects or Creating SysML Projects From Templates 2 In the main menu select Options gt Project 3 The Project Options dialog will open 4 Select the Symbols properties styles node on the left hand side and then select OMG SysML style in the Symbols properties styles panel 5 Click the Make Default button Generic Procedures 6 Click OK Your SysML project will use OMG SysML style as a default style LAW Pro ject Options Symbols properties styles Default Default 7 Default Default OMG SysML style DB Shanes El Paths he 8 Shereokyoes B OMG SysML style Make Default H E Default model properties E e Code Engineering jeg Code Generation cod Java Language Options no C Language Options Seo ich C Language Options Export 26 CORBA IDL 3 0 languag i DDL Language Options Cancel Figure 3 Setting symbol properties style To apply OMG SysML style to an existing SysML project 1 Open a SysML project 2 On the main menu click Options gt Project 3 The Project Options dialog will open 4 Select the Symbols properties styles node on the left hand 5 Select OMG SysML style click Make Default gt OK Skip steps 6 to 10 6 I
47. OMG SysML Specifications 1 3 with permission 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 A classifier to which the PropertySpecificType stereotype is applied must be referenced as the type of one and only one property The name of a classifier to which a PropertySpecificType is applied must be missing The name attribute of the NamedElement metaclass must be empty Classifiers with the PropertySpecificlype stereotype are owned by the block which owns the property which has the property specific type Property which is typed by the PropertySpecificType should be owned by block or subtypes of block Directly Derived specified from inOMG OMG SysML SysML spec spec C 2 2 C 2 2 C 2 2 8 3 2 7 8 3 2 7 8 3 2 7 8 3 2 7 8 1 Stereotype Usage Standard stereotypes in SysML plugin are defined in SysML 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 Geta 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 J
48. Otherwise the direction is inout Diagram Specific Procedures Figure 45 Proxy Port s combined direction including directed features 5 2 2 6 NEW Displaying Direction Prefixes of Flow Property Directions of flow property can be identified with help of direction prefixes The flow property direction prefixes are displayed e On Parts 1 To hide flow property direction prefix on the Part set the Show Flow Property Direction in Compartment property value to true in the Symbol Properties dialog of that Part e In the Model Browser 2 _ Fe Contain amp Structure 48 Diagrams _ Bij Water Heating Element x Containment um D x d y 5wa w ibd Block Water Heating Element Water Heating Element E ea Data E rE Data E E 00 User Needs team Steam Dispense H E 01 Conceptual Model s eam UISpenser H E 02 Functional Model flow properes a steam in aj 03Fhysical Model H C9 34Interfaces H E 31 Katfeeautomat H E 32 Brewing Group E 61 G E 33 Water Heating Element open f oc i Steam H E Steam Dispenser Valve Et Cl steamMass Real 1 0 E Cl steamMassRequired Re steam adjust pul a shot Et Cl steamMassPerSecond F Lellin s Data 03 Physical M i P in steam in Data 03 Ph steam adi ul a shot P in mikin Data 03 Physi sam adjust P Figure 46 Places of displaying flow property s direction prefixes 5 2 2 Using Edit Compartment You ca
49. PERTY returns a string of prefix 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 PartProperty stereotype object Check if an element is stereotyped Usage includes MDCustomizationForSysMLProfile isStereotype 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 ValueProperty stereotype applied and returns false otherwise 8 1 3 SysML Profile API Changes SySML Profile API changes were made in relation to the SysML 1 4 support The following constants were moved from the com nomagic magicdraw sysml util SysMLProfile to com nomagic magicdraw sysml util MDCustomizationForSysMLProfile public static final String CONSTRAINTPROPERTY_ STEREOTYPE ConstraintProperty public static final String QUANTITYKIND STEREOTYPE QuantityKina public static final String QUANTITYKIND_ DEFINITIONURI_PROPERTY definitionURI public static final String
50. Port ICEFuelFitting eblocks tuelDelivery fuelSupply Fuel fw FrontWheel 1 E Figure 66 Internal Block diagram before extracting structure 2 Select Refactor gt Extract The Extract Structure Wizard dialog will open listing three steps to extract a structure Specify a new element Create port s and Create a property 3 Follow the steps of the wizard The following figure 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 existing layout will remain Diagram Specific Procedures cif torqueln Torque gi Torque torqueQut Torque tram And rightv Wheel Frontyhee ice InternalCombustionEngine spline PA aies FrontWheelAssemb L lett heel Front reel fi Fuelinjector 4 t1 Torque 4 dist Port EF uelF iting fuelSupply Fuel Figure 67 Internal block diagram after extracting structure 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 Open the created IBD to display the structure which was recently extracted The structure view will be ready oe 2 2 x FF I DERAS Aa O ith m E l ee Pg E ees l Eal Y n E Common oO ER HSU Structure E Note a Relations Problem H E H
51. Required Interfaces help identify compatible ports that can be connected together in an IBD On a port you can e create a new Provided Required Interface using the port specification dialog or e display an existing Provided Required Interface using the port shortcut menu Creating New Provided Required Interfaces Using the Port Specification Dialog To create new Provided Required Interface of a port 1 Do one of the following 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 group to open the Provided Required Interfaced pane E Z aA dp iiferential E A Frovwided Reguired inte faces Figure 50 Port Smart Manipulator Menu Provided Required interfaces e Click a port in a diagram to open its smart manipulator menu and then select the Provided Required interfaces icon to open the Provided Required Interfaced pane Diagram Specific Procedures Ly Port trsm Provided Required Interfaces ABI Documentation Hyperlinks E e eget e l Usage in Diagrams a ee eProvided Required Interfaces Mame 3 Template Parameters iS Provided i j Inner Elements Relations 3 Tags Constraints Language Properties I TCECmds Provided Remove Provided Forward ee Required Figure 51 Port Specification window Provided Required Interfaces group J Only typed ports can realize use interfaces
52. SU internalCom internalCom internalCom eee bustionEngi bustionEngi bustionEngi puationEnal l ne fif ne fif 3 ne fif4 ae eT Fuelinjector Fuelinjector Fuelinjector EL fuelDermand fuelDernand fuelDemand Figure 27 Instances after changing slot value of fuelReturn property Case Study To automatically instantiate a Block to be used with ParaMagic Plugin 1 Right click a block and select Tools gt Create Instance on the shortcut menu The Automatic Instantiation Wizard opens 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 here is used to demonstrate how this feature works CO NO Diagram Specific Procedures 2 In Step 1 select the required properties as shown in the following figure and set the value for each value property of the instantiate classifier 3 Click Next X 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 subtype 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 subkype of the abstract type Default values iF existed will be used new instance will not be created For a part with default value press SHIFT a
53. SU Interfaces pet E Wheel Rationale EE FrontwWheelAssembly abe Text Box 7 E Relations E Anchor i EE fw Front heel 1 Containment He Cal rfv FrontWheel 1 a if i CE dif Differential a Abstraction i iB eftwheel Frontyheel Dependency F rightWwheel Frontwheel A Allocate popan Space Sse oe al prrontwheeldassenbl Rieu Boleuon E Accelerator H E 4utomotiveDomain pen in E BatteryPack H E BodySubsystem E BrakePedal Specification a2 BrakeSubsystem Go To b bases CAM Bus mE Refactor F E chassisSuihsvstem Figure 68 The created IBD of extracted classifier Diagram Specific Procedures ibd Block Frontvwhneel4ssembly FrontYvhneel4ssembly rightvheel gt Front heel rightHaltshatt tri ry trem pline dif Differential 1 ti Torque t2 Torque letHaltshaft an i eblocks lett wheel Frontyyneel a fw FrontWheel 1 Figure 69 Displayed extracted structure 5 2 2 15 Creating a flow port In general 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 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 2 If you click the Flow Port button on the IBD toolbar select a part where the flow port will be created If you clicked the smart manipulato
54. U internalCombustionEngine ti4 fra HSU internallombustionEngine tra fuelReturn HSL internalCombustionEngine tuelReturmn TuelSupply HSL internalCombustionEngine tuelSupply iceEfficiency lt lt blocks gt zeblock lt lt block gt HSU HSU g HSU internalCombustionEng internalCombustionEng internalCom ine fuelReturn Fuel ine fuelsu Fuel bustionEngi ne tit fuelPressure fuelPressure Fuelinjector pressure Unit psi pressure unit psi i i fuelDemand dimension Pressure dimension Pressure fuelDemand temperature unit F tunit temperature Yunit F dimension Temperature dimension Temperature lt lt block gt lt lt block gt O zablock lt lt block gt HSU HSU HSU HSU internalCom inernalCom internalCom internalCom bustionEngi bustionEngi bustionEngi bustionEngi nefi ne fis ne fid ne tifi Fuelinjector Fuelinjector Fuelinjector Fuelinjector fTuelDemand TuelDemand fTuelDemand fTuelDemand lt lt block gt lt lt block gt ssblock shlack HSU HSU HSU nE asi internalCom internalCom internalCom MERT bustionEngi bustionEngi bustionEngi puationEnal ne fif ne fi 3 ne fif 4 eae aati Fuelinjector Fuelinjector Fuelinjector ee fuelDermand fuelDerniand fuelDerniand Figure 25 Example of instance created by Automatic Instantiation Wizard You can reassign some values for example if you like to use Sup
55. a HSU a ee HSUV Structure 1 ES HSUV Interfaces 1 A E HSUV UseCases Figure 8 Refine Requirements matrix 3 2 1 5 Derive Requirement Matrix The Derive Requirement matrix consists of e Row Named element which can be the client element of Derive dependency e Column Requirement Element which can be the supplier element of Derive dependency 31 Copyright 2009 2015 No Magic Inc Dependency Matrix oe R Derive Matrix x gt We Delete i Remove From Matrix gt fa Change Axes 28 Export J a r k Criteria Row Element Type Package Column Element Type Requirement Select Row Scope HSUVModel Select Column Scope HSUVModel Dependency Criteria Derive Direction Row to column 7 E G HSUV Requirements HSUVModel Eo i EES HSUV Specification T B C 2 Performan 4 a C ay ee PE D m ao i O o D j gt g 2 oi eae a 6 D 3 i 2 To i TU j a hy a a co U GG an g wu A a T p H T FE 1 S oo g LJ I C o 5 Foo Ss go amp og D a on 5 i os 2 e Y 6 5 3 ty ce a a cl a L O q F U L amp wi mot m m e N m T a TW co oY A A f amp A Tr or Tt wo Al Al E Al E E E a E l a Al B C HSUVModel E HSUY Analysis 1 1 Fi E3 HSUV Behavior if DeliverPower Behavior gt gt HSUV Instance Values El E5 HSUV Requirements i hE HSUV Specification 6 6 Pa Ae AA E HSUV Structure E HSUV Interfaces Figure 9 Derive Requirement
56. a new requirement type from the options The type s of the selected requirement s will then be changed 5 2 5 2 Creating Requirements Diagram for sub requirements MagicDraw SysML provides an easy way to create a requirements diagram for sub requirements of the selected requirement symbol To create requirements diagram for sub requirements 1 Click the requirement symbol in which you want to create the requirements diagram for its sub requirements 2 Click the Create diagram for sub requirements button from the smart manipulator Diagram Specific Procedures 3 The new requirements diagram for the sub requirements will then be created with the same name as that of the selected requirement reg requirement Performance RA Performance requirements Performance a rT iL srequirements srequirements srequirements srequirements FuelEconony Braking Acceleration OTRoadCapability Ts eae As Id 2 g iio oe Text The Hybrid Tesxt The Hybrid SUWY Test The Hybrid SUWY Text The Hybrid SUW HSU 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 Sly Sly Sly SIL Figure 85 Requirements Diagram for sub requirements 5 2 5 3 Numbering requirement IDs Numbering requirements is a trivial time consuming task in particular when working with a large SysML project S
57. 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 constraints such SYSML Block Definition Diagram Elements 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 purpose 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 defined in terms of more basic constraints 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 Sample constraints VerticalVelocity constants iv vO sin a parameters v misiunt metrePerSecond a rad unit radian v mfs unit metrePerSecond 4 1 8 Interface Block Description An Interface Block is a special kind of block for typing proxy ports It has no behaviors or internal parts Normally it contains a set of flow properties which can be shown in the flow properties compartment An interface block is introduced in OMG SysML 1 3 specification to rep
58. age and Text SysML Callout Style true SysML Element Type true Symbol IL 16 Sbeta 17530432 1264070354546 490 Symbol Bounds java awt Rectangle x S7 4 y 147 width 19 a Name Description Apply Style Default _ Make Default Figure 36 Symbol Properties dialog of callout box The new callout notation applies to all types of SysML diagrams Diagram Specific Procedures 5 2 1 9 NEW Managing Interfaces of the Block All owned and inherited Ports and their Interfaces of the selected Block are collected on the left of the Block Specification window gt Ports Interfaces Manage them by creating redefining or deleting Block properties The Port Interfaces node contains a list of Block owned ports Create or delete ports Use the ports specification button to edit properties of a specific port ES ER abe Port Name Type Features CA inc Coffee coffee beans in C4 icoffee Data Al oute Coffee coffee beans out E iCoffee Data Redefine Delete Figure 37 Block Specification window Ports Interfaces node 89 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures Column name Direction Port Name Port Type Type Features Button name Create Redefine Delete Description Direction prefix of t
59. al structures 1 Sample externals Road incline Real 4 1 4 System Description 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 SYSML Block Definition Diagram Elements Sample asystems Hybridsuv b BodySubsystem p bk GrakeSubsystem bk c ChassisSubsystem c i Int riorSubsystem i LightingSubsystem mpg Real p PowerSubsystem p payloadCapacity Real position Real vehicleDryVVeight Real VIN String 4 1 5 Subsystem Description A Subsystem is a typically large encapsulated block within a larger system 1 Sample subsystems Cylinder values bore m 0 06 unit metre siroke m 0 1325 unt metre 4 1 6 System Context Description A System context element is a virtual container that includes the entire system and its actors 1 Sample system contexts Car parts wheel Wheel properties tdriver Driver passenger Passenger 4 1 7 Constraint Block Description 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 represent mathematical expressions such as F m a and a dv dt which constrain the physical properties of
60. another Block Every Reference Property has none AggregationKind and is typed by a block Reference Properties are displayed in the references compartment 4 2 4 Value Property Description A Value Property is a property that specifies the quantitative property of its containing Block Every Value Property has composite AggregationKind and is typed by a SysML Value Type Value Properties are displayed in the values compartment Sample time sec 4 2 5 Constraint Property Description 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 Internal Block Diagram Elements Sample aconstrains Derivative iy derivativelx 4 2 6 Distributed Property Description A Distributed Property is a property of a Block or a Value Type used to apply a probability distribution to the values of the property Specific distributions can be defined by applying a subclass of the DistributedProperty stereotype to the property Sample 4 2 7 Flow Port Description 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 owni
61. at specifies a constraint on the implementation of a system or on part of it 4 5 8 Business Requirement Description A Business Requirement is a requirement that specifies characteristics of the business process that must be satisfied by the system 4 5 9 Usability Requirement Description A Usability Requirement specifies the fitness for use of a system for its users and other actors 4 5 10 Test Case Description A test case Activity StateMachine Interaction is a method for verifying a requirement SYSML Activity Diagram Elements 4 5 11 Satisfy Description 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 4 5 12 Verify Description A Verify 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 client test case to the supplier requirement 4 5 13 Derive Description 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 4 5 14 Copy Description A Copy relationship is a dependency between a sup
62. ation suites and then click Apply In this example three validation suites will be excluded from the validation process Additional validation rules constraints can be added and grouped into an active validation 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 pdf 7 1 2 SysML Constraints SysML constraints implementation for SysML validation suites and active validation suites include the following Directly Derived specified from Constraint Description in OMG OMG Description excerpts have been taken from the SysML SysML Constraint OMG SysML Specifications 1 3 with permission spec spec Binding Connector 1 The two ends of a Binding Connector must have either 8 3 2 1 the same type or types that are compatible so that equality of their values can be defined Block 7 Within an instance of a SySML Block the instances of 8 3 2 2 properties with composite aggregation must form an acyclic graph Block 8 Any classifier which specializes a Block must also have 8 3 2 2 the Block stereotype applied Validation Constraint Block BlockProperty ValueProperty DistributedProperty ValueType ValueType AcceptChangeStructural FeatureEventAction AcceptChangeStructural FeatureEventAction AcceptChangeStructural FeatureEventAction AcceptChangeStructural FeatureEventActi
63. avaDoc for the two API classes 8 1 1 SysML Profile You need to import com nomagic magicdraw sysml util SysMLProfile to use this API class Get a string constant for each property of stereotype tag Usage includes SysMLProfile STEREOTYPE_PROPERTY_NAME For example SysMLProfile ALLOCATED_ALLOCATEDFROM_PROPERTY returns a string of allocatedFrom Get a stereotype element Usage includes e SysMLProfile getInstance project getStereotype where project refers to a project that uses SysML Profile e SysMLProfile getInstance element getStereotype where element refers to the element in a project that uses SysML Profile For example SysMLProfile getInstance project getBlock returns the reference to the Block stereotype object Check if an element is stereotyped Usage includes SysMLProfile isStereotype Elem where Elem is the element you would like to check For example given an element Elem SysMLProfile isBlock Elem returns True if the element Elem has Block stereotype applied and returns false otherwise 8 1 2 MD Customization for SysML Profile You need to import com nomagic magicdraw sysml util MDCustomizationForSysMLProfile to use this API class Get a string constant for each property of stereotype tag Usage includes MDCustomizationForSysMLProfile STEREOTYPE_PROPERTY_NAME Stereotype Usage For example MDCustomizationForSysMLProfile NUMBEROWNER_PREFIX_PRO
64. block as its context using the IBD shortcut menu Diagram Specific Procedures ibd Block ModifiedF iA gaj Modified yy rightHaltShatt x rfw FrontWheel 1 Figure 61 Sample of structure displayed in IBD 4 You can also display the structure of the FrontWheelsAssembly block in the structure compartment of the block itself 5 2 2 13 Converting nested parts to dot notation To convert a Part or a set of Nested Parts to the Dot Notation form simply drag such Parts and drop them on another valid view For example drag the part d D to empty space in the containing diagram as shown below Figure 62 Drag and drop the part to be converted to dot notation The confirmation dialog will be then open Click the Show in Path Notation button to convert the Part to the Dot Notation form Then the part will be moved to the diagram canvas and displayed in the Dot Notation form Figure 63 Dot notation part created Diagram Specific Procedures You can also move the created part from the diagram back to the structure compartment of the part b B The part will then be moved to the structure compartment and shown in the Dot Notation form Figure 64 Dot notation part in Structure compartment You can also convert a Part displayed in the Dot Notation form to a set of Nested Parts where applicable Simply right clicks the part and then select Refactor gt Con
65. ces NEW Managing Interfaces of the Proxy Port Create Directed Features and Specify Feature Directions Displaying Structures of Blocks in Compartments and IBDs 5 2 2 1 Creating Ports You can easily create full and proxy ports A full port is a part on a boundary You can now easily convert your parts into full ports by dragging them to the diagram frame All ports connectors other information including the layout will remain unchanged To convert a part to the full port 1 Select a part and drag it to the diagram frame 2 When the diagram frame is highlighted release the part The full port is created on the diagram 92 frame When the full port is created on the diagram frame you cannot drag it back except Undo the conversion Copyright 2009 2015 No Magic Inc Diagram Specific Procedures ibd Block PC SBC USB Drag part to diagram frame E proxy proxy proxy pi USB p2 USB Motherboard A ibd Block PC SBC USB proxy proxy proxy pi USB p2 USB i p3 USB Figure 39 Part converted to full port To create a proxy port 1 Select a part or a port on the part and from the smart manipulator toolbar select Connector 2 Attach a connector to any part or diagram frame The appropriate port is created ibd Block PC SBC USB proxy proxys proxys pi USB p2 USB p3 USB Motherboard A v Attach connector to diagram frame
66. cific Procedures bdd Package Satelltelnstancel2 Sh Instance of the SatellteSystem blocks stem Satellite Con satellitesystemn coart Insi satellitesystem ins Frol satelliteSystem prot Psyl satellitesystem psyi Weaight blocks blocks satelliteSyvst satelinteSyst em cont Control ud Poon 2000 Power 1000 Wicon 400 Wiosy 3000 hlocks blocks satellteSyst satellteSyst em ins1 em prot Instruments Propulsion Pins 2700 Fpro 4800 wins 2700 wipro 4800 Figure 31 Example of instance created with Automatic Instantiation Wizard with initialized slots 7 Right click the Satellitelnstance02 package in the browser and select ParaMagic gt Util gt Create CXI_heading 8 Right click again and select ParaMagic gt Util gt Add default causalities The package will then be ready for ParaMagic Plugin 9 Right click the Satellitelnstance02 package in the browser and select ParaMagic gt Browse to open the ParaMagic browser Diagram Specific Procedures A ParaMagic IM 16 0 SatellitelnstanceO 2 Symbal Satellite system E Cont oo Poon i weon se Insi r Fins i Wins se Frol oo Poro i wpro EI Psy r Power a Wipsy Weight Collapse All rook i SatelliteSystem Local Relation Type Causality Valles Satellite system Control FEAL FEAL undefined undefined Instruments REAL REAL Propulsion REAL REAL Unde
67. city CA FuelEconomy CA OFFRoadCapa LE PassengerCa CA Performance CA Power H LA PowerSource CA Qualification CA Range H5 CA Regenerative CA SaFetyTest EE E e i E AE Are a a Ba pew ou oo uo a ft oo UW AT Figure B 38 Special C testRun060401 HS tH testVehidled HSUV i 2 El t HSUVModel HSUYV St j E testVehide1 HSUVMod h AA Verify HSUVModel HSU AAR HSUV Requirements EL Association HSUvModel f hag HSUVModel HSUV A Assocdation HsUVModel ER HSUVModel HSUY Figure 6 Satisfy Requirement matrix 3 2 1 3 Verify Requirement Matrix The 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 Dependency Matrix a Vv p arih j Ma rik X meg 2 ia fa Criteria Row Element Type ecificationAction ValueType Pe Column Element Type Requirement Souda i HSUVModel ModelingDomain Column Scope iba att stn Dependency Criteria Verify E Direction Row to column w Sh lir EiT E k ee SUY c CargoCapacit CA Eco Friendine CA Emissions H5 C Ergonomics CA FuelCapacity CA FuelEconorny CA OFFRoadCapa LE PassengerCa C4 Performance CA Power Hi Le PowerSource CAl Qualification
68. ck the Up icon on the table toolbar or press Ctrl Up Down To move the selected row of requirement down either click the Down icon on the table toolbar or press Ctrl Down 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 supports for the multiple selection of the nested requirements which are owned by the same owner 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 Report The SysML Requirements Table allows you to generate a requirements report directly from the table The default report template used is Requirements Table Type A To generate a report click the Report icon on the table toolbar The template drop down menu will then open Select the report template you would like to use The Generate Report dialog will then open 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 but
69. constraints to be validated against select another smaller validation 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 chosen 4 In the Validate For drop down list select one of the following e Whole Project to validate the entire SysML project e Validation Selection to validate only specific elements in that SysML project Bd Validation Ed Validation Validation Suite Fy S sML YalSuite MD Customization For SyvsMLi SysML constraints we Validate For Whole Project Whole Project Validation Selection Exclude elements from read only modules lw Minimal Severity Validation Options Figure 2 Validation element selection 5 If you have selected Validation Selection click the browse button to open the Select Elements dialog Add elements to the Selected objects pane using buttons in the middle of the dialog Only the element s listed in the Selected objects pane will then be validated When all required elements are selected click OK Validation LAW Select Elements All data Selected objects HSU sample A mpSelected objects E Relations E E A HSU Model ER matrix templates me _ Baer Mo AN fo Add ll H E ModelingDomain
70. d from UML 4 5 2 Extended Requirement Description A SysML Extended Requirement is a standard Requirement subtype which adds some properties to a requirement element These properties such as source risk and verify method are important for requirement management Specific projects should add their own properties All these properties are now available in the standard Requirement Specification window and Requirements Table If any of these property values is specified a requirement is automatically converted to ExtendedRequirement 4 5 3 Functional Requirement Description A Functional Requirement is a requirement that specifies a behavior that a system or part of a system must perform SySML Requirements Diagram Elements 4 5 4 Interface Requirement Description 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 4 5 5 Performance Requirement Description 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 4 5 6 Physical Requirement Description A Physical Requirement specifies the physical characteristics and or physical constraints of a system or a system part 4 5 7 Design Constraint Description A Design Constraint is a requirement th
71. dependency e Column a named element that can be the supplier element of the Allocate dependency SUPPORTIVE DIAGRAMS Dependency Matrix PT Row Element Type cificationAction ValueType Column Element Type cificationAction ValueType Row Scope Column Scope HSUVModel ModelingDomain Dependency Criteria mi Direction Row to column w Es ItemFlow flo AG CE peu HSUYM 1 Connector fu 12 9 HSUVModel EF HSUV Behavior EQ Figure 8 33 Behavior Mo 3 El ProvidePower trans D alProportonPower a2 ProvideGasPo O a3 ControlElectric at Provideblectri L driveCurrent F HSUV Structure 8 InternalCombustionEngine La Connectorsfdist Hsu PowerSubsystem Figure 5 SysML Allocation matrix 3 2 1 2 Satisfy Requirement Matrix Satisfy Requirement Matrix consists of 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 28 Copyright 2009 2015 No Magic Inc Dependency Matrix Criteria Row Element Type 2cificationAction ValueType es Column Element Type Requirement Row Scope HSUVModel ModelingDomain coe Column Scope HSUVModel ModelingDomain Dependency Criteria Satisfy ee Direction Row to column w Ly pem i LE CargoCapacit CA Eco Friendine CA Emissions HS CA Ergonomics CA FuelCapa
72. e 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 e Using Context Specific Value Compartments e Displaying Context Specific Value Compartments e Selecting the Context of Context Specific Value Compartments e Customizing Context Specific Value Compartment Display e Value Propagation You can see an example of a Deep Reconfiguration project by opening context specific values mdzip in the lt md install dir gt samples SysML directory 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 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 va
73. e 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 having composite aggregation kind Flow Properties properties which apply the FlowProperty stereotype All other properties which cannot be classified into the previous compartments In addition three SysML compartments are provided for displaying the Constraint Block properties constraints others and parameters compartments constraints PowerEquation Cons e itp shlpvr fodFy i parameters whlpyvr Horsepwriunit hg Real Ld Real Ct Real tw Weightiunit lb t Horsepwriunit ng vo Veliunit mgh Figure 23 SysML constraint block compartments SysML Compartments constraints others parameters Displayed Elements Constraints and Constraint Properties Constraint Properties are properties that are typed by Constraint Blocks or subtypes of a Constraint Block always having composite aggregation kind All other properties that cannot be classified into the previous compartments Constraint Parameters reusing the ports compartment of a Class 5 2 1 4 Creating an association block Participant properties will be created automatically when an Association Block is created between Blocks To create an Association Block in a Bl
74. ecific Values group 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 example if the selected context is A then the compartment label will be values A To select a context using the shortcut menu e From the selected part s shortcut menu select Context Specific Values gt Context Generic Procedures 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 the Symbol s Properties dialog or the part shortcut menu To display or hide element type 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 e None to hide types e Name to display the names of the element types e Qualified Name to display the qualified names of the element types Ad Pro perties Part lt lt PartProperby gt gt Show Tagged Values On Shape Show Tagged Values Stere true Show Qualified Names For P False Show Default Value False Suppress Structure Show Slot Type Symbal ID Symbol Bounds Mame E Qualified Mane Suppress UML properties Suppress references False Some ees tore C Fsleo Show Slot Type Show slot typ
75. el of risk or no risk To indicate that verification will be performed by technical 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 To indicate that verification will be performed by the operation movement or adjustment of the item under specific conditions to perform the design functions without the record of quantitative data Demonstration is typically considered the least restrictive verification type Diagram Specific Procedures Enumeration Enumeration Function Literals Inspection To indicate that verification will be performed by examining 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 Test To indicate that verification will 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 specified requirements Test Cases a on A The type of return parameter Direction
76. elated procedures Requirements Diagram Procedures LIAN DANA N ANAL AIA NA a T CC INV Q P 7A N IA A NONIO INA EW ZUUYSI ZU O INO WMidU AT LVUGA LVIVINY IVIGAY Pit SySML Diagrams 2 1 6 SysML Activity Diagram Description Activity diagrams describe control input and output flows among actions They represent the system business and 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 Sample act Activity showDialog showDialog acreateObjects eel Controller d Dialog value Zz eaddStructuralFeatureValues object application d ereadSelfs result self eaddStructuralFeature alues controlDialog he Figure 5 SysML Activity diagram Related elements Accept Change Structural Feature Event Action Change Structural Feature Event Invocation on
77. en Clear the Show centerlines in flow diagrams option under the Diagram gt Display group of the Environment Options dialog Se ae ee EE E C Common E5 Note act Activity ACTI B Fa ACTI E abe Text Box T E Anchor T 7 Dependency Image Shape Separator HF SysML Activity Diag Figure 96 Show Centerlines button Diagram Specific Procedures 5 2 6 3 Decomposing activities 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 hierarchies in a diagram structure To decompose activities using the Activity Decomposition Hierarchy Wizard 1 Do one of the following e From the SysML Activity diagram shortcut menu select Activity Decomposition Hierarchy Wizard e On the main menu select Diagrams gt Diagram Wizards gt Activity Decomposition Hierarchy Wizard e On the main menu select Analyze gt Model Visualizer The Model Visualizer dialog opens Select the Activity Decomposition Hierarchy Wizard 2 Follow the three steps in the Activity Decomposition Hierarchy Wizard The Class Diagram will then be generated class HSU sample 29 Decomposition of Activity Accelerate ProvidePow er Monitor Traction Criving ProvideGasPow er ca saatti ity Accelerate pr ov idePovy er lt lt a ctwity Pro
78. ens when you move the pointer over the Proxy or Full Port or their names 4 Diagram Specific Procedures Te Contain E structure 40 Diagrams f Nater Heatin J Jement X prere m 2 x Bw B A Data E rE Data E 00 User Needs H E 01 Conceptual Model H E 02 Functional Model 1 6 03 Physical Model H E 34Interfaces Eg 31Kafeeautomat E 32 Brewing Group E 651 E 33 Water Heating Element Bo Steam Dispenser E Cl steamMass Real 1 0 Fl Ol steamMassRequired Re E Cl steamMassPerSecond R in Data 03 Physical M Bl in steam in Data 03 Ph if in milkin Data 03 Physi P out frothy milk out Da open Steam Valve EH E E out e milk out iMilk in steam adjust AdjustSteam Figure 44 Places of displaying Proxy or Full Port s direction prefixes 5 2 2 5 NEW Displaying Combined Direction on Proxy Port Combined direction consists of all owned and inherited flow properties and directed features of the Proxy Port The flow properties direction are shown by default on the Proxy Port shape To include directed features into combined direction of the Proxy Port set the Include Directed Features into Combined Direction of Proxy Port property value to true in the Project Options dialog If all features have direction out or provided the combined direction is out If all features have direction in or required the combined direction is in
79. ent Edit dialog 4 Select the element properties constraints and tagged values that you want to show in the callout box Then click OK to close the dialog 5 Select Show Tagged Values on the context menu of Note symbol to show the selected tagged values in the callout box allocatedFrom ehlocksElement2 eConnectorsElement4 connectort allocatedTo eblocks eatomicFlowPortsElement3 portt Block spartsElement4 parti Figure 35 Callout box with SysML callout style 6 You can customize the way the callout box looks using the Symbol Properties dialog of Note symbol 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 for example block connector atomicFlowPort and part will be shown instead of the icon of the tagged values which are the model elements Diagram Specific Procedures 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 Lag Symbol Properties HTML Text true Text Display Mode Do not 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 Im
80. ent of a part using either the Symbol Properties dialog or the part shortcut menu Generic Procedures To display a compartment using the Symbol Properties dialog e Inthe 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 To suppress a compartment using the Symbol Properties dialog e Inthe 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 Ad Pro perties Park 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 Suppress Context Specific alues Suppress Context Specific values compartment Apply Style Default I Make Default Figure 11 Symbol Properties dialog Suppress Context Specific Values 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 To suppress a compartment using the part shortcut menu e On the shortcut menu select the Suppress Context Specific Values option under the Context Sp
81. ents and IBDs 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 limitation exists when you need to modify or extend existing structures in subtypes Composite Structure diagrams will only let you display e Parts e Nested parts e Ports on the frame e Ports on every part e Paths for every part and port Nested parts can be displayed with the dot notation in addition to using structure compartment In the Display Parts dialog when only the nested part property of a class is selected that class with the nested part property selected will be displayed with the name of the class that contains the nested part property inside and the name of the nested part separated from each other with the dot notation Diagram Specific Procedures Display Parts Displaying SysML parts and deep nested parts on shapes Select parts you want bo display on the shape and ensure that their checkboxes are Fully selected with black checkmarks To display deep nested parts in SyshL dot notation simply select the deep nested parts Click OK when you are done ncapsulated Centrifugal Pump A ine Cel bearings Tips and Tricks Blocks Bearing 3 Tips and Tricks Blocks Centrifugal Pi easting Tips and Tricks Blocks Casting Tips and Tricks Blocks Centrifugal Pump CA discharge Tips and Tricks Blocks Discharge Nozzle
82. erFuel for fuelReturn instead then reassign the fuelReturn slot in the HSU internalCombustionEngine InternalCombustionEngine instance specification to SuperFuel a Fuel kind with a specific fuelPressure Diagram Specific Procedures G Instance Specification HSU internalCombustionEngine abe 5 History HSU internalCombustionEngine HSU Model HSU Structure Internal E HSU internalCombustionEngine HSU Slots n B Documentation Hyperlinks a gt EE Property are Usage in Diagrams Bet Fe Fa Pert fuelReturn Fuel value ve Deployed Artifacts H E Slots bw Inner Elements ve Relations me Tags 2 Constraints 8 H InternalCombustionEngine iB crtl i fi HSU internalCombustionEngin i fil HSU internalCombustionEngi i fiz HSU internalCombustionEngi i f3 HSU internalCombustionEngi i S fid HSU internalCombustionEngi iF Fp FS_ICE i CE fr FuelRequlator i B fra HSU internalCombustionEng i CH ft FuelTankAssembly P FuelFitting Fuel mage ruelReturn Fuel p Select Elements Es HSU Structure Selected elec ng Po HSUY Interfaces 5 E EJ ICE Type LE Sanerriel HSUVModel HSU ef HSULinternal E HSU internal E HSU internal Add E HSU internal E HSU internal Add Al E HSU internal E HSU internal E HSU internal E HSU internale E HSU internal E HSU internal E HSU internal SuperFuel H Add Rec
83. ered automatically To number requirement IDs automatically 1 Click Options gt Project on the main menu The Project Options dialog will open 2 Under the SysML group select the Use Element Auto numbering check box 3 The IDs of any newly created requirements will now be numbered automatically with the Numbering Style Prefix and Separator which are defined in the requirement owner Automatic Numbering will NOT modify any existing ID Thus requirements with IDs will NOT participate in Automatic Numbering Diagram Specific Procedures Suggested Solutions for Invalid Requirement s ID When the ID of a requirement element is invalid with respect to the validation constraint Requirement A a requirement s ID must be unique the requirement will be highlighted If you select such a requirement the requirement smart manipulator menu will also propose the following two solutions Assigning A New Number You can also use this solution to automatically re assign a new requirement s ID to the selected requirement The first available correct ID will be assigned to the requirement automatically A Open Requirement ID Nurmbering dialog A l Ignore areguirements requirements Rx Ry Select in Validation Results lil y Text Wout Figure 86 Assign new number solution Finding A Requirement To find a requirement in the Containment tree and in the Requirement ID Numbering dialog tree 1 Select a
84. erfaces E Accelerator E E AutomotiveDomain J BatteryPack BodySubsystem E BrakePedal AS Brake Subsystem E CAN_Bus AS Chassissubsystern i E Differential L E ElecFower ngm ElectricalPowerController Figure 5 Structure standard normal display cele oe po body Subsystent J BrakeSubsystem EJ ChassisSubsystem iL ElectricMotorGenerator EG Hybrid Suv E InteriorSubsystem O InternalCoambustionEngine pL LightingSubsystem AS PowerSubsystem nE Transmission EJ AccelerationEquatian Accelerator E AeroDragEquation et i AubomotiveDomain ES Baggage sE Balance Weight E BatteryPack i H Block nE BodySubsystem Figure 6 Structure Browser plain list display Generic Procedures Show Inherited Structure The Structure browser can show the properties that are inherited from the generalization classifier bdd Model Data E ck zeblock gt zeblock a seblock ChassisSubsystem BodySubsystem BrakeSubsystem ElectricMotorGenerator lt Figure 7 Four specialization classifiers of blocks EE BodySubsystem Ol 5N IB El EQ BrakeSubsystem LO 4 5N ID AS ChassisSubsystern LO 45ND E ElectricMotorsenerator i C generatorEfficiency Real i Ol motorEfficiency Real i C 5N ID Hybrids l LightingSubsystern b BodySubsystem b C p PowerSubsysten p c ChassisSubsystem c i Interior Subsystem i
85. es in default values compartment Apply Style Default ka Make Default Figure 12 Symbol Properties dialog Show Slot Type To display or hide element type using the part shortcut menu e From the selected part s shortcut menu select Show Slot Type and then select a display mode Value Propagation The Value Propagation mechanism enables values that are not overridden by the values from the selected context 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 Context Specific Value Compartment indicating that the property is not reconfigured at all See the following figure for an example of the Context specific Values Compartments having the Value Propagation enabled Generic Procedures bdd Model Datal ES BED lt lt block lt hlock gt lt bhlock gt Locati hi Uni s lt block gt ocation ing niverse Utd Thin fats Location Tl ao ti isC sS s lt black s lt block gt Location eeblock eeblocks gt Util Location wakes t1 Thing t2 Thing x Real 0 Parts Parts y Real 0 Location TJ Location TI z Real 0 vale si Thing zab
86. f it or on its tab To display a package name 1 Right click a package and select Header Position on the shortcut menu 2 Select either e Top to display the package name on top e In Tab to display it in the 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 2 The elements owned by the package will then be displayed in the package Diagram Specific Procedures Figure 76 List of elements 5 2 4 SysML Parametric Diagram Procedures SysML Parametric Diagram features include Display Parameters and the other six specific features similar to IBD They are as follows e Displaying parameters e Creating automatic constraint parameters e Creating a binding connector For more information on the above six features see the SysML Internal Block Diagram Procedures section 9 2 4 1 Displaying parameters 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 Do one of the following e Select Display Parameters on the property shortcut menu e Click the Display Parameters icon on the property smart manipulator 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 3 Select constraint parame
87. f the block owning the port except ports that are not full Full ports cannot be behavioral isBehavior false Full ports cannot be conjugated isConjugated false Interface blocks cannot own or inherit behaviors and have classifier behaviors or methods for their behavioral features Interface blocks cannot have composite properties that are not ports Ports owned by interface blocks can only be typed by interface blocks Interface block should inherit from interface block only The onPort property of an invocation action must have a value when this stereotype is applied The port at the first position in the onNestedPort property must be owned by the target object of a stereotyped action The port at each successive position of the onNestedPort property following the first position must be contained in the block that types the port at an immediately preceding position Within a stereotyped invocation action the onPort port of the invocation action must be contained in the type of the port at the last position of the onNestedPort list An ItemFlow itemProperty must be typed by a Block or by a ValueType ltemProperty is a property of the common possibly indirect owner of a source and target If an ItemFlow has an itemProperty one of the classifiers of conveyed items must be the same as the type of the item property Item property cannot have a value if the item flow is realized by an Association If an
88. f you do not see the OMG SysML style option in the Symbols properties styles panel click the Import button The Open dialog opens 7 Open the lt md install dir gt templates SysML directory and select OMG SysML style stl 8 Click Open 9 The OMG SysML style option will appear in the Symbols properties styles panel 10 Select it click Make Default gt OK The OMG SysML style is now a default style in your SysML project However you can apply such style only to a SysML diagram The following steps show you how to apply the style to a SysML diagram To apply OMG SysML style on a SysML diagram 1 Open the Project Options dialog 2 Select OMG SysML style in the Symbols properties styles panel 3 Click the Apply button The Select Diagrams dialog opens 4 Select a SysML diagram you can select more than one diagram and click OK Generic Procedures 5 Click the OK button in In the Project Options dialog Applying OMG SysML style to existing SysML diagrams might distort the diagrams Use the Layout feature on the main menu of MagicDraw to change how diagram looks 9 1 4 Using QUDV Model Library QUDV Model Library is introduced in Annex C Non normative Extensions to OMG SysML Specifications 1 3 This model library is designed in such a way that extensions to ISQ and SI can be represented as well as any alternative systems of quantities and units For more information see Model Library for Quantities Units Dimensio
89. ferenced unit The action has exactly one trigger the event of which 9 3 2 1 must be a Change Structural Feature event The action has two result pins with the type and order 9 3 2 1 the same as the type and order of the structural feature of an trigger event The action s multiplicity is also compatible with the multiplicity of a structural feature The structural feature of a trigger event must be owned 9 3 2 1 by or inherited to the context of the behavior containing an action The context of a behavior is its owning block or itself if it is not owned by a block See the definition in the UML 2 Superstructure Specification Visibility of the structural feature of the trigger event 9 3 2 1 must allow access to the object that performs the action The structural feature must not be static 9 3 2 3 The structural feature must have exactly one 9 3 2 3 featuringClassifier Derived from OMG SysML spec 8 3 2 2 8 3 2 2 8 3 2 10 Validation Constraint DirectedFeature DirectedFeature FlowPort FlowPort FlowPort FlowPort FlowPort non active FlowPort FlowProperty FlowProperty FlowSpecification Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 3 with permission DirectedFeature can only be applied to behavioral features or to properties that do not have FlowProperty applied including subset or redefined features Operations
90. fined undefined undefined undefined Powersystem REAL REAL REAL undefined undefined undefined Update to SyshL Weight Prol Worot Ins1 Wins Conl Wweont Psy1 wps poner O Eo 7 Figure 32 ParaMagic browser 10 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 MagicDraw UserManual pdf 5 2 1 8 SysML callout box For more information about using the Automatic Instantiation Wizard see Automatic Instantiation Wizard chapter in To create a callout box showing the attributes constraints and tag values of an element 1 Do one of the following e Create an anchored Note to the symbol of element on the diagram using the anchor button on the smart manipulator e Create a 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 a Note e Select the context menu items in Edit Compartment menu group Diagram Specific Procedures Edit Compartment shocks Block Figure 33 Edit Compartment manipulator button 3 The Compartment Edit dialog will open Ag Compartment Edit Element Properties Constraints Tagged Values All Selected isEncapsulated true allocatedFrom Element connector 1 allocatedTo porti part1 Figure 34 Compartm
91. g ones from your model to the table e Directly edit the properties of requirements in the table e Directly generate requirements reports renumber requirements IDs or export the table into a CSV or HTML format or into a Microsoft Excel xlsx spreadsheet e Quickly search and filter requirements e Easily access custom requirement s properties Column Name Visible by Description Default Y A row number ID Y A requirement s ID Name Y A requirement s name Text Y A requirement text Requirement Type N A requirements type for example business requirement or design constraint Owner N A Requirement s owner Source N For extendedRequirement and its subtypes only The source of a requirement Risk N For extendedRequirement and its subtypes only The risk level of a requirement Verify Method N For extendedRequirement and its subtypes only The method to verify a requirement Requirements Table Ht HSUV Requirement Table a orem Add Nested 1 Add Existing HG Delete From Table fm Delete lt E Export E Report a gt 4 Up lt 4 Down dim Unnest Requirement H Nest Requirement h Show Columns B Show Full Paths Filter Q Id Satisfied By PowerSubsystem Name ma Power C RegenerativeBraking sia Em cargocapecty Figure 1 Requirements table Creating A Requirements Table You can create a Requirements Table using the main toolbar main menu
92. gram Specific Procedures With the Display Internal Structure feature you can copy and paste display an existing structure diagram defining a Block Class either in e The structure compartment of that Block a subtype of that Block a part typed by that Block or a 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 2 Right click the property and select Related Elements gt Display Internal Structure from the shortcut menu 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 the following figure the FrontWheelsAssembly IBD is available Select it to display the structure of FrontWheelsAssembly block in the property lt lt block frontWheelsAssembly FrontWheelsAssembly lei wheel Frontvvwheel d t2 Torque spline t1 Torque Figure 60 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
93. h represents an association between two Deployment Targets It connects actors to use cases 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 Extend An extend relationship provides an optional functionality which extends the base use case at defined extension points under specified conditions Generalization A generalization relationship provides a mechanism to specify variants of the base use case SySML Diagrams Use cases are often organized into packages with the corresponding dependencies among the use cases included in the packages uc Model Use Cases Use Cases Inverted Pendulum System set Amplifier Gain set ControllerGain stop Controller i start Controller disturb System Nuisance Figure 6 SysML Use Case diagram Related elements External System Sensor Boundary System User System Actuator Environmental Effect Related procedures SysML Use Case Diagram Procedures 2 1 8 Views and Viewpoints Diagram Description The concept of View and Viewpoint reflects perspectives of different stakeholders The views are constructed from a subset of the model that addresses their concerns The new technology interprets Views and Viewpoints models to construct XML document conforming with DocBook standard A combination of diagrams tables model
94. he Port The tilde symbol appears before the direction prefix when the Port is conjugated Name of the Port Type of the Port Features of the Port type Description Opens the Specification window of the selected Port Opens the list with the available to create properties Click to create the Connector property Part property Reference property Value property Constraint property Flow property Duplicates the selected item and marks its name in ascending order Removes the selected item from the list 5 2 1 10 NEW Managing Block properties All owned and inherited Block properties are collected on the left of the Block Specification window gt Properties Block properties are grouped as in the Block compartments Manage them by creating redefining or deleting directly in the General Specification pane Diagram Specific Procedures Block properties The Properties node contains a list of Block properties Create or delete properties Use the properties specification button to edit properties of a specific attribute E E Documentation Hyperlinks Usage in Diagrams E E Usage In E Constraints E E Ports Interfaces ee Operations Behaviors Relations 4 Allocations Instances Properties Em ER abe Name Type Owner El Flow Properties in fuelSupply E Fuel HS EJ FuelTankAssembly out fuelReturn E Fuel HS FuelTankAssembly El Part Properties fp E FuelPump
95. iagram e SysML Block Definition diagram SysML Parametric diagram SySML Activity diagram UML Class diagram UML Composite Structure diagram Generic Procedures e UML Activity diagram The following figure illustrates the function declaration in m file It is for least square fitting to find the slope m and the y intercept b of a straight line equation from two given input parameters x and y The constraint expression is m b linefit x y The constraint parameters are x y m and b After the function transfer into the element its type property and parameter are set automatically and are displayed on the element shape Constraint Block FA Transfer mathematical expressions into linefit m Least squares Tit of data to y m x b constraints Function m b linefit x y Constraint linefit C X Property m b linefit x y y w 517e x 1 a gt d Call Behavior Action Figure 19 Creating Constraint Block Constraint Property or Call Behavior Action from MATLAB source code The name of the created element is the same as the name of the function in the m file If the name of that element already exists the name duplicates with incremental number at the end of the name F Te Containment Containment 3 x Ee yw Q it B Data E Relations 7 i HEJ constraints linefiti m b line fit x y parameters pareamerers parameisrs x Real x Real x Real
96. ially Defining Flow Specifi Zz tal T Aeelor skeae lI bi Figure 55 Select Port Type dialog for Provided Required interface Displaying Existing Provided Required Interfaces To display the existing Provided Required Interface of a port 1 Right click a port to open its shortcut menu and do one of the following e select Show Required Interfaces or Show Provided Interfaces e select Related Elements gt Display Provided Required Interfaces 2 The Required Provided Interfaces will be displayed on the port in the form of ball socket lollipop notation Diagram Specific Procedures ibd Block Assembly Fal Assembly zablock 5 zeblock Parti Part lt block e lt block Porte Part Figure 57 BDD with parts ports and interfaces Diagram Specific Procedures 5 2 2 10 NEW Managing Interfaces of the Proxy Port The detailed information about Proxy Port interface is collected on the left of the Port Specification window gt Interface Block Properties The Properties node contains a list of Proxy Port properties Create or delete properties Use the properties specification button to edit properties of a specific attribute Interface Block Properties Name Type Default Value Owner El Flow Properties in c E Coffee Data 0 C4 iCoffee Data 03 E E ae Block Properties Redefine Delete 4 ui SS ee I Figure 58 Proxy Port Specification wi
97. ides a model library that contains predefined value types You can use them for typing the value properties in your SysML model These value types use the units and quantity kinds defined in the QUDV model library Name Unit Quantity Kind A ampere SimpleUnit electricCurrent SimpleQuantityKind Alm amperePerMeter DerivedUnit magneticFieldStrength DerivedQuantityKind Alm amperePerSquareMeter currentDensity DerivedQuantityKind DerivedUnit Model Library for Quantities Units Dimensions and Values QUDV Quantity Kind becquerel DerivedUnit radionuclideActivity DerivedQuantityKind coulomb DerivedUnit electricCharge DerivedQuantityKind candela SimpleUnit luminousIntensity SimpleQuantityKind cd m __ candelaPerSquareMeter DerivedUnit farad DerivedUnit gray DerivedUnit luminance DerivedQuantityKind capacitance DerivedQuantityKind Gy absorbedDose DerivedQuantityKind henry DerivedUnit hertz DerivedUnit joule DerivedUnit inductance DerivedQuantityKind frequency DerivedQuantityKind energy DerivedQuantityKind kelvin SimpleUnit katal DerivedUnit kilogram SimpleUnit thermodynamicTemperature SimpleQuantityKind catalyticActivity DerivedQuantityKind mass SimpleQuantityKind kilogramPerCubicMeter DerivedUnit lumen DerivedUnit kg m massDensity DerivedQuantityKind luminousFlux DerivedQuantityKind lux DerivedUnit illuminance DerivedQuantityKind mete
98. ing requirement element 129 SySML Activity Diagram Procedures 131 Select Operation 131 Dynamic Centerlines 131 Decomposing activities 133 SysML Use Case Diagram Procedures 137 Numbering Use Cases 138 SySML Sequence Diagram Procedures 138 Model Library for Quantities Units Dimensions and Values QUDV 140 QUDV Model Library 140 QUDV 140 SI Definitions 140 SI Specializations 140 SI Value Type Library 140 Validation 143 Active Validation 147 Active Validation Options 150 SySML Constraints 151 Stereotype Usage 158 SYSML Profile 158 MD Customization for SysML Profile 158 SYSML Profile API Changes 159 SysML classes for open API 160 Systems Modeling Language SysML is designed to unify the diverse modeling languages 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 Requirements Activity and Use Case diagrams SysML Plugin also makes it possible for MagicDraw to support additional specifications analysis designs and validations on a broader range of systems and system integrations The SysML sample projects are available in the lt md install dir gt lsamples SysML directory 1 1 Sy
99. iption of each property Descriptions are presented in the description area of the Specification window The AllocatedActivityPartition stereotype is applied on the partitions automatically when creating swimlanes Allocation Mode is now available for the swimlanes e Definition mode allocates a behavior to the block This mode is selected by default e Usage mode allocates an action to the part 3 wimLaneDiagrams act Activity ProvidePower Figure 6 35 Detailed Behavior Model for Provide Power alocate alocate pecu PowerControlUnit ice InternalCombustionEngine Symbol s Properties Alt Enter Refactor Related Elernents Insert Swimlane Insert Inner Swimlane Delete Swimlane Figure 98 Allocation modes Making changes in the model changing types moving elements among swimlanes changing allocation mode etc can impact allocations In this version all such changes are validated automatically In the swimlanes the actions that are not allocated or allocated incorrectly are highlighted and automatic solutions are suggested alocate x locate epc i ElectricalPowerController emg ElectricMotorGenerator aa ControlElect ric a x E INUOUS di Current Figure 99 Highlighting not allocated behaviors Diagram Specific Procedures All allocated behaviors are now listed in the Behaviors property group of the Block Specification window The Behavior node contains
100. k SysML Parametric or UML Composite Structure diagrams Constraint Block automatically is set as type for newly created Constraint Property The properties and parameters of Constraint Block are displayed on the Constraint Property shape e Call Behavior Action with its pins and opaque in the SysML or UML Activity diagrams Drag the m file onto the already existing element shape empty or full to set one of the following Diagram Specific Procedures e Constraints and parameters for Constraint Block in the SysML Block Definition or UML Class diagrams e Type for Constraint Property by creating new the Constraint Block in SysML Internal Block SysML Parametric or UML Composite Structure diagrams The properties and parameters of newly created Constraint Block are displayed on the Constraint Property shape To transfer the mathematical expression into the Constraint Block or Constraint Property 1 In the Containment tree or on the diagram pane select a Constraint Block or Constraint Property with set type 2 From the shortcut menu choose Tools gt Create Expression from M File The Open file dialog opens 3 Select the m file and click Open The constraints and parameters are set for Constraint Block Related diagrams SYSML Block Definition Diagram BDD SYSML Internal Block Diagram IBD SYSML Parametric Diagram SYSML Activity Diagram Related external resources Class Diagram in Magic Draw UserManual pdf
101. l be subject to greater torque and boltTension 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 Generic Procedures 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 TruckWheelAssembly right down to a TruckLugBoltJoint However you could use instead SysML PropertySpecificT ype strategy which is a set of on the fly extensions 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 PropertySpecificT ype section in OMG SysML specifications For more information about Deep Reconfiguration see htip training nomagic com 5 1 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 Progressive Reconfiguration the capacity of a FuelTank ina Vehicle context is reconfigured to 46 litres In the WheelHubAssembly example see Deep Reconfiguration the diameter of the Tire Tir
102. lace the use of flow specifications which have been deprecated Sample alnterfaceBlocks FS _ ICE flow properties out engineData lCEData in mixture Real in throtthePosition Real Related procedures NEW Managing Interfaces of the Block NEW Managing Interfaces of the Proxy Port 4 1 9 Flow Specification Description A Flow Specification specifies inputs and outputs as a set of flow properties It has a flowProperties compartment 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 The only valid attribute of a Flow Specification element is a Flow Property For more information on the flow port and the flow properties please refer to the SysML Internal Block Diagram Procedures chapter SYSML Block Definition Diagram Elements Sample Flow Specifications FuelFlow afo WP pet yoo fuelReturn Fuel readOnly direction in fuelSuplly Fuel readOnily direction out 4 1 10 Value Type Description 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 Value 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 3 specification In gene
103. laying Rake icon on symbol e Transferring mathematical expressions from MATLAB source code into the model 5 1 1 Creating SysML Projects To create a new workspace for a new project 1 Do one of the following e Click File gt New Project on the main menu e Click the New Project button on the main toolbar e Press CTRL N The New Project dialog will open 2 Click the SysML Project icon on the left hand side 3 Enter a filename in the Name box 4 Click the button to select a location for your new project 5 Click OK If the current perspective is not the System Engineer perspective the Open Associated Perspective dialog will open Select Yes to change it to the System Engineer perspective 52 Copyright 2009 2015 No Magic Inc Generic Procedures Create a new blank SysML project Systems Modeling Language SysML is designed for systems engineering applications Creating a SysML project will switch application to the SysML graphical user interface and will use the SysML model templates Specify a project name select a location to store the newly created project and press OK Mame Distiller_model oy 4 FHL cya Project location C Projects Project Create directory for project and related data Figure 1
104. lock lt lt block gt x Location Location lt WEer gt i J i n Wales Wales x Real 0 x Real O v Real 0 v Real U eeblock z Real 0 Zz Real 0 Ll Location valves Umi verse valves Umi verse mo H x 0 x 0 U t2 Thing y a T ae T 4 lII UniverseContext lt block gt e lt block gt UniverseContext UC u Universe 32 Ct lt lt block u Universe lt lt hlock gt lt lt back gt UC u ti Thing UC u t2 Thing t1 Thing Ut UCU Sane t2 Thing Ut2 UC ut2 lt lt block gt lt lt block gt sshock gt B sshlock gt B UC u ti Location UC u t2 1 Location t1 Thing t2 Thing parts parts Location T I Location T l sblock gt lt block gt l Location l Location wales Wales x Real 0 x Real 0 vo Real O y Real O z Real 0 z Real 0 vales Umi verse Lonte ad vaes Ui Wee Lonte rt x 0 Y agn T j H Figure 13 BDD value propagate In the UniverseContext package only the value of x of a Location is reconfigured to 3 in the UniverseContext context The values of y and z are not set by the selected context Since the value propagation is enabled the next n z 2 l la ANananurinht A NNA DN1E NA Manin Inn o0 copyrigni 2009 2015 No Ma gic INC MYS Y Y Generic Procedures context Universe is considered In the Universe context the value of z is set to 2 However the value of
105. lue of x If UniverseContext is selected the value of z instead of x will be reconfigured to 2 Generic Procedures bdd Model Datal cS BDC lt lt block gt lt lt bhlock gt lt lt block gt Locati Thi Uni a ocation ing niverse Ut Thin parts l Location T c i LTT l lt lt block e lt hlock e lt block Uti Location Wales t1 Thing t2 Thing x Real 0 i parts parts y Real 0 Location TJ Location TJ z Real 0 valves Thing lt lt black gt lt lt block i l Location l Location z wales Mees x Real O x Real 0 y Real 0 y Real 0 7 Feal 0 z Real 0 n el z pi ATTN ES SOUT UC u Universe parts yor ta WG t2 OOOO o ooo OOO TTrrrrrrr C EL e ec hlock gt u Universe shlock sshlock gt UC u t1 Thing Uc ut Thing ti Thing U t1 UG uti t2 Thing U t2 lt lt block gt lt lt block gt FE Saui UC u ti l Location UC u t2 1 Location t1 Thing t2 Thing a parts pants Location T Location TI lt lt block gt Ey lt lt block gt I Location Location Wales wees x Real 0 x Real 0 v Real 0 vo Real U z Real 0 z Real 0 UC ut Wee s Umiverse Context valne s Urine tse Context Y a Y pa Figure 10 Block Definition Diagram Displaying Context Specific Value Compartments You can display or suppress the Context Specific Value Compartm
106. lues 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 diagrams can be used to support trade off analysis A constraint block can define an objective function to compare alternative solutions SySML Diagrams Sample par Subsystem AllOrNethingFeqgulatar Fa AllOrNothingRegulator cp ControlPanel 1 chosen TemperatureSignal ct Real aconstraints sub Subtraction 1 fo ct tt SENSES LEMPErallresigna i cooling Actuator Signal constraints eva Evaluation 1 if lt 0 then heating 0 and cooling 1 if i gt 0 then heating 1 and cooling 0 if i 0 then heating 0 and cooling 0 heating ActuatorSignal cooling ActuatorSignal heating gt ActuatorSignal Figure 3 SysML Parametric diagram Related elements Moe Objective Function Binding Connector Related procedures SYSML Parametric Diagram Procedures Transferring mathematical expressions from MATLAB source code into the model 2 1 5 Requirements Diagram Description Requirements 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 Requirements diagra
107. m Info E E o Symbols properties styles 5 EE Default model properties ced Code Engineering Validation scope Exclude elements From read only modules Mark in tree and diagrams Ignored validation suites Minimal severity Ignored validation suites Cancel Figure 11 Project Option dialog Data true true Parameters Synchronizat fy warning UML Standar Reset to Defaults 7 Validation scope default data use this option to limit the scope of elements to be actively validated 8 Exclude elements from read only modules default true if this option is selected selecting the check box means true read only modules for example read only profiles will not be actively validated 9 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 10 Ignored validation suites you can enter the active validation suite s you would like to exclude from the Active Validation process 11 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 wi
108. me Packages can also be shown on Block Definition diagrams or Requirements diagrams Sample NA Related procedures SYSML Package Diagram Procedures 2 1 4 SysML Parametric Diagram Description Parametric diagrams can be defined as restricted forms of IBDs They are similar to IBDs except that the only connectors allowed are binding connectors each having at least one end connected to a constraint parameter 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 constraint parameters Constrained properties typically have simple value types that can also carry units quantity kinds and probability 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 va
109. ms display requirements packages other classifiers test cases rationales and relationships Possible relationships available for Requirements diagrams are containments deriveReqt and requirement dependencies Copy Refine Satisfy Trace and Verify The callout notation can also be used to reflect the relationships of other models SySML Diagrams Requirements can also be shown on other diagrams to illustrate their relationships to other modeling elements Sample ig R g Text Adjustthe room temperature to the temperature chosen bythe user able to set the temperature he wants in the room arefines A afines delie x F k f k w zextendedReguirements zextendedReguirements eextendedRequirements eperformanceRequirements Comfort Speed Consumption Accuracy Id ER T Id ER 2 Id ER 3 ld PR 1 Text Adjustthe room Text adjust the Text Achieve this Text The system should temperature to temperature adjustment with adjust the temperature the chosen as fast as possible the lower energy within a defined range of temperature with consumption degree Celsius no pumping ofthe system Figure 4 Requirements diagram Related elements Requirement Extended Requirement Functional Requirement Interface Requirement Performance Requirement Physical Requirement Design Constraint Business Requirement Usability Requirement Test Case Satisfy Verify Derive Copy R
110. n Nest Requirement n a Report n a T Show Columns n a c Show Full Paths n a Export n a Add New You can either click the Add New icon on the table toolbar or press Insert 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 If you have created your own custom requirement types they will appear under the Custom Requirements group in the menu for example myRequirement in the following figure 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 Requirements Table 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 f a table row is selected the requirement in that row will be selected in the Select Owner dialog automatically If the selected owner is a requirement then you are creating a new nested requirement If you click the buttons a requirement will be created promptly You can then change the type of the newly created requirement directly in the table Add Nested When a requirement is highlighted in the table you can either click the Add Nested icon on the table toolbar or
111. n actual reference point by placing the time labels as text boxes The horizontal ordering of the objects is not significant to the operation and you can rearrange them as necessary Diagram Specific Procedures The dot notation is available for the lifelines Now you can send messages directly to the deeply nested parts To display a deeply nested part 1 Create a Sequence diagram The Display Lifelines dialog opens You can open the Display Lifelines dialog in the existing diagram On the diagram pane click the right mouse button and from the shortcut menu select Related Elements gt Display Lifelines 2 Select a nested part you want to display l Make sure that the nesting part is not selected otherwise it will be displayed instead of the nested part Y Display Lifelines Display or create lifelines Select lifelines for displaying them in the aa g diagram gt m DO Also select parameters and or properties for A creating and displaying lifelines for them El C Part Property gt E CAN_Bus E Ca fuelSupply Fuel E G 91 Torque E C 1 BectricCurrent E dif Differential F CA ce InternalCombustionEngine ice fuelSupply Fuel ice fi Fuelinjector H CA fi Fuellnjector 4 fil Fuellnjector E CA fi2 Fuelinjector E f3 Fuellnjector sd Interaction PowerSubsystem PowerSubsystem Dot notation 6 1
112. n customize elements to be displayed in the various compartments of a part Such compartments include Constraints Tagged Values Default Value Structure and many more To customize a compartment of a part 1 Right click a part and select Edit Compartment on the shortcut menu Diagram Specific Procedures 2 Select a compartment to be customized The Compartment Edit dialog will open 3 In the Compartment Edit dialog move an element from the All to the Selected box to display the element 4 Click OK when done p Compartment Edit onstraints Tagged Values Default Value Structure _ properties references parks Wales LL constraints operations Selected tconstraint Constraint Block Cancel Figure 47 Compartment Edit dialog 5 2 2 8 Show Default Value and Show Slot Type Use Show Default Value to display the default value of a part If the default value is an Instance Specification the defaultValue compartment containing the Instance Specification slots will be displayed on the part instead In this case you can use Show Slot Type to display the types of the slots in the compartment 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 If the property has no default value drag an instance with slot s to the property symbol The instance will then
113. nd click to select recursively a El e EQ SatelliteSystem Satellite CA Conl Satellite Control Satellite SatelliteSystem Ca Preon SysML Profile Blocks Real Satellite Control Value 2000 Ca Wieon SysML Profile Blocks Real Satellite Control Value 400 CA nsi Satellite Instruments Satellite SatelliteSvstem i Cal Pins SysML Profile Blocks Real Satellite Instruments Value 2100 Ca Wins SysML Profile Blocks Real Satellite Instruments Value 7100 EH poweri Satellite PowerBalance Satellite SatelliteSystem CA Proi Satellite Propulsion Satellite SatellitesSystern i Cl Ppro SwsML Profile Blocks Real Satellite Propulsion Value 4800 Co Wipro SysML Profile Blocks Real Satellite Propulsion Value 4800 CA Psy1 Satellite PowerSystem Satellite SatelliteSystemn o Cl Power SysML Profile Blocks Real Satellite FPowerSysterm Value 1000 wpsy SysML Profile Blocks Real Satellite PowerSystermn value 3000 2 Cal weight SysML Profile Blocks Real Satellite Satellitesystern weight1 Satellite WeightBalance Satellite SatelliteSystem Instantiated properties Type Real SysML Profile Blocks k lt Back Figure 28 Automatic Instantiation Wizard Step 1 Select parts 4 In Step 2 create a new package named Satellitelnstance02 and click Next Copyright 2009 2
114. nd dialog To find the requirement using the Quick Find dialog 1 You can either select Edit gt Quick Find in the main menu or press Ctrl Alt F to open the Quick Find dialog 2 To search for a requirement by ID type the ID of the requirement into the combo box Type Name in the Quick Find dialog Type Mame 2 makeh Found ma 2 2 FuelEconomy H5UY Model HSUY Requirements Performance Figure 91 Finding requirement by ID using Quick Find dialog 128 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures 3 To search for a requirement by its name type before the name of the requirement in the combo box Type Name Type Mame FuelCapacity Mi 4 2 FuelCapacity H50 Model HSUY Requirements H5UY Specific Figure 92 Finding requirement by name using Quick Find dialog 5 2 5 4 Using requirement element Creating Your Own Requirement Type Subtype You can define an additional requirement type by creating a new stereotype that generalizes the requirement stereotype Requirement Subtypes The following table provides the definitions of the non normative enumerations that are used to type the properties of the requirement subtypes Enumeration Enumeration Literals RiskKind High Medium Low VerificationMet Analysis hodKind Demonstration Function To indicate an unacceptable level of risk To indicate an acceptable level of risk To indicate a minimal lev
115. nd 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 FlowPort 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 specified and the default value of the direction should be inout A FlowSpecification can be used as a type of a FlowPort only Directly specified in OMG SysML spec 9 3 2 4 9 3 2 4 Deprecat ed Deprecat ed Deprecat ed Deprecat ed 9 3 2 7 Derived from OMG SysML spec Deprecat ed Deprecat ed 9 3 2 7 Deprecat ed Validation Constraint FullPort FullPort FullPort FullPort InterfaceBlock InterfaceBlock InterfaceBlock InterfaceBlock InvocationOnNestedPort Action InvocationOnNestedPort Action InvocationOnNestedPort Action InvocationOnNestedPort Action ItemFlow ItemFlow ItemFlow ItemFlow ItemFlow ItemFlow Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 3 with permission Full ports cannot also be proxy ports This applies even if some of the stereotypes are on subset or redefined ports Binding connectors cannot link full ports to other composite properties o
116. ndow Interface Block Properties Node Column name Description Name Compartment name Type Compartment type Default Value Use to set the value manually Owner Interface Block which is the owner of the selected Proxy Port Button name Description Opens the Specification window of the compartment Up Move item to upper position in the list The items are automatically renumbered after moving Down Move item to lower position in the list The items are automatically renumbered after moving Create Opens the list with the available to create properties Click to create the Value property Flow property or Reference property Redefine Duplicates the selected item and marks its name in ascending order Delete Removes the selected item from the list Diagram Specific Procedures 5 2 2 11 Create Directed Features and Specify Feature Directions The directed feature is a Feature element that applies the DirectedFeature stereotype MagicDraw SysML plugin provides the diagram context menu to specify the feature direction of the selected feature When you set the feature direction to the selected feature it will apply the DirectedFeature stereotype automatically To specify a feature direction 1 Right click a feature s symbols owned by a block such as part attribute operation and signal reception 2 Go to Feature Direction and select one of the directions of the feature 5 2 2 12 Displaying Structures of Blocks in Compartm
117. ng 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 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 are negated Sample suction Suction Nozzle suction Fluid Flow 4 2 8 Full Port Description A Full Port is a port which is considered as a separated element of owning blocks It may have internal parts or behaviors that support interactions with owning blocks Views and Viewpoints Diagram Elements Sample Tractor efulls 3 Point Hitch Full port 4 2 9 Proxy Port Description A Proxy Port is a port that specifies features of owning blocks or internal parts that are available to external blocks through external connectors to the ports It does not specify separated elements of the owning blocks or the internal parts It can only be typed by Interface Block Sample dcPower DC Power aproxys dcOutput DE Power B Proxy port F Related procedures NEW Displaying Direction Prefixes of Proxy and Full P
118. ng elements Binding Connector Block Distributed Property and Value Type e SysML_activeValSuite Constraint Blocks e This suite contains SysML constraints on the following elements Constraint Block and Constraint Property e SysML_activeValSuite Non normative Extensions e This suite contains SysML constraints on the following elements nonStreaming Streaming Design Constraint Functional Requirement Interface Requirement and Performance Requirement e SysML_activeValSuite Port and Flows e This suite contains SysML constraints on the following elements Flow Port Flow Property Flow Specification and Item Flow e SysML_activeValSuite Requirements e 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 Validation is selected The Active Validation engine will validate in real time the model you are working on whenever the need arises for example when a project is loaded or an element of a model changed The following example a simple SysML project with three requirements and a Copy dependency illustrates how this Active Validation feature works s lt requirement gt CE _ Requirement 2 lt COpY E gt s lt requirement gt C Requirement 1 S lt cOpy gt serequirement C7 Requirement 3 Figure 7
119. ns and Values QUDV The SysML 1 4 QUDV library was improved to e comply with International vocabulary of metrology VIM 3rd edition e encode ISO IEC 80000 definitions of base quantities and units to provide semantics for computer based dimensional analysis The ISO IEC 80000 library which is a collection of 14 standards is available to use in new projects on demand from the shortcut menu select Modules gt Load Module Coverage of Normative Definitions OMG SysML 1 4 ISO 80000 ISO IEC 80000 Collection part 1 ISO 80000 1 2009 General S sML s QUYD part 2 part 3 part 4 part 5 part 6 part 7 part 9 part 10 part 13 Generic Procedures 5 1 5 Using Quick Search Dialog To open the Quick Search dialog 1 Press Ctrl Alt F to open the Quick Search dialog Type Name rd to search Class or Interface Any Classifier Any Element Diagram Tuma tewt aro owoloecor ype EALO YULA U 2 Do one of the following e Enter the name of the element or diagram sought e Select the element or diagram from the drop down list box The diagram or the corresponding element opens in the Containment tree 5 1 6 Using 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
120. nt A requirement cannot copy more than one requirement Copy dependencies should not form a cyclic graph If the supplier requirement has sub requirements 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 associated copy A nested classifier of a class that is stereotyped by requirement must also be stereotyped by requirement A Requirement ID must be unique The type of return parameter of the stereotyped model element must be VerdictKind Note this is consistent with the UML Testing Profile The activity has at least one streaming parameter The streaming and nonstreaming stereotypes 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 Directly Derived specified from inOMG OMG SysML SysML spec spec 10 3 2 2 11 3 2 3 11 3 2 4 11 3 2 5 15 3 2 3 15 3 23 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 Validation Constraint interfaceRequirement performanceRequireme nt designConstraint PropertySpecific Type non active PropertySpecific Type non active PropertySpecific Type non active PropertySpecific Type non active Constraint Description Description excerpts have been taken from the
121. nt any diagram containing the selected invalid element will then be displayed i 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 le 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 Additional validation rules constraints can be added and grouped into a validation suite either in a newly created one or in an existing one Validation For more information about the Validation feature see the Model Analysis in the Validation section in the MagicDraw User Manual pdf 7 1 1 Active Validation This feature enables you to check at once if a model is correct and complete Unlike the regular Validation feature 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 e SysML_activeValSuite Activities e This suite contains SysML constraints on the following elements Discrete and noBuffer e SysML_activeValSuite Blocks e This suite contains SysML constraints on the followi
122. nto the Search By Mame input Field Search 3 aA elements by their qualified names or use camel case when searching if the Ya a appropriate mode is enabled Search By Name Type text or wildcard 7 to search T 776 matches Found lt UNSPECIFIED gt Elf Data 776 matches E E ME Customization For SysML MD customization For SyvsMLimdzip 115 matches H E QUDY Library MD_customization _For_SysML mdzip Fo matches E E UML Standard Profile UML Standard _Profile mdzip 362 matches E fee Matrix Templates Profile Matrix Termplates _Profile mdzip 69 matches E fea SysML SvsML Profile mdzip 151 matches E System 1 match o Creation Mode Cancel Figure 101 Select Property dialog 2 Select a structural feature The Change Structural Feature event model occurrences of changes to values of the selected structural feature will be created and set as an Event element of the trigger of the created Accept Change Structural Feature Event action 136 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures E Change tructuralFeatureEvent lt gt Specification of ChangeStructuralFeatureEvent properties Specify properties of the selected ChangeStructuralFeatureE vent in the properties specification table Choose the Expert or All options From the Properties drop down list to see more properties Be Ee 2 L h ange Exent ial h en E E Documentation Hype Inner Elements Relations Ap
123. ock Definition Diagram 1 Do one of the following e From the diagram panel select Association Block On the diagram pane select a Block to be used as the source of the to be created Association Block Diagram Specific Procedures e Select the Association Block icon on the Smart Manipulator menu of a Block to be used as the source of the Association Block 2 Select a target of the Association Block by either selecting an existing Block on the diagram to be used or clicking on empty space on the diagram to create such target Block 3 An Association Block will then be created between the source and target Blocks 5 2 1 5 Creating a SysML Internal Block Diagram To create a SysML Internal Block diagram for a Block 1 Select the Block symbol The smart manipulator menu will appear a 2 Click the SysML Internal Block diagram button H The SysML Internal Block diagram will then be created and owned by the selected block 3 The SysML Internal Block diagram and the owner block will have the same name The hyperlink to the created diagram will be added to the selected block 5 2 1 6 Representing association roles as block properties When a Block is represented in the other BDD diagrams all Association roles will be represented in the Block properties compartment as normal properties This representation option for Association roles is enabled by default in all new SysML projects This option however does not apply to an
124. oints Diagram Elements 44 View 44 Viewpoint 45 Conform 45 SYSML Parametric Diagram Elements 46 Moe 46 Objective Function 46 Binding Connector 46 SYSML Requirements Diagram Elements 47 Requirement 47 Extended Requirement 47 Functional Requirement 47 Interface Requirement 48 Performance Requirement 48 Physical Requirement 48 Design Constraint 48 Business Requirement 48 Usability Requirement 48 Test Case 48 Satisfy 49 Verify 49 Derive 49 Copy 49 SYSML Activity Diagram Elements 49 Accept Change Structural Feature Event Action 49 Change Structural Feature Event 49 Invocation on Nested Port Action 50 Trigger on Nested Port 50 SYSML Use Case Diagram Elements 50 External System 50 sensor 50 Boundary System 50 User System 50 Actuator 51 Environmental Effect 51 Generic Procedures 52 Creating SysML Projects 52 Creating SysML Projects From Templates 53 model Using OMG SysML Style 54 Using QUDV Model Library 56 Using Quick Search Dialog 57 Using Structure Browser 57 Specific display options 58 Generating SysML reports 59 Context Specific Value Compartments 60 Progressive Reconfiguration 60 Deep Reconfiguration 61 Context Specific Value Compartments 62 Feature based Compartments 67 Expanding and Suppressing Feature based Compartments 68 Displaying Options in Feature based Compartments 68 NEW Managing Element Groups 69 NEW Displaying Rake icon on symbol 70 Transferring mathematical expressions from MATLAB source code into the 71
125. on ChangeStructuralFeatur eEvent ChangeStructuralFeatur eEvent Directly specified in OMG SysML spec Constraint Description Description excerpts have been taken from the OMG SysML Specifications 1 3 with permission If isEncapsulated of a block is true then the 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 Block 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 type The DistributedProperty stereotype may be applied 8 3 2 4 only to properties of classifiers stereotyped by Block or Value Type Any classifier which specializes a ValueType must also 8 3 2 10 have the ValueType stereotype applied If a value is present for the unit attribute the quantity kind attribute must be equal to the value of the quantity kind attribute of the re
126. on Action Select Operation Model El Relations H E data EFA MD Customization For SysML MD_customization_for_5 FR UML Standard Profile UML Standard Profile xml H EA SysML Profile 5ysML Profile mdzip io Assembly E E Block Figure 94 Select Operation dialog 5 2 6 2 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 Diagram Diagram Specific Procedures 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 BF Activity Diagram Action hame So Behgpior 4 sestartObjectBehavior gt CallOperation BLOCK owl OpaqueAction he Figure 95 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 it To disable Dynamic Centerlines e Click the Show Centerlines button on the activity diagram toolbar e Press C e Select Options gt Environment on the main menu The Environment Options dialog will then op
127. or Containment tree To create a Requirements Table 1 In the Containment tree or on the diagram pane select an element that can be the owner of the requirement table 2 Do one of the following e From the main menu select Diagrams gt Create Diagram Type reqT and press Enter e On the main toolbars click the Create Diagram button Type reqT and press Enter e Press CtriI N Type reqT and press Enter e Right click the element and from the shortcut menu select Create Diagram gt Requirement Diagrams gt Requirement Table The newly created requirement table opens on the right side of the application window 3 Type a table name 4 Specify a scope for table or simply drag desired requirements from the Containment tree to the table SysML Requirements Table Toolbar The SysML Requirements table toolbar is located on the main toolbar There are 13 Requirements table icons on the Requirements table toolbar Add New Add Nested Add Existing Delete From Table Delete Up Down Unnest Requirement Nest Requirement Report Show Columns Show Full Paths and Export Insert k Add New Ctrl on MAC 20 Copyright 2009 2015 No Magic Inc Requirements Table Icon Name Keyboard Shortcut Alt Insert ia Add Nested Alt on MAC Ctrl Insert Ei Add Existing Ctrl E on MAC E Delete From Table Delete Tl Delete Ctrl D i Up Ctrl Up p Down Ctrl Down din Unnest Requirement n a bi
128. orEnd stereotype is used to represent such nested ends just as for nested ends of other SysML connectors SySML Requirements Diagram Elements 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 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 language but a more formal language such as OCL or MathML could also be used Sample UnitCostEquation E amoes HSUValt1 unitcost Real 4 5 SysML Requirements Diagram Elements 4 5 1 Requirement Description 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 elements 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 inherite
129. ormance 4 maiohes i Single Selection Figure 2 Select Requirement Dialog Add existing requirements to table 2 Select the requirement element s which you want to add to the table e Use the Add button to add a requirement selected in the element tree to the Selected elements pane e Use the Add Recursively button 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 to remove the selected requirement from the Selected elements pane e Use the Remove All button to remove all requirements from the Selected elements pane 3 In the Select Requirement dialog click e OK to add all requirements in the Selected elements pane to the table or e Cancel to cancel the operation 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 Requirements Table 2 Click the Delete From Table icon on the table toolbar or press Delete 3 The selected requirement s will then be removed from the table Delete To remove a 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 3 The selected requirement s will then be removed from the table and from your project Up To move the selected row of requirement up either cli
130. orts NEW Displaying Combined Direction on Proxy Port NEW Managing Interfaces of the Proxy Port 4 2 10 Directed Feature Description A directed feature is a feature which applies the DirectedFeature stereotype It specifies that the feature is provided required or both required and provided by an owning block Sample dcPower DE Power 4 3 Views and Viewpoints Diagram Elements 4 3 1 View Description 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 Views and Viewpoints Diagram Elements Sample View Introduction Discription of table Listed items Table made from smart package 4 3 2 Viewpoint Description 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 viewpoint They specify the elements expected to be represented in the view that may be formally or informally defined A viewpoint cannot own any operation nor attribute Sample viewpoints Grouping Viewpoint Creates View 4 3 3 Conform Description A Conform relationship is a dependency between a view and a viewpoint The view conforms to the rules and conventions specified in the viewpoint SysM
131. pe dialog opens Select the check box es in front of the packages models or profiles that will be the row scope Click OK to close the Scope dialog Click the button next to the Column Scope in the matrix pane The Scope dialog will open 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 Refresh button O A O N gt 3 2 1 8 Editing Matrix You can create or remove dependencies directly in an editable matrix Double click an empty rectangle in the matrix to create a new dependency or double click an existing dependency in the matrix to remove it 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 would like to create Dependency Matrix Q aS ControlElectric Q at ProvidecElectric E E HSU Behavior Ea Acceleratef transModecmd 3 a ProvidePowerf transMo e oe el al ProportionPow Be ejk emg HSUvMode m ef peu H5UvModel Soe e 0 a ProvideGasPo Co al ProportionPower
132. plied Stereotype 2 ChangeStructuralFeatureEwent i Tags Change Expression Constraints Image Name CWINEF ma System System Qualified Mame System System Structural Feature Structural Feature Figure 102 Specification window of created change structural feature event 3 Click OK in the Select Property dialog The Accept Structural Feature Event action will be created in the selected SysML Activity diagram act Activity System System eA cceptlChangestructuralF eatureEventActions when trigger Event Element ethangestructuralF eature Events Figure 103 Created accept change structural feature event action 5 2 7 SysML Use Case Diagram Procedures The SysML Use Case diagram specific features include Numbering Use Cases Diagram Specific Procedures 5 2 7 1 Numbering Use Cases To number the use cases in a Use Case diagram 1 Select Use Case Numbering on the diagram shortcut menu 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 2 Click Yes The Change Use Cases Numbering dialog will open Ad Change Use Cases Numbering B E H5U sample Use Cases Use Cases Owners EF HSU Model F9 Behavior Operate thewehicle F Configuration lt gt Insure thewehicle F Requirements lt gt Register the
133. plier requirement master and a client requirement slave specifying that the client requirement text is a read only copy of the supplier requirement text 4 6 SysML Activity Diagram Elements 4 6 1 Accept Change Structural Feature Event Action Description An Accept Change Structural Feature Event Action is an action that waits for the occurrence of a Change Structural Feature Event 4 6 2 Change Structural Feature Event Description A Change Structural Feature Event is an event which is used to model changes in values of structural features SysML Use Case Diagram Elements 4 6 3 Invocation on Nested Port Action Description An Invocation on Nested Port Action is an invocation action that applies the InvocationOnNestedPortAction stereotype which extends the UML s onPort property to support nested ports 4 6 4 Trigger on Nested Port Description A Trigger on Nested Port is a trigger that applies the TriggerOnNestedPort stereotype extending the UML s Port property of the trigger to support nested ports 4 7 SysML Use Case Diagram Elements 4 7 1 External System Description An External System is a system that interacts with the system under development For example Information server or Monitoring system 1 4 7 2 Sensor Description A Sensor is a special external system that forwards information from the environment to the system under development For example Temperature sensor 1 4 7 3 Boundary Sys
134. queries and simple text fragments can be presented in a built in preview window or exported to PDF or HTML documents SySML Diagrams Sample Discription of table Listed items Table made from smart package Introduction eviews E Listed items gt Introduction VIE WD Table made from smart package Introduction Related elements View Viewpoint Conform 2 1 9 SysML Sequence Diagram This diagram is similar to UML Sequence Diagram 2 1 10 SysML State Machine Diagram This diagram is similar to UML State Machine Diagram 18 Copyright 2009 2015 No Magic Inc The supportive diagrams are e Requirements Table e Dependency Matrix e Predefined Relation Maps 3 1 Requirements Table All requirements are text based With Requirements Table you can easily type your requirements into a spreadsheet like table instead of the limited size boxes in a diagram This table is consistent with OMG SysML specifications The Requirements Table has been refactored to be based on the MagicDraw Generic Table component Requirements Table contains requirements Each row in the table represents a requirement A new table consists of three columns by default However you can add more columns to represent the properties of each requirement in the table Table ebelow lists the name and description of some of the columns With this table you can e Create new requirements directly in the table or import existin
135. r 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 SysML blocks can be used to define relationships between parts or other properties of the same containing block Sample ablocks AC Power constants ACElectricPowerEquation values v Y ACtunit volt i A AC unit ampere power Wiunit watt Related procedures NEW Displaying Direction Prefixes of Proxy and Full Ports NEW Managing Interfaces of the Block NEW Managing Block properties SYSML Block Definition Diagram Elements 4 1 2 Domain Description 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 Sample adoamains AutomotiveDomain Driver Passenger Maintainer drivingConditions Environment HSU HybridSi y vehicleCargo Baggage 4 1 3 External Description An External block is a block that represents an actor It facilitates a more detailed modeling of actors like ports or intern
136. r SimpleUnit length SimpleQuantityKind m s meterPerSecond DerivedUnit velocity DerivedQuantityKind meterPerSecondSquared DerivedUnit mole SimpleUnit m s acceleration DerivedQuantityKind amountOfSubstance SimpleQuantityKind amountOfSubstanceConcentration DerivedQuantityKind area DerivedQuantityKind mol m molePerCubicMeter DerivedUnit squareMeter DerivedUnit cubicMeter DerivedUnit volume DerivedQuantityKind cubicMeterPerKilogram DerivedUnit reciprocalMeter DerivedUnit m kg specificVolume DerivedQuantityKind waveNumber DerivedQuantityKind newton DerivedUnit force DerivedQuantityKind pascal DerivedUnit pressure DerivedQuantityKind radian DerivedUnit planeAngle DerivedQuantityKind second SimpleUnit time SimpleUnit siemens DerivedUnit electricConductance DerivedQuantityKind steradian DerivedUnit solidAngle DerivedQuantityKind V sievert DerivedUnit doseEquivalent DerivedQuantityKind tesla DerivedUnit magneticFluxDensity DerivedQuantityKind volt DerivedUnit electricPotentialDifference DerivedQuantityKind watt DerivedUnit power DerivedQuantityKind weber DerivedUnit magneticFlux DerivedQuantityKind Model Library for Quantities Units Dimensions and Values QUDV C celcius Temperature celcius Temperature DerivedQuantityKind AffineConversionUnit ohm DerivedUnit electricResistance DerivedQuantityKind 7 1 Validation
137. r Provided Interface only Set provided interface as port type The Select Interface dialog 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 Diagram Specific Procedures e Create dummy port type automatically The Select Interface dialog 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 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 of the port e Select or create port type manually The Select Port Type dialog will then open You can then choose a classifier to be used as the type of the port Click OK the Select Interface dialog 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 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 Ad Select Port Type Model Search By Mame F5_EPC H E FS_ICE FS_TRSM H E FuelFlow E3 FuelTankFitting I ICECmds T_ TCEData IIEP md T_ JEPCData 1 TRSMCrnd T_ TRSMDaka IFS EPC IF S_ICE IF5_TR5M H a TCEData Figure 6 20 Interfaces Typing Standardi Figure 6 21 Int
138. r Renumber Recursively buttons to number the selected requirements 4 For example if you click 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 predefined Separator Prefix Numbering Scheme Diagram Specific Procedures 5 You can click the Recursive Renumber button to renumber all requirements that are recursively contained inside the selected node The Numbering Scheme 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 existing values with the values of the selected node 6 Since there is no Numbering Scheme Prefix and Separator values defined in the HSUV Specification HSUV Requirements and HSUVModel packages the values defined in the Data package default will be used instead Numbering Style Multi Levels Prefix and Separator For more information about numbering elements see the MagicDraw User Guide pdf The Edit Create Remove Increase Decrease Renumber or Renumber Recursively buttons are used to add edit remove requirements numbers directly owned by the package or the selected requirement selected in the browser on the left hand side of the Element Numbering dialog only e SysML Plugin provide
139. r of the part go directly to step 3 Diagram Specific Procedures ibd Block Block Fa Block seblock gt partla part2a partda Block5 lt lt block gt partib Blocks lt lt bloack part3a part4da BlockS Figure 70 Flow port created on part 3 Select a port type in the Select Port Type dialog The flow port will then be created having an Inout direction 4 You can change its direction using the port shortcut menu 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 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 Item 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 Do one of the following e click the Item Property button on the IBD diagram toolbar and then select the connector or e click the Item Property icon on the connector smart manipulator menu or e drag the property which will be used as the item property to the connector 2 The Item Flow
140. ral 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 An existing 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 For more information see the Validation chapter You can select value types from the model library that holds more than 80 units and quantity kinds of SI system ValueTlypes m s oWalue Typen Unit CoCubicMeterPersSecond 4 1 11 Quantity Kind Description 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 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 SySML Internal Block Diagram Elements eQuantityKinds torque DervedQuanti name torque 4 1 12 Unit Description 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 pa
141. ree to the Selected objects pane Use the Add Recursively button in to add all elements listed under the element selected in the element tree to the Selected objects pane Use the Remove button in to remove the selected element from the Selected objects pane Use the Remove All button in to remove all selected elements from the Selected objects pane 5 After the scope of the report is defined click Next to proceed to the Output Options pane 6 Specify the report file name report file format and image file format It is recommended to use RTF as the report file format 7 Click Generate to create the report Your report will be generated and automatically open in the default document editor For more information about working with the Report Wizard see the MagicDraw ReportWizard UserGuide pdf 5 1 8 Context Specific Value Compartments Context Specific Value Compartments allows for e creating different configurations for the same structure and display them directly in IBD diagram s e having different values for the same part in different contexts e assigning a different initial value to an inherited property 5 1 8 1 Progressive Reconfiguration Progressive Reconfiguration enables SysML to handle a wide range of systems engineering configuration tasks Progressive Reconfiguration continuously applies the following values e Static class level default values e Inherited Property specific initial values e Redefined Property
142. rement satisfy Su rveillance Came ra block Surveillance Camera Specification Enter Symbol Properties Alt Enter Create Group Create Diagram Go To Figure 17 Add element to group 5 1 11 NEW Displaying Rake icon on symbol You can use rake icon for faster navigation in the model The rake icon on the symbol indicates that the appropriate element has an internal structure Double click the element to open the internal diagram The rake icon is shown by default on the symbol To hide rake icon 1 Right click the symbol 2 Select Symbol Properties from shortcut menu or press Alt Enter 3 Set the Show Rake Icon property value to false Generic Procedures ibd System Coffee Machine Thermal View Brewing Group dispersion frothy milk in water in Figure 18 Using rake icon 5 1 12 Transferring mathematical expressions from MATLAB source code into the model MATLAB source code contains a functions declaration The m file is a text file containing a list of commands written in MATLAB or Octave syntax You can define functions and scripts in the m file You can move the mathematical expressions from MATLAB source code into the model Use the m file to transfer functions to a Constraint Block Constraint Property or Call Behavior Action Creation of elements from MATLAB source code is supported in the following diagrams e SysML Internal Block definition d
143. requirements OffRoadCapability ld 2 2 Text The Hybrid SUY shall have the off road capability of atypical SW eFequirements iia ae Text The Hybrid SUY shall have dramatically better fuel economy than a typical SUW Jr Figure 5 Error message displayed on warning symbol 9 Click the warning icon to display a menu Then select either Ignore or Select in the Validation Results 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 erequirements FuelEconony Ignore A Select in Validation Results j De ae Text The Hybrid A A Tdramatically i better fuel Pi economy than a ae typical SUW mE a Figure 6 Invalid element validation options 10 The Validation Results window includes the following icons If you click the a icon Select in Containment Tree you will be redirected to the selected invalid sment in the Containment Tree icon Select Rule in the Containment Tree you will be redirected to the broken constraint of the selected invalid element in the Containment Tree icon Open all diagrams containing the selected eleme
144. rticular 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 The only valid use of a Unit instance is to be referenced by the unit property of a Value Type stereotype Sample eaUnits radianPerSecond DerwedUnit factor second 1 name radian per second primarnQuantityEind planeAngle quantityEind anqularvelocity 4 2 SysML Internal Block Diagram Elements 4 2 1 Part Property Description 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 compartment Sample clock Clock Related Procedures NEW Displaying Direction Prefixes of Flow Property SySML Internal Block Diagram Elements 4 2 2 Shared Property Description 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 4 2 3 Reference Property Description A Reference Property is a property that specifies a reference of its containing Block to
145. s 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 ype text or wildcard 7 to search fe Tree List Master Requirement SyvshL Profile Requirements Requirement RealizingElements Element 0 MO Customization For SysML customizations For traceability Properti RealizingRequirements Class 0 MD Customization for SwsML customizations For traceability Prope RefinedBy NamedElement 5SysML Profile Requir ments Requirenent RefinedByRequirements Class 0 MD Customization for SysML customizations for traceability Propl RefineRequirements Class 0 MO Customization For SysML customizations For traceability Properti ReqDerive Class 0 MD Customization For SysML customizations For traceability Properties descrip ReqDerivedFrom Class 0 MD Customization For SysML customizations For traceability Properties c RegRefineBy Class 0 MO Customization for SysML customizations For traceability Properties desc RegRefines Class 0 MD Customization for SysML customizations For traceability Properties descri RegqTracedFrom Class 0 MB Customization For SyvsMLi customizations For traceability Properties de RegqTracedTo Class 0 MD Customization for SwsML customizations For traceability
146. s two numbering styles to number requirement IDs Consecutive previously called normal style and Multi Levels previously called nested style e Using the Consecutive numbering style each requirement ID is numbered with a prefix followed by numbers without any separator e 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 You can use a Character or a symbol excluding number as a Separator Numbering Scheme Prefix and Separator can be defined at a package ora 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 Scheme 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 Scheme Prefix and Separator values defined for your project Numbering Scheme Multi Level Prefix and Separator Automatic Numbering Once this functionality is turned on the IDs of the newly created requirements will be numb
147. sML Block definition diagram Related elements Block Domain External System Subsystem system Context Constraint Block Interface Block Flow Specification Value Type Quantity Kind Unit Related procedures SYSML Block Definition Diagram Procedures Transferring mathematical expressions from MATLAB source code into the model 2 1 2 SysML Internal Block Diagram IBD Description Internal Block Diagrams are based on UML composite structure diagrams and include restrictions and extensions 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 references to other blocks can be specified However whereas an Internal Block Diagram created for a Block as an inner element 10 Copyright 2009 2015 No Magic Inc SySML Diagrams 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 allows any property part to be shown in an Internal Block Diagram to display compartments within the property or part symbol Sample ibd Block
148. ss Real Boolean festatress maxstress Real J Boolean Figure 14 Compartments in block vs Feature based compartments in internal property Generic Procedures 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 constraints UML properties and operations compartments 5 1 9 1 Expanding and Suppressing Feature based Compartments You can expand or suppress feature based compartments using either the Symbols Properties dialog or the property shortcut menu Using the Symbol Properties Dialog of an Internal Property To expand or suppress a feature based compartments using the Symbol Properties dialog 1 Either right click the property symbol and select Symbol s Properties or select the property and press Alt Enter The Properties dialog opens 2 In the SysML Internal Properties Compartments property group do one of the following e Set the value of the corresponding symbol property to false by clearing the check box e Set the value of the corresponding symbol property to true by selecting the check box L Pro perties Park lt lt PartProperty gt gt Suppress properties False Suppress references False Suppress parts False Suppress values False Suppress constraints False Suppress operations False Make Default Figure 15 Symbol Properties dialog S
149. stem Engineer Perspective The SysML plugin is available in MagicDraw Standard and higher editions for an additional fee 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 You can switch among perspectives at any time To switch to the System Engineer perspective 1 On the main menu click Options gt Perspectives gt Perspectives 2 In the Select Perspectives dialog select System Engineer 3 Click the Apply button System Engineer Perspective Choosing perspective will switch the application to the graphical user interface designed for a specific role business system analyst architect etc Select predefined MagicDraw configuration according listed Perspectives Perspective provides features primarily dedicated for eliciting requirements and modeling the system Analysis features are highlighted Configuration is modeling oriented Code engineering transformations and other features are hidden System Analyst Expert 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 You may integrate MagicDraw with Integrated Development
150. t be contained in the block that types the port at an immediately preceding position The value of the port property of a stereotyped trigger must be contained in the type of the port at the last position of the onNestedPort list A ConstraintBlock cannot own any structural or behavioral elements 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 Any classifier which specializes a ConstraintBlock must also have the ConstraintBlock stereotype applied Binding connectors are used to bind each parameter of the constraint block to a property in the surrounding context This constraint parameter has not been used in a constraint expression of its constraint block This constraint is not explicitly specified in OMG SySML spec however the unused constraint parameter can imply that there is a high probability of the presence of an excess constraint parameter or an incorrectly named constraint parameter Directly specified in OMG SysML spec 9 3 2 12 9 3 2 12 9 3 2 12 9 3 2 13 9 3 2 13 9 3 2 13 9 3 2 13 9 3 2 13 10 3 2 1 10 3 2 1 Derived from OMG SysML spec 10 3 2 1 Validation Constraint ConstraintProperty
151. t Property Flow Property For more information on SysML properties see the SysML Block Definition Diagram BDD section You can also use the Block shortcut menu to create a new UML property or UML operation For more information see MagicDraw UserManual pdf The Block smart manipulator menu will not be displayed after you have created a new stereotype as a subtype of a Block unless you save and restart your project first bdd Model Data Untitled ja E A e A stereotypes Block Class isEncapsulated Boolean 0 1 A stereotypes CustomBlock Class O Diagram Specific Procedures 5 2 1 2 Inserting a new SysML diagram To create a SysML diagram with a Block as its owner e From the selected Block shortcut menu select New Diagram and then select a diagram you want to create 5 2 1 3 Using SysML Style compartments SysML Specifications allow Blocks to have multiple compartments SysML plugin provides five independent compatible block compartments e parts references e values constraints property s compartments blocks AutomotiveDomain fart ants drivinglonditions Environment HSU gt Aybridsu y vehicleClargo Baggage Aim fetes driver Driver maintainer Maintainer passenger Passenger blocks FuelTankAssembly parts fp FuelPurmp fuelReturn Fuelidirection out fuelSupply FueltreadOnly direction int Wales TuelFlow Fa
152. te Feal fuelVeight Real eblocks PowerSubsystem Corse inits tuelF low FuelF lios parts acl Accelerator bp BatteryPack bus CAR Bus dif Differential em ElectricMotorGenerator allocatedFrom a4 epc ElectricalPoyrerControllerjallocatedFram a3 ft FuelTank Assembly fuelSupply Fuel gi Torque i1 ElectricCurrent i2 gt Electric urrent ice InternalCambustionEnginejallocatedFram a2 ecu PowrerControallnittallacatedFrom al ti Torque t2 Torque trm Transmission EemmesS bkp BrakePedal 1 ftuelReturn Fuel fve Fronteyvheet 1 ri gt Fronteyneet 1 wheelHubsAssy YvheelHubAssembly 2 FT Figure 22 SysML block compartments SysML Displayed Elements Compartments parts Part Properties properties which are typed by Blocks or subtypes of Block except Constraint Block having composite aggregation kind Any Part property automatically becomes a reference property if aggregation kind is set to shared or none Diagram Specific Procedures SysML Compartments references values constraints flow properties properties Displayed Elements Shared Properties and Reference Properties are the properties typed by Blocks or subtypes of Block except Constraint Block having shared and none aggregation kind respectively There is no distinction between Shared Property and Reference Property Value Properties properties which are typed by Valu
153. tem Description 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 4 7 4 User System Description 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 SysML Use Case Diagram Elements 4 7 5 Actuator Description 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 4 7 6 Environmental Effect Description An Environmental Effect is an influence on the system from the environment without communicating with it directly For example Temperature or Humidity 1 1 USING SYSML PLUGIN You can find out the useful information about working with SysML plugin while studying e Generic Procedures e Diagram Specific Procedures 5 1 Generic Procedures Depending on whether you want to e Creating SysML Projects e Creating SysML Projects From Templates e Using OMG SysML Style e Using QUDV Model Library e Using Quick Search Dialog e Using Structure Browser e Generating SysML reports e Context Specific Value Compartments e Feature based Compartments e NEW Managing Element Groups e NEW Disp
154. ters to be shown on the constraint property symbol The selected constraint parameters will be displayed as small square boxes Diagram Specific Procedures p Select Parameters Select Parameters P parameteri Constraint Block P parameter Constraint Block P parameter Constraint Block Unselect All Figure 77 Select Parameters dialog zaconatraint l Constraint Block parameters parameters parameter Figure 78 Constraint property with its constraint parameters 5 2 4 2 Creating automatic constraint parameters When you drag a binding connector from a property to a constraint property MagicDraw SysML automatically shows a list of hidden constraint parameters in the constraint property and suggest new names for a constraint parameters that you might want to create If the constraint parameter you want to connect does not exist you can create it on the spot The suggested parameter names come from the names of the properties on the other end of the binding connector you are trying to connect and the extracted variable names come from the constraint expressions defined in a constraint block that types the constraint property To create new constraint parameters from the context menu of a constraint block 1 Right click a constraint block for example Sum and select Tools gt Create Parameters 2 Create a constraint parameter in this example z which is the variable in an expression that has not been
155. th warnings errors or fatal severities will be included e gt error Constraints with error or fatal severities will be included To open the Active Validation Options dialog Fatal Only constraints with fatal severities will be included 1 Click Analyze gt Validation gt Active Validation Options The Project Options dialog opens 2 Go to the General project options pane and select Active Validation gt Ignored validation suites Validation To ignore some unused or unimportant active validation suites 1 Click the Browse L button The Select Suites dialog opens X Select Suites Ea Orphaned Proxies UML Standard Profile Validation Profile CG Parameters Synchronization UML Standard Profile validation Profile Eo Shape Ownership UML Standard Profile Validation Profile Eo SysML_activeValSuite Activities MD Customization for SysMLi SysML constraints 5 me 3SML_activevalSuite Blocks MD Customization for SysMblirsysML constraints Sys Fo SysML_activeValSuite Constraint Blocks MD Customization For SysMLi SysML const F SysML_activevalSuite Mon normative Extensions MO Customization For SysML 5ys B SysML_activevalSuite Ports and Flows MD Customization For SysML SysML constra Eg S sML_activevalSuite Requirements MO Customization for SysML SysML constrain Apply Clear All Figure 12 Select Suites dialog 2 Select the check boxes in order to ignore the active valid
156. that type the parent property node In the following figure the node diameter m represents the property diameter m of the classifier Cylinder Liner and also the property cylinderLiner Cylinder Liner is the property of the classifier Engine E E Data i E Battery E Brake System i E Cam Shaft EG car l CE engine Engine C cylinderLiner Cylinder Liner diameter r cylinderHead Cylinder Head t intakeValves Intake Valve 8 texhaustValves Exhaust Valve pistons Piston 4 starterMotor Starter Motor injectionNozzles Injection Mozzl t distributor Distributor sparkPlugs Spark Plug 4 camShaft Cam Shaft i Figure 4 Structure browser To open the Structure browser e From the main menu select Window gt Structure Generic Procedures 5 1 6 1 Specific display options There are two specific display options e Display as Plain List e Show Inherited Structure 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 without consideration of their owner When you select the Display in Plain List option the classifiers will be sorted by their name mos a Y za HSU Model of Explanations H E HSU Analysis H E HSUY Behavior i E9 HSUY Requirements J E HSU Structure zi C9 HSU Int
157. the main menu or press Ctrl F to open the Find dialog 2 To search for a requirement by 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 Diagram Specific Procedures E Search Results Search element by tag value E E From loaded diagrams 2 Name E E From model 1 3 value TR 4 1 CargoCapacity A1 Type Ci 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 89 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 the button next to the Type text field and select Requirement Finally click the Find button 127 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures Find 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 90 Finding requirement by name using Fi
158. ton in the Generate Report dialog Click the Next button in the Report Wizard twice to proceed to the Select Element Scope pane You can then change the report scope using this pane 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 Appendix IIl Open API for more information on report generation Requirements Table N 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 Display empty value as Publish to server Empty text Custom text none v Display in viewer after generating report Figure 3 Generate Report dialog SysML Requirements Table Show Columns To show or hide columns in the table click the Show Columns icon on the table toolbar The Table Column drop down menu will then display Select a column name to display that column on the table or deselect a column name to hide it To customize displayed columns select Customize Column The Select Custom Requirement Columns dialog will then display 25 Copyright 2009 2015 No Magic Inc Requirements Table N select Custom Requirement Columns Select search for or create elements Search for an element by using list or tree view
159. unding context of that constraint block Binding connectors are the only connectors allowed to bind constraint parameters to the properties of other blocks Diagram Specific Procedures To create a binding connector 1 Click either the Binding Connector button on the Parametric diagram toolbar or the Binding Connector icon on the smart manipulator of a constraint parameter or a part property 2 If you have clicked the Binding Connector button on the toolbar select a part as the connector s origin but if you clicked 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 2 5 Requirements Diagram Procedures The Requirement Diagram procedures are as follows e Changing requirement type e Creating Requirements Diagram for sub requirements e Numbering requirement IDs e Using requirement element For more information about creating importing and analyzing requirements see CameoRequirementsModelingPlugin UserGuide pdf 5 2 5 1 Changing 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 2 Select More Specific More General or Other The requirement type options will be displayed 3 Select
160. ursively Remove Figure 26 Changing slot value of fuelReturn property 80 Copyright 2009 2015 No Magic Inc Diagram Specific Procedures fi WSU Ine Tee ii HSLinternalCombustionEngine fil HSL internalCombustionEngine filial HSU internalCombustionEngine ti 4 fi HSU internalCombustionEngine t1 fi HSLinternalCombustionEngine te fis HSLinternalCombustionEngine ts fi4 HSU internalCombustionEngine t4 fra HSU internalCombustionEngine tra TuelSupply HSL internalCombustionEngine tuelSupply iceEfficiency 2 lt block gt zeblock zahlock HSU HSU g HSU internalCombustionEng internalCombustionEn internalCom ine fuelReturn Fuel nine fuelSupply Fuel bustionEngi ne tit fuelPressure fuelPressure Fuellnjector pressure unit psi pressure unit psi dimension Pressure dimension Pressure fuelDemand temperature unit F temperature Yunit F dimension Temperature dimension Temperature saoe g SuperFuel Fuel ftuelPressure 30 lt lt block gt lt lt block gt zablock lt lt block gt HSU HSU HSU HSU internalCom internalCom internalCom internalCom bustionEngi bustionEngi bustionEngi bustionEngi nefi ne fis ne fid ne tifi Fuelinjector Fuelinjector Fuelinjector Fuelinjector fuelDemand TuelDemand TuelDemand fTelDemand s lt block gt eeblock gt eeblock gt lt lt block gt HSU HSU HSU a
161. vert to Nested Parts The part will be converted to a set of Nested Parts Figure 65 Nested parts after conversion 5 2 2 14 Extracting structure Extract Structure is the first advanced automated refactoring method in our 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 to this the Extract Structure feature can also play a move or a 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 complex 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 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 Diagram Specific Procedures TRSMCmd I ctrl t2 Torque TRSMData torqueln Torque qi Torque torquet Torque spline ice InternalCombustionEngine ICECmds crtl l ICEData
162. videPower af al a af ecactiv ity gt zagt ti ity gt zage tity zagt th ity gt ControlEle ctr icPo wer ProvideGasPower ProporntionPower Provide HectricPower Mei scactivity gt scactivity gt sagt thy ity ssacti ity gt Monitor Traction Turn Key To On Driving Behavior Figure 97 Class diagram of the decomposed activities Swimlane Allocations Actions and subactivities can be organized into swimlanes in the activity diagrams The swimlanes are used to organize responsibility for actions and subactivities according to the class They often correspond to the organizational units in a business model The swimlanes limit and provide a view on the behaviors invoked in the activities They consist of one or more partitions They can be vertical and horizontal Diagram Specific Procedures An activity diagram can be divided visually into swimlanes each separated from the neighboring swimlanes by vertical or horizontal solid lines on both sides Each swimlane represents a responsibility for part of the overall activity and may eventually be implemented by one or more objects The relative ordering of the swimlanes has no semantic significance but can indicate some affinity Each action is assigned to one swimlane Transitions can cross lanes There is no significance to the routing of a transition path You can specify swimlane properties in the swimlane Specification window In the same window you can find the descr
163. y existing projects you may already have ents engine Engine Figure 24 Association Role is represented as normal property 5 2 1 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 use the Automatic Instantiation feature To automatically instantiate a Block 1 Right click a Block and select Tools gt Create Instance on the shortcut menu The Automatic Instantiation Wizard opens 2 Follow the steps of the wizard 3 Click Finish to create the instance specifications and diagram The Instance specifications will be created and displayed in the chosen diagram Diagram Specific Procedures i JAUME Cee eee fii HSLinternalCombustionEngine fi 2 HSJ internalCombustionEngine filial HSU internalCombustionEngine ti 4 fi HSWinternalCombustionEngine t1 fi HSLinternalCombustionEngine te fis HSWinternalCombustionEngine t3 fi4 HS
164. 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 e y 1 ez 2 For more information about Value Propagation see http training nomagic com To enable the value propagation mechanism 1 Click Options gt Project on the main menu to open the Project Options dialog 2 Select General project options gt SysML 3 Select the Propagate SysML Values check box and click OK Clear the Propagate SysML Values check box to disable the Value Propagation mechanism 5 1 9 Feature based Compartments SysML Plugin feature based compartments allow you to display additional compartments in internal properties There are six feature based compartments e values e parts e references e constraints e properties formerly UML properties e operations e flow properties For any given property these compartments will show information from the classifier of the property in conformity with SysML specifications outlined in the Compartment on Internal Properties section lt block gt box BallBox qoperties stress StressType s lt block YEEESSS lita cubes Cube 0 pmperties cylinders Cylinder 0 stress Stress Type PSE TIes Tarts cubes Cube 0 cylinders Cylinder 0 balls Ball 0 volEg volEg VolumeEquation Een testStrese maxStre
165. ySML Plugin uses the DSL numbering engine which is generic highly flexible and customizable The requirements numbering mechanism in SysML is the same as that in MagicDraw Consequently the Requirement ID Numbering menu has been changed to Element Numbering and the Requirement ID Numbering dialog has been replaced with the Element Numbering dialog To edit the requirements numbering settings 1 On the main menu click Options gt Project The Project Options dialog will open 2 Select General project options from the list on the left hand side You will see the Numbering options opens on the right hand side 3 You can select the Use Element Auto numbering check box if you want SysML to number requirements automatically and then select the Display Element Number check box if you want requirement numbers appear before the requirements in the Containment tree 4 Click OK Manual Numbering To number a requirement or edit a requirement s number using the Element Numbering dialog 1 Right click a requirement in the Containment tree and select Element Numbering The Element Numbering dialog will open 2 Select for example the HSUV Requirements 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 dialog 3 In the Requirements pane select the requirement s Use the Edit Create Remove Increase Decrease Renumber o
166. ysML internal properties compartments 5 1 9 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 Properties dialog of each property Generic Procedures To customize the display of the elements in the feature based compartments e Select or clear any of the check boxes as shown in the following figure Ag Properties x Part lt lt PartProperty gt gt SysML Internal Block Diagram m O Sf g Show Attribute visibility False Show Attribute Type true Show Attribute Stereotype Show Attribute Properties Show Attribute Constraints Show Attribute Default value Show Operation Signature Show Operation Visibility Show Operation Stereotype Show Operation Properties Show Operation Constraints False true False true true False true true False Show Operation Parameters Direction Kind False Show Attribute Type Show attribute type in internal properties compartments Apply Style CreFault w Make Default Figure 16 Symbol Properties dialog SysML internal attributes and operations 5 1 10 NEW Managing Element Groups You can create and manage element groups add or remove group elements faster and more easily Generic Procedures k h J i3 oy dy F requi

SysML Plugin User Guide

Contents

Download Pdf Manuals

Related Search

Related Contents