A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.
To request an account, ask an autoconfirmed user on Chat (such as one of these permanent autoconfirmed members).
Component Model Methodology: Difference between revisions
Jump to navigation
Jump to search
(Created page with 'Here are the guidelines for understanding the problem of and developing specification for the Component Model =Approach== # Capture requirements as [[Compo...') |
No edit summary |
||
| Line 1: | Line 1: | ||
Here are the guidelines for understanding the problem of and developing specification for the [[Component_Model | Component Model]] | Here are the guidelines for understanding the problem of and developing specification for the [[Component_Model | Component Model]]. | ||
=Approach | =Approach= | ||
# Capture requirements as [[Component_Model_Use_Cases | use cases]]; | # Capture requirements as [[Component_Model_Use_Cases | use cases]]; | ||
# Study use cases and extract a set of [[Component_Model#Properties | desired properties]] for these use cases; | # Study use cases and extract a set of [[Component_Model#Properties | desired properties]] for these use cases; | ||
| Line 8: | Line 8: | ||
# Iterate until [[#Success_Criteria | success criteria]] is reached. | # Iterate until [[#Success_Criteria | success criteria]] is reached. | ||
=Success criteria | =Success criteria= | ||
* The use cases: | * The use cases: | ||
** reasonably cover a set of component model needs on the Web. | ** reasonably cover a set of component model needs on the Web. | ||
| Line 18: | Line 18: | ||
** follow the component model [[#Design_Priniciples | design principles]]. | ** follow the component model [[#Design_Priniciples | design principles]]. | ||
=Design Principles | =Design Principles= | ||
* '''Reuse existing mechanisms''' as much as possible, gently extending them if necessary; | * '''Reuse existing mechanisms''' as much as possible, gently extending them if necessary; | ||
* Study popular patterns in existing Web frameworks and '''pave the cowpaths''' when appropriate; | * Study popular patterns in existing Web frameworks and '''pave the cowpaths''' when appropriate; | ||
* Encourage '''each building block to stand on its own''' merits. | * Encourage '''each building block to stand on its own''' merits. | ||
Revision as of 16:20, 23 August 2011
Here are the guidelines for understanding the problem of and developing specification for the Component Model.
Approach
- Capture requirements as use cases;
- Study use cases and extract a set of desired properties for these use cases;
- Come with a design that satisfies all desired properties;
- Extrude building blocks out of the design;
- Iterate until success criteria is reached.
Success criteria
- The use cases:
- reasonably cover a set of component model needs on the Web.
- The properties:
- completely describe the set of use cases;
- are orthogonal to each other.
- The building blocks:
- satisfy all desired properties;
- follow the component model design principles.
Design Principles
- Reuse existing mechanisms as much as possible, gently extending them if necessary;
- Study popular patterns in existing Web frameworks and pave the cowpaths when appropriate;
- Encourage each building block to stand on its own merits.