TO DO:

2-11
12-17

18-35
36-52

53-100

101-112

113-124
125-136

137-145
146-154
Software Requirement Specification Document

For

PASSPORT AUTOMATION SYSTEM

Prepared by

JUNAID SHAIK(23BCE8679)

School of Computer Science and Engineering

 1. Class Diagram -

In software engineering, a class diagram in the Unified Modelling Language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationship s among objects.

In the diagram, classes are represented with boxes that contain three compartments:
The top compartment contains the name of the class. It is printed in bold and centred, and
the first letter is capitalized.
The middle compartment co ntains the attributes of the class. They are left-aligned and the
first letter is lowercase.
The bottom compartment contains the operations the class can execute. They are also left -
aligned and the first letter is lowercase.

The classes in the following class diagram are -

.PassportAutomationSystem : -

1.1. Attributes

1.1.1. char Option

1.2. Methods 1.2.1.

UserOrAdmin() - Selects whether the actor is USER or ADMIN.:

. User:-

2.1. Attributes

2.1.1. String LoginId

2.1.2. String Password

2.2. Methods

2.2.1. displayDetails() - Displays the user details

AdminLogin
Attributes

o AdminLoginId

o AdminPassword

Methods

o login() - Getting access to the admin account.

AdminAuthentication

Attributes

o PendingApplications

o Dispatched Passports






 o ApplicationId

Methods

o process() - Processes the requests generated by Admin.

NewUser
Attributes

o String Name

o String DOB

o Char Gender

o String EmailId

o Long MobileNo.

Methods

o submit() - Submits the User information to the Database.

o register() - Registers the user to the portal.

o cancel() - Discards the user input details.

RegisteredUser
Attributes

o String LoginId

o String Password

. Methods

* UploadDocs() - Uploads the user documents to the portal.

* CheckApplicationStatus() - Checks the Application status of the applicant.

* Paymentprocess() - Displays the various modes of fees payments.

* SelectApointmentDate() - Provides the list of available dates to select the appointment





 2. STATE DIAG RAM :-

A State chart diagram describes a state machine. State machine can be defined as a machine

which defines different states of an object and these states are controlled by external or internal

events.

Activity diagram explained in the next chapter, is a special kind of a State chart diagram. As State

chart diagram defines the states, it is used to model the lifetime of an object.

Following are the main purposes of using State chart diagrams -

To mode l the dynamic aspect of a system.

To model the life time of a reactive system.

To describe different states of an object during its life time.

Define a state machine to model the states of an object.





3. DATA FLOW DIAGRAM : -

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an information
system, modeling its process aspects. A DFD is often used as a preliminary step to create an overview
of the system without going into great detail, which can later be elaborated. DFDs can also be used
for the visualization of data processing (structured design).

A DFD shows what kind of information will be input to and output from the system, how the data will
advance through the system, and where the data will be stored. It does not show information about
the timing of process or information about whether processes will operate in sequence or in parallel
unlike a flowchart which also shows this information
 4. USECASE DIAGRAM : -

To model a system, the most important a spect is to capture the dynamic behavior. Dynamic behavior
means the behavior of the system when it is running/operating.

Only static behavior is not sufficient to model a system rather dynamic behavior is more important
than static behavior. In UML, there are five diagrams available to model the dynamic nature and use
case diagram is one of them.

The internal and external agents are known as actors. Use case diagrams consists of actors, use cases
and their relationships.

In brief, the purposes of use case diagrams can be said to be as follows -

Used to gather the requirements of a system.

Used to get an outside view of a system.

Identify the external and internal factors influencing the system.

Show the interaction among the requirements are actors





 5. ACTIVITY DIAGRAM : -

Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system.

Activity diagram is basically a flowchart to represent the flow from one activity to another activity.
The activity can be desc ribed as an operation of the system.

The control flow is drawn from one operation to another. This flow can be sequential, branched, or
concurrent.

The purpose of an activity diagram can be described as -

Draw the activity flow of a system.

Describe the sequence from one activity to another.

Describe the parallel, branched and concurrent flow of the system.




 6. SEQUENCE DIAGRAM -
UML Sequence diagrams are used to represent or model the flow of message, events or
action between the objects and components of the system.
It is primarily used to design document and validate the architecture, interfaces and logging
to the system.
Sequence diagrams provide a dynamic view to the system behaviour which can be difficult to
extract from static diagrams or specifications.
In the sequence diagrams the time is represented in the vertical direction showing the
sequence of interaction of the he ader element.




 7. DEPLOYMENT DIAGRAM -
Deployment diagrams are used to visualize the topology of the physical component their
distribution and association of a system where the software components are deployed.
Component diagrams are used to describe the component and deployment diagram shows
how they are deployed in hardware.
UML is mainly designed to focus on software artifacts of a system. But these two diagrams
are used to focus on software component and hardware component.
The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles
within the boxes. Node may have sub nodes, which appear as nested boxes.
A single node in a deployment diagram may conceptually represent multiple physical nodes,
such as a cluster of database servers.
The usage of deployment diagrams can be described as follow:

o To model the h/w topology of a system.

o To model embedded system.

o To model h/w details for a client / server system.

o To model h/w details of a distribution application.

o Forward and reverse engineering.







Software Requirement Specification Document

For

BOOK BANK

Prepared by

Junaid Shaik(23BCE8679)

School of Computer Science and Engineering

 USE CASE DIAGRAM

A use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. The use case is made up of a set of possible sequences of interactions between
systems and users in a particular environment and related to a partic ular goal. It is represented using
ellipse.

Actor is any external entity that makes use of the system being modeled. It is represented using stick
figure.

The actors in this use case diagram are member and database. The use cases are the activities
performed by actors.
The member will register himself in the book bank.

After registration he will select the year to which he belongs

After selecting he will select books

Database will verify the status of book and the books will be given.

CLASS DIAGRAM

A class diagram in the unified modeling language (UML) is a type of static structure diagram that
describes the structure of a system by showing the system's classes, their attributes, and the
relationships between the classes. It is represented using a rectangle with three compartments. Top




compartment have the class name, middle compartments the attributes and the bottom
compartment with operations

a class diagram with 8 classes:

1. Member details class : Attributes include name, father name, date of birth, address, phone
number, member id, college, degree, course, and semester. Operations are registration,
authentication, and year selection.

2. Administrator: Attributes include name, address, phone, and mail id. Operations are
authentication, verification, and issuing books.

3. Year: Attribute is year selection. Operations are 1st1st year, 2nd2nd year, 3rd3rd year,
and 4th4th year.

4. Issue for 1st1st year: Attributes include member code, member name, book code, book
name, and quantity. Operation is issue.

5. Issue for 2nd year: Attributes include member code, member name, book code, book name,
and quantity. Operation is issue.

6. Issue for 3rd year : Attributes include member code, member name, book code, book name,
and quantity. Operation is issue.

SEQUENCE DIAGRAM

A s equence diagram in Unified Modeling Language (UML) is a kind of interaction diagram that shows
how processes operate with one another and in what order. It is a construct of a Message Sequence
Chart. There are two dimensions.

1. Vertical dimension -represen t time.

2. Horizontal dimension -represent different objects.

 The sequence diagram describes the sequence of steps to show
The member registers himself in book bank

He will select the year

He select the books given and the database will update the status of b ook.

Then administrator will log in and verify the status of books.

If the book is available he will issue the book

STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in performing a
method. It is also called as state diagram. A state is represented as a round box, which may
contain one or more compartments. An initial state is represented as small

dot. An final state is represented as circle surrounding a small dot

This state diagram describes the behavior of the system.

In the first state the member registers himself in book bank.

After that he will select the year in next state.

In the next state he will select the books.

In the next state database will update the status of book.

In the next state administ rator will log in.

After authentication he will verify the availability of book.












 If available he will issue the book.

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice , iteration and concurrency.

In the Unified Modeling Language, activity diagrams can be used to describe the business and
operational step -by-step workflows of components in a system. An activity diagram shows the
overall flow of control. An activity is shown as an rounded box containing the name of the operation

This activity diagram flow of stepwise activities performed in book bank management system.

The member registers himself in book bank

After that he will select the year.

He will select the books .

Database will update the status of book

Database will update the details

Then the administrator will log in to his account.

After authentication he will verify the availability of book.

If available he will issue the book










DEPLOYMENT DIAGRAM

A deployment diagram in the unified modeling language serves to model the physical deployment of
artifacts on deployment targets. Deployment diagrams show "the allocation of artifacts to nodes
according to the Deployments defined between them. It is represen ted by 3-dimentional box.
Dependencies are represented by communication association.

The processor in this deployment diagram is the book bank which is the main part and which are the
some of the main activities performed in the system. And issue for firs t year, issue for second year
issue for third year and issue for fourth year are some activities performed in this system.
 Software Requirement Specification Document

For

ONLINE EXAM REGISTRATION

Prepared by
J YASHWANTH(23BCE9747)

School of Computer Science and Engineering

 SOFTWARE ENGINEERING
EXPERIMENT 1
1. Problem Statement: The Online Exam Registration System enables students to register for exams
efficiently, ensuring proper validation and management. It allows students to create accounts, browse
available exams, check eligibility, make secure payments, and receive confirmation. Administrators can
manage exam schedules, student registrations, and generate reports. The system ensures seamless
registration with real-time notifications, preventing errors like overlapping exams or missed deadlines. By
automating the process, it reduces manual workload, enhances ac curacy, and provides a user -friendly
experience for both students and administrators.

2. Preparation of Software Requirement Specification Document:

1. User Characteristics

Student: Students register for exams by submitting their details to the database. They can view
available exams, register, make payments, and receive confirmation.

Administrator: The administrator (exam coordinator) has privileges to manage exams, approve
registrations, update schedules, and oversee the registration process.

2. System Modul es

Login & Authentication: Secure registration for students and administrators via an online form with
username and password credentials.

Exam Management: The system contains all available exams. New exams are added with details like
exam ID, subject, date , time, and eligibility criteria. Exams can be deleted if canceled, and updates
can be made to the exam details.

Operations: Students can register for exams, pay fees, and view their registration details.
Administrators can add, update, and remove exams, v erify student registrations, and manage
schedules.

3. Non -Functional Requirements

Privacy: User data is secured with credentials (username and password) to ensure privacy.

Portability: The system should be installable on multiple platforms and support web -based access
for ease of use.







3. Preparation of Software Configuration Management

Software Requirements:

Operating sytem: windows 7/10

Front end : J2EE

Back end : My SQL Server

IDE used : Netbeans

Hardware Requirements:

Processor:i3 or higher

RAM : 4 GB

Hard Disk drive: 500 GB

1. Study and usage of any Design phase CASE tool

CASE Tool: STARUML

How to Install StarUML on Windows 10

Star UML is a UML ( Unified Modeling Language ) tool, introduce by MKLab. It is an open - source
modeling tool that supports the UML framework for system and software modeling. StarUML
is based on UML version 1.4, it provides 11 different types of diagram and it accepts UML 2.0
notation. Version 2.0 was released for beta testing under a property license.

StarUML is actively supporting the MDA (Model Driven Architecture). It approaches by

supporting the UML profile concept and allowing it to generate code for multiple languages. It
also provides a number of bug fixes and improved compatibility with the modern versions of
the Windows Operating System.

StarUML is mostly used by the Agile and small development teams, professional persons and
used by the educational institutes
Diagram Types in StarUML

1. Use Case Diagram

2.Sequence Diagram

3.Class Diagram

4.Collaboration Diagram

5.Statechart Diagram

6.Component Diagram

7.Deployment Diagram

8. Composite Structure Diagram

Features of StarUML

1. It supports multi- platform such as macOS, Windows, and Linux.

2. It involves UML 2.x.standard compliant.

3. Includes Entity- Relationship diagram (ERD), Data- flow diagram (DFD), and Flowchart
diagram.

4. It creates multiple windows.

5. It has modern UX and dark and light themes.

6. Featured with retina (High- DPI) display support.

7. Includes model- driven development.

8. It has open APIs.

9. Supports various third - party extensions.

10. Asynchronous model validation.

9
 11. It can export to HTML docs.

Steps to Download and Install StarUML

Step 1: Go on the browser, type in the URL “StarUML”

Step 2: Click on the very first search “Download - StarUML”.

Step 3: There will be 3 Operating Systems (OS) options, click on the option as per the devise
OS.

Step 4: Now, right - click on the downloaded file, select “Show in Folder” option.

Step 5: Click on the open file, a popup wind ow opens, click on the “Yes” button.

Step 6: Installation gets start. After installation popup opens to ask to buy a license. If you
want to click on the “Buy Now” button or else close that window. StarUML is ready to use.

2. Performing the Design by using any Design phase CASE tools

CASE Tool: StarUML

Use Cases:

1. Student Registration

2. Exam Enrollment

3. Payment Processing

4. Generate Admit Card

5. View Exam Schedule

Actors Involved:

6
 1. Student

2. Admin

3. Payment Gateway

Use Case Details

Use Case Name: Student Registration

Initiated by: Student

Precondition: The student should provide valid personal details.

Normal Flow: The student enters details such as name, email, phone

number, and creates a password.

Post Condition: Student account is created, and login credentials are

generated.

Use Case Name: Exam Enrollment

Initiated by: Student

Precondition: The student must have a registered account.

Normal Flow: The student selects the exam, chooses the preferred

exam center, and submits the form.

Alternative Flow: If the exam slot is full, the student will be asked to

select another available slot.

7








 Post Condition: The exam seat is reserved for the student.

Use Case Name: Payment Processing

Initiated by: Student

Precondition: Student should have successfully selected an exam.

Normal Flow: The system redirects the student to the payment

gateway for fee submission.

Alternative Flow: If the payment fails, the system prompts the user to

retry.

Post Condition: Upon successful payment, the exam registration is

confirmed.

Use Case Name: Generate Admit Card

Initiated by: Admin/System

Precondition: The student must have completed the registration and

payment process.

Normal Flow: The system generates the admit card with exam details.

Post Condition: The student can download the admit car d for

examination entry.

8










 Use Case Name: View Exam Schedule

Initiated by: Student

Precondition: The exam schedule must be updated in the system by the

admin.

Normal Flow: The student logs in and views the available exam

schedule.

Post Condition: The student is informed about the exam date and time.

Figure 1. Use case diagram for Online Exam Regestration

9




Activity Diagram:

Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
can be used to describe the business and operational step - by- step workflows of components in a

system. An activity diagram shows the overall flow of control. An activity is shown as an rounded
box containing the name of the operation.
This activity diagram describes the behaviour of the system.

Figure 2. Activity Diagram for Online Exam Regestration

10
Sequence Diagram:
A sequence diagram represents the sequence and interact ions of a given USE - CASE or scenario.
Sequence diagrams can capture most of the information about the system. Most object to object
interactions and operations are considered events and events include signals, inputs, decisions, interrupts,
transitions and actions to or from users or external devices.

An event also is considered to be any action by an object that sends information. The event line
represents a message sent from one object to another, in which the “form” object is requesting an
operation be performed by the “to” object. The “to” object performs the operation using a method that the
classcontains.

It is also represented by the order in which things occur and how the objects in the system send
message to one another.

Figure 5. Sequence Diagram For online exam regestration

11
Figure 6. Collaboration Diagram For Book Issue & Return

12
 Class Diagram:

The class diagram, also referred to as object modeling is the main static analysis diagram. The main
task of object modeling is to graphically show what each object will do in the problem domain. The
problem domain describes the structure and the relationships among objects.

The Online Exam Registration System consists of six main classes: Student, Exam, Registration,
Payment, Admin, and Notification. The Student class stores student details such as studentID, name,
DOB, email, contact number, department, course, year, and credentials, with operations like registering,
deleting, and updating student information. The Exam class manages exam- related details, including
examID, subject name, date, duration, total marks, eligibility criteria, and fee, along with operations to add,
update, delete, and view exams. The Registration class tracks exam enrollments, storing registrationID,
studentID, examID, registration date, and status, with operations for registering and canceling registrations.
The Payment class ensures secure fee transactions by handling paymentID, studentID, examID, amount,
payment date, and payment status, with functio ns for processing and verifying payments. The Admin class
allows administrators to manage students, exams, and registrations, storing adminID, name, email, contact
number, and credentials, with operations to manage student and exam records. Lastly, the Not ification class
manages communication, storing notificationID, studentID, message, and timestamp, with functions to send
and view notifications. This structured system ensures a smooth and secure exam registration process for
both students and administrato rs.

13
Figure 7. Class Diagram For Book Bank System

14
Deployment Diagram and Component Diagram
Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed.

Figure 8: Deployment Diagram for Book Bank System

15
State chart diagram

ER diagram

16
17
18
 Software Requirement Specification Document

For

STOCK MAINTAINANCE SYSTEM

Prepared by
J YASHWANTH(23BCE9747)

School of Computer Science and Engineering

 SOFTWARE ENGINEERING
EXPERIMENT 1
1. Problem Statement: The Stock Maintenance System is designed to help
businesses efficiently track and manage inventory, preventing overstocking,
understocking, and discrepancies. It enables users to add, update, and delete
stock items, monitor stock levels with alerts, categorize inventory, and manage
p urchases and sales. The system also provides real - time reporting on stock
levels and trends, ensuring informed decision - making. With user roles and
permissions, it secures inventory data while offering a scalable, user - friendly
solution for businesses of a ll sizes.

2.Software Requirement Specification (SRS) for Stock Maintenance System

1. User Characteristics
Store Manager: Responsible for overseeing stock levels, adding new items, updating inventory
details, generating reports, and managing supplier information.
Sales Staff: Can view stock availability, process sales transactions, and update stock quantities after
sales.
Administrator: Has full system privileges, including managing user roles, auditing stock records,
and setting access permissions.
2. System Modules
Login & Authentication: Secure access for different users (store managers, sales staff, and
administrators) wi th role -based permissions.
Stock Management: Allows users to add, update, and remove stock items with details like item ID,
name, quantity, supplier, and category.
Inventory Tracking: Monitors stock levels in real time, triggers low - stock alerts, and maint ains






 stock movement history.
Sales & Purchase Management: Records incoming stock (purchases) and outgoing stock (sales),
linking them with invoices and suppliers.
Reporting & Analytics: Generates reports on stock levels, sales trends, purchase history, and
restocking needs for informed decision - making.
3. Non- Functional Requirements
Security & Privacy: User authentication ensures secure access, and sensitive inventory data is
protected with encryption.
Scalability: The system should support businesses of va rying sizes and handle large datasets
efficiently.
Portability: It should be accessible via web and mobile platforms for ease of use and remote
inventory management.
Would you like any modifications or additional details?

3Preparation of Software Configuration Management

Software Requirements:

Operating sytem: windows 7/10

Front end : J2EE

Back end : My SQL Server

IDE used : Netbeans

Hardware Requirements:

Processor:i3 or higher

RAM : 4 GB





Hard Disk drive: 500 GB

1. Study and usage of any Design phase CASE tool

CASE Tool: STARUML

How to Install StarUML on Windows 10

Star UML is a UML ( Unified Modeling Language ) tool, introduce by MKLab. It is an open - source
modeling tool that supports the UML framework for system and software modeling. StarUML
is based on UML version 1.4, it provides 11 different types of diagram and it accepts UML 2.0
notation. Version 2.0 was released for beta testing under a property license.

StarUML is actively supporting the MDA (Model Driven Architecture). It approaches by

su pporting the UML profile concept and allowing it to generate code for multiple languages. It
also provides a number of bug fixes and improved compatibility with the modern versions of
the Windows Operating System.

StarUML is mostly used by the Agile and sm all development teams, professional persons and
used by the educational institutes

Diagram Types in StarUML

1. Use Case Diagram

2.Sequence Diagram

3.Class Diagram

4.Collaboration Diagram

5.Statechart Diagram

6.Component Diagram

7.Deployment Diagram

8. Composite Structure Diagram

Features of StarUML

1. It supports multi -platform such as macOS, Windows, and Linux.

2. It involves UML 2.x.standard compliant.

3. Includes Entity -Relationship diagram (ERD), Data - flow diagram (DFD), and Flowchart
diagram.

4. It creates multiple windows.

5. It has modern UX and dark and light themes.

6. Featured with retina (High -DPI) display support.

7. Includes model - driven development.

8. It has open APIs.

9. Supports various third -party extensions.

10. Asynchronous model validation.

9
 11. It can export to HTML docs.

Steps to Download and Install StarUML

Step 1: Go on the browser, type in the URL “StarUML”

Step 2: Click on the very first search “Download - StarUML”.

Step 3: There will be 3 Operating Systems (OS) options, click on the option as per the devise
OS.

Step 4: Now, right - click on the downloaded file, select “Show in Folder” option.

Step 5: Click on the open file, a popup window opens, click on the “Yes” button.

Step 6: Installation gets start. After installation popup opens to ask to buy a license. If you
want to click on the “Buy Now” button or else close that window. StarUML is ready to use.

2. Performing the Design by using any Design phase CASE tools

CASE Tool: StarUML

Use Cases for Stock Maintenance System

Actors Involved:

1. Store Manager – Manages inventory, adds stock, and generates

reports.

2. Sales Staff – Processes sales transactions and updates stock levels.

3. Supplier – Provides stock and receives purchase orders.

Use Case Details

6
 Use Case Name: Add New Stock

Initiated by: Store Manager

Precondition: The user must be authenticated and have admin

privileges.

Normal Flow: The store manager enters stock details such as item

name, quantity, supplier, and purchase date.

Alternative Flow: If required fields are missing, the system prompts

the user to complete them.

Post Condition: The stock item is successfully added to the inventory.

Use Case Name: Update Stock Levels

Initiated by: Store Manager / Sales Staff

Precondition: The item must a lready exist in the inventory.

Normal Flow: The user selects a stock item and updates quantity or

details.

Alternative Flow: If the stock item is not found, an error message is

displayed.

Post Condition: The updated stock details are saved in the system.

Use Case Name: Process Sales Transaction

Initiated by: Sales Staff

Precondition: The item must be available in stock.

7












 Normal Flow: The sales staff selects the item, records the quantity

sold, and processes the transaction.

Alternative Flow: If stock is insufficient, the system alerts the user to

update stock.

Post Condition: Stock levels are reduced, and a sales record is

generated.

Use Case Name: Generate Stock Report

Initiated by: Store Manager

Precondition: The system must have recorded stock data.

Normal Flow: The manager selects a report type (e.g., low stock, sales

summary) and generates the report.

Post Condition: The report is displayed or exported for further

analysis.

Would you like any modifications or additional use cases?

Use Case Name: View Exa m Schedule

Initiated by: Student

Precondition: The exam schedule must be updated in the system by the

admin.

Normal Flow: The student logs in and views the available exam

schedule.

8










 Figure 1. Use case diagram for stock maintenance system

Activity Diagram:

Activity diagrams are graphical representations of workflows of stepwise activities and actions with
support for choice, iteration and concurrency. In the Unified Modeling Language, activity diagrams
can be used to describe the business and operational step - by - step workflows of components in a

system. An activity diagram shows the overall flow of control. An activity is shown as an rounded
box containing the name of the operation.
This activity diagram describes the behaviour of the system.

9

 Figure 2. Activity Diagram for stock maintenance system

Sequence Diagram:
A sequence diagram represents the sequence and interactions of a given USE -CASE or scenario.
Sequence diagrams can capture most of the information about the system. Most object to object
interactions and operations are considered events and events include signals, inputs, decisions, interrupts,
transitions and actions to or from users or external devices.

An event also is considered to be any action by an object that sends information. The event line
represents a message sent from one object to another, in which the “form” object is requesting an
operation be performed by the “to” object. The “to” object performs the operation using a method that the
classcontains.

It is also represented by the order in which things occur and how the objects in the system send
message to one another.
10
Figure 5. Sequence Diagram For online exam regestration

11
Collaboration Diagram

Figure 6. Collaboration Diagram For Book Issue & Return

Class Diagram:

The class diagram, also referred to as object modeling is the main static analysis diagram. The main
task of object modeling is to graphically show what each object will do in the problem domain. The
problem domain des cribes the structure and the relationships among objects.
The Online Exam Registration System consists of six main classes: Student, Exam, Registration,
Payment, Admin, and Notification . The Student class stores student details such as studentID, name,
DOB , email, contact number, department, course, year, and credentials, with operations like registering,
12
deleting, and updating student information. The Exam class manages exam -related details, including
examID, subject name, date, duration, total marks, elig ibility criteria, and fee, along with operations to add,
update, delete, and view exams. The Registration class tracks exam enrollments, storing registrationID,
studentID, examID, registration date, and status, with operations for registering and canceling registrations.
The Payment class ensures secure fee transactions by handling paymentID, studentID, examID, amount,
payment date, and payment status, with functions for processing and verifying payments. The Admin class
allows administrators to manage stud ents, exams, and registrations, storing adminID, name, email, contact
number, and credentials, with operations to manage student and exam records. Lastly, the Notification class
manages communication, storing notificationID, studentID, message, and timesta mp, with functions to send
and view notifications. This structured system ensures a smooth and secure exam registration process for
both students and administrators.

Figure 7. Class Diagram For Book Bank System

13
Deployment Diagram and Component Diagram
Deployment diagrams are used to visualize the topology of the physical components of a system where
the software components are deployed.

Figure 8: Deployment Diagram for Book Bank System

14
State chart diagram

15
ER diagram

16
17
1

Software Requirement Specification Document

For

ONLINE COURSE RESERVATION

Prepared by

T SAI VIVEK REDDY(23BCE8725)

School of Computer Science and Engineering

1

AIM:
To develop the problem statement for Online Course Reservation System.

PROBLEM STATEMENT:
Online Course Reservation System is meant for students who wish to apply for the course
through online in a college. At first the system will list the available courses in the college. Then
the student will check the available seats for the particular course in the college. If the interested
course is available then the student will login and directed to fill the application. The system will
check fo r the eligibility and if the student is eligible then they will directed for payment to reserve
the course. If the course is reserved, then an acknowledgement will be send to the student and also
to the registrar of the college.
2

Software Requirements
Specification
For

ONLINE COURSE
RESERVATION

Prepared by

T SAI VIVEK REDDY-23BCE8725

Table of Contents

Table of Contents ................................ ................................ ................................ ...................... 3

1. Introduction ................................ ................................ ................................ ............................ 4
1.1.Purpose ................................ ................................ ................................ ................................ ......... 4
1.2.Document Conventions ................................ ................................ ................................ ................. 4
1.3.Intended Audience and Reading Suggestions ................................ ................................ ................. 4
1.4.Product Scope ................................ ................................ ................................ ............................... 4
1.5.References ................................ ................................ ................................ ................................ .... 4
2. Overall Descrip tion ................................ ................................ ................................ ................ 4
2.1.Product Perspective ................................ ................................ ................................ ....................... 4
2.2.Product Functions ................................ ................................ ................................ ......................... 5
2.3.User Classes and Characteristics ................................ ................................ ................................ ... 5
2.4.Operating Environment ................................ ................................ ................................ ................. 5
2.5.Design and Implementation Constraints ................................ ................................ ........................ 5
2.6.User Documentation ................................ ................................ ................................ ..................... 5
2.7.Assumptions and Dependencies ................................ ................................ ................................ .... 5
3. External Interface Requirements ................................ ................................ .......................... 6
3.1.User Interfaces ................................ ................................ ................................ .............................. 6
3.2.Hardware Interfaces ................................ ................................ ................................ ...................... 6
3.3.Software Interfaces ................................ ................................ ................................ ....................... 6
3.4.Communications Interfaces ................................ ................................ ................................ ........... 6
4. System Feature ................................ ................................ ................................ ....................... 7
4.1System Feature1 ................................ ................................ ................................ ................... 7
Description andPriority ................................ ................................ ................................ ....................... 7
4.2.FunctionalRequirements ................................ ................................ ................................ ................ 8
5.Other Nonfunctional Requirements ................................ ................................ ...................... 9
5.1 Performance Requirement ................................ ................................ ................................ ............. 9
· Capacity: The System must support 1000 people at a time. ................................ .............................. 9
· Interface: The interface screen shall respond within 5seconds. ................................ ......................... 9
· Conformity: The systems must confirm to the Microsoft Accessibilityguidelines. ............................ 9
5.2 Safety and Sec urity Requirements ................................ ................................ ................................ . 9
Class Notation: ................................ ................................ ................................ ................................ . 24

Revision History

Name Date Reason For Changes Version

 1.Introduction
1.1. Purpose
This SRS is developed for the entire system .Course Reservation by means of Direct communication would
consume time and takes more man power.In order to resolve this one, an Automated Online Course
Reservation System provides a smart way to reserve the cou rse through online which helps the Student to
apply in a efficient and convenient way .

1.2. Document Conventions

In general, this document follows IEEE formatting requirements. This document contains Times template
font size 14 for Sub headings, Size 18 for Headings and Arial template font size 11 for Descriptions
throughout the document. Heading are followed by subheadings which is followed by paragraphs.

Content Font Face Font Size Font Style

Heading Times New Roman 18 Bold
Sub Heading Times New Roman 14 Bold
Paragraph Times New Roman 12 Normal

1.3. Intended Audience and Reading Suggestions

This document can be used by,
Developers
Testers
Users

1.4. Product Scope

The objective of the Software is to provide an easy way for students to reserve a course through
online.
The main goal of this system is the time efficiency.

1.5. References
IEEE Software Requirement Specification Template
https://krazytech.com/projects/sample -software -requirements -specificationsrs

2.Overall Description
2.1. Product Perspective







 The Online Course Reservation System will be useful for students so that they can reserve their interested course in a
college .This Online Course reservation system is a interface between ‘Students ’ and the ‘College’. This system is
developed to save energy and time of the student.

In the System, Students must register to reserve their interested course in a college. Then Students mu st enter the
details in the application form and the system checks for the eligibility of student. If the student is eligible he/she will
be allowed to pay for the course through E -Pay after payment both the student and registrar will be notified.

2.2. Product Functions

The System secures the information about the student ’s reservation
The Students will receive SMS and Mail updates
The Registrar will get the report about the registration made by each students

2.3. User Classes and Characteristics

Students - They are the person who desires to obtain the course and submit the information tothe database.
Administrator – He has privilege to allocate the seats for the course and check the eligibility of the student.
He can approve or reject student ’s application.

2.4. Operating Environment

This System Support following Operating Systems
Windows10
Windows 8
Windows 7
Windows XP.

2.5. Design and Implementation Constraints

The information of all users must be stored in a database that is accessible by the administrators.
My SQL Server will be used to maintain a database.
Users may access from any computer that has internet browsing capabilities.
The system will work 24*7

2.6. User Documentation

The System provides User manual that defines the functions and option available in the system. The User
manual will be available in a document format .

2.7. Assumptions and Dependencies

The student may be required to upload the certificates.
The student and admin should have a internet connection to avoid disruption.













 3.External Interface Requiremen ts
3.1. User Interfaces
The interface should be user friendly for the user. It can be implemented by using java script.

The user interface is easy to implement.

3.2. Hardware Interfaces

The System requires the Intel processor and minimum of 2 GB RAM for the client. And also have
the dedicated links between theserver andclients.

3.3. Software Interfaces

The client machines require Microsoft Windows XP or better. The server requires Oracle Database
to hold all information,both the client and server computer must hav e internet browser to work
online.

3.4. Communications Interfaces

The System will perform the following functions:

· Sophisticated and - friendly interface for allsystem.

· Individual account or profile for all related to thesystem.

· Sophisticated interfaces for all people who related to thesystem.

· Implement student, course and instructor databasesystems.

· Implement Account System for managinginvoices.

· Keepsecretforallofstudentprofiles.Eachdivisioncanseeonlynecessarydataof each
student foranalyzing.
· Internet connection to work on with thesystem.


4.System Feature

4 . 1System Feature1

Description andPriority
ReserveSeat :

· Sign In: The first needs to sign in to the system with the name andpassword he/she have
provided with. The system needs to check for validation of that name and password and then
only allow he/she to access thesystem.

· Check Availability: They must be allowed to see all available options for courses.And see
if the seat is available ornot.

· Reserve Position: Then if the position is available then it must be booked by the only and
should not be granted to any other again till it getsfree .

MaintainHistory :

· Thewatchhistoryforthecourseregisteredbythe user mustbemaintainedregularlywhen he/she

signs out from the account.
ReportGeneration:

· Course Information: The System shall generate reports on course about thefollowing
Information: Course ID, Course Name.
· The System will generate reports on seats availability about thefollowing information: Course ID,
Seat Number,Reserved or Unreserved.

Database:
· Mandatory Information: First Name, Last Name, Phone Number, ID, Address, Postal Code, City,
Country, name and Password.
· Course Type: Technical or Non-Technical, Instructor, InstructorDetails.
· Update Information: The registrar will allow Admini strator to update anyof the information.
· Course Related Information: Course ID, No. of Seats.
 8

4.2. FunctionalRequirements

The course registration system has the following requirements:

1. Login

2. View coursedetails

3. Reserve forcourse

4. Payfee

5. CheckStatus

ACTORS INVOLVED :

1. Student
2. Registrar
REQ - 1 : LOGIN
The User enters the name and password and chooses whether the user is Student or
Registrar.If entered details are valid, the user’s account becomes available. If it is
invalid, anappropriate message is displayed to the user .
REQ - 2 :VIEW COURSE DETAILS
In this use case, a student can search all the courses available to him and choose the
best course he wants. The student can view the course duration, faculty and
department ofthe courses he maychoose.
REQ - 3 :RESERVE FOR COURSE

When a student has successfully chosen a course, he can register to that course. Upon
registration, the student’s details are stored in the database .
REQ - 4 :PAY FEE
After registration to any course, the student may see the details of his current course. He
may wish to know details about fees and other information.
REQ - 5 :CHECK STATUS

The system displays the status information to the student

 9

5.Other Nonfunctional Requirements

5.1 Performance Requirement

· Capacity: The System must support 1000 people at a time.

· Interface : The interface screen shall respond within 5seconds.

· Conformity : The systems must confirm to the Microsoft Accessibilityguidelines.

· Network Connection : It should be connected to internet 24 X 7. And the

Server must be onall time.

5.2 Safety and Security Requirements

· Identification : The system requires to identify himself or herself usingE - mail.

· Login ID: Any who uses the system shall have a Login ID andPassword.

· Modification : Anymodification(Insert,Delete, Update) for

theDatabaseshallbesynchronizedand done only by the administrator.

· Administrator ’ s Rights: Administrator shall be able to view and modify all information
inSystem.

· Back Up : The system shall provide the capability to back - up theData

· Errors: The system shall keep a log of all theerrors.

· Reliability: The system keeps the data securely students who enrolled the courses.
 10

· Availability: The system shall be available all thetime

· Appendix A: Glossary
· OCRS:
· It stands for Online course resrervation system.
· AUNTHETICATION:
· The process of identifying an individual, usually based on a username and password. In
security systems, authentication
· E- Pay :
e -pay is an eWallet that shoppers can use to pay u tility bills or transfer money online.
Shoppers register their debit or credit card when signing up for an ePay account.
Shoppers can then make payment either directly from their eWallet, or from the credit
or debit card linked to their account.

REGISTRAR:

Registrar is an official recorder or keeper of records such as a officer of an educational institution

responsible for registering students, keeping academic records, and corresponding with
applicants and evaluating their credentials.

DATABA SE:

database is an electronic system that allows data to be easily accessed, manipulated and
updated. In other words, a database is used by an organization as a method of storing, managing
and retrieving information.

Server:

server is a computer, a device or a program that is dedicated to managing network

resources. Servers are often referred to as dedicated because they carry out hardly any other
tasks apart from their server tasks
 11

Ex.No:3 Identify Use Cases and develop use case model

Date:

USE CASE DIAGRAM:

A use case diagram at its simplest is a representation of a user's interaction with the system that
shows the relationship between the user and the different usecases in which the user is involved.
A use case diagram can identify the different types of users of a system and the different use cases
and will often be accompanied by other types of diagrams as well. The use cases are represented
by either circles or ellipses.
 12

Purpose of Use Case Diagrams:

The purpose of use case diagram is to capture the dynamic aspect of a system. However, this
definition is too generic to describe the purpose, as other four diagrams (activity, sequence,
collaboration, and Statechart) also have the same purp ose.

Basic Use Case Diagram Symbols and Notations:

System:
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.

Usecase:
Draw use cases using ovals. Label the ovals with verbs that represent the system's functions.

Actors:
Actors are the users of a system. When one system is the actor of another system, label the actor
system with the actor stereotype.
 13

Relationships:
Illustrate relationships between an actor and a use case with a simple line. For relationships among
use cases, use arrows labeled either "uses" or "extends." A "uses" relationship indicates that one
use case is needed by another in order to perform a task. An "extends" relationship indicates
alternative options under a certain use case.
 14

USE CASE DIAGRAM:

Use case Modeling:

Usecase name: Login
Brief:
The Student enters into the system’ s software and looks into the control panel, then he enters the
login ID and password. If the password is valid then the system will display the next step or if the
password is wrong then it shows a message.

Casual:
 15

Success scenario:
The Student enters into the system ’s software and looks into the control panel, then he enters the
login ID and password. . If the password is valid then the system will display the next step.

Alternate scenario:
If the password entered by the Student is invalid, the system cannot be opened and can’t
perform any actions. So he must reenter the valid password. The system allows to enter the
valid passwo rd upto three attempts.

Fully Dressed:
Use case name Login
Goal To login successfully into the system.
Level Enter the login ID and password.
Primary actor Student.
Secondary / Suporting actor Admin
Stake holders Student plays the important role in the
system. He login to the system and and then
fill the application.

Precondition The system login should be working.

Main success scenario Enter to
the
system
software.
Look at
the
control
panel.
Enter the login ID and
password
Exception I
n
c
o
r
r
e
 16

c
t
p
a
s
s
w
o
r
d
.
F
o
r
g
e
t
p
a
s
s
w
o
r
d
.
Extension Proper maintenance of the system is needed.
Unauthorised person cannot login to the
system.
Special requirements Security
is
importan
t.
Provide
more
authentic
ation.

Usecase name: Check Status

Brief:
 17

The Student can enter the system and select the course to check the status of seat availability for
the course. If the seat is available for that course then the student will select the course else the
student will select the other available course.

Casual:
Success scena rio:
The student can enter the system and select the course to check the status of seat availability for
the course. If the seat is available for that course then the student will select the course.

Alternate scenario:
But at some situations, if the seat is not available then the student will select the other
available course.

Fully Dressed:

Use casename Check Status

Goal To select the course from the list of
course.

Level To check the status of the course.

Primary actor Student.
Secondary / Suporting actor Admin , Registrar.
Stake holders Student plays the important role in the
system.

Precondition The Student should eligible for that course

Main success scenario The student can enter the system and select the
course to check the status of seat availability for
the course. If the seat is available for that course
then the student will select the course.
 18

Exception Any other intervention of hazardous virus

occurred, the whole system may
be
collapsed.

Extension Proper maintenance of the system during the

regular interval time.
Special requirements Security Maintainence.
 19

Ex.No:4 Identify Conceptual classes and develop the domain

model and also derive a class diagram from that
Date:

Domain model:
Steps to create a domain model:
1. Find conceptual classes.

2. Draw them as classes in a UML class diagram.

3. Add Associations and attributes.

Finding Conceptual classes:

1. Reuse or modify existing conceptual models

2. Use category list.

3. Identify noun phrases.

Category list:
1.Business transaction: Reservation.
2.Transaction item: Reservation line items.
3.Product or service Course.
Related to transaction:

4. Where the transaction recorded: Database

5. Role of people or organization related to Student, registrar, College
transaction:

6.Place of transaction: Browsing center, College

7.Noteworthy events: Reserve course, fee pay.
8.Physics objects: System(pc or laptop).
 20

9.Description of things: Course description.

Identify the noun phrase:

Main success scenario:
First, the respected student can view the course details.
If the student wants to enrolled the course then the student should login with their
username and password.
Next for the selected course the student should reserve .
For the reservation process we should give the appropriate details of the students.
Then the system validate the user details.
After the validation step, the student should pay the fees for the reserved course.
After the end of payment the acknowledgement sent via the email of the student and so
only the student can easily check their details.

NOUNS:
· Course

· Student

· Registrar

· Detail

· Username

· Password

· Acknowledgement

· Email

· Fees

· System

· Payment

· Details








 21

Domain Model:
 22

CLASS DIAGRAM:
Class diagram is a static diagram. It represents the static view of an application. Class diagram is
not only used for visualizing, describing, and documenting different aspects of a system but also
for constructing executable code of the software applicat ion.
Class diagram describes the attributes and operations of a class and also the constraints imposed
on the system. The class diagrams are widely used in the modeling of objectoriented systems
because they are the only UML diagrams, which can be mapped d irectly with object - oriented
languages.
Class diagram shows a collection of classes, interfaces, associations, collaborations, and
constraints. It is also known as a structural diagram.
Purpose of Class Diagrams:
Analysis and design of the static view of an application.
Describe responsibilities of a system.
Base for component and deployment diagrams.
Forward and reverse engineering.
Members:
UML provides mechanisms to represent class members, such as attributes and methods, and
additional information about them.
Visibility:
To specify the visibility of a class member (i.e. any attribute or method), these notations must be
placed before the member's name.




 23

Derived property:
Is a property which value (or values) is produced or computed from other information, for
example, by using value of other properties.
Derived property is shown with its name preceded by a forward slash '/'.
Scope :
The UML specifies two types of scope for members: instance and classif ier, and the latter is
represented by underlined names.
Classifier members are commonly recognized as “static” in many programming languages.
The scope is the class itself.
o Attribute values are equal for all instances
o Method invocation does not affect the classifer ’ s state
Instance members are scoped to a specific instance.
o Attribute values may vary between instances
o Method invocation may affect the instance ’ s state (i.e. change instance ’ s attributes)
To indicate a classifier scope for a member, its name must be underlined. Otherwise, instance
scope is assumed by default.
Relationships:


 24

Class Notation:

UML class is represented by the following figure. The diagram is divided into four parts.
The top section is used to name the class.
The second one is use d to show the attributes of the class.
The third section is used to describe the operations performed by the class.
The fourth section is optional to show any additional components

Classes are used to represent objects. Objects can be anything having properties and
responsibility.
Object Notation:
It is represented in the same way as the class. The only difference is the name which is underlined
as shown in the following figure.




 25

Classes:
1. User

Username: String

Password: String

2. CourseDetails

Coursena me: String

Coursetype: String

Duration: Integer

3. Reservation

Name: String

Age: Integer

DOB: String

Marks:Integer

Parentdetail:String

4. Payment










 26

Amount: Integer

ModeofPayment: String

5. NetBanking

userid: String

password: String

6. CardPayment

Cardnumber: Long

ExpiryDate: String

CVVnumber: Integer

7. Status

Name: String

Coursename: String

Paidamount: Integer

CLASS DIAGRAM:










 28

Class diagram
 29

Ex.No:5 Using the identified scenarios find the interaction

between objects and represent them using UML
Date: sequence diagram

SEQUENCE DIAGRAM:
A sequence diagram simply depicts interaction between objects in a sequential order i.e. the order
in which these interactions take place. We can also use the terms event diagrams or event scenarios
to refer to a sequence diagram. Sequence diagrams describe how and in what order the objects in
a system function. These diagrams are widely used by businessmen and software developers to
document and understand requirements for new and existing systems.

Sequence Dia gram Notations:

1. Actors: An actor in a UML diagram represents a type of role where it interacts with the
system and its objects. It is important to note here that an actor is always outside the scope
of the system we aim to model using the UML diagram.
 30

2. We use actors to depict various roles including human users and other external subjects.
We represent an actor in a UML diagram using a stick person notation. We can have
multiple actors in a sequence diagram. For example: Here the user in seat reserv ation
system is shown as an actor where it exists outside the system and is not a part of the
system.

Figure: an actor interacting with a seat reservation system

3. Lifelines: A lifeline is a named element which depicts an individual participant in a
sequence diagram. So basically each instance in a sequence diagram is represented by a
lifeline. Lifeline elements are located at the top in a sequence diagram. The standard in in
 31

UML for naming a lifeline follows the following format – Instance Name : Class Name

We display a lifeline in a rectangle called head with its name and type. The head is located
on top of a vertical dashed line (referred to as the stem) as shown above. If we want to model
an unnamed instance, we follow the same pattern except now the portion of lifeline ’s name
is left blank.

Difference between a lifeline and an actor: A lifeline always portrays an object internal to
the system whereas actors are used to de pict objects external to the system. The following is
an example of a sequence diagram:
 32

4. Messages: Communication between objects is depicted using messages. The messages

appear in a sequential order on the lifeline. We represent messages using arrows. Li felines
and messages form the core of a sequence diagram.
Messages can be broadly classified into the following categories :

1. Synchronous messages: A synchronous message waits for a reply before the

interaction can move forward. The sender waits until the receiver has completed
 33

the processing of the message. The caller continues only when it knows that the
receiver has processed the previous message i.e. it receives a reply message. A large
number of calls in object oriented programming are synchronous. We use a solid
arrow head to represent a synchronous message.

2. Asynchronous Messages: An asynchronous message does not wait for a reply

from the receiver. The interaction moves forward irrespective of the receiver
processing the previous message or not. We use a lined arrow head to represent an
asynchronous message.

3. Create message: We use a Create message to instantiate a new object in the

sequence diagram. There are situations when a particular message call requires
the creation of an object. It is repres ented with a dotted arrow and create word
labeled on it to specify that it is the create Message symbol.
For example – The creation of a new order on a e -commerce website would
 34

require a new object of Order class to be created.

Delete Message: We use a Delete Message to delete an object. When an object is deallocated
memory or is destroyed within the system we use the Delete Message symbol. It destroys the
occurrence of the object in the system.It is represented by an arrow terminating x. For
example – In the scenario below when the order is received by the user, the object of order
class can be destroyed.

 35

Self Message: Certain scenarios might arise where the object needs to send a message to
itself. Such messages are called Self Messages and are represented with a U shaped arrow.

For example – Consider a scenario where the device wants to access its webcam. Such a scenario
is represented using a self message.

Reply Message: Reply messages are used to show the message being sent from the re ceiver
to the sender. We represent a return/reply message using an open arrowhead with a dotted
line. The interaction moves forward only when a reply message is sent by the receiver.


 36

For example – Consider the scenario where the device requests a photo from the user. Here
the message which shows the photo being sent is a reply message.

Found Message: A Found message is used to represent a scenario where an unknown source
sends the message. It is represented using an arrow directed towards a lifeline fro m an end
point. For example: Consider the scenario of a hardware failure.

 37

It can be due to multiple reasons and we are not certain as to what caused the hardware
failure.
 38

Lost Message: A Lost message is used to represent a scenario where the recipient is not
known to the system. It is represented using an arrow directed towards an end point from a
lifeline. For example: Consider a scenario where a warning is generated.

The warning might be generated for the user or other software/object that the lifeline is
interacting with. Since the destination is not known before hand, we use the Lost Message
symbol.

Guards: To model conditions we use guards in UML. They are used when we need to restrict the
flow of messages on the pretext of a condition being met. Guards play an important role in letting
software developers know the constraints attached to a system or a particular process.
For example: In order to be able to withdraw cash, having a balance greater than zero is a condition
that must be met as shown below.

Uses of sequence diagrams:


 39

Used to model and visualize the logic behind a sophisticated function, operation or
procedure.
They are also used to show details of UML use case diagrams.
Used to understand the detailed functionality of current o r future systems.
Visualize how messages and tasks move between objects or components in a system.

SEQUENCE DIAGRAM:




40
 41

Flow of messages:
The student login to the system by entering a valid ID and password.

Then student select a course from the list of available courses.

Next student has to enter the details of them such as name,dob,age marks.
After entering the details the system validate the datails.
Once the validation complete the student done the payment.
After completing the payment the acknowledgement send to the student via email.
Then the student check their status of the course using the status option.







 42

Ex.No:6 Using the identified scenarios, find the interaction

between objects and represent them using UML
Date: collaboration diagram

COLLABORATION DIAGRAM:
A collaboration diagram, also known as a communication diagram, is an illustration of the
relationships and interactions among software objects in the Unified Modeling Language ( UML).
These diagrams can be used to portray the dynamic behavior of a particular use cases and define
the role of each object.
Collaboration diagrams are created by first identifying the structural elements required to carry out
the functionality of an interaction. A model is then built using the relationships between those
elements. Several vendors offer software for creating and editing coll aboration diagrams.

Notations of a collaboration diagram:

A collaboration diagram resembles a flowchart that portrays the roles, functionality and behaviours
of individual objects as well as the overall operation of the system in real time. The four major
components of a collaboration diagram are:

1. Objects- Objects are shown as rectangles with naming labels inside. The naming label follows
the convention of object name: class name. If an object has a property or state that specifically
influences the collaboration, this should also be noted.

2. Actors- Actors are instances that invoke the interaction in the diagram. Each actor has a name
and a role, with one actor initiating the entire use case.

3. Links- Links connect objects with actors and are depicted us ing a solid line between two
elements. Each link is an instance where messages can be sent.
 43

4. Messages- Messages between objects are shown as a labeled arrow placed near a link. These
messages are communications between objects that convey information about the activity and
can include the sequence number.

The most important objects are placed in the centre of the diagram, with all other participating
objects branching off. After all objects are placed, links and messages should be added in between.

COLLABORATION DIAGRAM:
 45

ACTIVITY DIAGRAM: \
 46

Activity diagram describe activities which involve concurrency and synchronization, which are a
variation of state diagrams that focuses on the flow of actions and events. They can be used for:
To model a human task (a business process, for instance).
To describe a system function that is represented by a use case.

ACTIVITY DIAGRAM:

This Activity diagram consists of three swimlanes namely student,reservation

system,admin,accountant.The initial process is course selection by the student.Theparallel
behaviours such as branch used for selection of the course and login. The reservation then next


 47

processed by the filling the ap plication by entering the details and get validate by the
system.Then payment is done by the help of accountant.Then the acknowledgement send to the
student for the resevation of a course.

STATE CHART DIAGRAM:

A state machine Diagram (or start diagram, also called state chart of state transition diagram) is a
behaviour which specifies the sequence of states an entity (or object) visits during its lifetime in
response to events, together with its responses to those events.

Key concepts:
State

A state is a condition during the life of an object during which it satisfies some condition,
performs some activity, or waits for some external event.
A state machine diagram is a graph consisting of:

States (simple states or composite states)

State transitions conne cting the states

Initial and Final States:

The initial state of a state machine diagram, known as an initial pseudo - state, is indicated
with a solid circle. A transition from this state will show the first real state



 48

The final state of a state machine diagram is shown as concentric circles. An open loop
state machine represents an object that may terminate before the system terminates, while
a closed loop state machine diagram does not have a final state; if it is the case, then the

object lives until t he entire system terminates.

STATE CHART DIAGRAM:


 49

Conclusion:
The Online course Reservation system can help to save the time of the students. The
system is designed to reduce the time , also improve the efficiency of maintaining the course.
It provides flexible and powerful reports regarding the course available in the list.it provides
the status to get the details of their enrolled course. It also helps to overcome some problems
faced by the students in real timecourse reservation .
 Software Requirement Specification Document

For

E -TICKETING SYSTEM

Prepared by
T SAI VIVEK REDDY(23BCE8725)

School of Computer Science and Engineering

 e-TICKETING SYSTEM BY T SAI VIVEK REDDY -23BCE8725
AIM

To develop the E-Ticketing System using Umbrello Tool and to implement

using
visual basic.

PROBLEM ANALYSIS AND PROJECT PLANNING

In the E-Ticketing system the main process is a applicant have to login

the database
then the database verifies that particular username and password then the user
must fill the
details about their personal details then selecting the flight and the database
books the ticket
then send it to the applicant then searching the flight or else cancelling the
process.

PROBLEM STATEMENT

The E-Ticketing system is the initial requirement to develop the project

about the
mechanism of the E-ticketing system what the process do at all.
· The main scope for this project is the applicant should reserved for
the flight
ticket.
· First the applicant wants to login to the database after that the
person wants to
fill their details.
· Then the database will search for ticket or else the person will can-
celled the
ticket if he/she no need.

SYSTEM REQUIREMENT SPECIFICATION

S.NO CONTENTS

1 INTRODUCTION

1.1 Purpose

1.2 Scope

1.3 References

1.4 Technology To Be Used

1.5 Tools Be Used

1.6 Overview

2 OVERALL DESCRIPTION

2.1 Functionality

2.2 Usability

2.3 Performance
 2.4 Reliability

1. INTRODUCTION

Purpose

The applicant should login to the database for reserving the ticket.

In the specification use define about the system requirements that are part from
the
functionality of the system. It tells the usability, reliability defined in the
use case
specification.

References

IEEE Software Requirement Specification format.

Technology To Be Used

Microsoft Visual Basic 6.0

Tools Be Used

Umbrello tool (for developing UML Patterns)

Overview

SRS includes two sections overall description and specific requirements -

Overall
description will describe major role of the system components and inter -connec-
tions. Specific
requirements will describe roles & functions of the actors.

2. OVERALL DESCRIPTION

Functionality

The database should be act as an main role of the e -ticketing system it

can be booking
the ticket in easy way.

Usability

The User interface makes the Credit Card Processing System to be effi-
cient.

Performance

It is of the capacities about which it can perform function for many us-
ers
at the same times efficiently that are without any error occurrence.

Reliability

The system should be able to process the user for their corresponding re-
quest.
UML DIAGRAMS
Sno UML DIAGRAMS

1 Use Case diagram

2 Class diagram
3 Sequence diagram
4 State Chart diagram
5 Activity diagram

USE CASE DIAGRAM

DOCUMENTATION

The actors in this use case diagram are applicant, and E -ticketing Data-
base. The use
cases are the activities performed by actors. The actors in this use case dia-
gram are
login,filling details,selecting flight,book ticket,search,cancel ticket.

CLASS DIAGRAM
DOCUMENTATION

This class diagram has two classes applicant, E -Ticketing DataBase.

o Applicant - logins the E -Ticketing and filling the required data
fields.
o E-Ticketing DataBase -verify the login and filling the details and
selected
applicant details are stored in it.

SEQUENCE DIAGRAM
DOCUMENTATION

This sequence diagram describes the sequence of steps to show

· Applicants are used to login the form. And then its verify the username
and
password.
· If the password and username are correct then applicants are used to
login the
filling details.
· Applicants are used to selecting the flights and book the tickets.
· Now the E-Ticketing Database verify the filling Details.
· And then the E-Ticketing Database displays the ticket information.
· In case of any sudden change of the plan, the applicant can cancel the
ticket.

DOCUMENTATION

· This collaboration diagram is to show how the applicant login and

register in
the E-Ticketing system. Here the sequence is numbered according to
the flow
of execution.
· This collaboration diagram is to show the selection process of the
applicant for
the ticket booking. The flow of execu tion of this selection process
is
represented using the numbers.

STATE CHART DIAGRAM

DOCUMENTATION

This state diagram describes the behavior of the system.

· First state is login where the applicant login to the E -Ticketing sys-
tem.
· The next state is filling details the applicant is used to fill the
form.
· Then applicant used to selecting the flight.
· The applicant appears for book ticket and search details from E -Tick-
eting
Database.

ACTIVITY DIAGRAM
DOCUMENTATION

This activity diagram describes the behavior of the system.

 · First state is login where the applicant login to the E -Ticketing system.
· The next state is filling details the applicant is used to fill the form.
· Then applicant used to selecting the flight.
· The applicant appears for book ticket a nd search details from E -Ticketing
Database.

RESULT
Thus the project to develop E -Ticketing system using Umbrello Tool
and to
implement using Visual Basic is done successfully.
 Software Requirement Specification Document

For

SOFTWARE PERSONAL MANAGEMENT SYTEM

Prepared by
M.ASISH REDDY(23BCE8660)

School of Computer Science and Engineering

SOFTWARE PERSONAL MANAGEMENT SYSTEM

AIM

To develop a project software personnel management system using the rational rose
software and to implement the software in java

PROBLEM STATEMENT

The CEO must enter the name and password to login the form and select the particular
employee to view the details about that employee and maintaining the employee details
personally. This process of software personnel management system are descri bed sequentially
through following steps, The CEO login to the software personnel management system .He/she
search for the list of employees. Then select the particular employee. Then view the details of
that employee. After displaying the employees detail then logout.

UML DIAGRAMS

1. Use Case diagram

2. Class diagram
3. Sequence diagram
4. Collaboration diagram
5. State Chart diagram
6. Activity diagram
7. Component diagram
8. Deployment diagram

USE CASE DIAGRAM.

The use case diagram in the software personnel management system illustrates the
sequence of sequencing and describing an interaction between a CEO and a system.

CEO - login to the software personnel management system and maintaining the employee
details.

EMPLOYEE - View the details of the particular employee.

DATABASE - Maintainance the list of employee details and check whether the CEO has given
the valid name and password.

The vario u s user case are

LOGIN - This use case gives as entry to the CEO and the database.

LIST OF EMPLOYEE- This will create the situation for the CEO to select particular
employee from the available list.
EMPLOYEE DETAILS - The CEO can able to view the details of the employee using this
usecase.
VERFICATION - Database check name and password is valid or invalid.

MAINTAIN PERSONNELDETAILS - The CEO maintain the employee details in the details.

LOGOUT - The CEO can be logout the software personal management system.

USECASE DIAGRAM
CLASS DIAGRAM

The Classes used in this project are

CEO - The CEO has to login the form by specifying the name and password of him.

DATABASE - The database checks whether the CEO has given the name and password
Accordingly. if not the error message will be displayed.

AVAILABILE EMPLOYEE - The database is connects to the list of available employees and
the CEO. if wants then select the employee from it.

CLASS DIAGRAM

CEO
DATABASE
name : string
name : string
login()
joballocation() login()
regularAttedance() storeDetails()
verification() logout()
logout()

EMPLOYEE
name : string

login()
qua;lification()
experience()
logout()
SEQUENCE DIAGRAM

The CEO must enter his name and password to login the software personnel management
system. The verification process is undergone by the database .If the details are correct he can
enter to the system otherwise error is displayed. After login the details of the particular employee
is viewed by the CEO. Finally he is logged out from the system.

SEQUENCE DIAGRAM

ceo dba employe e

login

COLLABORATION DIAGRAM
 It is same as the sequence diagram that involves the object of the project with the only
differences that we give the sequence no to the each process. The CEO must enter his name and
password to login the software personnel management system. The verification process is
undergone by the database .If the details are correct he can enter to the system otherwise error is
displayed. After login the detail of the particular employee is viewed by the CEO. Finally he is
logged out from the system.

COLLABORATION DIAGRAM

6: login
8: view employee details
9: verification
10: logout
ceo dba

7: display employee details

1: login
2: name and address
3: qualification
4: experiance
5: logout

employe
e
STATE CHART DIAGRAM

The various states are the login, listsof employees, selects a employee, display the
information about the employee, logout.The state chart diagram describes the behavior of the
system. The main purpose of the system is to maintain an employee details personally. For that
the CEO Log in to the software personnel management system. He/she s elects a particular
employee from the list of available employee. The CEO has to view the details of the particular
employee by clicking the respective button.The CEO views the details then finally he is logout
from the system.

STATE CHART DIAGRAM

login name and qualificatio experience joballocatip regular attendence

addresss
n on checking

logout storedetail verificati on

s
ACTIVITY DIAGRAM

The CEO Log in to the software personnel management system. He/she selects a
particular employee from the list of available employee. The CEO can view the details of the
particular employee by clicking the respective button. After viewing the details he is logout from
the s ystem.
ACTIVITY DIAGRAM

Employee DBA CEO

COMPONENT DIAGRAM

In this diagram there link between the actors is present in the SPMS that could be shown
in diagrammatically way in the component diagram. Each every actor is having a directional link
to process further details present in the system.

COMPONENT DIAGRAM

software personal
management system

emplo DBA
yee ceo

DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the software personnel management system
which is the main part and the devices are the CEO login, viewing the details of the employee
are some of the main activities performed in the system.
DEPLOYMENT DIAGRAM

RESULT

Thus the UML diagrams are drawn for software personnel management system and the
java code was generated successfully by using Rational Rose software.
 Software Requirement Specification Document

For

CREDIT CARD SYSTEM

Prepared by

M.ASISH REDDY(23BCE8660)

School of Computer Science and Engineering

CREDIT CARD SYSTEM
AIM:
To develop a Credit Card Processing System using Rational Rose for UML
modeling and implement the software in Java .

PROBLEM STATEMENT:

The system allows users to apply for a credit card, manage transactions, and make payments.
The process includes:

1. Users registering and logging in.

2. Admin verifying and approving credit card applications.
3. Users viewing transactions and making payments.
4. System maintaining card details, payment history, and dues.
5. Secure logout after operations.

UML DIAGRAMS:

1. Us e Case Diagram
2. Class Diagram
3. Sequence Diagram
4. Collaboration Diagram
5. State Chart Diagram
6. Activity Diagram
7. Component Diagram
8. Deployment Diagram
 USECASE DIAGRAM

Actors & Use Cases

Customer: Registers, logs in, applies for a credit card, views transactions, makes payments.
Admin: Reviews and approves applications, manages credit card details.
Database: Stores and verifies customer details.

Use Cases

Register/Login : Allows users to enter the system.

Apply for Credit Card : Customers submit an appl ication.
Approval Process : Admin verifies and approves/rejects applications.
View Transactions : Customers can see past transactions.
Make Payment : Users pay dues and update credit balance.
Logout : Securely exits the system.

login

Allot

User Due Admin

Pay

Signup









 Usecase diagram for Credit Card Processing System

CLASS DIAGRAM

Defines the structure and relationships among system classes.

Classes

Customer: Handles login, transactions, payments.

Admin: Manages card approvals and user data.
CreditCard: Stores credit limits, transactions, and due amounts.
Database: Verifies user details and stores transaction history.




Class diagram for Credit Card Processing System
 SEQUENCE DIAGRAM

To design a sequence diagram for Credit Card Processing System.

Describes the flow of interactions between objects over time.

1. Customer logs in → System verifies credentials.

2. Applies for credit card → Admin verifiesdetails and approves/rejects.
3. Customer views transactions → Database retrieves d ata.
4. Customer makes a payment → System updates balance.
5. Customer logs out → Session ends securely.

User Database Admin

admin login

verify authentication
Allot card

User login
Verify authenticate
Get card
Check due
check due
pay due

user logout

Admin logout

Sequence diagram for Credit Card Processing System

 COLLABORATION DIAGRAM

Similar to the sequence diagram but focuses on interactions among objects.

Customer interacts with System → Requests login, credit card application.

System communicates with Admin → Admin reviews requests.
System updates Database → Stores customer transactions and payments.

2: verify authentication
5: verify authentication
4: user login
8: check due
9: pay due
10: user logout
User Database

6: get card

1: admin login
3: allot card
7: check due
11: admin logout

Admin

Collaboration diagram for Credit Card Processing System




 STATE CHART DIAGRAM

Shows state transitions within the system.

States

1. Idle → User is not logged in.

2. Logged In → User enters the system.
3. Application Submitted → Customer applies for a card.
4. Approval Pending → Admin reviews application.
5. Card Approved → Customer receives a credit card.
6. Transaction Made → System updates balance.
7. Payment Processed → Reduces outstanding dues.
8. Logged Out → Session ends

login Allot check due Pay

State chart diagram for Credit Card Processing System

 ACTIVITY DIAGRAM

Illustrates the step -by-step workflow of the system.

1. Customer logs in.

2. Views account details or applies for a credit card.
3. Admin reviews and approves applications.
4. Customer checks transactions and dues.
5. Makes payments.
6. Logs out.
 Login

Allot card

Check due

Make
payment

update
balance

Logout

Activity diagram for Credit Card Processing System

 COMPONENT DIAGRAM

Depicts the system’s components and their relationships.

Main components:

User Interface: Handles user interactions.

Database: Stores customer information and transactions.
Payment Module: Manages credit card payments.
Approval System: Processes admin approvals

Custome NewCom
r ponent2

Bank

Component diagram for Credit Card Processing System





 DEPLOYMENT DIAGRAM

Shows the system’s physical structure, including hardware and software deployment.

Nodes:

Client Device: Users access the system via web or app.

Server : Hosts the application and database.
Payment Gateway : Handles secure credit card payments.

Credit Card
processing system

Custom Bank
er

Deployment diagram for Credit Card Processing System




Software Requirement Specification Document

For

E-BOOK MANAGEMENT

Prepared by

L THARUN(23BCE8698)

School of Computer Science and Engineering

 E -BOOK MANAGEMENT SYSTEM

AIM
To develop a project for an E -Book Management System using
UML diagrams and to implement the software in an appropriate
programming language.

PROBLEM STATEMENT
The system allows users to manage, organize, and access e -
books efficiently. Users can register, log in, upload, download,
and categorize e -books. The system will include an
administrative module for managing users and content.

UML DIAGRAMS
Use Case Diagram
Class Diagram
Sequence Diagram
Collaboration Diagram
State Chart Diagram
Activity Diagram
Component Diagram
Deployment Diagram

USE CASE DIAGRAM

The Use Case Diagram illustrates the interactions between
users, administrators, and the system.
Actors:








 User: Registers, logs in, uploads, downloads, and
categorizes e -books.
Administrator : Manages users, books, and system
settings.
Database: Stores and retrieves user and e -book details.
Use Cases:
User Registration – Users register with the system.
Login – Users and administrators log in.
Upload E -Book – Users upload ne w e-books.
Download E -Book – Users download e -books.
Categorization – Users organize e -books into categories.
Management – Admins manage users and books.
Logout – Users and admins log out.

CLASS DIAGRAM










 The main classes involved in the system:
User: Handles user authentication and actions.
Admin : Manages users and e -books.
E -Book: Stores book details such as title, author, and file
location.

Database: Manages the storage and retrieval of

information.

SEQUENCE DIAGRAM




Describes the interaction between users, administrators, and
the system when managing e -books.

COLLABORATION DIAGRAM
Similar to the sequence diagram but focuses on object
interactions with sequence numbers.
STATE CHART DIAGRAM
Depicts various states such as login, boo k selection, reading,
and logout.
ACTIVITY DIAGRAM
Illustrates the flow of activities from login to e -book
management and logout.
COMPONENT DIAGRAM
Shows the relationship between different components of the
system.

DEPLOYMENT DIAGRAM
Illustrates the system ’s physical deployment, including servers,
users, and data storage.
RESULT
The UML diagrams are designed for the E -Book Management
System, and the implementation will be carried out using the
chosen technology stack.
Software Requirement Specification Document

For

RECRUITMENT SYSTEM

Prepared by

L THARUN(23BCE8698)

School of Computer Science and Engineering

 RECRUITMENT SYSTEM

AIM

To develop a project for a Recruitment System using UML diagrams and to implement the software in
an appropriate programming language.

PROBLEM STATEMENT

The system allows companies to post job openings, and applicants to register, apply for jobs, and
track their application status. The system will include an administrative module for managing job
postings and user applications.

UML DIAGRAMS
Use Case Diagram

Class Diagram

Sequence Diagram

Collaboration Diagram

State Chart Diagram

Activity Diagram

Component Diagram

Deployment Diagram

USE CASE DIAGRAM

The Use Case Diagram illustrates the interactions between job seekers, recruiters, and the system.

Actors:
Job Seeker : Registers, logs in, searches for jobs, applies, and tracks applications.

Recruiter : Posts job openings, reviews applications, and manages recruitment processes.

Administrator : Manages users and job postings.

Database: Stores and retrieves job and user details.

Use Cases:
User Registration – Job seekers and recruiters register w ith the system.

Login – Users and administrators log in.

Post Job – Recruiters post new job openings.
















 Search Jobs – Job seekers browse available jobs.

Apply for Job – Job seekers submit applications.

Manage Applications – Recruiters review and process appl ications.

Logout – Users and admins log out.

CLASS DIAGRAM

The main classes involved in the system:

Job Seeker : Handles job search and applications.

Recruiter : Posts and manages job applications.

Job Posting : Stores job details such as title, description, and requirements.

Application: Tracks job applications.









 Database: Manages storage and retrieval of user and job data.

SEQUENCE DIAGRAM

Describes the interaction between job seekers, recruiters, and the system when applying for jobs.

COLLABORATION DIAGRAM

Similar to the sequence diagram but focuses on object interactions with sequence numbers.

[PLACEHOLDER FOR COLLABORATION DIAGRAM]

STATE CHART DIAGRAM

Depicts various states such as job posting, application submission, interview s cheduling, and hiring.
ACTIVITY DIAGRAM

Illustrates the flow of activities from job posting to hiring or rejection.

COMPONENT DIAGRAM

Shows the relationship between different components of the system.

DEPLOYMENT DIAGRAM

Illustrates the system ’ s physical deployment, including servers, users, and data storage.
RESULT

The UML diagrams are designed for the Recruitment System, and the implementation will be carried
out using the chosen technology stack.