Enterprise Architecture Planning (EAP)

Paper Summary:

This paper uses the principles of enterprise architecture planning (EAP), to analyze what went wrong in the application of a data warehousing system for the company SPFIS and determines what recommendations can be made regarding future projects. It examines how the initial system was implemented through a whim of the CEO lacking clear definition and identifiable milestones. It looks at the four stages of EAP, developing a framework for the plan, performing initial migration, performing major application migration and the post-migration stage and uses them to analyzes SPFIS's shortcomings.

From the Paper:

"In many cases, significant IS programs lack an executive sponsor and the IS staff struggles to gain support for their project at the highest levels of the organization. This was not the case at SPFIS. Indeed, there was considerable support for the data warehousing project from the CEO, but the CEO failed to appreciate exactly what a data warehouse could and could not do for his organization. This "blind" approach to implementing a data warehouse imposed unrealistic deadlines and resource limits on the IS staff, and ensured that users would not be part of the solution (users were left believing that the data warehouse would be forced on them even though they did not understand its benefits)."

More papers on Enterprise Architecture Planning (EAP):

• Case Study # 26147 : "Enterprise Architecture Planning"
• Analytical Essay # 126091 : "Enterprise Resource Planning"
• Analytical Essay # 119006 : "Enterprise Resource Planning (ERP)"

APA Citation:

MLA Citation: