Object-Oriented Analysis and Design - Experiment 2 Use Case Event Flow Description (Daily Punch)



1.  Daily check-in 

1.1  Brief description

This use case allows registered members to check in. The premise is to complete 10,000 steps or more on the day . 

1.2  Event Stream

1.2.1  Elementary Stream

This use case starts when the user turns on the system and closes when logging out / login .

1. .Detect if the member is walking or exercising

   1. If there is a motion state, the step counting system will accumulate the number of steps.

   2. If there is no movement state, the function of suspending cloth counting will be enabled to save memory.

2. At 23:59:59 every day , the step counting system will count the total number of steps on the day with the Beijing time reset .

3. If the number of steps exceeds 10,000 steps, you can check in, and the credit points will increase. If you log in continuously, the points will increase exponentially.

4. If there is a malicious punch-in behavior such as a member instead of punching the card , and the gym administrator exercises supervisory privileges , the credit points of both parties will be deducted .

1.2.2  Alternative Streams

1.2.2.1  Supplementary punch card

If in the basic process, members reach 10,000 steps but forget to check in, they can make up for the check-in operation for up to 3 days .

1.2.2.2  Time system unavailable

If the system cannot communicate with the time system, the system will attempt to resend the request without interruption until the time system becomes available.

1.3  Special requirements

without.

1.4  Precondition

The check-in function is available only after logging in to the system.

1.5  Postconditions

If the sign - in is successful, go back to the main interface . Otherwise, the system state remains unchanged.

1.6  Extension points

without.