Enterprise Application SystemsIntegration- Assessment Documentation - Research Paper Example

It is the intent of this document to align the business and system requirements that get articulated during the Enterprise Application Service Integration (EASI) design process with business requirements for availability, performance and manageability. Non-technical readers should be able to understand the concepts, expectations and limitations of the system(s) outlined in this document.This document contains anticipated physical inventory information, application details and other critical aspects related to the physical and logical components that make up this specific system.

Also included are key ancillary systems that this system will utilize and the interoperability between these systems. Our goal in this process is to capture realistic estimates for all required infrastructure (physical/virtual) and information technology management requirements to adequately deliver and operate this system over a 5-7 year operational period.Information Technology documentation artifacts may come through standard Enterprise Application ServicesIntegration processes or directly from other sources such as Telecom & Network Engineering.

In many cases, business/system requirements are gathered through vendor engagements that will be utilized in place of standard Business Requirement Documentation (BRD). Regardless of the initial process, Enterprise Application ServicesIntegration (EASI) processes will uniformly document both proposed system requirements and resulting technical design documents. When finalized, these documents will receive a design document number and begin the configuration management process managed by the systems administrators of the system.

Design changes will be recorded through the use of design configuration or change processes. This process will included both design changes and general maintenance tasks outlined in the EASI design document. For changes outside the standard maintenance, scope such as application patching, approval will need to be granted by the system administrator and enterprise developer/architect.