Deliverables

Requirements Document:

    • Use Cases written using the format attached.

    • Internal design including your choice of tools

    • User interface design with screen mockups

Be prepared to say why you chose each of the above.  Your team may be asked to present at code review next week.

Your use cases must be typed into a word processor and attached to a post in our Etudes Discussion.

Action Plan

1. Come up with questions for your interview with the user.
2. Conduct the interview with the user and take notes.
3. Confer with your team and convert your notes into a list of use cases.
4. Write these cases in complete, concise, correct sentences.
5. Think of cases where the user makes a mistake. These are Exception courses within use cases.
6. Research a few toolkits and frameworks.
7. Consider the expertise you have in your team members.
8. Decide which toolkits you will use.
9. Draw some mockups of the way your screens will look and act

Tips for Success

Use cases should define “what, not how” in other words, they should capture what the system will do from a user’s perspective without making specific commitments to how it will be done.

Write your use cases in correct English prose.

If you are not a good speller, use a spell checker.

If you need help writing proper English, visit the Language Arts Lab at Foothill College:

            http://www.foothill.edu/la/labla.php

You are encouraged to submit ONE draft for your manager's review. In order to receive feedback and incorporate it into your final submission, your draft must be submitted via etudes ng at least 24 hours before the due date.

Checklist for Submitting Your Work

Before you submit your use cases, check that you have attended to the following areas of the task:

• Did you refer to your interview notes while writing use cases?
• Did you extract at least 3 use cases from that interview?
• Did you document your use cases appropriately?
• Did you check the spelling in your document?