Starter Construction Diagram
The Starter Construction Diagram Pattern One pattern creates a Construction Diagram and Use Case element that has a number of construction items added. The element gives a clear and cohesive view of the important aspects of how the Use Case will be managed and implemented including:  Requirements, Constraints, Tests, Maintenance Items, Resources that have been allocated and more.

Figure 1. Shows a Use Case element displayed on a Construction diagram with visible compartments for requirements, constraints, tests-scripts,maintenance and resources.

Figure 1. Shows a Dynamic Document that is automatically generated as the Use Case is completed..
.
Discussion
The purpose of the pattern is to allow Business Analysts, Project Managers, Implementation Teams and other stakeholders to create and view a diagram that gives a cohesive view of the important management and implementation aspects of a Use Case. The modeler is able to scroll through the items in the element in the diagram and conveniently view the details of each item in the construction window. 

It is typically created after a Use Case has been analyzed and implementation is due to be started. The construction diagram would then continue to be a diagram of central focus allowing project mangers, scrum masters and others to get a clear cohesive and coherent understanding of all of the important implementation aspects of the element.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the Package, Diagram and Use Case element to suite the initiative.
Change the name of the maintenance items and add others as required.
Change the names of the Tests and add others as required.
Change the name and roles that have been assigned or the Resources.
Change the element's Notes to describe the Use Case.
View the Dynamic document by opening the document window.

The following is a list of some of the next steps available when applying the pattern.
·	Add Tagged Values to record user-defined properties
Use relationships to show the connections the Use Case has to up-process elements such as stakeholder Requirements and down-process elements such a Components.
Add a Linked Document that can be used to describe or document aspects of the implementation

Useful Workspace Layouts Core | Core Modeling, Wide View
Reference
The following help topics will assist you learn about how to work with this pattern.
Maintenance Items
Testing
Resource Allocation
Element Browser
Document Window
Use Case Diagram
System Boundary
Use Case
Actor

The following are some of the tools that will be helpful when working with this pattern.

Maintenance Items
The Maintenance Items feature allows any element to have information added to detail, explain or clarify the element from a project management point of view. They can be added to Requirements, Use Cases, User Stories, Components, Deployment Nodes and many more and  capture problems, changes, issues, tasks, events and decisions that affect an individual element.  For more details see the Maintenance Items help topic.
Testing
The Testing facility provides a powerful way of managing a wide range of testing classes including; Unit, Integration, System, Acceptance, Scenario and Inspections. The testing window can record the name of the Test, status of the test, Who the Test was run by, Type of Test (such as Regression), Who it was Checked by, Class of Test (such as Acceptance), Date it was last run. Description of the Test, Inputs required, Acceptance Criteria and Test Results. For more details see the Testing help topic.
Resource Allocation
Resource Allocation can be used to manage resources and track how work is progressing against predefined estimates.  Resources can be defined as repository reference data and then one or more resources can be allocated to a model element. The allocation can be done in an agile way where a resource simply identifies a task or element that needs to be completed and allocates themselves or the allocation could be done by a project manager. Sophisticate and compelling charts and dashboard diagrams can be generated automatically given a powerful representation of the progress. For more details see the Resource Allocation help topic.
Element Browser
The Element Browser is a tree view style window that contains many of the details for individual elements including: Attributes, Operations, Tagged Values, Files, Requirements (internal), Relationships, Constraints Maintenance and Project Maintenance Items and more. It can be used in synergy with the Project Browser so that when an element is selected in the Project Browser all its details can be conveniently displayed in the Element Browser.  For more details see the Element Browser help topic.
Document Window
The Document Window is a powerful tool for generating, reading and editing narrative style information for an element. There are two tabs: the Dynamic Document Tab and the Linked Document Tab. The Dynamic Document tab generates documentation automatically from element information and the Linked Document tab cab be used for reading and editing an element's linked document. For more details see the Document Window help topic.

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