Sprint 3

The milestone can be found at the following link: Sprint #3.

Objective

Objective: Enhance Website Application, Implement GitLab Pipeline, Supply Backend Functionality, and Refactor Software for Project Delivery

Focus: Extensively work on the GitLab pipeline, including automated unit testing and deployment mechanisms, to improve software reliability and streamline delivery workflow.

Task: Supply defined backend functionality to Vue components using JavaScript modules, integrating necessary backend modules to ensure seamless communication and data exchange between the concerned components.

Final stage: Refactor and refine the software, addressing issues, optimizing performance, and improving codebase readability and maintainability for project stability and scalability.

Outcome: By the end of Sprint #3, the project team aims to have an enhanced website application with refined Vue components, an effective GitLab pipeline for automated testing and deployment, supplied backend functionality, and completed final software refactoring and refinement. These efforts ensure project readiness for high-quality delivery.

List of requirements

The following section includes the list of requirements that were considered for Sprint #3. Moreover, for each, it is indicated whether it was completed or not. As part of documenting the issues, the Requirement template was used, which enforced the use of user stories, SRS requirements, etc., as much as applicable. The list as the following:

1. #47: Create Sitemap diagram
   • This issue has been out-scoped for Sprint #3 as it proved to be a non-essential addition to the project.
2. #62: Create navbar for logged in user
3. #63: Add reconnect to mqtt.js connect function
4. #64: Create a Vue component for the sensor-specific graphs
5. #65: Implement a JS module that generates a simple line graph
6. #67: Calculate average sensor values
7. #68: Add publish mechanism that transfers user-defined ranges (from the web-app) to the terminal
8. #69: Add mechanism that supplies MonitorTerrarium page with real-time sensor values
9. #70: Parse vibration data as a counter in application module
10. #71: Create Website "MonitorTerrarium"-component
11. #72: Add Client-Side Routing for the Terminarium Website
12. #73: Refactor Behavior for "Your Terrariums"-page
13. #74: Add More (Avatar) Image Assets
14. #75: Apply global web styling
15. #76: Improve Web-app Codebase Consistency
16. #77: Refactor set sensor ranges component
17. #78: Create an install/build pipeline for terminarium-web
18. #79: Add a linting job to the pipeline
19. #80: Implement save & read from local storage in set sensor ranges component
20. #81: Add testing job to the pipeline
21. #82: Add Unit Test for the DefaultPageLayout Vue Component
22. #83: Fix logo file path in header
23. #84: Add Unit Test for the Header Vue Component
24. #85: Add a Unit Test for AccessButton Component
25. #86: Add Unit Test for Avatar Component
26. #87: Add Unit Test for Chart Component
27. #88: Add Unit Test for the SelectTerrariumPage Component
28. #89: Add Unit Test for the SetSensorRanges Component
29. #90: Allow user input to modify network credentials from Wio terminal
30. #91: Bug: fix Wio Terminal errors when simultaneously receiving multiple ranges
31. #92: Add functionality to User Settings save button
32. #93: Create registration page
33. #96: Save network info and sensor ranges in Wio Terminal flash storage

TODO: revisit the states of the issues and update the list accordingly based on if they were completed or not.

Timeline

The timeline for Sprint #3 is outlined as the following:

• Start date: 2021-05-08
• End date: 2021-05-21

Thus, making the duration of the sprint to be 14 days.

Risks

A summary of risks are challenges is outlined in detail in the Challenges subsection of the Sprint #3 section here.

Communication plan

The team has successfully continued to make use of Discord as the primary communication platform as well as GitLab and all its rich features for the development of the project. The team has also continued hold daily stand-ups, which were previously introduced as part of Sprint #2. Furthermore, Discord has enabled to effectively schedule meetings and share the agenda for the meetings via the Discord Events functionality.

Lastly, the team has also continued to make use of GitLab's issue board to keep track of the progress of the project and the issues that are being worked on.