Product Vision Statement » Historie » Verze 4
Roman Kalivoda, 2021-03-30 08:45
Add risks definition
1 | 1 | Roman Kalivoda | h1. Product Vision Statement (WIP) |
---|---|---|---|
2 | |||
3 | h2. Project Goals |
||
4 | |||
5 | 2 | Alex Konig | Creating an application that will, based on weather input, predict the attendance in class. User will be able to input their own weather information, or choose prediction based on current weather information or prediction for future days. |
6 | 1 | Roman Kalivoda | |
7 | 3 | Eliška Mourycová | h3. Happy Day use-case |
8 | |||
9 | The user will specify a date and classroom (e.g. UC-336) for which they wish to get the prediction of attendance. It will be possible to choose to have the weather forecast data for the given day downloaded automatically or input manually. The output of the app will be a text field saying how high the attendance the model predicts (e.g. very high). |
||
10 | |||
11 | 1 | Roman Kalivoda | h2. Project Plan |
12 | |||
13 | |||
14 | h2. Stakeholders |
||
15 | |||
16 | * Development Team |
||
17 | * Project Sponsor |
||
18 | * Project Mentor |
||
19 | * Users: lecturers |
||
20 | * Users: students |
||
21 | |||
22 | h2. Risks |
||
23 | |||
24 | h3. Available data are too crude |
||
25 | 4 | Roman Kalivoda | |
26 | Chances are that the data are not specific enough to make proper predictions for single classrooms. Hopefully, the model could be improved gradually when there is more data available. In the meantime, we could modify the app to show just the prediction for a whole building. |
||
27 | |||
28 | h3. Our effort estimation is grossly underestimated |
||
29 | |||
30 | We should define/negotiate a minimum viable product and prioritize individual features. |
||
31 | |||
32 | h3. We proposed an unsuitable technological stack |
||
33 | |||
34 | _(TBD)_ |