A ANNA UNIVERSITY,CHENNAI .

GKM
COLLEGE OF ENGINEERING AND TECHNOLOGY
(SPONSPERED BY SUGANTHI EDUCATIONAL TRUST)
(AN ISO ISO: 9001 :2005 CERTIFIDE, APPROVED BY AICTE ,AFFLIATED TO ANNA UNIVERSITY)
G.K.M NAGAR,New Perungalathur(Near Tambaram) Chennai-600 063.

ESTD.1996

(BACHELOR OF ENGINEERING)
COMPUTER SCIENCE AND ENGINEERING

LABORATORY RECORD

NAME :…………………………………….

REGISTER NUMBER :…………………………………….

SEMESTER :…………………………………….

YEAR :…………………………………….

BRANCH : ……………………………………..
 GKM
COLLEGE OF ENGINEERING AND TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

BONAFIDE CERTIFICATE

REG NO:

Name of the lab

Department of Certified that this is a bonafide record of

the work done by of Class in the

Laboratory during the Year

Signature of Staff-in-Charge Head of the Department

Internal Examiner External Examiner

Name of the Examination : ………………………….

Register No : …………………………..
Date of the Examination : ………………………….
 INDEX
Exp.No Date Name of the Experiment Page Marks Sign
No

Completed / Incomplete Staff-in-Charge Sign

EXNO: 1a PASSPORT AUTOMATION SYSTEM

AIM

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

PROBLEM ANALYSIS AND PROJECT PLAN

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

PROBLEM STATEMENT

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

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

2. The core of the system is to get the online registration form (with details such
as name, address etc.,) filled by the applicant whose testament 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

SNO SOFTWARE REQUIREMENTS

SPECIFICATION

1.0 Introduction
1.1 Purpose
1.2 Scope
1.3 Definition, Acronyms and
1.4 Abbreviations
1.5 Reference
1.6 Technology to be used
1.7 Tools to be used
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 inthis 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.
2.4 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.5 USER CHARACTERISTICS

1. Applicant - They are the people who desires to obtain the passport and submit
the information to the database.
2. Administrator - He has the certain privileges to add the passport status and to
approve the issue of passport. He may contain a group of persons under him
to verify the documents and give suggestion whether or not to approve the
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.6 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.7 ASSUMPTIONS AND DEPENDENCIES

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

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

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

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, givedetails, logout, collectdetails,

verification, issue.

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

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

e. The submit details use case is used by the applicant for submitting his
details
 f. The check status use case is used by the applicant for checking the
status of the application process.

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

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

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

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

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

CLASSDIAGRAM

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

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

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

and operations are login, givedetails and logout. The applicant login
and fill the details that are required for applying the passport .After
applying the person can view the status of the passport verification
process

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

operation is store. The purpose is to store the data.

c. REGIONAL ADMINISTRATOR- The regional administrator has

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

d. PASSPORT ADMINISTRATOR-The passport administrator has

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

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 get the details from the database and do
verification and the forward to regional administrator.

c. The regional administrator get details form passport administrator and

perform verification and send report to passport administrator.

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

COLLABORATION DIAGRAM

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

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

STATE CHART DIAGRAM

The state chart diagram contains the states in the rectangle boxes and starts in
indicated by the dot and finish is indicated by dot encircled. The purpose of state
chart diagram is to understand the algorithm in the performing method.

DOCUMENTATION OF STATE CHART DIAGRAM

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

b. Login state represent authentication for login the passport automation

system.

c. In this state, it checks whether the applicant has provided all the
details that is required.

d. Police, regional administrator and passport administrator get

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

operation

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 a systems. It is represented
by boxed figure. Dependencies are represented by communication assosiation.
DOCUMENTATION OF COMPONENT DIAGRAM

a. The components in the passport automation system are passport

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

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

dependent on passport automation system are shown by the dotted
arrow

DEPLOYMENT DIAGRAM
It is a graph of nodes connected by communication association. It is represented by
a three dimensional box. A deployment diagram in the unified modeling language
serves to model the physical deployment of artifacts on deployment targets.
Deployment diagrams show "the allocation of artifacts to nodes according to the
Deployments defined between them. It is represented by 3-dimentional box.
Dependencies are represented by communication association. The basic element of
a deployment diagram is a node of two types

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

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

DOCUMENTATION OF DEPLOYMENT DIAGRAM

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

PACKAGE DIAGRAM

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

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

o User interface layer

o Domain layer

o Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

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

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

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

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

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

technical services.

FORMS:
FORM1:

FORM2:
FORM3:
FORM4:
FORM5:
 FORM6:

FORM7:
 SOURCE CODE:
FORM1
Private Sub Command1_Click()
Dim app As Applicant
Set app = New Applicant
app.Login
End Sub
Private Sub Command2_Click()
Dim pass As PassportAdministrator
Set pass = New PassportAdministrator
pass.Login
End Sub
Private Sub Command3_Click()
Dim reg As RegionalAdminstrator
Set reg = New RegionalAdminstrator
reg.Login
End Sub
Private Sub Command4_Click()
Dim pol As Police
Set pol = New Police
pol.Login
End Sub
Private Sub Command5_Click()
If Form1.Text1.Text = "" And Form1.Text2.Text = "" Then
MsgBox "LOGIN SUCCESSFUL"
Form6.Show
Else
MsgBox "INVALID USERNAME AND PASSWORD"
Unload Me
End If
End Sub
Private Sub Command6_Click()
End
End Sub
FORM2:
Private Sub Command1_Click()
Dim subdetails As Applicant
Set subdetails = New Applicant
subdetails.SubmitDetails
End Sub
Private Sub Command3_Click()
Data1.Recordset.Edit
End Sub
Private Sub Command4_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Data1.Recordset.Fields(9) = "successful"
Data1.Recordset.update
End Sub
Private Sub Command8_Click()
Data1.Recordset.Edit
Data1.Recordset.Fields(9) = "unsuccessful"
Data1.Recordset.update
End Sub
Private Sub ve_Click()
Dim verify As PassportAdministrator
Set verify = New PassportAdministrator
verify.update
End Sub
FORM4:
Private Sub Command1_Click()
Dim search As RegionalAdminstrator
Set search = New RegionalAdminstrator
search.verify
End Sub
Private Sub Command2_Click()
Data1.Recordset.Edit
Data1.Recordset.Fields(10) = "successful"
Data1.Recordset.update
End Sub
Private Sub Command3_Click()
Data1.Recordset.Edit
Data1.Recordset.Fields(10) = "unsuccessful"
Data1.Recordset.update
End Sub
Private Sub Command4_Click()
Form1.Show
Unload Me
End Sub
Private Sub Command5_Click()
Dim update As RegionalAdminstrator
Set update = New RegionalAdminstrator
update.update
End Sub
Private Sub Command6_Click()
Data1.Recordset.MoveLast
End Sub
Private Sub Command7_Click()
Data1.Recordset.MoveFirst
End Sub
Private Sub Command8_Click()
If Data1.Recordset.BOF Then
MsgBox "NO DATA FOUND"
Else
Data1.Recordset.MovePrevious
End If
End Sub
Private Sub Command9_Click()
If Data1.Recordset.EOF Then
MsgBox "NO DATA FOUND"
Else
Data1.Recordset.MoveNext
End If
End Sub
FORM5:
Private Sub Command1_Click()
Dim search As Police
Set search = New Police
search.verify
End Sub
Private Sub Command2_Click()
Data2.Recordset.Edit
Data2.Recordset.Fields(11) = "successful"
Data2.Recordset.update
End Sub
Private Sub Command3_Click()
Data2.Recordset.Edit
Data2.Recordset.Fields(11) = "unsuccessful"
Data2.Recordset.update
End Sub
Private Sub Command4_Click()
Form1.Show
Unload Me
End Sub
Private Sub Command6_Click()
Data2.Recordset.MoveLast
End Sub
Private Sub Command7_Click()
Data2.Recordset.MoveFirst
End Sub
Private Sub Command8_Click()
If Data2.Recordset.BOF Then
MsgBox "NO DATA FOUND"
Else
Data2.Recordset.MovePrevious
End If
End Sub
Private Sub Command9_Click()
If Data2.Recordset.EOF Then
MsgBox "NO DATA FOUND"
Else
Data2.Recordset.MoveNext
End If
End Sub
FORM6:
Private Sub Command1_Click()
Dim checkstate As Applicant
Set checkstate = New Applicant
checkstate.CheckStatus
End Sub
Private Sub Command2_Click()
Form1.Show
Unload Me
End Sub
UML CODINGS:
APPLICANT:
Option Explicit
'##ModelId=4D7521E80271
Private Name As Variant
'##ModelId=4D7521EE02CE
Private FatherName As Variant
'##ModelId=4D7521F3009C
Private DateOfBirth As Variant
'##ModelId=4D75220B01A5
Private PermanentAddress As Variant
'##ModelId=4D752220033C
Private TemporaryAddress As Variant
'##ModelId=4D75224101E4
Private EmailID As Variant
'##ModelId=4D75224701E4
Private PhoneNumber As Variant
'##ModelId=4D75224E031C
Private PanNo As Variant
'##ModelId=4D7522590242
Private ApplicationNo As Variant
'##ModelId=4D75225D038A
Private UserName As Variant
'##ModelId=4D75226300CB
Private Password As Variant
'##ModelId=4D7523300271
Public NewProperty As Database
'##ModelId=4D7522690109
Public Sub Login()
If Form1.Text1.Text = "" And Form1.Text2.Text = "" Then
MsgBox "LOGIN SUCCESSFUL"
Form2.Show
Else
MsgBox "INVALID USERNAME AND PASSWORD"
Unload Me
End If
End Sub
'##ModelId=4D752271032C
Public Sub SubmitDetails()
Dim ap As Integer
Form1.Data1.Recordset.MoveLast
ap = Data1.Recordset.Fields(0)
Data1.Recordset.AddNew
ap = ap + 1
Form1.Data1.Recordset.Fields(0) = ap
Form1.Data1.Recordset.Fields(1) = Text1.Text
Form1.Data1.Recordset.Fields(2) = Text2.Text
Form1.Data1.Recordset.Fields(3) = Text3.Text
Form1.Data1.Recordset.Fields(4) = Text4.Text
Form1.Data1.Recordset.Fields(5) = Text5.Text
Form1.Data1.Recordset.Fields(6) = Text6.Text
Form1.Data1.Recordset.Fields(7) = Text7.Text
Form1.Data1.Recordset.Fields(8) = Text8.Text
Form1.Data1.Recordset.Fields(9) = "Under Process"
Form1.Data1.Recordset.Fields(10) = "Under Process"
Form1.Data1.Recordset.Fields(11) = "Under Process"
Form1.Data1.Recordset.update
Form1.Show
Unload Me
End Sub
'##ModelId=4D7522760261
Public Sub CheckStatus()
Dim Currentdb As Database
Set Currentdb = OpenDatabase("D:\PASSPORTPROJECT1\PASSPORT.mdb")
Dim Data As Recordset
Set Data = Currentdb.OpenRecordset("applicant", dbOpenDynaset)
Data.FindFirst "([ApplicationNo])=" & Form6.Text1.Text
If Data.NoMatch Then
MsgBox "No such record"
Else
MsgBox "success"
Form6.Text1.Text = Data.Fields(0)
Form6.Label5 = Data.Fields(1)
Form6.Label7 = Data.Fields(9)
Form6.label9 = Data.Fields(10)
Form6.Label11 = Data.Fields(11)
End If
Data.Close
End Sub
DATA BASE:
Option Explicit
'##ModelId=4D7522A30222
Private Name As Variant
'##ModelId=4D75233C005D
Public NewProperty As PassportAdministrator
'##ModelId=4D75233E006D
Form3.Text8.Text = Data.Fields(2)
End If
End If
End Sub
'##ModelId=4D7522BF01D4
Public Sub update()
If Form3.Text2.Text = Form3.Text7.Text And Form3.Text3.Text =
Form3.Text8.Text Then
Form3.Data1.Recordset.Edit
Form3.Data1.Recordset.Fields(9) = "successful"
Form3.Data1.Recordset.update
MsgBox "success"
Else
MsgBox "no "
Form3.Text7.Text = ""
Form3.Text8.Text = ""
End If
End Sub
POLICE:
Option Explicit
'##ModelId=4D7522E1001F
Private UserName As Variant
'##ModelId=4D75232601D4
Private Password As Variant
'##ModelId=4D7522E30251
Public Sub Login()
If Form1.Text1.Text = "poladmin" And Form1.Text2.Text = "12345" Then
MsgBox "LOGIN SUCCESSFUL"
Form1.Text1.Text = ""
Form1.Text2.Text = ""
Form1.Text1.SetFocus
Form5.Show
Else
MsgBox "INVALID USERNAME OR PASSWORD"
Form1.Text1.Text = ""
Form1.Text2.Text = ""
Form1.Text1.SetFocus
End If
End Sub
'##ModelId=4D7522E8008C
Public Sub verify()
Dim Currentdb As Database
Set Currentdb = OpenDatabase("D:\PASSPORTPROJECT1\passport.mdb")
Dim Data As Recordset
Set Data = Currentdb.OpenRecordset("Police", dbOpenDynaset)
If Form5.Text1.Text = "" Then
MsgBox "select any data"
Else
Data.FindFirst "([PanNo])=" & Form5.Text1.Text
If Data.NoMatch Then
MsgBox "No such record"
Else
MsgBox "success"
If Data.Fields(5) = "Notallowed" Then
MsgBox "not allowed"
Else
MsgBox "allowed"
End If
End If
End If
Data.Close
End Sub
'##ModelId=4D7522EA02BF
Public Sub update()
End Sub
REGIONAL ADMINSTRATOR:
Option Explicit
'##ModelId=4D7522C80222
Private UserName As Variant
'##ModelId=4D75231A0109
Private Password As Variant
'##ModelId=4D7522CB02CE
Public Sub Login()
If Form1.Text1.Text = "regadmin" And Form1.Text2.Text = "12345" Then
MsgBox "LOGIN SUCCESSFUL"
Form1.Text1.Text = ""
Form1.Text2.Text = ""
Form1.Text1.SetFocus
Form4.Show
Else
MsgBox "INVALID USERNAME OR PASSWORD"
Form1.Text1.Text = ""
Form1.Text2.Text = ""
Form1.Text1.SetFocus
End If
End Sub
'##ModelId=4D7522CE01A5
Public Sub verify()
Dim Currentdb As Database
Set Currentdb = OpenDatabase("D:\PASSPORTPROJECT1\passport.mdb")
Dim Data As Recordset
Set Data = Currentdb.OpenRecordset("RegionalAdminstrator", dbOpenDynaset)
If Form4.Text1.Text = "" Then
MsgBox "select any data"
Else
Data.FindFirst "([PanNo])=" & Form4.Text1.Text
If Data.NoMatch Then
MsgBox "No such record"
Else
MsgBox "success"
Form4.Text6.Text = Data.Fields(1)
Form4.Text7.Text = Data.Fields(2)
Form4.Text8.Text = Data.Fields(3)
Form4.Text9.Text = Data.Fields(4)
End If
End If
End Sub
'##ModelId=4D7522D002BF
Public Sub update()
If Form4.Text2.Text = Text6.Text And Form4.Text3.Text = Form4.Text7.Text
And Form4.Text4.Text = Form4.Text8.Text And Form4.Text5.Text =
Form4.Text9.Text Then
MsgBox "Details match"
Else
MsgBox "Details donot match"
End If
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

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 an 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

S.NO CONTENTS
INTRODUCTION

1.

OBJECTIVE

2.

OVERVIEW

3.

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

2. OBJECTIVE

The main objective of the system are 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

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

4. GLOSSARY

TERMS DESCRIPTION

MEMBER The one who registers himself and

purchase books from the bank.
DATABASE Database is used to store the details
of members and books.
ADMINISTRATOR The one who verifies the
availability of book and issue them
USER Member
SOFTWARE REQUIREMENT This software specification
SPECIFICATION documents full set of features and
function for online recruitment
system that is performed in
company website.

5. PURPOSE

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

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

7. FUNCTIONALITY

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

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

9. PERFORMANCE

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

10. RELIABILITY

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

11. FUNCTIONAL REQUIREMENTS

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

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

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 syatem : Microsoft windows xp.
4. Free disk space : 1gb

UML DIAGRAMS

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

a. Use case diagram

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

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, date of birth, address, phone number, member id,
college, degree, course and semester. Its operations are registration,
authentication, and year selection.

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

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

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

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

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

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

SEQUENCE DIAGRAM

A sequence diagram in Unified Modeling Language (UML) is a kind of interaction

diagram that shows how processes operate with one another and in what order. It is
a construct of a Message Sequence Chart. There are two dimensions.
1. Veritcal dimension-represent time.
2. Horizontal dimension-represent different objects.

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 select 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 andborrow
the book from the book bank. Here the sequence is numbered according to the flow
of execution.

STATE CHART DIAGRAM

The purpose of state chart diagram is to understand the algorithm involved in

performing a method. It is also called as state diagram. A state is represented as a
round box, which may contain one or more compartments. An initial state is
represented as small dot. An final state is represented as circle surrounding a small
dot.

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.

h.

ACTIVITY DIAGRAM

Activity diagrams are graphical representations of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as an rounded box containing
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.
Dependencies are represented by communication association

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. They are

o User interface layer

o Domain layer

o Technical services layer

FORM 3
FORM 4
FORM 5
FORM 6
FORM 7
FORM 8
FORM 9
SOURCE CODE:
Administrator. Class

Option 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.Show
Else
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...
'##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 Sub
Year . Class
Option Explicit
'##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=4D5A33F2036B
Private member_code As Variant
'##ModelId=4D5A33FA00EA
Private member_name As Variant
'##ModelId=4D5A34010399
Private book_name As Variant
'##ModelId=4D5A347E0138
Public NewProperty As year
'##ModelId=4D5A340F01B5
Public Sub issue_for_third()
On Error GoTo ErrorHandler
'## your code goes here...
Form8.Data1.Recordset.AddNew
Form8.Text5.Text = Form8.Text5.Text + 1
Form8.Text4.Text = Form8.Text4.Text - 1
If (Form8.Text4.Text <= 0) Then
MsgBox "only four books can be selected"
Form8.Show
End If
Exit Sub
ErrorHandler:
Call RaiseError(MyUnhandledError, "issue_for_third Sub")
End Sub
Form 1
Private Sub Command1_Click()
Form1.Show
End Sub
Private Sub Command2_Click()
Form9.Show
End Sub
Private Sub Command3_Click()
Form5.Show
End Sub
Form 2
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub Command2_Click()
Data1.Recordset.update
Form2.Show
End Sub
Form 3
Private Sub Command1_Click()
Form4.Show
End Sub
Private Sub Command2_Click()
End Sub
Private Sub Command3_Click()
Form7.Show
End Sub
Form 4
Private Sub Command2_Click()
Dim fi As Issue for first year
Set fi =new Issue for first year
fi.issue_for_first
End Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text4.Text = 5
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub
Form 5
Private Sub Command2_Click()
Dim se As Issue for second year
Set se =new Issue for second year
se.issue_for_second
End Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text4.Text = 5
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub
Form 6
Private Sub Command2_Click()
Dim th As Issue for third year
Set th =new Issue for third year
th.issue_for_third
End Sub
Private Sub Command3_Click()
Data1.Recordset.update
End Sub
Private Sub Form_Load()
Text5.Text = 0
End Sub
Private Sub List1_Click()
Text3.Text = List1.Text
End Sub
Form 7
private Sub Command1_Click()
Dim au As Administrator
Set au =new Administrator
au. authentication
End Sub
Private Sub Command2_Click()
Unload Me
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
 EXNO:3a EXAM REGISTRATION SYSTEM

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.

SOFTWARE REQUIREMENT SYSTEM

12. INTRODUCTION
 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 modelled. It is
represented using stick figure

DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are Student, Interface and Database. The
usecases 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,

Password and database. The operations performed are form
verification, store in database and send acknowledgement.

c. Database – is the class name. The operations performed are 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. Veritcal dimension-represent time.

2. Horizontal dimension-represent different objects.
 DOCUMENTATION OF SEQUENCE DIAGRAM

The sequence diagram describes the sequence of steps to show

a. The 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
maintains 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

DOCUMENTATION OF ACTIVITY DIAGRAM

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

a. First the student fills the form.

b. The student details are verified and stored in database.

c. Acknowledgement sent is received by student.

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

e. The searched data is displayed if available.

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

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

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.
7. Source Code
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
Private college As Variant
'##ModelId=4D41381923B5
Public NewProperty As reg website
Dim v1 As reg website
'##ModelId=4D91482B0167
"Confirm") = vbNo Then
datcollege.Recordset.Update
Exit Sub
End If
cmdSaveRecord.Enabled = False
cmdMovePrevious.Enabled = True
cmdMoveNext.Enabled = True
cmdDeleteRecord.Enabled = True
cmdNewRecord.Enabled = True
Form1.Show
End Sub
Private Sub cmdSaveRecord_Click()
Form1.Show
End Sub
Public Sub Processing()
datcollege.Recordset.MovePrevious
Form1.show
End Sub
Dim ob5 as students
Private sub cmdregistrationform_click()
Set ob5=new students
ob5. Delete
End Sub
Public Sub Delete()
On Error GoTo Delete_Error
If MsgBox("Are you sure you want to delete this record?", _
vbQuestion + vbYesNo + vbDefaultButton2, _
"Confirm") = vbNo Then
Exit Sub
End If
datcollege.Recordset.Delete
cmdMoveNext_Click
Exit Sub
Delete_Error:
MsgBox "This record cannot be deleted. Error code = " _
& Err.Number & vbCrLf & Err.Description, _
vbCritical, "Cannot Delete"
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: 4a STOCK MAINTENANCE SYSTEM

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. The stock maintenance system are
described sequentially through steps

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

S.NO CONTENT
1 INTRODUCTIO
N
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALI
TY
8 USABILITY
9 PERFORMANC
E
10 RELIABILITY
11 FUNCTIONAL
REQUIRMENTS
 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 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.

2. DATABASE:

a. All the details and orders given by customer are updated in the
database.
 3. 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. Veritcal 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. An 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 an 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 a systems. It is represented by boxed figure.
Dependencies are represented by communication assosiation.
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 assosiation.

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
reqirements, 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
decribes 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
FORM 1
FORM 3
FORM 4
'##ModelId=4D47C9B100EA
Private address As Variant
'##ModelId=4D47C9B5008C
Private phone_no As Variant
'##ModelId=4D47C93A008C
Public NewProperty As placing_orders
'##ModelId=4D47C947006D
Public NewProperty2 As database3
'##ModelId=4D47C98A01E4
Public NewProperty3 As database3
'##ModelId=4D47C98D036B
Public NewProperty4 As placing_orders
'##ModelId=4D47C9C00186
Public Sub submit()
End Sub
FORM 1
SUBMIT BUTTON
Private Sub Command1_Click()
Form6.Text1.Text = Form1.sgs.Text
Form6.Text2.Text = Form1.Text2.Text
Form6.Text3.Text = Form1.Text3.Text
Form2.Show
End Sub
EXIT BUTTON
Private Sub Command2_Click()
Unload Me
End Sub
PLACING ORDERS
Option Explicit
'##ModelId=4D47C9FE00AB
Private select_goods As Variant
'##ModelId=4D47C93D031C
Public NewProperty As database3
'##ModelId=4D47C9910222
Public NewProperty2 As database3
'##ModelId=4D47CA0E0232
Public Sub submit()
End Sub
FORM 2
SUBMIT COMMAND
Private Sub Command1_Click()

Dim p As placing_orders
Set p = New placing_orders
p.submit
End Sub
Form8.Text12.Text = Form3.Text2.Text
Adodc1.Recordset.Update
End Sub

RESULT
Thus the project stock maintenance system using Rational Rose Software and
implement the software in Visual Basic is executed successfully.
EXNO 5 ONLINE COURSE RESERVATION SYSTEM

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.

SYSTEM REQUIEMENT SPECIFICATION

GLOSSARY
Generally a glossary is performed to define the entire domain used in the problem.
It defines about the storage items that are familiar to the uses it provided these
definitions and information about the attribute we are using in the particular project
to the use,

DEFINITIONS
The glossary contain the working definition for the key concept in the course
registration system

COURSE
The course which are offered by the institution

COURSE CATALOG
The un a bridged for all the course offered by the institution.

GRADE
The ranking of a particular student for a particular course offered

PROFESSOR
A person who reaches the course

CERTIFICATE
DOCUMENTATION FOR USE CASE DIAGRAM
The use case diagram in the course registration system illustrates the sequence of
steps followed in the system related to the actions of the system

LOGIN
This usecase gives a 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 usecase given the marks scored by the system

MAINTAIN PROFESSOR INFORMATION

This usecase maintain the information about professor in the system

MAINTAIN STUDENT INFORMATION

This usecase maintain the information about the professor in the system

CLOSE REGISTRATION
This usecase 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, professor record all admistration 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 mark 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 usecase

b. In the registration for the course usecase 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 usecase and registration for the
course

e. In the record usecase submit grade at the end of each course each
student will be asked to write a test.The result will evaluavate for the
issue of grade sheet and the grade are submitted
COLLOBORATIION 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

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

b. Getting the catalog to now about the course

c. Selecting the course to study

d. The final step is to register for the selected course

e. In this submit garde usecase the sequence of step is:

f. At the end of the course the student will write a test

g. The test marks is validated to issue grade sheet

h. The certification is done to the student for the particular courses.

i.
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 theobject oriented technique. State diagram
are drawn for a single class to show to the lifetime behaviour of a single objects
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

SOFTWARE DEVELOPMENT AND DEBUGING

 a. Using rational rose software the software development and debugging
is done

b. This gives the over view of the project by the generation of defition and
implementation of packages classes with all the relationship method
and constructor

c. We debug the diagram using log file and rectify the immoral
relationship that exist among them and finally produce the project
perfect diagram which gives exact print of the project
d.
SOFTWARE TESTING

a. In this step we prepare there plan for testing the diagram

b. We perform the validation for the various data involved into the
projects

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 a 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
and ordinary model elements. All uml models and diagrams are organized into
package. A package diagram in unified modeling language that depicts the
dependencies between the packages that make up a model. A Package Diagram (PD)
shows a grouping of elements in the OO model, and is a Cradle extension to UML.
PDs can be used to show groups of classes in Class Diagrams (CDs), groups of
components or processes in Component Diagrams (CPDs), or groups of processors
in Deployment Diagrams (DPDs).
There are three types of layer. They are

a. User interface layer

b. Domain layer

c. Technical services layer

DOCUMENTATION OF PACKAGE DIAGRAM

• The three layer of online course reservation are user interface layer, domain layer
and technical service layer
FORM 4

FORM 5
SOURCE CODE
FORM1
Private Sub Command1_Click()
Dim log As student1
Set log = New student1
log.study
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
FORM2
Private Sub Command1_Click()
Dim course As college
Set course = New college
course.admission
End Sub
Private Sub Command2_Click()
End
End Sub
FORM3
Private Sub Command1_Click()
Text1.Text = Text1.Text - 1
Private marketing As Variant
'##ModelId=4D18FD8A01C5
Private management As Variant
'##ModelId=4D22343E03A9
Private mcourseObject As New course
'##ModelId=4D22343E03C8
Private Property Set course_(ByVal RHS As college)
Set mcourseObject. = RHS
End Property
'##ModelId=4D22343F000F
Private Property Get course_() As college
Set course_ = mcourseObject.
End Property
MECHANICAL
Option Explicit
'##ModelId=4D18FE4B001F
Implements course
'##ModelId=4D18FD28036B
Private Lathe As Variant
'##ModelId=4D18FD3F0119
Private workshop As Variant
'##ModelId=4D22343F0157
Private mcourseObject As New course
'##ModelId=4D18FD4500AB
Public Sub production()
End Sub
'##ModelId=4D22343F0167
Private Property Set course_NewProperty(ByVal RHS As college)
Set mcourseObject.NewProperty = RHS
End Property
'##ModelId=4D22343F01A5
Private Property Get course_NewProperty() As college
Set course_NewProperty = mcourseObject.NewProperty
End Property
STUDENT
Option Explicit
'##ModelId=4D223035000F
Private name As Variant
'##ModelId=4D2230380222
Private rollno As Variant
'##ModelId=4D22303C0242
Private mark As Variant
'##ModelId=4D22304102CE
Public Sub study()
If Form1.Text1.Text = "palani" And Form1.Text2.Text = "123456" Then
MsgBox "login successful"
Else
MsgBox "invalid password"
End If
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.
EXNO:6 E-TICKETING

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 reserved for the
flight ticket.

d. First the applicant wants to login to the database after that the person
wants to fill their details.

e. Then the database will seach for ticket or else the person will
cancelled the ticket if he/she no need.

SRS DOCUMENT
S.NO TABLE OF CONTENTS
 b. E-Ticketing DataBase-verify the login and filling the details and
selected 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 its verify the username
and password.

b. If the password and username are correct then applicants are used to
login the filling details.

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 display the ticket information.

 f. Incase 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 behaviour of the system.
• First state is login where the applicant login to the E-Ticketing system.

• The next state is filling details the applicant 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 an rounded box containing
the name of the operation.

DOCUMENTATION OF ACTIVITY DIAGRAM

This activity diagram describes the behaviour of the system.
 a. First state is login where the applicant login to the E-Ticketing
system.

b. The next state is filling details the applicant are used to fill the form.

c. Then applicant used to selecting the flight.

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

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

FORMS
FORM1

FORM2
FORM3

FORM4
FORM5

SOURCE CODE
FORM3
Private Sub Command1_Click()
Adodc1.Recordset.AddNew
End Sub
Private Sub Command2_Click()
Adodc1.Recordset.MoveNext
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.MovePrevious
End Sub
If txtus.Text = "admin" Then
If txtpass.Text = "admin" Then
MsgBox "login sucess"
Form1.Show
Unload Me
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
username and password.", vbCritical, "Wrong Entry"
txtus.Text = ""
txtpass.Text = ""
End If
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
FORM5
Private Sub Command1_Click()
Adodc2.Recordset.AddNew
End Sub
Private Sub Command2_Click()
Adodc2.Recordset.MoveNext
End Sub
Private Sub Command3_Click()
Adodc2.Recordset.MovePrevious
End Sub
Private Sub Command4_Click()
Adodc2.Recordset.MoveLast
End Sub
Private Sub Command5_Click()
Adodc2.Recordset.Update
End Sub
Private Sub Command6_Click()
Adodc2.Recordset.Delete
End Sub
Private Sub Command7_Click()
Unload Me
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 EMPLOYEE MANAGEMENT SYSTEM

AIM
To develop a project employee 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 employee 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 employee management system are
described sequentially through following steps,

• The CEO login to the employee 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.

SOFT REQUIREMENT SPECIFICATION:

S.NO TABLE OF CONTENTS

1 INTRODUCTION

1.7 Purpose

1.8 Scope

1.9 References

1.10 Technology To Be Used

1.11 Tools Be Used

1.12 Overview
2 OVERALL DESCRIPTION
2.1 Product Perspective
2.2 Functionality
2.3 Usability
2.4 Performance
2.5 Reliability
2.6 Assumption and Dependencies

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 ToolsBeUsed 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 sometime.

2.3 Usability
The User interface makes the employee Management System to be efficient.
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 employee 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
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
FORM 1
FORM 4

FORM 5
FORM 6
SOURCE CODE
Class modules
CEO
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=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 database
DATABASE:
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
Form6.Hide
Form2.Show
End sub

RESULT
Thus the project is to develop an EMPLOYEE MANAGEMENT SYSTEM 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

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.
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 thesignature
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.
• The Technical service layer – To verify a required Customer Signature.

COMPONENT DIAGRAM
The component diagram is represented by figure dependency and it is a graph of
design of figure dependency.

DOCUMENTATION OF COMPONENT DIAGRAM

In this diagram there link between the actor 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:
FORM 1
FORM 2

FORM 3
FORM 4

SOURCE CODE
CARD READER:
Option Explicit
'##ModelId=4D4136130261
Private machine number As Variant
'##ModelId=4D413619031C
Private software As Variant
'##ModelId=4D4136680177
Private company_name As Variant
Dim 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 vendors
Dim 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_reader
Dim v2 As card_reader
'##ModelId=4D4135BA03A9
Public Sub make_bill()
Form3.Show
End Sub
'##ModelId=4D4135CA029F
Public Sub delivery_item()
Form3.Show
End Sub
Form1:
Dim r1 As customers
Private Sub Command1_Click()
Set r1 = New customers
r1.purchase_item
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Public Sub purchase_item()
Form2.Show
End Sub
Form2:
Dim r2 As vendors
Private Sub Command1_Click()
Set r2 = New vendors
r2.delivery_item
End Sub
Private Sub Command2_Click()
Form1.Show
End Sub
Form3:
Dim r3 As card_reader
Private Sub Command1_Click()
Set r3 = New card_reader
r3.make_transaction
End Sub
Public Sub make_transaction()
Form4.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

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

Ebook 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 SPECIFICATION

1 INTRODUCTION
2 OBJECTIVE
3 OVERVIEW
4 GLOSSARY
5 PURPOSE
6 SCOPE
7 FUNCTIONALITY
8 USABILITY

9 PERFORMANCE
10 RELIABILITY
11 FUNCTIONAL
REQUIREMENTS
DOCUMENTATION OF USE CASE DIAGRAM

The actors in this use case diagram are Supplier, Store Keeper and Database. The
usecases 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 ebook 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
is 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. Veritcal 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 are 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 ebook 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 ebook management system.
• The next state is check the list of books in order.
• 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 an rounded box
containing the name of the operation.
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 are verified and is given in a ordered format.
• The needed book is selected.
• Enter your account details and purchase the book .

COMPONENT DIAGRAM
The component diagram's main purpose is to show the structural relationships
between the components of a 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 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.

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 ebook management
system. The activities are books are purchased from the websote
• Technical services layer: the update the account details and buy the book by
payment through the account

FORMS
FORM 1
FORM 2

FORM 3
SOURCE CODE
CUSTOMER
FORM1
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 Sub
BOOK
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
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.
EXNO: 10 ONLINE RECRUITMENT SYSTEM

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.

USE CASE DIAGRAM
A use case is a methodology used in system analysis to identify, clarify, and organize
system requirements. The use case is made up of a set of possible sequences of
interactions between systems and users in a particular environment and related to a
particular goal. It is represented using ellipse.Actor is any external entity that makes
use of the system being modelled. It is represented using stick figure.
DOCUMENTATION OF 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 send to the applicant by recruiter.

SELECTING APPLICANT
This sequence diagram shows steps to show

• The applicant attend aptitute 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.

DOCUMENTATION OF STATE CHART DIAGRAM
This state diagram describes the behaviour of the system.

• First state is login where the applicant login to the recruitment system.

• The next state is register where the applicant register 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 an 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 send 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.
FORMS
FORM1

FORM2
FORM3

FORM4
FORM5

FORM6
SOURCE CODE
APPLICANT
Option Explicit
'##ModelId=4D5CED1B0324
Private UserName As String
'##ModelId=4D5CED1B0325
Private Password As String
'##ModelId=4D5CED1B0326
Private Phoneno As Integer
'##ModelId=4D5CED1B0327
Private Address As String
'##ModelId=4D5CED1B0328
Private Name As String
'##ModelId=4D5CED1B0313
Public NewProperty As database1
'##ModelId=4D5CED1B032B
Public NewProperty2 As applicant1
'##ModelId=4D5CED1B0321
Public Sub register()
End Sub
'##ModelId=4D5CED1B0322
Public Sub login()
End Sub
'##ModelId=4D5CED1B0323
Public Sub applicant_details()
End Sub
Recruiter1
Option Explicit
'##ModelId=4D5CED1B0335
Private Name As String
'##ModelId=4D5CED1B0336
Private Designation As String
'##ModelId=4D5CED1B0337
Private Phoneno As Integer
'##ModelId=4D5CED1B0338
Private Marks_in_Aps As Integer
'##ModelId=4D5CED1B0339
Private Marks_in_tech As Integer
'##ModelId=4D5CED1B033C
Public NewProperty22 As database1
'##ModelId=4D5CED1B032B
Public NewProperty2 As applicant1
'##ModelId=4D5CED1B0331
Public Sub Aps_test()
End Sub
'##ModelId=4D5CED1B0332
Public Sub Aps1_test()
End Sub
'##ModelId=4D5CED1B0333
Public Sub Tech_Round()
End Sub
'##ModelId=4D5CED1B0334
Public Sub Tech1_Round()
End Sub
Database1
Option Explicit
'##ModelId=4D5CED1B0313
Public NewProperty As database1
'##ModelId=4D5CED1B033C
Public NewProperty22 As database1
'##ModelId=4D5CED1B030E
Public Sub apps_details()
End Sub
'##ModelId=4D5CED1B030F
Public Sub tech_details()
End Sub
'##ModelId=4D5CED1B0310
Public Sub selected_applicant_details()
End Sub
FORM1
Private Sub Command1_Click()
Set obj1 = New applicant1
obj1.login
End Sub
Public Sub login()
If Form1.Text1.Text = "recruit" And Form1.Text2.Text = "recruit" Then
MsgBox "login successfully"
Form2.Show
Else
MsgBox "invalid password"
End If
End Sub
FORM2
Private Sub Command1_Click()
Dim obj2 As applicant1
Set obj2 = New applicant1
obj2.register
End Sub
Public Sub register()
Form3.Show
End Sub
FORM3
Private Sub Command1_Click()
Dim obj3 As applicant1
Set obj3 = New applicant1
obj3.applicant_details
End Sub
Public Sub applicant_details()
If Form3.Text1.Text = "" Then
MsgBox "Enter the name"
ElseIf Form3.Text2.Text = "" Then
MsgBox "Enter the Address"
ElseIf Form3.Text3.Text = "" Then
MsgBox "Enter the Phoneno"
ElseIf Form3.Text4.Text = "" Then
MsgBox "Enter the Educational qualification"
ElseIf Form3.Text5.Text = "" Then
MsgBox "Enter the Percentage"
End If
If Val(Form3.Text5.Text) < 75 Then
MsgBox "you are not up to the qualification.you are not registered"
Else
MsgBox "you are registered successfully"
Form4.Show
End If
End Sub
End Sub
FORM6
Private Sub Command1_Click()
Dim obj8 As recruiter1
Set obj8 = New recruiter1
obj8.Tech_Round
End Sub
Private Sub Form_Load()
Dim obj7 As database1
Set obj7 = New database1
obj7.selected_applicant_details
End Sub
Public Sub selected_applicant_details()
Form6.Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Documents and Settings\Student\My Documents\recu1.mdb;Persist
Security Info=False"
Form6.Adodc1.RecordSource = "select * from tech"
Set Form6.DataGrid1.DataSource = Form6.Adodc1
End Sub
FORM7
Private Sub Form_Load()
Dim obj0 As recruiter1
Set obj0 = New recruiter1
obj0.Tech1_Round
End Sub
Public Sub Tech1_Round()
Form7.Adodc1.ConnectionString = "Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=C:\Documents and Settings\Student\My Documents\recu1.mdb;Persist
Security Info=False"
Form7.Adodc1.RecordSource = "select * from tech_query"
Set Form7.DataGrid1.DataSource = Form7.Adodc1
End Sub

RESULT
Thus the project to develop online recruitment system using Rational Rose
Software and to implement the project in Visual Basic is done successfully.
EXNO:11 FOREIGN TRADING SYSTEM

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 is 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.
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, accountno as

attributes. The operations performed are login, sourcing, placeorder, 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 accountno , 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 a parallel
vertical lines called lifelines. There are two dimensions in this diagram

1. Vertical dimension-represents time.

2. Horizontal dimension-represent different object

TraderTraderAdministratorAdministratorDatabaseDatabaseLoginSourcingPlace
orderUpdate orderPay 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 pay 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 come 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. They are

• User interface layer

• Domain layer

• Technical services layer

User interface layer

FORM2

FORM3
FORM7

SOURCE CODE
ACCOUNT
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.Show
End 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;Data
Source=C:\Documents and Settings\Student\Desktop\datum\db.mdb;Persist
Security Info=False"
Form5.Adodc1.RecordSource = "select itemname from itemtable"
Set Form5.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
Option Explicit
'##ModelId=4D6495B600CB
Private name As String
'##ModelId=4D6495BC0213
Private id As Integer
'##ModelId=4D6495CA0251
Set a5 = New trader
a5.pay
End Sub
Private Sub Form_Load()
Dim a As administrator
Set a = New administrator
a.bill1
End Sub
FORM5
Private Sub Command1_Click()
Dim a2 As trader
Set a2 = New trader
a2.sourcing
End Sub
Private Sub Form_Load()
Dim a0 As administrator
Set a0 = New administrator
a0.traceorder
End Sub
FORM6
Private Sub Command1_Click()
Dim a6 As trader
Set a6 = New trader
a6.logout
End Sub
FORM7
Private Sub Command1_Click()
Dim a3 As item
Set a3 = New item
a3.getdoll
Dim x2 As administrator
Set x2 = New administrator
x2.paybill2
End Sub
Private Sub Command2_Click()
Dim a4 As trader
Set a4 = New trader
a4.placeorder
End Sub
FORM8
Private Sub Command2_Click()
Dim a8 As trader
Set a8 = New trader
a8.pay
End Sub
Private Sub Form_Load()
Dim a7 As administrator
Set a7 = New administrator
a7.bill2
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.
EXNO: 12 CONFERENCE MANAGEMENT SYSTEM

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.

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 sumbit the paper.

• The reviewer reviews the paper and sends acknowlegement to the candidate.

• The candidate submits revised and camera ready paper.

• This candidate will registers their detials.

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

ACTIVITY DIAGRAM
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified
Modeling Language, activity diagrams can be used to describe the business and
operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control. An activity is shown as an rounded box containing
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 proces 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 fulfill
application 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
FORM1

FORM2
FORM4

FORM5
End Sub
DATABASE
Option Explicit
'##ModelId=459806A30280
Public NewProperty As candidate1
'##ModelId=4598060A02BF
Public Sub verify_the_ID()
End Sub
'##ModelId=4598062A01F4
Public Sub allow_to_the_reviewer()
End Sub
REVIEWER
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
Call a.login
End Sub
Private Sub Command2_Click()
Unload Me
End Sub
Public verify_the_ID()
Form2.Show
End Sub
FORM 4
Private Sub Command1_Click()
Dim a As database1
Set a = New database1
Call a.verify_the_ID
End Sub
Public Sub verify_the_ID()
Form2.Show
End Sub
FORM 5
Private Sub Command1_Click()
Dim a As database1
Set a = New database1
Call a. verify_the_ID
End Sub
Public Sub verify_the_ID()
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.
EXNO:13 BUSINESS PROCESS OUTSOURCING MANAGEMENT
SYSTEM

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.

PROBLEM STATEMENT
In this BPO inbound system , the process undergoing is that the agent tries to sell
his product so that the agent gets the details of the customer from the database and
pitches about his product and makes the sales successful. The communication is
done through the telephone. Telephone is the major component used for this
customer satisfaction service. The steps are as follows:

• The agent login to the website and enters the username and password .It checks
for authorization .

• If the username and password is correct ,it allows the agent to get the details of
the customer from the database.

• Now the agent makes the call to the customer and pitches about the product.

• If the customer is satisfied ,agent sells the product else disconnects the call.

• Agent proceeds with the another call.

SOFTWARE REQUIREMENT SPECIFICATION

1 INTRODUCTION
2 OBJECTIVE
3 PURPOSE
4 SCOPE
5 GLOSSARY
6 OVERVIEW
7 OVERALL DESCRIPTION
8 REFERENCES
9 FUNCTIONALITY
10 USABILITY
11 PERFORMANCE
12 SYSTEM ENVIRONMENT
13 FUNCTIONAL
REQUIREMENTS

1. INTRODUCTION
BPO is typically categorized into back office outsourcing-which includes internal
business functions such as human resources or finance and accounting, and front
office outsouring-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 neighbouring country is called
nearshore 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.

2. 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 campanies 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.

3. SCOPE
Developing a good BPO management system.BPO is a way in which it helps to
increase companys 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.
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
comparment the attributes and the bottom compartment with operations.

DOCUMENTATION OF CLASS DIAGRAM

This class diagram has three classes process agent, customer and database.

• Agent – is the class name. Its attributes are username, password, name, phoneno
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, phoneno, 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
• 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 no doubt 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 a systems. It is represented by boxed figure.
Dependencies are represented by communication assosiation.

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
component comes 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 assosiation.

DOCUMENTATION OF DEPLOYMENT DIAGRAM

FORM 2
SOURCE CODE:
FORM 1:
customer
Option Explicit
'##ModelId=4D62041B005D
Private NAME As Variant
'##ModelId=4D62041F01F4
Private address As Variant
'##ModelId=4D6204240119
Private phone_no As Variant
'##ModelId=4D6205B7008C
Public NewProperty As process_agent
'##ModelId=4D62042F0271
Public Sub attends_call()
End Sub
'##ModelId=4D62043B036B
Public Sub asks_query()
Public Sub pitches_about_product()
Form2.Show
End Sub
'##ModelId=4D62040401A5
Public Sub make_sales()
If (Form2.Combo1.Text = "Anand") Then
Form3.Show
End If
If (Form2.Combo1.Text = "Brindha") Then
Form4.Show
End If
If (Form2.Combo1.Text = "Rubini") Then
Form5.Show
End If
End Sub
'##ModelId=4D620409030D
Public Sub ends_the_call()
Form2.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 design an object oriented model for Library Management System using Rational
Rose software and to implement it using VB.

PROBLEM STATEMENT
The library management system is a software system that issues books and magazines
to registered students only. The student has to login after getting registered to the
system. The borrower of the book can perform various functions such as searching for
desired book, get the issued book and return the book.

OVERALLDESCRIPTION

TheLibrary
MaintenanceSystemisanintegratedsystemthathasfourmodulesaspartofit.The four
modulesare,

1) Registrationforthenewuser:Inthismodule,theusercanregisterasnewuserintheda
tabase.
2) IssueBook:Inthismodule,itshowsthedetailsofissuedbooktotheexistinguserandits
howsthe available booktothe particular user.
3) ReturnBook:Inthismodule,showsandmodifythedatabaseandstorethereturnbook
fromtheuserand showsthefineamount.

SOFTWAREREQUIRMENTS

 MicrosoftVisual Basic6.0
 RationalRose
 MicrosoftAccess

HARDWAREREQUIRMENTS

 128MB RAM
 PentiumIIIProcessor
USECASE DIAGRAM:
EX.NO.15 STUDENT INFORMATION SYSTEM

DATE :

AIM
To design an object oriented model for Student information system using Rational Rose
software.

PROBLEM STATEMENT

The student must register by entering the name and password to login the form. The
admin select the particular student to view the details about that student and maintaining
the student details. This process of student information system is described sequentially
through following steps. The student registers the system. The admin login to the student
information system. He/she search for the list of students. Then select the particular
student. Then view the details of that student. After displaying the student details then
logout.
CLASS DIAGRAM
The class diagram is the graphical representation of all classes used in the system. The
class diagram is drawn as rectangular box with three components or compartments like
class name, attributes and operations. The student information system makes use of the
following classes like student, staff, system, DBA and server.
COLLABORATION DIAGRAM

A Collaboration diagram represents the collaboration in which is a set of objects

related to achieve a desired outcome. In collaboration, the sequence is indicated by
numbering the message several numbering schemes are available. Login, request access,
allow access, display, view details, logout, login, request access, allow access, display,
enter profile, enter mark, provide data, logout, store data, update data.
SEQUENCE DIAGRAM

A Sequence diagram represent the sequence and interaction of a

given usecase or scenario. Sequence diagram capture most of the information
about the system. Here the sequence starts between the student and the
system. The second half of interaction takes place between staff and system
then by police and followed
 by database. The student first login to the system and then view the details of
the details. Staff login to the system enter mark and enter the details of the
student. DBA store and update the details of the student.

COMPONENT DIAGRAM

Component diagram carries the major living actors of the system.

The component diagram main purpose is to show thestructural relationship
between components of the system.The main component of the system is
student information system and the other components of the system are
student, staff and DBA.

USE CASE DIAGRAM

Use case diagram is a graph of actors, a set of use cases, association between the
actors and the use cases and generalization among the cases. Use case diagram is a list of
actions or events. Use case diagram was drawn to represent the static design view of the
system. Steps typically defined the interactions between a role and a system to achieve a
goal. The use case diagram consists of various functionality performed by the actors like
student, staff, system, DBA and server. The use case diagram consists of various
functionality like login, display, enter profile, enter mark, view details, update details,
allow access, request access, store details, logout.
DEPLOYMENT DIAGRAM

Deployment diagram shows the configuration of runtime processing elements and the
software components processes and objects that live in them. Component diagram are
used in conjunction with deployment diagram to show how physical modules code are
distributed on various hardware platform. The processor node in the system is student
information system and the execution environment nodes or device nodes are student,
staff and DBA.
STATE CHART DIAGRAM

A State chart diagram is also called as state machine diagram. The state chart contains
the states in the rectangular boxes and the states are indicated by the dot enclosed. The
state chart diagram describes the behavior of the system. The state chart involves six
stages such as login, enter mark, enter profile, view details, provide details, update
details, store details and logout.
ACTIVITY DIAGRAM

Activity diagram are graphical representation of stepwise

activities and actions with support for choice, interaction and
concurrency. Here in the activity diagram the student login to the system
and view the details of the student. The staff login to the system for
entering the student details and update the details in the database. The
final interaction is the DBA store the details of the student.
IMPLEMENTATION:
Form 1:

Form 2:
Form 3:

Form 4:
Form 9

CODING:
Form1:
Private Sub Command1_Click()
Form2.Show
Form1.Hide
End Sub
Form 2:
Private Sub Command1_Click()
If (Text1.Text = "admin" And Text2.Text = "123") Then
MsgBox "login successful"
Form3.Show
Form2.Hide
Else
MsgBox "invalid"
End If
End Sub
Private Sub command2_click()
Unload Me
End Sub
Form 3:
Private Sub Command1_Click()
Form4.Show
End Sub

Private Sub command2_click()

Form7.Show
End Sub
Form 4:
Private Sub Command1_Click()
Form5.Show
End Sub
Private Sub command2_click()
Form6.Show
End Sub
Private Sub command3_click()
Form8.Show
End Sub
Private Sub Command4_Click()
Form9.Show
End Sub
Form 5:
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub command2_click()
Data1.Recordset.Delete
End Sub
Private Sub command3_click()
Data1.Recordset.Update
End Sub
Private Sub Command4_Click()
Unload Me
End Sub
Form 6:
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub command2_click()
Data1.Recordset.Delete
End Sub
Private Sub command3_click()
Data1.Recordset.Update
End Sub
Private Sub Command4_Click()
Unload Me
End Sub
Form 7:
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub command2_click()
Data1.Recordset.Delete
End Sub
Private Sub command3_click()
Data1.Recordset.Update
End Sub
Private Sub Command4_Click()
Unload Me
End Sub
Form 8:
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub command2_click()
Data1.Recordset.Delete
End Sub
Private Sub command3_click()
Data1.Recordset.Update
End Sub
Private Sub Command4_Click()
Unload Me
End Sub
Form 9:
Private Sub Command1_Click()
Data1.Recordset.AddNew
End Sub
Private Sub command2_click()
Data1.Recordset.Delete
End Sub
Private Sub command3_click()
Unload Me
End Sub

RESULT

Thus the various UML diagrams for student information

system were drawn and code was generated successfully.