Important disclaimer: contents is subject to updates along the semester !
Week	Date	Description	Deliverables / Evaluations	Detailing
1	mar.27^th	Overall introduction and course overview. Short talk about the PMBOK method, examples of successfull projects. Formation of the teams of 6 students, by semi-random draw from predefined pairs.		Create a blog using the following pattern: "Team_N_Integration_Workshop3_UTFPR_2025_1", 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.
2	apr.3^rd	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.
3	apr.10^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.
4	apr.17^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.
5	apr.24^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 apr.30th 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
	may.1^st	Holyday - no classes
6	may.8^th	Project development: D1: Mechanical Project	Publish in the main page of the blog (before class time) a short video (maximum 10 minutes) named "Mechanical Project". This video should present at least 50% of the mechanical construction done, and the full "Electronic Design", including all schematic diagrams	At this point, the Mechanical project must be concluded and Electronic Design be approved.
7	may.15^th	Project development:	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.
8	may.22^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.
9	may.29^th	Project development and monitoring (All Teams)	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.
10	jun.5^th	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.
11	jun.12^th	Preliminary presentation of the project (up to 25 minutes) plus a short video of 5 minutes. All teams must present
	jun.19^th	Holyday - no classes
12	jun.26^th	Project development and monitoring	TR: Full Technical Report (15-20 pages) + 5 min. video clip (project overview) Preview: Full presentation of the project + demonstration	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.). Functioning in the demonstration is a mandatory criterion for the team to be authorized to present to the final evaluation panel.
13	jul.3^rd	Live presentation of the project to the examining board.	DF: Defense of the project. Self-evaluation
14	jun.10^th	Live presentation of the project to the examining board.	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