EA management views can help various types of users to both understand and share EA artifacts. For example, members of the EA team who are modeling data in several information systems can develop a management view to show how information from those systems is used between various LOBs, and in so doing gain the support… Continue reading Why are management views of EA artifacts important?
Because an enterprise’s strategic drivers, business requirements, and technology solutions change over time.
EA artifacts are types of documentation that describe components, including reports, diagrams, charts, spreadsheets, video files, and other types of recorded information. High-level EA artifacts are often text documents or diagrams that describe overall strategies, programs, and desired outcomes. Mid-level EA artifacts are documents, diagrams, charts, spreadsheets, and briefings that describe organizational processes, ongoing projects,… Continue reading What are EA artifacts and how do they relate to EA components?
EA artifacts document EA components in a consistent way across the entire architecture.
Examples of changes to components include a new strategic goal, business process, information flow, IT system, Web service, application network, security solution, standard, or workforce requirement. \nChanges to components may also reflect upgrade, integration, and retirement activities. \nProvide some examples of artifacts at the Goals & Initiatives level of the EA
Current Strategic Scenario, Strategic Goals, Initiatives, Measures.
Objects are like entities in that they have a name and attributes, and link to other objects according to rules for frequency. One might say that objects know things about themselves. Objects are unlike entities in that the code for objects also contains behaviors (also known as methods), which are triggered by events that are… Continue reading What are the differences between traditional (ERD and DFD) data modeling techniques and object oriented data modeling techniques (UML)?
Vendor supplied documentation may include data models, system and application interface information, network specifications and standards, and other artifacts that should be retained as part of the documentation of current and future EA views. Using vendor supplied information avoids the cost of recreating that information and maximizes the accuracy of that information.
Network Connectivity Diagram, Network Inventory, Capital Equipment Inventory, Building Blueprints, Network Center Diagram, Cable Plant Diagram, Rack Elevation Diagram
The future architecture should cover planned changes to EA components in the near term (tactical changes in the next 1-2 years), as well as changes to EA components that are a result of the implementation of long-term operating scenarios that look 3-10 years into the future. These scenarios incorporate different internal and external drivers and… Continue reading How far into the future should the EA future views attempt to provide documentation?