usecase: Sessions

public usecase: Sessions
Project: Phase: 1.0; Status: Proposed; Version: 1.0; Complexity: 1
Dates: Created: 6.12.2005 17:10:40; Modified: 14.12.2005 8:53:01;
Flags: Active: false; IsRoot: false; IsLeaf: false;
Extension Points:
UUID: {92DE49A7-E49A-44c0-8411-E84AA93E8926}

Goto: Scenarios

See also: User, Program

Appears in: Database administration, UC Main application

Sessions Scenarios
Scenario Type Detail
About Basic Path Application has to have exactly one open session. Information about current session are in SessionInfo object (Id, name, ...). This information is the same as information in database (table wrk_session).
On initial, there is empty session (without versions).
User can:
- create new session
- open existing session
- close current session.
Anytime, if some session is opened and contains at least one version, all three operations cause close current session. For mor detail see Close current session.