This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
project-wiki:syllabus:project_schedule [2023/08/16 11:23] mlhicks |
project-wiki:syllabus:project_schedule [2024/06/24 15:00] (current) mlhicks |
||
---|---|---|---|
Line 1: | Line 1: | ||
=====Project Schedule===== | =====Project Schedule===== | ||
- | < | + | < |
The overall project schedule is as follows: | The overall project schedule is as follows: | ||
Line 16: | Line 16: | ||
* A summary of the requirements validation activities and results that demonstrates the requirements have been validated by the market and/or sponsor. | * A summary of the requirements validation activities and results that demonstrates the requirements have been validated by the market and/or sponsor. | ||
- | The [[..design_reviews: | + | The [[..design_reviews: |
- | By 23 September 2022, your team will need to submit: | + | By the Opportunity Development Review, your team will need to submit: |
* A team Safety Training Sheet to the college office. | * A team Safety Training Sheet to the college office. | ||
Line 31: | Line 31: | ||
- | * //Concept Review//: The selected concept will be reviewed at the [[..design_reviews: | + | * //Concept Review//: The selected concept will be reviewed at the [[..design_reviews: |
- | * // | + | * // |
- | * //Fall Design Presentations//: | + | * //Fall Design Presentations//: |
- | * //The Fall Semester Design Report// will be due on Thursday, 8 December 2022. More information on the [[..design_reviews: | + | * //The Fall Semester Design Report// will be due as indicated in Learning Suite. More information on the [[..design_reviews: |
**Subsystem Engineering** (January and February): During the first six weeks of Winter semester, teams develop a complete system design, and obtain test results that show the subsystems independently meet their performance requirements. Teams also create evidence that the subsystems can work well together, ideally in the form of an assembled system. | **Subsystem Engineering** (January and February): During the first six weeks of Winter semester, teams develop a complete system design, and obtain test results that show the subsystems independently meet their performance requirements. Teams also create evidence that the subsystems can work well together, ideally in the form of an assembled system. | ||
Line 40: | Line 40: | ||
For projects that do not need subsystems defined, the test results listed above should be for the entire system. | For projects that do not need subsystems defined, the test results listed above should be for the entire system. | ||
- | * //The Winter Planning Review// will be held between | + | * //The Winter Planning Review// will be held between |
- | * //The Subsystem Engineering Review// reviews the complete system design and evaluates how well the product is expected to meet the target values of the requirements. Artifacts defining the system design and demonstrating that the subsystems meet their target values are reviewed during the [[..design_reviews: | + | * //The Subsystem Engineering Review// reviews the complete system design and evaluates how well the product is expected to meet the target values of the requirements. Artifacts defining the system design and demonstrating that the subsystems meet their target values are reviewed during the [[..design_reviews: |
**System Refinement** (March): Teams will revise the system, work out the remaining bugs, and thoroughly test overall system performance. A complete design package is prepared, and the Final Design Report is written. | **System Refinement** (March): Teams will revise the system, work out the remaining bugs, and thoroughly test overall system performance. A complete design package is prepared, and the Final Design Report is written. | ||
- | * //The System Refinement Review// evaluates the final design artifacts and the final design report. | + | * //The System Refinement Review// evaluates the final design artifacts and the final design report. |
- | * //Design Fair//: Teams will present their results and show off their designs, often by exhibiting prototypes, in a Design Fair that is open to the public. The [[..assignments: | + | * //Design Fair//: Teams will present their results and show off their designs, often by exhibiting prototypes, in a Design Fair that is open to the public. The [[..assignments: |
- | * //Final Design Presentations//: | + | * //Final Design Presentations//: |
- | * //The Final Design Report// will be due on Wednesday, 19 April 2023. More information on the [[..design_reviews: | + | * //The Final Design Report// will be due on the last day of class. More information on the [[..design_reviews: |