In the schedule, we are following a slightly different approach to defining the development phases. Each week has its own phase, and the phase base number is changed after a deliverable. The reason for that is since each deliverable is focused on a specific delivery and we need work for future deliverables to be started beforehand, we needed a different way to specify the progress of the project. With this, the mapping between deliverables and phases, together with the expected dates, is the following:
D1 [Mechanical Design]: Phases 1 and 1.5 (09/14 - 09/27)
D2 [Mechanical Project + Electronic Design]: Phase 2 (09/28 - 10/04)
D3 [Electronic Project + Software Design]: Phases 3 and 3.5 (10/05 - 10/18)
D4 [Software Project]: Phase 4 (10/19 - 10/25)
D5 [Mechanics, Hardware and Software Integration]: Phases 5 and 5.5 (10/26 - 11/08)
D6 [Overall Integration and Functional Tests]: Phase 6 (11/09 - 11/15)
TR [Full Technical Report + Video]: Phase 7 (11/16 - 11/23)
Additionally, it’s expected that each week starts on Thursday and ends on Wednesday (weekday of the Integration Workshop 3 class and the day before the next one).
As in the requirements, some tasks are marked as Optional or Time Constraints, which means they are either optional (will only be done if there’s enough time to do so, but are not required) or were removed to follow the hours/week limit for the subject. The buffer time for each task is 30%. The time constraint requirements were chosen so the phase total duration without the optional tasks is around 40h.