Genesys Test Drive

GENESYS Test Drive Explore and Discover Basic Features (with Instruction)

GENESYS Window Overview Estimated Time to Complete: 1 minute

2

GENESYS Window

Top Ribbons for context-sensitive commands and controls

Ribbons

Project Explorer panel for navigation of the project by packages or by classes, access to other project tools Browser panel for display of entities in the selected class folder Property Sheet panel for display of information of a selected entity: • Attributes, Properties, Parameters, Diagnostics, View Properties • Relationships • Views

Project Explorer Browser

Property Sheet

Relationships

Views

3

Test Drive Menu

Each participant will have a 15-minute time slot. Select from the following topics for the test drive:

• Requirements | 5 mins | Page 5 • Use Cases | 5 mins | Page 15 • Components | 10 mins | Page 19 • Functions | 15 mins | Page 27 • Report Generation | 5 mins | Page 42

If you have questions regarding the included instruction please contact a Vitech engineer at any time

4

Working with Requirements Estimated Time to Complete: 5 minutes

5

Viewing Requirements in Browser Panel

Requirement entities can be viewed in the Browser panel 1. Select Requirement class folder in Project Explorer a) View Requirement entities in Browser b) Notice that Property Sheet is blank when no entity is selected in Browser 2. Select “0 Smartphone Market Requirement” in Browser a) View the Requirement text in Description b) View refined by Requirement entities in Targets & Attributes 3. Select other Requirement entities in Browser to view their descriptions and relationships Notice that the displayed Relationships and Relationship Targets change as different Requirement entities are selected in Browser

6

Viewing Requirements in Requirement Diagram

Requirement entities can be viewed in a Requirements Diagram 1. Select “0 Smartphone Market Requirement” in Browser 2. Select Requirements diagram on the “Views” ribbon. A new window will appear. 3. If the diagram viewing area is too small, expand the available space by dragging the Toolbox Panel’s left side to the right

Scale and navigation controls

7

Viewing Requirements in Requirement Diagram (Cont.)

Requirement refinement is shown here in three levels. Notice the square dot in the upper-left corner of the 3 rd -level nodes, indicating additional level of relationship(s) to be traversed. Ctrl + double click on “Requirement Electronic Shutter Speed Control” to expand to the next relationship, i.e. <>

8

Custom View with Rule Set

The look and feel of a diagram can be customized to fit specific needs and specific audiences. One way is through Rule Sets. Color-code this Requirement diagram to identify requirement types easily. 1. Click on the background of the diagram to un-select any current node 2. In Toolbox, select “Properties” tab 3. Expand the dropdown list for “Rule Set” 4. Select Requirement Color Coding The node color is automatically changed: • “nil” type as rose • “Composite” type as gray • “Functional” type as light turquoise

• “Constraint” type as light green • “Performance” type as turquoise

9

Requirements Import with Excel Connector

Requirement entities can be imported from the Excel Connector 1. Bring up the accompanying Excel window to view the requirements for import. Note the Parent Requirement they are to be linked to. 2. Confirm on the GENESYS ribbon : a) The Excel Connector is logged in (the “Login” option is grayed out) b) The Project field is set to “SAMPLE: Smartphone” 3. Select Publish Changes 4. Click OK when prompted to confirm Define Table Definition update

10

Requirements Import with Excel Connector (Cont.)

The GENESYS Table Definition will appear. This is where we will define the necessary linkages between the Excel sheet and the GENESYS database for import. 1. Expand the dropdown list for GENESYS Table Definition 2. Select Requirements and view the populated table definition Each row of the table definition defines a corresponding column in the Excel spreadsheet. The Position field indicates which Excel column is being defined. 3. Select Load 4. Click OK

11

Requirements Import with Excel Connector (Cont.)

Existing requirements in the GENESYS database are also loaded into the Excel Connector to ensure synchronization between the two tools Bring up the GENESYS window to confirm the successful import of the two new requirements

12

Viewing Import Result

13

Viewing Import Result (Cont.)

Bring up the previously opened Requirement diagram to view the imported requirements. Notice the refined by relationship was also created with the import.

14

Working with Use Cases Estimated Time to Complete: 5 minutes

15

Viewing Use Cases in Use Case Diagram

Use Case entities can be viewed in a Use Case diagram 1. Select UseCase class folder in Project Explorer 2. Select “0 Use Smartphone” in Browser 3. Select Use Case diagram on the “Views” ribbon. A new window will appear displaying a Use Case diagram. 4. View the existing actors and use cases

16

Building Use Cases New actors and use cases can be created on the diagram using the Toolbox 1. Drag New Use Case from Toolbox onto the diagram. Enter “Purchase Apps” for the new UseCase entity. 2. Select “Purchase Apps” on diagram, Cltr + drag onto “Set up Phone”. A relationship menu will pop up. Select kind of . 3. Drag New Actor from Toolbox onto the diagram. Enter “Apps Store” for the new Component entity. 4. Select “Apps Store” on diagram, Ctrl + drag onto “Purchase App”. A relationship menu will pop up. Select participates in .

17

Building Use Cases (Optional)

1. If time permits create additional use cases: • Make a Phone Call • Shop Online • Stream Online Video • Connect on Social Media • Read the News 2. Create additional actors: • Wireless Service Provider • Online Store • Social Media Company • News Channel 3. Connect use cases and actors with relationship: Actor participates in Use Case

18

Working with Components Estimated Time to Complete: 8 - 10 minutes

19

Viewing Components in Block Definition Diagram

Component entities can be viewed in a Block Definition Diagram (BDD) 1. Select Component class folder in Project Explorer 2. Select “SYS Smartphone” in Browser 3. Select BDD on the “Views” ribbon. A new window will appear displaying a Block Definition diagram. 4. View the existing components decomposing the Smartphone system

20

Block Definition Diagram

21

Viewing Components in Internal Block Diagram

Component , Link , and Item entities can be viewed in an Internal Block Diagram (IBD) 1. Select Component class folder in Project Explorer 2. Select “SYS Smartphone” in Browser 3. Select Flow Internal Block on the “Views” ribbon. A new window will appear displaying an IBD. 4. View the existing components, connecting links, and transferred items. Notice some components are not linked because the Link entities between them have not been created.

22

Flow Internal Block Diagram

23

Custom View with Rule Set

The look and feel of a diagram can be customized to fit specific needs and specific audiences. One of the ways is through Rule Sets. 1. In Toolbox, select “Properties” tab 2. Expand the dropdown list for “Rule Set” 3. Select Block – Architoon Elide Ports

24

Adding Components in Block Definition Diagram

Component entities can be added into the physical hierarchy in a BDD 1. Bring up the previously opened BDD of the “SYS Smartphone” 2. Drag and drop New Part from the Toolbox onto node “Smartphone”. Enter “Antenna” for the new Component entity. Click OK . 3. Repeat the steps for “GPS Chipset” 4. Scroll to the right of the BDD to view the two new components If time permits, also create components: • “Microphone” • “Speakers”

25

Adding Components in Block Definition Diagram (Cont.)

An attribute of an entity can be edited in its Property Sheet. However, batch operations are possible for same-attribute of multiple same-class entities. 1. Select “Antenna”, “GPS Chipset”, “Microphone”, and “Speakers” (mouse area-select or shift + click select) 2. Right click to bring up the context menu. Select Set Attribute . 3. A new window will appear: Multi-Entity Attribute Editor a) Select Type for the “Attribute” dropdown list b) Select Part for the “Value” dropdown list c) Click OK “nil” type in the Component node will change to “Part” 4. Bring up the GENESYS Project window. The newly created Component entities can also be seen in the Browser.

26

Working with Functions Estimated Time to Complete: 15 minutes

27

Viewing Functions in Enhanced Functional Flow Block Diagram

Function entities can be viewed in an Enhanced Functional Flow Block Diagram (EFFBD) 1. Select Function class folder in Project Explorer 2. Select “0 Operate Camera” in Browser 3. Select EFFBD on the “Views” ribbon. A new window will appear. 4. View the existing functions, inputs and outputs in the behavior structure

28

Enhanced Functional Flow Block Diagram

29

Building a Behavior in EFFBD

Function entities can be created in the Structure contained in the EFFBD 1. Drag and drop New Entity from the Toolbox onto the line between the AND node and the LP node. 2. Enter “Make Sensor Ready” for the new Function entity. Click OK . 3. If the new Function node is too narrow, expand it by dragging its side to the right to make the whole name visible

30

Building a Behavior in EFFBD (Cont.)

Exit Condition for Function can be created in the Structure contained in the EFFBD 1. Drag and drop Exit Condition from the Toolbox onto “Make Sensor Ready” 2. A new window will appear to set the Exit Condition for “Make Sensor Ready”. a) Select New . b) Enter “Capture” for the new exit. c) Click OK . 3. Repeat steps in 2 to create another exit: “No Capture” 4. Click Close on window once both exits have been created

31

Building a Behavior in EFFBD (Cont.)

Loop Exit for a Loop construct is an essential concept of a behavior structure Drag and drop Loop Exit from the Toolbox onto the “Capture” exit branch Understanding the created functional flow: • After “Make Sensor Ready” has executed, there are two possible paths for the behavior to continue • If the “No Capture” condition is true, the functional flow takes the “No Capture” path to loop back through the “LP” node • If the “Capture” condition is true, the functional flow takes the “Capture” path to exit the loop through the “LE” node

32

Building a Behavior in EFFBD (Cont.)

Item entities act as inputs and outputs for Function entities in the behavior structure 1. Repeat steps on page 30 to create a new function “Capture Image” just outside of the Loop construct 2. Drag and drop New Input from the Toolbox onto “Capture Image”. Enter “Blur Effect” for the new Item . Click OK . 3. Repeat step 2 to create another input: “Exposure Time”

33

Building a Behavior in EFFBD (Cont.)

Item acting as an input to a Function must also be an output from a different Function 1. Select “Blur Effect”. Ctrl + drag and drop onto “Measure Time of Flight”. A relationship menu will pop up. Select output from . 2. Repeat step for: “Exposure Time” is an output from “Set Electronic Shutter Speed”

34

Building a Behavior in EFFBD (Cont.)

35

Building a Behavior in EFFBD (Cont.)

Adding an output for “Capture Image” 1. Drag and drop New Output from the Toolbox onto “Capture Image”. 2. Enter “Captured Image” for the new Item . Click OK .

36

Building a Behavior in EFFBD (Cont.)

Completing the set of inputs for “Capture Image” 1. Select Item “Captured Live Images” 2. Ctrl + drag and drop onto “Capture Image”. A relationship menu will pop up. Select input to .

37

Building a Behavior in EFFBD (Cont.)

38

Building a Behavior in EFFBD (Cont.)

A Function is allocated to a physical Component 1. In the Toolbox, select “Displays Key Entities” tab under “Insert” 2. Select “Component” folder in the Classes panel 3. Scroll down to see “SYS Smartphone” in the Entities panel 4. Shift + click to select both “Make Sensor Ready” and “Capture Image” functions in the diagram 5. Ctrl + drag and drop the functions onto “SYS Smartphone” in the Toolbox (that is visible after steps 1 -> 3). A relationship menu will pop up. Select allocated to .

39

Viewing the Complete Behavior in EFFBD

40

Viewing a Behavior in Activity Diagram

When a behavior is created/edited in an EFFBD, it is also created/edited in the GENESYS database. Because views are automatically generated from the database, such changes are also automatically reflected in other relevant diagrams. Open an Activity diagram to view what was created in the EFFBD 1. Bring up the Project window. Make sure “0 Operate Camera” is still selected in Browser. 2. Select Activity on the “Views” ribbon. A new window will appear displaying the Activity diagram. (Optional) Make changes in one diagram and go to the other diagram to observe the instant effect.

41

Generating Reports Estimated Time to Complete: 5 minutes

42

System Description Document Report

Many documentation templates are available to report on the system design. One of the more common reports is the System Description Document (SDD). 1. Click the triangle in front of “Reports” at the bottom of Project Explorer to expand the Reports folder 2. Select “SDD” to see the available reports in this folder 3. Select “SDD Report (by Project)” in Browser 4. Right-click and select Preview from the context menu 5. Once the preview generator has finished scroll through the report to view the document content

43

System Description Document Report (Cont.)

The actual SDD can be exported in several formats (PDF, HTML, RTF, etc.) 1. Click the triangle on “Export To” on the top ribbon. View the available formats. 2. (Optional) Export to PDF: a) Select PDF File > navigate to Desktop > Save b) Go to the Desktop to open the saved PDF export 3. Select Close to return to GENESYS Project window

44