Ex No: 1 PASSPORT AUTOMATION SYSTEM

DATE:
AIM
To develop the Passport Automation System using rational rose tools, visual basic
and MS access.
PROBLEM ANALYSIS AND PROJECT PLAN
To simplify the process of applying passport, software has been created by
designing through rational rose tool, using visual basic as a front end and Microsoft
access as a back end. Initially the applicant login the passport automation system and
submits his details. These details are stored in the database and verification process done
by the passport administrator, regional administrator and police the passport is issued to
theapplicant.
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.
4. The application is then processed manually based on the report given by the
system, and any forfeiting identified can make the applicant liable to penalty as per the
law.
5. The system forwards the necessary details to the police for its separate verification
whose report is then presented to the administrator. After all the necessary criteria
have been met, the original information is added to the database and the passport is
sent to the applicant.
SOFTWARE REQUIREMENTS SPECIFICATION
1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms and Abbreviations
1.4 Reference
1.5 Technology to be used
1.6 Tools to be used
1.7 Overview
2.0 Overall description
2.1 Productive description
2.2 Software interface
2.3 Hardware interface
2.4 System function
2.5 User Characteristic
2.6 Constraints
2.7 Assumption and Dependences
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 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 TECHNOLOGIES TO BE USED
• Microsoft Visual Basic 6.0
1.6 TOOLS TO BE USED
• Rational Rose tool (for developing UML Patterns)
1.7 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 SOFTWARE INTERFACE
1. Front End Client - The applicant and Administrator online interface is built using
Microsoft Visual Basic 6.0.
2. Back End - MS Access database
2.3 HARDWARE INTERFACE
The server is directly connected to the client systems. The client systems have
access to the database in the server.
SYSTEM FUNCTIONS
1. Secure Registration of information by the Applicants.
2. Message box for Passport Application Status Display by the Administrator.
3. Administrator can generate reports from the information and is the only authorized
personnel to add the eligible application information to the database.
2.4 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.5 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.6 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
S. No. UML DIAGRAMS
1 Use Case diagram
2 Class diagram
3 Interaction diagram
4 Sequence diagram
5 Collaboration diagram
6 State Chart diagram
7 Activity diagram
8 Component diagram
9 Deployment diagram
10 Package diagram
DOCUMENTATION OF USECASE DIAGRAM
a. The actors in use case diagram are Applicant, regional administrator, database, passport
Administrator, Police.
b. The use cases are Login, give details, logout, collect details, verification and issue.
c. The actors use the use case are denoted by the arrow
d. The login use case checks the username and password for applicant, regional
administrator, passport administrator and police.
e. The submit details use case is used by the applicant for submitting his details
f. The check status use case is used by the applicant for checking the status of the
application process.
g. The get details, verify and store verification use case is used by passport
administrator, regional administrator, and police.
h. The details use case is used for getting the details form the database for
Verification

the database.

For issuing passport who’s application verified successfully by all the actor.
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 middle
compartment holds the attribute and bottom compartment holds list of operations.
DOCUMENTATION OF CLASS DIAGRAM
APPLICANT-The applicant has attribute such as name and password and
operations are login, give details and logout. The applicant login and fill the details that
are required for applying the passport. After applying the person can view the status
of the passport verification process
THE DATABASE-The database has attributed such as name and operation is store.
REGIONAL ADMINISTRATOR- The regional administrator has attribute such as
name and operation are get details, verify details and send. The regional administrator
gets the details form database and verify with their database
PASSPORT ADMINISTRATOR-The passport administrator has attributed such as
name and operation are get details, verify details and issue. The passport administrator
gets the details form database and verifies with their database, update the verification
and issue the passport.
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.
SEQUENCE DIAGRAM
A sequence diagram shows an interaction arranged in time sequence. It shows
object participating in interaction by their lifeline by the message they exchange
arranged in time sequence. Vertical dimension represent time and horizontal dimension
represent object.
DOCUMENTATION OF SEQUENCE DIAGRAM
a. The applicant login the database and give his details and database store the
details.
b. The passport administrator gets the details from the database and
does 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
COLLABORATION DIAGRAM
A collaboration diagram is similar to sequence diagram but the message in
number format. In a collaboration diagram sequence diagram is indicated by the
numbering the message. A collaboration diagram, also called a communication
diagram or interaction diagram, A sophisticated modeling tool can easily convert a
collaboration diagram into a sequence diagram and the vice versa. A collaboration
diagram resembles flowchart that portrays the roles, functionality and behavior of
individual objects as well as the overall operation of the system in real time.

STATE CHART DIAGRAM

The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state
chart diagram is to understand the algorithm in the performing method.
DOCUMENTATION OF STATE CHART DIAGRAM
a. The states of the passport automation system are denoted in the state chart
diagram
b. Login state represent authentication for login the passport automation system.
c. In this state, it checks whether the applicant has provided all the 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.

DOCUMENTATION OF ACTIVITY DIAGRAM

a. The activities in the passport automation system are login, submit details, get
details, issue passport and penalty and verification.
b. In the login activity applicant give username and password and then login into
the passport automation system after then fill the details that are required for
application.
c. After the verification procedure completed successfully the passport is issued
to the applicant.
COMPONENT DIAGRAM
The component diagram is represented by figure dependency and it is a graph of
design of figure dependency. The component diagram's main purpose is to show
the structural relationships between the components of systems. It is represented by
boxed figure. Dependencies are represented by communication association.

DOCUMENTATION OF COMPONENT DIAGRAM

The components in the passport automation system are passport automation system,
applicant, passport administrator, regional administrator, and police. Applicant,
passport administrator, regional administrator and police are dependent on passport
automation system are shown by the dotted arrow.
DEPLOYMENT DIAGRAM
It is a graph of nodes connected by communication association. It is represented by a
three dimensional box. A deployment diagram in the unified modeling language serves to
model the physical deployment of artifacts on deployment targets. Deployment diagrams
show "the allocation of artifacts to nodes according to the Deployments defined between
them. It is represented by 3-dimentional box. Dependencies are represented by
communication association. The basic element of a deployment diagram is a node of two
types
DEVICE NODE
A physical computing resource with processing and memory service to execute
software, such as a typical computer or a mobile phone.
EXECUTION ENVIRONMENT NODE
This is a software computing resource that runs within an outer node and which itself
provides a service to host an execute other executable software element.
 DOCUMENTATION OF DEPLOYMENT DIAGRAM
The device node is passport automation system and execution environment node is
applicant passport administrator, regional administrator, and police.

PACKAGE DIAGRAM
A package diagram is represented as a folder shown as a large rectangle with a top
attached to its upper left corner. A package may contain both sub ordinate package
and ordinary model elements. All UML models and diagrams are organized into package.
A package diagram in unified modeling language that depicts the dependencies between the
packages that make up a model. A Package Diagram (PD) shows a grouping of elements in
the OO model, and is a Cradle extension to UML. PDs can be used to show groups of
classes in Class Diagrams (CDs), groups of components or processes in Component
Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. Theyare
o User interface layer
o Domain layer
o Technical services layer
DOCUMENTATION OF PACKAGE DIAGRAM
The three layers 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 gets details, verification and
issues.
c. Technical service layer- authenticated user only can access the technical
services.
FORMS:
 SOURCE CODE: FOR
FORM1 M2:
Private Sub Command1_Click Private Sub Command1_Click
()Dim app as Applicant ()Dim subdetails As
Set app = New Applicant Applicant Set subdetails = New
app.Login Applicant subdetails.SubmitDetails
End Sub End Sub
Private Sub Command2_Click() Private Sub Command3_Click()
Dim pass As PassportAdministrator Data1.Recordset.Edit
Set pass = New PassportAdministrator End Sub
pass.Login Private Sub Command4_Click()
End Sub Data1.Recordset.update
Private Sub Command3_Click()Dim End Sub
reg As RegionalAdminstrator Set reg = Private Sub
New RegionalAdminstratorreg.Login Form_Load()
End Sub Text1.Text = ""
Private Sub Command4_Click()Dim Text2.Text = ""
pol As Police Text3.Text = ""
Set pol = New Police pol.Login Text4.Text = ""
End Sub Text5.Text = ""
Private Sub Command5_Click() Text6.Text = ""
If Form1.Text1.Text = "" And Text7.Text = "" Text8.Text = ""
Form1.Text2.Text = "" Then MsgBox End Sub
"LOGIN SUCCESSFUL" FORM3:
Form6.Show Private Sub a_Click()
Else Data2.Recordset.AddN
MsgBox "INVALID USERNAME AND ewEnd Sub
PASSWORD" Unload Me End If End Sub Private Sub Command1_Click()
Private Sub Command6_Click() Dim search As PassportAdministrator
End Set search = New PassportAdministrator
End search.update
Sub End Sub
Private Sub Command2_Click() If Data1.Recordset.Fields(9)=
Data1.Recordset.BOF Then "unsuccessful"
MsgBox "NO DATA FOUND" Data1.Recordset.upd
Else ateEnd Sub
Data1.Recordset.MovePrevious Private Sub ve_Click()
End If Dim verify As PassportAdministrator
End Sub Set verify = New
Private Sub Command3_Click() If PassportAdministratorverify.update
Data1.Recordset.EOF Then End
MsgBox "NO DATA FOUND" Sub
Else FOR
Data1.Recordset.MoveNext M4:
End If Private Sub Command1_Click()
End Sub Dim search As RegionalAdminstrator
Private Sub Command4_Click() Set search = New
Form1.Show RegionalAdminstratorsearch.verify
Unload Me End Sub
End Sub Private Sub
Private Sub Command5_Click() Command2_Click()
Data1.Recordset.MoveFirst Data1.Recordset.Edit
End Sub Data1.Recordset.Fields(10) =
Private Sub Command6_Click() "successful"Data1.Recordset.update
Data1.Recordset.MoveLast End End Sub
Sub Private Sub
Private Sub Command7_Click() Command3_Click()
Data1.Recordset.Edit Data1.Recordset.Edit
Data1.Recordset.Fields(9) = Data1.Recordset.Fields(10)=
"successful"Data1.Recordset.update "unsuccessful"
End Sub
Private Sub
Command8_Click()
Data1.Recordset.Edit
Data1.Recordset.update '##ModelId=4D7522B20232
End Sub Public Sub Login()
Private Sub Command4_Click() If Form1.Text1.Text = "passadmin"
Form1.Show And Form1.Text2.Text = "12345"
Unload Me Then MsgBox "LOGIN
End Sub SUCCESSFUL"
Private Sub Command5_Click() Form1.Text1.Text = ""
Dim update As RegionalAdminstrator Form1.Text2.Text =""
Set update = New RegionalAdminstrator Form1.Text1.SetFocus
update.update Form3.Show
End Sub MsgBox "NO DATA FOUND"
Private Sub Command6_Click() Else
Data1.Recordset.MoveLast
Data1.Recordset.MovePrevious
End Sub
End If
Private Sub Command7_Click()
End Sub
Data1.Recordset.MoveFirst
DATA BASE:
End Sub
Option Explicit
Private Sub Command8_Click()
Private Name As Variant
If Data1.Recordset.BOF Then
Public NewProperty As
RegionalAdminstrator
PassportAdministrator
Public NewProperty3 As
Public NewProperty2 As
PolicePublic Sub store()
1\passport.mdb") Dim Data As Recordset
End Sub
Set Data =
PASSPORT ADMINSTRATOR:
Currentdb.OpenRecordset("PassportAdmi
Option Explicit
nistrator", dbOpenDynaset) If
'##ModelId=4D7522A90
Form3.Text1.Text = "" Then
128
MsgBox "select any data"
Private UserName As
Else
Variant
Data.FindFirst "([PanNo])=" &
'##ModelId=4D7522F9035B
Form3.Text1.Text
Private Password As
If Data.NoMatch Then
Variant
MsgBox "No such record" Form3.Text8.Text
Else Then
MsgBox "success" Form3.Data1.Recordset.Edit
Form3.Text7.Text=Data.Fields(1) Form3.Data1.Recordset.Fields(9)=
Form3.Text8.Text = Data.Fields(2) End If "successful"
End If Form3.Data1.Recordset.update
End Sub MsgBox
'##ModelId=4D7522BF01D4Public Sub "success"Else
update() MsgBox "no
If Form3.Text2.Text = Form3.Text7.Text =""
Form3.Text7.Text Form3.Text8.Text =""End If
AndForm3.Text3.Text= End Sub

RESULT:
Thus the project to develop passport automation system was developed using
Rational Rose Software and to implement the software in Visual Basic is done
successfully.
Ex No: 2 BOOK BANK MANAGEMENT SYSTEM
DATE:
AIM
To develop a project of Book bank management system using Rational Rose
Software and to implement the software in Visual Basic.
PROBLEM ANALYSIS AND PROJECT DESIGN
The book bank management system is 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.
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION
This system would be used by members who are students of any college to check
the availability of the books and borrow the books, and then the databases are
updated. The purpose of this document is to analyze and elaborate on the high-level needs
and features of the book bank management system. It also tells the usability, reliability
defined in use case specification.
OBJECTIVE
The main objective of the system was to design an online book-bank monitoring
system to enable a central monitoring mechanism of the book-bank be more faster and
less error prone. Apart from this,
a. To help the students acquire the right books for the syllabus at the right time.
b. To ensure availability of basic textbooks to students against limited funds and
To develop students ability to handle property loaned to them
OVERVIEW
The overview of this project is to design a tool for book bank so that it can be used
by any book banks to lend their books as well as colleges.
SCOPE
The scope of this book bank management system is to act as a tool for book bank
administrator for quick reference, availability of the books.
FUNCTIONALITY
Many members will be waiting to take the book from the book bank at a single day.
To serve all the members
USABILITY
User interface makes the Recruitment system to be efficient. That is the system will
help the member to register easily and helps them to get their books easily. The system
should be user friendly.
PERFORMANCE
It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.
RELIABILITY
The book bank management system should be able to serve the applicant with
correct information and day-to-day update of information.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the member who borrows book.
EXTERNAL INTERFACE
REQUIREMANTSSOFTWARE
REQUIREMENTS
1. Front end: IBM rational rose enterprise edition.
2. Back end: visual basic 8.0.
HARDWARE REQUIREMENTS
1. Processor: Pentium 4.
2. RAM : 256 MB
3. Operating system: Microsoft windows XP.
4. Free disk space : 1gb
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment system
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse. Actor is any external entity that makes use
of the system being modeled. It is represented using stick figure.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are member and database. The use cases are the activities
performed by actors.
a. The member will register himself in the book bank.
b. After registration he will select the year to which he belongs
c. After selecting he will select books
d. Database will verify the status of book and the books will be given.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes,
their attributes, and the relationships between the classes. It is represented using a
rectangle with three compartments. Top compartment have the class name, middle
compartments the attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has 8 classes:
o Member details class- is the class name. Its attributes are name, father name, and
date of birth, address, phone number, member id, college, degree, course and
semester. Its operations are registration, authentication, and year selection.
o Administrator- is the class name. Its attributes are name, address, phone, mail id. Its
operations are authentication, verification and issue books.
o Year-is the class name. Its attribute is year selection. Its operations are 1styear,
2nd year, 3rd year, 4th year.
o Issue for 1st year-is the class name. Its attributes are member code, member name,
book code, book name, and quantity. Its operation is issue
o Issue for 2nd year-is the class name. Its attributes are member code,
member name, book code, book name, and quantity. Its operation is issue
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is
a construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM
The sequence diagram describes the sequence of steps to show
a. The member registers himself in book bank
b. He will select the year
c. He selects the books given and the database will update the status of book.
d. Then administrator will log in and verify the status of books.
e. If the book is available he will issue the book.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram, A sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as
well as the overall operation of the system in real time.
DOCUMENTATION OF COLLABORATION DIAGRAM
The collaboration diagram is to show how the member registers himself and borrow
the book from the book bank. Here the sequence is numbered according to the flow of
execution.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round
box, which may contain one or more compartments. An initial state is represented as
small dot. A final state is represented as circle surrounding a small dot.
DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behavior of the system.
a. In the first state the member registers himself in book bank
b. After that he will select the year in next state.
c. In the next state he will select the books.
d. In the next state database will update the status of book.
e. In the next state administrator will log in.
f. After authentication he will verify the availability of book.
g. If available he will issue the book.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as a rounded box containing the
name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in book bank management
system.
a. The member registers himself in book bank
b. After that he will select the year.
c. He will select the books.
d. Database will update the status of book.
e. Database will update the details
f. Then the administrator will log in to his account.
g. After authentication he will verify the availability of book.
h. If available he will issue the book.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure.
Dependenciesare represented by communication.
DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is online book bank management
systems. And member details, issue for first year, issue for second year issue for third
year and issue for fourth year are components comes under the main component
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.
DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the book bank which is the main part
and which are the some of the main activities performed in the system. And issue for first
year, issue for second year issue for third year and issue for fourth year are some
activities performed in this system.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the
dependencies between the packages that make up a model. A Package Diagram (PD)
shows a grouping of elements in the OO model, and is a Cradle extension to UML. PDs
can be used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).
There are three types of layer. Theyare
o User interface layer
o Domain layer
o Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are
a. The User interface layer - consists of the web and member details. This layer
describes how the member goes to book bank and registers himself.
b. The Domain layer - shows the activities that are performed in the book bank
management system. The activities are register and book issues.
c. The Technical service layer - the member details and verification details are stored
in the database.
FORM
SOURCE CODE:
Administrator. ClassOption Explicit
'##Model Id=4D5A2FC4038A
Private name As Variant'##Model Id=4D6CB83B006D
Private address As Variant
'##Model Id=4D6CB84902DE
Private phone As Variant'##Model Id=4D6CB8510000
Private mail id As Variant '##Model Id=4D5A34780280
Public New Property As year '##Model Id=4D5A348B0290
Public NewProperty2 As database '##Model Id=4D5A31B30119
Public Sub authentication () On Error Go To Error Handler '## your code
goes here...
If Form10.Text1.Text = "admin" And Form10.Text2.Text = "1234" Then MsgBox "login
successfully"
Form9.ShowElse
MsgBox "invalid password"End If
Exit Sub ErrorHandler:
Call Raise Error (My Unhandled Error,
"authentication Sub") End Sub
'##Model Id=4D5A31E402BF
Public Sub verification()On Error Go To Error Handler '## your
code goes here... Exit Sub
Error Handler:
Call Raise Error (My Unhandled Error , "verification Sub") End Sub
'##Model Id=4D6CB8E403B9
Public Sub issue_books() On Error Go To Error Handler '##
your code goes here... Exit Sub
Error Handler:
Call Raise Error (My Unhandled Error,"issue_books Sub") End Sub
Database .classOption Explicit
'##Model Id=4D5A2FB00128
Private name As Variant'##Model Id=4D51082601C5
Public Sub update ()
On Error Go To Error Handler '## your code goes here... Exit Sub
Error Handler:
Call Raise Error(My Unhandled
Error ,"update Sub") End SubYear . Class
'##Model Id=4D5A317F00DA
Private year_selection As Variant '##Model Id=4D5A319B0128
Public Sub 1styear()
On Error GoTo ErrorHandler '## your code goes here... Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError,"styear Sub")
End Sub '##ModelId=4D5A319F00CB
Public Sub 2nd_year()On Error GoTo ErrorHandler '## your
code goes here... Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError,"nd_year Sub") End Sub
'##ModelId=4D5A31A2032C
Public Sub 3rd_year()
On Error GoTo ErrorHandler '## your code goes here... Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError,"rd_year Sub") End Sub
Issue for first year. class
Option Explicit
'##ModelId=4D5A3381006F
Private member_code As Variant'##ModelId=4D5A33810070
Private member_name As Variant'##ModelId=4D5A33810072Private
book_name As Variant'##ModelId=4D5A347B03B9
Public NewProperty As year'##ModelId=4D5A3381006E
Public Sub issue_for_first()On Error GoTo ErrorHandler '##
your code goes here...
Form6.Data1.Recordset.AddNew Form6.Text5.Text = Form6.Text5.Text + 1
Form6.Text4.Text = Form6.Text4.Text - 1If (Form6.Text4.Text<= 0) Then
 MsgBox "only four books can be selected"Form8.Show
End If Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError,"issue_for_first Sub") End Sub
Issue for second year class Option Explicit '##ModelId=4D5A33D902EE
Private member_code As Variant'##ModelId=4D5A33DC03D8
Private member_name As Variant
'##ModelId=4D5A33E30167
Private book_name As
Variant
'##ModelId=4D5A347C03D8
Public NewProperty As
year
'##ModelId=4D5A33ED00BB
Public Sub
issue_for_second() On
Error GoTo ErrorHandler '##
your code goes here...
Data1.Recordset.AddNew
Form7.Text5.Text = Form7.Text5.Text +
1Form7.Text4.Text = Text4.Text - 1
If (Form7.Text4.Text <= 0)
Then
MsgBox "only four books can be selected"
Form8.Show
End If
Exit
Sub
ErrorHandler:
CallRaiseError(MyUnhandledError,
"issue_for_second Sub") End Sub
Issue for third year class
Option Explicit
'##ModelId=4D5A33F2036
B
Private member_code As
Variant
'##ModelId=4D5A33FA00EA
Private Sub Command3_Click()
Form5.Show
End Sub

RESULT
Thus the project to develop book bank management system using Rational Rose
Software and to implement the software in Visual Basic was done successfully.
Ex No: 3 EXAM REGISTRATION SYSTEM
DATE:
AIM
To develop a project Exam Registration using Rational Rose Software and to
implement the software in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
The Exam Registration is an application in which applicant can register themselves
for the exam. The details of the students who have registered for the examination will
be stored in a database and will be maintained. The registered details can then be verified
for any 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.
1. INTRODUCTION
Exam Registration application is an interface between the Student and the
Authority responsible for the Exams. It aims at improving the efficiency in the
registration of exams and reduces the complexities involved in it to the maximum possible
extent.
2. OBJECTIVE
The main objective of Exam Registration System is to make applicants register
themselves and apply for the exam. Exam Registration System provides easy interface to
all the users to apply for the exam easily.
3. OVERVIEW
The overview of the project is to design an exam registration tool for the registration
Process which makes the work easy for the applicant as well as the Authorities of Exam.
Authorities of the exam can keep track of and maintain the database of the registered
applicants for the exams.
4. GLOSSARY
TERMS DESCRIPTION
APPLICANT OR STUDENT Applicant can register himself by filling out the
Registration form and finally paying the payment for
attending the exam.
DATABASE Database is used to maintain and store the details of
registered applicants.
SOFTWARE REQUIREMENT This software specification documents full set
SPECIFICATION of features and function for online recruitment
System that is performed in company Website.
5. PURPOSE
The purpose of exam registration system is to register for the exam in an easier way
and to maintain the registered details in an effective manner.
6. SCOPE
The scope of this Exam Registration process is to provide an easy interface to the
applicants where they can fill their details and the authorities maintain those details in an
easy and effective way.
7. FUNCTIONALITY
The main functionality of registration system is to make the registration and
database for it to be maintained in an efficient manner.
8. USABILITY
User interface makes the Exam Registration system to be efficient. That is the
system will help the applicant to register easily and helps the authorities to
maintain details effectively. The system should be user friendly.
9. PERFORMANCE
It describes the capability of the system to perform the registration process of the
applicant without any error and performing it efficiently.
10.RELIABILITY
The Exam Registration system should be able to serve the applicant with
Correct information and day-to-day update of information.

11. FUNCTIONAL REQUIREMENTS

Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the applicant who apply for the Exam.
12. EXTERNAL INTERFACE REQUIREMANTS SOFTWARE REQUIREMENTS
1. Front end: IBM rational rose enterprise edition.
2. Back end: visual basic 8.0.
HARDWARE REQUIREMENTS
1. Processor: Pentium 4.
2. RAM : 256 MB
3. Operating system : Microsoft windows XP.
4.Free disk space : 1gb
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment system
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. Itis represented using ellipse.
Actor is any external entity that makes use of the system being modeled. It is
represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are Student, Interface and Database. The use
cases are the activities performed by actors.
a. Student Fills out the form in the form filling process.
b. The interface checks and validates registered details.
c. Then the database is searched for details and verified.
d. Database stores the details and returns acknowledgement.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle
with three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has three classes’ applicant, recruiter and database.
a. Students - is the class name. Its attributes are name, Address, DOB, Gender,College,
Subjects, Semester, Year, Degree, Branch and Payment. The operations performed in the
students class are Form filling, search database and receiving acknowledgement.
b. Registrations Interface - is the class name. Its attributes are Login, Passwordand
database. The operations performed are form verification, store in database and send
acknowledgement.
c. Database - is the class name. The operations performed are storingSearch and
storing the values.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is
a construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
a. The applicant filling form and registering for exam.
b. The verification done by the interface and sending acknowledgement
for registration.
c. Searching the database with login and displaying it for maintenance.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as
well as the overall operation of the system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM
The collaboration diagram is to show how the Student registers and the authorities
maintain the details of the registered students in the registration system. Here the
sequence is numbered according to the flow of execution.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round
box, which may contain one or more compartments. An initial state is represented as
small dot. A final state is represented as circle surrounding a small dot.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
a. First state is form filling where the student fill the form to registration system.
b. The next state is form verification by the interface.
c. Then store the details in the database.
d. The student receives acknowledgement for registering.
e. Search database with login information.
f. Display the searched data in the interface.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as a rounded box containing the
name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in recruitment system.
a. First the student fills the form.
b. The student details are verified and stored in database.
c. Acknowledgement sent is received by student.
d. Search database with login and if data present in the database.
e. The searched data is displayed if available.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies
are represented by communication association.

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is Exam Registration system.
And register verification and search details are the components comes under the main
component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the Exam Registration system which
is the main part and the devices are the register, verify and search which are the some
of the main activities performed in the system.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a grouping
of elements in the OO model, and is a Cradle extension to UML. PDs can be used to
show groups of classes in Class Diagrams (CDs), groups of components or processes in
Component Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are
a. User interface layer
b. Domain layer
c. Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are
a. The User interface layer - consists of the form and login. This layer describes show the applicant logins
to the search and applies for the exam.
b. The Domain layer - shows the activities that are performed in theExam
Registration system. The activities are register and search the database.
c. The Technical service layer - get student details and the selected applicant details arestored in the
database.
FORMS
SOURCECODE
Students:
Option Explicit '##ModelId=4D2137EC15D6
Private name As Variant '##ModelId=4D3627BF0157
Private address As Variant '##ModelId=4D424904184B
Private dob As Variant '##ModelId=4D413519007D
Private subjects As Variant '##ModelId=4D4136D9037A
Registration Website:
Option Explicit '##ModelId=4D4135610399
Private qualification As Variant'##ModelId=4D413565000F
Private login details As Variant'##ModelId=4D41356F0203
Private fee details As Variant'##ModelId=4D4136E200EA
Private exam dates As Variant'##ModelId=4D4136E200EA
Public NewProperty As university database'##ModelId=4598067E032C
Public NewProperty2 As universitydatabase
Public NewProperty3 As universitydatabase
Private college As Variant '##ModelId=4D41381923B5
Public NewProperty As reg websiteDim v1 As reg website
'##ModelId=4D91482B0167 '##ModelId=4C71253D02AF
Public Sub Form Filling()
End Sub '##ModelId=4598050E03D8
Public Sub Registration() End Sub
Public Sub verification()End Sub
Public Sub processing()End Sub
Public Sub registration()End Sub
University Database:
Option Explicit '##ModelId=459806A30280
Public NewProperty As students'##ModelId=4598060A02BF
Public Sub verify_the_details()
End Sub '##ModelId=45980463F57B5
Public Sub storing registration()End Sub
Form1:
Dim ob1 as students
Private sub cmdregistrationform_click()
Set ob1=new studentsob1.Form_Filling End sub
Public Sub Form_Filling() datcollege.Recordset.AddNew cmdSaveRecord.Enabled= True
cmdMovePrevious.Enabled =FalsecmdMoveNext.Enabled = False
cmdNewRecord.Enabled =FalsecmdDeleteRecord.Enabled = False
datcollege.Recordset.MoveNext
End If Form1.ShowEnd Sub
Dim ob3 as students
Private sub cmdregistrationform_click()
Set ob3=new studentsob3.Previous
End sub
Private Sub previous()Form1.show
End Sub
Dim ob4 as students
Private sub cmdregistrationform_click()
Set ob4=new students
ob4. Storing_registrationEnd Sub
Public Sub Storing_registration()
Form1.ShowEnd Sub
Dim ob2 as students
Private sub cmdregistrationform_click()
Set ob2=new studentsob2.Next
End sub
Private Sub cmdMoveNext_Click()Form1.Show
End Sub
Private Sub next()
datcollege.Recordset.UpdateExit Sub
End If
cmdSaveRecord.Enabled = False cmdMovePrevious.Enabled = True
cmdMoveNext.Enabled = True cmdDeleteRecord.Enabled = True
cmdNewRecord.Enabled = TrueForm1.Show
End Sub
Private Sub cmdSaveRecord_Click() Form1.Show
End Sub
Public Sub Processing() datcollege.Recordset.MovePreviousForm1.show
End Sub
Dim ob5 as students
Private sub cmdregistrationform_click()
Set ob5=new studentsob5. Delete
End Sub
Public Sub Delete()
On Error GoTo Delete_ErrorExit Sub
End If
datcollege.Recordset.DeletecmdMoveNext_Click
Exit Sub Delete_Error:
End Sub
Private Sub cmdDeleteRecord_Click()form1.show
End Sub

RESULT
Thus the project to develop Exam Registration system using Rational Rose Software
and to implement the software in Visual Basic is done successfully.
Ex No: 4 STOCK MAINTENANCE SYSTEM
DATE:
AIM
To develop a project stock maintenance system using Rational Rose Software and
to implement the software in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
The Stock Maintenance System, initial requirement to develop the project about the
mechanism of the Stock Maintenance System is caught from the customer. The
requirement are analyzed and refined which enables the end users to efficiently use 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 stock maintenance system is that the customer login to the
particular site to place the order for the customer product.
a. The customer login to the particular site.
b. They fill the customer details.
c. They place the orders for their product.
d. The vendor login and views the customer details and orders.
SOFTWARE REQUIREMENT SPECIFICATION
1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY
9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL REQUIRMENTS
INTRODUCTION
This software specification documents full set of features and function for
online stock maintenance system that is performed in company website. In this we
give specification about the customer orders. It tells the usability, reliability defined in use
case specification.
OBJECTIVE
The main objective of the stock maintenance system is to maintain the stock. It
provides the vendor to maintain the stock in a precise manner.
OVERVIEW
The overview of the project is to design an online tool for the recruitment
process which eases the work for the customer as well as the companies.
Companies can create their company forms according to their wish in which the applicant
can register. The purpose of stock maintenance system is to maintain the stock in a precise
manner.
SCOPE
The scope of this stock maintenance system is to maintain the stock.
FUNCTIONALITY
The main functionality of the stock maintenance system is to maintain the stock.
USABILITY
User interface makes the stock maintenance system to be efficient. That is the
system will help the customer to place the details and orders easily and helps the vendor
to maintain the stock accurate. The system should be user friendly.
PERFORMANCE
It describes the capability of the system to maintain the stock without any loss of
stock and performing it efficiently.
RELIABILITY
The stock maintenance system should be able to maintain the stock with correct
updates from day to day placement of new orders from customer.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the customer who places the orders.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online
recruitment system
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
ofthe system being modeled. It is represented using stick figure.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are customer, vendor and database. The use
cases are the activities performed by actors.
CUSTOMER:
a. Customer logins to the particular system and fills the customer details
and places the orders.
DATABASE:
a. All the details and orders given by customer are updated in the database.
VENDOR:
a. Vendor logins and verify the customer orders and the stock details.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle with
three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
1. This class diagram has three classes’ customer, vendor and database.
a. Customer - is the class name. Its attributes are username, password, name,
phone no and address. The operations performed in the customer class are
login and places the orders.
b. Vendor - is the class name. Its attributes are views the database.
c. Database - is the class name. The operations performed are storing customer
details, and their orders.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order.
It is a construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM
The sequence diagram describes the sequence of steps to show
o The customer login in to the system and fills the customer details.
o Then the customer places the order. It updated to the database.
o The vendor login to the system and views the customer orders and the stock details.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as well
as the overall operation of the system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM
The collaboration diagram is to show how the customer login and places the orders
in the system. Here the sequence is numbered according to the flow of execution.
STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in performing a
method. It is also called as state diagram. A state is represented as a round box, which
may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.
DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behavior of the system.
• First state is login where the customer login to the system.
• The next state is to fill the customer details.
• And the next state is to place the orders.
• Update database with the orders and details of customer
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram shows
the overall flow of control. An activity is shown as a rounded box containing the name of
the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram flow of stepwise activities performed in stock maintenance
system. First the customer login then fills the details.
a. The customer places the order according to their needs.
b. After placing the order the database is updated.
c. Vendor login to the system and verifies the customer orders and stock details.
COMPONENT DIAGRAM
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.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is stock maintenance systems.
And customer database details and update database then vendor views the database are the
components comes under the main component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the stock maintenance system which
is the main part and the devices are the filling customer details and placing orders then
vendor views which are the some of the main activities performed in the system.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML. PDs can be
used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).
There are three types of layer. They are
1. User interface layer
Software objects representing domain concepts that fulfill application requirements,
such as calculation of a sale total.
2. Domain layer
Layer that contains domain objects to handle application logic work
3. Technical services layer
General purpose object and sub system that provide supporting technical services, such as
interfacing with a database logging

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the online recruitment system are
o The User interface layer - consists of the web and login. This layer describe s
how the applicant logins to the website and places the order.
o The Domain layer - shows the activities that are performed by the
customer to place the orders.
o The Technical service layer - the vendor logins and verifies the
customer orders and stock details
FORMS
SOURCE CODE Private Sub
CUSTOMER Command2_Click()
Option Explicit Unload Me
'##ModelId=4D47C9A90242 End Sub
Private cust_name As Variant PLACING ORDERS
'##ModelId=4D47C9B100EA Option Explicit
Private address As Variant '##ModelId=4D47C9FE00
'##ModelId=4D47C9B5008C AB
Private phone_no As Variant Private select_goods As
'##ModelId=4D47C93A008C Variant
Public NewProperty As placing_orders '##ModelId=4D47C93D031C
'##ModelId=4D47C947006D Public NewProperty As
Public NewProperty2 As database3 database3
'##ModelId=4D47C98A01E4 '##ModelId=4D47C9910222
Public NewProperty3 As database3 Public NewProperty2 As
'##ModelId=4D47C98D036B database3
Public NewProperty4 As placing_orders '##ModelId=4D47CA0E0232
'##ModelId=4D47C9C00186 Public Sub
Public Sub submit() submit()End
End Sub Sub
FORM 1 FORM 2
SUBMIT BUTTON SUBMIT COMMAND
Private Sub Command1_Click() Private Sub
Form6.Text1.Text = Form1.sgs.Text Command1_Click()Dim p
As placing_orders
Form6.Text2.Text = Form1.Text2.Text
Set p = New
Form6.Text3.Text = Form1.Text3.Text
placing_ordersp.submit
Form2.Show
End Sub
End Sub
EXIT BUTTON Public Sub submit()
If (Form2.Combo1.Text =
"MONITOR")Then
Form6.Text4.Text = Form2.Show
Form2.Combo1.TextForm3.Show End Sub
End If Private Sub Command2_Click()
If (Form2.Combo1.Text = "HARD Text1.Text = Text1.Text - Text3.Text
DISC")Then Adodc1.Recordset.Fields(2) =
Form6.Text4.Text = Form2.Combo1.Text Text1.TextForm6.Text5.Text =
Form4.Show Form5.Label2
End If Form6.Text6.Text =
If (Form2.Combo1.Text = Form5.Text3.Text
"KEYBOARD") Then Form6.Show
Form6.Text4.Text = Form2.Combo1.Text Form8.Text11.Text =
Form5.Show Form3.Text1.T
End If End extAdodc1.Recordset.Update
Sub End Sub
DATABASE Private Sub Command3_Click()
'##ModelId=4D47C9A90242 Text2.Text = Text2.Text - Text4.Text
Private cust_name As Variant Adodc1.Recordset.Fields(3) =
'##ModelId=4D47C9B100EA Text2.TextForm6.Text5.Text =
Private address As Variant Form5.Label3
'##ModelId=4D47C9B5008C Form6.Text6.Text =
Private phone_no As Variant Form5.Text4.Text
'##ModelId=4D47C93A008C Form6.Show
Public NewProperty As placing_orders Form8.Text12.Text =
'##ModelId=4D47C947006D Form3.Text2.T
Public Sub submit() extAdodc1.Recordset.Update
End Sub End Sub
FORM 8 Private Sub Command1_Click()
\

RESULT
Thus the project stock maintenance system using Rational Rose Software and
implement the software in Visual Basic is executed successfully.
Ex No: 5 ONLINE COURSE RESERVATION SYSTEM
DATE:
AIM
To design an object oriented model for course reservation system.
PROBLEM ANALYSIS AND PROJECT PLANNING
The requirement form the customer is got and the requirements about the course
registration are defined. The requirements are analyzed 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
a. Whenever the student comes to join the course he/she should be provided with the list
of course available in the college.
b. The system should maintain a list of professor who is teaching the course. At the end
of the course the student must be provided with the certificate for the completion of the
course.
OBJECTIVES
The main purpose of creating the document about the software is to know about
the list of the requirement in the software project part of the project to be
developed. It specifies the requirement to develop a processing software part that
completes the set of requirement.
SCOPE
In this specification, we define about the system requirements that are about from the
functionality of the system. It tells the users about the reliability defined in use case
specification
FUNCTIONALITY
Many members of the process line to check for its occurrences and transaction,
we have to carry over at sometimes
USABILITY
The user interface to make the transaction should be effectively
PERFORMANCE
It is the capability about which it can perform function for many users at sometimes
Efficiently (i.e.) without any ever occurrences
RELIABILITY
The system should be able to the user through the day to day transaction
USERCASE DIAGRAM
Use case is a sequence of transaction in a system whose task is to yield result of
measurable value to individual author of the system Use case is a set of scenarios together
by a common user goal. A scenario is a sequence of step describing as interaction between
a user and a system

DOCUMENTATION FOR USE CASE DIAGRAM

The use case diagram in the course registration system illustrates thesequence of
steps followed in the system related to the actions of the system LOGIN
This use case gives an entry to the student, professor and the register
SELECT COLLEGE AND COURSE
This use case list out the various courses offered by the institution
SUBMIT GRADES
This use case given the marks scored by the system
MAINTAIN PROFESSOR INFORMATION
This use case maintain the information about professor in the system
MAINTAIN STUDENT INFORMATION
This use case maintain the information about the professor in the system
CLOSE REGISTRATION
This use case describes the certification of the student when he/she finishes the
Course.
CLASS DIAGRAM:
A class diagram describes the type of objectors in the system the various kinds of
static relationship that exist among them.

DOCUMENTATION OF CLASS DIAGRAM

a. The various classes involved in the system are registered student record, professorrecord
all demonstration grade and close registration
b. The student register for the course
c. After the course gets over each student will be asked to write a test
d. Test marks are analyzed for the issue grade sheet after certification the registration of
the student in closes.
SEQUENCE DIAGRAM
A sequence diagram is one that includes the object of the projects and tells the
lifetimes and also various action performed between objects.

DOCUMENTATION OF SEQUECE DIAGRAM

a. The single use case in the course registration is taken and sequence of operation
followed in the use case
b. In the registration for the course use case diagram illustration on the process of
registering and select a course.
c. The student enters the institution and gets a catalog about the list of course offered by
the system.
d. The student can select a particular use case and registration for the course
e. In the record use case submit grade at the end of each course each student will be
asked to write a test. The result will evaluate for the issue of grade sheet and the grade are
submitted.
COLLOBORATION DIAGRAM
It is same as the sequence diagram that involved the project with the only
difference that we give the project with the only difference that we give sequence number
to each process.

DOCUMENTATION OF COLLOBORATION DIAGRAM

The diagram is also similar to sequence diagram but the difference is the various operations
involves in the particular use case will be numbered. In this diagram the sequence of steps.
Getting the catalog to now about the course Selecting the course to study
STATE DIAGRAM
It is a technique to describe the behavior of the system. It describes all the possible states
that a particular object gets into the object oriented technique. State diagram are drawn for
a single class to show to the lifetime behavior of a single objects
DOCUMENTATION OF THE STATE DIAGRAM
1. The various states are login student, register for course, maintain studentand
professor record, submit grade and close registration
2. The state diagram describes the behavior of the system.
3. The main purpose of the system is to register the student for a course
4. After the student enrolls the course maintain the record for the student and Professor
5. After the test being conducted each student mark will be analyzed for the gradesheet
purpose
6. After the certification the registration is closed
ACTIVIY DIAGRAM
It includes all the activities of particular project and various steps using join and
Forks.

DOCUMENTATION OF ACTIVITY DIAGRAM

a. The user login in to the course registration system
b. He/she select a particular course form the list of available course
c. After the student register into the course the institution start the bill operation and
record is maintain
d. The professor also start maintains the student record
e. At the end of the course based on the result grade the grade sheet or certificate is
issued to the student
f. The registration is closed for the particular student
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.

DOCUMENTATION OF COMPONENT DIAGRAM

a. The components of the online course reservation are course details, login, and
college details
b. The course details, login and college details are dependent on the online course
reservation are show by the dotted arrows
DEPLOYMENT DIAGRAM
It is a graph of nodes connected by communication association. It is represented by
a three dimensional box. A deployment diagram in the unified modeling language
serves to model the physical deployment of artifacts on deployment targets.
Deployment diagrams show "the allocation of artifacts to nodes according to the
Deployments defined between them. It is represented by 3-dimentional box.
Dependencies are represented by communication association. The basic element of a
deployment diagram is a node of two types
DEVICE NODE - A physical computing resource with processing and memory service to
execute software, such as a typical computer or a mobile phone.
EXECUTION ENVIRONMENT NODE-- This is a software computing resource that runs
within an outer node and which itself provides a service to host an execute other
executable software element.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The device node is online course reservation and execution nodes are course
details, login and college details
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).
DOCUMENTATION OF PACKAGE DIAGRAM
The three layer of online course reservation are user interface layer, domain layer and
technical service layer
a. The user interface layer- represent the user interface component such as web where
the student login
b. The domain layer- has the major action such as select college, select course, request
for seat and request for hostel.
c. Technical service layer-only authenticated user can access the technical service
FORMS
SOURCE CODE
Private Sub Command1_Click()Dim log As student1
Set log = New student1log.study
End Sub
Private Sub Command2_Click()Unload Me
End SubFORM2
Private Sub Command1_Click()Dim course As college
Set course = New collegecourse.admission
End Sub
Private Sub Command2_Click()End
End SubFORM3
Text1.Text = Text1.Text - 1 Text2.Text = Text2.Text - 1
Text2.Text = Text2.Text - 1 End Sub
End Sub Private Sub Command2_Click()
Private Sub Command2_Click() Text1.Text = Text1.Text - 1
Text1.Text = Text1.Text - 1 Text3.Text = Text3.Text - 1
Text3.Text = Text3.Text - 1 End Sub
End Sub
Private Sub Command3_Click()
Form6.Show
Unload Me
Private Sub Command1_Click()
Private Sub Command3_Click()Form6.Show
Unload Me
End SubFORM4
Private Sub Command1_Click()Text1.Text = Text1.Text - 1
Text2.Text = Text2.Text - 1
End Sub
Private Sub Command2_Click()Text1.Text = Text1.Text - 1
Text3.Text = Text3.Text - 1
End Sub
Private Sub Command3_Click()Form6.Show
Unload Me
End SubFORM5
Private Sub Command1_Click()Text1.Text = Text1.Text - 1
EndSubFORM6
PrivateSubCommand1_Click()End
End Sub

RESULT
Thus the project to develop online course reservation system was developed using
Rational Rose Software and to implement the software in Visual Basic is done successfully.
Ex No: 6 E-TICKETING
DATE:
AIM
To develop the E-Ticketing System using Rational Rose Software and to
implement the software in visual basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
In the E-Ticketing system the main process is a applicant have to login the
database then the database verifies that particular username and password then the user
must fill the details about their personal details then selecting the flight and the database
books the ticket then send it to the applicant then searching the flight or else cancelling
the process.
PROBLEM STATEMENT
The E-Ticketing system is the initial requirement to develop the project about the
mechanism of the E-ticketing system what the process do at all.
a. The requirement are analyzed and refined which enables the end users
to efficiently use the E-ticketing system.
b. The complete project is developed after the whole project analysis explaining
about scope and project statement is prepared.
c. The main scope for this project is the applicant should reserve for the flight ticket.
d. First the applicant wants to login to the database after that the person wants tofill
their details.
e. Then the database will search for ticket or else the person will cancelled the
ticket if he/she no need.
SRS DOCUMENT
1.1Purpose
The applicant should login to the database for reserving the ticket. In the
specification use define about the system requirements that are part from the functionality
of the system. It tells the usability, reliability defined in the use case specification.
1.3 References
IEEE Software Requirement Specification format
1.4 Technology to Be Used
Microsoft Visual Basic 6.0
1.5 Tools Be Used
Rational Rose 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. OVERALL DESCRIPTION
2.1 Functionality
The database should be act as a main role of the e-ticketing system it can be
booking the ticket in easy way.
2.2 Usability
The User interface makes the Credit Card Processing System to be efficient.
2.3 Performance
It is of the capacities about which it can perform function for many users at the
sometimes efficiently that are without any error occurrence.
2.4 Reliability
The system should be able to process the user for their corresponding request.
UML DIAGRAMS
The project can be explained diagrammatically using the following diagrams.
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. State chart diagram
f. Activity diagram
g. Component diagram
h. Deployment diagram
i. Package diagram
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
Particular goal. It is represented using ellipse. Actor is any external entity that makes use of
the system being modeled. It is represented using stick figure.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are applicant, and E-ticketing Database. The use
cases are the activities performed by actors.
The actors in this use case diagram are
a. Applicant - logins the E-Ticketing and filling the required data fields.
b. E-Ticketing Database-verify the login and filling the details and
selected applicant details are stored in it.
Login - applicant enter their username and password to enter in to the E-Ticketing form.
Filling Details -applicants are used to enter the details in the required Form.
Selecting Flight -it is used to selecting the flight for the applicants. Book
Ticket - it is used to book the ticket through the E-Ticketing database. Search -it is used to
search the flight details.
Cancel Ticket- it is used to cancel the ticket through the E-Ticketing Database.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes,
their attributes, and the relationships between the classes. It is represented using a
rectangle with three compartments. Top compartment have the class name, middle
compartment the attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has two classes applicant, E-Ticketing Database.
a. Applicant - logins the E-Ticketing and filling the required data fields.
b. E-Ticketing Database-verify the login and filling the details and select applicant
details are stored in it.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order.

It is a construct of a Message Sequence Chart. There are two dimensions.

1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM
This sequence diagram describes the sequence of steps to show
a. Applicants are used to login the form. And then it’s verified the username and
password.
b. If the password and username are correct then applicants are used to login the
fillingdetails.
c. Applicants are used to selecting the flights and book the tickets.
d. Now the E-Ticketing Database verify the filling Details.
e. And then the E-Ticketing Database displays the ticket information.
f. In case of any sudden change of the plan, the applicant can cancel the ticket.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram
into a sequence diagram and the vice versa. A collaboration diagram resembles a
flowchart that portrays the roles, functionality and behavior of individual objects as well
as the overall operation of the system in real time.

DOCUMENTATION OF COLLABRATION DIAGRAM

This collaboration diagram is to show how the applicant login and register in the
E-Ticketing system. Here the sequence is numbered according to the flow of execution.
This collaboration diagram is to show the selection process of the applicant for the ticket
booking. The flow of execution of this selection process is represented using the numbers
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in performing
a method. It is also called as state diagram. A state is represented as a round box, which
may contain one or more compartments. An initial state is represented as small dot. A
final state is represented as circle surrounding a small dot.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
• First state is login where the applicant login to the E-Ticketing system.
• The next state is filling details the applicants are used to fill the form.
• Then applicant used to selecting the flight.
• The applicant appears for book ticket and search details from E-Ticketing Database.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control.
An activity is shown as a rounded box containing the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram describes the behavior of the system. First state is login where
the applicant login to the E-Ticketing system. The next state is filling details the applicant
is used to fill the form. Then applicant used to selecting the flight. The applicant appears for
book ticket and search details from E-Ticketing Database.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies are
represented by communication association.

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is E-Ticketing systems. And Login,
Filling Details and selecting flights applicants are the components comes under the main
component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the E-Ticketing system which is the
main part and the devices are the login; appear for the filling details and selecting
flights applicant which are the some of the main activities performed in the system.
PACKAGE DIAGRAM
FORMS
SOURCE CODE Private Sub
FORM3 Command6_Clic
Private Sub Command1_Click() k()Unload Me
Adodc1.Recordset.AddNew End Sub
End Sub Private Sub Command7_Click()
Private Sub Command2_Click() Adodc1.Recordset.Delete
Adodc1.Recordset.MoveNext End Sub
End Sub Private Sub Command8_Click()
Private Sub Command3_Click() Form3.Show
Adodc1.Recordset.MovePrevious End
End Sub Sub
Private Sub Command4_Click() FOR
Adodc1.Recordset.MoveLast M1
End Sub Private Sub
Private Sub Command5_Click() Command1_Click() If txtus.Text
Adodc1.Recordset.Update = "admin" Then If txtpass.Text
Form1.Show = "admin" Then MsgBox "login
End Sub sucess"
UnloadMe
Else
MsgBox "The password you entered is incorrect.Please retype the password.", vbCritical,
"Wrong Entry"
txtpass.Text=""End If
Else
MsgBox "The username and password you entered is incorrect.Please retype the
usernameand password.", vbCritical, "Wrong Entry"
txtus.Text = ""
txtpass.Text ""
End If
End Sub
Private Sub Command
2_Click()
Unload Me
End Sub
FORM5
Private Sub Command
1_Click()
Adodc2.Record
set.AddNew
End Sub
Private Sub Command
2_Click()
Adodc2.Record
set.MoveNext
End Sub
RESULT
Thus the project to develop E-Ticketing system using Rational Rose Software and to
implement the project in Visual Basic is done successfully.
Ex No: 7 SOFTWARE PERSONNEL MANAGEMENT SYSTEM
DATE:
AIM
To develop a project software personnel management system using the Rational
Rose Software from the UML diagram and to implement the software in Visual Basic.
PROJECT ANALYSIS AND PROJECT PLANNING
The software personnel management system is used to manage our personnel
things such as maintaining databases in offices etc. this project is easy for the CEO to
handle the details. This is personally used for CEO.
PROBLEM STATEMENT
The CEO must enter the name and password to login the form and select the
particular employee to view the details about that employee and maintaining the
employee details personally. This process of software personnel management system are
described sequentially through following steps,
• The CEO login to the software personnel management system.
• He/she search for the list of employees.
• Then select the particular employee.
• Then view the details of that employee.
• After displaying the employee details then logout.
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION
1.1 Purpose
The main purpose of creating the document about the software is to know
about the list of requirements that is to be developed.
1.2 Scope:
It specifies the requirements to develop a processing software part that complete
the set of requirements. In this specification, we define about the system requirements that
are apart from the functionality of system
1.3 References
IEEE Software Requirements Specification format
1.4 Technology to Be Used
Microsoft Visual Basic 6.0
1.5 Tools Be Used
Rational Rose 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.
OVERALL DESCRIPTION
2.1 Product Perspective
The SPMP acts as an interface between the user and the database. This tries to
handle the personnel databases easily.
2.2 Functionality:
Many members of the process live to check for the occurrence and transaction,
we all have to carry over at some time.
2.3 Usability
The User interface makes the software personnel management System to be
efficient.
2.4 Performance
It is the capability about which it can perform function for many users at the same
time for the efficiency (i.e.) without any error occurrences.
2.5 Reliability
The system should be able to the user through the day to day transactions.
2.6 Assumptions and dependencies
The user must have the basic knowledge of computer and English language.
The user must correctly login the database
UML DIAGRAMS
The following UML diagrams describe the process involved in the online
recruitment system
USE CASE DIAGRAM
The use cases are a set of scenarios to guide together by a common user goal. A scenario is
the sequence of steps describing an interaction between a user and their system.
List of employee Login CEO Employee details Database

DOCUMENTATION OF USE CASE DIAGRAM

The use case diagram in the software personnel management system illustrates the sequence
of sequencing and describing an interaction between a CEO and a system.
Employee details:
The CEO can able to view the details of the employee using this use case.
CLASS DIAGRAM
The Class diagram the types of object in the system a various kinds of static relationships
that exists among them.

DOCUMENTATION OF CLASS DIAGRAM

The Classes used in this project are
CEO: The CEO has to login the form by specifying the name and password of him.
Database: The database checks whether the CEO has given the name and password
accordingly if not the error message will be displayed.
Available employees: The database is connects to the list of available employees and the
CEO if wants then select the employee from it.
SEQUENCE DIAGRAM:
It is a kind of interaction diagram in which an object is shown as a box at the top
of the dash vertical line. This vertical line is called object life time. The life time represent
the object’s life during interaction object deletion is shown with a large x.
DOCUMENTATION OF SEQUENCE DIAGRAM
The CEO must enter his name and password to login the software personnel
management system. The verification process is undergone by the database. If the details
are correct he can enter to the system otherwise error is displayed. After login the
details of the particular employee is viewed by the CEO. Finally he is logged out from the
system.

COLLABORATION DIAGRAM
In a collaboration diagram object are shown as icons as on. A collaboration
diagram arrow indicates the message send within the given use case. The sequence is
indicated by numbering the messages.
DOCUMENTATION OF COLLABORATION DIAGRAM
It is same as the sequence diagram that involves the object of the project
with the only differences that we give the sequence no to the each process. The CEO must
enter his name and password to login the software personnel management system. The
verification process is undergone by the database .If the details are correct he can enter to
the system otherwise error is displayed. After login the detail of the particular
employee is viewed by the CEO. Finally he is logged out from the system.
STATE CHART DIAGRAM
It is a technique to describe the behavior of the system. It determines all the
possible states as that of particular object gets into the object oriented technique.
State diagrams are drawn for a single class so status to the lifetime behavior of a single
objector.

DOCUMENTATION OF THE STATE CHART DIAGRAM:

The various states are the login, lists of employees, selects an employee,
display the information about the employee, logout. The state chart diagram describes
the behavior of the system. The main purpose of the system is to maintain an
employee details personally. For that the CEO Login to the employee
management system. He/she selects a particular employee from the list of available
employee. The CEO has to view the details of the particular employee by clicking
the respective button. The CEO views the details then finally he is logout from the
system.
ACTIVITY DIAGRAM
The Activity diagram describes the sequencing of activity will support for both
conditional and parallel. An activity is a variant of state diagram.

DOCUMENTATION OF ACTIVITY DIAGRAM

The CEO Logins to the software personnel management system. He/she selects a
particular employee from the list of available employee. The CEO can view the details of
the particular employee by clicking the respective button. After viewing the details he is
logout from the system.
PACKAGE DIAGRAM
A package is represented as folder among shown as large rectangle with a tab
attached its upper left corner. A package may contain both subordinated package both
ordinary model can be organized into packages. There are three types of layers,
a. User interface layer
b. Domain layer
c. Technical layer
DOCUMENTATION OF PACKAGE DIAGRAM
The three layers in the online recruitment system are
The User interface layer - consists of the web and login. This layer describes how the
applicant logins to the website and apply for the job.
 The Domain layer - shows the activities that are performed in the online recruitment
system. The activities are register, attend test and select talented applicant.
The Technical service layer - the applicant details, verification details and the selected
applicant details are stored in the database.

COMPONENT DIAGRAM
Components are a slightly fuzzy concept in the UML, because both classes and
components can be used to model the same thing. A component represents a modular part
of a system that encapsulates its contents and whose manifestation is replaceable within
its environment .A component defines its behavior in terms of provided and required
interfaces. As such, a component serves as a type, whose conformance is defined by
these provided and required interfaces.

DOCUMENTATION OF COMPONENT DIAGRAM

In this diagram there link between the actors is present in the SPMS that could be
shown in diagrammatically way in the component diagram. Each every actor is having a
directional link to process further details present in the system.
DEPLOYMENT DIAGRAM
A deployment diagram shows the assignment of concrete software artifacts (such as
executable files) to computational nodes (something with processing services). It shows
the deployment of software elements to the physical architecture and the communication
(usually on a network) between physical elements.
A deployment diagram usually shows an example set of instances (rather than classes)

FORMS
SOURCE CODE
Class modulesCEO
Option Explicit '##ModelId=4D413303009C
Private name As Variant
'##ModelId=4D41330502BF
Private Emp_no As Variant'##ModelId=4D41330E01F4
Private DOB As Variant'##ModelId=4D413434035B
Public NewProperty As database'##ModelId=4D413322005D
Public Sub view()
End Sub '##ModelId=4D41410F01B5
Public Sub update()
End Sub '##ModelId=4D41411401C5
Public Sub login()End Sub EMPLOYEE
Option Explicit '##ModelId=4D41409D0399
Private name As Variant'##ModelId=4D4140A400EA
Private DOB As Variant'##ModelId=4D4140B10290
Private salary As Variant
'##ModelId=4D4140B801C5
Private exp As Variant'##ModelId=4D4140BC01F4
Private ph_no As Variant'##ModelId=4D4140E8007D
Public NewProperty As databaseDATABASE:
Option Explicit ##ModelId=4D41334C02FD
Private pruducts As Variant'##ModelId=4D41414000EA
Private projects As Variant'##ModelId=4D4134380196
Public NewProperty As database_admin'##ModelId=4D4140F00290
Public NewProperty2 As employee'##ModelId=4D4133930271
Public Sub store_data()
End Sub '##ModelId=4D4133A00271
Public Sub update()
End Sub '##ModelId=4D4133A601A5
Public Sub insert()
End Sub '##ModelId=4D41414A032C
Public Sub enquiry()
End Sub '##ModelId=4D4133AC00BB
Public Sub delete()End Sub
'##ModelId=4D4133AF002E
Public Sub verify()
End Sub '##ModelId=4D4133B2034B
Public Sub display()End Sub
FORMS
Form 1:
If Form1.Text1.Text = "admin" And Form1.Text2.Text = "admin" Then MsgBox "login
successful"
Form1.Hide Form2.ShowElse
MsgBox "invalid password"End If
Dim v1 As CEO1
Private Sub command1_Click ()
Set v1 = New CEO1v1.login
End SubForm 2:
If (Form2.Combo1.Text = "rahul") ThenForm2.Hide
Form3.ShowEnd If
If (Form2.Combo1.Text = "ram") ThenForm2.Hide
Form4.Show
End If
If (Form2.Combo1.Text = "Kelli") ThenForm2.Hide
Form5.ShowEnd If
If (Form2.Combo1.Text = "Sam") ThenForm2.Hide
Form6.ShowEnd If
Dim v2 As database
Private Sub command1_Click ()
Set v2 = New databasev2.display
End SubForm 3:
Private Sub command1_Click ()Form3.Hide
Form2.ShowEnd Sub Form 4:
Private Sub command1_Click ()Form4.Hide
Form2.ShowEnd Sub Form 5:
Private Sub command1_Click ()Form5.Hide
Form2.ShowEnd Sub Form 6:
Private Sub command1_Click ()
Form6.Hide
Form2.Show
RESULT
Thus the project is to develop a SOFTWARE PERSONNEL
MANAGEMENTSYSTEM using the Rational Rose Software from the UML diagram and
to implement the employee details and successfully executed using visual basic and
rational rose.
Ex No: 8 CREDIT CARD PROCESSING SYSTEM
DATE:
AIM
To develop a project credit card system using the Rational Rose Software from the
UML diagram and to implement the software in Visual Basic
PROBLEM ANALYSIS AND PROJECT PLANNING
The Credit Card Processing System which is use to purchasing an item from any
shop mall, and it is used to maintain the limitation of credit card balance and current
transaction process could be update via credit card machine. This project mainly used for
large amount of item can be easy to buy from anywhere and required transaction
process should be maintained them.
PROBLEM STATEMENT
The customer should select the item to be purchase from the shop by using credit
card payment then the vendor should give a bill for the selected item .The customer
should give his card to swap and request for the kind of amount transaction. After
processing the transaction, the CREDIT CARD MACHINE should give the balance
print statement or receipt. Customer should select the item from the shop.
• Vendor makes the bill for the selected item.
• Customer gives the credit card to the vendor to swap the card.
• They required amount transaction is done by the card reader.
• Vendor will issue the balance statement to the customer.
• Customers put the signature in the receipt and return to the vendor.
SOFTWARE REQUIREMENT SPECIFICATION
2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The CCP acts as an interface between the 'Customer' and the 'Card Reader'. This
system tries to make the transaction as simple as possible and at the same time not risking
the security of data transaction process. This minimizes the time
duration in which the user receives the item.
2.2 FUNCTIONALITY
Many members of the process lives to checking for the occurrence and transaction
we all have to carry over sometimes user interface to make the transaction to be efficient.
2.3 USABILITY
The User interface makes the Credit Card Processing System to be efficient.
2.4 PERFORMANCE
It is of the capacities about which it can perform function for many users at the
sometimes efficiently that are without any error occurrence.
2.5 RELIABILITY
The system should be able to process the user for their corresponding request.
2.6 ASSUMPTION AND DEPENDENCIES
The Vendor and Customer must have basic knowledge of computers and English
Language. The vendor may be required to deliver the item purchased by the customer.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online
recruitment system
USE CASE DIAGRAM
The use cases are a set of scenarios to guide together by a common user goal. A
scenario is the sequence of steps describing an interaction between a user and their system.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are customer, vendor and card reader. The
use cases are the activities performed by actors.
The actors in this use case diagram are
• Customer - used to purchase some item from the shop by using credit card payment.
• Vendor - used to issue a bill for selected item and verify the card holder signature and
Then delivery the item.
• Card reader - its make the amount transaction for required credit card and print
the balance statement.
The use cases in this use case diagram are
Purchase item - customer enters the shop to purchase some item by using credit card payment.
• Bill issue - vendor will make a bill for the selected item.
• Swap the card - vendor will swap the card.
• Make transaction- card reader will processes the amount transaction.
• Print the statement - after the transaction, balance amount should be printed.
• Signature - customer should put the signature and give it to vendor.
• Deliver the item-vendor issued to deliver a item.
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.

DOCUMENTATION OF ACTIVITY DIAGRAM

The customer’s activity should contained an purchase item by using credit card
and then his referred to check the current transaction processing its completed or
not. The vendor should issue a bill copy to the customer and its swap the card to make
amount transaction by using card reader. The vendor should give required statement to
customer will deliver the item from the shop.
CLASS DIAGRAM
The Class diagram the types of object in the system a various kinds of static
relationships that exists among them.

DOCUMENTATION OF CLASS DIAGRAM

The Classes used in this project are:
• Customer - is the class name. Its attributes are name, age, signature, and card number. The
operations performed in the customer class are purchase item and swap the credit card.
• Vendor - is the class name. Its attributes are name, address, and phone number.The
operations performed are making bill and then delivered item purchased by the customer.
• Card Reader - is the class name. Its attributes are machine number, software and company.
The operations performed are making the transaction and print balance statement.

SEQUENCE DIAGRAM
It is a kind of interaction diagram in which an object is shown as a box at the top of
the dash vertical line. This vertical line is called object life time. The life time represent the
object’s life during interaction object deletion is shown with a large x.
DOCUMENTATION OF SEQUENCE DIAGRAM
The customer wants to purchase some item from the shop; Vendor makes a bill
for the selected item. The Customer gives the credit card to the vendor to the swap the
card. The further transaction is proceeding for if the credit card is validated. Vendor will
issue the required balance statement to the customer. Customer put the signature in the
receipt and returns the one copy of statement to the vendor.
COLLABORATION DIAGRAM
In a collaboration diagram object are shown as icons as on. A collaboration diagram
arrow indicates the message send within the given use case. The sequence is indicated by
numbering the messages
DOCUMENTAION OF COLLABORATION DIAGRAM
In this diagram there is sequence of ordered relationship should performing in the
CCP, then Customer will performed a selecting item, putting signature, and deliver the
item, Vendor should perform the swap the card, issue the statement and Card reader
should perform amount transaction and print the balance statement.
STATECHART DIAGRAM
It is a familiar technique to describe the behavior of the system. Events involve
in the state chart diagram a purchase, make transaction, delivery the item.
DOCUMENTAION OF STATECHART DIAGRAM
The Entire process of CCP could be shown in the start state to goal state behavior
should be performed by the Customer, Vendor and Card reader in this credit card
processing system.

PACKAGE DIAGRAM
A package is represented as folder among shown as large rectangle with a tab
attached its upper left corner. A package may contain both subordinated package both
ordinary model can be organized into packages.
There are three types of layers includes in package diagram:
• User interface layer
• Domain layer
• Technical layer
DOCUMENTATION OF PACKAGE DIAGRAM
The three layers in the credit card processing system are
The User interface layer - consists of the Card reader and Vendor. This layer describes how
the customer is used to purchasing and makes it transaction process.
• The Domain layer - shows the activities that are performed in the Credit card processing
system. The activities are purchase the item, make transaction and delivered item.
• The Technical service layer - To verify a required Customer Signature.

COMPONENT DIAGRAM
The component diagram is represented by figure dependency and it is a graphof
design of figure dependency.
DOCUMENTATION OF COMPONENT DIAGRAM
In this diagram there link between the actors is present in the CCP that could be
shown in diagrammatically way in the component diagram. Each every actor is having a
bidirectional link to process further details present in the system.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It
is represented by 3-dimentional box. Dependencies are represented by communication
association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the credit card processing system which is
the main part and the devices are the purchase item, swap the card, make transaction,
verify signature, delivery item which are the some of the main activities performed in the
system.
FORMS:

SOURCE CODE
'##ModelId=4D4136130261
Private machine number As Variant'##ModelId=4D413619031C
Private software As Variant'##ModelId=4D4136680177
Private company_name As VariantDim v1 As vendors '##ModelId=4D4136B6030D
'##ModelId=4D4136CB0222
Public Sub
print_receipt()End Sub
CUSTOMERS:
Option Explicit '##ModelId=4D4134EC01E4
Private name As Variant'##ModelId=4D4134EF0167
Private age As Variant'##ModelId=4D413504036B
Private signature As Variant'##ModelId=4D413519007D
Private card_number As Variant
'##ModelId=4D4136D9037A
 Public NewProperty As vendorsDim v1 As vendors
'##ModelId=4D4135250167 '##ModelId=4D41353E02AF
Public Sub swap()End Sub VENDORS:
Option Explicit '##ModelId=4D4135610399
Private name As Variant '##ModelId=4D413565000F
Private address As Variant '##ModelId=4D41356F0203
Private machine_num As Variant'##ModelId=4D4136E200EA
Public NewProperty As card_readerDim v2 As card_reader
'##ModelId=4D4135BA03A9
Public Sub make_bill()Form3.Show
End Sub'##ModelId=4D4135CA029F
Public Sub delivery_item()Form3.Show
End SubForm1:
Dim r1 As customers
Private Sub Command1_Click()
Set r1 = New customersr1.purchase_item
End Sub
Private Sub Command2_Click()Unload Me
End Sub
Public Sub purchase_item()Form2.Show
End Sub

RESULT
Thus the project to develop credit card processing system using Rational Rose
Software and to implement the project in Visual Basic is done successfully.
Ex No: 9 E-BOOK MANAGEMENT SYSTEM
DATE:
AIM
To develop a project E-Book Management system using Rational Rose Software
and to implement the software in Java.
PROBLEM ANALYSIS AND PROJECT PLANNING
E-book Management System gives an idea about how books are maintained in the
particular websites. The books that are to be purchased, the books that are to be sold
are maintained here. Further some additional details of the current books that is available
in the store are also given. EBook Management System in this project is done in an
authorized way. The password and user id has been set here.
PROBLEM STATEMENT
The website has to be maintained properly since the whole eBook purchase process
can be improved. EBook management in this project gives the idea about how eBooks
are maintained in a particular concern. The book details which includes the number of
books available, no of pages and price. EBook management system the EBook
management in this project is understood by going through the modules that is being
involved.
SOFTWARE REQUIREMENT
SPECIFICATIONINTRODUCTION
E- Book management gives an idea about how eBooks are maintained in the
particular concern. The eBooks that are to be purchased, the eBooks that are to be sold
are maintained here. Further some additional details of the current eBook list that is
available in the website are also given. EBook management in this project is done in an
authorized way.
OBJECTIVE
The main objective of this project is to overcome the work load and time
consumption which makes the maintenance of the eBook in an organization as a tedious
process. This project provides complete information about the details of the eBook to the
customers. This project identifies the amount of book available. Separate modules have
been created for purchasing, viewing book details, and delivery details.
OVERVIEW
The overview of the project is to Storing of information about the eBooks and
updating the eBooks list for each organization which is using this system, keeps track of
all the information about the eBooks purchased that are made by the customers, having
registration feature of adding up new customers to the organization are provided in this
system.
PURPOSE
The purpose of eBooks management system is to store and sell the books
in a website effectively.
SCOPE
The scope of this eBooks management is to maintain the book details after the
purchase and list of reaming books available in the same book type.
FUNCTIONALITY
The main functionality of eBooks maintenance system is to store and sell eBooks
for a website.
USABILITY
User interface makes the eBook management system to be efficient. That is the
system will help the admin to maintain stock details easily and helps the store to handle
the stocks effectively. The system should be user friendly.
PERFORMANCE
It describes the capability of the system to perform the eBook management system
of the store without any error and performing it efficiently.
RELIABILITY
The eBook management system should be able to serve the customer with correct
information and day-to-day update of eBooks list details.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the website which maintains eBooks in online database.
UML DIAGRAMS
The following UML diagrams describe the process involved in the stock maintenance system
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse. Actor is any external entity that makes
use of the system being modeled. It is represented using stick figure.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are Supplier, Store Keeper and Database. The
use cases are the activities performed by actors.
• The website will give the books available.
• Customer will login and check the list of eBooks in the database.
• The database will be updated according to the purchase done and it will be up to date.
The use cases in the use case diagram are Quotation & Purchase,
login, stock, purchase.
• Select books will gives us the status of the purchasing order details
• Login will gives us the entry for the customer of this project.
• Database will gives us the details about the total eBooks available.
• Purchase will gives us the details about the details and the history of eBooks purchased.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's
classes, their attributes, and the relationships between the classes. It is represented
using a rectangle with three compartments. Top compartment have the class name,
middle compartment the attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has three classes’ applicant, recruiter and database.
• Customer - is the class name. Its attributes are name, address and cont. no. The
operations performed in the Supplier class are get order, supply goods and get money.
• Books - is the class name. Its attributes are operating system,
Computer architecture, DBMS, web technology and OOAD. The operations performed
are select and buy.
• Database - is the class name. Its attribute is operation. The operations performed are store.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
• The Customer enters the EBook website.
• The list of books available is listed.
• Customer checks the book list.
• Database provides user id and pass.
• Customer selects the book.
• Pay money to the Website.
COLLABORATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram into
a sequence diagram and the vice versa. A collaboration diagram resembles a flowchart
that portrays the roles, functionality and behavior of individual objects as well as the
overall operation of the system in real time

DOCUMENTATION OF COLLABORATION DIAGRAM

The first collaboration diagram is to show how the customer login and getting
details of eBooks in the eBooks management system. Here the sequence is numbered
according to the flow of execution.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round
box, which may contain one or more compartments. An initial state is represented as
small dot. A final state is represented as circle surrounding a small dot.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
• First state is login where the customer login to the eBooks management system.
• Then select buy the book.
• Enter the account detail and purchase the book.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and operational
step-by-step workflows of components in a system. An activity diagram shows the
overall flow of control. An activity is shown as a rounded box containing the name of the
operation.
The next state is checking the list of books in order.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in recruitment system.
• First Customer login then checks books available.
• The book list is verified and is given in an ordered format.
• The needed book is selected.
• Enter your account details and purchase the book.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is online recruitment systems.
And Supplier, storekeeper and database are the components come under the main
component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show
"the allocation of artifacts to nodes according to the Deployments defined between
them. It is represented by 3-dimentional box. Dependencies are represented by
communication association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this deployment diagram is the online recruitment system
which is the main part and the devices are the select and payment which are the some
of the main activities performed in the system.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies
are represented by communication association.
 PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies between
the packages that make up a model. A Package Diagram (PD) shows a grouping of
elements in the OO model, and is a Cradle extension to UML.PDs can be used to show
groups of classes in Class Diagrams (CDs), groups of components or processes in
Component Diagrams (CPDs), or groups of processors in Deployment Diagrams
(DPDs).
There are three types of layer. They are
• User interface layer: consists of the form and login. This layer describes how the
customer logins and books maintained in website.
• Domain layer: shows the activities that are performed in the eBooks management
system. The activities are books are purchased from the website
• Technical services layer: the update the account details and buy the book bypayment
through the account
FORMS

SOURCE CODE
Option Explicit '##ModelId=4D63700C0148
Private name As Variant'##ModelId=4D63701003C8
Private address As Variant
'##ModelId=4D637016007D
Private contact_no As Variant
'##ModelId=4D637027031C
Private account_no As Variant'##ModelId=4D63714C02BF
Public NewProperty As books'##ModelId=4D63715201C5
Public NewProperty2 As Database'##ModelId=4D63706000BB
Public Sub login()End Sub
Private Sub Command1_Click()
If Text1.Text = "pandi" And Text2.Text ="**" Then MsgBox "login sucessfully" Form2.Show
Else
MsgBox "invalid password"End If
End Sub
Private Sub Command2_Click()Unload Me
End SubBOOK FORM2
Option Explicit
'##ModelId=4D63709803C8
Private operating_system As Variant'##ModelId=4D6370AA008C
Private computer_architecture As Variant'##ModelId=4D6370B30138
Private dbms As Variant '##ModelId=4D6370B603C8
Private web_technology As Variant'##ModelId=4D6370C0034B
Private ooad As Variant'##ModelId=4D6370C50167
'##ModelId=4D6370650213
Public Sub payment()End Sub
Public Sub select()
End Sub '##ModelId=4D6370D0000F
Public Sub buy()End Sub
Private Sub Command1_Click()Form3.Show
End Sub
Private Sub Command2_Click()Form3.Show
End Sub
Private Sub Command3_Click()Form3.Show
End Sub
Private Sub Command4_Click()Form3.Show
End Sub
Private Sub Label2_Click()End Sub
FORM3
Private Sub Command1_Click()Form4.Show
End Sub

RESULT
Thus the project to develop EBook Management System using Rational Rose
Software and to implement the software in Java is done successfully.
Ex No: 10 ONLINE RECRUITMENT SYSTEM
DATE:
AIM
To develop a project on online recruitment system using Rational Rose Software
and to implement the project in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
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
This software specification documents full set of features and function for online
recruitment system that is performed in company website. In this we give specification
about the system requirements that are apart from the functionality of the system to
perform the recruitment of the jobseekers. It tells the usability, reliability defined in use
case specification.
OBJECTIVE
The main objective of Online Recruitment System is to make applicants register
Themselves online and apply for job and attend the exam. Online Recruitment System
provides online help to the users all over the world.
OVERVIEW
The overview of the project is to design an online tool for the recruitment process
which eases the work for the applicant as well as the companies. Companies can create
their company forms according to their wish in which the applicant can register.
USABILITY
User interface makes the Recruitment system to be efficient. That is the
system will help the applicant to register easily and helps the companies to recruit the
applicant effectively. The system should be user friendly.
PERFORMANCE
It describes the capability of the system to perform the recruitment process of the
applicant without any error and performing it efficiently.
RELIABILITY
The online recruitment system should be able to serve the applicant with correct
information and day-to-day update of information.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the system. That is
the services that are provided to the applicant who apply for the job.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment system
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse. Actor is any external entity that makes use
of the system being modeled. It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are applicant, recruiter and database. The use
cases are the activities performed by actors.
The actors in this use case diagram are
• Applicant - logins the recruitment system and register for the job and attend the
test conducted at some venue.
• Recruiter - send the interview details, select talented applicant and send appointment
letter to them.
Databases - verify the login and register details and selected applicant details are stored init.
The use cases in this use case diagram are
• Login - applicant enter their username and password to enter in to the recruitment system
• Register - applicant register in to the recruitment system for job.
• Send interview details - recruiter send interview details to the applicant.
• Attend test - applicant appears for the test.
• Select talented applicant - based on the outcome of test talented applicant is selected.
• Send appointment letter - appointment letter is sent to the selected applicant by recruiter
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's classes,
their attributes, and the relationships between the classes. It is represented using a
rectangle with three compartments. Top compartment have the class name, middle
compartment the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has three classes’ applicant, recruiter and database.
• Applicant - is the class name. Its attributes are username, password, name, phone no and
address. The operations performed in the applicant class are login, register and giving
applicant details.
• Recruiter - is the class name. Its attributes are name, designation, phone no, marks in
apps and marks in technical. The operations performed are selecting applicants based on
apps and technical.
• Database - is the class name. The operations performed are storing applicant details,
verifying login and storing selected applicant details.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM

REGISTER
This sequence diagram describes the sequence of steps to show
• The applicant login in to the recruitment system and register for job.
• The verification done in the database and recruiter
• The interview details are sending to the applicant by recruiter.
SELECTING APPLICANT
This sequence diagram shows steps to show
• The applicant attend aptitude test and they are short listed based on evaluation
• The applicant appear for technical round
• The talented applicant is selected.
• This detail is stored in the database
COLLABRATION DIAGRAM

A collaboration diagram, also called a communication diagram or interaction

diagram. A sophisticated modeling tool can easily convert a collaboration diagram into
a sequence diagram and the vice versa. A collaboration diagram resembles a flowchart
that portrays the roles, functionality and behavior of individual objects as well as the
overall operation of the system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM REGISTER
FOR REGISTER
This collaboration diagram is to show how the applicant login and register in the
recruitment system. Here the sequence is numbered according to the flow of execution.
SELECTING APPLICANT
This collaboration diagram is to show the selection process of the applicant for
the job. The flow of execution of this selection process is represented using the numbers.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round
box, which may contain one or more compartments. An initial state is represented as
small dot. A final state is represented as circle surrounding a small dot.
DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behavior of the system.
• First state is login where the applicant login to the recruitment system.
• The next state is register where the applicant registers for job.
• Then verify the applicant details and sent interview details.
• The applicant appears for test.
• Update database with details of selected applicant.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In
The

Unified Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as a rounded box containing the
name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in recruitment system.
• First the applicant login then registers.
• The applicant details are verified and interview details are sending to applicant by recruiter.
• Applicants appear for test.
• Recruiter select talented applicant.
• Update the selected applicant details in the database.
COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies are
represented by communication association.

DOCUMENTATION OF COMPONENT DIAGRAM

The main component in this component diagram is online recruitment systems.
And register, attend test and select talented applicants are the components comes under
the main component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimensional box. Dependencies are represented by communication
association.
 DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the online recruitment system which
is the main part and the devices are the register, appear for test and select talented
applicant which are the some of the main activities performed in the system.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a grouping
of elements in the OO model, and is a Cradle extension to UML. PDs can be used to
show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).There are three types of layer. They are
• User interface layer - software objects representing domain concepts that fulfill
application requirements, such as calculation a sale total.
• Domain layer - layer that contains domain objects to handle application logic work.
Technical services layer - general purpose objects and subsystems that provide supporting
technical services, such as interfacing with a database or error logging.
DOCUMENTATION OF PACKAGE DIAGRAM
The three layers in the online recruitment system are
• The User interface layer - consists of the web and login. This layer describes how
the applicant logins to the website and apply for the job.
• The Domain layer - shows the activities that are performed in the online recruitment
system. The activities are register, attend test and select talented applicant.
• The Technical service layer - the applicant details, verification details and the
selected applicant details are stored in the database.
FORMS
SOURCE CODE Private Phoneno As Integer
APPLICANT Private Marks_in_Aps As Integer
Option Explicit Private Marks_in_tech As Integer
'##ModelId=4D5CED1B0324 Public NewProperty22 As database1
Private UserName As String Public NewProperty2 As applicant1
'##ModelId=4D5CED1B0325 Public Sub Aps_test()
Private Password As String End Sub
'##ModelId=4D5CED1B0326 Public Sub
Private Phoneno As Integer Aps1_test()End Sub
'##ModelId=4D5CED1B0327 Public Sub
Private Address As String Tech_Round()End Sub
'##ModelId=4D5CED1B0328 Public Sub
Private Name As String Tech1_Round()End Sub
'##ModelId=4D5CED1B0313 Database1
Public NewProperty As database1 Option
'##ModelId=4D5CED1B032B Explicit
Public NewProperty2 As applicant1 Public NewProperty As database1
'##ModelId=4D5CED1B0321 Public NewProperty22 As database1
Public Sub register() Public Sub apps_details()
End Sub End Sub
'##ModelId=4D5CED1B0322 Public Sub
Public Sub login() tech_details()End Sub
End Sub Public Sub
'##ModelId=4D5CED1B0323 selected_applicant_details()
Public Sub applicant_details() End Sub
End Sub FORM1
Recruiter1 Option Private Sub Command1_Click()
Explicit Dim obj1 As applicant1
Private Name As String Set obj1 = New applicant1
Private Designation As String obj1.login
End Sub
Public Sub login() ElseIf Form3.Text4.Text = "" Then
If Form1.Text1.Text = "recruit" And MsgBox "Enter the
Form1.Text2.Text = "recruit" Then Educationalqualification"
MsgBox "login successfully" ElseIf Form3.Text5.Text = "" Then
Form2.Show MsgBox "Enter the Percentage"
Else End If
MsgBox "invalid password" If Val(Form3.Text5.Text) < 75 Then
End If MsgBox "you are not up to
End Sub thequalification.you are
FORM2 not registered"Else
Private Sub Command1_Click()Dim MsgBox "you are registered
obj2 As applicant1 successfully"Form4.Show
Set obj2 = New applicant1 obj2.register End
End Sub If
Public Sub register() End
Form3.Show Sub
End Sub FOR
FORM3 M4
Private Sub Command1_Click()Dim Private Sub
obj3 As applicant1 Command1_Click()Dim
Set obj3 = New applicant1 obj4 As recruiter1
obj3.applicant_details Set obj4 = New
End Sub recruiter1obj4.Aps_test
Public Sub applicant_details() End Sub
If Form3.Text1.Text = "" Then MsgBox Private Sub
"Enter the name" Form_Load()Dimobj5
ElseIf Form3.Text2.Text = "" Then As database1 Set
MsgBox "Enter the Address" ElseIf obj5 = New database1
Form3.Text3.Text = "" Then obj5.apps_details
MsgBox "Enter the Phoneno" End Sub
Public Sub
 Aps_test() End Sub
Form5.Show Public Sub tech_details()
End Sub Form5.Adodc1.ConnectionString0=
Public Sub apps_details () "Provider=Microsoft.Jet.OLEDB.4.0;Data
Set Form4.DataGrid1.DataSource = Source=C:\Documents
Form4.Adodc1 End Sub And Settings\Student\My
FORM5 Documents\recu1.mdb;Persist Security
Private Sub Command1_Click()Dim Info=False"
obj6 As recruiter1 Form5.Adodc1.RecordSource = "select * from
Set obj6 = New recruiter1 obj6.Aps1_test suk_query"
End Sub Set Form5.DataGrid1.DataSource =
Private Sub Form_Load() Form5.Adodc1
Dim obj7 As database1 End Sub
Set obj7 = New database1 obj7.tech
_details
End Sub
Public Sub Aps1_test()
Form6.Show

RESULT
Thus the project to develop online recruitment system using Rational Rose
Software and to implement the project in Visual Basic is done successfully.
Ex No: 11 FOREIGN TRADING SYSTEM
DATE:
AIM
To design a project Foreign Trading System using Rational Rose Software and to
implement the software in Visual Basic
PROJECT ANALYSIS AND PROJECT PLANNING
The initial requirements to develop the project about the mechanism of the Foreign
Trading System are bought from the trader. The requirements are analyzed and refined
which enables the analyst (administrator) to efficiently use the Foreign Trading
System. The complete project analysis is developed after the whole project analysis
explaining about the scope and the project statement is prepared.
PROBLEM STATEMENT
The steps involved in Foreign Trading System are:
• The forex system begins its process by getting the username and password from the trader.
• After the authorization permitted by the administrator, the trader is allowed to perform
the sourcing to know about the commodity details.
• After the required commodities are chosen, the trader places the order.
• The administrator checks for the availability for the required commodities and updates it
in the database.
• After the commodities are ready for the trade, the trader pays the amount to
the administrator.
• The administrator in turn provides the bill by receiving the amount and updates it in
the database.
• The trader logouts after the confirmation message has been received.
SOFTWARE REQUIREMENT SPECIFICATION
INTRODUCTION
International trade is exchange of capital, goods, and services across international
borders or territories. In most countries, it represents a significant share of gross
domestic product (GDP). While international trade has been present throughout much of
history (see Silk Road, Amber Road), it’s economic, social, and political importance
has been on the rise in recent centuries. Industrialization, advanced transportation,
Globalization, multinational corporations, and outsourcing are all having a major impact
on the international trade system. Increasing international trade is crucial to the
continuance of globalization. Without international trade, nations would be limited to the
goods and services produced within their own borders.
OBJECTIVE
The main objective of Foreign Trading System is to make the traders to do trading
process easily through online as the forex is open 24 hours a day.
OVERVIEW
The overview of the project is to design an online tool for the foreign trading
process and it oversees the implementation, administration and operations covered in
foreign trade.
GLOSSARY
The primary purpose of the forex is to assist international trade and investment, by
allowing businesses to convert one currency to another currency. That is, In a typical
foreign exchange transaction, a trader purchases a quantity of one currency by paying the
quantity of another currency.
SCOPE
They are a lot of advantages in Forex Trading as compared to many other financial
trading, like futures or stock trading. The Forex market is open 24 hour a day.
Being the market available 24 hours a day, this gives the trader to choose which time they
would like to trade. It requires only minimum beginning capital to start the Forex
trade. Forex Trading has outstanding liquidity as it never closes.
UML DIAGRAMS
The following UML diagrams describe the process involved in the foreign trading
system.
USE CASE DIAGRAM
A use case diagram purpose is to present a graphical overview of the functionality
provided by the system in terms of actors, their goals, and any dependencies between
those use cases. A use case is an interaction between users and a system in a particular
environment. It captures the goal of the users and the responsibility of the system to the
user. It is represented using ellipse. Actor is a user playing a role with respect to the
System. A single actor may perform many use cases. It is represented using a stick figure
along with a label.

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are trader, administrator and database. The use
cases are the activities that are represented in the ellipse. Trader logins the foreign trading
system and perform the sourcing to select the required commodities and places the
order. The administrator checks for ordered commodities, after the commodities are ready
trader pay the amount. The administrator provides the items along with the bill. The
database stores the all the details and updates it whenever there is a change in any part of
the trading process.
CLASS DIAGRAM
A class diagram is a type of static structure diagram that describes the structure of
a system. The classes in the class diagram represent both the main objects and or
interactions in the application. The class diagram is represented using rectangular boxes
each of which contains three parts:
• The upper part holds the name of the class.
• The middle part contains the attributes of the class.
• The bottom part gives the operations or methods the class undertakes.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram consists of four class trader, administrator, account and item.
• Trader-is the class name. It consists of username, password, account no as attributes.
The operations performed are login, sourcing, place order, pay and logout.
• Admin-is the class name. It consists of name, id as attributes. The operations performed
are bill and Trace order.
• Item-is the class name? It consists of name, id, availability and cost.
• Account-is the class name. It consists of account no, balance and due as attributes.
SEQUENCE DIAGRAM
A sequence diagram in unified modeling language is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. Sequence diagrams are sometimes called event diagrams, event
scenarios, and timing diagrams. This diagram shows parallel vertical lines called lifelines.
There are two dimensions in this diagram
1. Vertical dimension-represents time.
2. Horizontal dimension-represent different object
TraderTraderAdministratorAdministratorDatabaseDatabaseLoginSourcingPlace order
Update order Pay update account details bill logout.
DOCUMENTATION OF SEQUENCE DIAGRAM
The sequence diagram represents:
• The trader logins and performs the sourcing (viewing the availability and amount) to
select the required commodities.
• Trader places the order to the administrator then the admin tracks order and update
the details in the database.
• The bill is provided to the trader as per the viewed amount and the trader pays for it.
• The trader after receiving the commodities successfully logout from the database.
COLLABORATION DIAGRAM
A collaboration diagram belongs to a group of UML diagrams called Interaction
Diagrams, collaboration diagrams, like sequence diagrams, show how the objects
interact over the course of time. Collaboration diagrams show the sequence by numbering
the messages on the diagram.
DOCUMENTATION OF COLLABORATION DIAGRAM
The collaboration diagram shows how the trader performs the sourcing and places
order for which the administrator provides the bill and updates it in the database.
STATE CHART DIAGRAM
The state chart is used to model dynamic nature of a system. They define different
states of an object during its lifetime. And these states are changed by events. So these
diagrams are useful for reactive systems i.e.., a system that responds to external or
internal events. It describes the flow of control from one state to other state. The initial
state is represented using the small dot. The final state is represented using a circle
surrounded by a small dot

DOCUMENTATION OF STATE CHART DIAGRAM

The state diagram represents the following states.
• The trader logins the register in the first state and performs sourcing in the second
state. The trader places the order in the third state.
• The trader receives the bill in the fourth state and pays the required amount in fifth state.
• The trader logouts from the system in the sixth state
ACTIVITY DIAGRAM
This diagram represents the graphical representation of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. It shows the
overall flow of control.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram represents the flow of stepwise activities performed in
foreign trading system.
• The first action represents the trader logins to the system.
• The second action is the place where the trader places the order.
• The decision state is the state where the trader decides to place the order.
• If the trader places the order, fill the form for the required commodities.
• The next activity is that the administrator provides the bill for those commodities.
• The trader pays for the bill and logout from the system.
COMPONENT DIAGRAM

A component diagram depicts how the components are wired together to form larger
components and or software systems. Components are wired together by using an
assembly connector to connect the required interface of one component with the provided
interface of another component.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in the component diagram is foreign trading system. The
trader who comes to do the trading process and administrator who manages all the other
processes is the sub components.
DEPLOYMENT DIAGRAM
A deployment diagram models the physical deployment of artifacts on nodes.
The nodes appear as boxes, and the artifacts allocated to each node appear as rectangles
within the boxes. Nodes may have sub nodes, which appear as nested boxes.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

The processor in this diagram is the foreign trading system. The devices are the
trader and administrator who perform the main activities in the system.
PACKAGE DIAGRAM
A package diagram in the unified modeling language depicts the dependencies
between the packages that make up a model. It provides a way to group the elements.
There are three types of layers in package diagram.
User interface layer
The user interface layer may call upon its directly subordinate application logic
layer, and also upon elements of a lower technical service layer, for logging and so forth.
Domain layer
Software objects representing domain concepts (for example, a software class
administrator) that fulfill application requirements, such as tracing order and providing
the bill.
Technical services layer
General purpose objects and subsystems that provide supporting technical
services, such as interfacing with a database or error logging. These services are usually
Application independent.

DOCUMENTATION OF PACKAGE DIAGRAM

The three layers in the foreign trading system are
• User interface layer - consists of web and login. This layer describes how the trader
logins to the website and trades for the commodities.
• Domain layer - shows the activities that are performed inside the trading system.
The activities are place order, pay for the bill and logouts.
• Technical service layer - The sourcing and updating the details are performed in this layer.
FORMS
SOURCE CODE
ACCOUNT
Option Explicit '##ModelId=4D64958501F4
Private accoutno As Integer'##ModelId=4D64958E0186
Private balance As Integer'##ModelId=4D64959B0290
Private due As Integer '##ModelId=4D6612990290
Public Sub accountno()
MsgBox "your transaction is successfull"Form6.Show
End Sub '##ModelId=4D66130F0128
Public Sub accountpay()
MsgBox "your transaction failed. Do yourtrading again" Form5.Show
End Sub ADMINISTRATOR '##ModelId=4D6496030128
Public NewProperty As item'##ModelId=4D6CAE4001F4
Public Sub paybill2()
Form7.Text3.Text = Form7.Text3.Text -Form7.Text5.Text End Sub
'##ModelId=4D649563003E
Public Sub bill1()
Form4.Text1.Text = Form3.Text4.Text *Form3.Text5.Text Form4.ShowEnd Sub
'##ModelId=4D6CA397008C
Public Sub bill2()
Form8.Text1.Text = Form7.Text4.Text *Form7.Text5.Text Form8.Show
End Sub '##ModelId=4D64956F0399
Public Sub traceorder() Form5.Adodc1.ConnectionString=
"Provider=Microsoft.Jet.OLEDB.4.0;DataSource=C:\Documents and
Settings\Student\Desktop\datum\db.mdb;Persist Security Info=False"
Form5.Adodc1.RecordSource = "selectitemname from itemtable"
SetForm5.DataGrid1.DataSource =Form5.Adodc1
Form3.Text5.Text = ""
End Sub '##ModelId=4D6612B70186
Public Sub paybill1()
Form3.Text3.Text = Form3.Text3.Text -Form3.Text5.Text End Sub
ITEM
Private id As Integer '##ModelId=4D6495CA0251
Private rate As Integer'##ModelId=4D6495D103C8
Private available As Integer'##ModelId=4D6612C202CE
Public Sub getperfume() Form3.Text3.Text = Form3.Text3.Text -Form3.Text5.Text
 Form4.Show
End Sub '##ModelId=4D6612D30167
Public Sub getdoll()
Form7.Text3.Text = Form7.Text3.Text -Form7.Text5.Text Form8.Show
End Sub TRADER
'##ModelId=4D64952500BB
Public Sub login()
If Form1.Text1.Text = "ramya" AndForm1.Text2.Text = "ramya" ThenMsgBox "logined
successfully"
FORM4
Private Sub Command2_Click()Dim a5 As trader
Set a5 = New tradera5.pay
End Sub
Private Sub Form_Load()Dim a As administrator Set a =
New administrator
a.bill1 End Sub

.
.

RESULT
Thus the project to develop foreign trading system using Rational Rose software
and to implement the software in Visual Basic is done successfully
Ex No: 12 CONFERENCE MANAGEMENT SYSTEM
DATE:
AIM
To develop a project on Conference management system using Rational Rose
Software and to implement the project in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
The Conference Management System is an online website in which candidate can
submit the paper and register themselves and then attend the conference. The paper will
be reviewed. The details of the conference, date and time will be made available to them
through the website. After getting the confirmation details the candidate should submit
the revised and camera ready paper. Then the registration process will be done.
PROBLEM STATEMENT
The process of the candidates is to login the conference system and submit the
paper through online. Then the reviewer reviews the paper and sends the
acknowledgement to the candidate either paper selected or rejected. This process of
on conference management system are described sequentially through following steps
• The candidate login to the conference management system.
• The paper title is submitted.
• The paper is been reviewed by the reviewer.
• The reviewer sends acknowledgement to the candidate.
• Based on the selection, the best candidate is selected.
• Finally the candidate registers all details.
SOFTWARE REQUIREMENT
SPECIFICATIONINTRODUCTION
This software specification document consist full set of features and function for
online conference management system. In this we give specification about the system
requirements that are apart from the functionality of the system to perform the candidate
paper valuation. It tells the usability, reliability defined in use case specification.
OBJECTIVE
The main objective of Conference Management System is to accomplish paper
Submission online, update the presentation details and confirm registration. Conference
management system provides online help to the users all over the world.
OVERVIEW
The overview of the project is to design a process which eases the work for the
candidate as well as the reviewer. Candidate can easily submit the paper and go for
registration.
SCOPE
The scope of this conference management process is to select the best candidate
from the list of candidates based on their performance in the process.
FUNCTIONALITY
The main functionality of conference system is to select the candidate for the
presentation in conference.
USABILITY
The user interface to make the process should be effective that is the system will
help the candidates to register easily. The system should be user friendly.
PERFORMANCE
It describes the capability of the system to perform the conference process of the
candidate without any error and performing it efficiently.
RELIABILITY
The conference system should be able to serve the applicant with correct
information and day-to-day update of information.
FUNCTIONAL REQUIREMENTS
Functional requirements are those that refer to the functionality of the
system that is the services that are provided to the candidate who register for the
conference.
UML DIAGRAMS
The following UML diagrams describe the process involved in the conference management
system.
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
Particular goal. It is represented using ellipse. Actor is any external entity that makes use
of the system being modeled. It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are candidate, reviewer and database. The use
cases are the activities performed by actors.
The actors in this use case diagram are
• Candidate - Logins the conference system and submits the paper then do the
registration process.
• Reviewer - Review the paper, select best candidate and send acknowledgement to them.
• Databases - verify the login and register details and selected candidate details are stored
in. The use cases in this use case diagram are
• Login - Candidate enter their username and password to login to the conference
system. Paper submission - Candidate submits the paper.
• Review the paper- The paper is been reviewed by the reviewer and the paper is selected.
• Paper confirmation details - The reviewer can send the confirmation details to the candidate.
• Revised and camera ready paper - After the paper is selected and the camera ready
paper should be submitted to the reviewer by candidate.
• Registration - After submitting the revised paper the candidate wants to register.

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

This class diagram has three classes’ candidate, reviewer and database.
• Candidate - Its attributes are name, college name, department, paper title. The
operations performed in the candidate class are login, submit the paper, submit revised
and camera ready paper and registration.
• Reviewer - Its attributes are naming, department, reviewer ID. The operations
performed are review the paper and send the paper confirmation details.
• Database -The operations performed are storing candidate details and verifying login.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order.
It is a construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
SEQUENCE DIAGRAM FOR SUBMITTING PAPER
DOCUMENTATION OF SEQUENCE DIAGRAM LOGIN
This sequence diagram describes the sequence of steps to show
• The candidate login in to the conference system and register for job.
• The verification done in the database.
PAPER SUBMISSION
This sequence diagram shows steps to show
• The candidate submits the paper.
• The reviewer reviews the paper and sends acknowledgement to the candidate.
• The candidate submits revised and camera ready paper.
• This candidate will register their details.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram into
a sequence diagram and the vice versa. A collaboration diagram resembles a flowchart
that portrays the roles, functionality and behavior of individual objects as well as the
overall operation of the system in real time.

COLLABRATION DIAGRAM FOR LOGIN

DOCUMENTATION OF COLLABRATION DIAGRAMLOGIN
This collaboration diagram is to show how the applicant login in the conference
system. Here the sequence is numbered according to the flow of execution.
PAPER SUBMISSION
This collaboration diagram is to show the submitting paper process of the
candidate for the conference. The flow of execution of this selection process is
represented using the numbers.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved in
performing a method. It is also called as state diagram. A state is represented as a round
box, which may contain one or more compartments. An initial state is represented as
small dot. A final state is represented as circle surrounding a small dot.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
• First state is login where the candidate login to the conference system.
• The next state is submitting the paper.
• Then review the paper if it is selected the process will continue..
• The candidate should submit revised and camera ready paper.
• Then registration process will be carried out.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram shows
the overall flow of control. An activity is shown as a rounded box containing the name of
the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in recruitment system.
• First the candidate login to the database.
• Then the candidate should submit the paper.
• If it is selected the acknowledgement will send to the candidate.
• After submitting revised paper the registration process will be done.

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies are
represented by communication association.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is conference management
system. And submit the paper, review the paper and registration.

DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimensional box. Dependencies are represented by communication
association.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the conference management system
which is the main part and the devices are the candidate, appear for do conference,
reviewer will reviews paper, database will store all details which are the some of the main
activities performed in the system.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML. PDs can be
used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).
There are three types of layer. They are
• User interface layer - software objects representing domain concepts that fulfillapplication
requirements, such as calculation of a sale total.
• Domain layer - layer that contains domain objects to handle application logic work.
• Technical services layer - general purpose objects and subsystems that provide supporting
technical services, such as interfacing with a database or error logging.
DOCUMENTATION OF PACKAGE DIAGRAM
The three layers in the online recruitment system are
• The User interface layer - consists of the web and login. This layer describes how
the candidate login.
• The Domain layer - shows the activities that are performed in the conference management
system. The activities are paper submission, review paper, registration.
• The Technical service layer - the verification details and the selected candidate details
will stored into the database.
FORMS
SOURCE CODE '##ModelId=4598060A02BF
CANDIDATE Public Sub verify_the_ID()
Option Explicit End Sub
'##ModelId=459804B502EE '##ModelId=4598062A01F4
Private name As Variant Public Sub allow_to_the_reviewer()
'##ModelId=459804B902DE End Sub
Private college_name As Variant REVIEWER

'##ModelId=459804BF01C5
Private department As Variant'##ModelId=459804E40119
Private paper_title As Variant'##ModelId=45980653030D
Public NewProperty As reviewer1'##ModelId=45980507034B
Public Sub login()
End Sub '##ModelId=4598050E03D8
Public Sub submit_the_paper()
End Sub '##ModelId=4598051302FD
Public Sub
revised_and_camera_ready_paper_submission() End Sub '##ModelId=4598053F009C
Public Sub registration()End Sub
DATABASE
Option Explicit '##ModelId=459806A30280
Public NewProperty As candidate1
Option Explicit '##ModelId=45980565035B
Private reviewer_name As Variant'##ModelId=45980568036B
Private reviewer_department As Variant'##ModelId=459805920251
Private reviewer_ID As Variant'##ModelId=4598065C008C
Public NewProperty As database1'##ModelId=4598067E032C
Public NewProperty2 As database1'##ModelId=4598069501B5
Public NewProperty3 As database1'##ModelId=459805A10128
Public Sub review_the_paper()
End Sub '##ModelId=459805B0038A
Public Sub
sending_paper_confirmation_details()End Sub
FORM 1
Private Sub Command1_Click()Dim a As candidate1
Set a = New candidate1 Dim a As candidate1

Call a.login Set a = New candidate1

End Sub Call a.verify_the_ID
Private Sub Command2_Click() End Sub
Unload Me Public verify_the_ID()
End Sub Form2.Show

Public Sub login() End Sub

If Form1.Text1.Text = "rss" And FORM 3

Form1.Text2.Text = "rss" Then MsgBox Private Sub Command1_Click()

"login sucessfully!!!"
Form2.Show
Else
MsgBox "invalid username or password"
End If
End Sub
FORM 2
Private Sub Command1_Click() verify_the_IDEnd Sub
Dim a As database1 Public Sub
Set a = New verify_the_ID()
database1 Call a. Form2.Show

RESULT
Thus the project to develop conference management system using Rational Rose
Software and to implement the project in Visual Basic is done successfully.
Ex No: 13 BUSINESS PROCESS OUTSOURCING MANAGEMENT SYSTEM
DATE:
AIM
To develop a project Business process outsourcing (BPO) management system
Using Rational Rose software and to implement the software in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
Generally outsourcing can be defined as an organization entering into a contract
with another organization to operate and managed one or more of its business
processes. There are many problems faced by the BPO one among them is meeting
their targets and leaving the concern very often and switch to another company. In this
project we deal with the inbound system of the BPO. In inbound system the agent calls
the customer from his database to sell his product.
SOFTWARE REQUIREMENT
SPECIFICATIONINTRODUCTION
BPO is typically categorized into back office outsourcing-which includes internal
business functions such as human resources or finance and accounting, and front office
outsourcing which includes customer related services such as contact center services.
BPO that is contracted outside a company’s country is called offshore outsourcing. BPO
that is contracted to a company’s neighboring country is called near shore outsourcing.
Given the proximity of BPO to the information technology industry, it is categorized as an
information technology enabled service or ITES. Knowledge process outsourcing
(KPO) and legal process outsourcing (LPO) are some of the sub-segments of business
process outsourcing industry. In the following SRS the front office outsourcing is explained
in detail.
PURPOSE
The purpose of this system is to provide information about the customer need
from inside and outside world. With the reduction in communication costs and improved
bandwidths and associated infrastructure, BPO as a segment is witnessing massive
growth. One of the key challenges that BPO companies is that to provide data
entry/data validation services is an efficient and effective way of getting the source
documents from different customers and accurately route the same of different operators
for processing.
SCOPE
BPO is a way in which it helps to increase company’s flexibility. As part of BPO,
documents need to be managed between the outsourcing company and the offshore
company. Multiple clients need to be managed by the BPO Company.
SYSTEM ENVIRONMENT
The BPO system is embedded in a larger system involving several management
systems. We describe this environment as communication system between customer and
agent through voice chat. The administrator of the system uses FTP for moving files
from one place to another.
FUNCTIONAL REQUIREMENTS
Functional requirements are those refer to the functionality of the systemize.
What services it will provide to the user. Nonfunctional (supplementary) requirements
pertain to other information needed to produce the system correctly and detailed
separately.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online recruitment system
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse. Actor is any external entity that makes use
of the system being modeled. It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are Process agent, Customer and Database.
The use cases are the activities performed by actors.
USE CASE
Use case is a collection of failure and related success scenarios that describe the
actor using a system to support a goal.
PROCESS AGENT
The ultimate Goal of the process agent is to make sale. The operation performed
by him/her is he/she will first call the customer then pitches there product for sale. If
the customer is interested the agents mark it has a sale else disconnects the call and
moves to another customer.
DATABASE
The database is neither a computer nor a memory where all the customers’ details
will be stored. It consists of the customer name, customer address, and customer phone
number. Further details of the customer can also be added in the future by the agent.
CUSTOMER
Customer plays a vital role in the BPO industry. Agent calls the customer from
the database. Once the call gets connected and the customer is happy with the product
which is pitched by the agent then he/she will show interest for buying the product else
he/she will reject the product and disconnect the call.

CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle
with three compartments. Top compartment have the class name, middle compartment the
attributes and the bottom compartment with operations.
DOCUMENTATION OF CLASS DIAGRAM
This class diagram has three class’s process agent, customer and database.
• Agent - is the class name. Its attributes are username, password, name, phone no and
address. The operations performed by the agent class are login, giving details to customer
and selling the product.
• Customer - is the class name. Its attributes are name, phone no, address. The operations
performed are attending the call, asks about the product.
• Database - is the class name. The operations performed are storing customer details,
verifying login and updating the customer details.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what order.
It is a construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.

2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM
The single use case in the BPO management system is taken and sequence of
operations followed in the use case.
The BPO has the following sequence of process:
1. Agent fetches the data from the database
2. Database provides the details of the customer to agent and agent dials to the customer.
3. Customer responds to the agent and agent pitches his/her product.
4. If necessary customer buys else
discards.5. Agent updates the call
history 6.proceeds with the call.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration
diagram into a sequence diagram and the vice versa. A collaboration diagram
resembles a
Flowchart that portrays the roles, functionality and behavior of individual objects as well
as the overall operation of the system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM
This diagram is similar to sequence diagram. But the difference is the various
operations involved in the particular use case will be numbered. In this diagram, the
sequence of step is
• Fetches the customer details from the database.
• Database provides the customer details.
• Agent dials the customer.
• Customer responds to the agent call.
The agent pitches about his/her product to the customer. If necessary customer buys else
disconnects the call. The agent updates the call history. The agent proceeds with the call.
STATE CHART DIAGRAM
It is also called as State diagram .The purpose of state diagram is to understand
the algorithm in problem statement. A state is represented as a rounded box, which may
contain one or more compartments. Compartments are all optional.
Types of compartment:
*Name compartment- holds name of the state
*Internal transition- holds internal actions or activities. State chart is shown as the small dot
.Final state is shown as circle surrounding a small dot.
DOCUMENTATION OF STATE CHART DIAGRAM
The various states are login, fetch data from database, call the customer,pitches
the product, sales the product, proceeds with another call.
The state chart diagram describes the behavior of the system.
1. The main purpose of the system is to sale the product to the customer.
2. After login, the agent gets details of customer from database.
3. The agent calls the customer.
4. The agent pitches about the product.
5. If customer interested, the agent buys the product else discards.
6. Agent proceeds with the call.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the
Unified Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as a rounded box containing the
name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

Activity Diagram is shows the flow of the activity which is carried out in
the BPO management. It is more or less equal to the flow chart which we use in our
programming languages. It consists of states such as login, fetches the data, calls the
Customer, pitches the product, makes the sale and etc.
Initial node: The filled in circle is the starting point of the diagram. An initial node isn’t
required although it does make it significantly easier to read the diagram.
• Activity final node. The filled circle with a border is the ending point. An activity
diagram can have zero or more activity final nodes.
• Activity. The rounded rectangles represent activities that occur. An activity may be
physical, such as Inspect Forms, or electronic, such as display the BPO details.
• Flow/edge. The arrows on the diagram. Although there is a subtle difference between
flows and edges I have never seen a practical purpose for the difference although I have
nodoubt one exists. I’ll use the term flow.
COMPONENT DIAGRAM
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.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is BPO management systems. And the
agent calls customer, pitches about his product and makes the sale are the main
componentcomes under the component diagram.

DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a
grouping of elements in the OO model, and is a Cradle extension to UML. PDs can be
used to show groups of classes in Class Diagrams (CDs), groups of components or
processes in Component Diagrams (CPDs), or groups of processors in Deployment
Diagrams (DPDs).

FORMS
SOURCE CODE: '##ModelId=4D62059502DE
'##ModelId=4D62041B005D Public NewProperty As process_agent
PrivateNAMEAsVariant '##ModelId=4D620459007D
'##ModelId=4D62041F01F4 PublicSubget_details()
PrivateaddressAsVariant End Sub
'##ModelId=4D6204240119 '##ModelId=4D62056900
Privatephone_noAsVariant 6D
'##ModelId=4D6205B7008C PublicSubupdate_details()End Sub
Public NewProperty As process_agent PublicNewProperty As
'##ModelId=4D62042F0271 customer
PublicSubattends_call() '##ModelId=4D6205AE00FA
End Sub Public NewProperty2 As database
'##ModelId=4D62043B036B '##ModelId=4D6203E2000F
PublicSubasks_query() Public Sub makes_call()
End Sub If Form1.Text1.Text = "bpo" And
database Option Form1.Text2.Text = "123" Then
Explicit MsgBox "Login successfull"
'##ModelId=4D620452000F Else
Private NAME As Variant MsgBox "Invalid
password"End If
Form2.Sh
owEnd
Sub
'##ModelId=4D6203EA02AF End If
Public Sub pitches_about_product() If (Form2.Combo1.Text = "Rubini") Then
Form2.Show Form5.Sh
End Sub owEnd If
'##ModelId=4D62040401A5 End Sub
Public Sub make_sales() ##ModelId=4D62040903
If (Form2.Combo1.Text = "Anand") Then 0D
Form3.Show Public Sub
End If ends_the_call()
If (Form2.Combo1.Text = "Brindha") Then Form2.Show
Form4.Show End Sub
RESULT
Thus the project to develop BPO management system using Rational Rose
Software and to implement the software in Visual Basic is done successfully.
Ex No: 14 LIBRARY MANAGEMENT SYSTEM
DATE:
AIM
To develop a project on Library management system using Rational Rose Software and
to implement the project in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
The case study titled Library Management System is library management software for
the purpose of monitoring and controlling the transactions in a library. This case study on the
library management system gives us the complete information about the library and the daily
transactions done in a Library. We need to maintain the record of news and retrieve the details
of books available in the library which mainly focuses on basic operations in a library like
adding new member, new books, and up new information, searching books and members and
facility to borrow and return books. It features a familiar and well thought-out, an attractive
user interface, combined with strong searching, insertion and reporting capabilities.
PROBLEM STATEMENT
The process of members registering and borrowing books from the library
are described sequentially through following steps:
a. First the member registers himself if he was new to the library.
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
OVERALL DESCRIPTION
The Library Management System is an integrated system that has five modules as
part of it. The five modules are,
1) Login for Student: Using this module student login to the system using his/herunique
username and password.
2) Search a book: The details are stored in book table in database by giving thedetails about
the selecting books
 3) Form for Registration: In this module the new user can apply for his/her library
membership.
4) Return Book: In this module the user can return the book.
5) Renewal Book: In this module the user can renewal the book before the due date is exceed.
SOFTWARE REQUIREMENT
SPECIFICATIONINTRODUCTION
This system would be used by members who are students of any college to check the
availability of the books and borrow the books, and then the databases are updated. The
purpose of this document is to analyze and elaborate on the high-level needs and features of
the library management system. It also tells the usability, reliability defined in use case
specification.
USABILITY
User interface makes the Recruitment system to be efficient. That is the system will help
the member to register easily and helps them to get their books easily. The system should be
user friendly.
SECURITY
This system is designed keep in view that chances of unauthorized users made
negligible. Only the administrator able to create the new users. He is the only person to access
of main database.
RELIABILITY
The library management system should be able to serve the applicant with correct
information and day-to-day update of information.
FUNCTIONAL REQUIREMENTS
Functional requirements are those that refer to the functionality of the system
that is the services that are provided to the candidate who register for the books.
EXTERNAL INFRASTRUCTURE
REQUIREMENTSSOFTWARE REQUIRMENTS
1. Front end: IBM rational rose enterprise edition.
2. Back end: visual basic 8.0.
HARDWARE REQUIRMENTS
1. Processor: Pentium 4
2. RAM : 256mb
3. Operating system : Microsoft windows XP
4. Free disk space : 1GB
UML DIAGRAMS
The following UML diagrams describe the process involved in the library
management system.
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of interactions
between systems and users in a particular environment and related to a particular goal. It is
represented using ellipse. Actor is any external entity that makes use of the system being
modeled. It is represented using stick figure.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are candidate, reviewer and database. The use
cases are the activities performed by actors.
The actors in this use case diagram are
 Librarian – Librarian is used to issue the books, update and maintain records,
request the vendor for a book, and track complaints.
 User – User is used to register and login for the account to take or search a book,
request for issue, view history, request to the librarian. After all the processes are
completed, he/she logout their account.
 Book Database - Book database is used to show the updated records and book status
of the students as well as the teachers. Vendor- provides the books to the library and
checks the payment acknowledgement.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. It is represented using a rectangle
with three compartments. Top compartment have the class name, middle compartments
the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has five classes:
o Library – it is the class name. Its attributes are location, library id. Its operations
are showing the id of the user.
 o Librarian – is the class name. Its attributes are details, librarian id, issue status,
complaint resolution, tracking, calculate fine, vendor request, payment. Its operations
are checking all the details of the users.
o Books Database – is the class name. Its attributes are title, author, book id, and
update. Its operations are showing the book title, author and their updates.
o User - is the class name. Its attributes are details, user id, search, request,
complaints, pay fine.
o Vendor – is the class name. Its attributes are book details, search, supply book,
payment details.
SEQUENCE DIAGRAM
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.
DOCUMENTATION OF SEQUENCE DIAGRAM
The sequence diagram describes the sequence of steps to show
a. The member registers himself in library.
b. He will select the year
c. He selects the books given and the database will update the status of book.
d. Then administrator will log in and verify the status of books.
e. If the book is available he will issue the book.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction diagram.
A sophisticated modeling tool can easily convert a collaboration diagram into a sequence
diagram and the vice versa. A collaboration diagram resembles a flowchart that portrays the
roles, functionality and behavior of individual objects as well as the overall operation of the
system in real time.
DOCUMENTATION OF COLLABRATION DIAGRAM

Collaboration Diagram for searching a book and issuing it as per the request by the user from
the librarian.
STATE CHART DIAGRAM
The purpose of state chart diagram is to understand the algorithm involved
in performing a method. It is also called as state diagram. A state is represented as a
round box, which may contain one or more compartments. An initial state is represented
assmall dot. A final state is represented as circle surrounding a small dot.

DOCUMENTATION OF STATE CHART DIAGRAM

This state diagram describes the behavior of the system.
• First state is authentication where the customer should authenticate to the system.
• The next state is to login where the user should check whether it is correctly login or re-
login.
• The next state is to search for a book (users)/request the vendor (librarian)/provide the
request book (vendor).
 And the last state is to receive acknowledgement and log-off /research/new function.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and operational
step-by-step workflows of components in a system. An activity diagram shows the
overall flow of control. An activity is shown as a rounded box containing the name of the
operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in library management
system. First the customer login then fills the details.
a) Search book operation for reader.
b) Acknowledge and issue books to the users by the librarian.
c) Provide books requested by the librarian from the vendor.
d) Bill payment from the librarian to the vendor.
e) Status of the books updated in the database.
COMPONENT DIAGRAM
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.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is library management systems.
And customer database details and update database then vendor views the database are the
components comes under the main component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model
the physical deployment of artifacts on deployment targets. Deployment diagrams show
"the allocation of artifacts to nodes according to the Deployments defined between them.
It is represented by 3-dimentional box. Dependencies are represented by communication
association.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

a. Local Consoles / Computers for login and search purposes by users, librarian and
vendors.
b. Library LAN Server interconnecting all the systems to the Database.
c. Internet to provide access to Vendors to supply the requested books by the Librarian
d. Vendor Server to maintain the records of the requests made by the librarian and
books provided to the library.
PACKAGE DIAGRAM
A package diagram in unified modeling language that depicts the dependencies
between the packages that make up a model. A Package Diagram (PD) shows a grouping
of elements in the OO model, and is a Cradle extension to UML. PDs can be used to
show groups of classes in Class Diagrams (CDs), groups of components or processes in
Component Diagrams (CPDs), or groups of processors in Deployment Diagrams (DPDs).
There are three types of layer. They are
1. User interface layer
Software objects representing domain concepts that fulfill application
requirements, such as calculation of a sale total.
2. Domain layer
Layer that contains domain objects to handle application logic work
3. Technical services layer
General purpose objects and sub system that provide supporting technical services,
such as interfacing with a database logging.
FORMS

Login form:

Choice form:
Renewal form:

Return form:
Searching form:

Registration form:
View books:

SOURCE CODE
FORM 1
Private Sub Command1_Click()Do
If Form1.Data1.Recordset.EOF ThenForm1.Data1.Recordset.MoveFirst
If(Form1.Text1.Text=Form1.Data1.Recordset.Fields(0)) And(Form1.Text2.Text=
Form1.Data1.Recordset.Fields(1)) Then
MsgBox "login suceed"Form2.Show
Exit DoElse
Form1.Data1.Recordset.MoveNextEnd If
LoopUntil
Form1.Data1.Recordset.EOF
If Form1.Data1.Recordset.EOF ThenMsgBox ("invalid login")
End If End Sub
Private Sub Label1_Click()Form7.Show
End Sub
Private Sub Command2_Click()Form7.ShowEnd Sub
FORM 2
Private Sub Command1_Click()Form3.Show
End Sub
Private Sub Command2_Click()Form4.Show
End Sub
Private Sub Command3_Click()Form5.Show
End Sub
Private Sub Command4_Click()Form6.Show
End SubFORM 3
Private Sub Command1_Click()
If (Text1.Text = "Internet Programming" Or Text1.Text = "ooad" Or Text1.Text = "computer
graphics") Then
MsgBox "Book is successfullyreturned "
Form2.ShowElse
MsgBox "Renewal timeexceeding "
End If End SubFORM 4
Private Sub Combo1_Change()End Sub
Private Sub Command1_Click()
Dim a As Stringa = Text1.Text Dim b As Stringb = Text2.Text
Dim i As IntegerFor i = 0 To 5
If((a=Data1.Recordset.Fields(0))And (b = Data1.Recordset.Fields(1))) Then
MsgBox "successfullyissued thank u!!!!!"
Exit ForElse
MsgBox "Sorry....ur book notfound try again!!!!!"
End If Next i End Sub
Private Sub Command2_Click()Form2.Show
End Sub FORM 5
Private Sub Command1_Click()
If (Text1.Text = "Internet Programming" Or Text1.Text = "ooad" Or Text1.Text =
"computer graphics") Then
MsgBox "Book is successfullyrenewaled"
Form2.ShowElse
 MsgBox "Renewal Public NewProperty4 As test
...................... timeexceeding " '##ModelId=55AF649200FB
End If Public Sub qualification_details()
End Sub End Sub
FORM 6 '##ModelId=5602789401
Private Sub B7
Command1_Click() Public Sub
Data1.Recordset.AddNew login() Dim
MsgBox count As
"successfullyregistered" IntegerFor
Form2.Sho count = 0 To 1
wEnd Sub If Form1.Data1.Recordset.EOF=False
CLASS Then
MODULE If (Form1.Data1.Recordset.Fields(0)
LIBRARY = Form1.Text1.Text) And
Option Explicit (Form1.Data1.Recordset.Fiel
'##ModelId=55AF6476030E ds(1) = Form1.Text2.Text)
Public username As Variant Then
'##ModelId=55AF648502FE MsgBox ("login successful")
Private pw As Variant Form2.Show
'##ModelId=55AF648703BA Exit For
Public ph_no As Variant '#unloadMe
'##ModelId=55AF658F012C Else
Public NewProperty As databa MsgBox ("invalid
'##ModelId=55AF659A02DF login")Exit For
Public NewProperty2 As Collection End If
'##ModelId=55B89A360327 End If Next
Public NewProperty3 As Collection count
'##ModelId=55B89EAB020D End Sub
 DATABASE '##ModelId=55B89A360329
Option Explicit Public theappp As Collection
'##ModelId=55B88A3F001F '##ModelId=55B89EAE0317
Private applicant As Variant Public NewProperty2 As test
'##ModelId=55B88A4800DA '##ModelId=55AF64F50197
Private selected_applicant As Variant Public Sub test()
'##ModelId=55AF658F012A End Sub
Public NewProperty As Collection '##ModelId=55AF651F02EF
'##ModelId=55AF659602B0 Public Sub marks()
Public therecruiters As Collection End Sub
'##ModelId=55AF65570030 '##ModelId=55AF6524039B
Public Sub verify_qualification() Public Sub select_applicant()
End Sub End Sub
'##ModelId=55AF65640224 LIBRARIAN
Public Sub select_canditate() Option Explicit
End Sub '##ModelId=55B89E6C029A
BORROWER Private username As Variant
Option Explicit '##ModelId=55B89E8A0336
'##ModelId=55AF64B600EB Private pw As Variant
Public designation As Variant '##ModelId=55B89EAB020F
'##ModelId=55AF64D4030E Public theappp As appp
Public ph_no As Variant '##ModelId=55B89EAE0319
'##ModelId=55AF64DB0272 Public NewProperty As recruiters
Public name As Variant '##ModelId=55B89E9102C9
'##ModelId=55AF659602B2 Public Sub apptitude_test()
Public thedataba As databa End Sub '##ModelId=55B89E9B00E4
'##ModelId=55AF659A02E1 Public Sub technical_test()End Sub
Public NewProperty As Collection
RESULT
Thus the project to develop Library Management system using Rational Rose
Software and to implement the software in Visual Basic is done successfully.
Ex No: 15 STUDENT INFORMATION SYSTEM
DATE:
AIM
To develop a project of Student Information system using Rational Rose Software and
to implement the software in Visual Basic.
PROBLEM ANALYSIS AND PROJECT PLANNING
A Student information system (SIS) is a software application for educational
establishments to manage student data. Student information systems provide capabilities for
entering student test and other assessment scores, building student schedules, tracking student
attendance, and managing many other student-related data needs in a school, college or
university.
PROBLEM STATEMENT
a. Effective for Administration Purpose
b. Cheap
c. Better service
OBJECTIVES
The main purpose of creating the document about the software is to know about thelist
of the requirement in the software project part of the project to be developed. It
specifies the requirement to develop a processing software part that completes the set of
requirement.
SCOPE
In this specification, we define about the system requirements that are about from the
functionality of the system. It tells the users about the reliability defined in use case
specification.
FUNCTIONALITY
Many members of the process line to check for its occurrences and transaction, we
have to carry over at sometimes.
USABILITY
The user interface to make the transaction should be effectively.
PERFORMANCE
It is the capability about which it can performed function for many user at
sometimes efficiently (i.e.) without any ever occurrences
RELIABILITY
The system should be able to the user through the day to day transaction.
UML DIAGRAMS
The following UML diagrams describe the process involved in the online
recruitment system.
a. Use case diagram
b. Class diagram
c. Sequence diagram
d. Collaboration diagram
e. Activity diagram
f. Component diagram
USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and
organize system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse. Actor is any external entity that makes use
of the system being modeled.
DOCUMENTATION OF USE CASE DIAGRAM
The actors in this use case diagram are Admin, Student and Database. The use
cases are the activities performed by actors.
a. Admin register login, and store the student records details in database.
b. Student Register from the Student Login process.
c. Then the database is searched for details and verified.
d. Database stores the details and returns acknowledgement.
CLASS DIAGRAM
A class diagram in the unified modeling language (UML) is a type of static
structure diagram that describes the structure of a system by showing the system's
classes, their attributes, and the relationships between the classes. It is represented using a
rectangle with three compartments. Top compartment have the class name, middle
compartment the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has three classes Login, Student details and Update details in
database.
a. Students – is the class name. Its attributes are name, Address, DOB, Gender,
College, Subjects, Semester, Year, Degree and Branch. The operations Performed in the
Students class, Store database and Update.
b. Administration– is the class name. Its attributes are Login, Password and
database. The operations performed are Student Details store in database and send
acknowledgement.
c. Database – is the class name. The operations performed are storing Search and
storing the values.
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction diagram
that shows how processes operate with one another and in what order. It is a construct of a
Message Sequence Chart. There are two dimensions.
1. Vertical dimension-represent time.
2. Horizontal dimension-represent different objects.

DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show
a. The Admin login and registering for Add Student Details.
b. The verification done by the interface and sending acknowledgement for registration.
c. Searching the database with login and displaying it for maintenance.
COLLABRATION DIAGRAM
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modeling tool can easily convert a collaboration diagram into a
sequence diagram and the vice. A collaboration diagram resembles a flowchart that
portrays the roles, functionality and behavior of individual objects as well as the overall
operation of the system in real time.

DOCUMENTATION OF COLLABRATION DIAGRAM

The collaboration diagram is to show how the Student registers and the authorities
maintain the details of the registered students in the Information system. Here the
sequence is numbered according to the flow of execution.
ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams can be used to describe the business and operational step-by-
step workflows of components in a system. An activity diagram shows the overall flow of
control. An activity is shown as a rounded box containing the name of the operation.
DOCUMENTATION OF ACTIVITY DIAGRAM
This activity diagram flow of stepwise activities performed in recruitment system.
a. The student details are Add and stored in database.
b. Select the course from the given Course by student.
c. Search Profile and Result with login and if data present in the database.
d. The searched data is displayed if available and then Log Out.
STATECHART DIAGRAM

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a system. It is represented by boxed figure. Dependencies are
represented by communication association.
DOCUMENTATION OF COMPONENT DIAGRAM
The main component in this component diagram is Student Information system.
And register, User and Manage, Request details are the components comes under the
main component.
DEPLOYMENT DIAGRAM
A deployment diagram in the unified modeling language serves to model the
physical deployment of artifacts on deployment targets. Deployment Diagrams show "the
allocation of artifacts to nodes according to the Deployments defined between them. It is
represented by 3-dimentional box. Dependencies are represented by communication
association.
DOCUMENTATION OF DEPLOYMENT DIAGRAM
The processor in this deployment diagram is the Student Information System
which is the main part and the Student are the Admin, verify and search which are the
some of the main activities performed in the system.
PACKAGE DIAGRAM

FORMS
LOGIN
EXAM SCHEDULE

EXAM DETAILS
STUDENT PROFILE

SERIAL TEST MARKS

SOURCECODE Private Sub Command2_Click()Dim countAs
FORM 1 Integer
Private Sub For count = 0 To 5
Command1_Click()Dim If Data2.Recordset.EOF = False Then
count As Integer If Data2.Recordset.Fields(0) = Text3.Text And
For count = 0 To 5 Data2.Recordset.Fields(1) = Text4.TextThen
If Data1.Recordset.EOF = False Then MsgBox ("login successful")
If Data1.Recordset.Fields(0) = Form2.Show
Text1.Text And Exit For
Data1.Recordset.Fields(1) = ‘#unloadMeElse
Text2.TextThen MsgBox ("login MsgBox ("invalid login")Exit
successful") Form6.Show For
Exit End IfEnd If
For Next countEnd Sub
'#unlo Private Sub Command3_Click()Text1.Text =
adMe ""
Else Text2.Text = ""End
MsgBox ("invalid Sub
Private Sub Command4_Click()
Text3.Text = ""
login")Exit ForEnd If Text4.Text = ""End Sub
End Private Sub Command1_Click()
If Form3.Show
End Sub
Private Sub Command2_Click()
Next Form5.Show
count End SubFORM2
End Private Sub Command1_Click()
Sub Form1.ShowEnd Sub
Private Sub Else
Command2_Click()Dim MsgBox ("invalid reg no")Exit
count As Integer For
For count = 0 To 5 End IfEnd If
If Data1.Recordset.EOF = False Then Next countEnd
If Text6.Text = Sub
Data1.Recordset.Fields(0) Private Sub Command3_Click()
Then Text1.Text = ""
'MsgBox ("login successful") Text2.Text = ""Text3.Text = ""Text4.Text = ""
Text1.Text = Text5.Text = ""Text6.Text = ""End Sub
Data1.Recordset.Fields(1)Text2.Text If Data1.Recordset.EOF = False Then
= Data1.Recordset.Fields(2) If Data1.Recordset.Fields(1) =
Text3.Text = Text2.Text Then
Data1.Recordset.Fields(3)Text4.Text Text1.Text =
= Data1.Recordset.Fields(4) Data1.Recordset.Fields(0)
Text5.Text = Text3.Text =
Data1.Recordset.Fields(5)Exit For Data1.Recordset.Fields(2)
FORM3 Text4.Text = Data1.Recordset.Fields(3) Text5.Text =
Private Sub Data1.Recordset.Fields(4) Text6.Text =
Command1_Click() Data1.Recordset.Fields(5)
Form4.Show Exit For '#Unload MeElse
End Sub
Private Sub MsgBox ("invalid register number")End If
Command2_Click()Dim End If Next count
count As Integer FORM 4
For count = 0 To 4 Dim a As DB
'#un Private Sub Command1_Click()
load Set a = New DBa.store End
Me Sub
 Private Sub Text6.Text = ""End Sub
Command3_Click End Sub
()Text1.Text = "" Private Sub Command2_Click()
Text2.Text = "" Form1.Show
Text3.Text = "" ENd Sub
Text4.Text = ""
Text5.Text = ""

RESULT
Thus the project to develop book student information system using Rational Rose
Software and to implement the software in Visual Basic was done successfully.