White papers
©
©
©
©
©
©
Principal template
©
  WHITE PAPERS
 
Principles Template
 
  Principle Name
  Description
  Rationale/Benefits
  Implications
  Counter argument
 
Give the principle a catchy name.
 
Statement of the principle.
 
Describe the reasoning behind the principle. Where applicable, provide trace ability to business or architectural objectives.
 
Identify implications such as actions that need to be undertaken, and constraints implied by the principle.
 
Describe the reasonable counter to this principle.
 
 
ARCHITECTURAL PRINCIPLES
 
Principles 
 
Architectural principles are statements of preferred architectural direction or practice.
  ........................................................................................................................................
 
 
Guidelines for Creating Principles  
 
 
In each principle, clearly state a chosen direction
Each principle should be stated in such a way that you will know if the architecture has the characteristics expressed by the principle
Each principle should have a counter-argument; that is, they should not be platitudes or general features that are desirable regardless of the system
Principles should be simply stated and understandable
Principles need to be rationalized, stating why the principle is preferred, drawing on business-related factors where possible
The implications of adopting the principle should also be identified
Base principles on experience (graphical history, literature, etc.) to repeat what worked and avoid what did not work
For each quality goal, consider whether there is a principle that will guide structuring decisions to achieve the goal
 
............................................................................................................................................
 
 
Uses of Principles 
 
 
Capture functional requirements: Use cases capture the functional requirements of the system. A representative set of use cases, covering the major goals of the users and important “corner cases” may be considered architecturally significant. Fine details of low-level use cases would not be.
help establish a context for architectural decisions by using business criteria to rationalize basic architectural choices, and
eliminate the need for evaluating endless alternatives in the modeling stages by agreeing up front on preferred directions.
 
  Disclaimer
 
     

 

Web Designing
SEO
Internet Marketing

Others

© 2007 Bean Architect
Contact us | Site Map | About us | Clients | White papers