1. Exmouth House 3–11 Pine Street London EC1R 0JH T +44 20 7832 5850 F +44 20 7832 5870 E office@adelard.com W www.adelard.com ASCE Master-class Configuration management – approaches and tools for ASCE George Cleland 10 th December 2015

2. © ADELARD 2015 Slide 2 CONFIGUATION MANAGEMENT File links/Web links Relative/absolute paths? Tracking change in files Tracking change in Web links Node numbering Simple configuration example Content mapping and change tracking Resource Manager File mapping Packaging Embedded issues management Node review manager

3. © ADELARD 2015 Slide 3 FILE LINKS Relative/absolute paths?

4. © ADELARD 2015 Slide 4 FILE LINKS Tracking change in files

5. © ADELARD 2015 Slide 5 GLOBAL LINK CHECKING Checks that all internal links terminate sensibly, and that file links terminate of an existing file and that the file has not changed since the link was last updated

6. © ADELARD 2015 Slide 6 Traceable Web link See demonstration. Tracks changes –However, only in static web pages Reported for individual links, but also on global DNR checking

7. © ADELARD 2015 Slide 7 NODE NUMBERING Provides fine grained configuration management within an ASCE document Set using the ID field in the node editor or for in-place editing –Prefix node title with ‘node number –’ Can be done manually Cumbersome and error prone –Even for relatively small example Node numbering plugin

8. © ADELARD 2015 Slide 8

9. © ADELARD 2015 Slide 9 NODE NUMBERING PLUGIN Can also be used for creating an export path See MS Word export Master-Class later

10. © ADELARD 2015 Slide 10 SIMPLE CONFIGUATION MANAGEMENT Master ASCE 1.0 Supporting files..\supporting files HTML 1.0..\supporting files Word 1.0..\supporting files ASCE 1.1 ASCE 2.0

11. © ADELARD 2015 Slide 11 CONTENT MAPPING AND CHANGE TRACKING - I Integration with other tools and evidence Continue using existing tools Minimises disruption of existing processes Powerful change tracking capability Integrate and track changes in information from –spreadsheets, narrative documents (Word, PDF), databases, DOORS, etc. Supports strong configuration management across heterogeneous document sets

12. © ADELARD 2015 Slide 12 CONTENT MAPPING AND CHANGE TRACKING - II Click to open a node for editing content Create links to files Create Web links ASCE DNR Plugins let you map content from most common ‘Office’ document formats Once information is mapped, ASCE can track change in the source document

13. © ADELARD 2015 Slide 13 CONTENT MAPPING AND CHANGE TRACKING - III ASCE can support similar content mapping and change tracking in most common document types: Word Excel Access and other databases PDF DOORS Cassandra/eCassandra Other ASCE documents –and other formats In principle, such mapping can be supported for any other document where there is a well defined file format or application programming interface to the supporting system

14. © ADELARD 2015 Slide 14 Global DNR checking Tools  Check plugin regions Produces a report on all DNRs in current network which have changed

15. © ADELARD 2015 Slide 15 RESOURCE MANAGER Manage links to external files Makes it easy to version your network and its supporting files Better supports access to ‘live files’ Can create a ‘package’ A snapshot of your ASCE document And all linked document

16. © ADELARD 2015 Slide 16 LINKS TO EXTERNAL DOCUMENTS DNR PLUGINS IMPORTING FROM EXTERNAL DOCUMENTS Instead of 5 nodes suppose 400 And instead of 1 document suppose 25 And each with 20 links Document V1

17. © ADELARD 2015 Slide 17 DOCUMENTS UP-ISSUED AS NEW VERSIONS Need to re-link all 500 links from 400 nodes Needs re-making all 20 links, and reading all 400 nodes!!! Document V1 Document V2

18. © ADELARD 2015 Slide 18 RESOURCE MANAGER CAN HELP Creates list of all external documents referenced and nodes referenced from Document V1 Browse to Document V2

19. © ADELARD 2015 Slide 19 DOCUMENT UP-ISSUED AS VERSION 2 Navigates all links from document V1 to document V2 Document V1 Document V2

20. © ADELARD 2015 Slide 20 NEW FILE(S) RE-LINKED For all 400 nodes and all 25 documents Document V1 Document V2

21. © ADELARD 2015 Slide 21 PACKAGING Creates a folder Copies our ASCE network to it Creates a new folder: supporting files Copies all referenced docs there And re-makes links to those Result: A stand-alone copy of our ASCE network and all linked files Copy to CD, or archive Supporting files Docum ent V2

22. © ADELARD 2015 Slide 22 EMBEDDED ISSUES MANAGER During the Assurance Case management lifecycle a number of issues will often arise requiring further management: Assumptions to be confirmed, Actions to be closed off, Issues to be resolved, Operating limitations to be recorded and transferred out to the operating environment … These issues usually arise in a specific context of the argument structure From a management point of view we want to look after them and track them understand them in context Summarise them across the overall case Summarises them in higher level cases

23. © ADELARD 2015 Slide 23 HOW TO MANAGE THESE ISSUES? Could be managed using some external tool database, text document, spreadsheet etc disadvantages: –the link to the originating context is generally lost –yet another separate process and tool to be managed Or, could be managed as an integral part of the Assurance Case enter the Embedded Issues Manager

24. © ADELARD 2015 Slide 24 EMBEDDED ISSUES MANAGER An ASCE plugin that allows management of embedded issues within an Assurance Case, and its linked cases Uses ASCE DNRs objects to manage issues and issue summaries

25. © ADELARD 2015 Slide 25 USE IS SIMPLE As the analysis proceeds, drop any number of embedded issues within the narrative of the nodes Basic fields: –Title –Keywords –Text Different issues types: –Issue, Action, Requirement, Limitation, Assumption, Risk –… (the list can easily be extended if desired) At a high level in the case insert an Issues Summary DNR This collates all issues of a certain type into a table Summary can be of the current network or an external network

26. © ADELARD 2015 Slide 26 SCREENSHOT This screenshot shows: embedded issue DNR in an individual node Summary DNR of all issues in the current network

27. © ADELARD 2015 Slide 27 NODE REVIEW METADATA MANAGER Commissioned by QinetiQ Requirements defined by Laurie Henery Used to record last review dates and set next review period Also to record ‘metadata’ at node level history - who, what, and when Can then search for nodes due for review in defined period and navigate to them from the table

28. © ADELARD 2015 Slide 28 NODE REVIEW METATA MANAGER – USE I

29. © ADELARD 2015 Slide 29 NODE REVIEW METATA MANAGER – USE II Control-click to navigate to the node

30. © ADELARD 2015 Slide 30 Questions? Thank you

31. © ADELARD 2015 Slide 31