Week	Date	Description	Deliverables / Evaluations	Detailed deliverables
1	mar. 7^th	Overall introduction and course overview. The PMBOK method, examples of successfull projects. Teams composition. Open brainstorm about project ideas.
2	mar. 14^th	Time management strategies. Comments about teams' project proposals (plans A, B, and C) previously provided as short videos
3	mar. 21^st	Presentation and discussion about 3 possible project proposals (plans A, B, and C) for each team	Live presentation of project proposals (plans A, B, and C) made available in the blog	A blog site freely accessible in the internet should be created. Such a blog shall follow the template of previous projects. At the inception, the blog shall have, at least, full information about the team, project, requirements, schedule, budget and risk analysis. The blog will be dynamic and weekly updated with all the information and documents generated along the development of the project. Until the end of semester, the blog will be used to present the weekly deliverables. Teams should present at least 3 possible project ideas that comprise mechanical, electronic and software development and integration. Projects must be original, not replay of previous projects. The extension and complexity of the projects should be compatible with the number of students in the team and the time available for development.
4	mar. 28^th	*Seminar for discussing project proposals and presentation of enhanced* versions of plans A and B. Selection of the project proposal. Choice of the best suitable project for developping during the semester.**	Enhanced project proposals (plans A and B)	After rebuttal from the professors, teams must choose 2 out of the 3 initial proposals. Teams should enhance both plans with more details and specifications.
5	apr. 4th	Project development: detailed requirements Interview with the expert #1	Funcional and non-functional requirements for hardware and software. Platforms, budget, detailed tasks and schedule. Risks management analysis	Presentation of the funcional and non-functional requirements for hardware and software platforms, budget, initial definition of tasks and schedule. In-depth analysis of the risk management plan together with schedule and requirements
6	apr. 11^th	Project development and monitoring	PC1: Project Charter	The Project Charter must contain detailed information about the motivations and objective of the project, as well as the funcional and non-functional requirements (and counter-requirements, if necessary); hardware and software platforms, budget, full definition of tasks and detailed schedule. Both, budget and schedule must be formatted following the rules predefined by the professors.
7	apr. 18^th	Project development and monitoring	PC2: Project Charter	The Project Charter must contain detailed information about the motivations and objective of the project, as well as the funcional and non-functional requirements (and counter-requirements, if necessary); hardware and software platforms, budget, full definition of tasks and detailed schedule. Both, budget and schedule must be formatted following the rules predefined by the professors.
8	apr. 25^th	Project development and monitoring (All Teams)	D1: Mechanical design	Full mechanical design (including all diagrams and technical drawings).
9	may. 2^nd	Project development and monitoring (All Teams)	D2: Full Mechanical project. Electronic design	Complete mechanical project, including drawing of all parts, printed parts and their mounting. Electronic design including schematics and test of components.
10	may. 9^th	Project development and monitoring (All Teams)	D3: Full electronic project. Software design	Finished mechanical structure. Electronic hardware design including schematics, PCB and state-machine. Functional tests of sensors & actuators are necessary. Software design with UML diagrams (use-case, sequence, activity, classes, deployment, entity-relationship), for firmware, frontend and backend, and mobile app.
11	may. 16^th	Project development and monitoring (All Teams) Interview with the expert #2	D4: Software project	All electronic development should be ready, partially integrated with the firmware and mechanics. Complete software design of firmware, database, mobile app, webserver (front/back), with all relevant UML diagrams must be presented. Tests of modules and PoCs are espected.
12	may. 23^rd	Project development and monitoring (All Teams)	D5: Mechanics, hardware and software integration	Demonstration of the integration between the mechanical parts with hardware/firmware and software elements by means of unit tests.
13	may. 30^th	HOLIDAY: Corpus Christi
14	jun. 6^th	Project development and monitoring (All Teams)	D6: Overall integration and functional tests	Complete solution demonstrating the integration of all elements of the project. All the requirements and functionalities of the project shall be accomplished and fully tested. The project development is finished.
15	jun. 13^th	Preview (qualification) of the project defense (Teams #1, #2)	TR: Full Technical Report + 5 min. video clip (project overview)	The Technical Report must be formatted according to the official format and sent by email. The full presentation of the project should last no more than 25 minutes.Slides and/or other multimedia support are expected to be used. An overview of the project should be presented as a short video (5 min.)
16	jun. 20^th	Preview (qualification) of the project defense (Teams #2, #3)	TR: Full Technical Report + 5 min. video clip (project overview)	The Technical Report must be formatted according to the official format and sent by email. The full presentation of the project should last no more than 25 minutes.Slides and/or other multimedia support are expected to be used. An overview of the project should be presented as a short video (5 min.)
17	jun. 27^th	Live presentation of the project to the examining board (Teams #1, #2)	DF: Defense of the project. Self-evaluation
18	jul. 4^th	Live presentation of the project to the examining board (Teams #3, #4)	DF: Defense of the project. Self-evaluation

Universidade Tecnológica Federal do Paraná (UTFPR) - Câmpus Curitiba

Departamento Acadêmico de Eletrônica & Departamento Acadêmico de Informática

Curso de Engenharia de Computação

Oficina de Integração 3