Data Architecture Principles

Plan before you build
Design with the user in mind
Integrate plan with envioronment
Structure and method should be reusable
Define the problem in the context in which it must be resolved
Analysing and defining an area must be done before any activity in that area
1. Incorrect assumptions can be made
2. Short term vision may handicp development
3. Inappropriate scoping my produced artificial boundaries
Well developed architectures evolve as the business evolves
Using architecture leads to foundational stability not rigidity

Resource summary

	Created by Chris LaVallin almost 12 years ago

	Copied by M Sirsi about 7 years ago