2021-03-30 » Historie » Verze 1
Roman Kalivoda, 2021-03-30 13:42
| 1 | 1 | Roman Kalivoda | h1. 2021-03-30 |
|---|---|---|---|
| 2 | |||
| 3 | h3. Attendees |
||
| 4 | |||
| 5 | * @brada |
||
| 6 | * @kacerekz |
||
| 7 | * @akonig |
||
| 8 | * @emouryc |
||
| 9 | * @kali |
||
| 10 | |||
| 11 | h3. Tasks |
||
| 12 | |||
| 13 | * improve product vision statement: what are the user roles, what problem are we trying to solve with the app, where do we want to get |
||
| 14 | * specify maintenance details |
||
| 15 | * sponsor requirement: visually appealing result visualizations |
||
| 16 | |||
| 17 | h3. Notes |
||
| 18 | |||
| 19 | to vision statement |
||
| 20 | - what will it be good for |
||
| 21 | - what it does |
||
| 22 | - where do we want to get |
||
| 23 | |||
| 24 | explore |
||
| 25 | - data |
||
| 26 | - prediction method |
||
| 27 | - user interface |
||
| 28 | -> not like aswi project is "standardized"´ |
||
| 29 | |||
| 30 | who are users |
||
| 31 | what they gain from the app / what they can expect |
||
| 32 | what problem are you trying to solve |
||
| 33 | |||
| 34 | risks + challenges |
||
| 35 | - technological side of things unclear |
||
| 36 | - decide if mobile / WebGL |
||
| 37 | |||
| 38 | to vision statement |
||
| 39 | - what would be the prediction |
||
| 40 | - in more detail |
||
| 41 | - unify terminology, clarify what is predicted (! only how busy zču is !) |
||
| 42 | - stuff interesting for stakeholder |
||
| 43 | - what is needed to input from user |
||
| 44 | - how it will be maintained |
||
| 45 | - who / how will be model retrained |
||
| 46 | |||
| 47 | visualization |
||
| 48 | - map? do we have enough data for that -> we don't know, until then we can't really decide |
||
| 49 | - whatever the visualization looks like has to be visually appealing |
||
| 50 | - map / histogram |