Based on our UCD from last week we decided on which parts we want to concentrate on this semester. Luckily this decision wasn’t very difficult as we will need a base system before we can implement additional features. This means that we will need a frontend to display our calculated statistics, some scripts to collect the raw data and of course the part which processes all data in order to allow us to predict something. Therefore we selected the following use cases from our diagram:
- Registration and Login
- View our data
- Customize Interests
- Collect public data
- Calculate ELOs
- Predict results
Our first activity diagrams
Cause this were our first activity diagrams we started with creating one for the registration and login, although it was not necessary for the homework. But it was quite straightforward to draw these diagrams for such a common case that it helped us to get an idea of what we had to do. Also for the purpose of having a complete documentation we needed to create this document.
The next use case we examined in more detail was the collection of publicly available data which should be the basis for our first predictions. This case differs a bit from others because you can not separate the activities into user, UI and system or something similar as the whole process is part of the backend. For this reason it was also not possible to develop a mock up.
We also had a closer look on the use case “View our data” which was a bit challenging because therefor we had to plan the overall design of our website, but we did not have any ideas how to design it. For that reason this task tooks longer than expected. We still didn’t finished the UC-document for this use case so we could not put a link in the blog post. But we will update this post as soon as we have finished the document.
Looking forward to get some feedback