Cs6511 Case Tools Lab Record-1

INDEX
PAGE
S.NO. DATE NAME OF THE EXPERIMENT MARKS SIGNATURE
NO.
1 PASSPORT AUTOMATION SYSTEM 5
2 BOOK BANK MANAGEMENT SYSTEM 15
3 EXAM REGISTRATION SYSTEM 33
4 ONLINE COURSE RESERVATION SYSTEM 49
5 STOCK MAINTENANCE SYSTEM 65
6 ONLINE RECRUITMENT SYSTEM 82
7 E-TICKETING 99
SOFTWARE PERSONNEL MANAGEMENT

8 106
SYSTEM
9 CREDIT CARD PROCESSING 114
10 E-BOOK MANAGEMENT SYSTEM 120
11 FOREIGN TRADING SYSTEM 127
12 CONFERENCE MANAGEMENT SYSTEM 134
13 STUDY OF UML 140

EX NO: 1 PASSPORT AUTOMATION SYSTEM
DATE:
AIM
To develop the Passport Automation System using rational rose/ Argo UML tools and
implements it using Java
PROBLEM ANALYSIS AND PROJECT PLAN
To simplify the process of applying passport, software has been created by designing
through rational rose/ Argo UML tool, using java. 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 is verified 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.
SOFTWARE REQUIREMENTS 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 reduces 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
2
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. 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.
1.3 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 any higher 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.
1.4 REFERENCES: IEEE Software Requirement Specification format.
1.5 TOOLS TO BE USED: Rational rose/ Argo UML tool (for developing UML Patterns)
1.6 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.
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.2 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 database.
3
2.3 USER CHARACTERISTICS
1. Applicant - They are the people who desire 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 dispatch of passport.
3. 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.4 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.
2.5 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
USE CASE DIAGRAM
DOCUMENTATION OF USECASE DIAGRAM
 The actors in use case diagram are Applicant, regional administrator, database, passport
Administrator, Police.
 The use cases are Login, givedetails, logout, collectdetails, verification, issue.
 The actors use the use case are denoted by the arrow
 The login use case checks the username and password for applicant, regional
administrator, passport administrator and police.
 The submit details use case is used by the applicant for submitting his details
 The check status use case is used by the applicant for checking the status of the
application process.
 The get details, verify and store verification use case is used by passport administrator,
regional administrator, and police.
 The details use case is used for getting the details form the database for verification
The verify use case is used for verifying the details by comparing the data in the database.
4
get application
fill application
submit application
applicant
verify application
send police verification
get more information

police officer
send report to passport officer

passport office
passport approval
send passport to applicant
get passport
5
CLASSDIAGRAM
DOCUMENTATION OF CLASS DIAGRAM
a. APPLICANT-The applicant has attribute such as name and password and

operations are login, givedetails 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 get 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 get the details form database and verify with their database , update
the verification and issue the passport
e. THE POLICE-The police has 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
6
SEQUENCE DIAGRAM
:applicant :verification :personal :passport

officer verifier officer
submit application
acknowledgement
send verification
submit report
required more information
provide details
send for approval
submit passport to applicant
DOCUMENTATION OF SEQUENCE DIAGRAM.
a. The applicant login the database and give his details and database store the
details.
b. The passport administrator get the details from the database and do verification
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
7
COLLOBORATION DIAGRAM
1: submit application
6: provide details
:applicant :verification
officer
2: acknowledgement
5: required more information
4: submit report
8: submit passport to applicant 7: send for approval
3: send verification
:personal :passport
verifier officer
STATE CHART DIAGRAM
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 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
state.
ACTIVITY 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 operation.
8
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
9
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
DEVICE NODE
A physical computing resource with processing and memory service to execute software,
such as a typical computer or a mobile phone.
EXECUTION ENVIRONMENT NODE
This is a software computing resource that runs within an outer node and which itself provides a
service to host and 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).
10
DOCUMENTATION OF PACKAGE DIAGRAM
The three layer in the passport automation system are user interface layer, domain layer, and
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.
RESULT:
Thus the project to develop passport automation system was developed using rational rose/ Argo
UML Software and to implement the software in java is done successfully.
11
EX NO: 2 BOOK BANK MANAGEMENT SYSTEM
DATE:
AIM
To develop the Book Bank Management System using rational rose/ Argo UML tools
and implements it using Java.
The book bank management system is a software in which a member can register
themselves and then he can borrow books from the book bank. It mainly concentrates on
providing books for engineering students.
PROBLEM STATEMENT
The process of members registering and purchasing books from the book bank are described
sequentially through following steps:
a. First the member registers himself if he was new to the book bank.
b. Old members will directly select old member button.
c. They select their corresponding year.
d. After selecting the year they fill the necessary details and select the book and he
will be directed towards administrator
e. The administrator will verify the status and issue the book.
INTRODUCTION
Software Requirement Specification for Book Bank Management System. The Book
Bank Management System contains user details such as name, user-id, password, contact
number, mail-id, and address.
PURPOSE
The staff and student can register their details and it is automatically stored. Purpose is to
lend book for engineering students and staff for a particular period of time through online. It is to
explain system process, constraints and interfaces.
12
SCOPE
This software will be a book lending system for users. This system will be designed to
calculate the number of books taken by the users. Each member is provided with a unique user-id
at the time of registering as member.
DEFINITIONS
Term Definition
User Student and staff.
Database Collection of all the information monitored
by this system.
Administrator The person who maintain all user details.
Software Requirement Specification A document that completely describes all of
the function of a proposed system.
OVERALL DESCRIPTION
This application consists of signup page for the new user and login page for permanent
user who can get details of books.
PRODUCT PERSPECTIVE
This project is a self-contained one for enabling a book bank organization to be
connected with user through this system. They can check for availability of books, details of
lending books, due date and fine. Requirement Specification Section of this document is written
for the developers.
PRODUCT FUNCTION
This system functions for keeping track of its members and available resources.
Search() Register()
Save() Login()
Delete() Validate()
View() Verify()
Add() Update().
USER CHARACTERISTICS
 The user must know how to enter the details.

 The user must know how to use the Book Bank Management System.
 The user must know to enter the details.
 The administrator must know how to maintain the details of books.
13
GENERAL CONSTRAINTS
This user will enter the valid user-id and password.
USER INTERFACES
This is the interface that the user interacts with the system. Here coding act as a user
interface. The system must contain rational rose/ Argo UML software for generating UML
diagrams. This can be used in any operating system.
HARDWARE INTERFACES
 System
 A good processor
 128mb RAM.
SOFTWARE INTERFACES
 Rational rose/ Argo UML.
OPERATION
The Book Bank Management System has two active actors. They are user and
administrator. The user will be able to enter his/her details only. The administrator will access
the entire system.
SOFTWARE PRODUCT FEATURES

This software contains the features like adding a new user, maintaining book details,
calculating due date and fine.
UML DIAGRAMS
USE CASE DIAGRAM

Student, staff and other users makes the registration then logins and searches for books
and gets the book. The administrator and database maintains user details, book details and
manages the books and also administrator lends books.
14
registration view
view book avalability create
admin
user edit
view student classification
register
payment
diamond
process payment
platinum
exit
ACTIVITY 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
15
user administrator database
register
enter details check if the

details are valid
re-enter valid
details
login using user generate user maintain the

id& password id & password user details
enter the book search for

details availability for books
lend books
get books
display book is not

available

The user does registration by entering details. Administrator’s work is to check if details
are valid. If valid then database maintains user details and admin generates userID and password
for user. Then the user logins and enters the book details if they are in need of book else they just
view their details. Database searches for the book asked by user. If book is available the
administrators lend books to user.
16
CLASS DIAGRAM
A class is drawn as rectangle box with three compartments or components separated by
horizontal lines. The top compartment holds the class name and compartment holds list of
operations. Middle compartment holds the attribute and functions.
17
SEQUENCE INTERACTION 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.
:login :register :book :diamond type :platinum type

availability
login
view availability
select dbook
pay money
issue dbook
pay money
issue pbook
logout
DOCUMENTATION OF SEQUENCE INTERACTION DIAGRAM

The user registers by entering details. The details is checked by administrator and it is
stored in database. Administrator generates userID and password then the user logins and enters
book details. The availability of book is checked by database and if the book is available it is
lend to the user by administrator.
18
COLLABORATION DIAGRAM
STATE CHART DIAGRAM
Register Enter Check If detail

details are valid
Generate userID & Maintain the

password user details
Search for Enter the Login using userID

availability of books book details & password
Lend Get books

books
19
PACKAGE DIAGRAM
<<layer>>
UI
login customer admin Books
<<layer>>
Domain
user details admin details book details
<<layer>>
Technical Service
DB Server Web browser

The UI layer contains main classes like login, customer, admin and books. Domain layer
contains the details of customer, administrator and book. The Technical service layer contains
supportive software’s such as database, server and web browser.
20
COMPONENT DIAGRAM
student
administrator
staff other
books users
database
membership
status

Book details are managed by admin and DB so it depends on administrator and database.
The users like student, staff and other users depend on books. Membership status is managed by
database so it depends on the database.
DEPLOYMENT DIAGRAM
DEVICE NODE
This is a software computing resource that runs within an outer node and which itself
provides a service to host and execute other executable software element.
Server
user login
admin books
21
The main node is server. The other nodes such as admin, user, books and login depends
on the server so it is represented by the dependency line.
SAMPLE IMPLEMENTATION CODE

ADMIN:
//Source file: Z:\\OOAD\\admins.java
public class admins
{
private String aname;
private Integer aID;
public staff theStaff[];
public student theStudent[];
public book theBook[];
publicmembershipstatustheMembershipstatus;
publicotheruserstheOtherusers[];
/**
* @roseuid 533278510036
*/
public admins()
{
/**
* @return java.lang.String
* @roseuid 533277670389
*/
public String averify()
{
return null;
}
/**
* @return java.lang.Integer
* @roseuid 533277790086
*/
public Integer aadd()
{
22
return null;
}
/**
* @roseuid 53327785007E
*/
public Integer adelete()
{
return null;
}
}
STUDENT
//Source file: Z:\\OOAD\\student.java
public class student
{
private String names;
private String ID1;
private Integer contactnum;
/**
* @roseuid 533275C00096
*/
public student()
{
/**
* @roseuid 532BFAC900B1
*/
public String view()
{
return null;
}
23
/**
* @roseuid 532BFAD00176
*/
public String login()
{
return null;
}
/**
* @roseuid 532BFAD700E3
*/
public String search()
{
return null;
}
/**
* @roseuid 532BFCAF03AE
*/
public String register()
{
return null;
}
}
STAFF
//Source file: Z:\\OOAD\\staff.java
public class staff
{
private String name1;
private String mailID;
private Integer contactno;
/**
* @roseuid 533275AC002F
*/
24
public staff()
{
/**
* @roseuid 532BFAE5001B
*/
public String view1()
{
return null;
}
/**
* @roseuid 532BFAE90215
*/
public String login1()
{
return null;
}
/**
* @roseuid 532BFAEE019F
*/
public String search1()
{
return null;
}
/**
* @roseuid 532BFCBB02F2
*/
public String register1()
{
return null;
}
25
}
OTHER USERS
//Source file: Z:\\OOAD\\otherusers.java
public class otherusers
{
private String mailID2;
private Integer contactno2;
/**
* @roseuid 533275D00210
*/
publicotherusers()
{
/**
* @roseuid 532BFAFF0158
*/
public String view2()
{
return null;
}
/**
* @roseuid 532BFB0401AD
*/
public String login2()
{
return null;
}
/**
* @roseuid 532BFB0903B8
26
*/
public String search2()
{
return null;
}
/**
* @roseuid 532BFCC70060
*/
public String register2()
{
return null;
}
}
BOOK
//Source file: Z:\\OOAD\\book.java
public class book
{
private String bookname;
private String authors;
private String publication;
/**
* @roseuid 533274F401CC
*/
public book()
{
/**
* @roseuid 532BFB160271
*/
public String namee()
{
return null;
}
27
/**
* @roseuid 53325C4C0240
*/
public String publication()
{
return null;
}
}
DATABASE
//Source file: Z:\\OOAD\\database.java
public class database
{
private Integer storagespace;
publicmembershipstatustheMembershipstatus[];
/**
* @roseuid 533275DF00F6
*/
public database()
{
}
/**
* @roseuid 532BFB2D02EE
*/
public String validate()
{
return null;
}
/**
* @roseuid 532BFB3601E0
*/
* @roseuid 532BFB3B0041
28
*/
public Integer delete1()
{
return null;
}
}
MEMBERSHIP STATUS
//Source file: Z:\\OOAD\\membershipstatus.java
public class membershipstatus
{
private Integer booksholding;
private Integer duedate;
private Integer fine;
/**
* @roseuid 533275F6000B
*/
publicmembershipstatus()
{
}
/**
* @roseuid 532BFB4F0194
*/
public Integer add2()
{
return null;
}
/**
* @roseuid 532BFB52033F
*/
public Integer delete2()
{
return null;
}
/**
* @roseuid 5332595100F9
29
*/
public String update()
{
return null;
}
}
RESULT
Thus the Book Bank Management System project was developed using Rational rose/
Argo UML Software and implemented successfully using Java.
30
EX NO: 3 EXAM REGISTRATION SYSTEM
DATE:
AIM
To develop the Exam Registration System using rational rose/ Argo UML tools and
implements it using Java.
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 fraudulent or
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.
c. They complete the payment process.
d. The authorities verify or check the details.
e. After all verification the exam registration database is finalized.
SOFTWARE REQUIREMENTS SPECIFICATION:

INTRODUCTION
It is automation software, it contains the details of an applicant such as name, age,

gender, educational details, course , payment details are stored in the database and the authority
verify those details for providing hall ticket.
31
PURPOSE
The purpose of this document is to present a detailed description of the Exam registration
system. It will explain the purpose and features of the system, the interfaces of the system, what
the system will do, the constraints under which it must operate and how the system will react to
external stimuli. This document is intended for both the applicant and the authority of the
system.
SCOPE
This system will be designed to verify the applicant details according to the constraints
and provide hall ticket for the eligible candidate. It will be easily understand by all. This system
can be used in large industries and also in small industries.
DEFINITIONS AND ABBREVATIONS
Term Definition
Applicant The person who enter the details for a

particular firm.
Administrator The person who maintains all applicant detail.
Database Collection of all the information monitored by

this system.
Field A cell within a form.
Software Requirements Specification A document that completely describes all of

the functions of a proposed system and the
constraints under which it must operate. For
example, this document.
User candidate
OVERALL DESCRIPTION
It consists of three modules. In the first module the applicant fill the application form and
payment is made based on the course. In second module the authority verify the details and in
third module hall ticket is provided for the eligible candidate.
PRODUCT FUNCTIONS
 Search()
32
 Save()
 Delete()
 View()
 Add()
 The candidate must know how to enter details.

 The candidate must know how to use this system.
 The candidate must able to enter his/her necessary details.
 The candidate should have bank account for the payment.
 The authorities should know the constrain for providing hallticket.
SOFTWARE INTERFACES
 Rational rose/ Argo UML .
OPERATION
The Exam Registration system has two active actors. They are the applicant and
administrator. The applicant should able to fill the form and payment process. The administrator
will access the entire system and provide hall ticket for the eligible candidate.
UML DIAGRAMS
USE CASE DIAGRAM
User,Admin and the Computer system are the actors in Usecase digram.The various use
cases are login,user details, verify details,receive hallticket,generate hallticket.The user makes
the login into the system. Then the user enters details for hallticket.The verification of the user
details is done by the Administrator.Once the verification is completed , the user hallticket is
generated. If the details entered is not valid,then the hallticket will not be generated.The user has
to check and correct the entered details again. The computer system is responsible for generating
the hallticket.Admin decide either the hallticket to be issued or cancel
33
register
enter details
student
check the details
<<include>>
data base
check constrains
administrator
payment
generate hallticket
store the details
issue hallticket
get hall ticket
ACTIVITY 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
34
student administrrator bank
enter into
application form
fill the details check the

details
details verified
make payment
(else) authorization of
card
(cash) check the

amount
generate hall
ticket
get the hall

ticket isssue hall
ticket

All the actions in this system are represented as activities here, in this diagram.The user
makes the login into the system.The user makes the login1 into the system. Then he/she enters
the details.The verification of the user provided details is done by the class admin. During
verification, if the admin indicates wrong information, the user has to correct the details.Once the
verification is completed , the user is allowed to receive the hallticket.User,Admin and the
Computer system are the actors in this system.
35
CLASS DIAGRAM

36
student administrator bank
enter details
check details
make payment
authorize card
accepted
issue hall ticket
get the hall ticket
7: get the hall ticket
1: enter details
3: make payment
student administ
rator
2: check details
6: issue hall ticket
5: accepted
4: authorize card
bank
DOCUMENTATION OF COLLABORATION DIAGRAM

The various actions taking place in the exam registration system are represented
one-by-one in this diagram.The user makes the login into the system.Admin validates the
username and password entered by the user.Then the user enters the details.The details are stored
in the database for retreival.The entered details are validated by admin.If the details entered are
correct then the hallticket is generated by admin.admin issues the hallticket,where the user
receives.
37
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.
enter into fill details check

app form detail
make the
paymen
generate check for authorizati

hallticket amount on card
issue get
hallticket hallticket

This diagram represents operations in the Exam registrationsystem in a step-by- step manner.
The user makes the login into the system.Admin validates the username and password entered by
the user.Then the user enters the details.The details are stored in the database for retreival.The
entered details are validated by admin.If the details entered are correct then the hallticket is
generated by admin,admin issues the hallticket,where the user receives..Statechart diagram has
only an end state. It has no starting state.The state of an object depends on its current activity or
condition.
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
38
o Domain layer
o Technical services layer
<<layer>>
UI
(from NewPackage)
jframe web exam-registarati
on
<<layer>>
domain
enterdetail verify generate issue
<<layer>>
technicalsupport
browser servers database
COMPONENT DIAGRAM
student1 admin
hall
ticket
details
personal
payment
details
39
Component diagram consists of several components. The components are linked with the help of
dependency. . The user makes the login into the system.Admin validates the username and
password entered by the user.Then the user enters the details.The details are stored in the
database for retreival.The entered details are validated by admin.If the details entered are correct
then the hallticket is generated by admin.admin issues the hallticket,where the user
receives..Statechart diagram has only an end state. It has no starting state.The state of an object
depends on its current activity or condition.User,Admin and the Computer system are the actors
in this system.The various components used are User,Login1,Admin,Details,Hallticket.
DEPLOYMENT DIAGRAM
DEVICE NODE
generat
e
examregistrationsyst issue
enterdet em
ail
verify

Student1
public class student1
{ public String name;

public Integer id;
public Integer age;
40
public hallticket theHallticket[];
public details theDetails[];
public admin theAdmin;
/**
*/
public student1()
{
}
/**
@return String
*/
public String register()
{
return null;
}
/**
@return String
*/
public String edit()
{
return null;
}
/**
*/
public void update()
{ } }
41
Admin
//Source file: Z:\\ooad pro\\admin.java
public class admin
{
public String name;
public Integer id;
public student1 theStudent1[];
public hallticket theHallticket;
public details theDetails[];
/**
public admin()
{
}
/**
@return string
public string verifydetails()
{
return null;
}
/**
*/
public String getdetails()
{
return null;
}
public class NewClass
{
42
/**
*/
public NewClass()
{ }
} }
Hallticket
//Source file: Z:\\ooad pro\\hallticket.java
public class hallticket
{
public Integer regno;
public String sub;
/**
*/
public hallticket()
{
}
/**
@return String
*/
public String generate()
{
return null;
}
/**
@return String
43
*/
public String isuee()
{
return null;
}
}
Details
//Source file: Z:\\ooad pro\\details.java
public class details
{
public String course;
public String subject;
public Date date;
/**
*/
public details()
{
}
/**
@return String
*/
public String verify()
{
return null;
}
44
/**
@return String
*/
public String enterdetails()
{
return null;
}
}
Personal
//Source file: Z:\\ooad pro\\personal.java
public class personal extends details
{
public Integer d.o.b;
public Integer ph_no;
/**
*/
public personal()
{
}
@return String
*/
public String insert()
{
return null;
}
}
Paymentdetail
45
//Source file: Z:\\ooad pro\\paymentdetails.java
public class paymentdetails extends details
{
public Integer acc.no;
public Integer creditcard;
public Integer cash;
/**
@roseuid 5332723800DC
*/
public paymentdetails()
{
}
*/
public String makepayment()
{
return null;
}
/**
public String authorize()
{
return null;
}
}
RESULT
Thus the exam registration system project was developed using Rational rose/ Argo UML
Software and implemented successfully using Java.
46
EX NO: 4 ONLINE COURSE RESERVATION SYSTEM
DATE:
AIM
To develop the online course reservation system using rational rose/ Argo UML tools and
implement it using Java.
The requirement form the customer is got and the requirements about the course
registration are defined. The requirements are analysed and defined so that is enables the student
to efficiency select a course through registration system. The project scope is identified and the
problem statement is prepared
PROBLEM STATEMENT
Online course reservation system is used to choose the course through online by the students.
They are provided with a catalogue they can choose the course. The catalogue contains the
detailed description about each course and also the availability of the course which helps the
students to decide on their own.

INTRODUCTION
PURPOSE
The purpose of this document is to present a detailed description of Online Course

Reservation System.It will explain the purpose and features of the system, the interfaces of the
system, what the system will do, the constraints under which it must operate and how the
system will react to external stimuli. This document is intended for both the student and the
administrator of the system.
SCOPE
Online course reservation system will be a online course reservation system for a
student who want to register in a college/university.this system will be designed to allow the
student to reserve coursesin any easy manner. Online course reservation system can be used in
large universities as well as colleges.
Terms Definition
Administrator The person in the college who maintains all course detail.
47
Database Collection of all the information monitored by this system.
Software Requirements A document that completely describes all of the function of a

proposed system and the constraints under which it must
Specification operate.For example ,this document.
User Student ,who wants to register for a course.
TOOLS TO BE USED
Rational rose/ Argo UML Tool (for developing UML patterns)
OVERVIEW
OCRS includes features such as security,e-mail user account,credit card

payment,automatic scheduling,late fee collection ,registration deadline and multicourse
deadline.Also online course system can be fully customized according to user specification.
OVERALL DESCRIPTION
OCRS allows the student to submit the course preferences quickly and
conveniently.the mentioned courses are designed for a peoplewho want to combine the
convenience of online deliverywith hand market assignments,personal supportand feedback from
expert instructor.
PRODUCT PRESPECTIVE
Less cost ,easy ,timesaving,storage.This document gives an overview of the

functionality of the product. This product reduce the manual effort of users.this process can be
done at any time which is comfortable to us.
PRODUCT SPECIFICATION
 Search()
 Save()
 Delete()
 View()
 Add()
 Register()
 Login()
48
 The student must know how to enter the details.

 The student must know how to use the OCR system.
 The student must be able to enter his/her details.
 The administrator must also know how to use OCR system.
GENERAL CONSTRAINTS
 The student will enter the valid username and password.

 The student must enter his name and designation.
 The student must enter the mark details.
SOFTWARE INTERFACES
 Rational rose/ Argo UML
OPERATION
The Payroll System has two active actors. They are employee and administrator. The
employee will be able to enter his details only. The administrator will access the entire system.
He will calculate the salary information of an employee and publish the result. Then the
employee can view his salary calculation.
PRODUCT FUNCTION
 Search()
 Save()
 Delete()
 View()
 Add()
UML DIAGRAMS
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.
49
Login
Register
Student
Verify register
details
<<include>>
Select course
Admin
System
Select timing
Payment
Authorise payment
Update course
details
Logout
Use digram is represented as actors and use cases. In, this case,the student makes
the login into the system. Then he/she registers the course details.The verification of the student
provided details is done by the computer system. During verification, if the system indicates
wrong information, the student has to correct the details.Once the verification is completed
positively, the student is allowed to make the course selection.Again the system verifies whether
the course is available or not. If the selected course is not available, the student has to go on for
selecting other courses, else quit. If available, the student makes the payment via cash or card.
The Admin authorizes the payment via a bank. The computer system is responsible for updating
the course details.After completing all the transactions(once after he/she receives the receipt for
payment), the student finally logs out of the system.Student,Admin and the Computer system are
the actors in this system.The various use cases are login, register, verify register details, select
course, select timing, payment, authorize payment, update course details, logout.
ACTIVITY DIAGRAM
50
User (Student) Admin ( System) Bank
Fill The
registration form
Select "Submit"
option
NO
Student corrects
the details YES
System indicates
wrong information
Receive account Create

details account
Send account
details
[Card]
Submit Authorization
[Cash Pay]
Request
Authorize
request
Receive
receipt
All the actions in this system are represented as activities here, in this diagram.The
student makes the login into the system. Then he/she registers the course details.The verification
of the student provided details is done by the computer system. During verification, if the system
indicates wrong information, the student has to correct the details.Once the verification is
completed positively, the student is allowed to make the course selection.Again the system
verifies whether the course is available or not. If the selected course is not available, the student
has to go on for selecting other courses, else quit. If available, the student makes the payment via
cash or card. The Admin authorizes the payment via a bank. The computer system is responsible
for updating the course details.After completing all the transactions(once after he/she receives
the receipt for payment), the student finally logs out of the system.Student,Admin and the
Computer system are the actors in this system.
CLASS DIAGRAM
51
horizontal lines. The top compartment holds the class name and middle compartment holds the
attribute and bottom compartment holds list of operations.

52
There are various classes in this diagram representing the system. Each class has some attributes
and functions.The attributes represent the various details included in that particular class. The
fuctions specify hat actions can be done in that class. The student makes the login into the
system. Then he/she registers the course details.The verification of the student provided details is
done by the computer system. During verification, if the system indicates wrong information, the
student has to correct the details.Once the verification is completed positively, the student is
allowed to make the course selection.Again the system verifies whether the course is available or
not. If the selected course is not available, the student has to go on for selecting other courses,
else quit. If available, the student makes the payment via cash or card. The Admin authorizes the
payment via a bank. The computer system is responsible for updating the course details.After
completing all the transactions(once after he/she receives the receipt for payment), the student
finally logs out of the system.Student,Admin and the Computer system are the actors in this
system.The various classes used are Student, Login,Admin,Course details, Total amount.
Student Admin System Bank
Login the system
Select course
Available
Register
Submit details
Verify details
Issue approval
Pay fee
Payment Authorization
Enroll
53
The sequence diagram represents all actions taking place in the system in a
sequencing order. The student makes the login into the system. Then he/she registers the course
details.The verification of the student provided details is done by the computer system. During
verification, if the system indicates wrong information, the student has to correct the details.Once
the verification is completed positively, the student is allowed to make the course
selection.Again the system verifies whether the course is available or not. If the selected course
is not available, the student has to go on for selecting other courses, else quit. If available, the
student makes the payment via cash or card. The Admin authorizes the payment via a bank. The
computer system is responsible for updating the course details.After completing all the
transactions(once after he/she receives the receipt for payment), the student finally logs out of
the system.Student,Admin and the Computer system are the actors in this system.The actors here
are Student, admin, bank and the computer system.
1: Login the system

5: Submit details
8: Pay fee
Student Admin
6: Verify details
2: Select course 7: Issue approval
3: Available 10: Enroll
4: Register 9: Payment Authorization
System Bank
The various actions taking place in the online course reservation system are represented one-by-
one in an understandable format in this diagram.The student makes the login into the system.
Then he/she registers the course details.The verification of the student provided details is done
by the computer system. During verification, if the system indicates wrong information, the
student has to correct the details.Once the verification is completed positively, the student is
allowed to make the course selection.Again the system verifies whether the course is available or
not. If the selected course is not available, the student has to go on for selecting other courses,
else quit. If available, the student makes the payment via cash or card. The Admin authorizes the
payment via a bank. The computer system is responsible for updating the course details.After
54
completing all the transactions(once after he/she receives the receipt for payment), the student
finally logs out of the system.Student,Admin and the Computer system are the actors in this
system.
STATE CHART DIAGRAM
no
System shows wrongs
Fill in the Select the Verification information
form "Submit" option
Student corrects
details
yes
create the
cash account
send acount
Payment receive account details
card details
Submit Authorization
request
Authorize
the request
Receive
the receipt
This diagram represents operations in the online course reservation system in a step-by- step
manner. The student makes the login into the system. Then he/she registers the course
the system.Statechart diagram has only an end
PACKAGE DIAGRAM
55
<<layer>>
UI
jframe web login form administrator payment
<<layer>>
Domain
login course details handle payment
<<layer>>
Technical services
Server Database Browser
The package diagram has 3 layers. They are UI layer, Domain layer, Technical Services.
Here the UI layer consists of jframe, web, login form, administrator(actor), payment.The Domain
layer has login, handle payment and course details. Technical services layer has server, database
and browser.
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 structural
relationships between the components of systems. It is represented by boxed figure.
Dependencies are represented by communication association.
56
Details
Student
Administr Total
s
ator amount
Course log in
Details
Component diagram consists of several components. The components are linked with the help of
dependency. Here,the student makes the login into the system. Then he/she registers the course
the system.Student,Admin and the Computer system are the actors in this system.The various
components used are Student, Login,Admin,Course details, Total amount.
DEPLOYMENT DIAGRAM
DEVICE NODE
A physical computing resource with processing and memory service to execute
software, such as a typical computer or a mobile phone.
57
EXECUTION ENVIRONMENT NODE:
login
course
Online course details
reservation system
handle
payment
This deployment diagram shows the relationships among software and hardware components
involved in online course reservation system.The physical hardware is made up of node. Each
component belongs to a node. The various nodes here are login,course details and handle
payment.
Details class
//Source file: Z:\\OOAD lab\\course reser\\Details.java
public class Details
{
private String Name;
private Integer RegNo;
private Integer Percentage;
58
public Administrator theAdministrator;
public Students theStudents[];
/**
*/
public String Edit()
{
return null;
}
}
/**
* Details.Details()
Student class:
//Source file: Z:\\OOAD lab\\course reser\\Students.java
public class Students
{
private String Coursetaken;
private Integer Yearopted;
public Details theDetails[];
public TotalAmount theTotalAmount;
public CourseDetails theCourseDetails[];
public login theLogin;
/**
*/
public Students()
{
}
59
/**
*/
public String Select()
{
return null;
}
}
Coursedetails class
//Source file: Z:\\OOAD lab\\course reser\\CourseDetails.java
public class CourseDetails
{
private String Cname;
private String Cnumber;
private Integer Period;
/**
*/
public CourseDetails()
{
}
/**
*/
public String Display()
{
60
return null;
}
}
TotalAmount class
//Source file: Z:\\OOAD lab\\course reser\\TotalAmount.java
class TotalAmount
{
private Integer PaymentID;
private Integer TotalAmount;
public Students theStudents;
/**
*/
public TotalAmount()
{
}
*/
public Integer Transaction()
{
return null;
}
}
Adminstrator class
//Source file: Z:\\OOAD lab\\course reser\\Students.java
public class Administrator
{
61
private String Coursetaken;
private Integer Yearopted;
public Details theDetails[];
public TotalAmount theTotalAmount;
public CourseDetails theCourseDetails[];
public login theLogin;
/**
public Students()
{ }
public String Select()
{
return null;
}
Login class
//Source file: Z:\\OOAD lab\\course reser\\Details.java
public class logim
{
private String Name;
private Integer RegNo;
private Integer Percentage;
/**
RESULT
Thus the online course reservation system project was developed using Rational rose/
62
EX NO: 5 STOCK MAINTANANCE SYSTEM
DATE:
AIM
To develop the stock maintenance using Rational rose/ Argo UML tools and implement it
using Java.
The Stock Maintenance system initial requirement to develop the project about the mechanism of
the stock maintenance system is caught from the customer. The requirements are analysed and
refined which enables the end users to efficiently use the stock maintenance system.The
complete project is developed after the whole project analysis explaining about the scope and the
project statement is prepared
PROBLEM STATEMENT
The process of the stock maintanence system is that the customer login to the particular
site to place the order for the customer product.The stock maintanence system are described
sequentially through the steps.
a). The customer login to the particular site.
b). They fill the customer details.
c). They place the orders of their project.
d). The vendor login and views the customer details and orders

INTRODUCTION
PURPOSE
Stock maintainence is used to maintain a stock items in a various domain of the

industries.
SCOPE
 It’s goal is to maintain the stocks in various industries.

 This project gives the idea about the fault items and then the products that are to be
replaced.
63
DEFINITION
 The stock has to be maintained properly,since the whole marketing process can be
improved stock maintainance gives the idea about how the stocks are maintained in
a particular concern.
 The stock details which includes the amount of stock available and the stock is to be
purchased and the items which are already bought or delivered is updated
periodically.
OVERVIEW
The main objective of this project is to overcome the workload and time consumption
which makes the maintanance in an organisation a tedious process.this project provides a overall
information about the stock to the users.
PRODUCT PERSPECTIVE
The stock management software can reduce the maximum time consumed by the other
management works and also it is used to maintain a bulk of various items in a various domain
industries.
OVERVIEW
Separate modules have been created for purcharing.view ing stock details.selling
detailsand delivery details as a whole,marketing process can be improved if stock has been
maintained properly.
PRODUCT FUNCTIONS
PURCHASE ORDER
The company places the purchase order to the supplier before making the items
purchased. The supplier in turn purchase the order to the company and the company purchase the
items.
PURCHASE
The company inorder purchase the products from the supplier by quoting the itemname
and the quantity.
SALES ORDER
64
The customer sends the sales order to the customer before selling the items or the
customer without making the sales order he can purchase the items from the company. They will
quote us the product name quantity rate for checking the quantity of the item is available or not.
SALES
The customer purchases the items from the company by making sale order or without
making sale order. The customer has to enter all the details his company and then he can order
his items by enter the item name,quantity and rate.
STOCK TRANSACTION
The company can view the various reports like stock this month can be viewed using the
report.
LOGIN
User can login in to the system if he wants to do the transaction
SECURITY
The system use password authentication username and password is supplied at the time
of installation general construction and operation.
UML DIAGRAMS
USE CASE DIAGRAM

modeled.
65
<<include>> Record check
<<include>>
Admin
purchase officer
Purchase date
Issue date
<<extend>> ware house admin

sales person Place order
cancel order
Purchase
Customer
Issue stocks
Delivery
Cash payment
This model is normally represented by using usecases and actors,And here the purchase officer
places the order and maintains the record by checking the records periodically Here the record
check consist of purchase date and issue date and the sales person purchases the stock from the
purchase officer and issues the stock and the delivery will be made to the customer ,Then the
customer purchases the stock from the sales person and the cash payment will be made to the
sales person.The admin and warehouse admin maintains the same record check which includes
purchase date and issue date and placing orders.
66
ACTIVITY DIAGRAM
Customer Cashier Admin
Place the Receive the Maintaining

orders orders the stocks
Bill the Send the purchase sell the

order Bill amount the stock stock
pay the
bill
Order
deliver
pay by cash pay by card
give the
receipt
Receive the
receipt

All the actions will be represented as activities in this diagram, here the customer starts
the activity by placing the orders to the cashier the cashier receives the orders and bills the order
and sends the bill amount to the customer and the customer pays the bill in two ways they are
pay by cash or else pay by card simultaneously the order will be made by the bill the order and
the delivery is made and the admin will maintain the stock by purchase the stock and sell the
stock(which is delivery),after the cash payment the receipt will be generated to the customer and
the receipt will be received by the customer and the activity will be end here.
67
CLASS DIAGRAM
horizontal lines. The top compartment holds the class name and middle compartment holds the
attribute and bottom compartment holds list of operations.

1. customer
2. cashier
3. stock
4. cashpayment
5. billgenerated
6.saletransaction
7.supervisor
cashpayment is a class that contains an attributes such as total amount,tax calculationand

functions as paycash(). billgenerated is a class that contains an attributes bill amount ,date and
the methods in billgeneration is issuebill().sale transaction is class that contains an attribute item
saled,item purchased and the methods,in database are store transaction details() supervisor
contains an attribute as name,id,phone no and the methods in the supervisor has manages().
68
customer is a class that contains salesperson name, id and the methods in customer class is
store customer details(). Cashier is a class that contains name and id,and the method handle
transaction().the stock class contains an attribute quantity and the method hold resource details().
customer cashier admin
1: place the orders
2: receive stock
3: send stock order
4: deliver stock list
5: deliver stock
6: send bill amount
7: pay bill amount
8: give receipt
9: receipt received

1. The actors used in the stock maintenance system are customer, warehouse admin,
purchase officer and sales officer.
2. The customer put order to the warehouse admin.
3. The warehouse admin will verify the whether the request item is prefect in the database.
4. If the item is available, then the record available function is send to the sales officer.
5. Else the record not available() is send to the purchase officer and the purchase officer
will purchase() the required stock and send to the sales officer.
6. The sales officer will deliver the stock to the customer.
69
1: Place orders
2: Receive orders
7: Pay bill amount
Custom Cashier
er
5: Deliver stock
6: Send bill amount
8: Give receipt
3: Sends stock orders
9: Receipt received 4: Deliver stock list
Admin

1. The customer put an order to the warehouse admin.
2. The ware house admin verify whether the item is available in the database.
3. If the record is not available then the purchase officer purchases the stock .
4. The purchased stock is given to the sales officer.
5. The sales officer will deliver the stock to the customer
6. If the stock is available in the database then it will be delivered to the customer
STATE CHART DIAGRAM
place the receive the maintainin orders

orders orders g the stock
delivery pay the give the receive the

amount receipt receipt
70
PACKAGE DIAGRAM
<<layer>>
ui layer
login form details form transaction form
<<layer>>
domain layer
login product details handle

transaction
<<layer>>
technical service layer
Server browser database
COMPONENT DIAGRAM
cash bill sale superviso

payment generated transaction r
customer cashier stock
71
DEPLOYMENT DIAGRAM
DEVICE NODE
provides a service to host and execute other executable software element
Stock maintanence
system
Ware house
Purchase Customer
admin Sales
officer officer

CASHIER
/**
//Source file: Z:\\OOAD LAB\\errors\\cashier.java
import java.awt.TexturePaintContext;
public class cashier
public TexturePaintContext.Int Phoneno;
public String Address;
public Billgenerated theBillgenerated;
72
public saletransaction theSaletransaction;
public customer theCustomer
* @roseuid 53327D1F00A6
*/
public cashier()
/**
* @roseuid 53325CD900E1
*/
public String handletransaction()
return null;
BILLGENERATED
//Source file: Z:\\OOAD LAB\\errors\\Billgenerated.java
public class Billgenerated
public TexturePaintContext.Int BillAmount;
public TexturePaintContext.Int Date;
public customer theCustomer[];
public cashier theCashier[];
73
public saletransaction theSaletransaction;
public cashpayment theCashpayment;
/**
* @roseuid 5332779300FB
*/
public Billgenerated()
/**
* @return int
* @roseuid 53325A30016A
*/
public int issuebill()
return 0;
STOCK
//Source file: Z:\\OOAD LAB\\errors\\stock.java
public class stock
protected String Quantity;
public supervisor theSupervisor;
/**
* @roseuid 53327D0101D1
74
*/
public stock()
/**
* @roseuid 53325D060302
*/
public String holdresourcedetails()
return null;
CASHPAYMENT
//Source file: Z:\\OOAD LAB\\errors\\cashpayment.java
public class cashpayment
public TexturePaintContext.Int TotalAmount;
private TexturePaintContext.Int TaxCalculation;
/**
* @roseuid 533277300131
*/
75
public cashpayment()
/**
* @return int
* @roseuid 533259F600E3
*/
public int paycash()
return 0;
CUSTOMER
/**
* @roseuid 533277300131
*/
76
{
/**
* @return int
* @roseuid 533259F600E3
*/
return 0;
SALE
/**
* @roseuid 533277300131
*/
77
{
/**
* @return int
* @roseuid 533259F600E3
*/
return 0;
SUPERVISOR
//Source file: Z:\\OOAD LAB\\errors\\stock.java
public class stock
protected String Quantity;
public supervisor theSupervisor;
/**
* @roseuid 53327D0101D1
*/
public stock()
/**
78
* @roseuid 53325D060302
*/
public String holdresourcedetails()
return null;
RESULT:
Thus the stock maintenance project was developed using Rational rose/ Argo UML
79
EX.NO:6 ONLINE RECRUITMENT SYSYTEM
DATE:
AIM
To develop the online recruitment system using rational rose/ Argo UML tools and
The Online Recruitment System is an online website in which applicant can register
themselves and then attend the exam. Examination will be conducted at some venue. The details
of the examination, venue & Date of the examination will be made available to them through the
website. Based on the outcome of the exam the applicant will be short listed and the best
applicant is selected for the job.
PROBLEM STATEMENT
The process of applicants is login to the recruitment system and register for the job through
online. The resume is processed by the company and the required applicant is called for the test.
On the basis of the test marks, they are called for next level of interview. Finally the best
applicant is selected for the job. This process of online recruitment system are described
sequentially through following steps,
• The applicant login to the online recruitment system.

• They register to the company for the job.
• They appear for examination.
• Based on the outcome of the exam, the best applicant is selected.
• The recruiter informs the applicant about their selection.

INTRODUCTION
The online recruitment system helps job seekers to look for job through online. To
recruit the candidate the online recruitment system is used.
PURPOSE
There are different types of reader that this document is intended for, such as developers,
project managers, marketing staff, users, testers, documentation
writers, jobseekers.
80
SCOPE
To provide the information about the job seekers to the industries. Company can get the
information about the proper candidate according to its requirement. According to the
requirement of the companies, provide the information of job seekers to the companies.
DEFINITIONS AND ABBREVIATIONS
Term Definition
Applicant The person who works for a particular firm.
Administrator The person who maintains all employee’s

detail.
Database Collection of all the information monitored by

this system.
Software Requirements Specification A document that completely describes all of

the functions of a proposed system and the
constraints under which it must operate. For
example, this document.
User Employee
PRODUCT PERSPECTIVE
User should be able to see No. Of companies according to place. Vacancies of company
available according to positions that user belongs to.Practice test.(according to subjects)Test
papers for specific company.
.
PRODUCT FUNCTIONS
 User login.
 HR login.
 Consultancy person (customer) login.
 Help Menu.
There are two types of user and our project act as a
81
Middleware :-
 Client(user)= Who search for job and creates its login id on server side for access it.
 Server(End user or provider)= It responsibility to check the information got from user
and check it.
OPERATIONS
The online recruitment system as the main actors such as candidate , admin and company. The
candidate register for the online test and according to the result , the candidate is selected for the
further recruitment.
PRODUCT FUNCTIONS
 User login().
 HR login()
 Consultancy person (customer) login().
 Help Menu.
SOFTWARE PRODUCT FEATURES
This section tell some unique features of our project. In our project links provide to
user to read about how it get hire to specific companies. Online important books provide to user ,
which user can easily download directly from the our website.
UML DIAGRAMS
USE CASE DIAGRAM
modeled.
82
Registration
Checking the details
Candidate
Login <<include>>
Check password
Admin
Attend test
Organization
Result verification
Company details
Company
Update
Attend HR interview
HR
Job coformation
ACTIVITY DIAGRAM
83
User Admin Company
Registration Verifing the

details
yes
Sends username and
password
Login No
Attend the test result

verification
Sees the result Announce the

result
Conducts the
HR interview
Job
conformation
CLASS DIAGRAM
The classes are candidate,manager,company,admin and HR.the attributes are name,mail id,pn
no,address.the operations are uploading resume,result verification,send call letter.Also the
multiplicity excits like 1 and 1…n between the classes.
84
85
User Admin Company
Registration
check the details

if the details are correct
Allow to attend test
Gives username and password
Attend the test
Result verification
Announce result
Attends HR interview
JOB Conformation
.
1: Registration
6: Attend the test
9: Attends HR interview
User Admin
2: check the details

5: Gives username and password
8: Announce result
4: Allow to attend test

7: Result verification
10: JOB Conformation 3: if the details are correct
Company
STATE CHART DIAGRAM
86
form fill receive
send username check the

and password detail
log in
attend the result verify

test
see the annunce

result the result
Job HR
confirmation interview
PACKAGE DIAGRAM
<<layer>>
UI
registration form log in form candidtae adminstrator
<<layer>>
DOMAIN
candiate company detail update details

detaills
<<layer>>
TECNICAL
Database browser
87
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 structural relationships
between the components of systems. It is represented by boxed figure. Dependencies are
represented by communication association.
candidat managerr Company

e y
HR
adminn
DEPLOYMENT DIAGRAM
server
candidate company upadate

details details details
88
HR
//Source file: Z:\\OOAD LAB\\OOAD LAB1\\HR.java
public class HR
private String company;
private String confirmationOfJob;
public candidate theCandidate;
public Candidate theCandidate;
/**
* @roseuid 53327C4C0065
*/
public HR()
/**
* @roseuid 53325AD102E2
*/
public String downloadresume()
return null;
/**
* @return java.awt.TexturePaintContext.Int
89
* @roseuid 53325AF800FD
*/
public TexturePaintContext.Int shortlistresume()
return null;
/**
* @roseuid 53325B0402F1
*/
public TexturePaintContext.Int sendcallletter()
return null;
/**
* @roseuid 53325DAD01CC
*/
public TexturePaintContext.Int requestfeedback()
return null;
MANAGER
90
//Source file: Z:\\OOAD LAB\\OOAD LAB1\\manager1.java
public class manager1
private Integer managerid;
private String manageraddress;
/**
* @roseuid 53327DD5009F
*/
public manager1()
/**
* @roseuid 53327D860387
*/
public String storingresume()
return null;
/**
* @roseuid 53327DAB02B9
*/
public String adminaccess()
91
return null;
COMPANY
//Source file: Z:\\OOAD LAB\\OOAD LAB1\\Companyy.java
public class Companyy
private String coname;
private Integer coID;
private Integer cophno;
private String coaddress;
public managerr theManagerr;
/**
* @roseuid 53327DE702A9
*/
public Companyy()
/**
* @roseuid 53325B3F017A
*/
92
public String upadatedetails()
return null;
/**
* @roseuid 53325B5503DB
*/
public TexturePaintContext.Int shortlistresume()
return null;
ADMIN
//Source file: Z:\\OOAD LAB\\OOAD LAB1\\adminn.java
public class adminn
private String login;
private String username;
private String password;
private String updates;
/**
93
* @roseuid 53327C430294
*/
public adminn()
/**
* @roseuid 53325AAA0090
*/
public TexturePaintContext.Int issuelogin()
return null;
/**
* @roseuid 53325AB401F8
*/
public TexturePaintContext.Int issuepassword()
return null;
/**
* @roseuid 53325ABD03CC
*/
94
public TexturePaintContext.Int validatingdetails()
return null;
CANDIDATE
//Source file: Z:\\OOAD LAB1\\OOAD LAB\\1.ONLINE RECRUITMENT\\candidate.java

public class candidate
{
private Integer candidatename;
private String candidatemailID;
private Integer candidatephno;
public adminn theAdminn;
public HR theHR;
public Companyy theCompanyy;
public managerr theManagerr;
/**
* @roseuid 53327B000302
*/
public candidate()
{
/**
* @roseuid 53327AAD0394
*/
public String uploadresume()
{
return null;
}
/**
95
* @roseuid 53327AC101AE
*/
public String collectcallletter()
{
return null;
}
/**
* @roseuid 53327AE101CB
*/
public String attendinginterview()
{
return null;
}
}
RESULT:
Thus the online recruitment system project was developed using Rational rose/ Argo
UML Software and implemented successfully using Java.
96
EX.NO:7 E-TICKETING
DATE:
AIM:
To develop theE –ticketing system using rational rose/ Argo UML tools and implement it
using Java.
PROJECT SCOPE:
The main scope of the project is to perform the reservation, modification and
cancellations for E-Ticketing with easy.
OBJECTIVE:
The main objective of designing and developing an E-Ticketing is to make the reservation
and other related processes of this system more flexible and easier for the end users and without
waiting in the long queue for the above mentioned processes.
ABSTRACT:
In the existing system all the transactions are done manually. These systems will
have to maintain the data in a hard file. While searching any data is too difficult to find those.
Maintaining too many passenger details and ticket details in separate files are too
complicated. Similarly, it is too difficult to maintain the data for each and every manual
transaction. So the time utilization will be more for this manual system. In order to overcome
these we have to propose the software for the existing method.
We have proposed system that would modernize the activities of E-Ticketing. The
developed system would perform all the functions of the manual system. Using this system we
can save time and the operation will be performed with ease comparatively.
97
USE CASE DIAGRAM:
enter website
login
select ticket
passenger pay
system
print ticket
cancel ticket
logout
check availability
98
CLASS DIAGRAM:
COLLABORATION DIAGRAM:
99
SEQUENCE DIAGRAM:
100
ACTIVITY DIAGRAM:
101
COMPONENET DIAGRAM:
E-Ticketing
DEPLOYMENT DIAGRAM:
application
printer server database
server
client 1 client 2 client 3
//Sourcefile:Z:\\3CSEB34\\railwayManagementSystem.java
public class railwayManagementSystem
{
privateint trainNo; privateint trainName; privateint name;
public centralcomputer theCentralcomputer;
/**
*/
public railwayManagementSystem() {
}
/**
public voidstatus() {
/**
public voidreservation() {
/**
102
public voidcancellation() {
public class centralcomputer
{
privateint trainName; privateint passengerName;
{
privateint trainName; privateint passengerName;
/**
public centralcomputer() {
/**
public voidcancellation() {
/**
/**
RESULT:
Thus the E –Ticketing system project was developed using Rational rose/ Argo UML
EX.NO:8 SOFTWARE PERSONNEL MANAGEMENT SYSTEM
103
DATE:
AIM
To develop the software personnel management system using rational rose/ Argo UML
tools and implement it using Java.
PROJECT SCOPE:
The main scope of the project is to provide the developing company to maintain an
interface to store and access the project details and the respective customer associated with it
along with the assignment details with regards to the team working on the project.
OBJECTIVE:
The main objective of designing and developing a Software Personnel Management

system is to provide with a system which proves to be manually beneficial i.e., benefits the
software developing company. The complete activities and the process right from projects
inception to its successful delivery is incorporated in this system.
PROBLEM STATEMENT:
Software personnel system is a real time application used in the developer’s day to day
system. This is a database to store the project configuration that is specified by the customer and
the software developed for it includes customer and developer requirements needed for the
process. Here we assume ourselves as the developing company:
1. The company is the developer of the software and it contains the necessary
information of the software such as requirements, time limit etc.
2. The customer provides the requirements to the company and requests a suitable
solution system. The company is only responsible for developing the system out of the
requirements of the customer.
3. The company mainly obtains the requirements from the customer and by analyzing
it, prepares a requirements and feasibility documentation initially.
4. Then the company develops a software system that is apt for the integrated
requirements and tests it within itself and by exposure to the concerned customer, and finally
builds a complete a satisfactory solution.
104
ABSTRACT
The Software Personnel management system is highly unique, because of its distinguished
activities and behavior. It sounds to be different, because of its classified nature. It starts right
from the conception of an application and it covers up the entire life cycle till the customer’s
problems are successfully handled. The management of this process and its required
documentation proves to be challenging as it has many cases to concern.
The special cases arise from this management system such as handling the customer’s
problem in such a way that it can be clearly mapped to the development details in the database.
In the existing system all the processing are done manually. These systems will have to
maintain the data in a hard file. While searching any data it is too difficult to find those.
Maintaining too many data about the software in separate files are too complicated.
Similarly, it is too difficult to maintain data for each and every activity. So, the time utilization
will be more in the manual system. In order to overcome these problems we have to propose the
system which overcomes the problem of the existing method.
We have proposed a system that would modernize the activities of Software Personnel
management system. The developed system would perform all the function of the manual
system. Using this system we can save time and the operation will be performed with ease
comparatively.
USE CASE DIAGRAM:
105
login
personal_details
insurance_details
emp
emp_db
bank_details
vehicle_owned
view_emp_details
salary
view_salary_details
company_db
maintain_emp_details
manager
maintain_salary_details
supervise_works
generate_reports
CLASS DIAGRAM
106
ACTIVITY DIAGRAM
107
SEQUENCE DIAGRAM
108
:employee :manager :company
login
if valid
login successful
view company details
allocates jobs for emp and superviser
performsjob andsubmit results
evaluate results
allocates appraisal basedon performance
computes salary and reports
viewsalary details
109
7: 7:evaluate results
6: 6:performs job and submit results

employe manager
e
5: 5:allocates jobs for emp and superviser
1: 1:login 8: 8:allocates approval based on performance
4: 4:view company details
10: 10:view salary details
3: 3:login successful
2: 2:if valid 9: 9:computes salary and reports
compan
y
COMPONENT DIAGRAM
user
interface
about MySQL
system interface
DEPLOYMENT DIAGRAM
ebook-system server
user
//Sourcefile:Z:\\OOAD LAB\\CENTRALMANAGEMENTSYSTEM.java
110
public class CENTRALMANAGEMENTSYSTEM
{
privateint EMPLOYEENAME;
privateint EMPNUMBER;
privateint DETAILS;
/**
@roseuid4D6A16D00179 */
public CENTRALMANAGEMENTSYSTEM() {
}
/**
public voidLEAVETAKEN() {
}
/**
public voidTAX() {
}
/**
@roseuid4D50CC5C00B7 */
public voidLOAN() {
}
/**
@roseuid4D50CC5F0089 */
public voidSALARY() {
}}
//Sourcefile:Z:\\OOAD LAB\\EMPLOYEE1.java
public class EMPLOYEE1 {
privateint EMPDETAILS;
privateint SALARY;
public CENTRALMANAGEMENTSYSTEMtheCENTRALMANAGEMENTSYSTEM;
/**
@roseuid4D6A16D001CE */
public EMPLOYEE1()
{
}/**
@roseuid4D50CCB20311 */
public voidLEAVETAKEN() {
}
RESULT:
Thus the software personnel management system project was developed using Rational rose/
111
EX.NO:9CREDIT CARD PROCESSING
DATE:
AIM
To develop the Credit card processing system using rational rose/ Argo UML tools and
PROJECT SCOPE:
The main scope of the project is to perform the activities like issuing of credit card,
enquiring about the balance, billing process made by customer.
OBJECTIVE:
The main objective of designing and developing the credit card processing is to provide
with the system which proves to be manually beneficial i.e., benefits for both customer and bank.
The complete activities and the process right from accessing a bank account, getting a credit card
and processing of credit card, every single activity is incorporated in this system.
PROBLEM STATEMENT:
1. Submit the application form to the bank
2 Verification of personal details of customer is done by the bank
3. Credit card is given to the customer after issuing
4. After purchasing, the credit card is given to the customer to swipe
5. Retailer checks for the our balance enquiry from the database
6 Database informs bank about data access and current balance
7. The billing details are provided by the bank to the customer
112
USE CASE DIAGRAM
apply for card

bank
customer
send creditcard
update
check customer detail
bill pay via creditcard

pay due amount
database
get payment
retailer
submit pay slip
113
CLASS DIAGRAM
2: fill and submit form

custome bank
r
1: issue form
5: issue card
10: student slip

7: swipe 3: verify customer
6: submit bill credit card 4: generate unique card number
11: get payment

8: check balance
retailer databas
e
9: return pay slip
114
ACTIVITY DIAGRAM
issue application
form
fill form
issue credit
card
visit banking
site
sign in
if authentication valid
NO
yes
access details
COMPONENT DIAGRAM
<<standardEXE>>
credit card
processing
115
SEQUENCE DIAGRAM
customer bank retailer database
issue form
fill and submit form
verify customer
generate unique card number
issue card
submit bill
swipe credit card
check balance
return pay slip
student slip
get payment
DEPLOYMENT DIAGARM
Applicat bank NewDevi

database ce4
printer ...
client2 client3
client1
116
Source Coding://Sourcefile:Z:\\ooad\\Cashier.java public class Cashier
{
privateint ProductName; privateint CostOfProduct;
public CentralsystemtheCentralsystem; /**
@roseuid4D47A1F001C6 */
public Cashier() {
} /**
@roseuid4D479612034A */
public voidEnterAmount() {
} /**
@roseuid4D47961602DD */
public void SwipeCard() {
} /**
@roseuid4D47961C0167 */
public voidPrintBill()
{
} /**
*/
public voidDeliverProduct() {
}}
RESULT:
Thus the Credit card processing systemproject was developed using Rational rose/ Argo
117
EX.NO:10E-BOOK MANAGEMENT SYSTEM
DATE:
AIM
To develop the E-book management system using rational rose/ Argo UML tools and
PROJECT SCOPE:
The main scope of the project is to provide a exhaustive, flexible and reliable E-Book
Management system. This E-BOOK should contain index of the topics. When the main page is
visited index of the topics is displayed. Select the required topic and double click on it. Then the
page with the contents of the selected topic will be displayed. A certain option is also present in
that page to go back to main page and search for other topics.
OBJECTIVE:
The main objective of designing and developing a EBook Management system is to

provide with the system which proves to be beneficial. The activities such as search for the book
online and download, every single activity is incorporated in the system.
PROBLEM STATEMENT:
E-book management system is helpful for the download the books from internet the problem
statements are as follows,
1. User accesses the web browser and gives the book details to be searched.
2. The server checks for the availability of the book, if found display the book to the
user through the browser.
3. The user can also download the book .The server searches for the downloading
software and downloads the book if the software is available.
4. The user can access the book by paying for it.
118
ABSTRACT
EBook refers to the electronic book .We can use books or view them using the
electronic devices like computer by way of browser, which is rightly called as EBook.We can
view the book as the whole. We can also download it buy paying for it and downloaded book can
be read at any time. We can also make printouts on our own demands. In this way both the user
and developer are benefited.
USE CASE DIAGRAM:
119
CLASS DIAGRAM:
120
ACTIVITY DIAGRAM
121
SEQUENCE DIAGRAM:
:login :register :book_details :payment
login
submit
book
ISBN
author
pay
122
2: submit
1: login
:login :register
3:8:
book
5: author 4: ISBN
6: pay
:book_d :paymen
etails t
7:
COMPONENT DIAGRAM
user
interface
e-book
system MySQL
interface
DEPLOYMENT DIAGRAM
user ebook server

system
123
Source Coding:
//Source file:Z:\\OOAD\\USER1.java
public classUSER1 {
private intLOGIN;
private int LOGOUT;
private int DOWNLOAD;
public INTERNET theINTERNET;
/**
@roseuid 4D6B996D029A */
public USER1() {
/**
@roseuid 4D5A0CD902F4 */
public void SURFBOOKS() {
RESULT:
Thus the E-book management system project was developed using Rational rose/ Argo
124
EX.NO:11 FOREIGN TRADING SYSTEM
DATE:
AIM
To develop the foreign trading systemusing rational rose/ Argo UML tools and
PROJECT SCOPE:
The main scope of the project is to provide a exhaustive, flexible and reliable stock
maintenance system which would be beneficial for both stock manager and retailer
OBJECTIVE:
The main objective of designing and developing a Foreign trading system is to provide
with a system which proves to be manually beneficial i.e., benefits both the buyer and the seller
through an broker. The complete activities and the process right from product’s manufacture till
the product gets sold out, every single activity is incorporated in this system.
PROBLEM STATEMENT:
Foreign Trading System is a real time application used in the merchant’s day to day
system. This is a database to store the transaction that takes places between the Buyer seller and
the Broker that includes Product selling and buying with reference to the Broker. Here we
assume our self as the Broker and proceed with the transaction as follows:
1.The Seller is the producer of the items and it contains the necessary information of
the item such as price per item, Date of manufacture, best before use, Number of tem available
and their Company Address.
2. The Broker is the secondary source of an Item and he purchases Item from the Seller
by requesting the required Item with its corresponding Company Name and the Number of Items
required. The Broker is only responsible for distribution of the Item to the Buyer in the Town or
City
3. The Buyer is the one who is prime source for Buying items in the market. The Buyer
get Item from the Broker and not directly from the Seller.
4. The Product availability is the database used in our System which records all
transactions that takes place between the Broker, the buyer and the Seller.
125
5. Forex is the system where the buyer or broker pay the money for the product in their
own money and it will paid in the form of what the seller cash.
6. Customs is responsible for trading the product all over the world. If they give approval
the only we accept to trade.
ABSTRACT
The Foreign trading system is highly unique, because of its distinguished activities and
behavior. It sounds to be different, because of its classified nature. It starts right from the Seller
of the product and its covers up the entire life cycle till the product as purchased by the Buyer.
The maintenance of this Product proves to be challenging as it has many cases to concern.
The special cases arise from this Foreign trading system such as handling the damaged and
expired stock are appropriately designed to match the needs of the real world.
In the existing system all the processing are done manually. These systems will have to
maintain the data in a hard file. While searching any data it is too difficult to find those.
Maintaining too many data about produce in separate files are too complicated. Similarly, it
is too difficult to maintain data for each and every activity. so , the time utilization will be more
this manual system. In order to overcome these problems we have to propose the system which
overcomes the problem of the existing method.
We have proposed a system that would modernize the activities of Foreign trading system.
The developed system would perform all the function of the manual system. Using this system
we can save time and the operation will be performed with ease comparatively.
126
USE CASE DIAGRAM:
login
imports
select operation
reports
register export details

domain
admin
register import details
process payment
payment
logout
127
CLASSDIAGRAM
128
ACTIVITY DIAGRAM
login
user interface relogin
import details export details payment
logout
129
SEQUENCE DIAGRAM
:login :exportdetails :importdetails :payment
register report
make payment
register import details
make payment
exit
130
COMPONENT DIAGRAM
user
interface
foreign trading MySQL

system interface
DEPLOYMENT DIAGRAM
foreign trading
system server
user
RESULT:
Thus the foreign trading systemproject was developed using Rational rose/ Argo UML Software
and implemented successfully using Java.
131
EX.NO:12 CONFERRENCE MANAGEMENT SYSTEM
DATE:
AIM
To develop the conferrence management system using rational rose/ Argo UML tools
and implement it using Java.
PROJECT SCOPE:
The main scope of the project is to issue the prizes and national level certificates.
OBJECTIVE:
The main objective of designing and developing a Conference Management System is to

provide with a system which proves to be manually beneficial i.e., benefits both the participant
and the coordinator. The complete activities and the process is to present the papers and issue the
prizes.
PROBLEM STATEMENTS:
1. The coordinator of the conference spreads the news that the conference is to be held
through the advertisements.
2. The Author or the Participant after seeing the advertisement will register and then
send their paper.
3. The Conference Coordinators collect the registered papers and forwards those papers
to the selection committee.
4. The various selection committees split the work and selects the paper and combines
all the selected papers.
5. The selected papers are passed to the reviewers.
6. The reviewers will recheck the selected paper and if required short down list.
7. After the reviewing process, the reviewing panel members rank the papers and reports
to the conference coordinators.
8. The coordinator updates the database with the details of the author whose papers have
been selected.
9. after updating the coordinator intimates the author that their papers has been selected.
132
USE CASE DIAGRAM
registration
audience
genrateid
participants
submit abstract
select paper
adminstrator
acknowledgement
book hotel
attend conference
133
CLASS DIAGRAM
134
ACTIVITY DIAGRAM
admin participants audience
register
generate id register1
submit papers
select paper
get id
get
send acknowledgemnt
acknowledgement
book hotel
attend
conference
logout
135
SEQUENCE DIAGRAM
:participants :audience :administration :book hotel

details details details
register conference
send id
register conference
send id
send abstract
select abstract
send acknowledgement
book hotel
attend conference
attend conference
136
10: attend conference 9: attend conference
:participants :audience
details details
7: send acknowledgement
1: register conference
4: send id
6: select abstract
8: book hotel
5: send abstract 2: send id
3: register conference
:administrati
on details :book
hotel
COMPONENT DIAGRAM
user
interface
conference MySQL
management system interface
RESULT:
Thus the conferrence management systemproject was developed using Rational rose/ Argo UML
137
EX NO: 13 STUDY OF UML
DATE:
AIM
General Study of UML
DESCRIPTION
The heart of object-oriented problem solving is the construction of a model. The model
abstracts the essential details of the underlying problem from its usually complicated real
world. Several modeling tools are wrapped under the heading of the UML, which stands
for Unified Modeling Language. The purpose of this course is to present important
highlights of the UML.
At the center of the UML are its nine kinds of modeling diagrams, which we
describe here.
 Use case diagrams

 Class diagrams
 Object diagrams
 Sequence diagrams
 Collaboration diagrams
 Statechartdiagrams
 Activity diagrams
 Component diagrams
 Deployment diagrams
The UML is applicable to object-oriented problem solving. Anyone interested in learning UML
must be familiar with the underlying tenet of object-oriented problem solving -- it all begins with
the construction of a model. A model is an abstraction of the underlying problem. The domain is
the actual world from which the problem comes. Models consist of objects that interact by
sending each other messages. Think of an object as "alive." Objects have things they know
(attributes) and things they can do (behaviors or operations). The values of an object's
attributes determine its state.
138
Classesare the "blueprints" for objects. A class wraps attributes (data) and
behaviors (methods or functions) into a single distinct entity. Objects are
instances of classes.
AN INTRODUCTION TO UMLDIAGRAM
The Unified Modeling Language is a language for specifying, constructing,

visualizing, and documenting the artifacts of a software-intensive system. Analogous to
the use of architectural blueprints in the construction industry, UML provides a common
language for describing software models, and it can be used in conjunction with a wide
range of software lifecycles and development processes.
1 USE CASE DIAGRAM

Use Case diagrams identify the functionality provided by the system (use cases),
the users who interact with the system (actors), and the association between the users and
the functionality. Use Cases are used in the Analysis phase of software development to
articulate the high-level requirements of the system. The primary goals of Use Case
diagrams include:
 Providing a high-level view of what the system does

 Identifying the users ("actors") of the system
 Determining areas needing human-computer interfaces.
GRAPHICAL NOTATION
The basic components of Use Case diagrams are the Actor, the Use Case, and the
Association.
ACTOR
An Actor, as mentioned, is a user of the system, and is depicted using a stick figure. The
role of the user is written beneath the icon. Actors are not limited to humans.
If a system communicates with another application, and expects input or delivers output,
then that application can also be considered an actor.
USE CASE
139
A Use Case is functionality provided by the system, typically described as verb +
object (e.g. Register Car, Delete User). Use Cases are depicted with an ellipse. The name
of the use case is written within the ellipse.
ASSOCIATION
Associations are used to link Actors with Use Cases, and indicate that an
Actor participates in the Use Case in some form. Associations are depicted by a
line connecting the Actor and the Use Case.
The following image shows how these three basic elements work together
to form a use case diagram.
Use case diagramsdescribe what a system does from the standpoint of an external
observer. The emphasis is on what a system does rather than how.
Use case diagrams are helpful in three areas.
• Determining features (requirements). New use cases often generate

new
• requirements as the system is analyzed and the design takes shape.
• Communicating with clients. Their notational simplicity makes use case
diagrams a good way for developers to communicate with clients.
• Generating test cases. The collection of scenarios for a use case may
suggest a suite of test cases for those scenarios.
140
2 SEQUENCE DIAGRAM
Sequence diagrams document the interactions between classes to achieve a result, such
as a use case. Because UML is designed for object-oriented programming, these
communications between classes are known as messages. The Sequence diagram lists
objects horizontally, and time vertically, and models these messages over time.
NOTATION
In a Sequence diagram, classes and actors are listed as columns, with
vertical lifelines indicating the lifetime of the object over time.
OBJECT
Objects are instances of classes, and are arranged horizontally. The
pictorial representation for an Object is a class (a rectangle) with the name
prefixed by the object name (optional) and a semi-colon.
ACTOR
Actors can also communicate with objects, so they too can be listed as a column.
An Actor is modeled using the ubiquitous symbol, the stick figure.
LIFELINE
The Lifeline identifies the existence of the object over time. The notation for a Lifeline is
a vertical dotted line extending from an object.
ACTIVATION
Activations, modeled as rectangular boxes on the lifeline, indicate when the object is
performing an action.
141
MESSAGE
Messages, modeled as horizontal arrows between Activations, indicate the
communications between objects.
Below is a sequence diagram for making a hotel reservation. The object initiating the
sequence of messages is a Reservation window.
The Reservation window sends a makeReservation() message to a

HotelChain. The HotelChain then sends a makeReservation() message to a Hotel.
If the Hotel has available rooms, then it makes a Reservation and a Confirmation.
Each vertical dotted line is a lifeline, representing the time that an object exists. Each
arrow is a message call. An arrow goes from the sender to the top of the activation bar
of the message on the receiver's lifeline. The activation bar represents the duration of
execution of the message.
3 ACTIVITY DIAGRAM
Activity diagrams are used to document workflows in a system, from the business level
down to the operational level. When looking at an Activity diagram, you'll notice
elements from State diagrams. In fact, the Activity diagram is a variation of the state
diagram where the "states" represent operations, and the transitions represent the
activities that happen when the operation is complete. The general purpose of Activity
diagrams is to focus on flows driven by internal processing vs. external events.
142
ACTIVITYSTATES
Activity states mark an action by an object. The notations for these states
are rounded rectangles, the same notation as found in State chart diagrams.
TRANSITION
When an Activity State is completed, processing moves to another Activity State.
Transitions are used to mark this movement. Transitions are modeled using
arrows.
➢ SWIM LANE
Swim lanes divide activities according to objects by arranging objects in
column format and placing activities by that object within that column. Objects
are listed at the top of the column, and vertical bars separate the columns to form
the swim lanes.
➢ INITIAL STATE
The Initial State marks the entry point and the initial Activity State. The
notation for the Initial State is the same as in State chart diagrams, a solid circle.
There can only be one Initial State on a diagram.
FINAL STATE
143
Final States mark the end of the modeled workflow. There can be multiple
Final States on a diagram, and these states are modeled using a solid circle
surrounded by another circle.
SYNCHRONIZATION BAR
Activities often can be done in parallel. To split processing ("fork"), or to
resume processing when multiple activities have been completed ("join"),
Synchronization Bars are used. These are modeled as solid rectangles, with
multiple transitions going in and/or out.
4 COMPONENT DIAGRAM
Component diagrams fall under the category of an implementation diagram, a kind of

diagram that models the implementation and deployment of the system. A
Component Diagram, in particular, is used to describe the dependencies between various

software components such as the dependency between executable files and source files.
This information is similar to that within make files, which describe source code
dependencies and can be used to properly compile an application.
COMPONENT
Component represents a software entity in a system. Examples include source code files,
programs, documents, and resource files. A component is represented using a rectangular box,
with two rectangles protruding from the left side, as seen in the image to the right.
DEPENDENCY
144
Dependency is used to model the relationship between two components. The notation for a
dependency relationship is a dotted arrow, pointing from a component to the component it
depends on.
5 CLASS DIAGRAM
A Class diagram gives an overview of a system by showing its classes and the
relationships among them. Class diagrams are static -- they display what interacts but not
what happens when they do interact.
The class diagrams below models a customer order from a retail catalog. The central
class is the Order. Associated with it are the Customer making the purchase and the
Payment. A Payment is one of three kinds: Cash, Check, or Credit. The order contains
OrderDetails (line items), each with its associated Item.
UML class notation is a rectangle divided into three parts: class name, attributes, and
operations. Names of abstract classes, such as Payment, are in italics. Relationships
between classes are the connecting links.
Our class diagram has three kinds of relationships.
• Association -- a relationship between instances of the two classes. There

is an association between two classes if an instance of one class must
145
know about the other in order to perform its work. In a diagram, an
association is a link connecting two classes.
• Aggregation -- an association in which one class belongs to a collection.
An aggregation has a diamond end pointing to the part containing the
whole. In our diagram, Order has a collection of OrderDetails.
• Generalization -- an inheritance link indicating one class is a superclass
of the other. A generalization has a triangle pointing to the superclass.
Payment is a superclass of Cash, Check, and Credit.
An association has two ends. An end may have a role name to clarify the nature of the
association. For example, an Order Detail is a line item of each Order. A navigability
arrow on an association shows which direction the association can be traversed or
queried. An OrderDetail can be queried about its Item, but not the other way around.
The arrow also lets you know who "owns" the association's implementation; in this case,
OrderDetail has an Item. Associations with no navigability arrows are bidirectional.
The multiplicity of an association end is the number of possible instances of the class
associated with a single instance of the other end. Multiplicities are single numbers or
ranges of numbers. In our example, there can be only one Customer for each Order, but
a Customer can have any number of Orders.
This table gives the most common multiplicities.
Multiplicitie Meaning
s
0..1 zero or one instance. The notation n . . m indicates n tom
instances.
0..* or * no limit on the number of instances (including none).

1 exactly one instance
1..* at least one instance

Every class diagram has classes, associations, and multiplicities. Navigability and
roles are optional items placed in a diagram to provide clarity.
146
6 PACKAGES AND OBJECT DIAGRAMS
To simplify complex class diagrams, you can group classes into

packages. A package is a collection of logically related UML elements. The
diagram below is a business model in which the classes are grouped into
packages.
Packages appear as rectangles with small tabs at the top. The package
name is on the tab or inside the rectangle. The dotted arrows are dependencies.
One package depends on another if changes in the other could possibly force
changes in the first.
Object diagramsshow instances instead of classes. They are useful for

explaining small pieces with complicated relationships, especially recursive
relationships.
This small class diagram shows that a university Department can contain lots of
other Departments.
The object diagram below instantiates the class diagram, replacing it by a

concrete example.
147
Each rectangle in the object diagram corresponds to a single instance.
Instance names are underlined in UML diagrams. Class or instance names may be
omitted from object diagrams as long as the diagram meaning is still clear.
7 COLLABORATION DIAGRAMS
Collaboration diagrams are also interaction diagrams. They convey the

same information as sequence diagrams, but they focus on object roles instead of
the times that messages are sent. In a sequence diagram, object roles are the
vertices and messages are the connecting links.
The object-role rectangles are labeled with either class or object names (or
both). Class names are preceded by colons ( : ).
148
Each message in a collaboration diagram has a sequence number. The
top-level message is numbered 1. Messages at the same level (sent during the
same call) have the same decimal prefix but suffixes of 1, 2, etc. according to
when they occur.
8 STATE CHART DIAGRAMS
Objects have behaviors and state. The state of an object depends on its
current activity or condition. A statechart diagram shows the possible states of
the object and the transitions that cause a change in state.
Our example diagram models the login part of an online banking system.
Logging in consists of entering a valid social security number and personal id
number, then submitting the information for validation.
Logging in can be factored into four non-overlapping states: Getting

SSN, Getting PIN, Validating, and Rejecting. From each state comes a
complete set of transitions that determine the subsequent state.
States are rounded rectangles. Transitions are arrows from one state to
another. Events or conditions that trigger transitions are written beside the arrows.
Our diagram has two self-transition, one on Getting SSN and another on Getting
PIN.
149
The initial state (black circle) is a dummy to start the action. Final states
are also dummy states that terminate the action.
9 COMPONENT AND DEPLOYMENT DIAGRAMS
A component is a code module. Component diagrams are physical

analogs of class diagram. Deployment diagrams show the physical
configurations of software and hardware.
The following deployment diagram shows the relationships among

software and hardware components involved in real estate transactions.
The physical hardware is made up of nodes. Each component belongs on a node.

Components are shown as rectangles with two tabs at the upper left.
150

Cs6511 Case Tools Lab Record-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cs6511 Case Tools Lab Record-1

Uploaded by

Copyright:

Available Formats

INDEX

1 PASSPORT AUTOMATION SYSTEM 5

2 BOOK BANK MANAGEMENT SYSTEM 15

3 EXAM REGISTRATION SYSTEM 33

4 ONLINE COURSE RESERVATION SYSTEM 49

5 STOCK MAINTENANCE SYSTEM 65

6 ONLINE RECRUITMENT SYSTEM 82

SOFTWARE PERSONNEL MANAGEMENT

9 CREDIT CARD PROCESSING 114

10 E-BOOK MANAGEMENT SYSTEM 120

11 FOREIGN TRADING SYSTEM 127

12 CONFERENCE MANAGEMENT SYSTEM 134

13 STUDY OF UML 140

PROBLEM ANALYSIS AND PROJECT PLAN

SOFTWARE REQUIREMENTS SPECIFICATION

1.3 DEFINITIONS, ACRONYMS AND THE ABBREVIATIONS

1.4 REFERENCES: IEEE Software Requirement Specification format.

2.0 OVERALL DESCRIPTION

2.1 PRODUCT PERSPECTIVE

2.2 SYSTEM FUNCTIONS

1. Secure Registration of information by the Applicants.

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

2.5 ASSUMPTIONS AND DEPENDENCIES

send police verification

get more information

send report to passport officer

send passport to applicant

DOCUMENTATION OF CLASS DIAGRAM

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

b. THE DATABASE-The database has attributed such as name and operation is

c. REGIONAL ADMINISTRATOR- The regional administrator has attribute such

d. PASSPORT ADMINISTRATOR-The passport administrator has attributed such

:applicant :verification :personal :passport

required more information

send for approval

submit passport to applicant

DOCUMENTATION OF SEQUENCE DIAGRAM.

8: submit passport to applicant 7: send for approval

STATE CHART DIAGRAM

DOCUMENTATION OF STATE CHART DIAGRAM

c. After the verification procedure completed successfully the passport is issued to

a. The components in the passport automation system are passport automation

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

EXECUTION ENVIRONMENT NODE

DOCUMENTATION OF DEPLOYMENT DIAGRAM

PROBLEM ANALYSIS AND PROJECT PLAN

b. Old members will directly select old member button.

c. They select their corresponding year.

SOFTWARE REQUIREMENTS SPECIFICATION

 The user must know how to enter the details.

 Rational rose/ Argo UML.

SOFTWARE PRODUCT FEATURES

DOCUMENTATION OF USECASE DIAGRAM

view book avalability create

enter details check if the

login using user generate user maintain the

enter the book search for

display book is not

DOCUMENTATION OF ACTIVITY DIAGRAM

A sequence diagram shows an interaction arranged in time sequence. It shows object

:login :register :book :diamond type :platinum type

DOCUMENTATION OF SEQUENCE INTERACTION DIAGRAM

STATE CHART DIAGRAM

Register Enter Check If detail