L08: Developing Current Architecture Views Flashcards
IDEF
Integration Definition for Function - A method for modeling business processes.
The Project Management Plan (PMP) is a standard format document used by project managers, project sponsors, and the project team to improve the conceptualization, documentation, tracking, oversight, and execution of project work throughout the enterprise.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
UML
Uniform Modeling Language (UML).
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Polymorphism
Polymorphism: Multiple object behaviors invoked by triggering events.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Inheritance
Inheritance: Attributes that carry over between parent and child objects.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Encapsulation
Encapsulation: Hidden code that protects object attributes and behaviors.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
System & Service LEvel EA Artifacts-Current View
The current view of IT systems and applications should function to show an accurate picture of the software applications, front/back office services, and operating systems that the enterprise currently has active in its IT operating environment.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Information Level EA Artifacts-Current View
Documenting information flows involves the development of data models that show the structure and flow of data in the enterprise’s business services and supporting IT systems/services. Data can be modeled and analyzed using “traditional” and/or “object-oriented” methods, depending on how the resulting documentation is intended to be used.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Business Level EA Artifacts-Current View
One method for modeling business processes is known as the Integration Definition for Function (IDEF) technique.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Strategic Level EA Artifacts-Current View
Strategic planning produces a high-level view of the direction that an enterprise sets for itself. This is documented in the general Strategic Plan and accompanying E-Commerce or E-Government Plan where the role of IT is described in more detail. The enterprise’s strategic direction is further articulated in EA artifacts that include long-range scenarios, goals, and initiatives that serve as the baseline for identifying short-term tactical (operational) goals. Strategic Plans should look five to ten years into the future and be published every two to three years. The current view of strategic level artifacts should be updated only as changes to the Strategic Plan and/or E-Commerce/E-Government Plan are formally published. This preserves the authoritative nature of the artifacts at this level and represents what is currently endorsed as policy by executive leadership.
Bernard, Scott A.. An Introduction to Enterprise Architecture: Third Edition . AuthorHouse. Kindle Edition.
Infrastructure Level EA Artifacts-Current View
EA Components:
- Data Networks
- Computing Clouds
- Telecommunications Networks
- Video Networks
- Cable Plants
- Security Solution
EA Artifacts:
- Network Connectivity Diagram (NI-1)
- Network Inventory (NI-2)
- Capital Equipment Inventory (NI-3)
- Building Blueprints (NI-4)
- Network Center Diagram (NI-5)
- Cable Plant Diagram (NI-6)
- Rack Elevation Diagram (NI-7)
System Interface Matrix (SA-3)
Physical and logical interfaces of enterprise applications are described in the Systems interface Matrix. The details of the interfaces are characterized by their status (existing, future, decommissioned), role, classification, and key integrations. The matrix permits a quick review and assessment for potential reuse and/or redundancies. As systems evolve the matrix becomes a critical tool for evaluating infrastructures, functional upgrades and the introduction of new technologies into the infrastructure.
System Data Flow Diagram (SA-4)
A system data flow diagram represents the flows and system functions that exchange data via specified interfaces. This includes data that flows in an out of the system. The diagram ensures that a clear representation of data flows exist which, in turn, provides a guide to creating complete functional connectivity between systems. The diagram also captures and describes the system functions. The completeness of the System Data Flow Diagram is important in the current state as future architectures rely on an adequate representation of current data flows.
Network Inventory (NI-2)
A network inventory serves to document the hardware and software of the enterprise networks. This includes data, voice, and video networks within the enterprise. The inventory typically includes a description, ID, IP Address, location, vendor, model information for each asset within the inventory.
Rack Elevation Diagram (NI-7)
The rack elevation diagram is more detailed than the network inventory as it provides a physical representation of an asset in a physical equipment rack. Representations include the front and rear view of each asset in the rack. The diagram is saved and updated as changes are made to the physical system. Changes may include rewiring of the cables supporting the device and relocation of the device within the rack or to another location.
