Data Technology Architecture baseline standards drawing
Title : Data Technology Architecture baseline
Purpose : Describe the enterprise data technology standards.
Owner : The Data Architecture team
Audiance : Data Architects, Application Developes.
Data technology architecture baseline
Purpose : Describe the enterprise data technology standards.
Owner : The Data Architecture team
Audiance : Data Architects, Application Developes.
Data technology architecture baseline
Business alignment
Information Exchange Matrix
Practical guide to federal enterprise architecture describe information exchange matrix as following :
D.9. Information Exchange Matrix
The Information Exchange Matrix documents the Information Exchange Requirements (IERs) for an EA. IERs express the relationships across three basic entities (activities, business nodes and their elements, and information flow) and focus on characteristics of the information exchange, such as performance and security. IERs identify who exchanges what information with whom, why the information is necessary, and in what manner. IERs identify the elements of information exchanged between nodes in support of a particular activity. Relevant attributes of the exchange are noted. The specific attributes included are dependent on the objectives of the specific architecture effort, but may include the type of information media (e.g., data, voice, and video), quality (e.g., frequency, timeliness, and security), and quantity (e.g., volume and speed).
The IEM can be produced at three levels:
• Conceptual Information Exchange Matrix—an essential work product
that describes the prominent, high-level information exchanges between prominent nodes
• Logical Information Exchange Matrix—a supporting work product that describes the design that details all categories and classes of information exchanges, but does not describe the physical implementation of them
• Physical Information Exchange Matrix— a supporting work product that describes the physical characteristics of the implementation of information exchanges.
Particular capabilities such as security level of communications may also be captured for each exchange. This work product emphasizes the logical and operational characteristics of the information, namely, what information is needed by whom, from whom, and when. Table 6 illustrates an example of an entry in the Logical IEM of the US Customs Service EA. In the table, AIS is the automated information system at the source and destination that sends and receives the information exchange and LISI is the Level of Information System Interoperability. LISI is scaled from zero for a totally manual interface to five for a fully electronic connection.
This drawing describe the internal and external data connectivity.
D.9. Information Exchange Matrix
The Information Exchange Matrix documents the Information Exchange Requirements (IERs) for an EA. IERs express the relationships across three basic entities (activities, business nodes and their elements, and information flow) and focus on characteristics of the information exchange, such as performance and security. IERs identify who exchanges what information with whom, why the information is necessary, and in what manner. IERs identify the elements of information exchanged between nodes in support of a particular activity. Relevant attributes of the exchange are noted. The specific attributes included are dependent on the objectives of the specific architecture effort, but may include the type of information media (e.g., data, voice, and video), quality (e.g., frequency, timeliness, and security), and quantity (e.g., volume and speed).
The IEM can be produced at three levels:
• Conceptual Information Exchange Matrix—an essential work product
that describes the prominent, high-level information exchanges between prominent nodes
• Logical Information Exchange Matrix—a supporting work product that describes the design that details all categories and classes of information exchanges, but does not describe the physical implementation of them
• Physical Information Exchange Matrix— a supporting work product that describes the physical characteristics of the implementation of information exchanges.
Particular capabilities such as security level of communications may also be captured for each exchange. This work product emphasizes the logical and operational characteristics of the information, namely, what information is needed by whom, from whom, and when. Table 6 illustrates an example of an entry in the Logical IEM of the US Customs Service EA. In the table, AIS is the automated information system at the source and destination that sends and receives the information exchange and LISI is the Level of Information System Interoperability. LISI is scaled from zero for a totally manual interface to five for a fully electronic connection.
This drawing describe the internal and external data connectivity.
Data securitry
This drawing describe the enterprise data security classification and requirements.
Data reuse
This drawing describe the data reuse patterns which consist of standard enterprise data and meta data standards and data models.
Data Resources
The enterprise data is created once and use by many. To share data and informion, the enterprse must organizat the information and assure the data quaility via data cleansing.
Information is the enterprise asset which must be preservere, maintaind and organize to become useful knowledge via data warehousing, data mining and knowledgement. Knowledge management does not just happen, it is the result of architecture and engineering effort.>
Information is the enterprise asset which must be preservere, maintaind and organize to become useful knowledge via data warehousing, data mining and knowledgement. Knowledge management does not just happen, it is the result of architecture and engineering effort.>
Data Description
The data landscpe decribe the information subect areas in the enterprise. It is a very high levle conceptul effort. The data subject area conresponds to the line of business and function.
The enterprsie data landscap example
The data description area from the FEAPMO DRM:
The enterprsie data landscap example
The data description area from the FEAPMO DRM: