CMPUT 301

Software Engineering

Project Part 2

Project Part 2 -- Preparation

Learning Objectives

Overview

The project description outlines the problem and a set of needs. The entire project has several deliverables. Subsequent deliverables may be further refinements of earlier ones, and should address any TA feedback or concerns. This project part focuses on some initial preparations.

Deliverables

The following components are required for this project part.

1. Product Backlog:

Form the initial partial user stories into a backlog of the product's requirements. For each user story, estimate its size in story points, and denote its risk level (i.e., low, medium, or high). These requirements will likely evolve and should be maintained up-to-date throughout the project. Make sure they are numbered for easy reference. Note which stories will be released for the half-way checkpoint.

2. User Interface Mockups and Storyboard Sequences:

Diagram the layout of your main user interface and major dialogs, with comments describing the important elements. Also, diagram storyboard sequences of using your application, with transitions between different states of the user interface, caused by the user manipulating the controls or providing input. Within the diagrams, reference the relevant requirements. Convincingly show all the requirements are covered.

3. Object-Oriented Analysis:

Document your initial object-oriented analysis using CRC cards, focusing on the most important anticipated classes, their responsibilities, and collaborators.

4. Tool use:

Regular and consistent use of GitHub by all team members to share files for the project deliverables, to effectively track issues, and to manage tasks.

Hints

Ask questions about the requirements. Your interpretation of a need or task may be more complex or sophisticated than what is actually desired. Involve the TA for your team to gain feedback on your deliverables.

For neatness and readability, diagrams must be drawn well using a computer tool at a suitably legible scale for insertion into your document(s). Submitted diagram(s) must be embedded as image(s) in your team wiki, not linked externally.

You should look ahead to the future project parts and their deliverables to know what is coming. Do not wait until this part's deliverables are due before working on the next part.

Very likely, the requirements and user interface design will need to evolve during the project. You should keep this information up-to-date so that your team members are properly coordinated.

Submission Procedure

Use GitHub. Your team repo must be self-contained, i.e., not link to external content that might change.

Individual Task and Peer Review Form

After the due date, each member must complete an assessment form to describe his or her individual contribution to the project for this stage, and to review the performance of the other members.

Marking

No part marks, no extra marks. No half marks.