INFRASTRUCTUREARCHITECTUREPRINCIPLES基础设施架构原则.docVIP

INFRASTRUCTURE ARCHITECTURE PRINCIPLES IP1. The infrastructures ability to adapt to user needs is paramount. Rationale: Department requirements are both unique and dynamic. The infrastructure should support an environment that allows applications to start small, quickly, and inexpensively. An adaptable infrastructure provides the capability to add onto the current investment with minimum inconvenience to the user. Applications should be able to expand or contract in concert with the demand for services. The infrastructure should support applications that are flexible and portable. Implications: Adaptability and life expectancy are major criteria in setting infrastructure standards and selecting components. Solutions which demonstrate a growth path and support portability are more likely to be maintained or supported in the future. IP2. Interoperability is a goal of infrastructure, data management, and applications development. Rationale: Interoperability enhances the ability to share data and other resources which is critical to the effective delivery of services by the State. Interoperability fosters better inter-department cooperation by eliminating many of the barriers which make inter-department efforts difficult. By promoting and providing interoperable components, scarce training and support resources can be directed in the most cost-effective manner. A consistent user view of the infrastructure leads to productivity gains. Implications: A department may incur higher initial costs to achieve statewide compatibility. This may delay upgrade for some Departments. However, this will position the department to realize future cost savings. Departments may need budgeting and staffing support to migrate to an infrastructure that supports interoperability. State management needs to be educated as to the benefits of a common infrastructure so they will support the strategic plan for such an infrastructure. IP3. The States infrastructure is bas