Technology Roadmap
The Technology Roadmap pattern creates elements and a Roadmap diagram that focuses on a strategic and high level view of how and organization's goals will be realized. It creates a high level view of the of internal systems, product management and process used to implement and support systems. The roadmap is divided into a number of sections that assist with the visualization of the strategic technology initiatives.

Figure 1. Shows a Technology Roadmap diagram using swimlanes to show the items in each facet of the roadmap. A legend controls the colored bands indicating the phase.
Discussion
The purpose of the roadmap is to allow Chief Information Officers, Architects, Analysts and other senior stakeholders to capture a time based visualization of how an organization will use technology to realize its goals and objectives.

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 type of the elements to suit the initiative.
Change the positions of the elements to reflect a different chronology.
Change the lengths of the colored divisions on the elements to reflect the period of time for each facet. 

The following is a list of some of the next steps available when applying the pattern.
·	Change the Legend to reflect a different aspect of the elements' lifecycle or evolution.
Create Trace or Realization relationships between elements in the diagram and other up-process or down-process elements in the model.
Automatically create documentation for business or technical audiences that includes the Roadmaps using the Document Generator .

Useful Workspace Layouts Core | Core Modeling
Reference
The following help topics will assist you to learn about how to work with this pattern.
Roadmaps
Roadmap Diagrams
Roadmap Diagram Options
Diagram Legends

The following are some of the tools that will be helpful when working with this pattern.
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.
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.
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.
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.
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.
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.

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