Using the information in the WUIM Project Vision Document, what you have learned about it for your Deliverable 1, what you have learned about it for your Deliverable 2, any updates to the vision document, and any good ideas that come to your minds, develop a list of proposed features for WUIM.
Describe each feature as a use case, i.e., give a simple imperative sentence as if when the user says the imperative sentence as a command, WUIM will obey and do the use case. From this list of features-as-use-cases, you should be able to identify WUIM use cases, as described in the lecture on Scenarios and Use Cases.
The hardest part of this exericise is coming up with a concise, consistent, and complete set of use cases that allow the user to do what he or she needs to without having too many different ways of doing any one thing.
You do not have to develop any scenarios yet. However, your imperative sentences must be complete enough that the customer can understand what the feature does. Thus, a phrase, such as ``the WatIam user ID'', does not cut the mustard because it does not explain what happens with the WatIam user ID.
Build a use case diagram that shows the system boundary, all actors, all use cases and that associates each use case with each actor that may do it. Use the notation of the use case diagram on page 22 of the slides for Classes & Concepts or on the diagram of page 61 of the slides for Scenarios & Use Cases.
You will need to submit both a hard copy AND and an electronic copy of this deliverable: