1. Integration of User Requirements Notation (URN) and DOORS with URNtoDOORS SEG3201 Fall 2006

2. © 2006 Page 2 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS u RunDXLScript imports URN into DOORS Importing and Updating of UCMs/GRL in DOORS

3. © 2006 Page 3 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS WriteDXLScript = Exporting URN Models u Right click on jUCMNav editor – Export – Export whole URN file – File type: Telelogic DOORS (*.dxl) – Filename prefix: will be used as the name of the root URN folder in DOORS u Alternatives – File – Export – Other – Export UCM/GRL/URN – … – Right click on UCM, GRL graph, or URNSpec in outline – … u Creates a dxl file (DXL script for DOORS) and a bmp file for each UCM and GRL diagram

4. © 2006 Page 4 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS LoadDXLScript and RunDXLScript = Import u Select the DOORS folder or project in which you would like to import the URN model u DOORS Database – Tools – Edit DXL – Load – Loads your dxl file u DXL Interaction – Run – Executes your dxl script Make sure you are importing into the desired folder. This is required for functionality not used in the course. Ignore this message and click Import.

5. © 2006 Page 5 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS LoadDXLScript and RunDXLScript = Import u Creates folder for your URN model u Creates several formal UCM modules in that folder Responsibilities Components Maps * Map.Stub * Map.Resp * Map.Comp Map Devices Scenarios * Scenario * * Seq / Par * * Do Element Group * * Condition Do Element: start points, end points, responsibilities, timers, and waiting places Naming convention: Map.Element and Scenario.Resp to avoid linking confusion Definitions Not supported by jUCMNav export at this point.

6. © 2006 Page 6 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS LoadDXLScript and RunDXLScript = Import u Creates several formal GRL modules in the same folder Intentional Elements (IntEls) Actors GRL Diagrams * Diagram.IntEl * Diagram.Belief * Diagram.Actor Diagram Definitions Intentional Elements: Goals, Softgoals, Tasks; Intentional Element Associations: Contribution, Decomposition, Dependency Naming convention: Diagram.Element to avoid linking confusion Intentional Element Associations Strategies

7. © 2006 Page 7 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS Maps References Bound To Traced By Scenarios Scenario. Resp * Map.Stub Refines * Map.Resp * Map.Comp LoadDXLScript and RunDXLScript = Import u Creates several link modules in the same folder Responsibilities Components Map    from plug-in to stub (one level up)  from stub to map (at same level) Requests Hosts Devices One link module for one type of link; direction of links is bottom-up

8. © 2006 Page 8 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS u Creates several link modules in the same folder GRL Diagrams * Diagram.IntEl * Diagram.Belief * Diagram.Actor Diagram Intentional Elements (IntEls) Actors Intentional Element Associations Strategies References Bound To Rationales Refines LoadDXLScript and RunDXLScript = Import    from source element  to destination element One link module for one type of link; direction of links is bottom-up Refines

9. © 2006 Page 9 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS LoadDXLScript and RunDXLScript = Import u Creates URN Links link module in the same folder Responsibilities Components URN Links Maps One link module for one type of link; direction of links is bottom-up Intentional Elements (IntEls) Actors URN Links

10. © 2006 Page 10 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS Maintaining the URN Model in DOORS u Only link URN modules with external modules in DOORS – New objects may have to be added, existing objects may have to be modified or deleted in external modules u Make changes to the URN model with jUCMNav and then re-import the model into DOORS Make sure you are updating the desired folder. Objects with incoming links cannot be deleted automatically. You can choose to extend this policy to objects with outgoing links. Summary of objects which could not be deleted.

11. © 2006 Page 11 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS u The process is as close to the standard process as possible, considering that URN models cannot be updated directly in DOORS SynchronizeURN: The Overall Process

12. © 2006 Page 12 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS SynchronizeURN: Changes in URN Model Import Change to URNAddDeleteModify Changes to URN Modules New object: flagged as new, no links to external modules Deleted object (possibly only flagged ) Modified object New Object ViewDeleted View--- Impact on external module Establish links, add new objects Delete links (possibly delete objects ) Suspect links: clear suspect link, modify object … see page 10… if no links left

13. © 2006 Page 13 SEG3201 / Fall 2006 URNtoDOORS URNtoDOORS Report SynchronizeURN: Changes in DOORS Change to external module AddDeleteModify Impact on URN Modules Establish links, add elements with jUCMNav Delete links (possibly delete elements with jUCMNav) Suspect links: clear suspect link, modify element with jUCMNav Generate Change Report with … No Link View in external module No Link ViewSuspect View … may have to be supplemented by additional change requests