Hey guys!
Today we want show you our function point estimations. Function points are used for estimating the time that will be spent on a certain Use Case. They are calculated in reference on External Inputs, Outputs, Inquiries as well as Internal and External Logical Files from the User’s view, thereby they do not depend on the used technology.
To estimate how long it will take to implement a Use Case, function points of UC that have been already implemented are put in relation to the time we spent on it.
We used the calculation for our function points from „TINY TOOL„.
This table shows our Use Cases with the time we needed to implement. The acronyms DET, RET and FTR mean Data Element Type, Record Element Type and File Type Reference. Through these we identified the complexity which can be low, average or high. The part „numbers of“ are the numbers for the measurement parameter of the TINY TOOL.
Here you can see our Complexity Adjustment Table:
Here you can see the Domain Characteristic Table for the Use Case “Choose Room, Workout or Level”:
Below you can see our Use Case:
- Change server address (Completed)
- Choose room, workout, level (New)
- Create a room (New)
- Create an exercise (New)
- Workout activity flow (Old)
- Workout license (Old)
At last you can see the FP calculation and time Estimation diagram:
We have two outliners. “Workout acivity flow” (the blue one on the top) and “Choose room, workout and level” (the right one). Reasons for the the first outliner is the prework, which was very heavy -> Setup network connection, get minor Xamarin problems fixed. The other use cases benefited from this use case. The last outliner is just the complexity of Xamarin, which results in large function points and hours to develop.
Greetings,
WhiteCode 🙂
WhiteCode-TINF15B4 
