Function Points

After choosing our next use-cases last week, this week we spend our time on predicting how long it would take us to fulfill these goals. In order to do this we used the function points methods to calculate the time needed for each use-case. A funtion point is a unit for the complexity of a single piece of your software.

At first we started by calculating the function points for the already implemented use-cases. Even after searching around the internet we are still a bit confused how exactly the vaule gets determined but we tried our best to be as accurate as possible. Unfortunatly three of the old use-cases aren’t completely finished so they became outliners which doesn’t fit the model very well. Therefore we could only use two of the old use-cases to generate a function to calculate the time used per function points. Maybe we should adjust our graph when we finished one or two more use-cases to get more reliable data.

After that we calculated the function points for the use-cases planned for this semester and estimated the time based on the trend of the old use-cases. The current status of our function point estimation can be found in the document section of our GitLab project. The following diagram shows all our use-cases together.

All usecases

See you next week.

Edit:

Unfortunately we managed to convert one youtrack day into 24 hour instead of 8 so our whole result wasn’t helpful at all. Therefore we updated our calculation again. But this even didn’t changed the fact, that we only have “View our data”, which may has consumed more time then required as we had a lot of setup work to do for this use-case, and “Registration and Login” as basis for our estimation.

We also added all the remaining use-cases to our calculation and get an result of 135 hours of work to do for this semester. Although we only spend 127 hours of work last semester in developing the first use-cases, we are still optimistic about reaching our goal until the end of semester two. Because our setup is now complete we can fully concentrate on implementation and won’t loose that much time as we did in the beginning.

Join the Conversation

4 Comments

  1. Hey guys,

    Your graph looks good and healthy i guess. Ours has some illness in comparison.
    Also your use cases are really detailled in numbers, but are there any notes about the particular DET somewhere? A List or something? Would be interesting for me at least.
    Also, did you add the function point sheets to your use case information sheet? I guess, that’s a grading criteria.

    But all in all a very detailled work, good job.

    Cheers,

    -RawBean-

    1. Hey RawBean,
      thank you for your feedback.
      Although our graph looked healthy it wasn’t but we fixed it.
      Concerning your question about the documentation, we have one page where we listed all use-cases, see https://gitlab.com/sasep-clairvoyance/sasep-documents/-/wikis/Function-Points. We also added the table to each use-case separately (e.g. https://gitlab.com/sasep-clairvoyance/sasep-documents/-/wikis/UC/Read-news#12-function-points), thanks for the advice.

      Best regards
      Marlon

  2. Hey SaSEp: Clairvoyance Team,
    Great work, your Blogentry is very clean and sorted.
    Your Funktion Points are almost to perfect on the line. But if those are your real FP’s there is nothing to improve.
    Best regards
    TrackYourFit

    1. Hello Johannes,
      thanks for the feedback.
      I wouldn’t say that our FPs are perfectly on the line as the line is only calculated based on two use-cases. So we don’t know how accurate it really is. Hopefully it will become better in the future.

      Best regards
      Marlon

Leave a comment

Leave a Reply to Johannes Cancel reply

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.