Lab 8: Streams & Components

Transcription

1 Lab 8: Streams & Components Objectives After completing this lab, you will be able to: Create a new stream Create components in the stream Restrict Access to those components to specific teams, individuals or groups Split a Rhapsody model across several components allowing fine grained access control Scenario In this Lab, you will create a new Stream for working on the Advanced Driver Assistance Systems (ADAS) for a vehicle. You will create several Components and restrict visibility to them to separate the work: ADAS System a component which will hold the high-level systems model accessible only to the Systems Team. ADAS Interfaces a component which will hold Interfaces. Elements in this component will be visible to all Feature teams. The Systems Team will use editable units to edit these interfaces directly from the Systems model in the ADAS System component. ACC Feature a component owned by the ACC Feature team this team will use the Interfaces defined in the shared ADAS Interface component. To restrict visibility, you will explore two options. For the ADAS System and ACC Feature you will define new teams that own those components and restrict access to them to just their owners. For the shared ADAS Interfaces component you will define an Access Control Group that will allow access to both the System and Feature teams. It is assumed you are still working in Pete s workspace from the previous lab. Task 1: Create a New Stream and Components In this task, you will create a new Stream called ADAS Features (ADAS = Advanced Driver Assistance Systems). You will create three new components in that Stream: ACC System which will hold the high-level systems model (and will be accessible only to the systems team), ACC Feature which will hold the Functional/Architectural model of the Adaptive Cruise Control System (and will only be accessible to that team) and ACC Interfaces a shared component which will hold the Interfaces between different ADAS features. It is assumed you are still logged into Pete s workspace from the previous lab. 1. Create a Stream: a. Select the Team Artifacts tab: Copyright IBM Corp

2 Rhapsody Model Manager Tech Jam b. Expand the Sample Models project area c. Right-click the Source Control section and select New Stream: d. The Stream Editor loads e. In the Name field, type ADAS Features: f. At the top, right-hand corner of the editor, click Save 2. Create New Components: a. In the Components section, click New: b. In the Enter name for new component field, type ADAS System 1-2 Copyright IBM Corp. 2018

3 Lab 7 Streams and Components c. Click OK d. Repeat the process this time naming the new component ADAS Interfaces e. Repeat the process again this time naming the new component ACC Feature f. At the top, right-hand corner of the editor, click Save 3. Create a Repository Workspace for the Stream: a. In the Team Area browser, expand the Source Control All Streams section b. Right-click the ADAS Features stream and select New Repository Workspace: c. Add Pete to the end of the existing name: Copyright IBM Corp

4 Rhapsody Model Manager Tech Jam d. Click Next e. Select Use current repository f. Click Next g. Select Project Area: h. Click Next i. Note that all three new components are already selected: j. Click Finish k. Select Browse the components to select the folders to be loaded: 1-4 Copyright IBM Corp. 2018

5 Lab 7 Streams and Components l. Click Next m. Select all three components: n. Expand the Advanced Options section o. Select Load component files into sandbox subfolder p. Select Load the selected folders but do not create Eclipse projects: q. Click Finish r. Click OK: Copyright IBM Corp

6 Rhapsody Model Manager Tech Jam 4. Confirm Folder Creation: a. Open Windows Explorer b. Navigate to C:\Workspaces\pete c. Confirm that there is a new folder for the stream and inside it one for each component: Task 2: Restrict Visibility to Components Using Teams There are many ways to restrict visibility in this example you will create two team areas a Systems Team and an ACC Feature Team and then you will assign ownership of components to those teams. The Systems Team will have access to the ADAS System and ADAS Interfaces components. The ACC Feature Team will have access to the ACC Feature component and the ADAS Interfaces component. To achieve this, you will use two different mechanisms: for the ACC System and ACC Feature components you will restrict access to only their owners. For the shared ACC Interfaces component, you will create an Access Group. Access Groups can only be created in the web client. 1. Open the Team Areas View: a. In RTC right-click the SampleModels (RMM) project in the browser and select Show in Team Organization: 1-6 Copyright IBM Corp. 2018

7 Lab 7 Streams and Components 2. Create a Systems Team a. In the Team Organization view, right-click the Sample Models (RMM) project and select New Team Area b. In the Name field, type Systems Team c. Click Finish d. In the Team Area editor click Add in the Members section: Copyright IBM Corp

8 Rhapsody Model Manager Tech Jam e. In the Enter username field, type pete and click Search f. Click Select g. Click Next h. Select all available process roles and click Add i. Click Finish j. At the top of the editor window, click Save 3. Create a Feature Team: a. In the Team Organization view, right-click the Sample Models (RMM) project and select New Team Area b. In the Name field, type ACC Feature Team c. Click Finish 1-8 Copyright IBM Corp. 2018

9 Lab 7 Streams and Components d. As before, click Add to add new Members but this time add only Dan (with all process roles) e. Click Save f. Click Cancel: 4. Change Ownership of Components: a. Click the Team Artifacts tab in the sidebar b. Expand Sample Models (RMM) Source Control All Streams ADAS Features c. Right-click the ACC Feature component and select Change Owner: d. In the Select Component Owner dialog, select the ACC Feature Team e. Select Restrict to members of this team and its child team areas: Copyright IBM Corp

10 Rhapsody Model Manager Tech Jam f. Click OK g. Repeat the process for the ADAS System component this time changing its ownership to the System Team (and restricting access) Task 3: Restrict Visibility to Components Using Access Groups In this task, you will define an Access Control Group and restrict visibility to the shared component using Access Control Groups. Note that Access Control Groups may contain teams, project areas or individuals. In this example, your Access Group will contain both the Systems Team and the ACC Feature Team. Access Control Groups may only be defined using the web client. 1. Create an Access Control Group: a. In the web browser, open the Architecture Management application and navigate into the Administration page for the Sample Models project b. In the main menu, click Access Groups: c. At the top right hand corner of the page, click Create Access Group: 1-10 Copyright IBM Corp. 2018

11 Lab 7 Streams and Components d. In the Name field, type ADAS Shared e. In the Members section click Add a Project or Team Area: f. Select the ACC Feature Team and click OK: g. Repeat the process and add the Systems Team TIP: Multiple select is not possible Copyright IBM Corp

12 Rhapsody Model Manager Tech Jam h. Click Save 2. Assign Access Groups: a. Switch back to RTC b. Right-click the ADAS Interfaces component and select Change Access Control: c. Select Access Group and then click Browse: d. In the search field, type * then click Search: 1-12 Copyright IBM Corp. 2018

13 Lab 7 Streams and Components e. Select the ADAS Shared Acess Group and click OK f. Click OK: Task 4: Create a New Model In this task, you will create a new sample model in Pete s sandbox in the ADAS System component folder. You also will add the Harmony profile so that you can make use of the automation features included to speed up creation of model elements. You will then create a shared model in the ADAS Interfaces component folder and move one of the System packages into that model. 1. Create a New Model: a. Switch to Rhapsody b. From the menu, select File New c. In the In folder field, click Browse d. Browse to C:\Workspaces\pete\ADAS Features Workspace Pete\ADAS System and click OK e. In the Name field, type ADAS_System f. In the Project Type field, select SysML g. Select Enable Rhapsody Model Manager: Copyright IBM Corp

14 Rhapsody Model Manager Tech Jam h. Click OK i. Click No: Click Yes: j. The model is created with each of the units in an unresolved state: 1-14 Copyright IBM Corp. 2018

15 Lab 7 Streams and Components 2. Modify RTC Properties: a. Right-click the root of the browser and select Features b. Select the Properties tab c. Click the filter button and select Rational Team Concert Settings d. Set the DeleteActivation property to Automatic e. Set the MoveActivation property to Automatic f. Set the RenameActivation property to Automatic TIP: In a few moments you will add the Harmony profile to the model and use the Systems Engineering Toolkit to create a new project structure. That wizard renames the Default package. If the DeleteActivation property is set to user confirmation (the default) this is ignored during any automated operations performed through the API and will lead to RTC being out of sync with the model. 3. Add the Harmony Profile: a. From the menu, select File Add Profile to Model b. Double-click the HarmonySE folder c. Double-click the HarmonySE.sbs file d. Click OK: Copyright IBM Corp

16 Rhapsody Model Manager Tech Jam 4. Save and Check-In a. From the menu, select File Save 5. Create a Project Structure: a. Right-click the root of the browser tree and select SE-Toolkit Create Harmony Project 6. Save and Check-In a. From the menu, select File Save 7. Observe Changes: a. Right-click the ActorPkg Package and select Rational Team Concert Locate in Pending Changes b. Note that there are unresolved elements in the Pending Changes: 1-16 Copyright IBM Corp. 2018

17 Lab 7 Streams and Components TIP: The wizard copied some RTF files to the project folder but did not add them as Controlled Files (this is a defect and will be fixed in a future version). For now we will add one of new files as Controlled Files manually to see the effect we will then add the others to the change set manually. 8. Add a Controlled File: a. Switch back to Rhapsody b. Right-click the RequirementsAnalysisPkg Package and select Add New Extensions ControlledFile c. Navigate to C:\Workspaces\pete\ADAS Features Workspace Pete\ADAS System\ADAS_System\ADAS_System_rpy d. Select the Actor template.rtf file: e. Click Open 9. Save and Check-In a. From the menu, select File Save b. Note the Controlled File is now outgoing: 10. Observe Changes: a. Right-click the new Controlled File and select Rational Team Concert Locate in Pending Changes b. Note the Controlled File is part of the change set: Copyright IBM Corp

18 Rhapsody Model Manager Tech Jam 11. Add the other files: a. Right-click the Unresolved folder and select Check-in Rhapsody Files Check-In: ADAS_System: 12. Deliver the Changes: a. Right-click the change set and select Deliver 13. Create a Shared Model: a. Switch back to Rhapsody b. From the menu, select File New c. In the In folder field, click Browse d. Browse to C:\Workspaces\pete\ADAS Features Workspace Pete\ADAS Interfaces and click OK e. In the Name field, type ADAS_Interfaces f. In the Project Type field, select SysML g. Select Enable Rhapsody Model Manager: 1-18 Copyright IBM Corp. 2018

19 Lab 7 Streams and Components h. Click OK i. Click No to the SysML Perspectives question and click Yes to create a new folder j. Click File Save 14. Move the Interfaces Package: a. From menu, select File Insert Project Existing b. Browse to C:\Workspaces\pete\ADAS Features Workspace Pete\ADAS System\ADAS_System c. Select ADAS_System.rpyx and click Open d. If Rhapsody asks you to save, click Yes: e. Click OK: Copyright IBM Corp

20 Rhapsody Model Manager Tech Jam f. Right-click the ADAS_Interfaces model and select Set as Active Project: g. Click Yes: 1-20 Copyright IBM Corp. 2018

21 Lab 7 Streams and Components h. In the browser, expand the ADAS_System project and its Packages: i. Select the InterfacesPkg Package j. Hold down the Shift key and drag the InterfacesPkg to the ADAS_Interfaces project: k. Keeping the shift key held, release the mouse button a menu appears with options for moving / copying the unit: Copyright IBM Corp

22 Rhapsody Model Manager Tech Jam l. Click Move here leave a reference m. Note that the InterfacesPkg is now a reference and read only: TIP: What we really want here is an editable reference rather than a read only one however the drag and drop mechanism does not yet offer that option so you will now re-add the package to the System model and make it an editable reference, n. Right-click the ADAS_System model and select Set As Active Project o. Click Yes: 1-22 Copyright IBM Corp. 2018

23 Lab 7 Streams and Components p. From the menu, select File Add to Model q. On the right-hand side of the window, select As Unit and clear Copy into Model: r. Navigate to C:\Workspaces\pete\ADAS Features Workspace Pete\ADAS Interfaces\ADAS_Interfaces\ADAS_Interfaces_rpy s. Select InterfacesPkg.sbsx and click Open t. Select Replace existing unit: u. Click OK v. Save the model w. Note that the InterfacesPkg unit is now an editable reference and though it resides in the shared area it can now be edited directly from the Systems model: Copyright IBM Corp

24 Rhapsody Model Manager Tech Jam 15. Deliver the Changes: a. Switch to RTC and note the two outgoing change sets and an unresolved element: TIP: The unresolved InterfacesPkg.sbsx file is because you did not set the default delete/move/rename properties for RTC. You will now add that file manually to the change set. 16. Add the unresolved file: a. Right-click the unresolved InterfacesPkg.sbsx file and select Check-In Rhapsody Files Check-in: ADAS_Interfaces 17. Deliver the changes: a. Right-click the Stream and select Deliver to deliver both change sets: 1-24 Copyright IBM Corp. 2018

25 Lab 7 Streams and Components b. Click OK: c. Note that RTC throws an error as Pete does not have visibility into the ACC Feature component: 18. Unload the ACC Feature component: a. Switch to the Pending Changes tab b. Right-click the ACC Feature Component and select Unload: Copyright IBM Corp

26 Rhapsody Model Manager Tech Jam c. Click Yes: d. Note the component becomes clear to indicate it is not loaded: e. Attempt the change set delivery again this time there should be no errors and the delivery should complete Task 5: Create the Feature Model In this task, you will work as Dan in the Feature team creating a Feature model that references the Interfaces in the shared component. 1. Switch to Dan s Workspace: a. Switch to Rhapsody 1-26 Copyright IBM Corp. 2018

27 Lab 7 Streams and Components b. From the menu, select File Close c. Click No: d. Switch back to RTC e. From the menu, select File Switch Workspace c:\workspaces\dan 2. Accept the Incoming Baseline: a. Select the Pending Changes tab b. Right-click the incoming change set and select Accept: 3. Create a Repository Workspace for the Stream: a. In the Team Artifacts browser, expand the Sample Models [RMM] project b. Expand the Source Control All Streams section c. Expand the ADAS Features Stream and note that Dan cannot see the System component: d. Right-click the ADAS Features stream and select New Repository Workspace e. Add Dan to the end of the existing name: Copyright IBM Corp

28 Rhapsody Model Manager Tech Jam f. Click Next g. Select Use current repository: h. Click Next i. Select Project Area: j. Click Next k. Note that both (of the visible) new components are already selected: l. Click Finish 1-28 Copyright IBM Corp. 2018

29 Lab 7 Streams and Components m. Select Browse the components to select the folders to be loaded: n. Click Next o. Select the ACC Feature Component p. Place a checkbox in the ADAS_Interfaces component TIP: IMPORTANT: as before if you do not select the higher-level component then a folder will not be created for it. q. Expand the Advanced Options section r. Select Load component files into sandbox subfolder s. Select Load the selected folders but do not create Eclipse projects: t. Click Finish Copyright IBM Corp

30 Rhapsody Model Manager Tech Jam u. Click OK: 4. Confirm Folder Creation: a. Open Windows Explorer b. Navigate to C:\Workspaces\dan c. Confirm that there is a new folder for the stream and inside it one for each component: 5. Create a New Feature Model: a. Switch to Rhapsody b. From the menu, select File New c. In the In folder field, click Browse d. Browse to C:\Workspaces\dan\ADAS Features Workspace Dan\ACC Feature and click OK e. In the Name field, type ACC_Feature f. In the Project Type field, select SysML g. Select Enable Rhapsody Model Manager: 1-30 Copyright IBM Corp. 2018

31 Lab 7 Streams and Components h. Click OK i. Click No: Click Yes: 6. Add the Interfaces: a. From the menu, select File Add to Model b. Browse to C:\Workspaces\dan\ADAS Features Workspace Dan\ADAS Interfaces\ADAS_Interfaces\ADAS_Interfaces_rpy c. Select the InterfacesPkg.sbsx file and click Open d. Click File Save e. The Feature model may now use Interfaces defined by the Systems team with no visibility into the rest of the Systems model: Copyright IBM Corp

32 Rhapsody Model Manager Tech Jam 7. Save and Check-In: a. From the menu, select File Save 8. Deliver the changes: a. Switch to RTC b. Deliver the change set: Task 6: Create a Flow Diagram In this task, you will create a Flow Diagram that visualizes the streams, their components and flow targets. 1. Create a new Flow Diagram: a. In the Pending Changes tab, right-click the ADAS Features Workspace and select New Flow Diagram: b. The new Flow Diagram opens: 1-32 Copyright IBM Corp. 2018

33 Lab 7 Streams and Components c. In the Dan node on the Flow Diagram, click the two downward arrows to expand the node to show components in Dan s repository workspace: d. In the Dan node, click the filled-in downward arrow on the right and select Show Flow Targets: e. In the new ADAS Features node, click the icon in the center to show other streams/workspaces that flow into it: Copyright IBM Corp

34 Rhapsody Model Manager Tech Jam f. Right-click the diagram canvas and select Layout to trigger an auto-layout routine: 2. Show the Palette: a. Click the small arrow in the top, right-hand corner of the diagram to open the Palette: TIP: The palette allows you to add other streams, workspaces and so on and also notes you could then save the flow diagram as an image. b. Click the X in the Flow Diagram tab to close it c. Click No: 1-34 Copyright IBM Corp. 2018

35 Lab 7 Streams and Components 3. Change a Flow Target: a. In the Pending Changes view, right-click ADAS Features Workspace Dan and select Change Flow Target: b. In the Show section, select Workspaces c. In the Search field, type pete: d. Select ADAS Features Workspace Pete (Pete) [RMM] e. Click OK 4. Observe changes: a. Note that this change of flow target triggers a comparison between Dan s workspace and Pete s and this results in a change set. Note also that the flow target is indicated in the Pending Changes view: Copyright IBM Corp

36 Rhapsody Model Manager Tech Jam 5. Generate a Flow Diagram a. Repeat the previous steps to generate a new Flow Diagram and show the flow targets: TIP: The Default flow target for each stream is annotated with the word Default. A dashed line indicates that this flow target is not the current one. There may be multiple flow targets but only ever one current flow target indicated with a solid line. b. Close the Flow Diagram and click No to the save dialog. 6. Restore the Flow Target to the Team Stream a. In the Pending Changes view, right-click ADAS Features Workspace Dan and select Change Flow Target b. Click Select Default Outgoing and click OK: 1-36 Copyright IBM Corp. 2018