1.
PASSPORT AUTOMATION SYSTEM
AIM: To create an automated system to perform the Passport Process.
PROBLEM STATEMENT: 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. 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 is verified for its genuineness by the Passport Automation
System with respect to the already existing information in the database.
SOFTWARE REQUIREMENT SPECIFICATION:
SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online interface is built using JSP and HTML. The
Administrator’s local interface is built using Java.
•Web Server - Glassfish application server (Oracle Corporation).
•Back End - Oracle database.
HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have access to the database in the
server.
USECASE DIAGRAM:
registrati
enter applicant
id
check
administrat
applica process
dispatch passport
Fig.3. USECASE DIAGRAM FOR PASSPORT AUTOMATION SYSTEM
(IV) ACTIVITY DIAGRAM:
Fig.4.1. ACTIVITY DIAGRAM FOR REGISTER
Fig.4.2. ACTIVITY DIAGRAM FOR ADMINISTRATION
Fig.4.3. ACTIVITY DIAGRAM FOR CHECKING STATUS
(V) 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 Passport Automation system class diagram consists of four classesPassport
Automation System
1. New registration
2. Gender
3. Application Status
4. Admin authentication
5. Admin Panel
Fig.5. CLASS DIAGRAM FOR PASSPORT AUTOMATION SYSTEM
2.BOOK BANK SYSTEM
AIM:
To create a system to perform book bank operation
(I) PROBLEM STATEMENT:
A Book Bank lends books and magazines to member, who is registered in the
system. Also it handles the purchase of new titles for the Book Bank. Popular titles are
brought into multiple copies. Old books and magazines are removed when they are out or
date or poor in condition. A member can reserve a book or magazine that is not currently
available in the book bank, so that when it is returned or purchased by the book bank, that
person is notified. The book bank can easily create, replace and delete information about
the tiles, members, loans and reservations from the system.
(II) SOFTWARE REQUIREMENTS SPECIFICATION: 2.1SOFTWARE
INTERFACE
Front End Client - The Student and Librarian online interface is built using
JSP and HTML. The Librarians local interface is built using Java.
Web Server - Glassfish application server (Oracle Corporation).
Back End - Oracle database
2.2HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
access to the database in the server.
(III)USE-CASE DIAGRAM:
Fig 3. USE-CASE DIAGRAM FOR BOOK BANK SYSTEM
(IV) ACTIVITY DIAGRAM:
Fig.4. ACTIVITY DIAGRAM
(V) 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.
Fig.5. CLASS DIAGRAM FOR BOOK BANK SYSTEM
3.EXAM REGISTRATION SYSTEM
AIM:
To create a system to perform the Exam Registration system
(I) PROBLEM STATEMENT:
Exam Registration system.is used in the effective dispatch of registration form
to all of the students. This system adopts a comprehensive approach to minimize the
manual work and schedule resources, time in a cogent manner. The core of the system
is to get the online registration form (with details such as name, reg.no etc.,) filled by
the student whose testament is verified for its genuineness by the Exam Registration
System with respect to the already existing information in the database.
(II)SOFTWARE REQUIREMENT SPECIFICATION: 2.1SOFTWARE
INTERFACE
• Front End Client - The student and Controller online interface is built using
JSP and HTML. The Exam Controller's local interface is built using Java.
• Web Server - Glassfish application server(SQlCorporation).
• Back End - SQL database.
2.2HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
Access to the database in the server.
(III)USECASE DIAGRAM:
The Exam Registration use cases in our system are:
1. Login
2. View exam details
3. View fees details
4. Pay fee
5. Display details
6. Logout
USECASE DIAGRAM :
Fig. 3.USECASE DIAGRAM FOR EXAM REGISTRATION SYSTEM
(IV) ACTIVITY DIAGRAM:
Fig. 4.USECASE DIAGRAM FOR EXAM REGISTRATION SYSTEM
(V)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.
Fig.5. CLASS DIAGRAM FOR EXAM REGISTRATION SYSTEM
4.STOCK MAINTENANCE
AIM:
To create a system to perform the Stock maintenance
(I) PROBLEM STATEMENT
The stock maintenance system must take care of sales information of the
company and must analyze the potential of the trade. It maintains the number
of items that are added or removed.The sales person initiates this Use case.
The sales person is allowed to update information and view the database.
(II) SOFTWARE REQUIREMENT SPECIFICATION
1.1 PURPOSE
The entire process of Stock maintenanceis done in a manual manner
Considering the fact that the number of customers for purchase is increasing
every year, a maintenance system is essential to meet the demand. So this
system uses several programming and database techniques to elucidate the
work involved in this process.
1.2 SCOPE
• The System provides an interface to the customer where they can fill
in orders for the item needed.
• The sales person is concerned with the issue of items and can use
this system.
• Provide a communication platform between the customer and
the sales person.
1.3 TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
(III) USE CASE DIAGRAM
The functionality of a system can be described in a number of different
use-cases, each of which represents a specific flow of events in a system. It is
a graph of actors, a set of use-cases enclosed in a boundary, communication,
associations between the actors and the use-cases, and generalizationamong
the use-cases
Place
Order
Track
order
Custom
er
Validate
Ship Customer
Order
Ship Partial
Order
Sales
Person
Bill Customer
Fig.3. USE CASE DIAGRAM
(IV) ACTIVITY DIAGRAM
It shows organization and their dependence among the set of
components. These diagrams are particularly useful in connection with
workflow and in describing behavior that has a lot of parallel processing. An
activity is a state of doing something: either a real-world process, or the
execution of a software routine.
Custome
r
Sale
Request s
Service
Pay Take Fill
Order Order
Delive
r
Collec
t
Fig.4. ACTIVITY DIAGRAM
(V) CLASS DIAGRAM
Description:
A class diagram describes the type of objects in system and
various kinds of relationships that exists among them.
Class diagrams and collaboration diagrams are alternate
representations of object models.
Fig.5. CLASS DIAGRAM
5.ONLINE COURSE RESERVATION SYSTEM
AIM
To design an object oriented model for course reservation system.
(I) PROBLEM STATEMENT
a. Whenever the student comes to join the course he/she should
be provided with the list of course available in the college.
b. The system should maintain a list of professor who is teaching
the course. At the end of the course the student must be
provided with the certificate for the completion of the course.
(II) SYSTEM REQUIEMENT SPECIFICATION
OBJECTIVES
a. The main purpose of creating the document about the
software is to know about the list of the requirement in the
software project part of the project to be developed.
b. It specifies the requirement to develop a processing
software part that completes the set of requirement.
SCOPE
a. In this specification, we define about the system requirements
that are about from the functionality of the system.
b. It tells the users about the reliability defined in usecase
specification
FUNCTIONALITY
Many members of the process line to check for its occurrences and transaction,
we are have to carry over at sometimes
USABILITY
The user interface to make the transaction should be effectively
PERFORMANCE
It is the capability about which it can performed function for many user at
sometimes efficiently (ie) without any ever occurrences
RELIABILITY
The system should be able to the user through the day to day transaction
(III) USERCASE DIAGRAM
a. Use case is a sequence of transaction in a system whose task is
to yield result of measurable value to individual author of the
system
b. Use case is a set of scenarios together by a common user goal
c. A scenario is a sequence of step describing as interaction
between a user and a system
CLASS DIAGRAM:
A class diagram describes the type of objectors in the system the various
kinds of static relationship that exist among them.
To develop the Airline/Railway reservation System using Rational Rose
Software.
6.AIRLINE/RAILWAY RESERVATION SYSTEM
AIM
(I) PROBLEM ANALYSIS AND PROJECT PLANNING
In the Airline/Railway reservation 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.
(II) OVERALL DESCRIPTION
2.1 Functionality
The database should be act as an main role of the e-ticketing system it can be
booking the ticket in easy way.
2.2 Usability
The User interface makes the Credit Card Processing System to be efficient.
2.3 Performance
It is of the capacities about which it can perform function for many users
at the same times efficiently that are without any error occurrence.
2.4 Reliability
The system should be able to process the user for their corresponding request.
(III) USE CASE DIAGRAM
The passenger can view the status of the reserved tickets. So the passenger
can confirm his/her travel.
Fig. USE-CASE DIAGRAM FOR AIRLINE RESERVATION
(IV) CLASS DIAGRAM
The online ticket reservation system makes use of the following classes:
1. ticketReservation
2. trainInfo
3. passengerInfo
4. seatAvailStatus
7. SOFTWARE PERSONNEL MANAGEMENT SYSTEM
AIM:
To implement a software for software personnel management system.
(I) PROBLEM STATEMENT:
Human Resource management system project involves new and/or
system upgrades of software of send to capture information relating to the
hiring termination payment and management of employee. He uses system to
plan and analyze all components and performance of metrics driven human
resource functions, including recruitment, attendance, compensation, benefits
and education. Human resources management systems should align for
maximum operating efficiency with financial accounting operations customer
relationship management,security and business lines as organization.
( II )SOFTWARE REQUIREMENT SPECIFICATION:
2.1SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online interface
is built using
JSP and HTML. The HR's local interface is built using Java.
• Server - Glassfish application server (SQL Corporation).
• Back End - SQL database.
2.2HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.
( III )USECASE DIAGRAM:
The HR of an organization involves recruitment training, monitoring and
motivation of an employee. The HR also involves gives salary as observed
in the payroll sheet. The employee undergoes training, receives the salary ,
gives the expected performance and manages time in order to complete a
given task within the required period.
Fig.3. USE CASE DIAGRAM
(IV) ACTIVITY DIAGRAM:
The activity diagram notation is an action, partition, fork join and object
node. Most of the notation is self-explanatory, two subtle points. Once an
action finished, there is an automatic outgoing transaction. The diagram can
show both control flow and data flow.
Fig.4. ACTIVITY DIAGRAM
(V) 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.
Fig.5.CLASS DIAGRAM
8.CREDIT CARD PROCESSING
AIM:
To create a system to perform the credit card processing
(I) PROBLEM STATEMENT:
Credit card processing through offline involves the merchant collecting
order information (including credit card numbers), storing this in a database on
your site, and entering it using their on-site merchant credit card processing
system. Takes time to manually enter credit card information for each order.
This solution creates following cons:
( II )SOFTWARE REQUIREMENT SPECIFICATION:
2.1 PRODUCT PERSPECTIVE
This solution involves signing up for a free Business Account. Once this
is done and the e-commerce site is properly configured, you can accept
payments from Visa, MasterCard, Amex, and Discover cards payments.
2.2SOFTWARE INTERFACE
• Front End Client - The applicant and Administrator online
interface is built using
JSP and HTML. The Administrators's local interface is built using Java.
• Web Server - Glassfish application server(SQL Corporation).
• Back End - SQL database.
2.3HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems
have access to the database in the server.
( III )USECASE DIAGRAM:
USE-CASE NAME: PAYMENT APPROVAL
The transaction details are recorded by the credit card processor and
results are securely relayed to the merchant. Merchant’s site receives
transaction result and does appropriate actions (e.g. saves the order & shows
message).
Fig.3. USECASE DIAGRAM FOR PASSPORT AUTOMATION
SYSTEM
(IV) 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 Credit Card Processing system class diagram consists of three
classes.
They are
Cashier
User
Authorization Service
Fig.4.CLASS DIAGRAM
9.E-BOOK MANAGEMENT SYSTEM
AIM:
To create a system to perform E- book Management System.
(I) PROBLEM STATEMENT:
An E- Book lends books and magazines to member, who is registered in
the system. Also it handles the purchase of new titles for the Book Bank.
Popular titles are brought into multiple copies. Old books and magazines are
removed when they are out or date or poor in condition. A member can reserve
a book or magazine that is not currently available in the book bank, so that
when it is returned or purchased by the book bank, that person is notified. The
book bank can easily create, replace and delete information about the tiles,
members, loans and reservations from the system.
(II) SOFTWARE RESOURCE SPECIFICATION:
2.0 OVERALL DESCRIPTION
Itwill describe major role of the system components and inter-
connections.
2.1PRODUCT PERSPECTIVE
The ORS acts as an interface between the user and the 'e-book
manager'. 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 books or magazines.
2.2SOFTWARE INTERFACE
Front End Client - The Student and Librarian online interface is built
using JSP and HTML. The Librarians local interface is built using Java.
Web Server - Glassfish application server (Oracle Corporation).
Back End - Oracle database
2.3HARDWARE INTERFACE
The server is directly connected to the client systems. The client
systems have access to the database in the server.
(III) USE-CASE DIAGRAM:
Fig.3.USE-CASE DIAGRAM FOR E-BOOK SYSTEM
(IV) ACTIVITY DIAGRAM:
(V) 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.
Fig.5.CLASS DIAGRAM FOR E-BOOK SYSTEM
10. LIBRARY MANAGEMENT SYSTEM
AIM
To design an object oriented model for Library Management System using
Rational Rose software and to implement it using Java.
PROBLEM STATEMENT
The library management system is a software system that issues books and
magazines to registered students only. The student has to login after getting
registered to the system. The borrower of the book can perform various
functions such as searching for desired book, get the issued book and return
the book.
CLASS DIAGRAM
A class diagram in the unified modeling language is a type of static structure
diagram that describes the structure of a system by showing the system’s
classes, their attributes, operations and the relationships among objects. The
library management system makes use of the following classes user,
librarian, system and DBA.
USE CASE DIAGRAM
Use case is a list of actions or events. Steps typically defining the
interactions between a role and a system to achieve a goal. The use case
diagram consists of various functionality performed by actors like user,
librarian, system and DBA.
logi
n
enter name and <<actor>
password >
display
page
requesting for
use book
r
display book
details
search for
book libraria
n
issue
book
return
book
DBA
maintain
database
