Requirements Document for Final Project

Because during the summer we have so little time, you will develop a relatively light, non-standard requirements document consisting of just use cases and associated wireframes.

Section 1 of the document, a description:

A narrative description of the purpose of your web site. Include a description of your web site's audience(s).

Section 2, use cases:

Develop a set of use cases for each type of user that your site supports. For a good description of how to write a use case, see https://www.usability.gov/how-to-and-tools/methods/use-cases.html. You will create "heavyweight" use cases.

Example types of users: shoppers, store managers, game players, etc.

Example use cases:

• shopper browsing for, then purchasing items. [Alternative flow: user places item in shopping cart, but then disconnects. Alternative flow: user rejoins a session with items already in shopping cart.]
• shopper reviewing previouis purchases, then repurchasing a previous purchase
• shopper updating shopping information, then making a purchase
• manager adding a new item to inventory
• manager deleting an item from inventory
• manager identifying which inventory items need to be replenished
• game player views currently active games and joins a game, completes the game. [Alternative flow: opponent disconnects before game completion.]
• game player hosts a game, waits for other players to join, completes the game.

Section 3, UML use case diagrams:

For each of your use cases create a UML use-case diagram. This will help you identify subcomponents of your system. If you are unfamiliar with UML use-case diagrams, there is a good explanation at http://www.uml-diagrams.org/use-case-diagrams.html. One of the examples there is for online shopping.

Section 4, wireframes:

Next, for each of your use cases develop a wireframe of the web page for each major step in the use case. ("Major" in the sense that the page's appearnce changes significantly.) The wireframes can be hand-drawn, or use Powerpoint, or a graphing program. There's a nice overview of wireframes at https://www.infoq.com/articles/wireframes-start-development-projects.

Section 5, timeline:

Provide a timeline for the remaining weeks of the semester. The timeline should include at least two "deadlines" for each week. Clearly specify which of your teammates is responsible for completing which work by each deadline. Use a Gannt chart to clarify the responsbilities and deadlines.

Additional Requirements for Projects:

• User registration must involve e-mail to verify registration.
• Your web site must be populated with enough items (i.e., products to buy, or games to play) that you can provide a representive demonstration of a "real life" use of your system. For example, if there are only four items in an online store, browsing will not be interesting, nor would a search function be particularly useful.

Extra credit:

Integrate PayPal into your system. The developer.paypal.com site provides lots of documentation for how to do this, including integration of their own shopping cart technology (if you want to use it) and use of the PayPal Sandbox.