[Type here]

Case Tools Lab-1

Name: B. Vishal(14MSE0079)
Hassan(14MSE0153)
Rohith Varma(14MSE0132)
Anugu Prasanth
Faculty: Dr.KamalaKannan J
Slot:L43+44+45+46

[Type here]

Table of Contents
1.

Use Case Name

1.1 Brief Description

2.

Flow of Events
2.1 Basic Flow
2.2 Alternative Flows
2.2.1 < First Alternative Flow >
2.2.2 < Second Alternative Flow >

3.

Special Requirements
3.1 < First special requirement >

4.

Preconditions
4.1 < Precondition One >

5.

Post Conditions
5.1 < Post condition One >

6.

Extension Points
6.1 <name of extension point>

[Type here]

1. Use cases
A use case describes a sequence of interactions between a user and system, without specifying
the user interface. Use cases describe the system functions from the perspective of external users
and in a manner and terminology they understand.
List of use cases are:

Add department
Login
Add question
Manage student group
Student registration
Appear for test
Result generation

1.1. Use case description

Add Department

Use case name

Primary Actor(s)
Description
Precondition
Post condition

Add Department
Administrator
Adding new department to the institution.
The administrator first knows the department
code and department name.
Department is added.

[Type here]

Basic courses of action

1.
2.
3.
4.
5.

Administrator wants to add department in to database.

The Administrator looks the department code and department name.
The Administrator adds the department by name and code of the department.
Department is added.
The use case ends

Alternative course of action

Alternative course of action A: if the department has no code
A.2 The administrator gives it a code.
A.3 Go to step 3.

Add Question Use Case

Use case name

Primary Actor(s)
Description
Precondition
Post condition

1.
2.
3.
4.
5.
6.
7.

Add Question
Department
Adding questions according to the courses.
The department first knows course code.
The question is added.
Basic courses of action

Department wants to add questions into database.

The Department looks the course name and course code.
The department looks for the options.
Give the answer for the questions
The Department adds the question by name of the course and course code.
The question is added.
The use case ends

Alternative course of action

Alternative course of action A: if the course has no code.
A.2 The department gives it a code.
A.5 Go to step 5.

[Type here]

Login Use Case

Use case name

Primary Actor(s)
Description
Precondition
Post condition

1.
2.
3.
4.
5.
6.

Login
Administrator, User and Department.
Login into the system.
All authorized has the user name and password
The system accepts user name and password.
Basic courses of action

All authorized user wants to login into the system.

User first must have username and password.
User enters their user name and password.
The system checks the user name and password.
The system accepts user name and password.
The use case ends

Alternative course of action

Alternative course of action A: if the users have no user name and password.
A.2 Users create their own new account.
A.3 Go to step 3.
Alternative course of action B: if the entered user name and password is wrong.
B.3 Try with another user name and password.
A.4 Go to step 4.

Student Registration Use Case

Use case name

Primary Actor(s)
Description
Precondition
Post condition

Student Registration
Department.
Department register the students.
Students send all their own required
information.
Students are registered.

[Type here]

Basic courses of action

1.
2.
3.
4.
5.
6.

Students send all their own required information.

Department looks for the student information.
The department groups the students according to their department name.
Department fill all required student information.
Students are registered.
The use case ends.

Alternative course of action

Alternative course of action A: if the student did not send all their own required information.
A.1 the department announced them to send their own full information.
A.2 Go to step 2.

Appear for Exam Use Case

Use case name

Primary Actor(s)
Description
Precondition
Post condition

1.
2.
3.
4.
5.
6.
7.

Appear for the exam

Student.
Student can appear for the exam on the time.
Student must be login by their name, IDno and
their password.
Submit the answer.
Basic courses of action

Student wants to take the exam.

Student must be login by their name, IDno and their password.
Then the students search the posted questions by questionId.
Start answering the questions.
Finish in a given time.
Submit the answer.
The use case ends.

Alternative course of action

Alternative course of action A: if the student did not finish all the given question in given time

[Type here]

A.6 The student should have to submit what they answered.

A.7 Go to step 7.

Result Generation Use Case

Result Generation
Department and System.
Department generates the result by calculating
the submitted answer by student
System gets submitted answers.
Result is generated.
Basic courses of action

Use case name

Primary Actor(s)
Description
Precondition
Post condition

1.
2.
3.
4.
5.
6.
7.
8.

System gets submitted answers.

System checks answer.
System counts correct answer
System counts wrong answer.
The system calculates the mark.
Department posts the results.
Result is generated.
The use case ends.
Alternative course of action
Alternative course of action A: if the posted result is wrong
A.2 The system checks the answer.
A.3 Go to step 3.

1.2. Actor description

Actors are external entities that interact with the system. Actor initiates system activities for the
purpose of completing some task.
So actors in this project are as follows:

Administrator:-Super user, adds department and manages system.

Student:-User mostly a student who will appear for the examination.
Department:-Another user mostly department member, lecturer or
examiner who posts set of questions, the available options and correct
answers.
System:-is the system which checks users or administrators inputs.

[Type here]

1.3. Use case diagram

[Type here]

1.4. Add question Use Case

[Type here]

1.5. Appear for Test Use Case

[Type here]