Attention: This is a preliminary schedule, subject to updates along the semester!
Week	Date	Description	Deliverables / Evaluations	Detailing
1	aug.14^th	Overall introduction and course overview. Short talk about the PMBOK method, examples of successfull projects. Short presentation about the necessary features required in the projects		Formation of the teams of 5 students, by semi-random draw from predefined pairs.
2	aug.21^th	First round of preliminary project proposals		Create a blog using the following pattern: "Team_N_Integration_Workshop3_UTFPR_2025_2", where N is the number of the team 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.
3	aug.28^th	Live reply about project proposals (plans A, B, and C) for all teams. Short talk about "Time Management Strategies"	Publish in the blog (before class time) a short video (maximum 10 minutes) describling 3 project proposals (plans A, B and C).	After rebuttal from the professors, teams must choose 2 out of the 3 initial proposals. For te next class, teams should enhance both plans with more details and specifications.
4	sep.4^th	Live reply about the enhanced project proposals (plans A and B). Short talk about "Functional and Non-functional Requirements"	Publish in the blog (before class time) a short video (maximum 10 minutes) describling enhanced versions of plans A and B, selected from previous class.	After rebuttal from the professors, teams must choose only one from plans A and B, which will be the project to be developed along the semester.
5	sep.11^th	Short talk about "Risk Management Analysis" Bônus: Talk with the expert (#1)	Publish in the blog (before class time) a short video (maximum 10 minutes) presenting the details of the project, including Funcional and non-functional requirements for hardware and software, platforms, preliminary budget, detailed tasks and schedule.
6	.sep.18^th	Project development: PC1: Project Charter	Publish in the main page of the blog (before class time) a short video (maximum 15 minutes) named "Project Charter". This video should present full details of the project, including, also, the Risk Management Analysis.	IMPORTANT: Until sep.25th it is expected that teams publish in their Blog a video (maximum 10 minutes) a section named "Mechanical Design" in which is found the full diagrams/technical design of the mechanical parts. Professors will give a feedback until the next weekend
7	sep.25^th	Project development: D1: Mechanical Design	Publish in the main page of the blog (before class time) a short video (maximum 10 minutes) named "Mechanic Design".	Complete mechanic design, including drawing of all parts, printed parts and their mounting.
8	oct.2^nd	Project development: D2: Partial Mechanic Project + Electronic Design	D2: Partial Mechanic project (50%), plus Electronic design, including all schematic diagrams	Partial Mechanical project (50%) Electronic design including schematics and test of components.
9	oct.9^th	Project development: D3: Full Mechanic Project + Partial Electronic Project + Software Design	D3: Full Mechanic project, plus Electronic Project (50%), plus Software design	Finished mechanical structure. Electronic hardware project 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.
10	oct.16^th	Project development: D4: Full Electronic Project + Partial Software implementation	D4: Full Electronic project, plus Partial Software implementation	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.
11	oct.23^th	NO-CLASSES	SEI-SICITE: Seminário de Extensão e Inovação / Seminário de Iniciação Científica e Tecnológica da UTFPR
12	.oct.30^th	Project development: D5: Full Software implementation	D5: Full Software implementation
13	nov.6^th	Project integration D6 Bônus: Talk with the expert (#2)	D6: Mechanics, hardware and software fully integrated. Live demonstration	Demonstration of the full integration between the mechanical parts with hardware/firmware and software elements
14	nov.13^th	Preliminary presentation of the project (up to 25 minutes) plus a short video of 5 minutes. All teams must present	Preview: Full presentation of the project + demonstration	Functioning in the demonstration is a mandatory criterion for the team to be authorized to present to the final evaluation panel.
15	nov.20^th	NO-CLASSES	HOLIDAY: Dia da Consciência Negra
16	nov.27^th	Project development and monitoring	TR: Full Technical Report (15-20 pages) + 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	nov.4^th	Live presentation of the project to the examining board.	DF: Defense of the project. Self-evaluation
18	nov.11^th	Live presentation of the project to the examining board.	DF: Defense of the project. Self-evaluation
19	nov.18^th	Conclusion, with course evaluation and strategic planning

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