User stories

Functional requirements

  1. As a Developer, I can register a new Component , so that I can make it available to Apps.

  2. As a Developer, I can register a new Shape , so that I can make it available to Apps.

  3. As a App, I can query Components based on their Metadata, so I can get a list suitable Components.

  4. As a App, I can give my preference to one of the suitable Components , so that I

  5. As a App, I can download a Shape  which corresponds to the preferred Component , so that I

  6. As a App, I can validate an instance of a Shape , so I can be certain that the Component  can be rendered.

  7. As a App, I can download a specific Component from a Repository, so I can use it to Render data.

  8. As a App, I can render a Component based on an instance of a Shape , so that I can show data in the user interface.

  9. As a Repository, I can query Components in other Repositories  based on their Metadata , so that I can serve Components I don’t know yet.

  10. As a System Administrator, I can configure other Repositories which can be queried, so that I can choose which Repositories I trust.

Out of scope

  1. Support downloading at build time.

  2. Support for non-web applications.

  3. Versioning