IT Architecture Standards Principles (Draft)

Yale ITS standards should be developed in a manner consistent with these guiding principles.

Name	Affordable
Statement	Standards should be attainable within available resources
Rationale	Standards which cost too much to implement or adopt will never be adopted.
Implications	This gives weight to or is related to another possible enterprise principle, not yet agreed, that “cost containment is an overriding priority for managing the IT infrastructure." In some cases, Standards are due to regulatory requirements and cost may not be a limitation that Yale has control over.

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Attainable & Compelling
Statement	Standards should be realistic, while at the same time they should inspire solutions which are ever increasing in quality.
Rationale	Usually it is better to use currently attainable standards than ideal standards because attainable standards may encourage/motivate adoption to a greater degree. Over time, as standards are adopted they can be moved incrementally toward an ideal through the principle of "Assessed & Updated."
Implications	This implies a commitment to a mature, ongoing process of renewal and incremental movement towards ideal standards. See also "Standards are Assessed & Updated."

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Published & Communicated
Statement	Standards should be published and made known to all concerned.
Rationale	You can only effect standards adoption if standards are readily available to and understood by employees involved in their delivery, and if they are clear and easy to understand. (See "Standards are Understandable.")
Implications

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Consistent
Statement	Standards must be created with other standards in mind. A hard dependency does not need to be created, but Standards should not contravene other standards. This is especially true where the standards are external standards such as regulations, policies, etc.
Rationale
Implications

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Consultative
Statement	Standards should be developed in consultation/collaboration with those who deliver the service and, where possible, representatives of the customers who avail of them (e.g. focus groups)
Rationale	Developing standards in conjunction with the consumers of the standards will drive adoption and will be improved by the insight of the consumers.
Implications	A successful collaboration or partnership also needs to be approached systematically. There needs to be a basic agreement about the purpose of the collaboration, what the organization will try to achieve together, mutual expectations and the principles or values by which the partners will operate.

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Maintained
Statement	Standards should be reviewed regularly and adjusted to reflect new circumstances.
Rationale	Continuous improvement will allow adoption of higher and higher standards
Implications	A continuous improvement process will need to be established. Regularly review helps to insure that standards keep pace with regulations, technology, and industry best practices. Review ensures that Standards remain are consistent and effective. Reviewing standards is especially important for high-risk or highly regulated activities or data.

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Measurable
Statement	Performance achievements should be measured against the standards, as well as customer satisfaction with the service provided. The performance measures used should be comparable over time and tracked to demonstrate improvements; standards should be written in terms of specific measures that will be used to appraise performance.
Rationale	Standards, especially those intended to improve or affect performance, should be objective, measurable, realistic, and stated clearly in writing (or otherwise recorded).
Implications	Not all standards will have a measurable component. However, we should strive to determine if and where standards can be measured. The following questions may help determine specific measures. For each measure, ask: How could [quality, quantity, timeliness, and/or cost effectiveness] be measured? Is there some number or percent that could be tracked?

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Principled Decision Making
Statement	Information systems principles apply throughout Information Technology Services (ITS) and take precedence over other considerations when information system decisions are made.
Rationale	Principles generally provide guidance and direction for the use and evolution of information systems or business processes relative to the creation, deployment and operation of information systems. Deviating from principles may result in unnecessary and avoidable long-term cost and risk. The only way we can provide a recognized, consistent and measurable level of operations is if all units within the ITS abide by the same set of principles when making decisions.
Implications	Without principles, short-term considerations, convenient exceptions and inconsistencies will rapidly undermine the management of information systems. Information system initiatives will not begin until they are examined for compliance with the principles. Principles are inter-related and need to be applied as a cohesive set. Initiatives that conflict with the principles require the explicit approval of the Technical Architecture Committee through its designated Architectural Governance process.

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.

Name	Understandable
Statement	Standards should be responsive. They should be meaningful and understandable to the individuals delivering the service, expressed in terms to which they can relate and refer to aspects of the service customers find important. Typically, standards should cover elements of service that are visible and measurable.
Rationale	To be effective and therefore adopted, standards and standards documentation must capture the audience's attention and be easy to understand
Implications	Use ‘plain language.’ Write standards using words and language that are familiar to the audience. Test standards to determine how well employees understand and receive them. Fits well with consultation. A standard should list who its intended audience is.

Note: Learn more about what principles are and how to make them by viewing the TOGAF 9.x standard.