EX.

NO:
DATE: LIBRARY MANAGEMENT SYSTEM

AIM:
To develop a project of Library management system using MYSQL Database and
to implement the software in PHP Admin

ABSTRACT
Sure, let's abstract a library management system focusing on book issues, categories, and
authors. Book represents a physical or digital book in the library. It has attributes such as title,
author(s), publication year, ISBN, category, availability status, etc. Category represents the
genre or subject classification of books. Categories could be fiction, non-fiction, science
fiction, mystery, etc. Author represents the creator of a book. It has attributes such as name,
biography, bibliography, etc. -User Represents individuals who interact with the library can
borrow, return, or reserve books. Issue Book Users can request to borrow a book. This action
involves checking the availability of the book, assigning it to the user, updating its availability
status, and recording the transaction. Return Boo Users can return borrowed books. This action
involves updating the availability status of the book and removing the association with the user.
Search Users can search for books based on various criteria such as title, author, category. Add
Book Librarians can add new books to the library system, including details such as title,
category, ISBN.Add Author Librarians can add new authors to the system along with their
details. Categorize Book Librarians can assign categories to books. Update Information
Librarians can update book details such as title, author, category. Remove Book Librarians
remove books from the system.

4
SOFTWARE REQUIREMENT SPECIFICATION:
• INTRODUCTION
• OBJECTIVES
• OVERVIEW
• GLOSSARY
• PURPOSE
• SCOPE
• FUNCTIONALITY
• USABILITY
• PERFORMANCE
• RELIABILITY
• FUNCTIONAL REQUIREMENTS

INTRODUCTION

This system would be used by members who are students of any college to check
the availability of the books and borrow the books, and then the databases are
updated. The purpose of this document is to analyze and elaborate on the high- level
needs and features of the book bank management system. It also tells the usability,
reliability defined in use case specification.

1. OBJECTIVE

The main objective of the system is being to design an online book-bank monitoring
system to enable a central monitoring mechanism of the book-bank be more faster
and less error prone. Apart from this,

a. To help the students acquire the right books for the syllabus at the
right time.

b. To ensure availability of basic textbooks to students against limited

funds and to develop student’s ability to handle property loaned to
them

.
2. OVERVIEW

The overview of this project is to design a tool for book bank so that it can be used
by any book banks to lend their books as well as colleges.

5
3. GLOSSARY

TERMS DESCRIPTION

MEMBER The one who registers himself and

purchase books from the bank.
DATABASE Database is used to store the details
of members and books.
ADMINISTRATOR The one who verifies the
availability of book and issue them
USER Member

4. PURPOSE

The purpose of the book bank management system is to reduce the manual
intervention.

5. SCOPE

The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.

6. FUNCTIONALITY

Many members will be waiting to take the book from the book bank at a single
day. To serve all the members

7. USABILITY

User interface makes the Recruitment system to be efficient. That is the system
will help the member to register easily and helps them to get their books easily.
The system should be user friendly.

8. PERFORMANCE

It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.

9. RELIABILITY

6
 The book bank management system should be able to serve the applicant
with correct information and day-to-day update of information.

10. FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system.

That is the services that are provided to the member who borrows book.

EXTERNAL INTERFACE REQUIREMANTS

SOFTWARE REQUIREMENTS:
Front end :PHP
Back end :MYSQL

PURPOSEHARDWARE REQUIREMENTS

1. Processor : intel i3
2. RAM : 4 GB
3. Operating syatem : Microsoft windows

UMLDIRAM

The following UML diagrams describe the process involved in the online
recruitment system

a. Use case diagram

b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. State chart diagram
f. Activity diagram
g. Component diagram
h. Deployment diagram
i. Package diagram

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
particular goal. It is represented using ellipse.

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

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are member and database. The use cases are the
activities performed by actors.

a. The member will register himself in the book bank.

b. After registration he will select the year to which he belongs

c. After selecting he will select books

d. 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

8
compartments the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has 8 classes:

o Member details class- is the class name. Its attributes are name,
father name, date of birth, address, phone number, member id,
college, degree, course and semester. Its operations are registration,
authentication, and year selection.

o Administrator- is the class name. Its attributes are name, address,

phone, mail id. Its operations are authentication, verification and issue
books.

o Year-is the class name. Its attribute is year selection. Its operations
are 1st year,2nd year, 3rd year,4th year.

o Issue for 1st year-is the class name. Its attributes are member code,
member name, book code, book name, and quantity. Its operation is
issue

Issue for 2nd year-is the class name. Its attributes are member code,
member name, book code, book name, and quantity. Its operation is
issue

o Issue for 3rd year-is the class name. Its attributes are member code,
member name, book code, book name, and quantity. Its operation is
issue

9
SEQUENCE DIAGRAM

A sequence 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. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects.

10
DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show

a. The member registers himself in book bank

b. He will select the year

c. He selects the books given and the database will update the status
ofbook.

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

e. If the book is available, he will issue the book.

COLLABRATION DIAGRAM

A collaboration diagram, also called a communication diagram or interaction

diagram, a sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as
well as the overall operation of the system in real time
11
DOCUMENTATION OF COLLABORATION DIAGRAM

The collaboration diagram is to show how the member registers himself and borrow
the book from the book bank. Here the sequence is numbered according to the flow
of execution.

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.

12
DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.

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

b. After that he will select the year in next state.

c. In the next state he will select the books.

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

e. In the next state administrator will log in.

13
 f. After authentication he will verify the availability of book.

g. 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

14
DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in book bank

management system.

a. The member registers himself in book bank

b. After that he will select the year.

c. He will select the books.

d. Database will update the status of book.

e. Database will update the details

f. Then the administrator will log in to his account.

g. After authentication he will verify the availability of book.

h. If available, he will issue the book.

COMPONENT DIAGRAM

The component diagram's main purpose is to show the structural relationships

between the components of a system. It is represented by boxed figure.
Dependencies are represented by communication association

15
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is online book bank management
systems. And member details, issue for first year, issue for second year issue for
third year and issue for fourth year are components comes under the main
component

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 represented by 3-dimentional box. Dependencies are represented by
communication association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

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 first year, issue for second year issue for third year and issue for fourth year are
some activities performed in this system.

16
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML. PDs can be
used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).
There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are

a. The User interface layer - consists of the web and member details.
This layer describes how the member goes to book bank and registers
himself.

b. The Domain layer – shows the activities that are performed in the
17
 book bank management system. The activities are register and book
issues.

c. The Technical service layer - the member details and verification

details are stored in the datab

18
RESULT:

Thus the project to implement Library Management System using Mysql and PHP has been
successfully designed

19
 EX.NO:
DATE: STUDENT INFORMATION SYSTEM

AIM:
To develop a project of Student information management system using Mysql
Software and to implement the software in PHP Admin

ABSTRACT
Our project aims to develop a comprehensive Student Information System (SIS)
tailored for educational institutions to efficiently manage student-related data. The
system will incorporate modules for admissions, registration, attendance tracking,
grading, scheduling, and more, providing a centralized platform for administrators,
faculty, and students to access and update pertinent information. Key features of the
SIS include robust data management capabilities, allowing for the storage, retrieval,
and manipulation of student records with ease. User roles and permissions will be
implemented to ensure appropriate access levels and data security. Integration with
other systems, such as learning management systems and financial databases, will
streamline processes and reduce duplicate data entry. The SIS will offer extensive
reporting capabilities, enabling administrators to generate various reports for
analysis and decision-making. Additionally, the system will prioritize user
experience with an intuitive interface and responsive design, accessible across
devices. By implementing our SIS, educational institutions can expect improved
efficiency, communication, and decision-making, ultimately enhancing the overall
student experience and organizational effectiveness

20
SOFTWARE REQUIREMENT SPECIFICATION:
• INTRODUCTION
• OBJECTIVES
• OVERVIEW
• GLOSSARY
• PURPOSE
• SCOPE
• FUNCTIONALITY
• USABILITY
• PERFORMANCE
• RELIABILITY
• FUNCTIONAL REQUIREMENTS

INTRODUCTION:

In today's digital age, educational institutions face the challenge of managing vast amounts of
student data efficiently and securely. Student Information Management System (SIMS) serves
as a comprehensive solution designed to streamline the process of collecting, storing,
managing, and utilizing student information effectively. It acts as the backbone of educational
administration, providing administrators, teachers, students, and parents with access to critical
data and functionalities.

OBJECTIVE:

The main objective of the system is being to design an student information system
monitoring system to enable a central monitoring mechanism of the student register
be more faster and less error prone. Apart from this,

a. To help the students acquire the right books for the syllabus at theright
time.

b. To ensure availability of basic students information against limitedfunds

and to develop student’s ability to handle property loaned to them
21
 OVERVIEW:
The overview of this project is to design a tool for student information so that it canbe
usedby any student information register to collages.

GLOSSARY:

TERMS DESCRIPTION

MEMBER The one who registers himself and

store the student profile
DATABASE Database is used to store the details
Numbers of student information

ADMINISTRATOR The one who verifies the

availability admin login
USER Member

PURPOSE

The purpose of the student information systems is to reduce the manual

intervention.

SCOPE

The scope of this student information system system is to act as a tool for information
administrator for quick reference, availability of the information.

FUNCTIONALITY

Many members will be waiting to take the information from the student at a
singleday. To serve all the members

USABILITY

22
 User interface makes the Recruitment system to be efficient. That is the system
will help the member to register easily and helps them to get their information
easily.The system should be user friendly.

PERFORMANCE

It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently
RELIABILITY

The student information system should be able to serve the applicant

with correct information and day-to-day update of information.

FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system.

That is the services that are provided to the member student registers

EXTERNAL INTERFACE REQUIREMANTS:

SOFTWARE REQUIREMENTS:

Front end : PHP

Back end :MYSQL

The purpose of the student information systems is to reduce the manual

intervention.

SCOPE

The scope of this student information system system is to act as a tool for information
administrator for quick reference, availability of the information.

23
FUNCTIONALITY

Many members will be waiting to take the information from the student at a
singleday. To serve all the members

USABILITY

User interface makes the Recruitment system to be efficient. That is the system
will help the member to register easily and helps them to get their information
easily.The system should be user friendly.

PERFORMANCE

It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.

RELIABILITY

The student information system should be able to serve the applicant

with correct information and day-to-day update of information.

FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system.

That is the services that are provided to the member student registers

EXTERNAL INTERFACE REQUIREMANTS

SOFTWARE REQUIREMENTS:

1. Front end : PHP

2. Back end : MSQL

24
 1. Processor : intel i3
2. RAM : 4GB RAM
3. Operating syatem : Microsoft windows

UML DIAGRAM

The following UML diagrams describe the process involved in the online
recruitment system
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. State chart diagram
f. Activity diagram
g. Component diagram
h. Deployment diagram
i. Package diagram

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 particular 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.

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are member and database. The use
cases are theactivities performed by actors.

a. The member will register himself in the student information.

25
b. After registration he will select the year to which he belongs

c. After selecting he will select student ‘s

d. Database will verify the status of register and the information will
be given.

26
 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.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has 8 classes:

o Member details class- is the class name. Its attributes

are name, father name, date of birth, address, phone
number, member id, college, degree, course and
semester. Its operations are registration
,authentication,and year selection.

o Administrator- is the class name. Its attributes are

name, address, phone, mail id. Its operations are
authentication, verification and issue information

o Year-is the class name. Its attribute is year selection.

Its operations are 1st year,2nd year, 3rd year,4th
year.

o Issue for 1,2,3rd year-is the class name. Its attributes

are member code, member name, book code, book name,
and quantity. Its operation is issue

27
SEQUENCE DIAGRAM:

A sequence 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 isa construct of a Message Sequence Chart. There
are two dimensions.
1. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show

a. The member registers himself in

b. He will select the year

c. He selects the student information given and the

database will update the status of information

d. Then administrator will log in and verify the status of information

registration
28
 e. If the student information is available, he will issue the staffs

COLLABRATION DIAGRAM:

A collaboration diagram, also called a communication diagram or

interaction diagram, a sophisticated modeling tool can easily convert a
collaboration diagram into a sequence diagram and the vice versa. A
collaboration diagram resembles a flowchart that portrays the roles,
functionality and behavior of individual objects as well as the overall
operation of the system in real time

DOCUMENTATION OF COLLABORATION DIAGRAM

The collaboration diagram is to show how the member registers himself

and borrow the book from the book bank. Here the sequence is
numbered according to the flow of execution.

29
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.

30
DOCUMENTATION OF STATE CHART DIAGRAM:

This state diagram describes the behavior of the system.

In the first state the member registers himself in student information

a. After that he will select the year in next state.

b. In the next state he will select the students

c. In the next state database will update the status of information

d. In the next state administrator will log i

31
RESULT:
Thus the project to implement Student Information System using Mysql and PHP has been
successfully designed

32
 EX.NO:
DATE: ONLINE- COURSE RESERVATION SYSTEM

AIM:
To develop a project of Online Course Reservation System using java Eclipse Software
and to implement the software in Visual Basic

ABSTRACT:
The Online Course Reservation System (OCRS) is an innovative solution catering to the
evolving landscape of educational booking needs. Designed with a user-centric approach,
OCRS aims to streamline the process of course reservation for both providers and
participants. At its core, OCRS offers a seamless user experience through an intuitive
interface, ensuring effortless navigation and efficient utilization of its functionalities. With
comprehensive course listings, participants can explore diverse educational offerings, each
accompanied by detailed information such as course descriptions, schedules, instructor
profiles, and pricing details. The system's advanced search and filtering capabilities empower
users to refine their search criteria, enabling them to quickly discover courses that align with
their preferences and requirements. Once a suitable course is found, participants can make
reservations directly through the platform, with integrated payment processing ensuring
secure transactions and timely confirmations. Moreover, OCRS incorporates a robust
feedback mechanism, allowing participants to provide insights and ratings based on their
course experiences. This feature fosters a culture of continuous improvement and
transparency, benefiting both participants and course providers.

33
SOFTWARE REQUIREMENT SPECIFICATION:
• INTRODUCTION
• OBJECTIVES
• OVERVIEW
• GLOSSARY
• PURPOSE
• SCOPE
• FUNCTIONALITY
• USABILITY
• PERFORMANCE
• RELIABILITY
• FUNCTIONAL REQUIREMENTS

INTRODUCTION:
An online course reservation system is a digital platform designed to facilitate the process
of registering for and managing enrollment in various courses offered by educational
institutions, training centers, or online learning platforms. It streamlines the entire process,
from browsing available courses to making payments and receiving confirmation of
enrollment.
OBJECTIVE:
To develop an efficient and user-friendly online course reservation system that streamlines
the process of course enrollment, providing a seamless experience for both students and
administrators. The system aims to enhance accessibility, improve transparency, and
optimize resource utilization within educational institutions, ultimately fostering a more
efficient and effective learning environment.
OVERVIEW:
An online course reservation system is a web-based platform designed to facilitate the
process of reserving seats or slots for various courses offered by educational institutions or
training providers. Here's an overview of its key components and functionalities
PURPOSE:
The purpose of the online course reservation system to reduce the manual intervention.

34
SCOPE:
The scope for an online course reservation system is quite broad and can encompass various
features and functionalities to meet the needs of different educational institutions and their
students. Here are some key aspects to consider when defining the scope of such a system
USABILITY:
An online course reservation system requires several key functionalities to effectively
facilitate the process of course selection, reservation, and management. Here's a breakdown
of essential functionalities for such a system
FUNCTIONALITY:
For an online course reservation system to be effective, it needs to incorporate a range of
functionalities that cater to the needs of both students and administrators. Here's a breakdown
of essential functionalities
PERFORMENCE: Ensuring optimal performance is crucial for an online course
reservation system to provide a seamless user experience and handle a large volume of
concurrent users. Here are key considerations for improving performance
REQUERMENTS: When defining the requirements for an online course reservation
system, it's essential to consider the needs of both users and administrators. Here's a
comprehensive list of requirements
SOFTWARE REQUIRMENTS
1. Front end : java
2. Back end: Visual Studio
UML DIGRAMS:
The following UML diagrams describe the process involved in the online
recruitmentsystem
a. Use case diagram

b. Class diagram

C. Sequence diagram

d. State chart diagram

e. Activity diagram
35
 f. Collaboration diagram

g. Component diagram

h. Deployment diagram

i. Package Diagram

USE CASE DIAGRAM

Creating a use case diagram for an online course reservation system involves
identifyingthe primary actors, their interactions with the system, and the
different use cases or functionalities the system provides. Here's a basic outline
of the use case diagram for an online course reservation system

36
CLASS DIAGRAM:

Creating a class diagram for an online course reservation system involves

identifying themain classes and their relationships.

DOCUMENTATION FOR CLASS DIAGRAM:

• User: Represents the users of the system. This can include students,
instructors,administrators

37
 • Course: Represents the courses available for reservation. Each course has
attributeslike name, description, duration, etc.
• Reservation: Represents the reservation made by a user for a particular
course. It includes attributes like reservation ID, date, time, etc. Each
reservation is associatedwith one user and one course.
• Payment: Represents the payment details associated with a reservation. It
includesattributes like payment ID, amount, payment method, etc. Each
payment is associated with one reservation.
• Instructor: Represents the instructors who teach the courses. An instructor
can beassociated with multiple courses.
• Admin: Represents the administrators who manage the system.
Admins haveprivileges to manage courses, users, reservations

SEQUENCE DIAGRAM:

Creating a sequence diagram for an online course reservation system involves

illustrating the interactions between various objects or components in the system to
achieve a specificfunctionality. Here's a sequence diagram for the process of
making a reservation

38
DOCUMENTATION OF SEQUENCE DIAGRAM:

• User: Initiates the reservation process by selecting a course and clicking

on the"Reserve" button.
• Reservation Controller: Receives the request from the user to make a reservation.
• Course Catalog: Retrieves course details based on the user's selection.
• Reservation Controller: Sends a request to check availability for the
selectedcourse.
• Reservation Manager: Checks if there are available slots for the
course at thespecified date and time.
• Reservation Manager: Sends a response to the Reservation Controller
indicatingthe availability status.

39
COLLABRATION DIAGRAM:

A collaboration diagram, also known as a communication diagram, illustrates how

objects interact to accomplish specific tasks or functionalities within a system. For
an online coursereservation system, here's a simplified collaboration diagram

DOCUMENTATION OF COLLABORATION DIAGRAM:

• Responsibilities:
o Display course information and availability.
o Capture user inputs for course selection and reservation
o Controller Module
o Course Management Module
o Reservation Management Module

STATE CHART DIAGRAM:

Creating a state chart diagram for an online course reservation system involves

40
identifying the various states that the system can be in and the transitions between
those states. Here'sa simplified example of a state chart diagram for an online
course reservation system

DOCUMENTATION OF CHART DIAGRAM

• This diagram represents the basic flow of states and transitions in an online
coursereservation system.
• The system starts with the user not logged in, then the user logs in and
navigates through the system to select a course, view course details, enroll in
the course, makea payment, receive confirmation, and then either cancel the
enrollment or log out

41
 EX.NO:
DATE: ONLINE RAILWAY RESERVATION SYSTEM

AIM:

To develop a project of Online-Railway reservation system using MYSQL

Database and to implement the software in PHP Admin

ABSTRACT:
The online railway reservation system programmed in PHP is a web-based platform that
facilitates the booking of train tickets. It provides an intuitive user interface for selecting travel
dates, routes, and trains, as well as real-time access to train schedules, seat availability, and fare
information. Users can securely make reservations and payments, and the system manages user
accounts, booking history, and cancellation/refund processing. Leveraging PHP for server-side
scripting, the system offers efficient and scalable performance, allowing railway authorities to
manage reservations and bookings seamlessly. The system's user-centric design enhances the
travel experience by providing convenient and accessible railway booking services online.The
railway reservation system facilitates the passengers to enquiry about the trains available on the
basis of source and destination, booking and cancellation of tickets, enquiry about the status of
the booked ticket, etc. The aim of case study is to design and develop a database maintaining
records of different trains, train status and passengers. Online reservation has made the process
for the reservation of seats very much easier than ever before. The record of train includes its
number, name, source, destination, and days on which it is available, whereas record of train
status includes dates for which tickets can be booked, total number of seats available, and number
of seats already booked.

42
SOFTWARE REQUIREMENT SPECIFICATION:
• INTRODUCTION
• OBJECTIVES
• OVERVIEW
• GLOSSARY
• PURPOSE
• SCOPE
• FUNCTIONALITY
• USABILITY
• PERFORMANCE
• RELIABILITY
• FUNCTIONAL REQUIREMENTS

INTRODUCTION:
The railway reservation system is a digital platform that enables customers to book train tickets
and manage reservations online. It provides real-time access to train schedules, seat availability,
and fare information. Users can search for trains based on routes and dates, view seat availability,
and make secure online payments to confirm bookings. The system supports user registration,
booking history management, and cancellation and refund options for a seamless experience. By
automating booking processes and reducing manual workload, the system improves operational
efficiency and minimizes errors such as overbooking, making train travel more accessible and
convenient for passengers.
OBJECTIVE:
The objective of the railway reservation system is to provide a convenient and efficient online
platform for booking train tickets and managing reservations. It aims to enhance customer
convenience by offering real-time information on train schedules, seat availability, and fares. The
system enables secure online payments and reservation management, including booking history,
cancellations, and refunds. By automating booking processes, it improves operational efficiency,
minimizes errors such as overbooking, and increases accessibility to railway services.

OVERVIEW:
The railway reservation system using PHP is a web-based application that allows customers to
book train tickets online. It provides real-time access to train schedules, seat availability, and fare
information, making it easy for users to select travel dates and routes.
GLOSSARY:
43
 • Booking: Reserving a train ticket for a specific date and route.
• Cancellation: Voiding a booking to free up seats.
• Fare: Cost of a train ticket based on route, class, and time.
• Payment Gateway: Service for secure online payments.
• Real-Time Information: Continuously updated data on train schedules and seat
availability.
• Reservation Management: Handling bookings, including creating, modifying, and
canceling.
• Route: The path a train follows, including starting and ending points.
• Seat Availability: Information on available seats for a train.
• User Authentication: Verifying a user's identity with login credentials.
• User Registration: Creating an account for new users.

PURPOSE:
The purpose of the railway reservation system is to provide customers with a convenient and
efficient online platform to book train tickets and manage reservations.
SCOPE:
The scope of the railway reservation system includes providing a comprehensive online
platform for booking train tickets and managing reservations. This involves offering real-time
train schedules, seat availability, and fare information, as well as secure online payment options.
The system supports user registration and authentication, booking history tracking, and
reservation management, including cancellations and refunds. Additionally, the system may
integrate with other railway systems for data exchange and may offer customer support features
to enhance user experience.
USABILITY:
The usability of the railway reservation system is defined by its user-friendly interface, offering
intuitive navigation and efficient search and filter options for easy booking. The system also
supports reservation management, such as viewing booking history and handling cancellations,
and includes feedback and support channels for a seamless user experience.
FUNCTIONALITY:
The functionality of a railway reservation system includes user registration and authentication,
train search and booking, real-time information on schedules and availability, secure online
payment processing, and reservation management such as cancellations and refunds.
PERFORMANCE:

44
 The system's performance is characterized by fast loading times and responsiveness, scalability
to handle increasing users and transactions, reliability with consistent uptime, security to protect
user data and transactions, and resource efficiency for smooth operation.

SOFTWARE REQUIREMENTS:
XAMPP SERVER
Front end: HTML, CSS, JavaScript
HTML: HTML is used to create and save web document. E.g. Notepad/Notepad++
CSS : (Cascading Style Sheets) Create attractive Layout
Bootstrap : responsive design mobile freindly site
JavaScript: it is a programming language, commonly use with web browsers.
Back end: PHP, MySQL
PHP: Hypertext Preprocessor (PHP) is a technology that allows software developers to create
dynamically generated web pages, in HTML, XML, or other document types, as per client
request. PHP is open source software.
MySQL: MySql is a database, widely used for accessing querying, updating, and managing data
in databases.
DIAGRAMS:
The following UML diagrams describe the process involved in the online reservation system
a. Use case diagram
b. Class diagram
c. State chart diagram
d. Activity diagram
e. Collaboration diagram
f. Component diagram
g. Deployment diagram
h. Package diagram

45
USE CASE DIAGRAM:
A use case diagram for a railway reservation system visually represents the interactions
between users (actors) and the system's use cases (functions). In the context of a railway
reservation system.

CLASS DIAGRAM:
A class diagram for a railway reservation system represents the structure of the system by
showing classes, their attributes, methods, and relationships between them.

46
COLLABRATION DIAGRAM:
A collaboration diagram, also known as a communication diagram, shows the interactions
between objects in a system and how they collaborate to achieve a specific task or use case. In a
railway reservation system, a collaboration diagram would illustrate the interactions among
objects such as user, reservation, train, route, payment, and admin to fulfill a booking request.

47
STATECHART DIAGRAM:
A state chart diagram, also known as a state machine diagram, shows the states an object can
be in and the transitions between those states. In the context of a railway reservation system, a
state chart diagram can be useful for depicting the life cycle of an object, such as a reservation,
as it progresses through different states from creation to completion or cancellation.

48
RESULT:
Thus the project to online- Railway Reservation System using PHP and MYSQL has been
successfully designed
49
 EX.NO:
DATE: PASSPORT AUTOMATION SYSTEM

AIM

To develop the Passport Automation System using rational rose tools, visual basic
and MS access.

PROBLEM ANALYSIS AND PROJECT PLAN

To simplify the process of applying passport, software has been created by designing
through rational rose tool, using visual basic as a front end and Microsoft access as
a back end. Initially the applicant login the passport automation system and submits
his details. These details are stored in the database and verification process done by
the passport administrator, regional administrator and police the passport is issued
to the applicant.
PROBLEM STATEMENT

1. Passport Automation System is used in the effective dispatch of passport to

all of the applicants. This system adopts a comprehensive approach to
minimize the manual work and schedule resources, time in a cogent manner.

2. The core of the system is to get the online registration form (with details such
as name, address etc.,) filled by the applicant whose testament isverified for
its genuineness by the Passport Automation System with respect to the already
existing information in the database.

3. This forms the first and foremost step in the processing of passport
application. After the first round of verification done by the system, the
information is in turn forwarded to the regional administrator's (Ministry of
External Affairs) office.

4. The application is then processed manually based on the report given by the
system, and any forfeiting identified can make the applicant liable to penalty
as per the law.

5. The system forwards the necessary details to the police for its separate
verification whose report is then presented to the administrator. After all the
necessary criteria have been met, the original information is added to the
database and the passport is sent to the applicant.
50
SOFTWARE REQUIREMENTS SPECIFICATION
SNO SOFTWARE
REQUIREMENTS
SPECIFICATION
Introduction
Purpose
Scope
Definition, Acronyms
and Abbreviations
Reference
Technology to be used
Tools to be used
Overview

Overall description
Productive description
Software interface
Hardware interface
System function
User Characteristic
Constraints
Assumption and
Dependences

PURPOSE

If the entire process of 'Issue of Passport' is done in a manual manner then it would
take several months for the passport to reach the applicant. Considering the fact that
the number of applicants for passport is increasing every year, an Automated System
becomes essential to meet the demand. So this system uses several programming and
database techniques to elucidate the work involved in this process. As this is a matter
of National Security, the system has been carefully verified and validated in order to
satisfy it.

SCOPE

The System provides an online interface to the user where they can fill in
their personal details. The authority concerned with the issue of passport can
use this system to reduce his workload and process the application in a speedy
manner. Provide a communication platform between the applicant and the
administrator Transfer of data between the Passport Issuing Authority and the.
51
DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

1. Administrator - Refers to the super user who is the Central Authority who has
been vested with the privilege to manage the entire system. It can be anyhigher
official in the Regional Passport Office of Ministry of External Affairs.
2. Applicant - One who wishes to obtain the Passport.
3. PAS - Refers to this Passport Automation System.

REFERENCES IEEE Software Requirement Specification format.

TECHNOLOGIES TO BE USED • Microsoft Visual Basic 6.0

TOOLS TO BE USED • Rational Rose 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-
connections. Specific requirements will describe roles & functions of the actors.

PRODUCT PERSPECTIVE
The PAS acts as an interface between the 'applicant' and the 'administrator'. This
system tries to make the interface as simple as possible and at the same time not
risking the security of data stored in. This minimizes the time duration in which the
user receives the passport.

SOFTWARE INTERFACE

1. Front End Client - The applicant and Administrator online interface is built
using Microsoft Visual Basic 6.0.
2. Back End – MS Access database

HARDWARE INTERFACE

The server is directly connected to the client systems. The client systems have
access to the database in the server.
SYSTEM FUNCTIONS

1. Secure Registration of information by the Applicants.

2. Message box for Passport Application Status Display by the Administrator.
3. Administrator can generate reports from the information and is the only
authorized personnel to add the eligible application information to the
52
 database.

USER CHARACTERISTICS

1. Applicant - They are the people who desires to obtain the passport and submit
the information to the database.
2. Administrator - He has the certain privileges to add the passport status and to
approve the issue of passport. He may contain a group of persons under him
to verify the documents and give suggestion whether or not to approve the
CONSTRAINTS

1. The applicants require a computer to submit their information.

2. Although the security is given high importance, there is always a chance of
intrusion in the web world which requires constant monitoring.
3. The user has to be careful while submitting the information. Much care is
required.

ASSUMPTIONS AND DEPENDENCIES

1. The Applicants and Administrator must have basic knowledge of computers

and English Language.
2. The applicants may be required to scan the documents and send.

UML DIAGRAMS
Sno UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Interaction diagram
4 Sequence diagram
5 Collaboration diagram
6 State Chart diagram
7 Activity diagram
8 Component diagram
9 Deployment diagram
10 Package diagram

53
DOCUMENTATION OF USECASE DIAGRAM

a. The actors in use case diagram are Applicant, regional administrator,

database, passport Administrator, Police.

b. The use cases are Login, give details, logout, collect

details,verification, issue.

c. The actors use the use case are denoted by the arrow

d. The login use case checks the username and password for applicant,
regional administrator, passport administrator and police.

e. The submit details use case is used by the applicant for submitting his
details

54
 f. The check status use case is used by the applicant for checking the
status of the application process.

g. The get details, verify and store verification use case is used bypassport
administrator, regional administrator, and police.

h. The details use case is used for getting the details form the database for
verification

2. The verify use case is used for verifying the details by comparing the data in
the database.

a. The store verification use case is to update the data in the database

b. And finally the issue passport use case is used by the passport
administrator for issuing passport whose application verified
successfully by all the actor.

CLASSDIAGRAM

A class is drawn as rectangle box with three compartments or components separated

by horizontal lines. The top compartment holds the class name and middle
compartment holds the attribute and bottom compartment holds list of operations

55
DOCUMENTATION OF CLASS DIAGRAM

a. APPLICANT-The applicant has attribute such as name and password

and operations are login, give details and logout. The applicant login
and fill the details that are required for applying the passport. After
applying the person can view the status of the passport verification
process
b. THE DATABASE-The database has attributed such as name and
operation is store. The purpose is to store the data.

c. REGIONAL ADMINISTRATOR- The regional administrator has

attribute such as name and operation are get details, verify details and
send. The regional administrator gets the details form database and
verify with their database

d. PASSPORT ADMINISTRATOR-The passport administrator has

attributed such as name and operation are get details, verify details and
issue. The passport administrator gets the details form database and
verify with their database, update the verification and issue the passport
e. THE POLICE-The police have attribute such as name and operation
are get details, verify details and send. The police get the details form
database and verify with their database, update the verification in the
database

56
SEQUENCE DIAGRAM

A sequence diagram shows an interaction arranged in time sequence,

It shows object participating in interaction by their lifeline by the message they
exchange arranged in time sequence. Vertical dimension represent time and
horizontal dimension represent object.

57
 DOCUMENTATION OF SEQUENCE DIAGRAM.

a. The applicant login the database and give his details and database
store the details.
b. The passport administrator gets the details from the database and
doverification and the forward to regional administrator.

c. The regional administrator get details form passport administrator and

perform verification and send report to passport administrator.

d. The police get the details form passport administrator and perform
verification and send report to passport administrator

COLLABORATION DIAGRAM

A collaboration diagram is similar to sequence diagram but the message in number

format. In a collaboration diagram sequence diagram is indicated by the numbering
the message. A collaboration diagram, also called a communication diagram or
interaction diagram, a sophisticated modeling tool can easily convert a
collaboration diagram into a sequence diagram and the vice versa. A collaboration
diagram resembles a flowchart that portrays the roles, functionality and behavior of
individual objects as well as the overall operation of the system in real time
STATE CHART DIAGRAM
The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state
chart diagram is to understand the algorithm in the performing method.

DOCUMENTATION OF STATE CHART DIAGRAM

a. The states of the passport automation system are denoted in the state
chart diagram

b. Login state represent authentication for login the passport automation

system.

c. In this state, it checks whether the applicant has provided all the

58
 details that is required.

d. Police, regional administrator and passport administrator get

necessary details and verification of the applicant are denoted from
the Get detail state and verification stateACTIVITY DIAGRAM
An activity diagram is a variation or special case of a state machine in which the
states or activity representing the performance of operation and transitions are
triggered by the completion of operation. The purpose is to provide view of close
and what is going on inside a use case or among several classes. An activity is shown
as rounded box containing the name of

DOCUMENTATION OF ACTIVITY DIAGRAM

a. The activities in the passport automation system are login, submit

details, get details, issue passport and penalty and verification.

b. In the login activity applicant give username and password and then
login into the passport automation system after then fill the details that
are required for application.

c. After the verification procedure completed successfully the passport is

issued to the applicant.

COMPONENT DIAGRAM

The component diagram is represented by figure dependency and it is a graph of

design of figure dependency. The component diagram's main purpose is to show the
59
structural relationships between the components of a systems. It is represented by
boxed figure. Dependencies are represented by communication assosiation.

DOCUMENTATION OF COMPONENT DIAGRAM

a. The components in the passport automation system are passport

automation system, applicant, passport administrator, regional
administrator, and police.

b. Applicant, passport administrator, regional administrator and police are

dependent on passport automation system are shown by the dotted
arrow
DEPLOYMENT DIAGRAM
It is a graph of nodes connected by communication association. It is represented by
a three dimensional box. 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 represented by 3-dimentional box.
Dependencies are represented by communication association. The basic element of
a deployment diagram is a node of two types

DEVICE NODE–
A physical computing resource with processing and memory service to execute
software, such as a typical computer or a mobile phone.

60
EXECUTION ENVIRONMENT NODE
This is a software computing resource that runs within an outer node and which
itself provides a service to host an execute other executable software element.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The device node is passport automation system and execution environment node
are applicant passport administrator, regional administrator, and police.

PACKAGE DIAGRAM

A package diagram is represented as a folder shown as a large rectangle with a top

attached to its upper left corner. A package may contain both sub ordinate package
and ordinary model elements. All uml models and diagrams are organized into
package. A package diagram in unified modeling language that depicts the
dependencies between the packages that make up a model. A Package Diagram (PD)
shows a grouping of elements in the OO model, and is a Cradle extension to UML.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
components or processes in Component Diagrams (CPDs), or groups of processors
in Deployment Diagrams (DPDs).
There are three types of layer. They are

o User interface layer

o Domain layer

o Technical services layer

61
62
DOCUMENTATION OF PACKAGE DIAGRAM

The three layer in the passport automation system are user interface layer, domain
layer, technical service layer

a. The user interface layer- represents the user interface components

such as web, applicant, passport administrator, police, and regional
administrator.

b. The domain layer- has major actions such as give and get details,
verification and issues.

c. Technical service layer- authenticated user only can access the

technical services.

63
RESULT:
Thus the project to develop passport automation system was developed using
Rational Rose Software and to implement the software in Visual Basic is
done successfully.

64
 EX.NO:
DATE: ONLINE –EXAM REGISTRATION

AIM:
To develop a project Exam Registration using Rational Rose Software and to
implement the software in Visual Basic.

PROBLEM ANALYSIS AND PROJECT PLANNING:

The Exam Registration is an application in which applicant can register
themselves for the exam. The details of the students who have registered for the
examination will be stored in a database and will be maintained. The registered
details can then be verified for any fraudulentor duplication and can be removed if
found so. The database which is verified can be used to issue hall tickets and other
necessary materials to the eligible students.

PROBLEM STATEMENT:
The process of students accessing the registration application and applying for the
examination by filling out the form with proper details and then the authorities
verify those details given for truth and correctness are sequenced through steps

a. The students access exam registration application.

b. They fill out the form with correct and eligible details.
SOFTWARE REQUIREMENT SYSTEM:
12. INTRODUCTION
13. OBJECTIVE
14. OVERVIEW
15. GLOSSARY
16. PURPOSE
17. SCOPE
65
18. FUNCTIONALITY
19. USABILITY
20. PERFORMANCE
21. RELIABILITY
22. FUNCTIONAL REQUIREMENTS
INTRODUCTION

Exam Registration application is an interface between the Student and the

Authority responsible for the Exams. It aims at improving the efficiency in the
registration of exams and reduces the complexitiesinvolved in it to the maximum
possible extent.
1. OBJECTIVE
The main objective of Exam Registration System is to make applicants register
themselves and apply for the exam. Exam Registration System provides easy
interface to all the users to apply for the exam easily.
2. OVERVIEW
The overview of the project is to design an exam registration tool for the
registration process which makes the work easy for the applicant as well as the
Authorities of Exam. Authorities of the exam can keep track of and maintain the
database of the registered applicants for the exams.
3. GLOSSARY
Applicant can register himself by filling out the registration form and finally
paying the payment for attending the exam.

Database is used to maintain and store the details of registered applicants.

SOFTWARE REQUIREMENT SPECIFICATION

This software specification documents full set of features and functionfor

online recruitment system that is performed in company website.

4. PURPOSE
The purpose of exam registration system is to register for the exam in aneasier
way and to maintain the registered details in an effective manner. 6. SCOPE
The scope of this Exam Registration process is to provide an easyinterface to the
applicants where they can fill their details and the authorities maintain those details
in an easy and effective way.

66
 7. FUNCTIONALITY
The main functionality of registration system is to make the registration and
database for it to be maintained in an efficient manner.
8. USABILITY
User interface makes the Exam Registration system to be efficient. That is the
system will help the applicant to register easily and helps the authorities to
maintain details effectively. The system should be user friendly.
9. PERFORMANCE
It describes the capability of the system to perform the registrationprocess of the
applicant without any error and performing it efficiently.
10. RELIABILITY
The Exam Registration system should be able to serve the applicant withcorrect
information and day-to-day update of information.
11. FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the applicant who apply for the Exam.
12. EXTERNAL INTERFACE REQUIREMANTS
SOFTWARE REQUIREMENTS
1. Front end: HTML,Css and Javascript
2. Back end: visual basic 8.0.

UML DIAGRAMS
The following UML diagrams describe the process involved in the online
recruitment system

a. Use case diagram

b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. State chart diagram
f. Activity diagram
g. Component diagram
h. Deployment diagram
i. Package diagram

67
 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 particular goal. It is represented using ellipse.Actor is any external
entity that makes use of the system being modelled. It is represented using stick
figure

DOCUMENTATION OF USE CASE DIAGRAM:

The actors in this use case diagram are Student, Interface and Database. Theuse
cases are the activities performed by actors.

a. Student Fills out the form in the form filling process.

b. The interface checks and validates registered details.
c. Then the database is searched for details and verified.
d. Database stores the details and returns acknowledgement.

68
 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 compartment the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM:

This class diagram has three classes applicant, recruiter and database.

a. Students – is the class name. Its attributes are name, Address, DOB,Gender,
College, Subjects, Semester, Year, Degree, Branch and Payment. The
operations performed in the students’ class are form filling, search database and
receiving acknowledgement.
b. Registrations Interface – is the class name. Its attributes are Login, Password
and database. The operations performed are form verification,store in database
and send acknowledgement.

c. Database – is the class name. The operations performed are storingSearch

and storing the values.

69
 SEQUENCE DIAGRAM:
A sequence 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-represent time.
2. Horizontal dimension-represent different objects.

70
 DOCUMENTATION OF SEQUENCE DIAGRAM:
The sequence diagram describes the sequence of steps to show
a. The applicant filling form and registering for exam.
b. The verification done by the interface and sending acknowledgementfor
registration.
c. Searching the database with login and displaying it for maintenance.

COLLABRATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction
diagram,. A sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects
as well as the overall operation of the system in real time

DOCUMENTATION OF COLLABRATION DIAGRAM:

The collaboration diagram is to show how the Student registers and the authorities
maintains the details of the registered students in the registration system. Here the
sequence is numbered according to the flow of execution.

71
 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. A final state isrepresented as circle surrounding a small
dot.

DOCUMENTATION OF STATE CHART DIAGRAM:

This state diagram describes the behaviour of the system.

a. First state is form filling where the student fill the form to registrationsystem.
b. The next state is form verification by the interface.
c. Then store the details in the database.

d. The student receives acknowledgement for registering.

e. Search database with login information.
f. Display the searched data in the interface.

72
 ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows ofstepwise 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 a rounded box containing the name ofthe operation.

DOCUMENTATION OF ACTIVITY DIAGRAM:

This activity diagram flow of stepwise activities performed in recruitmnet system.

a. First the student fills the form.

b. The student details are verified and stored in database.
c. Acknowledgement sent is received by student.

d. Search database with login and if data present in the database.

e. The searched data is displayed if available.

COMPONENT DIAGRAM:
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure.
Dependencies are represented by communication association.

73
DOCUMENTATION OF COMPONENT DIAGRAM:
The main component in this component diagram is Exam Registration system. And
register, verification and search details are the components comes under the main
component.

DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modeling language serves to modelthe
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 represented by 3-dimentional box. Dependencies are
represented by communication association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM:

74
 The processor in this deployment diagram is the Exam Registrationsystem which
is the main part and the devices are the register, verify andsearch which are the
some of the main activities performed in the system.

PACKAGE DIAGRAM:
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML. PDs
can be used to show groups of classes in Class Diagrams (CDs), groups of
componentsor processes in ComponentDiagrams (CPDs), or groups of processors
in Deployment Diagrams (DPDs).
There are three types of layer. They are
a. User interface layer
b. Domain layer
c. Technical services layer

75
RESULT:
Thus the project to online- Course Reservation System using HTML has been
successfully designed

76
 EX.NO:
DATE: CREDIT CARD PROCESSING

AIM
Credit card processing is a system that facilitates the electronic transfer of funds
from a customer's credit card account to a merchant's account to complete a
financial transaction.
ABSTRACT
Credit card processing is a crucial aspect of modern commerce, enabling
businesses to accept electronic payments securely and efficiently. This process
involves authorization, authentication, clearing, and settlement stages to ensure
that transactions are valid and funds are transferred accurately. With the rise of e-
commerce and digital payments, credit card processing systems continue to evolve,
incorporating advanced security measures and faster transaction speeds to meet the
demands of consumers and merchants alike.

INTRODUCTION.
The credit card network sends an authorization request to the cardholder's issuing
bank. The credit card issuer verifies customer identity and available credit, approves
the purchase, and responds to the payment network. The payment network relays
this information to the credit card processing company.

1. OBJECTIVE
Credit card processing allows you to accept credit card
payments. It includes everything that happens behind the scenes,
from when a customer hands you a card until you receive the money
in your account. This process applies tobrick-and-mortar and e-
commerce sales, as well as purchases made over the phone or by
mail.
2. OVERVIEW
Once you have selected the right card for yourself, check with the bank about
your eligibility for the card and the documents you must submit with your Credit

77
 Card application. Get all your documents ready – a bank will usually ask for
identity, address and income proofs.
3. GLOSSARY
A method of online fraud where someone gains access to an
online account by acquiring the login, often by theft, and then takes
over the account and its access from the rightful owner.
4. PURPOSE.
A credit card is a type of credit facility, provided by banks
that allow customers to borrow funds within a pre-approved credit
limit. It enables customers to make purchase transactions on goods
and services.
5. SCOPE.
A credit card is a card used for payment that is given to
cardholders to allow them to pay a merchant for products and
services based on the debt they have accumulated.
6. FUNCTIONALITY.
A credit card allows you to spend money up to a pre-set limit.
You'll get a bill for what you've spent each month. It's important to
try to pay off the balance in full every month. But you'll need to pay
off at least the minimum amount.
7. USABILITY.
A credit card is a physical card that can be used to make purchases, pay
bills, or, depending on the card, withdraw cash. The simplest way to
think of a credit card is as a type of short-term loan. When you open
a credit card account, your credit card company gives you a set credit
limit.
8. PERFORMANCE.
The current 12-month average charge-off rate as of December was
2.25%, also higher than the same period one year ago, which registered
1.82%. Similarly, 60+ day delinquency performance continued to increase as
it recorded 1.00% in December 2023, representing the highest level since July
2002.

78
9. RELIABILITY.
One of the most significant risks associated with Credit Cards is the
potential for accumulating debt. Credit Cards make it easy to overspend, and
if you're not careful, you can quickly accumulate debt you may struggle to
repay. This can lead to high-interest rates, late fees, and damage to your credit
score.
10. FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system.
That is the services that are provided to the member who borrows credit card.
EXTERNAL INTERFACE REQUIREMANTS.
SOFTWARE REQUIREMENTS:
Front end: PHP
Back end: MYSQL
PURPOSEHARDWARE REQUIREMENTS
1. Processor : intel i3
2. RAM : 4 GB
3. Operating syatem : Microsoft windows

UMLDIRAM
The following UML diagrams describe the process involved in the online
recruitment system
a. Use case diagram.
b. Class diagram.
c. Sequence diagram.
d. Collaboration diagram.
e. State chart diagram.
f. Activity diagram.

79
 g. Component diagram.
h. Deployment diagram.
i. Package diagram.
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 particular goal. It is represented using ellipse.
Actor is any external entity that makes use of the system being model.
It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are member and database. The use
cases are the activities performed by actors.
a. The member will register himself in the book bank.
b. After registration he will select the year to which he belongs

80
 c. After selecting he will select books.
d. Database will verify the status of book and the books will.
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.

81
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has 8 classes:
Member details class- is the class name. Its attributes are name, father name, date
of birth, address, phone number, member id, college, degree, course and semester.
Its operations are registration, authentication, and year selection. O
Administrator- is the class name. Its attributes are name, address, phone, mail id. Its
operations are authentication, verification and issue books. O
Year-is the class name. Its attribute is year selection. Its operations are 1st year,2nd
year, 3rd year,4th year. O
Issue for 1st year-is the class name. Its attributes are member code, member name,
book code, book name, and quantity. Its operation is issue Issue for 2nd year-is the
class name. Its attributes are member code, member name, book code, book name,
and quantity. Its operation is issue o Issue for 3rd year-is the class name. Its attributes
are member code, member name, book code, book name, and quantity. Its operation
is issue. Horizontal dimension-represent different objects

82
RESULT:
Thus the project to CREDIT CARD PROCESSING System using HTML has been
successfully designed
83