Catalogs
The Catalogs pattern creates catalogs as diagram elements that allow for the visualization of architectural content in lists with properties displayed in columns within the lists. Catalogs along with Matrices and Diagrams describe the architectural and are typically incorporated into Deliverables.

Figure 1. Shows a diagram that contains a number Model View elements that are available from the Dashboards toolbox.

Figure 2. Shows he Model View elements in the Project Browser.
Discussion
The purpose of the pattern is to allow Architects and other stakeholders to model and view Catalogs that can be used to visualize the architecture content in a list. The list can include any number of properties represented as columns and the Catalog is dynamically updated as elements are added to, removed from or updated in the repository.

It is typically created after a number of artifacts have been added to the repository and can also be reused between initiatives in which case the catalogs will typically be empty until the architectural content is added to the repository. Catalogs can be used to give stakeholders a quick view of the content in a spreadsheet like view which is often more appealing to business stakeholders.

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 underlying scripts that determine what content is display.
·	Create additional Catalogs as required.
Create Traces to elements that form part of the deliverables
·	Change the name of the elements to suit the initiative.
Create additional elements and relationships to suit the initiative.

The following is a list of some of the next steps available when applying the pattern.
·	Import or link to architecture content that may reside in other tools and in formats such as spreadsheets and word processor documents.
Create documentation automatically with the document generator using built-in or user defined templates.
·	Create drill-down from diagram elements by adding a child diagram which will make the element composite and allow a user to click-through to a more detailed or explanatory diagram .

Useful Workspace Layouts Core | Core Modeling, Wide View
Reference
The following help topics will assist you learn about how to work with this pattern.
Enterprise Architecture
Welcome to MDG Technology for TOGAF
Using the MDG Technology for TOGAF
The TOGAF Enterprise Continuum
The Architecture Development Method
Modeling

The following are some of the tools that will be helpful when working with this pattern.
Gap Analysis Window
The Gap Analysis Matrix is a specialized Relationship Matrix that is used to record the gaps that exist between two versions of some part of an enterprise. The gaps between two different version of an architecture could be recorded, or the gaps in two versions of Capabilities or Staff Competencies, or two versions of Information or Data. The tool is structured like a spreadsheet with columns and rows. For more details see the Gap Analysis Matrix help topic.
Time Aware Modeling
The Time Aware Modeling feature allows architects, analysts and others to create incremental versions of their models by providing tools that allow the modeling of future states. The tool facilitates the visualization of elements, diagrams and packages through the dimension of time, allowing multiple transitions or versions to be created. The baseline ('As-is', current state) models remain unaffected and any number of target ('To-Be', future state) models can be constructed for the purpose of visualization and analysis. For more details see the Time Aware Modeling help topic.
Reviews
The Review facility is a collaborative and team tool that allows one or more models elements to be reviewed and the comments made visible directly in the model.  The reviews can be conducted formally or informally and the review process can be augmented by further Discussions and Chat available from the same location in the User Interface. For more details see the Formal Review Elements help topic.
Decision Tree
A Decision Tree is a diagram that is part of the Strategic Modeling Technology and uses a visual notation to represent a series of decisions and possible outcomes. It can be used in either a descriptive or predictive manner to visualize outcomes and decision points. The Decision Tree diagram can be used to create a Five Whys diagram starting with the problem and fanning out. For more details see the Decision Tree help topic.
Decision Tables
The Decision Table Editor can be used simply to record the conditions and the conclusions that form the basis of decision making. Alternatively, implementation code can be generated using the Enterprise Architect Simulation Library (EASL) code generation macros. It uses a clear and understandable interface allowing the analyst to enter conditions, condition value columns, defined values that act as a decision point, and one or more conclusions. For more details see the Decision Table Editor 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.
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 the Components and Interfaces particularly 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
Baseline Tool
The Baseline Tool can capture a snapshot of a selected Package at a point in time and then at a later time the repository can be compared to this (or another baseline) for the purpose of determining what has changed. Any number of baselines can be created and labeled and there is a baseline comparison tool which displays the differences between the baseline and the model and allows the modeler to revert a change in the model to a baseline at a granular level. For more details see the Baseline Tool 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.
Hand Drawn and Whiteboard Diagrams
The Hand Drawn and Whiteboard Mode are display options available for any diagram that changes a system-drawn diagram to appear as though it was drawn by hand and, optionally, hand drawn on a whiteboard. It is a powerful device to engage an audience by presenting the diagram in a rough and more immediate style giving the impression that it is just a sketch that can be changed. For more details see the Hand Drawn and Whiteboard Mode help topic.
Alternate and Images for Diagram Elements
Most standard elements allow an alternate image to be defined for an element that will be used in place of the graphical notation for the element either on a selected diagram or as a default on all diagrams. For more details see the Using the Image Manager help topic.

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