Enterprise Information Architect

Enterprise Information Architect

Enterprise architecture is the organizing logic for business processes and IT infrastructure reflecting the integration and standardization requirements of the company’s operating model. The operating model is the desired state of business process integration and business process standardization for delivering goods and services to customers. (Robertson, et al. 2006)
The EIA’s operational model is a simple statement of the integration and standardization requirements for the firm’s core processes (Nick, 2011). It is a means for connecting the Strategy with Implementation and Governance of Change programs to convey on the Strategy. The model involves Enterprise architects working together with stakeholders to build a holistic view of the company’s processes, information, information technology assets and strategy. This involves taking this knowledge and ensuring that the business and IT are in alignment. (Nick, 2011) The enterprise architect links the business mission, strategy, and processes of an organization to its IT strategy, and documents this using multiple architectural models or views that show how the current and future needs of an organization will be met in an efficient, sustainable, agile, and adaptable manner. (Robertson, et al. 2006)
Logical model describes the structure of some domain of information which consists of descriptions of tables, columns, object-oriented classes, and XML tags. In contrast, Physical model describes the physical means used to store data which are concerned with partitions, CPUs and tablespaces. (Nick, 2011)
The logical model includes entities (tables), attributes (columns/fields) and relationships (keys) while physical model Includes tables, columns, keys, data types, validation rules, database triggers, stored procedures, domains, and access constraints. (Nick, 2011)
Logical model uses business names for entities & attributes while on the other hand physical model uses more defined and less generic specific names for tables and columns, such as abbreviated column names, limited by the database management system (DBMS) and any company defined standards (Nick, 2011)
Logical model is independent of technology (platform, DBMS) and is normalized to fourth normal form while physical model includes primary keys and indices for fast data access and May be de-normalized to meet performance requirements based on the nature of the database. (Nick, 2011) If the nature of the database is Online Transaction Processing (OLTP) or Operational Data Store (ODS) it is usually not de-normalized. De-normalization is common in Data warehouses. (Robertson, et al. 2006)
Logical data is represented in the DIV-2 Viewpoint (DoDAF V2.0) and OV-7 View (DoDAF V1.5 while the physical data is represented in the DIV-3 Viewpoint (DoDAF V2.0), and SV-11 View (DoDAF V1.5) (Robertson, et al. 2006)
Both logical data model and physical data model are a mandatory requirement for an on-line transaction processing system. Logical data model is required to show the correct business rules that need to be applied to the information and Physical Model is the final representation of the data base structures that will be generated from the model (Robertson, et al. 2006). It contains the detailed specifications for the database design and, in a model driven environment; the modeling tool will generate the data definition language (DDL) that is used to create the database structure. (Robertson, et al. 2006)
Potential operational data requirements for the American Natural Soda Ash Corporation are proper research, planning, and implementation techniques to acquire information about the company assets, location, store, customers and to clearly depict the relationships between all the business entities. Data will be shared efficiently from the management to the customers. All this will be achieved by use of TOGAF.
.

References
Nick R. (2011) Software Systems Architecture: Working with Stakeholders Using Viewpoints and Perspectives. Oxford University Press. Oxford.
Robertson D.et al (2006) Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Harvard Business School Press. Harvard.

Type of paper Academic level Subject area
Number of pages Paper urgency Cost per page:
 Total:

Last Completed Projects

# topic title discipline academic level pages delivered
6
Writer's choice
Business
University
2
1 hour 32 min
7
Wise Approach to
Philosophy
College
2
2 hours 19 min
8
1980's and 1990
History
College
3
2 hours 20 min
9
pick the best topic
Finance
School
2
2 hours 27 min
10
finance for leisure
Finance
University
12
2 hours 36 min