0% found this document useful (0 votes)

295 views257 pages

Ooad Lab Material

The document describes a project to develop a passport automation system and draw UML diagrams. It includes: 1) An overview of the problem statement and goals of automating the passport application process and reducing manual work. 2) Details of the project plan involving applicants filling an online form, verification by passport administrators and police, and issuance of passports. 3) UML diagrams created using Rational Rose including use case, class, sequence, collaboration, statechart, activity, component, deployment, and package diagrams. 4) Screenshots and source code for forms and modules to implement the passport automation system.

Uploaded by

Elakkiya E

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

295 views257 pages

Ooad Lab Material

Uploaded by

Elakkiya E

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as DOCX, PDF, TXT or read online on Scribd

You are on page 1/ 257

EX.

NO:1
DATE: PASSPORT AUTOMATION SYSTEM

AIM:

To develop mini project on passport automation system and to draw UML

diagrams using Rational Rose.

PROBLEM STATEMENT:

 Passport automation system is used in effective manner of passport to all of the

applicant.This system reduces the manual work instead of applying passport in
office and it also reduces the time complexity.
 The scope of passport automation system is to get the online registration form
with details such as name, address, date of birth etc..which is filled by
applicant. This is the first step in passport automation system.
 After the first step the information is forwarded to passport admin and then
passport admin verifies the applicant details.If applicant details are invalid
paassport is rejected.The regional admin verifies the details submited by
passport admin.The passport admin request the police for enquiry.After police
enquired the information is send to passport admin.
 And finally passport admin issues the passport to applicant.

PROJECT PLAN:

In passport automation system initially the applicant fill the registration

process. Then it is forwarded to passport admin for verification. If verification
process is done it is send to regional admin for further verification and is returned to
passport admin. The passport admin request police for enquiry and police enquires
1
the applicant and report is send to passport admin. Finally passport admin issues the
passport to applicant.

USE CASE DIAGRAM:

The use cases are set of scenarios to guide together by a common user goal.
A scenario is a sequence of steps describing an interaction betweeen user and their
system. Use case diagram is a visual representation of what the application wants the
system to do.

CLASS DIAGRAM:

The class diagram is a static diagram. It represents the static view of application.
Class diagram is not only used for visualising, describing and documenting different
aspects of system but also for constructing executable code of software aplication.

2
SEQUENCE DIAGRAM:

Sequence diagram is a most common kind of interacton diagram which focuses on

message exchange between a number of life lines. Sequence diagram describes
interaction by focusing on sequence of messgaes exchanged.

3
COLLABORATION DIAGRAM:

Collaboration diagram describes the interaction among objects in terms of

sequence messages. It represents the combination of information taken from class,
sequence and use case diagram describing both static structure and dynamic behaviour of
system.

7. verify details
4. verify the details

1. login 6. s end details

2. give details regional
applicant pas s port admin
admin
8. s end verification
14. is s ue pas sport
3. s tore details
5. update the details
9. update the details
13. update the details

12. send verification

10. send details

11. verify the details

databas e
police

STATECHART DIAGRAM:

State chart diagram model the dynamic behaviour of individual classes or

may other kind of object. They show the sequence of states that an object goes through,
the events that cause transition from one state to another .

ACTIVITY DIAGRAM:

Activity diagram is UML behaviour diagram which shows the flow of control or
objecct flow with emphasis on sequence and conditions of flow. The actions coordinate

4
by activity models can be initiated because other actions finish executing because objects
and data become available or because some even external to the flow occur.

regis tration

applicant form

enquiry verification paym ent

getting the
pas s port

COMPONENET DIAGRAM:

Component diagram provides a physical view of component model. A component

diagram shows the organizations and dependencies among software components
including source code components binary code components and executable components.
These diagrams also show the externally visible behaviour of components by displaying
interfaces of components.

5
passport automation
system

applicant

passport police
regional
admin admin

DEPLOYMENT DIAGRAM:

Deployment diagram show the physical configuration of software and hardware. It

shows how and where the system will be deployed. Physical machine sand processors are
reflected as nodes and internal construction can be embedding nodes or artifacts.
Artifacts are allocated to nodes to model the system deployment.

passport
auto...

update

registrati check validatio

on status verificati n
on

PACKAGE DIAGRAM:

Package diagram in UML depicts the dependencies between the packages that
make up a model. Package is a namespace used to group together elements that are
semantically related and might change together. It is a general purpose mechanism to
organize elements into groups to provide better structure of the system model.

6
us er interface

vis ual bas ic

web page

domain

pas s port adm in regional admin police

technical service

databas e

IMPLEMENTATION:
FORM 1:

7
FORM 2:

FORM 3:

8
FORM 4:

FORM 5:

9
FORM 6:

SOURCE CODING:
FORM 1:
Private Sub Command1_Click()
Me.Hide
Form3.Show
End Sub
Private Sub Command2_click()
Me.Hide
Form6.Show
End Sub
Private Sub Command3_Click()
Unload Me
End Sub
FORM 2:
Private Sub Command1_Click()
Me.Hide
Form2.Show

10
End Sub
Private Sub Command2_click()
Me.Hide
Form4.Show
End Sub
Private Sub Command3_Click()
Me.Hide
Form1.Show
End Sub
FORM 3:
Private Sub Command1_Click()
Adodc1.Recordset.AddNew
MsgBox "submitted successfully"
End Sub
Private Sub Command2_click()
Me.Hide
Form1.Show
End Sub
FORM 4:
Private Sub Command1_Click()
Me.Hide
Form3.Show
End Sub
Private Sub Command2_click()
Dim As Integer

11
s = Text1.Text
Adodc1.Recordset.Find "[id]=" & s
If Adodc1.Recordset.EOF Then
MsgBox "It's not found"
End If
Else
MsgBox "Its found"
End If
End Sub
FORM 5:
Option Explicit
Public Loginsucceeded As Boolean
Private Sub Command1_Click()
Loginsucceeded = False
Me.Hide
Form1.Show
End Sub
Private Sub Command2_click()
If Text2 = "admin" Then
Loginsucceeded = True
MsgBox "login succeed"
Form5.Show
Else
MsgBox "invalid password,try again!!! login"
Me.Show

12
End If
End Sub
FORM 6:
Private Sub Command1_Click()
Me.Hide
Form1.Show
End Sub
Private Sub Command2_click()
Dim s As Integer
s = InputBox("enter the id to search")
Adodc1.Recordset.MoveFirst
Adodc1.Recordset.Find "[id]=" & s
If Adodc1.Recordset.EOF Then
MsgBox "it's not found"
Else
MsgBox "its found"
End If
End Sub
Private Sub Command3_Click()
Adodc1.Recordset.Update
End Sub

RESULT:
Thus the application program for passport automation system is created
successfully and UML diagrams were drawn using rational rose software.

13
EX NO:2 BOOK BANK MANAGEMENT SYSTEM
DATE:
AIM:

To draw the UML diagrams and to implement coding for book bank management
system.

PROBLEM STATEMENT:

Book bank management system is where the books can be collected every semester
and must be returned at the end of the semester. The system must have some options for
new member to enrol 1 for membership by paying deposit. A provision for getting six or
seven books per semester. Membership can be renewed by using the registered number.
The deposit must be refunded on termination of membership. A database must be
maintained to guide the issues to track the details of the student. Search option must be
provided so that the member can search for the availability of the particular books.

MODULE DESCRIPTION:

MODULE 1: REGISTRATION

The user or the student must register first by using his\her password and the
following user id and then the validity of the password is checked. If the user id and the
password is correct then allow issue or else reject.

MODULE 2: SEARCH FOR BOOKS

Allow the user to search for the books that he\she requires. Then make request for
display. Then display the following book details.

MODULE 3: PREVIOUS BOOK HISTORY

14
Check out how many books are allowed for a person to borrow. If the number of
books allowed less than the number books borrowed then allow the user to borrow. I f it
is in reverse then reject.

MODULE 4: CALCULATE FINE AMOUNT

If the book is not returned within the due date then calculate the fine
amount to be paid. If the book is returned within the due date then no need to calculate
the fine amount.

MODULE 5: DISPLAY FINE AMOUNT

Finally display the fine amount to be paid by the borrower.

MODULE 6: LOGOUT

The user must log out from the book bank after borrowing\returning the book.

DESIGN PHASE:

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.

15
Name College

Dept

No.of books per sem

Registration

Book bank
manager

Inital reg payment

Cash

By book name

Student Search

By author name
<<extend>>
Book

<<extend>>

Not Available
Available
PG Student UG Student

Membership status

Issue book

CLASS DIAGRAM:

A class diagram in the unified modelling 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.

16
SEQUENCE DIAGRAM:

A sequence diagram in Unified Modelling 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.

17
member administrator database

1: register

2: checks for validity

3: Issue/reject

4: login

5: search for books

6: make request for display

7: display details

8: request for borrow

9: check previous borrowed books

10: if allowed issue books

11: return books

12: calculate fine if applied

13: provide status

14: display fine if applicable

15: display the unreturned book list

16: log out

COLLABORATION DIAGRAM:

A collaboration diagram, also called a communication diagram or interaction

diagram. A sophisticated modelling 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 behaviour of individual objects as well as the
overall operation of the system in real time

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.

18
return
books

search
books

if avail
error

if new user
new user
issue
books

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

book bank
managem... issue for
member 4th year
details

issue for issue for

issue for 2nd year
1st year 3rd year

19
DEPLOYMENT DIAGRAM:

A deployment diagram in the unified modelling 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.

BOOK BANK

issue for issue for issue for issue for member

1st year 2nd year 3rd year 4th year details

PACKAGE DIAGRAM:

A package diagram in unified modelling 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).

20
There are three types of layer. They are

1. User interface layer

2. Domain layer
3. Technical services layer

WEB

DOMAIN

BOOK UPDATE AUTHENTICATI

SEARCH ON

TECHNICAL SERVICES

DATABASE ADMIN

21
IMPLEMENTATION:
FORM 1:

FORM 2:

22
FORM 6:

FORM 8:

23
FORM 9:

FORM 10:

24
SOURCE CODE:

FORM1:

Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles Button1.Click
Form03.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Form02.Show()
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
Form09.Show()
End Sub
End Class
FORM2:
Public Class Form02
Dim loginerror As String
Public Function Login()
Dim DBConn As New ADODB.Connection
Dim User As New ADODB.Recordset
Dim Username As String
Dim userDB As String
Dim passDB As String
Dim UserFound As Boolean
DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _

25
"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")
User.Open("UserTable", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
UserFound = False
Login = False
Username = "uname = '" & txtUser.Text & "'"
Do
User.Find(Username)
If User.BOF = False And User.EOF = False Then
userDB = User.Fields("uname").Value.ToString
passDB = User.Fields("pass").Value.ToString
If userDB <> txtUser.Text Then
User.MoveNext()
Else
UserFound = True
If passDB = txtPass.Text Then
User.Close()
DBConn.Close()
Return True
End If
End If
Else
loginerror = "Invalid Password"
User.Close()
DBConn.Close()
Return False
End If
26
Loop Until UserFound = True
User.Close()
DBConn.Close()
Return False
End Function
Private Sub cmdLogin_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles cmdLogin.Click
If Login() = True Then
MessageBox.Show("Login Succesfull!!!", "Login Message")
Form05.Show()
Else
MessageBox.Show(loginerror, "Login Message")
End If
End Sub
End Class

FORM 3:

Public Class Form03

Inherits System.Windows.Forms.Form
Dim DBConn As New ADODB.Connection
Dim User As New ADODB.Recordset
Private myCommand As New ADODB.Command
Private strSQL As String
Public Function connection()
DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _
"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")
27
User.Open("Members", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
Return 0
End Function
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
connection()
strSQL = "INSERT INTO Members (sname, dob, regno, degree, semester, phone)
VALUES ('" & TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "','"
& TextBox4.Text & "','" & TextBox5.Text & "','" & TextBox6.Text & "')"
DBConn.Execute(strSQL)
MessageBox.Show("Form Submitted Successfully.")
DBConn.Close()
Form04.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
End Sub
End Class
FORM 4:
Public Class Form04
Inherits System.Windows.Forms.Form
Dim DBConn As New ADODB.Connection
Dim User As New ADODB.Recordset
Private myCommand As New ADODB.Command
Private strSQL As String
28
Public Function connection()
DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _
"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")
User.Open("UserTable", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
Return 0
End Function
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
connection()
strSQL = "INSERT INTO UserTable(uname, pass) VALUES ('" & TextBox1.Text & "','"
& TextBox2.Text & "')"
DBConn.Execute(strSQL)
MsgBox("User Created")
Form02.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
End Sub
End Class
FORM 5:
Public Class Form05
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Form06.Show()
End Sub
29
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Form07.Show()
End Sub
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
Form08.Show()
End Sub
End Class
FORM 6:
Public Class Form06
Inherits System.Windows.Forms.Form
Dim DBConn As New ADODB.Connection
Dim User As New ADODB.Recordset
Private myCommand As New ADODB.Command
Private strSQL As String
Public Function connection()
DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _
"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")
User.Open("Books", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
Return 0
End Function
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
connection()

30
strSQL = "INSERT INTO Books (memid, mname, bname) VALUES ('" &
TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "')"
DBConn.Execute(strSQL)
MessageBox.Show("Book Issued.")
DBConn.Close()
Form11.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
End Sub
Private Sub ListBox1_MouseClick(ByVal sender As Object, ByVal e As
System.Windows.Forms.MouseEventArgs) Handles ListBox1.MouseClick
TextBox3.Text = ListBox1.SelectedItem
End Sub
End Class
FORM 7:
Public Class Form07
Inherits System.Windows.Forms.Form
Dim DBConn As New ADODB.Connection
Dim User As New ADODB.Recordset
Private myCommand As New ADODB.Command
Private strSQL As String
Public Function connection()
DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _
"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")

31
User.Open("Books1", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
Return 0
End Function
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
connection()
strSQL = "INSERT INTO Books1 (memid, mname, bname) VALUES ('" &
TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "')"
DBConn.Execute(strSQL)
MessageBox.Show("Book Issued.")
DBConn.Close()
Form11.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
End Sub
Private Sub ListBox1_MouseClick(ByVal sender As Object, ByVal e As
System.Windows.Forms.MouseEventArgs) Handles ListBox1.MouseClick
TextBox3.Text = ListBox1.SelectedItem
End Sub
End Class
FORM 8:
Public Class Form08
Inherits System.Windows.Forms.Form
Dim DBConn As New ADODB.Connection
32
Dim User As New ADODB.Recordset
Private myCommand As New ADODB.Command
Private strSQL As String
Public Function connection()

DBConn.Open("Provider = Microsoft.Jet.OLEDB.4.0;" & _

"Data Source = '" & Application.StartupPath & "\Logindb.mdb'")
User.Open("Books2", DBConn, ADODB.CursorTypeEnum.adOpenStatic,
ADODB.LockTypeEnum.adLockOptimistic)
Return 0
End Function
Private Sub Button1_Click_1(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
connection()
strSQL = "INSERT INTO Books2 (memid, mname, bname) VALUES ('" &
TextBox1.Text & "','" & TextBox2.Text & "','" & TextBox3.Text & "')"
DBConn.Execute(strSQL)
MessageBox.Show("Book Issued.")
DBConn.Close()
Form11.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
End Sub
Private Sub ListBox1_MouseClick(ByVal sender As Object, ByVal e As
System.Windows.Forms.MouseEventArgs) Handles ListBox1.MouseClick
33
TextBox3.Text = ListBox1.SelectedItem
End Sub
End Class
FORM 9:
Public Class Form09
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
If TextBox1.Text = "admin" And TextBox2.Text = "root" Then
MsgBox("Login Successfull", MsgBoxStyle.DefaultButton1, "Success")
Form10.Show()
Else
MsgBox("Username or Password Error", MsgBoxStyle.DefaultButton1, "Error")
End If
End Sub
End Class

RESULT:

Thus the UML diagrams and the implementation of book bank management
system using visual basics is executed and the output is verified.

34
EX.NO:3 EXAM REGISTRATION SYSTEM
DATE:
AIM:

To draw the UML diagram and to implement coding for exam registration system.

PROBLEM DEFINITION:

The Exam Registration System helps the candidate to register their personal
details, who want to write the Indian Service Examination. This system certainly reduces
the time complexity. The duration of the project is 3 days. Registration for exams by
means of online is possible from house, college etc. Exam registration is to automate the
system, rechecking the inclusion of all required material and automatically including each
student’s details based on a number of criteria. Specific design and implementation
details will be specified in a future document. The system reduces the time taken for
processing registration.

MODULES:

Modules in this project are,

1. Student (Candidate)

2. Administrator

3. Payment Handler

MODULE DESCRIPTION:

In this project there are different modules to enable the exam registration system in
successful manner.

35
STUDENT:

The Student is the initiator of the systems. The Student enters the details for
registration. He has to login to the Exam Registration Form and should provide
mandatory information like name, age, organisation etc. The student receives hall-ticket
from the administrator after handling the payment.

ADMINISTRATOR:

The administrator is another actor who interacts with the various activity of the
system. The administrator will verify the details and confirm the student for writing
exam. The status will be updated in the database. This database is managed by
administrator.

PAYMENT HANDLER:

After the confirmation of student details by the administrator, payment handler is

responsible for collection fees. After handling the payment, he updates the status. Then
the administrator issues the hall-ticket.

DESIGN PHASE:

USE CASE DIAGRAM:

UML provides use case diagram notation to illustrate the names of use case and
author relationship between them. Use case diagram and case relationship are secondary
in use case work and use case text document.

36
CLASS DIAGRAM:

The UML class diagram is to illustrate class interfaces and their actions. They are
used for static object modelling, we have already introduced and used their UML diagram
while domain modelling.

web
s _name
Student
s _dept
name s _year
dept visits to reg s _gen
Father_name s _regno Maintains
Web_Admin
Gender
Semes ter name
capture()
year login
maintain()
Regno id

Specify_details() store maintain_web()

pay_exam_fee() Maintain_db()

update

Databas e
name
dept
father_name
Gender
s em
year
Regno
admin_name
admin_id

s tore()
update()

37
ACTIVITY DIAGRAM:

A UML activity diagram shows sequential and parallel activities in a process,

workflows, data flows and compiler algorithm.

logi n

fee paym ent and

proces s ing

dis play detai ls

and form

form
verificati on

s toring to Update
db detail s

ack trans acti on

fai lure
regi s tration
acknowl edgem ent

SEQUENCE DIAGRAM:

A Sequence diagram illustrates a kind of format in which each object interacts via
message. It is generalize between two or more specialized diagram.

38
COLLABORATION DIAGRAM:

Collaboration diagram illustrate that object interact on a graph or network format

in which object can be placed as a diagram. In collaboration diagram the object can be
placed in anywhere on the diagram. The collaboration comes from sequence diagram.

39
STATE CHART DIAGRAM:

UML state machine represents the interaction events and states of an object and
behaviour of an object in reaction to an event. Transaction shown as allows labelled with
their event. It is included with initial pseudo state and final end state.

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.

Student

Book

Hall ticket

Sys tem
adm in

40
DEPLOYMENT DIAGRAM:

A deployment diagram in the unified modelling 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.

Exam -regis tration s ys tem

Regis ter
Verify

PACKAGE DIAGRAM:

A package diagram in unified modelling language that depicts the dependencies

41
c. Technical services layer

DOMAIN

Registration Verification Fees Paym ent Issue HallTicket

Technical Service

Database

IMPLEMENTATION:

FORM 1:

42
FORM 3:

End Sub

FORM 4:

Private Sub Command1_Click()

Me.Hide

Form6.Show

End Sub

Private Sub Command2_Click()

Me.Hide

Form3.Show

End Sub

Private Sub Command3_Click()

Data1.Recordset.AddNew

End Sub

Private Sub Command4_Click()

Data1.Recordset.Delete

47
MsgBox "record is deleted"

End Sub

Private Sub Form_Load()

Combo1.AddItem "chennai"

Combo1.AddItem "trichy"

Combo1.AddItem "villupuram"

Combo1.AddItem "madurai"

Combo1.AddItem "kanci"

Combo1.AddItem "salem"

End Sub

FORM 5:

Private Sub Command1_Click()

frmLogin.Show

End Sub

Private Sub Command2_Click()

Me.Hide

Form1.Show

End Sub

Private Sub Command3_Click()

Me.Hide

Form6.Show

End Sub

48
FORM 6:

Private Sub Command1_Click()

MsgBox "transaction successfull", 1 + 64

End Sub

Private Sub Command2_Click()

If (Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "") Then

MsgBox "enter all fields"

Else

Me.Hide

Form7.Show

End If

End Sub

Private Sub Command3_Click()

Me.Hide

Form4.Show

End Sub

Option Explicit

Public LoginSucceededAs Boolean

Private Sub cmdCancel_Click()

'set the global var to false

'to denote a failed login

49
LoginSucceeded = False

Me.Hide

End Sub

Private Sub cmdOK_Click()

'check for correct password

If txtPassword = "ezhil" Then

MsgBox "login successfull"

'place code to here to pass the

'success to the calling sub

'setting a global var is the easiest

LoginSucceeded = True

Me.Hide

Else

MsgBox "Invalid Password, try again!", , "Login"

txtPassword.SetFocus

SendKeys "{Home}+{End}"

End If

End Sub

RESULT:

Thus the project for EXAM REGISTRATION SYSTEM has been successfully
executed and codes are generated.

50
EX.NO:4 STOCK MAINTENANCE SYSTEM
DATE:
AIM:

To develop the stock maintenance system using VB software and to draw UML
diagram using Rational Rose.

PROBLEM STATEMENT:

The main scope of this stock maintenance system is to maintain the stock details of
the shop and the following problems are identified below,

1.There will be major drawback in maintaining warehouse stock information.

2.Verification process will be time consuming.

3.Update details about the stock in the database.

4.Easy interface may not be obtained in current scenario.

UML DIAGRAMS:

USE CASE DIAGRAM:

The use cases are a ser of scenarios to guide together by a common user goal. A
scenario of the sequence of steps describing an interaction between a user and their
system. use case diagram is a visual representation of what of the card holder wants the
system to do.

51
ST OCK M AINT AINENCE
<<incl ude>>
\
QUALIT Y

PRODUCT DET AILS

CUST OMER

SALES DET AILS

ADMINIST RAT OR

PAYMENT DET AILS

ST OCK DET AILS

<<Extend>>

<<extend>> ONLINE
PURCHASE T HE PRODUCT
<<extend>>
DIRECT
<<extend>>
SUPPLAYER PAY T HE AMOUNT

CASH

SUPPLY T HE PRODUCT DD

CLASS DIAGRAM:

The class diagram is a static diagram. It represents the static view of an

application. Class diagram is not only used for visualizing, discribing and documenting
different aspects of a system but also for constructing executable code of the software
application.

owner
cus tom er
login
login viewing product
view product adding product detail
s electingproduct verify
bill generation
login() paym ent
s election()
true product() login()
logout() verify()
updateproductdetail()
logout()

databas e
viewing product
adding productdetail

update()
logout()

52
ACITVITY DIAGRAM:

Activity diagram is UML behaviour diagram which shows flow of control or

object flow with Emphasis on the sequence and condition of the flow. The actions
coordinated by activity models can be initiated because other actions finish executing,
because objects and data become available,or because some events external to the flow
occur.

SEQUENCE DIAGRAM:

Sequence diagram is the most common kind of interaction diagram, which

focuses on the message interchange between a numbers of lifelines. Seqeuence diagram
describes an interation by focussing on the sequence of messages that are exchanged,
along with their corresponding occurrence specifications on the lifelines.

53
COLLABORATION DIAGRAM:

A collaboration diagram describes interactions among objects in terms of

sequenced messages. Collaboration diagrams represent a combination of information
taken from class, sequence, and use case diagrams describing both the static structure
and dynamic behaviour of a system.

5: PAYMENT
COUSTO VENDER
MER

6: ISSUE PRODUCT
4: BILL GENERATION

3: SELECTING PRODUCT

8: LOGOUT
DB 7: UPDATE PRODUCT DETAIL
2: VIEW PRODUCT DETAILS
1: LOGIN

54
STATE CHART DIAGRAM:

State chart diagrams model the dynamic behaviour of individual classes or any
other kind of object. They show the sequences of states that an object goes through, the
events that cause a transition from one state to another, and the actions that result from a
state change.

CUST
LOGIN

ENTER CUST
DETAILS

SELECT
PRODUCTS

DISPLAY
PRODUCT

PURCHAS
E

UPDATE
DETAILS

VENDER

COMPONENT DIAGRAM:

Component diagrams provide a physical view of the current model. A component

diagram shows components, binary code components and executable components. These
diagrams also show the externally-visible behaviour of the components by displaying the
interfaces of the components.

55
stock maintenance
system

db details
customer (stock)
vendor

DEPLOYMENT DIAGRAM:

Deployment diagrams show the physical configurations of softwre and hardware.

A Deployment diagram shows how and where the system will be deployed. Physical
machines and processors are reflected as nodes, and the internal construction can be
depicted by embedding nodes or artifacts are As artifacts are allocated to node to model
the systems deployment, the allocated is guided by the use of deployment specifications.

STOCK
MAITAONENENCE
CUST DB

VENDE
R

PACKAGE DIAGRAM:

A package diagram in the unified modelling language depicts the dependencies

between the packages that make up a model. Package is a namespace used to group
together elements that are semantically related and might change together. It is a general
purpose mechanism to organize groups to provide better structure for system model.
56
ui

web login

dom ain

cus t-details s elect goods

m onitor harddis c keyboard

databas e

update vendor

IMPLEMENTATION:

57
SHOP DETAILS:

CUSTOMER DETAILS:

58
PRODUCT DETAILS:

ORERED DETAILS:

59
PURCHASE DETAILS:

BILL GENERATION:

60
STOCK DETAILS:

SOURCE CODE:

FORM 1:

Private Sub Command1_Click()

If (Text2.Text = "admin" And Text1.Text = "123") Then

MsgBox ("login successfully")

Form2.Show

Else

MsgBox ("login unsuccessfully")

End If

End Sub

Private Sub Command2_Click()

61
Unload Me

Form2.Show

End Sub

Private Sub Command2_Click()

Form2.Show

End Sub

Private Sub Command3_Click()

Unload Me

End Sub

Private Sub Command4_Click()

Data1.Recordset.AddNew

End Sub

63
Private Sub Command5_Click()

Data1.Recordset.MovePrevious

If Data1.Recordset.EOF() = True Then

Data1.Recordset.MoveFirst

End If

End Sub

Private Sub Command6_Click()

Data1.Recordset.MoveNext

If Data1.Recordset.EOF() = True Then

Data1.Recordset.MoveLast

End If

End Sub

Private Sub Command7_Click()

Data1.Recordset.Delete

Data1.Recordset.MoveNext

If Data1.Recordset.EOF() = True Then

Data1.Recordset1.MovePrevious

End If

MsgBox ("Order Successfully Sent")

End Sub

Private Sub Command3_Click()

Form2.Show

End Sub

If Data1.Recordset.EOF() = True Then

Data1.Recordset.MovePrevious

End If

End Sub

FORM 12:
68
Private Sub Command1_Click()

Form13.Show

End Sub

Private Sub Command2_Click()

Data1.Recordset.AddNew

End Sub

End Sub

Private Sub Command4_Click()

Data1.Recordset.Delete

Data1.Recordset.AddNew

End Sub

FORM 14:
Private Sub Command1_Click()

Form2.Show

End Sub

RESULT:

Thus the application for stock maintenance system was created successfully and
UML diagrams were drawn using rational rose software.

71
EX.NO:5 ONLINE COURSE RESERVATION SYSTEM
DATE:
AIM:

To draw the UML diagrams and to implement coding for the Online Course
Reservation System.

PROBLEM STATEMENT:

Online course reservation system is web based software that helps people to
register courses online. This course preference quickly and conveniently. Our
implementations are designed for people who wants to combine the convenience of
online reservation with hand marked assignments, personal support and feedback from
expert inductors.

PROJECT PLAN:
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.

Software Quality Attributes:

EFFICIENCY:

The system must run without any interfaces or delay and should be capable of
handling multiple users.

ASSUMPTION AND DEPENDENCIES:

72
The Online Course Reservation System assumes that the applicant and
administrator must have basic knowledge about accessing the internet.

USE CASE DIAGRAM:

The use cases are a set of scenarios to guide together by a common user goal. A
scenario is the sequence of steps describing an interaction between a user and their
system. Use-case diagram is a visual representation of what the card holder wants the
system to do.

Name
Login
Age Course

ADMIN
Sel ect course

USER

<<incl ude>>
<<extend>>
Payment
<<incl ude>>

<<extend>> <<incl ude>>

T ransaction success By credit card

T ransaction failure
By debit card

Net banki ng

update

Hal l ticket

CLASS DIAGRAM:

The class diagram is a static diagram. It represents the static view of an

application. Class diagram is not only used for visualizing, describing and documenting
different aspects of a system but also for constructing executable code of the software
application. Activity diagram is UML behavior diagram which shows flow of control or

73
object flow with

Web web_databse
name name
id id
dept dep
course course
Store_web _details
branch branch
Student
payemt_details admin_name
name visits
course_duration admin_login_id
id start_date admn_pass
dept ending_date
course
store()
branch capture() update()
update_to_admin()
select_course() Update
pay_amount()
Maintains

Admin
name
id
pass

catpure_web()
maintain_db()

SEQUENCE DIAGRAM:
Sequence diagram is the most common kind of interaction diagram, which focuses
on the message interchange between a numbers of lifelines. Sequence diagram describes
an interaction by focusing on the sequence of messages that are exchanged, along with
their corresponding occurrence specifications on the lifelines.

74
s tudent web adm in databs e

vis its

s electcours e

duration

s elect_Dept

capture

update

enters other prim ary details

capture

update

paym ent

update

COLABORATION DIAGRAM:

A collaboration diagram describes interactions among objects in terms of

student

1. visits admin
2. selectcourse
3. duration
4. select_Dept
7. enters other primary details
10. payment

11. update
8. capture
5. capture
9. update
6. update

web
databse

75
ACTIVITY DIAGRAM:
Activity diagram is UML behaviour diagram which shows flow of control or
object flow with emphasis on the sequence and conditions of the flow. The actions
coordinated by activity models can be initiated because other actions finish executing,
because objects and data become available, or because some events external to the flow
occur.

76
STATE CHART DIAGRAM:

vis it
webs ite

s elect
cours e

get details
about cours e

proceed to
paym ent

authenticati verification
on

m ake
trans action

provide hall
ticket

update db

COMPONENT DIAGRAM:

Component diagrams provide a physical view of the current model. A

component diagram shows the organizations and dependencies among software
components, including source code components, binary code components, and executable
components. These diagrams also show the externally-visible behaviour of the
components by displaying the interfaces of the components.

77
Student
System
admin

Hall ticket
Course

DEPLOYMENT DIAGRAM:
Deployment diagrams show the physical configurations of software and
hardware. A Deployment diagram shows how and where the system will be deployed.
Physical machines and processors are reflected as nodes, and the internal construction
can be depicted by embedding nodes or artifacts. As artifacts are allocated to nodes to
model the system's deployment, the allocation is guided by the use of deployment
specifications.

Online Cours e
regis tration s ys tem

College
details

Cours e
details
login

PACKAGE DIAGRAM:

A package diagram in the Unified modelling language depicts the dependencies

between the packages that make up a model. Package is a namespace used to group
78
together elements that are semantically related and might change together. It is a general
purpose mechanism to organize elements into groups to provide better structure for
system model.

IMPLEMENTATION:

FORM 1:

79
FORM 2:

FORM 4:

80
FORM 5:

FORM 7:

81
FORM 8:

FORM 9:

Form1.Show

End Sub

Private Sub Command2_Click ()

Form2.Show

End Sub

FORM 7:

Private Sub Command1_Click ()

Form8.Show

End Sub

FORM 8:

Private Sub back _Click ()

85
Form7.Show

End Sub

Private Sub Command1_Click ()

89
Login

Check availability

Enter source and destination

Booking

Customer Admin
Message Delivery

Ticket Confirmation
Cashier

Cancel

Update

Handle Payment Cash

Display homepage
Card

CLASS DIAGRAM:

A class diagram in the unified modelling 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 classname, middle
compartment the attributes and the bottom compartment with operations.

90
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modelling 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.

91
PASSENGER BOOKING BANK TICKET PRINTER DB
SERVER
LOGIN

CHOOSE TRANSPORT

IF AVAILABLE

BOOK

UPDATE

REQ TO DEBIT AMOUNT

DEBIT TICKET FARE

PRINT TICKET

TICKET PRINTED

TICKET ISSUED

UPDATE

COLLABRATION DIAGRAM:

A collaboration diagram, also called a communication diagram or interaction

diagram. A sophisticated modelling 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.

5: UPDATE
11: UPDATE
1: LOGIN
2: CHOOSE TRANSPORT BOOKING DB
4: BOOK SERVER

PASSEN 3: IF AVAILABLE
GER 10: TICKET ISSUED

9: TICKET PRINTED

8: PRINT TICKET
PRINTE
6: REQ TO DEBIT AMOUNT R
TICKET
7: DEBIT TICKET FARE

BANK

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

CHECK ENTERING
IDLE AVAILABILITY DETAILS

CANCEL THE
HOME DETAILS TICKET
PAGE

AUTHENTI CREDIT/D
CATION EBIT

UPDATION MSG
ENTER BOOKING DELIVERY
FROM& TO

IDLE
STACK

ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise
activities and actions with support for choice, iteration and concurrency. In the Unified
Modelling 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.

93
RESERVE CANCEL THE
THE TICKET TICKET

VIEW THE
DETAILS
CHECK RESERVATION LIST
CHECK FOR SEAT RESERVATION
NO YES
FILL THE INFORM THE GIVE THE
FORM CUSTOMER FORM

SUBMIT THE GIVE THE

FORM DETAILS RETURN THE
PAYMENT

ISSUE THE
TICKET

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.

DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modelling 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

94
represented by 3-dimentional box. Dependencies are represented by communication
association.

PASSENGE
R1
RAILWAY RESERVATION
SYSTEM
PRINTERS

PASSENGER2

O
PASSENGER
3
APPLICATIO
N SERVER

DBASE
SERVER

PACKAGE DIAGRAM :
A package diagram in unified modelling 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
2. Domain layer
3. Technical services layer

95
IMPLEMENTATION:

FORM 1:

96
FORM 2:

FORM 3:

97
FORM 4:

FORM 7:

98
FORM 8:

FORM 8ii:

99
FORM 11:

End Sub

Private Sub Option3_Click()

Form6.Show

MsgBox ("Transaction is successfully")

End Sub

Private Sub Command3_Click()

MsgBox ("UpdationSuccessfull")

End Sub

Private Sub Form_Load()

103
End Sub

FORM 9:

Private Sub Command1_Click()

MsgBox ("Booking Canceled Successfully")

Form1.Show

End Sub

Private Sub Command2_Click()

MsgBox ("Transaction is successfully")

End Sub

Private Sub Command3_Click()

MsgBox ("UpdationSuccessfull")

End Sub

End Sub

Private Sub Form_Load()

End Sub

FORM 11:
Private Sub Command1_Click()

Form1.Show

End Sub

Private Sub Command2_Click()

Form12.Show

End Sub

Private Sub Form_Load()

End Sub

FORM 12:
Private Sub Form_Load()

End Sub

RESULT:

Thus the UML diagrams for E-Book management system is drawn and the
implementation is done successfully.

105
EX.NO: 7 SOFTWARE PERSONAL MANAGEMENT SYSTEM
DATE:

AIM:
To develop a mini project on software personal management system using VB and
to draw the UML diagrams using Rational Rose.
PROBLEM STATEMENT:
The HR 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 HR 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.
MODEL DESCRIPTION:

FORM1:

FORM LOGIN:

Administrator log into the software personnel management system by using this
form.

106
FORM2:

Actions such as view, modification which the administrator wish to done is given in
this form. It contains view, modification and exit options.

FORM3:

The existing employee details can be viewed in this form by using data connection.

FORM4:

Actual modifications which were done by administrator can be given in this form. It
contains search, add new, delete, update, and cancel options. Search option searches a
particular record in the database. Similarly add new option adds a particular record in the
database. Delete option deletes a particular record in the database. Update option updates
a particular value. Finally the cancel button shows that the project was completed.

DESIGN PHASE:
USE CASE DIAGRAM:
The use cases are a set of scenarios to guide together by a common user goal. A
scenario is the sequence of steps describing an interaction between a user and their
system. Use-case diagram is a visual representation of what the card holder wants the
system to do.

107
CLASS DIAGRAM:

The class diagram is a static diagram. It represents the static view of an

application. Class diagram is not only used for visualizing, describing and documenting
different aspects of a system but also for constructing executable code of the software
application.

108
SEQUENCE DIAGRAM:

Sequence diagram is the most common kind of interaction diagram, which focuses
on the message interchange between a numbers of lifelines. Sequence diagram describes
an interaction by focusing on the sequence of messages that are exchanged, along with
their corresponding occurrence specifications on the lifelines.

COLLABORATION DIAGRAM:
A collaboration diagram describes interactions among objects in terms of
sequenced messages. Collaboration diagrams represent a combination of information
taken from class, sequence, and use case diagrams describing both the static structure and
dynamic behaviour of a system.

109
ACTIVITY DIAGRAM:
Activity diagram is UML behaviour diagram which shows flow of control or
object flow with emphasis on the sequence and conditions of the flow. The actions
coordinated by activity models can be initiated because other actions finish executing,
because objects and data become available, or because some events external to the flow
occur.

110
STATE CHART DIAGRAM:
State chart diagrams model the dynamic behaviour of individual classes or any
other kind of object. They show the sequences of states that an object goes through, the
events that cause a transition from one state to another and the actions that result from a
state change.

COMPONENT DIAGRAM:
Component diagrams provide a physical view of the current model. A component
diagram shows the organizations and dependencies among software components,
including source code components, binary code components, and executable components.
These diagrams also show the externally-visible behaviour of the components by
displaying the interfaces of the components.

111
DEPLOYMENT DIAGRAM:
Deployment diagrams show the physical configurations of software and hardware.
A Deployment diagram shows how and where the system will be deployed. Physical
machines and processors are reflected as nodes, and the internal construction can be
depicted by embedding nodes or artifacts.

PACKAGE DIAGRAM:
A package diagram in the Unified Modelling language depicts the dependencies
between the packages that make up a model. Package is a namespace used to group
together elements that are semantically related and might change together. It is a general
purpose mechanism to organize elements into groups to provide better structure for
system model.

112
IMPLEMENTATION:

WELCOME FORM:

113
SELECT HR OR EMPLOYEE LOGIN:

HR LOGIN FORM:

114
HR LOGIN PROFILE:

VIEW STATUS OF EMPLOYEE:

115
EMPLOYEE LOGIN FORM:

EMPLOYEE REGISTERATION:

116
SOURCE CODING:

WELCOME FORM:

Private Sub Picture1_Click()

Form2.Show

End Sub

Private Sub Image1_Click()

Form3.Show

End Sub

EXIT:

Private Sub Image2_Click()

MsgBox ("LOGIN SUCCESSFULL!!!")

End If

End Sub

DELETE:

Private Sub Command2_Click()

Data1.Recordset.Delete

Data1.Recordset.MoveNext

If Data1.Recordset.EOF() = True Then

Data1.Recordset.MovePrevious

End If

End Sub

ADDNEW:

Private Sub Command3_Click()

Data1.Recordset.AddNew

End Sub

EXIT:

Private Sub Command4_Click()

Form9.Show
119
End Sub

BACK:

Private Sub Command5_Click()

c.Show

End Sub

MOVE NEXT:

Private Sub Command6_Click()

Data1.Recordset.MoveNext

If Data1.Recordset.EOF() = True Then

Data1.Recordset.MoveLast

End If

Form12.Show

End Sub

EXIT:

Private Sub Image3_Click()

Form9.Show

End Sub

121
EXIT:

Private Sub Command1_Click()

Form9.Show

End Sub

ADDNEW:

Private Sub Command2_Click()

Data1.Recordset.AddNew

End Sub

BACK:

Private Sub Command3_Click()

Form10.Show

End Sub

Private Sub Command4_Click()

Thus the application for software personnel management system was created
successfully and UML diagrams were drawn using rational rose software.

123
EX.NO:8 CREDIT CARD PROCESSING SYSTEM
DATE:
AIM:

To draw the UML diagrams and to implement coding for Credit Card Processing.

PROBLEM DEFINITION:

 Credit card processing is a very important aspect of online business.

 We have decided to investigate the use of credit card processing system. This
system would be used by members who had be a customer of any bank.
 The purpose of this document is to analyze and elaborate on the high level needs
and features of the credit card processing system. It focuses on the capability and
facilities provided by a credit card.
 The details of what are all the needs are detailed in the usecase and supplementary
specifications.

SOFTWARE REQUIREMENTS:

 The software requirement captures all the requirements in single documents. The
credit card processing system that is to be developed provides the credit card
holders to know their due dates and transaction results. The credit card processing
system is supposed to have the following features and benefits.
 The system provides the card holders to make successful online payment.
 The system provides a signature access and zero liability on lost card.

124
SECURITY REQUIREMENTS:

 To provide the security to the system based on the current security system
currently used by VISA.

THE BILLING SYSTEM:

 To provide the interface between the system being developed and the billing
system currently in use by VISA to update the member account when they
purchase items.

MODULAR DESCRIPTION:

PRODUCT PERSPECTIVE:

 The credit card processing is a versatile, reliable service can help your business
increase sales by enabling you to accept all forms of payment from anywhere at
any time.
 CCP system to be developed benefits greatly the card holders. Once a card holder
is verified for the credit, he signs the charge slip which is forwarded to the
acquiring bank and closes the transactions with the merchant: for the acquiring
bank settles a transaction with the issuing bank.
 The product to the developed as interactions with the users buyer and merchant
product as to interact with the other system like internet, card issuing bank and
acquiring bank.

USER CHARACTERISTICS:

CREDIT CARD HOLDER:

 The person who issued a credit card actually holds & uses it.

125
MERCHANT /SHOPKEEPER:

 The person who accept the payments from the card holders through the swiping of
the credit card in return of the transaction.

CARD ISSUING BANK:

 It is a bank which has actually issue the credit card to the customer and first credit
to them on transaction made by the card holder.

CREDIT CARD NETWORK:

 This is that network which helps facilitate the card transaction such as visa or
master card.

SPECIFICATION DESCRIPTION:

NON-FUNCTION REQUIREMENTS:

 The project should execute normally in all time.

SOFTWARE QUALITY ATTRIBUTES:

1. EFFICIENT:
 It would be efficient enough to deals the credit cards. It should provide
information about the credit as soon as possible.
2. PORTABILITY:
 It should run in any platform without any major alteration.
3. AVAILABILITY:
 It should be available in 24 hours.
4. MAINTAINABILITY:
 It should cost minimum during maintenance phase.

126
UML DIAGRAMS:

USE CASE DIAGRAM:

Use case diagrams are used to describe a set of actions that some system or
systems should or can perform in collaboration with one or more external users of the
system. Each use case should provide some observable and valuable result to the actors
or other stakeholders of the system.

Quantity

Purchase product
Name of the product

Give card

Swipe card

Card holder
Salesperson

Enter amount

Receive Receipt & card

Deliver product deliver

Not deliver

CLASS DIAGRAM:

Class diagram is a static diagram. It represents the static view of an application.

The class diagram described the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling
of object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.

127
Customer details(from)
name
sender
address
credit card no

get details()

+purchase purchase

Purchase details(from) Merchant (from)

item name name
price calcuate amount
address
date acct no
local
salary details()
detail calculation() credit & details()
process card

Acquiring bank credit card no

shop no
amount
shop name Bank
process transaction c.address
credit card() c.name
transfer details() address
credit shop amount() amount

check user account()

transfer amount()
transfer acc details()

SEQUENCE DIAGRAM:

Sequence diagram describes an interaction by focusing on the sequence of

messages that are exchanged, along with their corresponding occurrence specifications on
the lifelines.

Customer Browser shop handle acquiring bank bank

payment

1. Search the shop

2. visit the home page purchase the item

3. purchase

4. Pay through credit card

5. Transfer credit card bank

6. Find accout no bank acct type

7. transfer the acct no and bill amt

8. transfer process

9. accept/deney the transaction

10. Transfer the amt

11. accept / dency the purchase

12. get the items

128
ACTIVITY DIAGRAM:

An activity diagram is to provide a view of flows and what is going on inside a use case
or among several classes. Activity diagrams are typically used for business process
modelling the logic captured by a single use case or usage scenario or for modelling the
detailed logic of a business rul

LOGIN USER MANAGEMENT PURCHASE BILL

PURCHASE ID
REGISTRATION

USER ID
LOG IN

NO EXIT

VERIFY
YES
ADD NEW PURCHASE
USER PRODUCT

ADD
NO
ENTER CUST
USER NAME ID

YES
MATCH
CARD TYPE ADD NEW
PURCHASE
YES

CARD GENERATE
NUMBER BILL

COLLABORATION DIAGRAM:

Collaboration diagram is also used to model the dynamic behaviour of the

system. When compared to sequence diagram, the collaboration diagram is more focused
on showing the collaboration of objects rather than the time sequences.

129
Browser
1: 1. Search the shop
3: 3. purchase

Custome
r 2: 2. visit the home page purchase the item

4: 4. Pay through credit card

12: 12. get the items shop

handle
payment

11: 11. accept / dency the purchase

8: 8. transfer process

5: 5. Transfer credit card bank

bank
6: 6. Find accout no bank acct type
7: 7. transfer the acct no and bill amt

9: 9. accept/deney the transaction

acquiring 10: 10. Transfer the amt
bank

STATE CHART DIAGRAM:

A state diagram is a type of diagram used to describe the behaviour of the

system. State diagrams requires that the system describe is composed of finite number
of states.

Cus tomer

Brows e and s elec t t he s hop

Brows er

Visit homepage and purc has e item

Shop

Pay t hrough c ard

Handle
pay ment

t rans act ion c redit c ard bank

Ac quiring
bank

Find acc t no and ty pe

Bank

Trans ac tion s uc c es s fully

130
COMPONENT DIAGRAM:
Component diagram are used to model physical aspects of a system. So
component diagram are used to visualize the organization and relationships among
components in a system. These diagrams are used to make executable system.

admin

custom browser shop payme

er nt

DEPLOYMENT DIAGRAM:

Deployment diagram is defined as assignment of concrete software artifacts to

computational nodes. In other words, deployment of software elements to the physical
architecture and the communication between physical elements.

admin

browse payment
custome shop
r

PACKAGE DIAGRAM:
A package diagram in unified modelling 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).
131
User Interface

Web Customer Admin

Domain Model

Check account Payment Transaction

handling

Technical Service
Database Authentication

IMPLEMENTATION:

FORM 1:

132
FORM 2:

FORM 3:

133
FORM 4:

FORM 5:

134
FORM 6:

FORM 7:

135
SOURCE CODING:

FORM 1:
Private Sub Command1_Click()
Form2.Show
End Sub
FORM 2:
Private Sub Command1 _Click()
Data1.Recordset.AddNew
End Sub
Private Sub Form_Load()
combo1.AddItem "CASH"
combo1.AddItem "CREDIT"
combo1.AddItem "CHEQUE"
End Sub
Private Sub Command5_Click()
Form1.Show
End Sub
Private Sub Command6_Click()
If combo1.Text = "CREDIT" Then
Form3.Show
Else
MsgBox "cannot access,sorry"
End If
End Sub
FORM 3:
Private Sub Command1_Click()
frmLogin.Show
End Sub
Private Sub Command2_Click()
Me.Hide
End Sub
136
FORM 4:
Option Explicit
Public LoginSucceededAs Boolean
Private Sub cmdCancel_Click()
'set the global var to false
'to denote a failed login
LoginSucceeded = False
Me.Hide
End Sub
Private Sub cmdOK_Click()
'check for correct password
If txtPassword = "4321" And txtUserName = "project" Then
'place code to here to pass the
'success to the calling sub
'setting a global var is the easiest
LoginSucceeded = True
MsgBox "Login successfull"
Form4.Show
Me.Hide
Else
MsgBox "Invalid Password, try again!", , "Login
txtPassword.SetFocus
End If
End Sub
FORM 5:
Private Sub Command1_Click()
If Text1.Text = "" Then
MsgBox "FILL THE TEXT"
ElseIf Text1.Text = Text2.Text Then
MsgBox "VALID CARD"
Form5.Show

137
Else
MsgBox "INVALID CARD"
End If
End Sub
Private Sub Command2_Click()
Me.Hide
End Sub
FORM 6:
Private Sub Command1_Click()
Form6.Show
Me.Hide
End Sub
Private Sub Command2_Click()
If Val(Form5.Text4.Text) < Val(Form2.Text6.Text) Then
MsgBox "INSUFFICIENT AMOUNT"
Else
Text6.Text = Val(Text4.Text) - Val(Text5.Text)
End If
End Sub
Private Sub Form_Load()
Form5.Text5.Text = Form2.Text6.Text
End Sub
FORM 7:
Private Sub Command1_Click()
Form7.Show
End Sub
Private Sub Form_Load()
Form6.Text1.Text = Form5.Text7.Text
Form6.Text2.Text = Form4.Text1.Text
Form6.Text3.Text = Form5.Text1.Text
Form6.Text4.Text = Form5.Text5.Text

138
Form6.Text5.Text = Form5.Text1.Text
Form6.Text6.Text = Form4.Text1.Text
Form6.Text7.Text = Form5.Text3.Text
End Sub
FORM 8:
Private Sub Command1_Click()
Form1.Show
End Sub

RESULT:

Thus the UML diagram are drawn and coding for Credit Card Processing System
is implemented successfully.
139
EX.NO:9 E-BOOK MANAGEMENT SYSTEM
DATE:
AIM:

E-Book management system is an interface between the user and administrator,

who takes care of E-Book management system for downloading books.

PROBLEM STATEMENT:

 This project is mainly used for searching and downloading the books.
 The user who is in need of a particular book can search for the book based on
Title, Author, Book name .
 If the book is available means the user by creating their unique login, they can
sign in to their account using their login id and password and can perform
downloading and uploading process. After downloading process the contents of
downloaded books will be displayed.
MODULES DESCRIPTION:

1.WELCOME FORM:

E-Book management system is an interface between the user and administrator,

who takes care of E-Book management system for downloading books.

2. LOGIN FORM:

The user and the administrator have their own login id and password for accessing
the eBook management system.

140
3. USER LOGIN FORM:

The system provides a security by giving a user login name and password. The user
with id and password only can access the system.

4. BOOK AVAILABILITY FORM:

The list of available books in the database will be displayed for the user. The user
search can for the book from the database.

5. REGISTRATION FORM:

A new user should register the details in the register form. After filling the
registration form, the user name and the password is given t0 the user. Using that name
and password only the user can access the system.

6. DOWNLOAD FORM:

It is used for searching a book and if available means downloading a book from
the database through authorized access by the user. This system uses several
programming and database techniques to elucidate the work involved in this process.

7. ADMINISTRATOR LOGIN FORM:

Administrator can upload their book to the database which is after login into the
system by using a administrator login name and id.

8. UPLOAD BOOK FORM:

Uploading a book by a administrator from to the database is maintained by the

administrator, who authenticate the access.

141
9. EXIT FORM:

The user exit from the system after downloading the book and also the
administrator exit from the system after uploading the book.

UML DIAGRAMS:

USECASE DIAGRAM:

Use-case diagram is used to indicate the existence of use-cases, actors and

their relationships and the courses of actions that can be performed. It is used to illustrate
the static use case view of a system. Use-case diagram is a visual representation of what
the customer wants the system to do. It shows a sequence of actions a system performs
that yields an observable result and is of value to a particular actor.

<<include>>

create account
login <<extend>>
database

validation
search books

user.

view books
<<include>>

no of books
select books

<<include>>

<<include>>
credit cards payment

<<include>>

debit cards

admin
visa cards

<<include>>

postal
<<extend>>
delivery

courier

142
CLASS DIAGRAM:

The Class diagram captures the logical structure of the system - the classes and
things that make up the model. Class diagram shows the static view of the system and are
modeled in the Logical view under the appropriate use-case realization. It shows a set of
classes, interfaces and their relationships.

SEQUENCE DIAGRAM:
Sequence diagram is a structured representation of behavior as a series of
sequential steps over time. It is used to depict work flow, message passing and how
elements in general cooperate over time to achieve a result.

143
user administrator browser search &view select payment cancel download message exit
books delivery
visit web page

search books &view books

select books

pay for the books

select cancellation

cancellation message confirmation

download books

delivery the message

get message

get exit

COLLABORATION DIAGRAM:
A collaboration diagram shows the interactions between elements at run-time in
much the same manner as a Sequence diagram. However, collaboration diagrams are
used to visualize inter-object relationships, while Sequence diagrams are more effective
at visualizing processing over time.

2: search books &view books

1: visit web page

user browser search &view
administ books
rator

7: download books
3: select books 5: select cancellation
4: pay for the books
6: cancellation message confirmation

select 10: get exit

8: delivery the message payment cancel downloa
d
9: get message

message exit
delivery

144
ACTIVITY DIAGRAM:

Activity diagrams can also be used in business modelling and to model the
workings of an operation, an object, or anything that involves modelling the sequential
steps in a computational process.

STATE CHART DIAGRAM:

A State chart diagram is a view of a state machine that models the changing
behavior of a state. State chart diagrams show the various states that an object goes
through, as well as the events that cause a transition from one state to another

145
COMPONENT DIAGRAM:
Component diagrams provide a physical view of the current model. A component
diagram shows the organizations and dependencies among software components,
including source code components, binary code components, and executable components.
These diagrams also show the externally-visible behaviour of the components by
displaying the interfaces of the components.
e-book management
system

customer database

DEPLOYMENT DIAGRAM:
Deployment diagrams show the physical configurations of software and hardware.
A Deployment diagram shows how and where the system will be deployed. Physical
machines and processors are reflected as nodes, and the internal construction can be
depicted by embedding nodes or artifacts. As artifacts are allocated to nodes to model the
system's deployment, the allocation is guided by the use of deployment specifications.

E-book Managem ent

Sys tem

Paym ent

s elect
book
SQL Server

146
PACKAGE DIAGRAM:
A package diagram in the Unified Modelling language depicts the dependencies
between the packages that make up a model. Package is a namespace used to group
together elements that are semantically related and might change together. It is a general
purpose mechanism to organize elements into groups to provide better structure for
system model.

web login

Domain

purchas e book databas e

Technical s ervices

Payment

IMPLEMENTATION:

WELCOME FORM:

147
LOGIN FORM:

USER LOGIN FORM:

148
REGISTRATION FORM:

DOWNLOAD FORM:

SOURCE CODING:

FORM 1(WELCOME FORM):

149
Private Sub Command1_Click()

Form2.Show

End Sub

FORM 2(LOGIN FORM):

Private Sub Command1_Click()

Form5.Show

End Sub

Private Sub Command2_Click()

MsgBox "login successful"

Form7.Show

End If
150
End Sub

Private Sub Command2_Click()

Form3.Show

End Sub

FORM 5(USER REGISTRATION FORM):

Private Sub Command1_Click()

Data1.Recordset.AddNew

MsgBox "added successfull"

MsgBox "username is user"

MsgBox "password is ebook"

Form5.Show

End Sub

Private Sub Command2_Click()

End Sub

FORM 6(BOOK AVAILABILITY FORM):

Private Sub Command1_Click()

Form4.Show

End Sub

FORM 7(DOWNLOAD FORM):

Private Sub Command1_Click()

MsgBox "downloading....please wait"

MsgBox "download completed"

Form10.Show
151
End Sub

Private Sub Command2_Click()

Me.Hide

End Sub

FORM 8(ADMINISTRATOR LOGIN FORM):

Private Sub Command1_Click()

If Text2.Text = "4321" Then

MsgBox "login successful"

Form9.Show

End If

End Sub

FORM 9(UPLOAD BOOK FORM):

Private Sub Command1_Click()

Data1.Recordset.AddNew

MsgBox "update successfull"

End Sub

Private Sub Command2_Click()

Form10.Show

End Sub

FORM 10(EXIT FORM):

Private Sub Command1_Click()

Form2.Show

End Sub
152
Private Sub Form_Load()

End Sub

RESULT:

Thus, the above project for E-book management system has been successfully
executed and codes are generated.
153
EX.NO:10 RECRUITMENT SYSTEM
DATE:
AIM:

To draw the UML diagrams and to implement coding for Recruitment System.

PROBLEM DEFINITION:

The recruitment system allows the job seekers to enrol their names through the
process of registration. The employer also can act the list of available candidates and
shortlist for the company requirement. This system makes the tasks of the job seeker
easier rather than waiting in queue for enrolment.

MODULES:

Modules in this project are,

1. Administrator

2. Job seekers (candidates)

3. Company (organization)

MODULE DESCRIPTION:

In this project we have defined different modules to enable the recruitment system
in successful manner.

ADMINISTRATOR:

It has the full authority over the website. He can view all the registered users and
have the power to delete them. She/he can edit the webs and update them. She/he can
view all the company details also.
154
JOB SEEKER:

A Candidate can register himself after registration. He will be directed to his home.
Here, he can update his profile change password and see the examination details and
company details.

COMPANY:

A company can register it, conduct online examination, approve or disapprove

candidates attending examination and provides results about the selected candidates.

DESIGN PHASE:

UML USECASE DIAGRAM:

Uml provides use case diagram notation to illustrate the names of use case and
author relationship between them. Use case diagram and case relationship are secondary
in use case work usecase text document.

155
CLASS DIAGRAM:
The Uml class diagram is to illustrate class interfaces and their actions. They are
used for static object modelling, we have already introduced and used their uml diagram
while domain modelling.

ACTIVITY DIAGRAM:
A Uml activity diagram shows sequential and parallel activities in a process,
workflows, data flows and compiler algorithm.

156
SEQUENCE DIAGRAM:
A sequence diagram illustrate a kind of format in which each object interact via
message. It is generalize between two or more specialized diagram.

COLLABRATION DIAGRAM:
Collaboration diagram illustrate that object interact on a graph or network format
in which object can be placed where in the diagram. In collabration diagram the object
can be placed in anywhere on the diagram. The collabration comes from sequence
diagram.

157
STATE TRANSITION DIAGRAM:
A Uml state machine represents the interaction events and states of an object and
behaviour of an object in reaction to an event. Transaction shown as allows labelled with
their event. It is included with initial pseudo state and fins end state.

COMPONENT DIAGRAM:
Component diagrams provide a physical view of the current model. A component
diagram shows the organizations and dependencies among software components,
including source code components, binary code components, and executable components.
These diagrams also show the externally-visible behavior of the components by
displaying the interfaces of the components.

158
DEPLOYMENT DIAGRAM:
Deployment diagrams show the physical configurations of software and hardware.
A Deployment diagram shows how and where the system will be deployed. Physical
machines and processors are reflected as nodes, and the internal construction can be
depicted by embedding nodes or artifacts. As artifacts are allocated to nodes to model the
system's deployment, the allocation

PACKAGE DIAGRAM:

A package diagram in the Unified Modelling language depicts the dependencies

between the packages that make up a model.

159
IMPLEMENTATION:

FORM 1:

FORM 2:

160
FORM 3:

FORM5:

161
FORM 8:

FORM 9:

162
FORM 11:

FORM 12:

163
SOURCE CODING:

FORM 1:

Private Sub Command1_Click()

Form4.Show

End Sub

Private Sub Command2_Click()

Form2.Show

End Sub

Private Sub Image1_Click()

End Sub

Private Sub Form_Load()

FORM 2:

Private Sub Command1_Click()

MsgBox ("login success")

Form3.Show

End Sub

Private Sub Option1_Click()

Form3.Show

End Sub

FORM 3:

Private Sub Command1_Click()

MsgBox ("login success")

Form5.Show
164
End Sub

FORM 4:

Private Sub Command1_Click()

If Text2.Text = "1234" Then

MsgBox ("login success")

Form5.Show

End If

End Sub

FORM 5:

Private Sub Option1_Click()

Form6.Show

End Sub

Private Sub Command1_Click()

Form14.Show

End Sub

Private Sub Command2_Click()

Form10.Show

End Sub

Private Sub Command3_Click()

Form10.Show

End Sub

End Sub

Private Sub Form_Load()

End Sub

FORM 9:

End Sub Private Sub Command1_Click()

Form6.Show

End Sub

Private Sub Form_Load()

End Sub

FORM 10:

Private Sub Command1_Click()

Form5.Show

Form6.Show

End Sub

Private Sub Command3_Click()

Form6.Show

End Sub

Private Sub Command4_Click()

Form6.Show

End Sub

Private Sub Command5_Click()

Form6.Show

End Sub

Private Sub Command6_Click()

Form6.Show

End Sub

Private Sub Command7_Click()

Form6.Show
169
End Sub

Private Sub Command8_Click()

Form5.Show

End Sub

Private Sub Form_Load()

End Sub

FORM 14:

Private Sub Command1_Click()

MsgBox ("login success")

Form15.Show

End Sub

Private Sub Form_Load()

End Sub

FORM 15:

Private Sub Command1_Click()

Form5.Show

End Sub

Private Sub Form_Load()

End Sub

RESULT:

Thus the project for RECRUITMENT SYSTEM has been executed and codes are
generated successfully.

170
EX.NO:11 FOREIGN TRADING SYSTEM
DATE:
AIM:

To Draw the UML Diagrams and to implement coding for Foreign Trading
System.

PROBLEM DEFINITION:

The main objective of the project is to build a Foreign Trading System which
assists many Globalized Organizations to improve their trade of commodities and
services to various clients of the world. The project is developed using Rational Rose
Software developed by IBM Corporation. The duration of the project is three weeks.

1. There are many authorized organizations providing this service.

2. Foreign trading system serves the following domains namely Transportation,

BPO, etc.

3. Foreign Trading System can be used round the clock, and it's very safe and
secure for the clients.

MODULE DESCRIPTION:

In this project consists of 8 modules namely Login, solution, Product Details,

Payment and Shipping, BPO, Card Validation, price details?

In this module, we can perform operation such as enter the user name and
password. If the user name and password is correct then it can be entered into the specific
web page. Otherwise re-enter the user name and password at the particular time only.
171
SOLUTION:

In this module, we can select any one of the operation such as product details,
payment and shipping, maintenance cell by clicking the required operation. Otherwise,
click the back operation to go back to the login form.

PRODUCT DETAILS:

In this module, we can see the details of the products available. By clicking the
back operation, we can move to the previous web page.

PAYMENT AND SHIPPING:

In this module, the organisation checks the details of the product which are selected
by the customer. The organisation can check price, the card is valid or invalid, sufficient
balance is available are not and the amount is paid or not by selecting the appropriate
operation.

BPO MAINTANENCE CELL:

In this module, we can give the problem of the product. the problem can resolve now
or later by selecting the appropriate operation.

CARD VALIDATION:

In this module, the organisation checks the card is valid or not.

PRICE DETAILS:

In this module, we can see the amount details of the product.

172
DESIGN PHASE:

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

FOREGIN T RADING SYST EM

ORDER OF PRODUCT

SUPPLIER

QUALITY

SECURITY AMOUNT CONVERS INTO MONEY

MEMBER

<<EXT END>>
<<EXT END>> PAYMENT

PAY BY CASH

<<EXT END>> CUSTOMER

<<EXT END>> DELIVERY

PAY BY CREDIT CARD

SHIP
FLIGHT

CLASS DIAGRAM:

A class diagram in the unified modelling 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.

173
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modelling 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.

COMPANY DB COMPANY PRODUCT CUSTOMER

COMPANY DETAILS

REGISTRATION

UPDATE

PERMISSION

PURCHASE PRODUCT

UPDATE

PAY THE AMOUNT

DELIVER THE PRODUCT

174
COLLABORATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction
diagram,. A sophisticated modelling 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 behaviour of individual objects as well as the
overall operation of the system in real time.

COMPANY COMPAN
DB Y

6: UPDATE
3: UPDATE 4: PERMISSION
1: COMPANY DETAILS 8: DELIVER THE PRODUCT

7: PAY THE AMOUNT

2: REGISTRATION

PRODU CUSTOM
CT ER
5: PURCHASE PRODUCT

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.

HOME
PAGE

ADVERRTI
SE

ORDER CANCEL

CHECK HANDLE
DETAILS PAYMENT

DELIVER
PRODUCTS

175
ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified Modelling
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.

PRODUCT M ANAGER ORGANIZATION VENDER

BLUE PRINT OF
THE PRODUCT

ADVERTISE
THE PRODUCT

ORDER THE
PRODUCT

ORDER CANCEL

HANDLE THE
PAYMENT

CHECK
DETAILS

TRANSPORT
THE PRODUCT

DELIVER THE
PRODUCT

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.
FOREIGN TRADING
SYSTEM

ORGANIZ ORDER PRODUC

ATION T

176
DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modelling 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.
FOREIGN
ORGANI TRADING VENDE
ZATION R

PRODU
ORDER CT

PACKAGE DIAGRAM :
A package diagram in unified modelling 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

177
User Interface

VB Forms GUI Interface

Domain

Order Payments
orders

Product Delivery
Product Check
Detail Update
Product Factory

Technical Service

MS Access

IMPLEMENTATION:

FORM 1:

FORM 3:

178
FORM 4:

FORM 5:

FORM 6:

179
FORM 7:

FORM 8:

SOURCE CODE:

FORM 1:

Private Sub Command1_Click()

If Text1.Text = "admin" And Text2.Text = "123" Then
MsgBox ("you have successfully login")
Form2.Show
Else
MsgBox ("not a valid admin")

Private Sub Command1_Click()

If Form4.Text7.Text = Form7.Text4.Text Then
MsgBox "The poduct details verified"
Else
MsgBox "Recheck the details"
End If
End Sub
Private Sub Command2_Click()
MsgBox "Ready to Export"
Form8.Show
End Sub
FORM 8:

Private Sub Command1_Click()

MsgBox "Poduct delivered successfully"

Form9.Show
End Sub
Private Sub Command2_Click()
MsgBox "Go Back"
Form7.Show
End Sub
FORM 9:

Private Sub Command1_Click()

Form1.Show
End Sub

RESULT:

Thus the application for foreign trading system was created successfully and UML
diagrams were drawn using rational rose software.

183
EX.NO:12 CONFERENCE MANAGEMENT SYSTEM
DATE:
AIM:

To draw UML diagrams and to implement coding for Conference Management

System.

PROBLEM DEFINITION:

This problem deals with the conference management system. As a student staff
members are required to view the details of conference that is going to be conducted in
various colleges or institution and to attend the conference to gain knowledge from the
conference. Administrator will add the details about the various conferences available for
various department students and staff members.

MODULES:

Modules in this project are

1. Administrator

2. Reviewer

3. Participant

MODULE DISCRIPTION:

In this project we have defined different modules to enable the Conference

Management system in successful manner.

184
1. ADMINISTRATOR:

Administrator is the person who assign reviewer for the submitted paper, assigns
important dates, assign topics etc.

2. REVIEWER:

Reviewer is the person who assigns reviewer for the submitted by the participated
and gives the status.

3. PARTICIPANT:

Participant is the person who submits a paper for the review of authors and if the
papers get selected they attend the conference.

DESIGN PHASE:

USECASE DIAGRAM:

<<include>>

Reviewer
submit paper

<<extend>>

review paper paper selection

participant
status

assign date
<<include>>

Management
paper presentation held conference

certificates

185
CLASS DIAGRAM:

The Uml class diagram is to illustrate class interfaces and their actions. They are
used for static object modelling, we have already introduced and used their uml diagram
while domain modelling.

ACTIVITY DIAGRAM:

Uml activity diagram shows sequential and parallel activities in a process, work
flows, data flows and compiler algorithm.

186
user manager database

start
conference

set date

often
registration

signup for
signup register

aunthenticatio
n

reject view paper

select paper

comment on
paper

receive send
notification notification rank paper

present paper result display set rank

SEQUENCE DIAGRAM:

Sequence diagrams illustrate a kind of format in which each object interact via
message. It is generalize between two or more specialized diagram.

187
COLLABORATION DIAGRAM:

Collaboration diagram illustrate that object interact on a graph or network format

in which object can be placed where and the diagram. In collaboration diagram the object
can be placed in anywhere on the diagram. The collaboration comes from sequence
diagram.

CEO
author
Student

1. Visits 10. provide reviews

6. Registers 5. Checks and analyses papers and journals
8. Access 2. publishes
11. See reviews

Databas 3. verifies
e 7. Verifies

9. Updates web_confe
4. updates rence

STATECHART DIAGRAM:

A Uml state machine represents the interaction events and states of an object and
behaviour of an object in reaction to an event. Transaction shown as allows labelled with
their event. It is included with initial pseudo state and finds end state.

188
start

cancellatio
n
registration check log out
massage

publish
cancel paper
submission submission

message
review delivery

comments decision
making

exit

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.

author

publis her

s ys tem
adm in

paper

189
DEPLOYMENT DIAGRAM:

A deployment diagram in the unified modelling language serves to model the

conference
management system

preemptive
paper and its
<process name> devices
<thread name>

publisher

author

PACKAGE DIAGRAM:

A package diagram in unified modelling language that depicts the dependencies

190
user interface

domain

new entry

register payment paper submit

status check

comment decistion

technical service

consistency

database

IMPLEMENTATION PHASE:

HOMEPAGE FORM:

191
TOPICS:

SIGNUP FORM:

192
LOGIN FORM:

PARTICIPANT LOGIN FORM:

193
PAPER SUBMISSION FORM:

Form12.Show

End Sub

FORM 2:

Private Sub cmdCancel_Click()

'set the global var to false

'to denote a failed login

LoginSucceeded = False

Me.Hide
196
Form4.Show

End Sub

Private Sub cmdOK_Click()

'check for correct password

If txtPassword = "vasu" Then

'place code to here to pass the

'success to the calling sub

G 'setting a global var is the easiest

LoginSucceeded = True

Form3.Show

Me.Hide

Else

MsgBox "Invalid Password, try again!", , "Login"

txtPassword.SetFocus

End If

Form1.Show

End Sub

FORM 5:

Private Sub Command1_Click()

Form7.Show

End Sub

Private Sub Command2_Click()

Form4.Show

End Sub

FORM 6:

Private Sub Command1_Click()

If (Text1.Text = "") Or (Text2.Text = "") Or (Text3.Text = "") Then

198
MsgBox "Enter all fields"

Else

MsgBox "success"

Adodc1.Recordset.Update

Form8.Show

End If

End Sub

Private Sub Command2_Click()

Form6.Show

End Sub

FORM 7:

Private Sub Command1_Click()

Form1.Show

End Sub

Private Sub Command2_Click()

Form9.Show

End Sub

FORM 8:

Private Sub Command1_Click()

If ((Text1.Text = "") Or (Text2.Text = "") Or (Text3.Text = "") Or (Text4.Text = "") Or

(Text5.Text = "") Or (Text6.Text = "") Or (Text8.Text = "")) Then

MsgBox "Enter the all fields"

End If

199
If Text6.Text = Text7.Text Then

MsgBox "SIGNUP SUCCESS"

Adodc1.Recordset.Update

Form4.Show

End If

End Sub

Private Sub Command2_Click()

regi ster

employee

non-voi ce

customer

ask-query

manager
explai n

vi ewdetail s

add&detail s

update

CLASS DIAGRAM:
A class diagram in the unified modelling 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.

206
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modelling 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.
cus tom er m anager
em ployee

nonvoicecall

as kquiries

ans wer

viewdetails

update

COLLABRATION DIAGRAM:
A collaboration diagram, also called a communication diagram or interaction
diagram. A sophisticated modelling 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 behaviour of individual objects as well as the overall
operation of the system in real time.
1. nonvoicecall
2. askquiries
cus tomer
employe
e
3. ans wer

4. viewdetails
6. update

7. update
5. viewdetails

manager

207
STATE CHART DIAGRAM:
It is also called as State diagram .The purpose of state diagram is to understand the
algorithm in problem statement. A state is represented as a rounded box, which may
contain one or more compartments. Compartments are all optional. Types of
compartment:
*Name compartment- holds name of the state
*Internal transition- holds internal actions or activities.
State chart is shown as the small dot .
Final state is shown as circle surrounding a small dot.

regis ter

manager
cus tomer employee

ans wer databas e

as k query

ACTIVITY DIAGRAM:
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified Modelling
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.

208
customer employee manager

man login
regis ter epregis ter

click button

ans wer

non-voice view delete add

as k query

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

BPO management
system

DB
login

manager

customer employee

209
DEPLOYMENT DIAGRAM:
A deployment diagram in the unified modelling 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.

BPO
Ma...

employe
custome e
r

manage
r

PACKAGE DIAGRAM:
A package diagram in unified modelling 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
• Domain layer
• Technical services layer

210
User Interface

VB Applicant

Domain

Non Voice Answer Update

Ask Quaries

Technical Service

Database

IMPLEMENTATION:
FORM 1:

FORM 2:

211
FORM 4:

FORM 5:

FORM 6:

212
FORM 7:

FORM 8:

FORM 9:

213
FORM 10:

FORM 11:

FORM 12:

214
SOURCE CODE:
FORM 1:
PublicClass Form1
PrivateSub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
Close()
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
LoginForm3.Show()
EndSub
PrivateSub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
loginform2.show()
EndSub
PrivateSub Form1_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
EndSub EndClass
MANAGER LOGIN FORM:
PublicClass LoginForm3
' My.User.CurrentPrincipal = CustomPrincipal
' where CustomPrincipal is the IPrincipal implementation used to perform authentication.
' Subsequently, My.User will return identity information encapsulated in the
CustomPrincipal object
' such as the username, display name, etc.
PrivateSub OK_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles OK.Click
Form2.Show()
Me.Close()
EndSubs
PrivateSub Cancel_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Cancel.Click
Me.Close()
EndSub
EndClass
215
FORM 2:
PublicClass Form2
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click 267
Form3.Show()
EndSub
PrivateSub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
Form4.Show()
EndSub
PrivateSub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Form5.Show()
EndSub
PrivateSub Button6_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button6.Click
Form6.Show()
EndSub
PrivateSub Button4_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs)
EndSub
PrivateSub Button7_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs)
Handles Button7.Click
Me.Close()
EndSub
PrivateSub Form2_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
EndSub
EndClass
ADD EMPLOYEE:
Imports System.Data
Imports System.Data.OleDb
PublicClass Form3
Dim conn As OleDbConnection
216
Dim comm As OleDbCommand
PrivateSub Form3_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
conn = New OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=D:\BPO\bpo1.accdb;Persist Security Info=True;Jet OLEDB:Database
Password=admin")
conn.Open()
Dim sql AsString
comm = New OleDbCommand(sql, conn)
conn.Close()
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs)
Handles Button1.Click
If TextBox1.Text = ""And TextBox2.Text = ""Then
MsgBox(" enter the name")
ElseIf TextBox2.Text = ""Then
MsgBox(" enter the father's name")
ElseIf TextBox3.Text = ""Then 268
MsgBox(" enter the DOB")
ElseIf TextBox4.Text = ""Then
MsgBox(" enter the address")
ElseIf TextBox5.Text = ""Then
MsgBox(" enter the contact no")
Else
conn.Open()
comm.Connection = conn
comm.CommandText = "insert into table1(name,fname,dob,address,contact) values('"&
TextBox1.Text &"', '"& TextBox2.Text &"','"& TextBox3.Text &"','"& TextBox4.Text
&"','"& TextBox5.Text &"')"
comm.ExecuteNonQuery()
conn.Close()
MsgBox("REGISTER SUCCESSFULLY")
Me.Close()
EndIf
217
EndSub
PrivateSub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
EndSub
PrivateSub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
If TextBox1.Text = ""Then
MsgBox("first enter name")
Else
comm = New OleDbCommand("delete from table1 where name =@name", conn)
conn.Open()
comm.Parameters.AddWithValue("@name", TextBox1.Text)
comm.ExecuteNonQuery()
MsgBox("EMPLOYEE DELETED")
conn.Close()
Me.Close()
EndIf
EndSub
EndClass
EMPLOYEE LIST:
PublicClass Form5
PrivateSub Form5_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the 'DataSet1.Table1' table. You can move, or
remove it, as needed.
Me.Table1TableAdapter.Fill(Me.DataSet1.Table1)
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Close()
EndSub
EndClass 269
ADD CUSTOMER:
Imports System.Data
218
Imports System.Data.OleDb
PublicClass Form4
Dim conn As OleDbConnection
Dim comm As OleDbCommand
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
If TextBox1.Text = ""And TextBox2.Text = ""Then
MsgBox(" enter the name")
ElseIf TextBox2.Text = ""Then
MsgBox(" enter the father's name")
ElseIf TextBox3.Text = ""Then
MsgBox(" enter the DOB")
ElseIf TextBox4.Text = ""Then
MsgBox(" enter the address")
ElseIf TextBox5.Text = ""Then
MsgBox(" enter the contact no")
Else
conn.Open()
comm.Connection = conn
comm.CommandText = "insert into table1(name,fname,dob,address,contact) values('"&
TextBox1.Text &"', '"& TextBox2.Text &"','"& TextBox3.Text &"','"& TextBox4.Text
&"','"& TextBox5.Text &"')"
comm.ExecuteNonQuery()
conn.Close()
MsgBox(" REGISTER SUCCESSFULLY")
Me.Close()
EndIf
EndSub
PrivateSub Form4_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
conn = New OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=D:\BPO\bpo2.accdb;Persist Security Info=True;Jet OLEDB:Database
Password=admin")
conn.Open()
Dim sql AsString
219
comm = New OleDbCommand(sql, conn)
conn.Close()
EndSub
PrivateSub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
If TextBox1.Text = ""Then
MsgBox("first enter name")
Else
comm = New OleDbCommand("delete from table1 where name =@name", conn)
conn.Open()
comm.Parameters.AddWithValue("@name", TextBox1.Text)
comm.ExecuteNonQuery()
MsgBox("CUSTOMER DELETED") 270
conn.Close()
Me.Close()
EndIf
EndSub
EndClass
CUSTOMER LIST:
PublicClass Form6
PrivateSub Form6_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the 'DataSet2.Table1' table. You can move, or
remove it, as needed.
Me.Table1TableAdapter.Fill(Me.DataSet2.Table1)
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Close()
EndSub
EndClass
EMPLOYEE LOGIN:
PublicClass LoginForm2
' My.User.CurrentPrincipal = CustomPrincipal
' where CustomPrincipal is the IPrincipal implementation used to perform authentication.
220
' Subsequently, My.User will return identity information encapsulated in the
CustomPrincipal object
' such as the username, display name, etc.
PrivateSub OK_Click(ByVal sender As System.Object, ByVal e As System.EventArgs)
Handles OK.Click
Form7.Show()
Me.Close()
EndSub
PrivateSub Cancel_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Cancel.Click
Me.Close()
EndSub
PrivateSub LoginForm2_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
EndSub
EndClass

CUSTOMER LOGIN:
Imports System.Data
Imports System.Data.OleDb
PublicClass Form7
Dim provider AsString 271
Dim dataFile AsString
Dim connString AsString
Public myConnection As OleDbConnection = New OleDbConnection
Public dr As OleDbDataReader
PrivateSub Form7_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
'TODO: This line of code loads data into the 'DataSet3.Table1' table. You can move, or
remove it, as needed.
Me.Table1TableAdapter.Fill(Me.DataSet3.Table1)
'Dim conn As OleDbConnection
provider = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source="

221
dataFile = "D:\BPO\bpo2.accdb;Persist Security Info=True;Jet OLEDB:Database
Password=admin"
'provider = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source ="
'dataFile = "C:\Users\Jimmy\Desktop\Products.accdb" ' Change it to your Access
Database location
connString = provider & dataFile
myConnection.ConnectionString = connString
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
myConnection.Open()
'DescriptionText.Clear()
'CostText.Clear()
'PriceText.Clear()
Dim str AsString
str = "SELECT * FROM table1 WHERE (name = '"& ComboBox1.Text &"')"
Dim cmd As OleDbCommand = New OleDbCommand(str, myConnection)
dr = cmd.ExecuteReader
While dr.Read()
TextBox1.Text = dr("contact").ToString
TextBox2.Text = dr("address").ToString
TextBox3.Text = dr("fname").ToString
TextBox4.Text = dr("dob").ToString
'DescriptionText.Text = dr("Description").ToString
'CostText.Text = dr("Cost").ToString
'PriceText.Text = dr("Price").ToString
EndWhile
myConnection.Close()
'Form6.Show()
EndSub
PrivateSub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Me.Close()
EndSub

222
PrivateSub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
Form8.Show()
EndSub
EndClass 272
QUERY:
PublicClass Form8
PrivateSub Form8_Load(ByVal sender As System.Object, ByVal e As
System.EventArgs) HandlesMyBase.Load
Me.Table1TableAdapter2.Fill(Me.DataSet6.Table1)
EndSub
PrivateSub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
If ComboBox1.Text = "Washing Machine"Then
Form9.Show()
ElseIf ComboBox1.Text = "Refrigerator"Then
Form11.Show()
ElseIf ComboBox1.Text = "TV"Then
Form12.Show()
ElseIf ComboBox1.Text = "Micro Owen"Then
Form13.Show()
EndIf
EndSub
EndClass

RESULT:
Thus the application for BPO management system was created successfully and
UML diagrams were drawn using rational rose software.

223
EXNO:14 LIBRARY MANAGEMENT SYSTEM
DATE:
AIM :
To develop the Library Management System using Rational Rose Software and to
implement the software in visual basic.
PROBLEM STATEMENT:

Library Management system is where the books can be collected every semester
and must be returned at the end of the semester. The system must have some options for
new member to enrol 1 for membership by paying deposit. A provision for getting six or
seven books per semester. Membership can be renewed by using the registered number.
The deposit must be refunded on termination of membership. A database must be
maintained to guide the issues to track the details of the student. Search option must be
provided so that the member can search for the availability of the particular books.

MODULE DESCRIPTION:

MODULE 1: REGISTRATION

MODULE 2: SEARCH FOR BOOKS

Allow the user to search for the books that he\she requires. Then make request for
display. Then display the following book details.

224
MODULE 3: PREVIOUS BOOK HISTORY

Check out how many books are allowed for a person to borrow. If the number of
books allowed less than the number books borrowed then allow the user to borrow. I f it
is in reverse then reject.

MODULE 4: CALCULATE FINE AMOUN

If the book is not returned within the due date then calculate the fine
amount to be paid. If the book is returned within the due date then no need to calculate
the fine amount.

MODULE 5: DISPLAY FINE AMOUNT

Finally display the fine amount to be paid by the borrower.

MODULE 6: LOGOUT

The user must log out from the book bank after borrowing\returning the book.

DESIGN PHASE:

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

225
LIBRARY MANAGEMENT SYST EM

Submi t Id Card

Verify Id Card

Grant Permi ssi on only if Id Card is

Val id
Librarian

Request to Issue Books

Issue Books

Return The Book

Search The Database For Book

Suppli er

Check Whether The Book Is

Availabl e or not

Issue The Book If Avai lable

CLASS DIAGRAM :

226
SEQUENCE DIAGRAM:
A sequence diagram in Unified Modelling 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.

student librarian supplier librarian

database

submit id card

verify id card

request to issue book

available book checked

available book

Issue the book

store the details

submit the book

update

COLLABRATION DIAGRAM:

A collaboration diagram, also called a communication diagram or interaction

diagram. A sophisticated modelling 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 behaviour of individual objects as well as the overall
operation of the system in real time.

227
1: submit id card
3: request to issue book
student 8: submit the book

librarian
2: verify id card
6: Issue the book
5: available book

4: available book checked

supplier
7: store the details
9: update

librarian
database

STATE CHART DIAGRAM :

s tudent librarian

reques t
book

proof check
valid

book
databas e

available

book is s ue

update
databas e

228
ACTIVITY DIAGRAM :
Activity diagrams are graphical representations of workflows of stepwise activities
and actions with support for choice, iteration and concurrency. In the Unified Modelling
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.

reques t book

s ubm it id card

verify id crad

valid id

check available
book

yes

available book
not valid

book is sue
date

update
databas e

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.

229
<<system>>
library management system
form.jsp

available
books.dll issue.dll
<<components>>
library database

<<clientworks tation>>
library managem ent s ys tem

s tudent
details

valid
us er

<<s erver databas e>>

my s ql

library
databas e

s tudent s taff book

databas e databas e databas e

230
PACKAGE DIAGRAM :
A package diagram in unified modelling 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

Visual Basic

Domain

Book Detail Return Book Renewal

Registration Issue Book

Technical Service

DataBase

231
IMPLEMENTATION:
FORM 1:

FORM 2:

FORM 3:

232
FORM 4:

FORM 5:

FORM 6:

233
FORM 7:

FORM 9:

FORM 10:

234
FORM 11:

FORM 12:

FORM 13:

235
FORM 14:

SOURCE CODING:
FORM 1:
Private Sub Command1_Click()
If Text1.Text = "aaaaa" And Text2.Text = "11111" Then
MsgBox ("successfully login")
Else
MsgBox ("not valid")
End If
Form2.Show
End Sub
FORM 2:
Private Sub Command1_Click()
Form3.Show
End Sub
Private Sub Command2_Click()
Form3.Show

236
End Sub
FORM 3:
Private Sub Command1_Click()
Form5.Show
End Sub
Private Sub Command2_Click()
Form4.Show
End Sub
Private Sub Command3_Click()
Form2.Show
End Sub
FORM 4:
Private Sub Command1_Click()
MsgBox ("the new account created successfully")
Form2.Show
End Sub
AddNew:
Private Sub Command2_Click()
Data1.Recordset.AddNew
End Sub
MovePrevious:
Private Sub Command3_Click()
Data1.Recordset.MovePrevious
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveFirst

237
End If
End Sub
MoveNext:
Private Sub Command4_Click()
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveLast
End If
End Sub
DELETE:
Private Sub Command5_Click()
Data1.Recordset.Delete
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MovePrevious
End If
End Sub
FORM 5:
Private Sub Command1_Click()
MsgBox ("registration successfully")
Form6.Show
End Sub
ADDNEW:
Private Sub Command4_Click()
Data1.Recordset.AddNew

238
End Sub
MOVEPREVIOUS:
Private Sub Command5_Click()
Data1.Recordset.MovePrevious
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveFirst
End If
End Sub
MOVENEXT:
Private Sub Command6_Click()
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveLast
End If
End Sub
DELETE:
Private Sub Command2_Click()
Data1.Recordset.Delete
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MovePrevious
End If
End Sub
FORM 6:
Private Sub Command1_Click()

239
Form7.Show
End Sub
Private Sub Command2_Click()
Form10.Show
End Sub
Private Sub Command3_Click()
Form11.Show
End Sub
FORM 7:
Private Sub Command1_Click()
Form8.Show
End Sub
FORM 8::
Private Sub Command1_Click()
MsgBox ("select the newspaper and read peacefully")
Form7.Show
End Sub
FORM 9:
Private Sub Command3_Click()
Form10.Show
End Sub
Private Sub Command4_Click()
Form10.Show
End Sub
Private Sub Command5_Click()

240
Form10.Show
End Sub
FORM 10:
Private Sub Command1_Click()
Form11.Show
End Sub
ADDNEW:
Private Sub Command2_Click()
Data1.Recordset.AddNew
End Sub
MOVEPREVIOUS:
Private Sub Command3_Click()
Data1.Recordset.MovePrevious
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveFirst
End If
End Sub
MOVENEXT:
Private Sub Command4_Click()
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveLast
End If
End Sub
DELETE:

241
Private Sub Command5_Click()
Data1.Recordset.Delete
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MovePrevious
End If
End Sub
FORM 11:
Private Sub Command1_Click()
If Text1.Text = "yes" And Text2.Text = "no" Then
MsgBox (" You are Successfully Searchinge in manually")
Form12.Show
Else
MsgBox ("You are successfully searching in using computer")
End If
End Sub
FORM 12:
Private Sub Command1_Click()
Form13.Show
End Sub
Private Sub Command2_Click()
Form15.Show
End Sub
FORM 13:
Private Sub Command1_Click()

242
Form14.Show
End Sub
FORM 14:
Private Sub Command1_Click()
MsgBox ("return book successfully")
Form16.Show
End Sub
Private Sub Command2_Click()
Form12.Show
End Sub
ADDNEW:
Private Sub Command3_Click()
Data1.Recordset.AddNew
End Sub
MOVEPREVIOUS:
Private Sub Command4_Click()
Data1.Recordset.MovePrevious
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MoveFirst
End If
End Sub
MOVENEXT:
Private Sub Command5_Click()
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then

243
Data1.Recordset.MoveLast
End If
End Sub
DELETE:
Private Sub Command6_Click()
Data1.Recordset.Delete
Data1.Recordset.MoveNext
If Data1.Recordset.EOF() = True Then
Data1.Recordset.MovePrevious
End If
End Sub
FORM 15:
Private Sub Command1_Click()
Form16.Show
End Sub

RESULT:

Thus the application project for Library Management system was created
successfully and UML diagrams were drawn using rational rose software.

244
EX.NO:15 STUDENT INFORMATION SYSTEM
DATE:
AIM:

To draw the UML diagrams and to implement coding for student information
system.

PROBLEM DEFINITION:

The Student Information system allows the Students to enrol their names, marks,
and others through the process of registration. The Student information system makes the
tasks easier rather than waiting in queue for enrolment.

MODULES:

Modules in this project are,

1. Staff

2. Student

MODULE DESCRIPTION:

In this project we have defined different modules to enable the recruitment system
in successful manner.

STAFF:

It has the full authority over the website. He can view all the registered users and
have the power to delete them. He/ She can edit the webs and update them. He/ She can
view all the company details also.

245
STUDENT:

A student can register himself after registration. He will be directed to his home.
Here, he can update his profile change password and see the examination details and
company details.

COLLEGE:

A college can register it, conduct online examination, approve or disapprove

candidates attending examination and provides results about the selected candidates.

DESIGN PHASE:

USECASE DIAGRAM:

logi n

rol lno
<<incl ude>>

staff detai ls admin

<<incl ude>>

name

student detail s

student student mark list

student grade

staff

staff sal ary

logout

246
CLASS DIAGRAM:

The Uml class diagram is to illustrate class interfaces and their actions. They are
used for static object modelling, we have already introduced and used their uml diagram
while domain modelling.

College_web Univers ity_db

Student_db_admin name name
name rno rno
rno year year
year update dept dept
dept s em s em
s em cgpa cgpa
cgpa gpa gpa
gpa college_name
s tore() branch
update() update()
capture() s tore()
update()
maintains updates delete()

univ_adm in
name
id
login
pas s

update_univ_db()

ACTIVITY DIAGRAM:
A Uml activity diagram shows sequential and parallel activities in a process,
workflows, data flows and compiler algorithm.

if valid No

yes

Enter s tudent
progress

Update db

s tore

247
SEQUENCE DIAGRAM:
A sequence diagram illustrates a kind of format in which each object interact via
message. It is generalize between two or more specialized diagram.

s tudent s taff db

s ubmit s tu details

enter s tu attendance

enter mark

verify mark &attendance

view datails

view details

verify mark & attendance

if any change say pblm

print details

modify details

update

view m odification

logout

248
COLLABRATION DIAGRAM:
Collaboration diagram illustrate that object interact on a graph or network format
in which object can be placed where in the diagram. In collaboration diagram the object
can be placed in anywhere on the diagram. The collaboration comes from sequence
diagram.

6: verify mark &attendance

9: verify mark & attendance

staff

student
10: if any change say pblm

7: view datails
14: view modification
1: login 15: logout

16: logout
8: view details

13: update
12: modify details
11: print details
db 5: enter mark
4: enter stu attendance
3: submit stu details
2: login

STATE CHART DIAGRAM:

249
pers onal
details

s ubject

s taff
allocation

res ult
s tatus

as s esm ent current s em

over all
m arks cpga

other
activities

project
paper validate
pres entation

conduct
certification

PACKAGE DIAGRAM:

A package diagram provides a way to group element. A package name may be

based on tab if the package shows the inner member of main package.

us er interface

vis ual bas ic

domain

regis tration s taff details verification

s tudent details

technical service

databas e

250
IMPLEMENTATION:
FORM 1:

FORM 2:

FORM 3:

251
FORM 6:

FORM 7:

FORM 9:

252
FORM 11:

FORM 12:

SOURCE CODE:
FORM 1:

Private Sub Command1_Click()

Form2.Show

End Sub

Private Sub Command2_Click()

Form12.Show

End Sub

253
FORM 2:

Private Sub Command1_Click()

Form3.Show

End Sub

Private Sub Command2_Click()

Form4.Show

End Sub

Private Sub Command3_Click()

Form5.Show

End Sub

Form2.Show
254
End Sub

FORM 4:

Private Sub Command1_Click()

Form2.Show

End Sub

FORM 5:

Private Sub Command1_Click()

Form2.Show

End Sub

FORM 6:

Private Sub Command1_Click()

If Text1.Text = "21" And Text2.Text = "39" Then

MsgBox ("successfully login")

Form7.Show

Else

MsgBox ("incorrect password")

End If

Form7.Show

End Sub

FORM 11:
256
Private Sub Command1_Click()

Form7.Show

End Sub

FORM 12:

Private Sub Command1_Click()

MsgBox ("sucessfully updated")

Form1.Show

End Sub

Private Sub Command2_Click()

Form1.Show

End Sub

RESULT:
Thus the project for STUDENT INFORMATION SYSTEM has been executed and
codes are generated successfully.

257

Ccs356 - Oose Lab Manual
No ratings yet
Ccs356 - Oose Lab Manual
88 pages
Fitness Android App Full Project and Synopsis
No ratings yet
Fitness Android App Full Project and Synopsis
90 pages
OOAD - Unit 2 Part 1 Introductio To UML
100% (1)
OOAD - Unit 2 Part 1 Introductio To UML
11 pages
Passport Automation System
100% (5)
Passport Automation System
9 pages
Ooad Lab Manual
No ratings yet
Ooad Lab Manual
83 pages
Association, Aggregation, Composition, Abstraction, Generalization, Realization, Dependency
50% (2)
Association, Aggregation, Composition, Abstraction, Generalization, Realization, Dependency
16 pages
Ex 1-3
No ratings yet
Ex 1-3
28 pages
Passport Automation System
0% (1)
Passport Automation System
140 pages
Oose Record Raga
No ratings yet
Oose Record Raga
65 pages
Computer Shop Management
100% (2)
Computer Shop Management
34 pages
Final OOSE Lab Manual
No ratings yet
Final OOSE Lab Manual
87 pages
Ccs356-Oose - Record Print
No ratings yet
Ccs356-Oose - Record Print
109 pages
Criminal Face Identification
No ratings yet
Criminal Face Identification
94 pages
OOSE LabManual
No ratings yet
OOSE LabManual
274 pages
Uml - Class Diagrams
No ratings yet
Uml - Class Diagrams
15 pages
CCS356-OOSE Lab Manual New
No ratings yet
CCS356-OOSE Lab Manual New
172 pages
OOAD Full Record
0% (1)
OOAD Full Record
189 pages
Casetoollabmannual
No ratings yet
Casetoollabmannual
131 pages
Software Engineering Lab Project
No ratings yet
Software Engineering Lab Project
155 pages
Passport Service System
No ratings yet
Passport Service System
23 pages
Ccs356 - Oose Lab Manual
No ratings yet
Ccs356 - Oose Lab Manual
120 pages
OOAD REcord
No ratings yet
OOAD REcord
86 pages
Ccs356 Lab
No ratings yet
Ccs356 Lab
108 pages
Case Tools Lab
No ratings yet
Case Tools Lab
35 pages
OOSE Lab Record - 2025 - IT Dept
No ratings yet
OOSE Lab Record - 2025 - IT Dept
122 pages
Oose Final1
No ratings yet
Oose Final1
109 pages
R-2021 Ooad Lab Manual
No ratings yet
R-2021 Ooad Lab Manual
126 pages
Ooad Manual
No ratings yet
Ooad Manual
90 pages
OOSE Lab
No ratings yet
OOSE Lab
108 pages
Ilide - Info Ccs356 Oose Lab Manual PR
No ratings yet
Ilide - Info Ccs356 Oose Lab Manual PR
88 pages
EX - NO: 1 Passport Automation System Date: Aim
No ratings yet
EX - NO: 1 Passport Automation System Date: Aim
92 pages
OOAD REcord - Merged
No ratings yet
OOAD REcord - Merged
87 pages
SE LAB Exp-2-1
No ratings yet
SE LAB Exp-2-1
26 pages
Ccs356-Oose Lab..
No ratings yet
Ccs356-Oose Lab..
116 pages
Oose Lab Manual
No ratings yet
Oose Lab Manual
145 pages
UML Lab: Object-Oriented Design
No ratings yet
UML Lab: Object-Oriented Design
70 pages
Report of Student Management System
No ratings yet
Report of Student Management System
49 pages
Oose Record
No ratings yet
Oose Record
39 pages
Ooad Manual
No ratings yet
Ooad Manual
88 pages
OOSE Lab
No ratings yet
OOSE Lab
109 pages
Passport & Book Bank Systems
No ratings yet
Passport & Book Bank Systems
107 pages
Ooad Lab Manual
No ratings yet
Ooad Lab Manual
20 pages
Library Management System
No ratings yet
Library Management System
15 pages
Se Project
No ratings yet
Se Project
22 pages
Banking System Software Guide
No ratings yet
Banking System Software Guide
9 pages
LabbbbSoftware Engineering Lab
No ratings yet
LabbbbSoftware Engineering Lab
41 pages
Oose Lab Manual
No ratings yet
Oose Lab Manual
79 pages
Cs8582-Object Oriented Analysisand Design Laboratory-46023968-Cs8582 - Ooad Lab (1) - Removed
No ratings yet
Cs8582-Object Oriented Analysisand Design Laboratory-46023968-Cs8582 - Ooad Lab (1) - Removed
10 pages
Engineering Book Bank System
No ratings yet
Engineering Book Bank System
14 pages
Ooad Lab Gce
No ratings yet
Ooad Lab Gce
271 pages
007
No ratings yet
007
12 pages
Assignment 1: Transitions
No ratings yet
Assignment 1: Transitions
10 pages
CS Engineering Lab Manual
No ratings yet
CS Engineering Lab Manual
130 pages
Se Standard Lab Manual
No ratings yet
Se Standard Lab Manual
95 pages
Task 3 Updated
No ratings yet
Task 3 Updated
9 pages
Ooad Question Bank
No ratings yet
Ooad Question Bank
21 pages
SD Lab Mannual
No ratings yet
SD Lab Mannual
75 pages
Hotel Booking System Report
No ratings yet
Hotel Booking System Report
8 pages
LabManual 26298 Content Document 20241020065607PM
No ratings yet
LabManual 26298 Content Document 20241020065607PM
24 pages
SRS Sample
No ratings yet
SRS Sample
31 pages
CS8582 Object Oriented Analysis AND Design Laboratory
No ratings yet
CS8582 Object Oriented Analysis AND Design Laboratory
174 pages
Anna University OOAD Lab Manual
No ratings yet
Anna University OOAD Lab Manual
78 pages
Ooad Manual Record For Printout 1
No ratings yet
Ooad Manual Record For Printout 1
116 pages
SRS v1
No ratings yet
SRS v1
32 pages
Case Tools Lab-Manual
No ratings yet
Case Tools Lab-Manual
281 pages
Passportautomationsystem
No ratings yet
Passportautomationsystem
23 pages
Syllabus 15Fd11-Ooad Lab: OBJECTIVE: To Develop A Project Following The Exercises Listed Below
No ratings yet
Syllabus 15Fd11-Ooad Lab: OBJECTIVE: To Develop A Project Following The Exercises Listed Below
79 pages
OOAD Lab Manual for CSE Students
No ratings yet
OOAD Lab Manual for CSE Students
78 pages
OOSD Record
No ratings yet
OOSD Record
53 pages
IT Project Guidelines - NBNSTIC Pune
No ratings yet
IT Project Guidelines - NBNSTIC Pune
38 pages
Modeling With UML Solutions
No ratings yet
Modeling With UML Solutions
10 pages
Object-Oriented Design & Methodology CS 312 OO Modeling CS 214 Fall 2011
No ratings yet
Object-Oriented Design & Methodology CS 312 OO Modeling CS 214 Fall 2011
58 pages
Data Analytics Class - Unit-Ii
No ratings yet
Data Analytics Class - Unit-Ii
40 pages
OOAD Lab Exercise-1 To 3
No ratings yet
OOAD Lab Exercise-1 To 3
59 pages
Lecture 7 Introduction To UML OOP
No ratings yet
Lecture 7 Introduction To UML OOP
98 pages
Documentation
No ratings yet
Documentation
71 pages
OOAD & Unified Process Basics
No ratings yet
OOAD & Unified Process Basics
39 pages
UML Diagram Types Guide
No ratings yet
UML Diagram Types Guide
17 pages
Fowler Unified Modeling Language
No ratings yet
Fowler Unified Modeling Language
46 pages
UML Basics and Class Diagrams
No ratings yet
UML Basics and Class Diagrams
70 pages
Sda - Lab 5
No ratings yet
Sda - Lab 5
3 pages
Object Oriented Programming Lab 1
No ratings yet
Object Oriented Programming Lab 1
13 pages
Ooad SI Usd
No ratings yet
Ooad SI Usd
11 pages
Software Engineering - Ehrs: Draw Data Flow Diagram
No ratings yet
Software Engineering - Ehrs: Draw Data Flow Diagram
8 pages
Design Patterns by Example For Systemverilog Verification Environments Enabled by Systemverilog 1800-2012
No ratings yet
Design Patterns by Example For Systemverilog Verification Environments Enabled by Systemverilog 1800-2012
13 pages