Rational & implications

Rational & Implications Affiliation: Principle: Architectures must be appropriately scoped, planned, and defined based on the intended use of the architecture
Rationale: Those picked for the job should be qualified and have specific knowledge of the work they will perform and not just general knowledge.
Implications: Efficiency and specificity are the general rules to succeed in the architecture field and for any business.
2. Principle: Architectures must be compliant with the law as expressed in legislative mandates, executive orders, Federal regulations, and other Federal guidelines.
Rationale: Any changes in policies, rules or laws have to be adhered to as they are the basis of information distribution.
Implications: The changes in laws or rules may lead to changes in other areas of the business and architecture as well. Education of the existing laws and policy needs to be carried out regularly and updated.
3. Principle: Architectures facilitate change.
Rationale: Architectures are the main change agents and they are the beginners of any changes in an organization. It ensures change is uniform and consistent.
Implications: There will be no conflict in the change management process. The roles of each personnel in the organization will be well defined once this change facilitation is in progress hence reducing redundancy.
4. Principle: Enterprise architectures must reflect the Agency’s strategic plan.
Rationale: Their work must be in sync with the plans of the organization as they are on the forefront of any changes in the organization.
Implications: Coordination and cooperation of the architectures will lead the success of the strategic plans and their failure means failure of the plan in general. Faith is therefore put on the architectures and their effective work.
5. Principle: Architectures continuously change and require transition.
Rationale: Their work is not static and hence keeps on changing due to the constant changes in information technology. They therefore should also be on their toes to keep up with the changes.
Implication: Changes in information technology and other business issues require the facilitators of that change to keep on changing too if the organization is to continue being relevant in their work and keep up with the competition.
6. Principle: Target architectures should project no more than 3 to 5 years into the future.
Rationale: Long-term projections in this changing field will only waste time and resources since changes in this information technology field are constant and require only short-term plans.
Implications: The future is unknown based on previous knowledge of how changes keep taking place. Short-term workable goals and plans are the way to go if the plans are to be deemed useful and not redundant and backwards. Short-term projections keep the resources intact and help to uphold the currents laws and policies.
7. Principle: Architectures provide standardized business processes and common operating environments (COEs).
Rationale: They are the driving wheels behind the organization’s successes and change facilitation and hence the best to be on the forefront of ensuring standard business processes and also ensure the environment the organization is operating in is common.
Implications: Policies and laws are tied directly to this principle and so its correct implementation will save resources and time. Consolidation of such important duties to one sector reduces issues of data loss or mismanagement since the responsibility lies in the chosen few.
8. Principle: Architecture products are only as good as the data collected from subject matter experts and domain owners.
Rationale: Usefulness of data depends on the credibility and reliability of the data collection process and those who participated in the process. The same is true when it comes to products by the architectures. Their reliability and credibility are dependent on the process and the people involved.
Implications: Flaws in the process renders the products useless and hence a waste of resources and time. Measures to ensure credibility and reliability of the products from the process to the people involved are adamant for the success of the organization or business as a whole.
9. Principle: Architectures minimize the burden of data collection, streamline data storage, and enhance data access.
Rationale: They specialize in producing the best by use of as minimally as possible technicalities that cannot be understood by majority. They simplify the work and make it more accessible to the majority and hence save on time and resources.
Implications: Standardization of the data will be ensured and so will data security since the workload and trivialities are all compressed in a way to facilitate changes and reduce data loss which comes about when the burden of data is excess. Minimization also ensures transparency of the whole process in the organization.
10. Principle: Target architectures should be used to control the growth of technical diversity.
Rationale: Technical diversity solely depends on specific qualifications, measures and steps to be taken and which in turn rely heavily on specific dockets and individuals with that specific knowledge.
Implications: Generalization of duties and especially where diversity is involved should be discouraged. Specific policies and laws should be enforced in relation to technical diversity as that is what makes the business unique from all the others dealing with information technology and management.
References
The Open Group. (2009). TOGAF Version 9. Zaltbommel: Van Haren Publishing.