Ooad Lab Manual 1

EXPT NO:
DATE:
CREDIT CARD PROCESSING
PROBLEM STATEMENT:
The system developed should contain the following features:The Customer has to
login into the system using Credit Card or Debit Card number and Pin Number. The
system should check for validation.
The System queries the customer for the type of account either Savings Account or
Current Account. After getting the type of account,the system shows the list of
items such as balance enquiry, withdrawal ,cancel options. when the customer
select the balance enquiry option, then the system shows the balance that left in
the account and prints as receipt.when the customer select the withdrawal option
then the system should ask the amount.The minimum amount in the savings
account should be 5000,if the customer violates the n the system should give a
warning message.The minimum amount of current account should be 1000,if
violates give warning message.
Then print the transaction amount in the receipt after withdrawal process. The
maximum transaction amount should be 20,000.
If the customer select the cancel option, then stop all the process and eject the
card.
1. INTRODUCTION:
This project is aimed at developing a credit card processing system by creating details about
customers and provide transaction.
1.1 PURPOSE:
Manual maintenance of customer details is a tedious process considering the to the large number
of customers. Hence, this system is used for easy registration and maintenance of database.
1.2. SCOPE:
The credit card processing is used to specify a certain procedure to the customers for quick and
easy transaction.
1.3. DOCUMENT CONVENTIONS:
Manager - The person who has the full authority over the system. He can view all
registered users.
Customer-The person who registers and obtains books from the Book bank.
Bank-The entire System comprising of the customers, manager, staff and other elements.
1.4. REFERENCES:
www.rec.in
2 OVERALL DESCRIPTIONS:
2.1 PRODUCT PERSPECTIVE:
This project is a self-contained project for convenient credit card processing.
2.3 TOOLS TO BE USED

Rational Rose
3. SYSTEM FEATURES
3.1 APPLYING FOR JOB:
3.1.1 SYSTEM DESCRIPTION AND PRIORITY:
This feature allows the customers to know the procedure to access transaction.
4 OTHER NON-FUNCTIONAL REQUIREMENTS:
4.1 PERFORMANCE MANAGEMENT:
To increase the performance and free up database resources, the default features are written
to cache files on their initial load.
4.2 SAFETY REQUIREMENTS:
The database must be maintained effective from hacking.
4.3SECURITY REQUIREMENTS:
Seperate and unique ids must be provided for each and every user so that no user can access the
resources available to other users.
GANTT CHART:
UML DAIGRAMS
USE CASE DIAGRAM:
login
register
customer service
customer
bank details
customer details
payment details
CLASS DIAGRAM:
CUSTOMER
DETAILS
CID
CNAME
address
phno
name
bank
verify details()
accept details()
PAYMENT DETAILS
acc_no
cname
cid
amt
payment mode()
cardn stmt generation()
SEQUENCE DIAGRAM:
ACTIVITY DIAGRAM:
COLLABORATION DIAGRAM:
getdetails()
display details()
payment details()
STATE CHART DIAGRAM: (PAYMENT)
LOGIN
ENTER
MODE
ENTER AMT
PAY
GENERATE
STMT
PACKAGE DIAGRAM:
COMPONENT DIAGRAM:
BANK
CUSTOMER
PAYMENT
DEPLOYMENT DIAGRAM:
DATABASE
CUSTOMER
SERVICE
CUSTOMER
RESULT:
Thus the UML models for the credit card processing have been developed and verified.
EX NO:
DATE :
EBOOK
Problem Analysis:
The problem is to find out the book that we need with reference to the prescribed author .The books
will be categorized in to various sections . Some of the sections include Novels,Love and Romance etc.
Ebooks of various author can be found in ease.
SOFTWARE REQUIREMENT SPECIFICATION
1. INTRODUCTION:
The statement of the system is to group the books in various categories according to users comfort.The
main objective is to provide all the versions of book.
PURPOSE:
The system is designed with end user requirements as main criteria. It includes front end tool to receive
data needed and to validate the entries. It has backend access to store validate data for future reference.To
analyze and design a EBOOK based on Object Oriented Analysis and Design concept.
1.2. SCOPE:
The system designed is capable of providing functional requirements based on book we chose and the
Author we wish. Non-functional requirements are clarity,text decoration ,simple language etc.
DOCUMENT CONVENTIONS:
Administrator - The person who has the full authority over the system. He can view all
registered users.
Job Seekers - the person who registers in the system in search of jobs.
Company - A company can register itself, select the required employees and provide
information about the result.
1.4. REFERENCES:
www.timesjob.com:
This project is a self-contained project for convenient recruitment process.
2.2 PRODUCT FUNCTIONS:
The front end of the project is where the visitors or job seekers do their enrollment. The
back end is managed by the administrator effectively
Rational Rose Enterprise Edition, AgroUML
3. SYSTEM FEATURES
This feature allows the job seeker to apply for job.
3.1.2 STIMULUS AND RESPONSE SEQUENCE:
When the user types the book, a list of possible e-books has to be displayed along with other details
3.1.3 FUNCTIONAL REQUIREMENTS:
REQ1: Only registered users can search and download.

Password for registered accounts are stored securely in a hash, the uploads made by the
user must be checked and then accepted.
GANTT CHART:
use case diagram
CLASS DIAGRAM:
sequence diagram:
Activity diagram
Collaboration diagram
STATECHART:
Package diagram
DEPLOYMENT DIAGRAM:
RESULT:
Thus the UML diagrams for EBOOK management system were developed and verified.
EXPT NO:
E-TICKETING
DATE:
PROBLEM STATEMENT:
Here the passenger who used to login, who used to view the train details and they can able to
cancel the tickets. The system administrator who used to manage the users and the security. The
railway database which is getting include by all the passenger details like view train details and
cancel the ticket. In extra of the railway database they can reserve the tickets which was enroll by
the passenger.
SOFTWARE REQUIREMENT SPECIFICATION:
1. INTRODUCTION:
This project which aims to reserve the ticket using the login form. The passenger can able to
view the train details and cancel the booked ticket if they dont need.
1.1 PURPOSE:
The main purpose of E-Ticketing is that the travelling passenger need not go to the railway
station and book the ticket. The main advantage of the E-Ticketing is that the passenger can able
to book the ticket by using internet.
1.2. SCOPE:
The scope of the E-Ticketing is that the passengers time is saved and we can able to book the
seat which can be comfortable for us, and we can view the seats which are available when
booking.
Passenger- who can be able to login, view the train details, and cancel the tickets.
Railway database- the data which is reserved by the passenger can be included by the database.
System admin- the system admin which can manage the user and the security.
1.4. REFERENCES:
www.ticketbooking.com:
This project is a self-contained project for convenient E-TICKETING process.
The front end of the project is where the system admin or passenger do their enrollment. The
back end is managed by the railway database effectively.
Rational Rose
3. SYSTEM FEATURES
This feature allows the passenger to book the seats.
When the passenger login, the seats which are available to book can be viewed to book.
The passenger should enroll some personal details so that no cheating can be made in booking
the seats.
GANTT CHART:
USE CASE DIAGRAM:
Login
Train Details
Administrator
Passenger
<<uses>>
<<extend>>
Update Reports
Cancellation
<<uses>>
<<extend>>
<<uses>>
Seat Availability
Reservation
CLASS DIAGRAM:
Journey
board : String
start_pt : String
end_pt : String
fare : Float
seat_no : Integer
date : Date
time
Login
username : String
password : String
get_data()
verify()
display()
Train
train_no : Integer
train_name : String
start_pt : String
end_pt : String
seat_capacity : Integer
reservd_seats : Integer
unreservd_seats : Integer
get_journ_details()
print_journ_details()
get_train_details()
print_train_details()
1
User
address : String
age : Integer
sex : String
Report
reserv_ticks : Integer
unreservd_ticks : Integer
train_name : String
train_no : Integer
canceld_ticks : Integer
get_details()
generate_daily_report()
Passenger
p_name : String
p_id : Integer
tick_no : Integer
pin_no : Integer
pnr_no : Integer
get_pas_details()
print_pas_details()
Administrators
a_name : String
a_id : Integer
salary : Float
Desigantion : String
get_a_details()
print_a_details()
ACTIVITY DIAGRAM:
Enter username
and password
Validate username &

password
[ Trial >3 ]
[ Trial <3 ]
[ Valid ]
Login success
ID blocked
temporarily
LOGIN
TRAIN DETAILS
Login into the

system
Enter the source and

destination
[ unavailabe ]
[ available ]
Display requested
details
UPDATE REPORTS
Display unavailabilty
of train
Login as
administrator
Update database on completion

of each transaction
Generate daily
reports
SEAT AVAILABILITY
Login
Enter train
name or number
View seat
availability
RESERVATION:
Enter username
and password
Validate username &

password
[ Trial >3 ]
[ Trial <3 ]
[ Valid ]
Login success
ID blocked
temporarily
CANCELLATION:
User login's
Enter pnr and

pin number
Vaildate entry
Reconfirm
cancellation
[ Re-Confirmed ]
Cancel tickets
Update reports
[ Valid ]
[ Invalid ]
[ Not Re-Confirmed ]
Go to main
page
Display error
SEQUENCE DIAGRAM: RESERVATION

:passenger
:Reservation
System
:Railway
Database
enter name and password
verify
enter details
search for seat availability

if available
send information
seat available
enter credit card no.

validate
if accepted
send information
card accepted
issue ticket
store in database
SEQUENCE DIAGRAM: CANCELLATION

:Passenger
:Reservation
System
:Railway
Database
Enter name and password
Verify
Display form for cancel
Enter PNR no
search for PNR no
if available
verify details
cancel Ticket
store in database
LOGIN
4: Validation (Passenger)
12: Validation (Administrator)
2: Enter login details (Passenger)
10: Enter login details (Administrator)
USER
3: Send data for validation (Passenger)

11: Send data for validation (Administrator)
SYSTEM
DATABASE
5: Valid (Passenger)
7: Invalid (Passenger)
13: Valid (Administrator)
15: Invalid (Administrator)
6: Login success (Passenger)

8: Login Failure (Passenger)
9: Request login details (Administrator)
14: Login success (Administrator)
16: Login failure (Administrator)
TRAIN DETAILS
5: Validation
1: Login to the system

3: Enter requested data
4: Send data for validation

SYSTEM
USER
2: Request source and destination
7: Display train details
9: Display error message
DATABASE
6: Valid
8: Invalid
UPDATE REPORTS
5: updation completed
1: Login as admin
3: Select completed transactions
USER
(administrator)
4: Update selected transactions

SYSTEM
2: Display various transaction

7: Display success
9: Display error
DATABASE
6: Completed
8: Incomplete
SEAT AVAILABILITY
5: Validation
1: Login to the system
3: Enter the requested data
USER :
Passenger
4: Sends data to database

SYSTEM
2: Request train details

7: Display seat availability
DATABASE
6: Send seat availability details to system
RESERVATION
6: Available
13: Unavailable
1: Login as passenger
2: Check seat availability
4: Enter train details
9: Enter requested details
USER
(passenger)
5: Check availability
10: Update details
SYSTEM
3: Requests train& journey details

8: Requests passenger details
12: Display success message
15: Display failure message
ADMINISTRATOR
7: Tickets available
11: Tickets reserved and updated
14: Tickets unavailable
CANCELLATION
5: valid
12: invalid
1: Login as passenger
3: Enter requested details
8: Re confirms
USER
(passenger)
4: Validate
9: Cancel and update database
SYSTEM
2: Requests pnr and pin number

7: Requests reconfirmation
11: Tickets cancelled
14: Tickets not cancelled
STATE CHART DIAGRAM
DATABASE
6: Valid entry
10: Canceled
13: Invalid entry
[ Trial <3 ]
LOGIN
entry/ Login to system
[ Valid ]
VIEW
do/ View available seats
do/ View train details
[ Seat available ]
[ Trial <2 ]
BOOK TICKETS
do/ Reserve tickets if seats available
exit/ Update ticket details
[ Tickets must be already reserved ]
[ Not Re-Confirmed ]
CANCEL TICKETS
entry/ Cancel already booked tickets,if not needed
exit/ Update ticket details
[ Transaction completed ]
GENERATE REPORT
do/ Generate daily report
do/ Display reports
PACKAGE DIAGRAM:
COMPONENT VIEW
Database
Management
Ticket Updation
Train info
DEPLOYMENT VIEW
Server
(system)
PC 1
Printer 1
PC 2
Printer 2
Printer
PC n
Printer n
RESULT:
Thus the UML diagrams for e-ticketing have been developed and verified.
EXPT NO:
DATE:
BOOK BANK
PROBLEM STATEMENT:
Book Bank is used to issue books to customers which they have to return
after a specific period of time. It is necessary that the customers register at the book bank by
filling out an entry form with proper details and submit it to the manager along with the
mentioned fees. After the manager verifies the details and deposit, he/she issues the id card and a
book form.The registered customer then has to fill out the form with the names of books and the
authors and submit it back.The staff at the book bank check the availability of the books and
issue the available ones.
1. INTRODUCTION:
This project is aimed at developing a book bank system by creating details about
customers and the available books.
1.1 PURPOSE:
Manual maintenance of customer details is a tedious process considering the to the large number
of customers. Hence, this system is used for easy registration and maintenance of database.
1.2. SCOPE:
The Book Bank System is used to specify a certain procedure to the customers for quick and
hassle free registration and acquire the necessary books.
registered users.
Customer-The person who registers and obtains books from the Book bank.
Book Bank-The entire System comprising of the customers, manager, staff and other elements.
1.4. REFERENCES:
www.rec.in
This project is a self-contained project for convenient book bank registration process.
The front end of the project is where the customers register and get books. The
back end is managed by the manager effectively.
Rational Rose
3. SYSTEM FEATURES
This feature allows the customers to know the procedure to enrol l in a book bank.
When the customer details are validated he is enquired of his book preferences and the books are
issued.
REQ1: Only registered customers can apply for issue of books.
REQ2: The books need to be available in order to be issued.
Seperate and unique ids must be provided for each and every user so that no user can access the
resources available to other users.
GANTT CHART:
USE-CASE DIAGRAMS:
classdiagram
SEQUENCE-DIAGRAM:
Borrow books:
Return books:
ACTIVITY DIAGRAM:
member
faculty
Bood bank system
search books
Fill up the
application form
get member
card
Enter
return date
Issue book
Borrow books:
1: Presents Member Card and books

:Member
:Faculty of
Book Bank
6: Dispaly Due Date

7: Invalid Member Card
4: getBookDetails(bookid)
2: Enter member Details
3: Enter Book Details
5: Update Transaction
:System
:Book
Catalog
Update
transaction
Return books:
1: Return Books
6: Pay fine
:Faculty of
Book Bank
:Member
7: Return Member Card
5: Dispaly fine amount

2: Enter Book Details
3: Check return date

4: Check Fine Status
8: Update Transaction
:System
STATE CHART DIAGRAM:

Borrow books:
:Book
Catalog
Return books:
PACKAGE DIAGRAM:
DEPLOYMENT DIAGRAM:
COMPONENT DIAGRAM:
RESULT:
Thus the UML diagrams for Book Bank was developed and verified.
EXPT NO:
Passport Automation System
DATE:
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. 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. 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. The system also provides the applicant
the list of available dates for appointment to 'document verification' in the administrator's office,
from which they can select one. The system forwards the necessary details to the police for its
separate verification whose report is then presented to the administrator. The administrator will
be provided with an option to display the current status of application to the applicant, which
they can view in their online interface. After all the necessary criteria has been met, the original
information is added to the database and the passport is sent to the applicant.
Software Resource Specification

1.0 Introduction
Passport Automation System is an interface between the Applicant and the Authority
responsible for the Issue of Passport. It aims at improving the efficiency in the Issue of Passport
and reduce the complexities involved in it to the maximum possible extent.
1.1 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.
1.2 Scope
The System provides an online interface to the user where they can fill in their
personal details and submit the necessary documents (may be by scanning).
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 Local Police for
verification of applicant's information.
Users/Applicants will come to know their status of application and the date in
which they must subject themselves for manual document verification.
2.0 Overall Description

2.1 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.
2.4 System Functions
Secure Registration of information by the Applicants.
Schedule the applicants an appointment for manual verification of original
documents.
Panel for Passport Application Status Display by the Administrator.
SMS and Mail updates to the applicants by the administrator.
Administrator can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.
2.5 User Characteristics
Applicant - They are the people who desires to obtain the passport and submit
the information to the database.

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 dispatch of passport.
Police - He is the person who upon receiving intimation from the PAS, perform a
personal verification of the applicant and see if he has any criminal case against him
before or at present. He has been vetoed with the power to decline an application by
suggesting it to the Administrator if he finds any discrepancy with the applicant. He
communicates via this PAS.
2.6 Constraints
The applicants require a computer to submit their information.
Although the security is given high importance, there is always a chance of
intrusion in the web world which requires constant monitoring.
The user has to be careful while submitting the information. Much care is required.
2.7 Use Case Model Description
2.8 Assumptions and Dependencies
The Applicants and Administrator must have basic knowledge of computers and
English Language.
The applicants may be required to scan the documents and send.
GANTT CHART:
USE CASE DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM: ADMIN
SEQUENCE DIAGRAM:CHECK STATUS
SEQUENCE DIAGRAM : REGISTER
ACTIVITY DIAGRAM :ADMIN
ACTIVITY DIAGRAM: REGISTER
ACTIVITY DIAGRAM: CHECK STATUS
COLLABORATION DIAGRAM:ADMIN PANEL
COLLABORATION DIAGRAM: APPLICATION
COLLABORATION DIAGRAM: CHECK STATUS
PACKAGE DIAGRAM:
STATECHART: ADMIN PANEL
STATECHART: CHECK STATUS
STATE
CHART:
REGISTER
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
RESULT:
Thus the UML diagrams for Passport Automation System was developed and
verified.
EXPT NO:
DATE:
Exam Registration
PROBLEM STATEMENT
The exam registration system allows the students to register for their exams. The administration
of the university also can get the list of registered students with all their information. Once the
student registers he/she receives an id, which helps him in further correspondence. A fees amount
is received from the students for registration. This system makes the task of the students easier
rather than waiting in queue for enrollment. This also reduces the time consumption for both for
the students and administration.
1. INTRODUCTION:
This project aimed at developing a web-based exam registration system by storing application
data and relevant information about the registered students.
1.1 PURPOSE:
Registering for examinations is a tedious process for both the adminstration as well as the
students. This system is specially designed to reduce the difficulty of students in registering for
their examination.
1.2. SCOPE:
This system helps the both the adminstration and the students to finish their work with more
ease.
registered students.
Students - the person who registers in the system in search of jobs..
1.4. REFERENCES:
www.gre.org
This project is a self-contained project for convenient exam registration.
The front end of the project is where the students do their enrollment. The
Rational Rose Enterprise Edition
3. SYSTEM FEATURES
3.1 REGISTERING FOR EXAMINATION:
REQ1: Only registered users can register for examination.
REQ2: The administrator has the right to recruit the candidates, not the system.
GANTT CHART:
USECASE DIAGRAM:
CLASS DIAGRAM
SEQUENCE DIAGARAM:
PACKAGE DIAGRAM:
ACTIVITY DIAGRAM:
ACTIVITY DIAGRAM:
STATECHART:
STATECHART:
COMPONENT DIAGRAM:
DEPLOYMENT DIAGRAM:
RESULT:
Thus the use case diagrams for Exam Registration was developed and
verified.
EX-NO:
ONLINE COURSE REGISTRATION SYSTEM
DATE :
PROBLEM STATEMENT:
All the processes involved in the course registration system are

computerized.
It must contain all the details about: Student, Course offerings, Registering a course,
Availability of courses, Eligibility for Admission. This registration system enables the
admission of candidates into the institution on the basis of their educational and
social background.. The candidate has to register their desired branch from the
available courses. The registration must include the following details:
Application No, Student information, Course selected, course Availability, Eligibility.
If a student wishes to change his/ her course, then the schedule is
updated. If course is available then the change of course is permitted and changed,
else include it in waiting list. To update a schedule, the student needs to be logged
in. Then the student can select any other course from the available list of courses.
And the schedule is submitted.
If a student wishes to cancel his/her course, the students current schedule
is retrieved and displayed first. Then the system prompts the user to confirm the
deletion of schedule. If confirmed, the student is removed from the course offerings.
1. INTRODUCTION:
This project is aimed at developing a Course Registration system by creating details
about
customers and the available courses.
1.1 PURPOSE:
Manual maintenance of customer details is a tedious process considering the to the
large number of customers. Hence, this system is used for easy registration and
maintenance of database.
1.2. SCOPE:
The Course Registration is used to specify a certain procedure to the customers for
quick and hassle free registration of courses.

registered users.
Customer-The person who registers and gets registered.
1.4. REFERENCES:
www.google.com
This project is a self-contained project for convenient online course registration
process.
The front end of the project is where the customers register and online courses. The
back end is managed by the manager effectively.
Rational Rose
3. SYSTEM FEATURES
This feature allows the customers to know the procedure to find the courses.
When the customer details are validated he is enquired of his course preferences
and the details about the courses are issued.
REQ1: Only registered customers can apply for details of the courses.
REQ2: The courses need to be available in order to be issued.
4. OTHER NON-FUNCTIONAL REQUIREMENTS:

To increase the performance and free up database resources, the default features
are written
Seperate and unique ids must be provided for each and every user so that no user
can access the resources available to other users.
4.4 SYSTEM REQUIREMENTS
Processor : Pentium IV 1.7
RAM : 128 MB
Hard Disk : 40 GB
4.5 SOFTWARE REQUIREMENTS
case tool : rational rose
GANTT CHART:
UMLDIAGRAMS
USECASE DIAGRAM:
View courses
<<Actor>>
REGISTRATION DATABASE
STUDENT
Register course
includes
extends
Check course availability
Free registration
Cancel course
SYSTEM ADMIN
Update course
Check eligibility
CLASS DIAGRAM:
ACTIVITY DIAGRAM:
Change course
<<Actor>>
COURSE
CATALOG
STUDENT
REGISTRATION SYSTEM
Complete
application
application
Check course
availability
else
if available
<<datastore>>
courses
<<datastore>>
applications
Choose
alternate course
accept/deny
SEQUENCE DIAGRAM:
Check applicant
qualification
<<datastore>>
students
student
central management
system
university
1. browse course
2.select course
3.check availability
4.available
5.register
6.submit details
7.verify details
8.issue approval
9.pay fee
10.enroll
1: browse course 2: select course

student
5: register
6: submit details
9: pay fees
universit
y
10: enroll
3: check availability
7: verity details
8: issue approval
4: availability
cetral
management
STATECHART
DIAGRAM:
PACKAGE DIAGRAM:
User Interface
Domain
Forms
Report
Course
Student
Technical Services
Database
Logging
DEPLOYMENT DIAGRAM:
Registration
College
student
universit
y
central
man...
COMPONENT DIAGRAM:
univers
ity
student
central
management
RESULT:Thus the domain model with UML diagrams for the Course Registration System have
been developed and verified.
EXPT NO:
RECRUITMENT SYSTEM
DATE:
PROBLEM STATEMENT:
The recruitment system allows the job seekers to enroll their names through the process
of registration. The employee also can get the list of available candidates and shortlist for their
company requirement. Once the applicant enrolls he receives an id, which helps him in further
correspondence. A fees amount is received from the job seekers for enrollment. This system
makes the task of the job seeker easier rather than waiting in queue for enrollment. This also
reduces the time consumption for both for the job seeker and employee.
1. INTRODUCTION:
This project aimed at developing a web-based recruitment system by creating details about
vacancies, storing application data and interview process initiation.
1.1 PURPOSE:
Manual recruitment is a tedious processing to the increasing number of job seekers.
People around the world can apply for the online recruitment system and it is very convenient
too. This system is specially designed for those seek the most demanding job and challenging
positions in their own field.
1.2. SCOPE:
Recruitment system allows the job seekers to find their dream job in the chosen field.
This system helps the companies to recruit the right candidate for the job. This system serves as a
common meeting ground for job seekers and employees, both locally and globally.
registered users.
Job Seekers - the person who registers in the system in search of jobs.
Company - A company can register itself, select the required employees and provide
information about the result.
1.4. REFERENCES:
www.timesjob.com:
This project is a self-contained project for convenient recruitment process.
The front end of the project is where the visitors or job seekers do their enrollment. The
Rational Rose
3. SYSTEM FEATURES
When the job seeker uploads his resume, the list of jobs matching the resume will be
posted.
REQ1: Only registered users can apply for the job.
REQ2: The Company has the right to recruit the candidates, not the system.
GANTT CHART:
USE CASE
DIAGRAM
CLASS DIAGRAM
SEQUENCE DIAGRAM: REGISTER
SEQUENCE DIAGRAM: STATUS
SEQUENCE DIAGRAM:ADMIN PANEL
ACTIVITY DIAGRAM:
REGISTER:
ACTIVITY DIAGRAM: CHECK STATUS
ACTIVITY
DIAGRAM:
HR
ENTRY
STATUS
COLLOBORATION DIAGRAM: REGISTER
COLLOBORATION DIAGRAM: STATUS
COLLOBORATION DIAGRAM : ADMIN PANEL
PACKAGE DIAGRAM:
DEPLOYMENT DIAGRAM:
COMPONENT DIAGRAM:
RESULT:
Thus the UML diagrams for Recruitment system was developed and verified.
EXPT NO:
SOFTWARE PERSONNEL MANAGEMENT
SYSTEM
DATE:
PROBLEM STATEMENT:
A SOFTWARE PERSONNEL MANAGEMENT SYSTEM refers to the systems and
processes at the intersection between human resource management (HRM) and
information technology. It merges HRM as a discipline and in particular its basic HR
activities and processes with the information technology field, whereas the
programming of data processing systems evolved into standardized routines and
packages of enterprise resource planning (ERP) software. The linkage of its financial
and human resource modules through one database is the most important
distinction to the individually and proprietary developed predecessors, which makes
this software application both rigid and flexible.
1. INTRODUCTION:
This project which aims to efficiently manage the personnel details of a software
company which includes payroll details and other important functions.
1.1 PURPOSE:
The HR function consists of tracking existing employee data which traditionally
includes personal histories, skills, capabilities, accomplishments and salary. Also,
each employee can access his/her own profile, that lets him view his salary,
attendance and company related updates.
1.2. SCOPE:
The scope of the Software Personnel Management System is that it allows the HR to
view the entire employee Database conveniently and make updates. Similarly from
an employee point of view, he/she can be able to view company related information
easily.

Employees can view their personal details and other company information. They
can send messages to any other employee of the organization. The HR has more
features. He can view entire employee database, make payroll updates etc.
1.4. REFERENCES:
www.infosys.com
This project is a self-contained project for convenient Software Personnel

Management System.

The front end of the project is where the HR or employee can login. The
back end is managed by the organization database effectively.

Rational Rose Enterprise Edition, Argo UML
3. SYSTEM FEATURES
3.1 SYSTEM DESCRIPTION AND PRIORITY:

This feature allows the employee to view his profile.
3.2 STIMULUS AND RESPONSE SEQUENCE:

When the employee logs in, his or her personal details are displayed.

To increase the performance and free up database resources, the default features
are written

The employee is given a user id and password to ensure safety of personal
information.
GANTT CHART:
UML USE-CASE DIAGRAM
Recruit
Training
HR
Salary
Commitment
Bank Accounts
Regularity
Curriculum Vitae
Monitor Employees
Provide salary increment
Motivate
Recruit()
Monitor()
Increment()
Motivation()
Employee
Monitor
Performance
Increment
Time Management
Motivation
Training()
Salary()
Performance()
UML CLASS DIAGRAM
HR
Curriculum Vitae
Monitor Employees
Provide salary increment
Motivate
Recruit()
Monitor()
Increment()
Motivation()
Employee
Commitment
Bank Accounts
Regularity
Training()
Salary()
Performance()
Training Deatils
Salary Details
Provide educated trainees
create bank Account to deposit salary
Training()
salary()
time mgment
time period observed according to training details
time management()
UML SEQUENCE DIAGRAM
Employee
HR
Training details
Update Salary Details
View Salary Details

Training Information
Training Update
Performance
Training Period
Salary Increment
Salary Details
UML ACTIVITY DIAGRAM
HR Login
Employee
Name
Performance
&Attendence
Fixed Salary
Salary
Increment
HR Logout
UML COLLABORATION DIAGRAM
5: Performance
3: Training Information
Employee : <Actor
Name>
HR : <Actor Name>
2: View Salary Details
1: Update Salary Details
6: Training Period
Training
details
4: Training Update
7: Salary Increment
Salary
Details
STATECHART:
Provide
Increment
Login
Enter Employee
Name
Check Performance
and Attendence
Logout
Donot Provide
Increment
PACKAGE DIAGRAM:
UML COMPONENT DIAGRAM
Human Resources
involves
recruitment,motivation
, monitoring of
employees
HR
Provides
Employee and HR
with the salary
details
Salaray
Details
provides
employees with
training details
which is updated
by HR
Training
Details
Employee
employees are those

who are recurtited by
HR and work for the
respective company
UML DEPLOYMENT DIAGRAM
HR
provides
employee with
salary details
HR recurits the
employee for a given
company
Training Period is
given to the
employee with
training period
Training
Deatails
Salary Details
Employee
Employee recurited
by HR Undergoes
training before
actually working
RESULT:
Thus the UML diagrams for Software Personnel Management System was developed
and verified.
EXPT NO:
STOCK MAINTENANCE SYSTEM
DATE:
PROBLEM STATEMENT
The Stock maintenance system which allows the administrator to display the product
details, purchase details, sales details, stock details, and the purchase the products. The customer
which is used to purchase the product. The supplier who use to supply the product. Once they
enter the login details the verifier check the details of availability and says whether the login is
valid or not. Then enter the stock details, maintain and store it.
1. INTRODUCTION:
This project aimed at developing a web-based stock maintenance system by creating details
about product, purchase, sales and stock details.
1.1 PURPOSE:
This stock maintenance system which is used to say exactly how much product is in the stock
and how much product is got saled. This also helps that how to purchase the product and how to
supply the product.
1.2. SCOPE:
The stock maintaining system which implements that how to supply and get increament in the
sales. Before getting the demand of the particular product it is getting stocked so that in the
demand period we can easily attain that product.
registered users.
Customer- The person who is going to purchase the product.
Supplier- The person who is going to supply the product.
1.4. REFERENCES:
www.stock maintain.com:
This project is a self-contained project for convenient stock maintenance system process.
The front end of the project is where the customers or suppliers do their enrollment. The
back end is managed by the administrator effectively.

Rational Rose
3. SYSTEM FEATURES
This feature allows the customer to purchase the product.
When the administrator confirm the details of the stock, they will supply to the market. So the
supplier and the customer can get the advantage of the product.
REQ1: Only the administrator can be able to refer the stock details.
To increase the performance of the stock, the supplier should have the quality products.
The stock should be maintained carefully without any damage.
GANTT CHART:
USECASE DIAGRAM:
Order Cancellation
Customer
Placing Order Quotation

<<include>>
Sales Manager
Stock Level Checking
Maintain Product Details

<<Actor>>
Manufacturer
Maintain Purchase Details
<<Actor>>
Shipper
Purchase the Product
Return Item
Billing Process
<<Actor>>
Bank Account
CLASS DIAGRAM:
SEQUENCE DIAGRAM:
SEQUENCE DIAGRAM:
ACTIVITY DIAGRAM:
LOGIN
ANALYSIS
STOCK
NEEDED
LIST
PREPARATION
OLD
STOCK
EXPIRED
STOCK
QUOTATION
SELL
PURCHASE AND
PAYMENT
UPDATE
customer
stock manager
stock maintenance system
stock
view catalog
place order to
stock manager
Enter id
Ask for
password
Enter password
valid
invalid
check for stock availability
no
preorder
Alert for stock

availability
yes
link details
issue bill
paybill
update details
of stock
Deliver item
pack item
STATE CHART DIAGRAM:
OLD
STOCK
SELL
LOGIN
ANALYSIS
STOCK
NEEDED
LIST
PREPARATION
QUOTATION
PURCHASE AND
PAYMENT
UPDATE
EXPIRED
STOCK
4: GIVE QUOTATION
6: DELIVERY OF GOODS
STOCK MANAGER
CUSTOMER
3: ORDER FOR GOODS
5: PAYMENT
7: ORDER FOR GOODS NEEDED AND PAY FOR IT
2: APPROVE THE LOGIN

9: UPDATATION OF GOODS DETAILS
8: DELIVERY OF PRODUCTS
ADMINISTRAT
OR
1: LOGIN
COMPAN
Y
PACKAGE DIAGRAM:
UML COMPONENT DIAGRAM:
SMS Techn
ical services
SMS
Domain
UML DEPLOYMENT DIAGRAM:
Keyboar
d
Mouse
Node 1:
Sto...
Monitor
Printer
SMS UI
RESULT:
Thus the UML diagrams for Stock Maintenance System was developed and verified.

Ooad Lab Manual 1

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ooad Lab Manual 1

Загружено:

Авторское право:

Доступные форматы

EXPT NO:

CREDIT CARD PROCESSING

2.3 TOOLS TO BE USED

STATE CHART DIAGRAM: (PAYMENT)

REQ1: Only registered users can search and download.

use case diagram

USE CASE DIAGRAM:

Validate username &

Login into the

Enter the source and

Update database on completion

Validate username &

Enter pnr and

SEQUENCE DIAGRAM: RESERVATION

enter name and password

search for seat availability

enter credit card no.

SEQUENCE DIAGRAM: CANCELLATION

Enter name and password

Display form for cancel

search for PNR no

3: Send data for validation (Passenger)

6: Login success (Passenger)

1: Login to the system

4: Send data for validation

4: Update selected transactions

2: Display various transaction

4: Sends data to database

2: Request train details

6: Send seat availability details to system

3: Requests train& journey details

2: Requests pnr and pin number

STATE CHART DIAGRAM

[ Tickets must be already reserved ]

Bood bank system

1: Presents Member Card and books

6: Dispaly Due Date

5: Dispaly fine amount

3: Check return date

STATE CHART DIAGRAM:

Passport Automation System

Software Resource Specification

2.0 Overall Description

the information to the database.

USE CASE DIAGRAM

SEQUENCE DIAGRAM: ADMIN

SEQUENCE DIAGRAM:CHECK STATUS

SEQUENCE DIAGRAM : REGISTER

ACTIVITY DIAGRAM :ADMIN

ACTIVITY DIAGRAM: REGISTER

ACTIVITY DIAGRAM: CHECK STATUS

COLLABORATION DIAGRAM:ADMIN PANEL

COLLABORATION DIAGRAM: APPLICATION

COLLABORATION DIAGRAM: CHECK STATUS

STATECHART: ADMIN PANEL

STATECHART: CHECK STATUS

ONLINE COURSE REGISTRATION SYSTEM

All the processes involved in the course registration system are

1.3. DOCUMENT CONVENTIONS:

Customer-The person who registers and gets registered.

4. OTHER NON-FUNCTIONAL REQUIREMENTS:

4.1 PERFORMANCE MANAGEMENT:

Check course availability