Scope Modeling
The Scope Modeling pattern creates elements and a diagram that includes a boundary that is used as a visual container for the in-scope elements. The elements are grouped into appropriate packages in the Project Browser.

Figure 1. Shows a diagram that includes a Boundary element that allows the in-scope Features to be viewed visually. The show namespace option is turned on in the diagram so the namespace appears under each element.
Discussion
The purpose of the pattern is to prove a mechanism for Business Analysts and other stakeholders to define the elements that are in and out of scope for a particular initiative, need or endeavor. By articulating both the in-scope and out-of-scope elements an analyst can be certain the boundary between the two sets has been drawn correctly. 

It is typically used in workshops or meetings between diverse groups of stakeholders to ensure that the elements have been classified correctly.  The ability to visualize both sets of elements in the one diagram facilitates the process of moving elements between the boundary.

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 of the Features to suit the initiative.
Create additional Features as needed.

The following is a list of some of the next steps available when applying the pattern.
·	Create trace relationships between the in-scope elements and other elements in the model including up-process elements such as Goals, Drivers and Business and Stakeholder Requirements and down-process elements such as Services and Components.
Add the in-scope elements to a Kanban diagram to track their implementation.
Reference
The following help topics will assist you learn about how to work with this pattern.
Scope Modeling
Feature
Kanban Features
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.
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.
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.