Vishwakarma Institute of Technology, Pune-37.

<Organization>

Online Hostel Management System

Use Case Template

10-17-2021

Version 1.0

Approvals Signature Block

Project Responsibility Signature Date

Project Guide (Internal)
Project Guide (External)
Documentation Leader

Department of Computer Engineering

 Use Case Template

The document in this file is for UML Use Case Documentation Specifications, which
conforms to the requirements of UML 2.0.

Items that are intended to stay in as part of your document are in bold; blue italic text is
used for explanatory information that should be removed when the template is used.

2 v. 1.0 2006
 Use Case Template

Table of Contents
1. GENERAL INFORMATION................................................................................................................3
1.1 VERSION CONTROL..................................................................................................................... 4
1.2 INFORMATION DETAILS................................................................................................................ 4
2. USE CASE TEMPLATE.....................................................................................................................4

USE CASE #....................................................................................................................................................4

3. USE CASE SPECIFIER LIST............................................................................................................6

3.1 USE CASE ID............................................................................................................................... 6
3.2 USE CASE NAME......................................................................................................................... 6
3.3 USE CASE HISTORY..................................................................................................................... 6
3.3.1 Created By................................................................................................................................6
3.3.2 Date Created.............................................................................................................................6
3.3.3 Last Updated By.......................................................................................................................6
3.3.4 Date Last Updated....................................................................................................................6
4. USE CASE DEFINITION LIST..........................................................................................................6
4.1 ACTORS....................................................................................................................................... 6
4.2 TRIGGER...................................................................................................................................... 6
4.3 DESCRIPTION............................................................................................................................... 6
4.4 PRECONDITIONS........................................................................................................................... 7
4.5 POSTCONDITIONS......................................................................................................................... 7
4.6 NORMAL FLOW............................................................................................................................ 7
4.7 ALTERNATIVE FLOWS.................................................................................................................. 7
4.8 EXCEPTIONS................................................................................................................................ 7
4.9 INCLUDES.................................................................................................................................... 7
4.10 PRIORITY..................................................................................................................................... 8
4.11 FREQUENCY OF USE..................................................................................................................... 8
4.12 BUSINESS RULES.......................................................................................................................... 8
4.13 SPECIAL REQUIREMENTS.............................................................................................................. 8
4.14 ASSUMPTIONS.............................................................................................................................. 8
4.15 NOTES AND ISSUES...................................................................................................................... 8
5. APPENDIX............................................................................................................................................8

3 v. 1.0 2006
 Use Case Template

1. GENERAL INFORMATION

Fill in the following details to keep trace of Project Phases and Iterations.

Informational Item Information

Document Title Use Case Analysis Document
Version 1.0
Subtitle .
Author Shresthi Yadav and Nitesh Sonawane
Project Name Online Hostel Management System
Project Phase Phase 1
Project Iteration 1

1.1 VERSION CONTROL

Fill in the following details to keep trace of Versioning Details.

Date Version Description Author

Oct-18-2021 1.0 Created Shresthi Yadav and
Nitesh Sonawane

1.2 INFORMATION DETAILS

Fill in the following details to keep trace of information that you are generating.

Informational Item Information

Filename C:\Users\shres\Dropbox\My PC (LAPTOP-BELTKPQ4)\Downloads\SDAM
Last Saved On Monday, October 18, 2021, 10:13:00 AM
Last Saved By Shresthi Yadav
Number of Pages 17

2. USE CASE TEMPLATE

USE CASE 1 LOGIN

Goal
To authenticate credentials for accessing the system
Purpose Authentication
Preconditions None

4 v. 1.0 2006
 Use Case Template

Success Condition User/ Admin is able to access the system if the credentials are entered to
be correct.
Failed Condition Authentication error occurs leading to no access to the system
Postconditions 1. The user is logged in to system
2. The user has access to the functions of the system
Primary Actors User/ Admin

Secondary Actors None

Trigger The user/ admin requests to login

DESCRIPTION Ste Basic Course of Action
p
1 The system prompts the user for their account credentials.
2 The user enters their username and password.
3 The system authenticates the login information.
DESCRIPTION Ste Alternate Course of Action
p
1 The user gains access to the systems functionality

2 Check for admin or user login.

DESCRIPTION Ste Extension Points
p
1 New registration
DESCRIPTION Ste Error Scenario
p
1 No access to the system functions
2 Incorrect credentials

5 v. 1.0 2006
 Use Case Template

USE CASE 2 Manage Profile

Goal To view and update the profile
Purpose To manage the profile
Preconditions The user logs in to the system and selects the manage profile option to
get an access to view and update their profile
Success Condition The user can successfully view their information and save the updated
information.
Failed Condition None
Postconditions Information can be viewed and modified.
Primary Actors User or the student is the primary actor

Secondary Actors None

Trigger The user requests to view and modify their information

DESCRIPTION Ste Basic Course of Action
p
1 The system shows the user their information and given an option to
modify it

6 v. 1.0 2006
 Use Case Template

2 The user modifies their details

3 The system saves the modified information
DESCRIPTION Ste Alternate Course of Action
p
1 User can directly contact with the admin to manually view or modify
their details.
DESCRIPTION Ste Extension Points
p
1 None
DESCRIPTION Ste Error Scenario
p
1 Data not saved due to poor internet connectivity
2 Incorrect details added

USE CASE 3 Booking Hostel

Goal
<Statement indicating the High-Level Expectation from Use Case>
Purpose <Secondary Level information indicating breaking Use Case into
Partitions>
<One of: Summary, Primary Task, Subfunction>

7 v. 1.0 2006
 Use Case Template

Preconditions <Condition that the Use Case Assumes to start its Functionality>
Success Condition <The state of the Use Case upon successful completion>
Failed Condition <The state of the Use Case if goal abandoned>
Postconditions <Condition that is Satisfied by the Use Case at exit >
Primary Actors <A role name or description for the primary actor>.

Secondary Actors <Other systems relied upon to accomplish use case>

Trigger <The action upon the system that starts the use case>
DESCRIPTION Ste Basic Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Alternate Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Extension Points
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Error Scenario
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3

8 v. 1.0 2006
 Use Case Template

USE CASE 4 Manage Course

Goal
<Statement indicating the High-Level Expectation from Use Case>
Purpose <Secondary Level information indicating breaking Use Case into
Partitions>
<One of: Summary, Primary Task, Subfunction>
Preconditions <Condition that the Use Case Assumes to start its Functionality>
Success Condition <The state of the Use Case upon successful completion>
Failed Condition <The state of the Use Case if goal abandoned>
Postconditions <Condition that is Satisfied by the Use Case at exit >
Primary Actors <A role name or description for the primary actor>.

Secondary Actors <Other systems relied upon to accomplish use case>

Trigger <The action upon the system that starts the use case>
DESCRIPTION Ste Basic Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>

9 v. 1.0 2006
 Use Case Template

3
DESCRIPTION Ste Alternate Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Extension Points
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Error Scenario
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3

10 v. 1.0 2006
 Use Case Template

USE CASE 5 Manage Students

Goal
<Statement indicating the High-Level Expectation from Use Case>
Purpose <Secondary Level information indicating breaking Use Case into
Partitions>
<One of: Summary, Primary Task, Subfunction>
Preconditions <Condition that the Use Case Assumes to start its Functionality>
Success Condition <The state of the Use Case upon successful completion>
Failed Condition <The state of the Use Case if goal abandoned>
Postconditions <Condition that is Satisfied by the Use Case at exit >
Primary Actors <A role name or description for the primary actor>.

Secondary Actors <Other systems relied upon to accomplish use case>

Trigger <The action upon the system that starts the use case>
DESCRIPTION Ste Basic Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Alternate Course of Action
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Extension Points
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3
DESCRIPTION Ste Error Scenario
p
1 <Narrate the steps of the scenario from trigger to goal delivery, and
any cleanup after>
2 <...>
3

11 v. 1.0 2006
 Use Case Template

RELATED INFORMATION <Use case name>

Priority: <How critical to your system / organization>
Superordinates <Optional, name of use case(s) that includes this one>
Subordinates <Optional, depending on tools, links to sub use cases>

3. USE CASE SPECIFIER LIST

3.1 USE CASE ID

Give each use case a unique integer sequence number identifier. Alternatively, use a
hierarchical form: X.Y. Related use cases can be grouped in the hierarchy.

3.2 USE CASE NAME

State a concise, results-oriented name for the use case. These reflect the tasks the user
needs to be able to accomplish using the system. Include an action verb and a noun.
Some examples:
 View part number information.
 Manually mark hypertext source and establish link to target.
 Place an order for a CD with the updated software version.

12 v. 1.0 2006
 Use Case Template

3.3 USE CASE HISTORY

3.3.1 Created By
Shresthi Yadav and Nitesh Sonawane

3.3.2 Date Created

October-17-2021

3.3.3 Last Updated By

Shresthi Yadav

3.3.4 Date Last Updated

October-18-2021

4. USE CASE DEFINITION LIST

4.1 ACTORS
The main actors of the use case are the admin and the user who perform different kinds
of use cases like login, registration, booking hostel, allot rooms, manage and view room
details as well as student profile and manage students.

4.2 TRIGGER
The Triggers for the system are:
The User decides to login to the system.
The User decides to accommodate the hostel and fill the registration form.
The User decides to book the hostel by adding their room details and personal
information.
The User decides to view or modify their personal details.
The User decides to view and print their room details.
The Administrator decides to login to the system
The Administrator decides to accommodate a student in the hostel and fills the
registration form.
The Administrator decides to issue the membership card to the student.
The Administrator decides to add significant course the following student is pursuing as
well as removes and updates or modifies it.
The Administrator decides to allot the room.
The Administrator decides to view the dashboard with various options (other use cases)
The Administrator decides to manage the student by removing the student from the
hostel as well as viewing their personal details.

4.3 DESCRIPTION
The User can login to the system if they are already registered or fill the registration form
to accommodate the hostel room. The Administrator can login to the system and

13 v. 1.0 2006
 Use Case Template

accommodate a student in the hostel by filling the registration form. The User can book
the hostel by adding their room details and personal information and the Administrator
can issue the membership card to the student. The User can view or modify their personal
details and also print their room details. The Administrator on the other hand can add
significant course the following student is pursuing as well as removes and updates or
modifies it and allots the room. The Administrator has the facility to view the dashboard
with various options (other use cases) and manage their data by removing the student
from the hostel as well as viewing their personal details.

4.4 PRECONDITIONS
The activities that must take place, or any conditions that must be true, before the use
case can be started are:
1. User’s identity has been authenticated.
2. System must be fully configured; appropriate user ID and passwords must be
obtained.
3. User’s computer has sufficient free memory available to launch task.

4.5 POSTCONDITIONS
The state of the system at the conclusion of the use case execution is:
1. The user must have an access to the functions of the system.

4.6 NORMAL FLOW

X.1 How do I get an access to the system?
The system can be accessed using the user login portal only if the user is registered by
the admin and filling the registration form and provided with the membership card and
an allotment to the hostel.

X.2 How do I book a room in the hostel?

Hostel room can be booked by selecting and filling the registration form from the
dashboard and further entering room related information and personal details.

X.3 How can I manage my profile?

Profile can be managed by selecting the manage profile section from the dashboard and
modifying the details and saving it.

X.4 How do I print my details?

User details can be printed by selecting the view room details option and further selecting
the print option.

4.7 ALTERNATIVE FLOWS

X.1 Different credentials have been allotted for users or admin depending upon their
authority and their rights. Such a feature makes the system decentralized.

14 v. 1.0 2006
 Use Case Template

X.2 Student Registration can be performed both by the admin and the user.

4.8 EXCEPTIONS
X.1 The system will show an authentication error if the login credentials of the user or
the admin are entered to be incorrect.

X.1, X.2, X.3 The system login or registration, modification of data cannot be possible if
there is an internet connectivity error and the data will not be saved.

4.9 INCLUDES
Issuing of membership card for the student and not just viewing the student details alone
but also generation of a PDF to print the data to save for later as a record.

4.10 PRIORITY
There are the requirements that are not directly related to the functionality of the system which
should be considered as mandatory when the system is developed. The following Constraints
were arrived at for the system:
For gaining entry into the system the admin should be able use login & passwords for gaining
access to the system.
The admin should be able to change their passwords for increased security.
The system should be easy to understand and organized in a structured way.

4.11 FREQUENCY OF USE

The use cases mentioned should be used frequently by the users and admin. The system
shall be available 24 hours a day.

4.12 BUSINESS RULES

Business rule states the on-time submission of the duly mentioned cases which includes
the effective updating of the databases for sound consistency.

15 v. 1.0 2006
 Use Case Template

4.13 SPECIAL REQUIREMENTS

The system needs to be deployed on a good support of network resources, which most of
the recent servers are capable of running in their native state. The specific use-cases aim
to receive the RAM of 4 GB (minimum).

4.14 ASSUMPTIONS

The assumptions made were that the system software’s would be running on a duly
suitable environment, supporting high-scale massive infrastructural capabilities.

4.15 NOTES AND ISSUES

16 v. 1.0 2006