Basic Optional Last Guidance

The Basic Optional Last Guidance pattern creates elements and an Activity diagram that can be used to create a sequenced set of checklists each with a list of items (steps) that need to be completed. There is an optional checklist at the last Action that can be used to model extra steps that conditionally need to be completed at this point in the process.

Figure 1. Shows an Activity diagram with a series of sequenced checklists each containing a list of items. The last Action has an optional Checklist to indicate that there are additional steps that can conditionally be completed at that point in the process.

Figure 2. Shows a fragment of the sequence of checklists where all of the checklist items in the first Action have been checked as complete automatically resulting in a tick which provides a visual indicator of completeness.

Discussion
The purpose of the pattern is to allow a modeler to specify a potentially complex process as a sequence of actions, each with a list of items that can be followed allowing a user to indicate that the items in each checklist have been completed by ticking a checkbox. At the last Action there is a optional checklist that can be used if there are items that conditionally may be done at this point.

The pattern can be used whenever a task, process or method needs to be described in a  sequence of checklists. The following is a list of some of the ways it can be used:
·	Create a Process Guidance.
Describe the steps to implement a solution.
Describe the steps to install hardware or Software.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the Package and diagram to suit the initiative.
Change the name of the Actions to reflect the sequence of steps.
Change the names of the items in the checklists to suit the initiative.
Create additional items in any checklist.
Change the location of the optional checklist by dragging the connector end to another Action.
Create additional Actions and checklists as needed.

The following is a list of some of the next steps available when applying the pattern.
·	Once the checklist has been designed make a copy of the containing package and place it in an appropriate location in the Repository ready for completion. Making a copy of the package allows the original package to serve as a template that can be reused.
·	Create a model mail message to remind a modeler that the checklist sequence needs to be completed.
Apply diagram colors notes and include images to exemplify the sequence of actions or the list of item in the checklists.

Reference
The following help topics will assist you learn about how to work with this pattern.
Using the Checklist and Audited Checklist Artifacts
Activity Diagrams
Layout Diagrams
Tools you may find useful
The following are some of the tools that will be helpful when working with this pattern.
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.
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.
Diagram Layout
The Diagram Layout tool allows you to layout an entire diagram, selected elements or sections of a diagram to make it more visually appealing or meaningful to a particular audience. There are a wide range of layout types to choose from and some types have filters that can be applied. For more details see the Diagram Layout help topic.
Pan and Zoom
The Pan and Zoom facility is one of the tools that can be used to navigate around a large diagram. Often the resolution of a diagram must be reduced to ensure it is wholly visible but by using the Pan and Zoom window you can leave the diagram at a readable resolution and pan around to areas of interest zooming in when necessary. For more details see the Pan and Zoom help topic.
Diagram Legends
The Diagram Legend facility is useful for manually or automatically changing the appearance of elements and connectors on a diagram. A legend can be added from the Common Toolbox and configured to codify the fill and line color and line thickness. This is a powerful way to add meaning and expression to a diagram and is particularly expressive when applied automatically based on element or connector properties. It can be used with a number of specialized diagrams such as roadmaps to create a powerful visualization.  For more details see the Diagram Legends help topic.
Calendar
The Calendar provides a way to record and present important temporal information such as events and meetings in calendar format. Collaborative Games can be entered into the Calendar and setup as recurring if needed. Event subtypes can be configured to add Collaborative Games as a Meeting Type. For more details see the Calendar help topic.
Model Mail
Model Mail can be used to notify and remind people of a Collaborative Game and to notify them after the game has been played about outcomes and decisions and required actions. Links to model elements and diagrams, matrices, team reviews and a variety of other items can be added.. For more details see the Model Mail help topic.

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