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).

Difference between revisions of "Component Model Methodology"

From WHATWG Wiki
Jump to navigation Jump to search
Line 6: Line 6:
# Come with a design that satisfies all desired properties;
# Come with a design that satisfies all desired properties;
# Extrude [[Component_Model#Building_Blocks | building blocks]] out of the design;
# Extrude [[Component_Model#Building_Blocks | building blocks]] out of the design;
# Write [https://github.com/dglazkov/component-model specification] based on the building blocks;
# Write [https://github.com/dglazkov/component-model specification] draft(s) using the building blocks;
# Provide implementation feedback:
# Provide implementation feedback:
#* Provide experimental implementations and seek feedback from use case audiences;
#* Provide experimental implementations and seek feedback from use case audiences;

Revision as of 16:36, 23 August 2011

Here are the guidelines for understanding the problem of and developing specification for the Component Model.

Approach

  1. Capture requirements as use cases;
  2. Study use cases and extract a set of desired properties for these use cases;
  3. Come with a design that satisfies all desired properties;
  4. Extrude building blocks out of the design;
  5. Write specification draft(s) using the building blocks;
  6. Provide implementation feedback:
    • Provide experimental implementations and seek feedback from use case audiences;
    • Write a test suite;
  7. 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:
  • The specification:
    • is a complete set of requirements for all building blocks and corner cases, discovered during implementation;
  • The test suite:
    • provides coverage for each requirement in the specification.

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.