Dispatch /

On Principles of Applications

14 Oct 2012

As discussed previously, principles are high level statements of the fundamental values that guide business and technology decision-making and activities and are the foundation for architecture, standards, and policy development. Principles are stable enough to withstand technological and process changes but timely enough to maintain a clear relevancy with markets, policy, program, and management changes. Principles consist of the principle statement, rationale, and implications. Though the wording for principles should remain consistent, the rational and implications will evolve over time, as an organization responds to factors such as the current IT environment, internal initiatives, external forces and markets, and changes in mission, vision, and strategic plan. In my prior role as an Enterprise Architect, I used the following Principles for the foundation of the Enterprise Applications. Even with the changes in the industry since I last wrote these  - public, private and hybrid cloud computing, dev-ops, etc - these principles have been steadfast. Though, perhaps I could spend some time and update them...

Application Integration

Enterprise applications will include known, published mechanisms for integration.

Standards Compliance

Developers of enterprise applications will comply with all enterprise  standards in effect at the time. This principle applies to internal or outsourced development and to COTS software, although to a lesser extent.

Application Ownership

Applications will have an identified business owner and technical owner or lead.

Application Documentation

Enterprise applications will be documented, both internally and externally.

Business Alignment

Applications will have a stated business purpose. If there are multiple business purposes, they will be closely related.

Decision Analysis for Acquisition

A decision to custom build can be made only after an analysis that considers other sources such as COTS and Open Source alternatives.

Application Scope Definition

Enterprise Applications will meet broad needs. The requirements and design will be published prior to development, and all business units will have the opportunity to comment.

Software Configuration and Change Management (SCCM)

The Software Configuration and Change Management (SCCM) process will be documented and all parties will adhere to it.

Systems Development Lifecycle (SDLC)

The systems development lifecycle will be documented and repeatable.

Reusability of Components

Applications should be assembled, in part, from reusable components or services.

Twitter Facebook