This project is read-only.
1
Vote

Develop Use Cases for ReBook

description

We're going to begin identifying the feature-set and the UI requirements by writing some use cases detailing the types of users we envision using our product and the specific things they will need to accomplish their task(s) in a trivial manner.

I've started a discussion thread with 4 base use cases which I envisioned. Read over those and edit the current cases to reflect what you think our user classes need and create new use cases as you deem appropriate.

This will help us define the back-end requirements, the front-end requirements, as well as helping us identify the value-added propositions ReBook will bring to everyone involved - content owners as well as end users.

comments