Skip to content

Use cases

weinzmi edited this page Dec 23, 2018 · 6 revisions

Usecases are following the documentation rules below:

Use Case Element Description
Use Case Number ID to represent your use case
Application What system or application does this pertain to
Use Case Name The name of your use case, keep it short and sweet
Use Case Description Elaborate more on the name, in paragraph form
Primary Actor Who is the main actor that this use case represents
Precondition What preconditions must be met before this use case can start
Trigger What event triggers this use case
Basic Flow The basic flow should be the events of the use case when everything is perfect; there are no errors, no exceptions. This is the "happy day scenario". The exceptions will be handled in the "Alternate Flows" section.
Alternate Flows The most significant alternatives and exceptions

UC001 - 150W fixed power training

Use Case Element Description
Use Case Number 001
Application ergoFace usage and training
Use Case Name 150W fixed power training
Use Case Description a person whats to start a training session with a fixed power rate of 150W on the DAUM. He is going to start from 0 cadence and then pedal with a variable cadance between 50 - 110 RPM. The break performance of the DAUM has to be constant 150W except the minimum cadence of ???RPM or below is reached, so the ergoFACE has to drop the wattage to 25W to enable the person to pedal again. After a training of 5min, the person stops pedaling and the cadence is 0, switches off the DAUM and ergoFACE
Primary Actor any person
Precondition DAUM plugged to the power supply; ergoFACE plugged to the DAUM; mobile device connected to WiFi; open website of ergoFACE webserver; wattage set to 150W
Trigger Training
Basic Flow switch on DAUM & ergoFACE, use the mobile device to browse to the webserver of ergoFACE, set set point value for wattage to 150w and apply, star pedaling, training for 5min with variable cadence, stop pedaling, turn off DAUM & ergoFACE
Alternate Flows during training, drop cedance to 0 and start pedaling again

Basic State Diagram - Use case 001

UC002 - save and view training session

Use Case Element Description
Use Case Number 002
Application ergoFace usage and training
Use Case Name save the training session of UC001 and view it afterwards
Use Case Description same as UC001, but befor the person switches off the DAUM and ergoFACE, the person is "saving" the training session, waiting for confirmation of saving, switching off the DAUM and ergoFACE, switches on ergoFACE again (not the DAUM), reconnects to webserver, browses to saved trainings and open the saved training, views it.
Primary Actor any person
Precondition see UC001
Trigger Training
Basic Flow TBD
Alternate Flows TBD
Clone this wiki locally