What are major functional and non-functional requirements?
What is anticipated as an acceptance test?
What are your target implementation platforms?
Consider using a hierarchical organization: first a one paragraph overview
emphasizing goals, then more details in the following paragraphs.
Remember that the customer is going to read this. The customer's boss
might read it too. Be clear and to-the-point. Avoid jargon. Avoid hype.
Double-check spelling and grammar.
Note: you will probably revise your Assignment 2 introduction but
be sure you have the new points added if they were not already
there.
Use Cases.
Identify classes of users and their characteristics.
List features of the system with brief description. Give unique name
to each feature so you can refer to it later.
Describe use cases to specify how and why users accomplish specific
goals or tasks with those features.
Break down each use case into a sequence of steps. Descibe each step
with a few English sentences.
Make sure that it is clear what the system will do and will not do.
Consider listing "anti-features" (things that the system will
not do).
Overall, there should be about 12 to 15 diagrams. Not all use cases
will need diagrams.
Include one or more use case diagrams to show the relationships between
the users and use cases, and among the use cases themselves.
Deliverables. What are you going to give to the customer? (include
the items that apply)
Software: Executables? In what format/media?
Dococumentation: User's manual? On-line help? Web site? What will be
in these documents?
Development artifacts: Source code? Design docs?Test cases?
Support: Warranty? Rights to bug fixes? Rights to request improvement?
Delivery Platform. What hardware/software/database/etc. will
be needed to run the system? This is usually specified by your client.
Development Platform. Whathardware/software/database/etc.
will you need to develop the system? This is usually decided by you.