Difference between revisions of "Architecture Tactics"
From Suhrid.net Wiki
Jump to navigationJump to search (→Intro) |
|||
| Line 13: | Line 13: | ||
= Availability Tactics = | = Availability Tactics = | ||
| + | |||
| + | * All approaches to maintaining availability involve some type of redundancy, some type of health monitoring and some type of recovery when a failure is detected. | ||
| + | * Availability tactics involve- Fault detection, fault recovery and fault prevention. | ||
Revision as of 05:10, 28 March 2012
Intro
- How can we design an architecture that will achieve the desired quality attributes ?
- Sources of architecture
- Theft: From previous systems, literature
- Method: Systematic and conscious, derived from requirements via transformations and heuristics.
- Intuition: Ability to conceive without conscious reasoning. Increased reliance on intuition increases the risk.
- Ratio of usage of above three methods varies according to architects experience and novelty.
- What is a tactic ? - A tactic is a design decision that influences the control of a quality attribute response.
- A collection of tactics is an architectural strategy.
- Each tactic is a design option for the architect.
Availability Tactics
- All approaches to maintaining availability involve some type of redundancy, some type of health monitoring and some type of recovery when a failure is detected.
- Availability tactics involve- Fault detection, fault recovery and fault prevention.
