Use Cases

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:

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.

Activity diagram for data collection

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

Join the Conversation


  1. Hi,
    your use-case specifications look quite understanding so far for me. You linked your UCs in your SRS which is good too. However, for the use-cases it is required this week to provide two use-case specifications without Login/out, I am not quite sure whether the registration use-case matches the grading criteria, and I guess you forgot to replace the heading 1 in each use-case (“Use-Case Name”) 🙂
    In your “Collect public data” UC your activity diagram contains a little error I think. You chose to use an empty decision block to merge the two ways of fetching the data, but I think you can leave that empty decision block out and point directly to the next action. I am not 100% certain about this, that’s just my opinion 😉
    Also, in your SRS you mentioned a URL to find the version history of the document, which is missing in your UCs. I would suggest you change either of that to provide consistency over your documents.

    Keep it going, nice work so far!
    [email protected]

    1. Hello Leonard,

      thank you for your comment and your suggestions. We added “View our data” as the second UCD. We are not sure about the heading, the title is in the following paragraph.
      We did correct the error, thank you.

      The version history can be always found under the “Page history” button.


  2. Hi guys,
    your activity diagrams are well structured and understandable.
    You should think about seperating registration and login into two different documents because they are obviously two different use cases, when you need to create seperate use case diagrams. Also in my understanding are your use cases all CRUD activitys which should be marked as such. It is also stated in the grading criteria that you should describe two use cases that are not the Login.
    Besides this did you do a great job and I am looking forward to see your progress in the future.
    Best regards,
    Tim from MAPHYNN

    1. Hello Tim,

      thank you for your comment.
      Registration and Login are two different use cases with two different use case diagrams on the same page. We will discuss whether we want to split them into two documents as well.

      Our two use cases beside Login and Registration are “View our data” and “Collect public data”.

      Thank you again!


Leave a comment

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.