Requirements

TODO: Write the requirements as a numbered list, based on these sources of information:

• class discussion of the assignment
• the example Vision Statement
• the example Software Development Plan

Many projects write functional requirements as User Stories or Use Cases. For this project, just write them as a list.

Characteristics of good requirements are:

• Clear
• Consistent
• Complete
• Feasible
• Unambiguous
• Singular (one requirement is one thing)
• Testable
• Written in complete sentences with grammatically correct English!

"Clear" and "unambiguous" imply that requirements should be precise.

Things to avoid:

• Avoid writing implementation details as requirements.
• Don't invent your own requirements, unless you are the customer.