report

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
report [2025/06/16 19:16] – team2report [2025/06/25 16:45] (current) – [Glossary] team2
Line 23: Line 23:
 |ISEP|Instituto Superior de Engenharia do Porto| |ISEP|Instituto Superior de Engenharia do Porto|
 |USB |Universal Serial Bus| |USB |Universal Serial Bus|
-|E |Esther| 
-|F |Flavius| 
-|J|Jouke| 
-|M |Mateusz| 
-|T |Tim| 
-|V |Victor| 
 |QR | Quick-Response| |QR | Quick-Response|
 +|RAM | Random Access Memory|
 +|GHz | Gigahertz – billions of cycles per second|
 |Internet | A global computer network providing a variety of information and communication facilities| |Internet | A global computer network providing a variety of information and communication facilities|
 </WRAP> </WRAP>
Line 768: Line 764:
 <WRAP round box 400px center> <WRAP round box 400px center>
 <table tlabel1> <table tlabel1>
-<caption>Project Backlog</caption>+<caption>Updated Project Backlog</caption>
 <WRAP center> <WRAP center>
-^ PBI       ^ Title          ^ Status     ^ +^ PBI ^ Title                                      ^ Status        ^ 
-| A         | Define Project    | Done      |  +| A   | Define Project                             | Done          | 
-| B         | Black Box Diagram    | Done      |   +| B   | Black Box Diagram                          | Done          | 
-| C         | Structural Drafts    | Done      |   +| C   | Structural Drafts                          | Done          | 
-| D         | Project Backlog    | Done      |       +| D   | Project Backlog                            | Done          | 
-| E         | Global Sprint Plan    | Done      |    +| E   | Global Sprint Plan                         | Done          | 
-| F         | Initial Sprint Plan    | Done      |    +| F   | Initial Sprint Plan                        | Done          | 
-| G         | List of Components and Materials    | Done    |    +| G   | List of Components and Materials           | Done          | 
-| H         | Detailed Schematics    | To do      |   +| H   | Detailed Schematics                        | Done          | 
-| I         | Structural Drawings    | To do      |     +| I   | Structural Drawings                        | Done          | 
-| J         | Cardboard Model    | To do      |   +| J   | Cardboard Model                            | Done          | 
-| K         | Upload Interim Deliverables    | To do      |   +| K   | Upload Interim Deliverables                | Done          | 
-| L         | S&P Assessment    | To do      |    +| L   | S&P Assessment                             | Done          | 
-| M         | 3D Model Video    | To do      |   +| M   | 3D Model Video                             | Done          | 
-| N         | Final List of Materials & Components    | To do      |   +| N   | Final List of Materials & Components       | Done          | 
-| O         | Refined Report    | To do      |   +| O   | Refined Report                             | Done          | 
-| P         | Packaging Solution    | To do      |   +| P   | Packaging Solution                         | Done          | 
-| Q         | Functional Tests    | To do      |   +| Q   | Functional Tests                           | Done          | 
-| R         | Upload Final Deliverables    | To do      |   +| R   | Upload Final Deliverables                  | Done          | 
-| S         | Final Presentation    | To do      |  +| S   | Final Presentation                         | Done          | 
 +| T   | Transfer Scope to Canva                    | Done          | 
 +| U   | Power Budget Analysis                      | Done          | 
 +| V   | Project and Engineering Backlogs Definition| Done          | 
 +| W   | Engineering Ethics Section                 | Done          | 
 +| X   | Sustainability Section                     | Done          | 
 +| Y   | Business Model Canvas                      | Done          | 
 +| Z   | Flyer and Leaflet Design                   | Done          | 
 +| AA  | 3D Model Updates (Tablet, Cabling)         | Done          | 
 +| AB  | UI Design and Application Screens          | Done          | 
 +| AC  | Controller Requirements and Draw Logic     | Done          | 
 +| AD  | Login and Registration Logic               | Done          | 
 +| AE  | App Authentication and API Tests           | Done          | 
 +| AF  | Raspberry Pi Setup                         | Done          | 
 +| AG  | Multi-user Simulation                      | Done          | 
 +| AH  | SWOT Analysis and Strategy Docs            | Done          | 
 +| AI  | User Manual and Assembly Guide             | Done          | 
 +| AJ  | Load and Stress Simulations                | Done          | 
 +| AK  | Risk and Liability Assessment              | Done          | 
 +| AL  | Marketing Programmes and Materials         | Done          | 
 +| AM  | Stakeholder Management                     | Done          | 
 +| AN  | Burnup Charts and Sprint Refinement        | Done          | 
 +| AO  | Communication Plan                         | Done          | 
 +| AP  | Procurement List and Sourcing              | Done          | 
 +| AQ  | Refine UN SDG section                      | Done          | 
 +| AR  | Project Paper and Documentation            | Done          | 
 +| AS  | Final Deliverables Submission              | Done          |
 </WRAP> </WRAP>
 </table> </table>
 </WRAP> </WRAP>
 +
  
  
Line 924: Line 947:
  
 ==== - Sprint Outcomes ==== ==== - Sprint Outcomes ====
 +
 +There is no sprint burn-up charts for these sprints, Which have been further explained in the summary.
 +
  
 === Sprint 1 Outcome === === Sprint 1 Outcome ===
Line 1247: Line 1273:
 **Planned vs. Achieved:** 5/5 **Planned vs. Achieved:** 5/5
  
 +==== - Sprint Evaluations ====
  
 +=== Sprint 1 Evaluation ===
 +In the first sprint, the team set up the basics of the project. The topic was chosen, the team learned how to use Jira, and took part in introduction sessions. All tasks were finished on time, and the team worked well together during brainstorming.
  
 +This sprint helped the team define their roles, tools, and how they would work together in the future.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good teamwork and high motivation. |
 +| Negative | More time could have been spent looking at different project ideas. |
 +
 +=== Sprint 2 Evaluation ===
 +In Sprint 2, the team built on the first sprint by defining the project’s scope and technical direction. The Blackbox Diagram was created, the scope was finalized, and research on similar projects was done. The project name was also chosen.
 +
 +This sprint showed better communication and clearer task responsibilities.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good teamwork on defining the project and updating documents. |
 +| Negative | Research into existing solutions could have been more detailed. |
 +
 +=== Sprint 3 Evaluation ===
 +Sprint 3 focused on both technical work and research. A first 3D model was made, and important topics like sustainability, ethics, and marketing were covered. Material costs were also reviewed.
 +
 +The team handled both technical and research tasks well.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Reliable task completion and a good mix of technical and research work. |
 +| Negative | Some reports lacked enough detail, especially in sustainability and marketing. |
 +
 +=== Sprint 4 Evaluation ===
 +In this sprint, the team worked on organizing important project documents and deliverables. Tasks included creating schematics, engineering backlogs, updating the project scope, and making promotional materials.
 +
 +The sprint was productive, but some team members had too many tasks.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Fast task completion and better organized documents. |
 +| Negative | Task planning could be improved to avoid overloading some team members. |
 +
 +=== Sprint 5 Evaluation ===
 +Sprint 5 focused on improving previous work and preparing for implementation. The final Blackbox design, materials list, and software/hardware plans were completed. User interaction documents were also finished.
 +
 +The team was well-organized and completed all tasks on time.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good preparation for technical development and clear documentation. |
 +| Negative | Deciding on hardware options took longer than expected. |
 +
 +=== Sprint 6 Evaluation ===
 +In this sprint, the team started prototype development. Login and registration logic, UI designs, and hardware setup began. Some tasks stayed “In Progress,” and the team noticed a drop in the number of finished tasks compared to earlier sprints.
 +
 +This sprint showed where technical challenges were starting to appear.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good start on technical implementation. |
 +| Negative | The sprint was too ambitious with too many tasks at once. |
 +
 +=== Sprint 7 Evaluation ===
 +This sprint was a positive step forward. All planned tasks were completed, including UI development, flyer adjustments, and prototype improvements.
 +
 +The team managed to solve earlier technical problems and improve documentation.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | All tasks finished and visible technical progress. |
 +| Negative | Some tasks needed extra adjustments before meeting the expected quality. |
 +
 +=== Sprint 8 Evaluation ===
 +Sprint 8 focused on refining the software, packaging ideas, and promotional materials. New app screens were created, and work on the leaflet and flyer continued.
 +
 +Task management improved, and team communication was clear.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Balanced progress in software, packaging, and marketing work. |
 +| Negative | Packaging ideas needed clearer technical descriptions. |
 +
 +=== Sprint 9 Evaluation ===
 +This sprint involved technical improvements with simulations, testing, and packaging trials. The team also worked on the user manual and energy optimization.
 +
 +Most tasks were completed, though some needed extra time.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Steady technical progress and improved reports. |
 +| Negative | A few tasks were delayed because of unexpected challenges. |
 +
 +=== Sprint 10 Evaluation ===
 +In Sprint 10, the team focused on final technical documentation, software improvements, and stress test explanations. Updates to the 3D model and paper writing also took place.
 +
 +Even with a heavy workload, the team kept up good productivity.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Strong task completion and good final improvements. |
 +| Negative | Some paper sections needed extra changes after feedback. |
 +
 +=== Sprint 11 Evaluation ===
 +Sprint 11 was about final tests and fixing documents based on feedback. API testing, multi-user tests, risk management updates, and chapter revisions were done.
 +
 +Task tracking improved, and work was completed smoothly.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Quick issue-solving and helpful report updates. |
 +| Negative | Several documents required last-minute adjustments. |
 +
 +=== Sprint 12 Evaluation ===
 +This sprint finalized app development, testing, and user guidelines. Cost review and strategic documents were also finished.
 +
 +The team worked well together, and nearly all tasks were completed on time.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good balance between technical work and reporting. |
 +| Negative | Some documents, like SWOT and liability analysis, took more time than planned. |
 +
 +=== Sprint 13 Evaluation ===
 +Sprint 13 focused on polishing marketing materials, project management, and prototype documents. Tasks included procurement, stakeholder review, and final paper improvements.
 +
 +Though the workload was high, it was handled efficiently.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | Good updates to reports and promotional materials. |
 +| Negative | Some project management tasks extended beyond deadlines. |
 +
 +=== Sprint 14 Evaluation ===
 +The final sprint completed marketing analysis, final paper edits, test result reviews, and deliverable packaging. The team made sure everything was ready for final submission.
 +
 +It was a strong and organized finish to the project.
 +
 +^ Aspect ^ Reflection ^
 +| Positive | All tasks finished and final deliverables well prepared. |
 +| Negative | A few tasks could have been completed earlier with better scheduling. |
 +
 +==== - Summary ====
 +This chapter explained how the DrawYourWay project was organized and managed. It covered the main project management topics like scope, scheduling, cost estimates, quality checks, team roles, tools, and risk management. Weekly sprints and evaluations helped the team stay organized, make adjustments when needed, and complete tasks on time.
 +
 +Stakeholders were identified, and the necessary tools and resources for hardware and software development were planned. By following an agile method and a clear project plan, the team made steady progress and reached a working, sustainable prototype.
 +
 +With the technical planning and organization now finished, the next chapter will focus on how DrawYourWay will be introduced to the public through the Marketing Plan.
  
  
Line 1507: Line 1665:
  
 **Price** **Price**
-Participation in DrawYourWay is free. The choice was made to make participation free so that it is and remains attractive for users. For the financing of the project and the rewards, we will work together with companies. Companies can promote their brand on the platform. In exchange for promoting their brand, they sponsor the rewards or the necessary hardware.+Participation in DrawYourWay is free. It was decided to make participation free, so that it is and remains attractive for users. To finance the project, DrawYourWay will be sold for 5999.99 euros to waiting station for public transport. This price was created by doing the price of the Component/Material about 5 times. In this way, the labor cost can also be recovered in the long term. We work together with companies for the rewards. Companies can promote their brand on the platform. In exchange for promoting their brand, they sponsor the rewards for the daily/weekly winners.
  
 **Place** **Place**
Line 2212: Line 2370:
 {{:step_up_box.png?800|}} {{:step_up_box.png?800|}}
 <caption>step up box.</caption> <caption>step up box.</caption>
 +</figure>
 +</WRAP>
 +
 +<WRAP centeralign>
 +<figure fig-ss>
 +{{ ::childonstepupbox.png?600 |}}
 +<caption>Visualization of a child standing on a step up box.</caption>
 </figure> </figure>
 </WRAP> </WRAP>
Line 2328: Line 2493:
  
 === - Tests & Results === === - Tests & Results ===
 +
 +** Test environment **
 +
 +The tests were conducted on a computer located in the ISEP classroom. This machine simultaneously served as both the frontend and backend server for the users. Its specifications were as follows: a 3.2 GHz Intel Pentium G3250 processor, 4 GB of RAM, and Windows 10 as the operating system.
  
 === Hardware tests === === Hardware tests ===
Line 2403: Line 2572:
        
 ==== - Summary ==== ==== - Summary ====
-The DrawYourWay project is an interactive public art platform aimed at transforming idle commuter time in metro stations into moments of creativity and engagement. It enables users to create digital drawings using their own mobile devices or tablets and project them onto large public walls in real-time, encouraging public participation and community interaction. The idea stemmed from the team’s shared interest in digital art and was developed through collaborative brainstorming and design thinking sessions.+During the development of the prototype, several adjustments were made compared to the original design to simplify the process and stay within the available budget, while still ensuring that the core functionalities could be demonstrated. 
 + 
 +Regarding the structure, some practical decisions were taken. The protective case for the projector was not produced, as it was not essential for showing the system’s operation during testing. Additionally, modifications were made to the tablet’s protective case: instead of using ABS, PLA was used. While PLA has lower mechanical and chemical resistance, it was a good alternative for the prototyping phase. Furthermore, the prototype version of the tablet case excluded holes for wall and table mounting, cable openings, and clamps since these were unnecessary for this stage. To speed up production, the case was printed in two parts and then glued together, which slightly reduced the quality of the finish but made the process more efficient.
  
-Technologically, the platform integrates QR code interaction, drawing tools, and a projection system managed by a backend built with Django and React, forming a Progressive Web App (PWA) accessible on both desktop and mobile. The hardware setup includes second-hand tablets and energy-efficient laser projectors, ensuring cost-effectiveness and sustainability. A Raspberry Pi manages user input, connectivity, and projection, with a total power consumption of 123W and estimated annual cost of €160.+In terms of hardware, two main changes were implemented to remain within the €100 budget. An old projector was repurposed instead of acquiring a new one, and an old PC was used in place of the originally planned Raspberry Pi. These substitutions did not affect the testing of the main functionalities but did limit the scope of some hardware-specific tests.
  
-Sustainability plays a major role in the project. Environmentally, recycled and biodegradable material as plywood are used, economically, second-hand and locally sourced equipment keeps costs low and socially, the project promotes inclusivity, creativity, and community well-being. Ethical and deontological principles guide decisions around honest communication, environmental care, and content moderation.+The software for the prototype was built using Django for the backend and React for the frontend, resulting in a Progressive Web App (PWA). which makes the system accessible via both web browsers and mobile devices. The prototype’s software features included user login and registration, the ability to draw drawings, a drawing interface, and QR code scanning functionality to link specific locations with relevant drawings.
  
-The packaging was designed with dual functionality: a sturdy plywood step-up box for transporting and then supporting tablet use, and a stainless steel projector case that ensures durability and reusability. During prototyping, budget-friendly changes were made, including using PLA instead of ABS and repurposing old hardware.+Both hardware and software underwent a series of tests to evaluate the performance. Hardware tests were conducted in a metro station environment to assess real-world functionality. Of the nine tests, the prototype successfully passed Functionality Testing, Real-Time Display Test, User Experience Testing, Connectivity Test, and Hardware Durability Test. Theme Rotation and Moderation Tests were not completed due to time constraints and development priorities. Energy Consumption and Maintenance & Support Tests could not be performed effectively because the alternative hardware used in the prototype would not have provided representative results for the final product.
  
-Testing validated several key features such as functionality, user experience, connectivity, and hardware durability. However, limitations in time and equipment meant that theme rotation, content moderation, energy use monitoring, and long-term maintenance were not fully realized. Nonetheless, the project presents a promising, scalable, and socially engaging solution for urban environments.+Software testing included a detailed analysis of system request statistics and response times, confirming stable and reliable performance for the implemented functionalities. A full report detailing these results was compiled and made available for reference.
  
 +In conclusion, the prototype successfully demonstrated the core concept and main functions of the DrawYourWay system, providing valuable insights for future iterations and development phases.
  
 ===== - Conclusions ===== ===== - Conclusions =====
  • report.1750097801.txt.gz
  • Last modified: 2025/06/16 19:16
  • by team2