The raw ideas reported by all teams in the brainstorming sessions are found, one per line in the files found in the directory BrainstormingIdeas. Prune this list into a list of good ideas for features for the bi-directional word processor that you will be specifying. Combine these with other ideas that you may have heard in class and tutorial sessions. Throw in some new ideas that you have thought of. Finally, arrive at a first draft list of the features that you think the customer will want in the bi-directional word processor.
This list should be as complete as possible with respect to bi-directional word processing. It need not cover functionality that is basic to the word processor you are using as your basis (MS Notepad, MS Wordpad, MS Word, or Mac TextEdit) except as it is modified to deal with bi-directinal text.
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, the word processor will obey and do the use case. Some example use cases are:
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 ``current document direction'', does not cut the mustard because it does not explain what happens with the current document direction.
Hand in 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.