gobliip / time-tracker Goto Github PK

New Moment Type: Heartbeat

• This type allows us to register heartbeat moments that require no extra metadata.
• This type denotes that the tracking is still being used by the client at a certain instant in the timeline.

Work Session

Fields

• Tracking tracking: The tracking used in for the work session
• WorkSessionStatus status: The current status of the work session (LOGGING,PAUSED,IDLE,FINISHED)
• List<WorkPeriod> loggedPeriods: All WorkPeriod related to the session
• WorkPeriod lastPeriod: The last logged WorkPeriod

Rules

• A user can only have a WorkSession.status == LOGGING at any time
• loggedPeriods start date should always be between tracking.start and tracking.end
• loggedPeriods end date should always be between tracking.start and tracking.end

As a user tracking of time-tracker

• I should be able to
• then: I shoud be able to <add a timestamped attachment/memo> to the tracking session.

As a user with a running tracking session in time-tracker:

• I shoud be able to <add a timestamped attachment/memo> to the tracking session.

WorkPeriod Spec

Fields

• Moment start: represents the period start point in the timeline. It can only be a moment of the next types: START, RESUME, HEARTBEAT
• Moment finish: represents the period end point in the timeline. It can only be a moment of the next types: STOP, PAUSE, HEARTBEAT
• WorkPeriod parent: The parent workperiod
• int keyboardActions: Number of keyboard actions registered for this period
• int mouseActions: Number of mouse actions registered for this period

Rules

• WorkPeriod should always have a parent unless start.type == START || start.type == RESUME
• WorkPeriod should always parent.stop.when <= this.start.when
• WorkPeriod mouseActions > 0 || keyboardActions > 0