Each team has to turn in a print-out of their requirements document, and has to give a 20-minute oral presentation on it in class. The presentation should use slides.
The requirements document contains the following sections:
1 Purpose and Scope
1.1 What is the overall goal?
1.2 Who are the stakeholders?
1.3 What is in scope, what is out of scope?
2 Glossary
(an alphabetic list of non-obvious terms that are used and definitions for them)
3 Functional Requirements
(This is a revised version of the MS1 Draft. Group use cases (and other specifications) by functionality, and give a priority to each.)
3.1 Use cases
3.2 File formats for input files and output files
3.3 Provided API
4 Technology
4.1 What technological requirements exist?
4.2 What other programs will this system interface with?
5 Other Requirements
5.1 Are there any unusual requirements on the development process?
5.2 Are there external deadlines that have to be met?
5.3 Nonfunctional requirements
5.4 Business rules, formulas, laws, standards, and similar constraints
6 Mockups of the User Interface
(include one mockup for each window/page — do not include mockups of small dialogs, and do not focus on
visual details, but rather on functionality of the windows/pages)
The requirements document must have a table of contents and numbered pages.
Make sure that your requirements fulfill the qualities for requirements such as consistency and completeness.
Note: All the projects in this class are different. If something in the milestone requirements does not work well for your project, please talk to the instructor, and we may arrange changes to the milestone requirements.