| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| report [2022/06/20 01:24] – [3.7 Risk] team2 | report [2022/06/28 10:49] (current) – [7.7 Tests and Results] team2 |
|---|
| The last external stakeholders identified are the suppliers. Their importance is great because the manufacturing of the product relie almost them. From the raw materials, to the shaping of parts, but also the transportation, all these cannot be fully carried out as explained in the previous section 3.8 procurement. Therefore, it would be detrimental to not maintain good relationship with them. But on the other hand, since we are so dependant on them, it is necessary to monitor them closely. Thus, contrats must clarify precisely needs and expectation as well as what should happen if not respected (delays, etc). | The last external stakeholders identified are the suppliers. Their importance is great because the manufacturing of the product relie almost them. From the raw materials, to the shaping of parts, but also the transportation, all these cannot be fully carried out as explained in the previous section 3.8 procurement. Therefore, it would be detrimental to not maintain good relationship with them. But on the other hand, since we are so dependant on them, it is necessary to monitor them closely. Thus, contrats must clarify precisely needs and expectation as well as what should happen if not respected (delays, etc). |
| ==== - Sprint Outcomes ==== | ==== - Sprint Outcomes ==== |
| //To be added. Include the outcomes of all sprint reviews (what was the sprint backlog, completion status, planned capacity vs. achieved velocity).// | The following tables show the weekly sprints, indicating the task, the completion status and the person in charge. In addition, the planned working hours are compared with the actual workload. |
| |
| <WRAP center centeralign 750px> | <WRAP center centeralign 750px> |
| **Performance test** | **Performance test** |
| |
| The technological performance of software was assessed using the Google Developers service [[https://pagespeed.web.dev|Page Speed Insights]], which sends a request to the page and measures response and load times. The performance scores of the mobile and screen applications were both high with 90 and 92 percent respectively (see figures {{ref>figlabel41}} and {{ref>figlabel42}}). The small reduction in performance scores is due to the large data size of the 3D plugin. | The technological performance of software was assessed using the Google Developers service [[https://pagespeed.web.dev|Page Speed Insights]], which sends a request to the page and measures response and load times. The performance scores of the mobile and screen applications were both high with 90 and 92 percent respectively (see Table {{ref>tlabel29}}). The small reduction in performance scores is due to the large data size of the 3D plugin. |
| |
| |
| | <WRAP center centeralign 750px> |
| <figure figlabel41> | <table tlabel29> |
| {{ ::performance-mobile.png?600 |{{ :performance-screen.png?600 |}} | <caption>Page Speed Performance Test Results</caption> |
| <caption>Performance result mobile application</caption> | ^ Performance Indicator ^ Screen Application ^ Mobile Application ^ |
| </figure> | | Overall Score | 92 | 90 | |
| <figure figlabel42> | | First Contentful Paint | 0.7s | 0.7s | |
| {{ :performance-screen.png?600 |}} | | Time to Interactive | 1.4s | 1.5s | |
| <caption>Performance result screen application</caption> | | Speed Index | 1.0s | 1.1s | |
| </figure> | | Total Blocking Time | 10ms | 20ms | |
| | | Largest Contentful Paint | 2.8s | 2.0s | |
| | | Cumulative Layout Shift | 0.002s | 0 | |
| | </table> |
| | </WRAP> |
| |
| |
