| Design Project Resources |
|---|
| R1 Design Document Template |
| R1 Design Diary |
| R1 Requirements |
| R1 Design Patterns |
Design Project Release 1 (R1) will be divided into three phases.
At the start of phase 1, your instructor will provide you with several sets of requirements, each of which describes the features of a different software product. After you have read each of the requirements documents, your instructor will provide a link to a survey that you will use rank order the projects according to your preferences. Every effort will be made to assign you to one of your top 2 choices.
Once you have been assigned a specific set of project requirements, your first task will be to complete a domain model for the system that you will design.
Your instructor will also assign you one of the R1 Design Patterns. You will be responsible for researching the pattern outside of class and writing a GoF Pattern "Mini Design" that provides a detailed design applying your assigned pattern to a subsystem in your design project. Your instructor will ensure that the pattern to which you are assigned will be applicable to your specific project. Your instructor and Course Assistant are available to help you with any questions that you might have while working on this part of the project!
On the day that your pattern is scheduled, your instructor will present the pattern to the class. You (and any other student to which the same pattern was assigned) will then deliver a 5-minute GoF "Mini Design" presentation to the class.
In phase 2 of the project, you will be placed onto a team of other students that were assigned to the same design project. Your team will be responsible for documenting a consensus design that brings together your individual subsystem designs and fills in any "design holes" to create a complete design that meets all of the project requirements.
In the third and final phase of R1, your team will implement your consensus design. You will deliver a working version of the software product as well as a revised design document that includes any changes made to the design during implementation as well as a design diary describing the team's experience implementing the design.
Peer evaluations will be conducted after the end of phase 3.