Risk Analysis and Management
The Risk Analysis and Management pattern creates elements and a diagram allowing Risks to be modeled that are associated with a solution. The Risks could be associated with any element including a Subsystem, Component or a Business Process. The elements are displayed in the Info View presentation style making the diagram more appealing for non-technical audiences.

Figure 1. Shows a diagram where three risks have been modeled and are visually represented using the Info View presentation style.
Discussion
The purpose of the pattern is to allow Business Analysts and other stakeholders to analyze and manage Risks inside the repository allowing them to be related to an entire initiative or part of an initiative.  The Risks can be visualized in the context of the elements they relate to rather than being kept in an external register.

The Risks are typically managed throughout the lifetime of the project but a concerted effort is often made early on or at the outset of an initiative to tabulate the most important Risks to make sure they can be managed and to minimize the effect they have on the initiative. 

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the diagram to suit the initiative.
Change the name and stereotype of the main element that the Risks are associated with if required.
Change the name of the Risks and add notes and other properties to elaborate the Risks.
Create additional risks that are applicable to the initiative.

The following is a list of some of the next steps available when applying the pattern.
·	Consider using a formal risk taxonomy to manage the Risks.
A Kanban diagram could be used to manage the risks moving the Risks from lane to lane depending on properties such as likelihood or status.
Risks can be traced to other elements in the Repository including requirements and implementation elements such as Components and Artifacts.
Generate documentation in the form of a risk register or other document using built-in or custom templates.
Reference
The following help topics will assist you learn about how to work with this pattern.
Risk Taxonomy
Risk Analysis and Management
Kanban
Business Analysis Body of Knowledge (BABOK)
Traceability Tools
Documentation

The following are some of the tools that will be helpful when working with this pattern.
Kanban
Kanban diagrams can be used to manage a wide range of items in Enterprise Architect including User Stories, Requirements, Defects, Issues, Risks and more. The facility provides one or more Kanban boards that can be related to each other in a visually compelling and easy to work with tool. Workflows can be created that allow the management of items by different groups including product managers managing backlogs and implementation teams managing development teams. For more details see the Kanban help topic.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic or the more general topic on Model Publishing.
Element Discussions
The Element Discussion facility is a fully featured collaboration tool allowing modelers and model viewers and reviewers to communicate with each other directly inside the repository. Modelers using the full client or occasional viewers using WebEA can both post and reply to discussions and communicate and engage in chat. For more details see the Element Discussions help topic.
Specification View
The Specification View can be used as a way of working with any element type in a spreadsheet or word process view. It is particularly useful when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic.
Import and Export Spreadsheets
It is common for analyst to have started their modeling of Risks in a Spreadsheet or to want to manipulate existing elements in a Spreadsheet. Enterprise Architect has a flexible and configurable tool for importing and exporting elements from a CSV file which can be imported and exported from a Spreadsheet. Any type of element can be imported or exported to the spreadsheet file but it is very useful for working with Risks. The tool provides a flexible Specification window where the mapping between element properties and the columns in the Spreadsheet and other parameters can be defined and saved. Essentially the columns of the spreadsheet define the properties and each element is specified in a row. For more details see the Import and Export Spreadsheet help topic.
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.