CSCI 375 Team project: full presentation I and project requirements

Deadline

These deliverables are due by the start of the lecture on March 8th.

Document name

The document must be named Requirements.odt and must be located in the Documents directory of your team git repository.

Document overview

Provide a short (2-3 paragraph) outline of the content of this document.

Project update

Provide an update on the state of the project, clearly identifying any changes to the planned product/features/interface.

Project plan update

Provide an update on the project plan, noting any key changes (new/expanded tasks, task assignments, task completions) and an updated version of the software development plan.

Risk update

Provide an update on the risk management plan, noting any key changes (risks added/removed, updates on risk probabilities, etc).

Project requirements

Provide a full description of your product requirements, complete with at least the following:

• A product summary, covering the product features, audience, business needs met, and general interface.
• Provide a full description of all interface requirements for the product.
• Provide a full description of all functional requirements for the product.
• Provide a full description of all non-functional requirements for the product.
• Provide a comprehensive set of use cases and scenarios.
• Provide a description of the feature set the team plans to implement in time for the final presentations on April 10th.

Preliminary acceptance testing plan

Provide an outline on the planned approach to test the final product, complete with at least the following:

• A general outline of the plan.
• A preliminary timeline for testing, covering the development and set up of the test environment and the tests themselves, the application of testing, time for bug fixes, and sufficient time for subsequent re-testing.
• The intended testing environment, tools, and processes to be followed.
• The feature sets/requirements to be tested, and preliminary ideas on how to test those requirements are met.

Team presentation

In the lecture session of March 8th, each team will provide a 20-25 minute presentation summarizing the information in the document described above. This presentation will be evaluated by the audience members, and feedback on both the product requrements and the presentation will subsequently be provided to the project team.