Logbook

This is your logbook. Insert here all relevant information regarding the evolution of your project

Our team participated in team-building activities and took part in the Welcome Week, where we had the opportunity to get to know each other better and familiarize ourselves with the project framework. Additionally, we explored various topics related to the EPS (European Project Semester) program. As part of the preparation process, our team organized a meeting to discuss and decide on a project topic. After careful consideration, they selected three main topics in the following order of preference: ,,Our City Experiences“, ,,Digital Art”, and ,,Smart Health and Well-being“.

This week, we had our first meeting with the project supervisors, where we asked questions about our concept. Additionally, we brainstormed ideas using MIRO and chose a name for our project: DrawYourWay.

We started this week by writing an essay about our first team-building activity in the park and completing the “Group attitude rules” document, which outlines our best approach to the project. Moreover, we have done the Elevator Pitch, a research on other similar projects that integrate art in public spaces and the Blackbox Diagram for DrawYourWay project.

This week, we completed our scope and created a list of the necessary materials for the project. We made drawings representing our project and developed 3D models of our product. We improved the black box and created the Gantt chart using the program recommended by the professors. We also worked on the first details of the schematic design. Additionally, we planned what tasks need to be completed for the next sprint.

This week, the Blackbox design and list of materials were improved for better clarity and accuracy. A flyer proposal, user story, and user case were created to enhance project communication and user interaction. Additionally, detailed schematics were developed, and both software and hardware backlogs were updated. Lastly, the next sprint plan and Gantt chart were refined to ensure efficient project progression.

This week, the team began working on the prototype from a technical perspective. We started by coding the basic login and user registration logic. Additionally, we designed the login and registration screens. The team also planned a midterm presentation and started filling out the midterm report.

This week the team took part in an interim presentation, showcasing their achievements and work to date, while also gathering feedback from the course tutors.

This week, the team completed a 3D model video to showcase the design, and performed load simulations to test the structure’s durability. The expected cost, selling price, and operational costs were calculated. The relevant UN Sustainable Development Goals were identified and justified. Additionally, new screens for the user interface were created. Finally, the next sprint was planned with updated tasks and goals.

This week, the power budget analysis was updated to better reflect the system's energy needs. A first version of the poster and leaflet was created to promote the project. We also improved the stress tests for the prototype and made a video showing how the login feature works.

During the tenth meeting, the team discussed several key updates and developments. The second version of the poster and the first version of the leaflet were reviewed and improved based on previous feedback. Progress was made on the packaging design, focusing on functionality and sustainability. Updated stress tests for the prototype were presented, showing improved results. App development continued steadily, with added features and better usability. Lastly, the structure of the user manual was introduced, outlining the steps users will follow to interact with the system.

This week the focus was on finalizing different deliverables. We continued developing the app and made progress on writing the paper. We worked on the packaging and ran a stress simulation. We also started designing the leaflet and organizing the software manual. At the end of the week, we had a meeting to discuss what still needed to be added to the manual.

This week we prepared and showcased the final prototype. We carried out functional tests to measure key performance metrics. Work continued on the paper to get it ready for submission. We also focused on improving the software manual. A meeting was held to go over everything and plan the final steps.

This week we worked on preparing the final presentation. We outlined the content and structure, focusing on the key topics. We gathered the results from the functional tests. Time was spent finalizing the paper for submission. We also planned the demo and how it fits into the presentation.

This week we worked on the final presentation. The problem and motivation slides were completed. We added a slide to show the app interface and its features. A backup video was prepared in case the live demo fails. We also updated the final slide to show a project image instead of a thank-you message.

1. Presentation
2. Modus operandi
3. Project proposals
4. Electronic logbook (Wiki)

We were introduced to the project topics, guided on how we should approach our work, and informed about the overall process of the EPS project.

1. Presentation of Current Work
2. Introduction of the Idea
3. Discussion of the Brainstorming Session
4. Presentation of Next Steps
5. Tools Used by the Team
6. Tips, Guidelines, and Advice from the Leading Team

We presented our current results and the ideas generated during the brainstorming session and received feedback on our solution. We were given guidance on how to improve interactions with people. We were directed to ensure that our solution must be interactive and sustainable. Additionally, we were advised to begin research and analysis on sustainability, ethics, and marketing. We were also instructed on the next steps to take.

1. Final project idea
2. Brand identity
3. Video
4. Blackbox diagram
5. Q&A

Questions:

1. Is the black box correct?
2. Should we start addressing the technical aspects of the project?
3. Is our idea for the Gantt chart correct?
4. Which part of the research should we focus on right now?
5. When will we get access to Jira?
6. What would you like to see next week?
7. How precise should the backlog be now?

We presented our basic brand identity (logo), the elevator pitch, the video, the black box diagram (black box about the smart system), Gantt Chart and received feedback about the black box diagram to improve it. We need to start focusing on the Hardware because it will allow the project to run. To be defined milestones (diagrams).

1. Scope
2. List Of Materials
3. Drawings
4. 3D Model
5. Gantt's chart
6. First detailed schematic
7. Plans for the next sprint
8. Q&A

Questions:

1. Is our scope correct?

During the meeting, it was discussed that each item in the materials list and components should include a justification for its selection, ensuring an impersonal tone in the report. Additionally, a detailed power budget analysis is required. Regarding project planning, the Gantt chart should not include milestones but must incorporate human resource distribution. The materials list should also specify the price and supplier for each item. In the next iteration, a tablet and cabling should be added to the 3D model. The WiFi module must not be treated as a black box, and bidirectional communication should be ensured. An anti-theft system for the pencil needs to be designed and integrated. Furthermore, the Business Model Canvas should clearly differentiate between customers and users, avoiding any confusion. Lastly, all reports and documentation must include references with links where applicable.

1. Improved Blackbox
2. Improved List Of Materials & Components
3. Flyer Proposal
4. User Story
5. User Case
6. Detailed Schematics
7. Software Engineering Backlog
8. Hardware Engineering Backlog
9. Next Sprint Plan
10. Gantt Chart
11. Q&A

Questions:

1. 3D printing the prototype (Jorge)
2. Available hardware at school (Raspberry Pi)

During the meeting with the supervisors and the Team, key tasks were discussed, including finalizing Chapters 1, 2, and 7, properly adding links and references, and ensuring images in Chapter 7. The list of component materials must use the euro currency, maintain consistent significant digits, and include prices for Wi-Fi and PLA printers with filament. The Team will check the feasibility of positioning the projector at a distance, ensure ventilation for its case, and determine whether a microcontroller should be included. Deliverables must have properly formatted links, the selection of components should be listed without explanations, and the list of materials should exclude dollar prices. Additionally, schematics, user stories, and the flyer design should be refined, ensuring consistent colors, fonts, and terminology.

1. Improved 3D Model
2. Second Iteration Of The Flyer
3. Login / Registration Logic
4. Login screen
5. Plan For Interim Presentation
6. Next Sprint Plan
7. Q&A

Questions:

1. Status 3D printing the prototype (Jorge)
2. Status Available hardware at school
3. do we need to ad or remove someting from the Plan For the Interim Presentation?

1. Interim Report

During the presentation, it was highlighted that the slide structure needs improvement: the title should reflect the actual project instead of “Interim Presentation,” and the agenda should be more concise. The marketing part should be presented first, including the Elevator Pitch, supported by communication materials. The technical section requires refinement—there are unresolved issues with system integration, hardware diversity (second-hand tablets), and no mention of the smart system. The report needs better formatting, additional citations and references, and should include missing components such as design, structure, and a proper conclusion.

1. 3D Model Video
2. Load Simulations
3. Expected cost and selling price
4. Expected cost of the operation
5. Sustainable development
6. New screens
7. Q&A

The team received information that it should now focus on improving all project expenses. Also, power budget analysis and selection of appropriate components should be improved.

1. Updated Power Budget Analysis
2. Poster & Leaflet | Version 1
3. ⁠⁠Improved Stress Tests For Prototype
4. Login Prototype Video

1) Poster Feedback - The poster should preferably be vertical for better readability — having both a vertical and horizontal version is an option. - The sentence “Draw on the tablet at the station” is better than what is currently used on the poster and should be implemented. - The phrase “with new teams and daily challenges” is also a better alternative and should replace the current text. - It's recommended to make two different posters:
one targeting users, and another aimed at buyers. - Instead of repeating steps for each device, present the flow as:
Option 1: Smartphone,
Option 2: Tablet,
followed by the 4 action steps only once. - Colors should be more consistent across the design. - The wall drawings on the poster could be more creative and illustrative.

2) Stress Tests - Material suggestion:to use PLA only for prototype, ABS and aluminum for the final product; - Safety factor test was mentioned — a follow-up via email is advised.

3) Packaging / Product Offering - Consider giving packaging a second life. - Clearly define what is included in the final product:
Tablet, projector, case, and cables. - Either use recycled packaging materials,
or install everything directly in the metro station and reuse leftover materials.

1. Leaflet
2. Poster 2nd version
3. Packaging
4. ⁠⁠Improved Stress Tests For Prototype
5. App Development
6. Manual

A stress analysis should be done for the step-up box, and both it and the projector case should have rounded corners for safety. The leaflet design should use a lighter grey and decide whether to center the text or not, and several spelling mistakes need correction (e.g., “to ensure its safety”, “vote for the best one”). The poster is approved, the manual should be redesigned as strip pages (one per step), and the report is progressing well.

1. App Development
2. Paper
3. Packaging (stress simulation)
4. Leaflet
5. Software manual

Questions: What to add to the software manual?

The packaging stress simulation is good, but the safety factor should be calculated by comparing forces to stress. The paper needs to be written impersonally, with the team name “Draw Your Way,” include prices in descriptions, align tables with prior paragraphs, and end each chapter with a summary; the conclusion should include personal reflections from each team member. For the leaflet and user manual, focus on a flexible 6-fold layout, simple visuals with minimal text, organized steps, contact info (QR/email/phone), and consistent visual elements like the logo and brush icon; also, try using a lighter grey for the projector screen.

1. Prototype Showcase
2. ⁠Functional tests
3. Paper
4. Software manual

A new and improved version of the video should be created. For the functional tests, provide only the three required metrics: 10 requests, latency (average and standard deviation), and number of failures. The user manual should be user-oriented, with clear step-by-step instructions (1, 2, 3), simple language, and illustrative images.

1. Final presentation agenda
2. Paper
3. ⁠Functional tests results
4. Demo

The final presentation should include 10 slides (excluding the title and agenda), covering the problem, motivation, and a combined section on state of the art, marketing, and sustainability as pillars leading to the proposed solution. This should be followed by a visual diagram, listed functionalities, design decisions, cost, energy consumption, and software maintenance, ending with the prototype. The prototype section must explain the differences between prototype and final product, present web functionalities, test results, and usability, while the demo can be integrated but must have a dedicated time slot.

1. Final presentation agenda

The problem and motivation parts of the final presentation are complete. A slide showing the app interface and its functionalities should be added before or just after the prototype section. A video should be prepared in case the app doesn’t work live, and the final slide should show an image of our work instead of a “thank you” message (e.g., a video showing the screw tightening process).

Please register here all accomplished project activities