INDEX

EXPERIMENT

PAGE
No.

Study of Rational Rose

Software and UML Diagrams

Exam Registration System

Stock Maintenance System

29

Credit Card Processing

51

E-Book Management System

72

Online Ticket Reservation

System

92

S. No.

DATE

INTERNAL MARKS

MARKS
O

STAFF- INCHARGE

SIGN.

STUDY OF RATIONAL ROSE AND UML DIAGRAMS

AIM:
To study about the Rational Rose Software and UML Diagrams.

RATINAL ROSE SOFTWARE:

The Application method recommends the use of static and dynamic views
of the logical model and the physical model to capture in the process,
products of object oriented analysis and design.
Using the notations the application enables to create and refines these
views within an overall model representing the problems domain and
software system.
This over all models contains classes, use cases, objects, packages,
operations, package components, process and devices and the relationship
between them.
CASE Tools known as Computer-Aided Software Engineering tools is a
kind of component based development which allows its users to rapidly
develop information systems.
The main goal of case technology is the automation of the entire
information systems development life cycle process using a set of
integrated software tools, such as modeling, methodology and automatic
code generation.

CHARACTERISTICS OF CASE:
Some of the characteristics of case tools that make it better than
customized development are;
Its a graphic oriented tool.
It supports decomposition of process.
Some typical CASE Tools are:
Unified Modeling Language
2

 Data modeling tools, and

Source code generation tools

INTRODUCTION TO UML(UNIFIED MODELING LANGUAGE)

The UML is a language for specifying, constructing, visualizing, and
documenting the software system and its components.
The UML is a graphical language with sets of rules and semantics.
The rules and semantics of a model are expressed in English in a form
known as OCL(Object Constraint Language).
OCL uses simple logic for specifying the properties of a system.
The UML defines nine graphical diagrams:
1.class diagram
2.use-case diagram
3.Behaviour diagram
3.1.Interaction diagram
3.1.1.Sequence diagram
3.1.2.Collaboration diagram
3.2.State chart diagram
3.3.Activity diagram
4.Implementation diagram
4.1 Component diagram
4.2 Deployment diagram

1.CLASS DIAGRAM
A class diagram is a collection of static modeling elements, such as
classes and relationship connected as a graph to each other and the
contents.
The classes are drawn as a rectangular with three components separated
by horizontal lines.
The top components contain class name, middle contains
The top components contain class name, middle contains attributes button
contains the list of operations.

Symbols used in Class diagram:

Class

NewClass

Package

NewPackage2

2.USE CASE

DIAGRAM:

A use case diagram is a graph of actors a set of use case enclosed by system
boundaries, communication, association between the actors and the use
case and generalized among the use case.
The functionality of a system is described in a number of different use cases
each of which represents a specific flow of events in the system.

Symbols used in Use Case diagram:

Scenario
NewUseCase

Actor
NewCl ass4

Package

NewPackage4

Link

3.SEQUENCE DIAGRAM
A sequence diagram shows an interaction arrangement in a time sequence.
The horizontal line represents the objects.
The vertical line represents the object life time, which is the objects existing
during the interaction
A object is shown as a box at the top of clashed verticals lines.

Symbols used in Sequence diagram:

Object&Life

line

Message line

4.COLLABORATION DIAGRAM:
A collaboration diagram represents a collaboration which is a set of objects
related in a particular context and interacting, which is a set of messages
exchanged among the objects within the collaboration to achieve outcome.
The sequence is indicated by numbering the message.

Symbols used in Collaboration diagram:

Object
Message line

5.ACTIVITY DIAGRAM:
AN Activity diagram is a variation or special case of state machine.
The purpose of activity diagram is to provide a view of flow and what is going
on inside of use case (or) among several use cases.
It is similar to a state chart diagram, where a token represents and operations.
An activity is shown as a round box containing, the name of operation.

Symbols used in Activity diagram:

Starting point
State

Decision
End point
Link

RESULT:
Thus the case study of Rational Rose Software and Unified Modeling Language was
completed successfully.

EXAM REGISTRATION SYSTEM

AIM :
To develop a system that can perform exam registration.
PROBLEM STATEMENT:
To create an Exam registration software that will meet the needs of the
applicant and help them in registering for the exam ,enquiry about the registered
subject ,modification in database and cancellation for the registered project.
1. INTRODUCTION:
The main aim of this project is to automate registering student details,
maintaining the student detail, retrieving student details, retrieving specific
details when necessary, security from unauthorized access ,functionalities such
as insert, delete, update etc., issuing the hall ticket.
1.1. Purpose:
The main purpose of the system is to issue hall ticket immediately after
registering their details. Administrator will issue hall ticket only if the student
has paid the fee.
1.2. Scope of the Product:

The main aim of this software requirement specification is to give a

detailed idea about the various specification and the functionalities of the
software.

The mainly focuses for the understanding of the various users who are
going to use this software and best way to make the software behave in a
normal manner and user friendly.

The exam registration system automates the system, rechecking the

inclusion of all details, automatically initializing the hall ticket and other
details.

It checks out to see if the fee is paid based on which to check out if the
hall ticket has already been issued.

1.3. References:
IEEE SRS Format.
1.4. Overview:

The purpose of this section is to obtain agreement regarding the

objectives the system must meet. Ultimately this segment defines the
boundaries of the effort.

The

Exam Registration System helps administrator honor their

professional commitments by following a tailored version of the

standard process.

This application is supported by a database consisting of user details. It

could be updated with the details of user if required by the administrator.

Hall ticket issuing is done based on the details regarding payment of fees.

Communication needs to be restricted when the student is trying to access

the details that are submitted.

The user will register with the system by providing personal information
such as name, date of birth, gender, subject and its code and registration
number.

2.GENERAL DESCRIPTION:
2.1 Context of the Product:
Exam Registration system gives you managing the flexibility of
registering for exam by enrolling the personal details which are required by
administrator and finally simple click for hall ticket generation.
User profile shall include personal details and register number. The
student has to login before any processing is to be done.
2.2 Product Functions:
Module 1:
It is login form in which both user and administrator has to enter username and
password to enter into exam registration.
Module 2:
Student can enter in to register their details and in same form the admin can
enter to manage the student database and retrieve it.
Module 3:
If student registers after the payment of fees into exam registration system
administrator will issue hall ticket, if else not.
Module 4:
It is the form where the admin maintain the student database to insert, delete,
and update. The complete data of the student can otherwise be viewed in grid
form.
2.3 User Characteristics:
2.3.1 End Users

No specific knowledge or skills are required from the end user.

8

End user should have basic idea about computer operations and database.

2.3.2 Administrator

Administrator must be having good knowledge of database management

system.

Administrator must be capable to manage user rights.

If the network connection does not work properly than our system should
not work as intended. Also that is assumed that the product is installed
properly at web server.

This system will not take care of any virus problem, which might occur
either on the client or the server system. Avoiding the use of pirated
software and ensuring that floppies and other removable media are
scanned for viruses before use could minimize the possibility of viral
infection.

Recovery of data after a system crash will be possible only if backups are
taken at regular intervals.

2.4 Assumptions:

The code should be free with compilation errors/syntax errors.

The product must have an interface which is simple enough to

understand.

3.SPECIFIC REQUIREMENTS:
3.1 External Interface Requirements:
Describes the user interface characteristics
-user opens the main page which displays option such as register or cancel.
-Each option is linked to another page where user details and fees payment
details are updated.
-The monitor displays the project.
9

-The mouse and/or keyboard are used for data entry and/or to make selections.
3.1.1 User Interface
Keyboard, Mouse
3.1.2 Hardware Requirements:
1.128 MB RAM
2. Pentium III processor
3.1.3 Software Interface
Front End: Microsoft visual studio 2008
Back End: MS Access
Another one is Rational Rose software.
3.2 Functional Requirements
The different steps followed in using the project by the user is
described in this section.
Login:
The user enters the username and password and chooses if the user is
student or administrator .If entered details are valid, hall ticket will be issued by
checking fees payment details .If it is invalid, an appropriate message is
displayed to the user.
Update User Details:
User details can be updated by administrator if required such as fees
payment details, address or phone number etc..
Add User:
Only the administrator has access to this use-case. The administrator has
to provide the details of the user to register. If the user added already exists,
then an appropriate message is displayed.
3.3. Performance Requirements:
The project is designed for over user at a time. The number of page will
be more or less10.The navigation from one page to another takes place, within
10

fraction of seconds. Since the data is stored in database, huge amount of data
can be accessed and data storage is possible.
3.4. Quality Requirements:
This section decreases issues related to security and safety of the product
3.5. Security:
There would be some risks of details of any user is gone out. Therefore
each user is provided with username and password using which they can access
their own details. The product is password protected.
3.6. Safety:
The user must logout before closing the project to prevent malicious
access or destruction.
4. CONCLUSION
Future Enhancement:
The project can be upgraded to make it as an international accessing of
exam registration details project, so that users can be accessed easily and
effectively.

11

Gantt Chart For Exam Registration System

A Gantt chart is a type of chart that illustrates a project schedule. Gantt
charts illustrate the start and finish dates of the terminal elements and summary
elements of a project. Terminal elements and summary elements comprise the
work structure of the project. Some Gantt charts also show the dependency (i.e.,
precedence network) relationships between activities.

12

Assumptions:
The id generated to the enrolled candidates is unique.
The user has basic knowledge about working of computers and gives
appropriate data for the required fields.

UML DIAGRAMS FOR EXAM REGISTRATION SYSTEM

USE-CASE DIAGRAM:

13

14

CLASS DIAGRAM:

STATE CHART DIAGRAM:

15

ACTIVITY DIAGRAM :

16

SEQUENCE DIAGRAM :

COLLABORATION DIAGRAM:

17

COMPONENT DIAGRAM:

DEPLOYMENT DIAGRAM:

18

IMPLEMENTATIONvbb
FORM1: STUDENT LOGIN

Imports System.Data.OleDb
Public Class Form1
Dim conn As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=C:\Documents and Settings\User\My Documents\Database1.accdb")
Dim cmd As New OleDbCommand
Dim res As OleDbDataReader
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim count As Integer
conn.Open()
cmd = New OleDbCommand("select * from login", conn)
res = cmd.ExecuteReader()
count = 0
While (res.Read)
If TextBox1.Text = res.GetValue(0).ToString And TextBox2.Text =
res.GetValue(1).ToString() Then
count += 1
19

End If
End While
If count = 1 Then
MessageBox.Show("login successful")
Form2.Show()
Else
MessageBox.Show("enter correct user and pasword")
End If
conn.Close()
End sub
FORM2: REGISTRATION FORM
Imports System.Data.OleDb
Public Class Form2
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=C:\Documents and Settings\User\My Documents\Database1.accdb")
Dim cmd As New OleDbCommand
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
con.Open()
cmd = New OleDbCommand("insert into student values(' " &
TextBox1.Text & " ', ' " & TextBox2.Text & " ', ' " & TextBox3.Text & " '," &
TextBox4.Text & ",' " & TextBox5.Text & " ', " & TextBox6.Text & " ) ", con)
cmd.ExecuteNonQuery()
MessageBox.Show("inserted")
con.Close()
Form1.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button2.Click
Form1.Show()
Me.Hide()
End Sub
FORM 1: ADMIN LOGIN
Private Sub Button3_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button3.Click
conn.Open()
20

cmd = New OleDbCommand("select * from login2", conn)

res = cmd.ExecuteReader()
While (res.Read)
If TextBox3.Text = res.GetValue(0).ToString() And TextBox4.Text =
res.GetValue(1).ToString() Then
MessageBox.Show("login successful")
Form3.Show()
Else
MessageBox.Show("enter correct ad-name and password")
End If
End While
conn.Close()
End Sub
FORM3: VERIFYING DETAILS AND ISSUING HALL TICKET
Imports System.Data.OleDb
Public Class Form3
Dim conn As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Data
Source=C:\Documents and Settings\User\My Documents\Database1.accdb")
Dim cmd As New OleDbCommand
Dim res As OleDbDataReader
Dim da As New OleDbDataAdapter
Dim dt As DataTable
Dim dt1 As DataTable
Dim dt2 As DataTable
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs) Handles Button1.Click
Dim s As String
Dim i As Integer
conn.Open()
da = New OleDbDataAdapter("select * from userdetails", conn)
dt1 = New DataTable
da.Fill(dt1)
conn.Close()
For i = 0 To 1
s = dt1.Rows(i).Item(0)
ListBox1.Items.Add(s)
Next i
21

End Sub
Private Sub ListBox1_MouseClick(ByVal sender As Object, ByVal e As
System.Windows.Forms.MouseEventArgs) Handles ListBox1.MouseClick
Dim s1 As String
Dim j As Integer
Dim count As Integer
s1 = ListBox1.SelectedItem
conn.Open()
da = New OleDbDataAdapter("select * from userdetails where SNAME =
'" & s1 & "' ", conn)
dt2 = New DataTable
da.Fill(dt2)
conn.Close()
conn.Open()
da = New OleDbDataAdapter("select * from student where stname = '" &
s1 & "' ", conn)
dt = New DataTable
da.Fill(dt)
conn.Close()
count = 0
For j = 0 To 5
If dt2.Rows(0).Item(j) = dt.Rows(0).Item(j) Then
count += 1
End If
Next j
MessageBox.Show("valid user")
End Sub
Private Sub Button5_Click(ByVal sender As System.Object, ByVal e As
System.EventArgs)
conn.Open()
da = New OleDbDataAdapter("select * from student where stname = 'a' ",
conn)
dt = New DataTable
da.Fill(dt)
conn.Close()
End Sub
End Class
22

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

System.EventArgs) Handles Button4.Click
Dim s1 As String
Dim j As Integer
s1 = ListBox1.SelectedItem
conn.Open()
da = New OleDbDataAdapter("select * from userdetails where SNAME =
'" & s1 & "' ", conn)
dt2 = New DataTable
da.Fill(dt2)
conn.Close()
If dt2.Rows(0).Item(6) > 60 And dt2.Rows(0).Item(7) = "paid" Then
MessageBox.Show("issue hall ticket")
Else
MessageBox.Show("hall ticket cannot be issued")
End If
End Sub
OUTPUT FORMS:

23

24

25

USER DETAILS DATABASE:

26

ADMIN TABLE:

RESULT :
Thus the Exam Registration System project was
executed successfully.

27

STOCK MAINTENANCE SYSTEM

AIM:
To analyze, design and develop code for Stock
Maintenance System.
PROBLEM STATEMENT:
INVENTORY SYSTEM is a real time application used
in the merchants day to day system. This is a database to store
the transaction that takes places between the Manufacturer,
Dealer and the Shop Keeper that includes stock inward and
stock outward with reference to the dealer. Here we assume
our self as the Dealer and proceed with the transaction as
follows: The Manufacturer is the producer of the items and it
contains the necessary information of the item such as price
per item, Date of manufacture, best before use, Number of
Item available and their Company Address. The Dealer is the
secondary source of an Item and he purchases Item from the
manufacturer by requesting the required Item with its
corresponding Company Name and the Number of Items
required. The Dealer is only responsible for distribution of the
Item to the Retailers in the Town or City. The Shop Keeper or
Retailer is the one who is prime source for selling items in the
market. The customers get Item from the Shop Keeper and not
directly from the Manufacturer or the Dealer. The Stock is the
database used in our System which records all transactions that
takes place between the Manufacturer and the Dealer and the
Dealer and the Retailer.
1.INTRODUCTION:
28

1.1. Purpose of the Document:

The main purpose of the system is to maintain stock
for fancy store.
1.2. Scope of the Project:
To ensure the portability and therefore compatibility.
To ensure our system moves with time i.e it allows for
maintenance, upgrades and periodic backups by developed
and authorized personnel.
1.3. Project Description:
Stock manager is having the rights and controls to login
into the software by entering his username and valid
password.
They analyze what goods are need, what are the expired
ones and the old ones. Then he clears the old goods by
selling it with offer. Then he will eliminate the expired
goods from the godown. Then he prepares the list of
goods which are needed for the customer provision
shop. Then he calls the company for quotation.

After receiving the quotations from the company, the

stock manager chooses the best quotation. Then the
manager purchase the needed goods from the
corresponding company. After delivery of all the goods
by the company manager and the sales manager settles
all his payments with tax.
Then the stock manager sells the goods to many
customers and updates all the details in the database. By
processing these steps the stock manager manages the
stock available in the godown.
1.4. Acronyms, Abbreviations, Definitions:
SMS-Refers to this Stock Maintenance System.
2. GENERAL DESCRIPTION:
2.1 Product Functions:
Login:
The login is used for security of the customer. The
customer logs in with the user name and the password of the
29

customer.
Analysis:
The stock manager analysis the stocks. He identifies the
old stocks and the expired goods and also the list of items
needed.
Old stock clearance:
The stock manager clears the old stock goods by selling
it at a offer price.
Order List Preparation:
The stock manager prepares the list of items to be
bought. Then he calls the company for quotations.
Quotation:
The stock manager calls the company for quotations.
After receiving the quotations from the company, the stock
manager chooses the quotation.
Purchase: The stock manager purchases the needed goods
from the corresponding company in which the quotations are
selected.
Payment:
The stock manager pays the bills along with the tax and
the goods are delivered by the company manager.
2.2 User characteristics:
The new user can be add to this application by entering
the name, address, phone, email etc. Only the administrator
can modify the list of user details and also the administrator
can remove the unwanted user. If anyone wants to login then
firstly, the user has to create a module.
3. SPECIFIC REQUIREMENTS:
3.1. Hardware Requirements:
Processor Intel Pentium IV-2.0 GHZ.
Hard disk 40 GB.
RAM 512MB
DVD RAM 1 nos.
3.2. Software Requirements:
OS windows XP/vista.
30

Front end Tool Visual Studio 2008.

Back end Tool Oracle 10i.
3.3. Functional Requirements:
Login: Login is achieved by the stock manager.
Analysis of Goods: Finding the expired goods. Finding
the older ones and selling with offer prices
Preparing the List: List of goods or items which are
needed are prepaed by the stock manager.
Getting the Quotations: Stock manager gets the
quotation from the company manager.
Choosing the best one: Stock manager chooses the
best quotations.
Purchasing the goods: Stock manager purchase the
good from the company manager.
Delivery & Payment: Delivery of goods by the
required company and payment settled by the stock manager.
Update: It is performed by the stock manager in the
database.
3.4 Non- Functional Requirements:
Nonfunctional requirements define the needs in terms
if performance, logical database requirements, design
constraints, standard compliance, reliability, availability,
security, maintainability and portability.
3.4.1 Performance Requirements:
Performance requirements define acceptable response
times for system functionality. The load time for user interface
screens will take no longer than two seconds. The login
information shall be verified within five seconds. Queries shall
results within five seconds.
3.4.2Design Constraints:
The software shall be a standard system running in a
windows environment. The system shall be developed using
31

rational enterprise suite.

3.4.3Reliability:
Specify the factors required to establish the required
reliability of the software system at time of delivery.
3.4.4Availability:
The system should have an availability of 99.99%.
3.4.5Portability:
The system should be extremely via the usb drive. The
system shall be easy to migrate or backed up via another use
drive.
3.4.6Maintanability:
The system shall utilize interchangeable plugins.The
system shall be easily updateable for fixes and patches. The
system shall be easy to upgrade.
3.5 Quality Requirements:
This section decreases issues related to security and
safety of the product.
3.6 Security:
There would be soma risks of details of any customer
are gone out. Therefore each user is provided with username
and password using which they can access their own details.
The product is password protected.
3.7 Safety:
The user must logout before closing the project to
prevent malicious access or destruction.
4. CONCLUSION:
Future Enhancement: The project can be upgraded to make
it as an international accessing of stock maintenance system
that owner/ manager can access easily and effectively from
anywhere.

Gantt Chart For Stock Maintenance System

A Gantt chart is a type of chart that illustrates a project
schedule. Gantt charts illustrate the start and finish dates of
the terminal elements and summary elements of a project.
Terminal elements and summary elements comprise the
32

work structure of the project. Some Gantt charts also show the
dependency (i.e., precedence network) relationships between
activities.

Assumptions:
The assumptions for the stock management are as follows:

33

 Access to stock management system is provided only to

authorized persons like manager.
The application operates for a single stock management
system only.
The user has basic knowledge about working of
computers and gives appropriate data for the required
fields.

UML DIAGRAM FOR STOCK MAINTENANCE

SYSTEM

34

USECASE DIAGRAM:

logging

logs in
update inventory

inventory manager

order processing
clerk

item unavailability
demands item from stock
check inventory status
process order
produce stock summary report

purchase for stock

remove expired items

billing

makes payments for inventory

purchase
accountant

deposit money

CLASS DIAGRAM:

35

inventory
item_name
in_stock_quantity
total_sale
price
list of_vendors
vendor_address
vendor_phone
purchase_pending_items

order
Order No
deliverydate
orderedBy
totalamount

update_inventory()
check_status()
purchase_items()
make_bills()
remove_items()
generate_stocksummary_report()

process_order()

item
name
brand
quantity
price

accountant
name
password

payment
amount

cash payment

check_availability()

make_bills()
makes_payment()
deposit_money()

credit card
payment

STATECHART DIAGRAM:

Loging enter username and password

exit/logs in exit/invalid Username or password

log out

ACTIVITY DIAGRAM:

36

Search for
item

Update Stock

Purchase
items

Process Bill

purchase
order
verity of order

invalid

valid

payment

deliver
items

SEQUENCE DIAGRAM:
37

/order

/inventory
manager

/stock maintenance
system

/stock database

1:logs in()
2:validate()

3:send validity

4:demands items to fullfill the order()

5:check availability status()
6:checking availability()

8:send availability status()

9:process order()

10:update()

11:update database()
/accountant
12:generate bill()

13:send billing()

14:logs out()

COLLABORATION DIAGRAM:

38

4:demand item()

1: logs in()
5: check status() 2:validate()
8: process order()
13:logs out()

/inventory
manager

send status()

11:generate bill()
11:
2:

/stock maintenance system

3: send validity()

/order

12: send billing()

7: send availability()
6: checking availability()
9: update()

10: update database()

/accountan
t

/stock
database

PACKAGE DIAGRAM:

update inventory

login

order

purchase

COMPONENT DIAGRAM:
39

login

update
inventory

payment

make bills

cash
payment

credit card
payment

IMPLEMENTATION:
40

purchase

order

FORM1-LOGIN:
Public Class Form1
Dim conn As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=C:\Documents and Settings\user\My
Documents\stock.accdb")
Dim cmd As New OleDbCommand("", conn)
Dim res As OleDbDataReader
Private Sub Label1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Label1.Click
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Dim count As Integer
conn.Open()
cmd = New OleDbCommand("select * from manager",
conn)
res = cmd.ExecuteReader
count = 0
While (res.Read)
If TextBox1.Text = res.GetValue(0).ToString() And
TextBox2.Text = res.GetValue(1).ToString() Then
count += 1
End If
End While
conn.Close()
If count = 1 Then
MessageBox.Show("valid user")
Form2.Show()
Else
MessageBox.Show("Enter correct user name & pwd")
End If
End Sub

41

FORM2-WELCOME:
Public Class Form2
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Form3.Show()
Me.Close()
End Sub
End Class
FORM3-PURCHASE&STOCK VERIFICATION:
Public Class Form3
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Form4.Show()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
Form4.Show()
End Sub
End Class
FORM4-LIST OF PRODUCTS:
Public Class Form4
Private Sub Form4_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
ComboBox1.Items.Add("stationary")
ComboBox1.Items.Add("dress")
ComboBox1.Items.Add("jewellery")
End Sub
Private Sub ComboBox1_SelectedIndexChanged(ByVal
sender As System.Object, ByVal e As System.EventArgs)
Handles ComboBox1.SelectedIndexChanged
End Sub
42

Private Sub Button1_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles Button1.Click
If ComboBox1.SelectedItem = "stationary" Then
TextBox1.Text = "a"
Form5.Show()
ElseIf ComboBox1.SelectedItem = "dress" Then
TextBox1.Text = "b"
Form5.Show()
ElseIf ComboBox1.SelectedItem = "jewellery" Then
TextBox1.Text = "c"
Form5.Show()
End If
End Sub
FORM5-ITEMS,MODEL &QUANTITY:
Public Class Form5
Dim conn As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=C:\Documents and Settings\user\My
Documents\stock.accdb")
Dim cmd As New OleDbCommand("", conn)
Dim res As OleDbDataReader
Dim da As New OleDbDataAdapter
Dim dt As New DataTable
Dim dt1 As New DataTable
Dim dt2 As New DataTable
Private Sub Form5_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
If Form4.TextBox1.Text = "a" Then
ComboBox1.Items.Add("pen")
ComboBox1.Items.Add("notebooks")
ComboBox1.Items.Add("pencil")
End If
If Form4.TextBox1.Text = "b" Then
43

ComboBox1.Items.Add("churidhar")
ComboBox1.Items.Add("sarees")
End If
If Form4.TextBox1.Text = "c" Then
ComboBox1.Items.Add("earing")
ComboBox1.Items.Add("ring")
End If
End sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Dim i As New Integer
Dim s As String
If Form4.TextBox1.Text = "a" Then
s = ComboBox2.SelectedItem
conn.Open()
da = New OleDbDataAdapter("select Quantity from
stationary where ptype='" & s & "' ", conn)
dt = New DataTable
da.Fill(dt)
i = dt.Rows(0).Item(0)
i = i - Val(TextBox1.Text)
conn.Close()
conn.Open()
cmd.CommandText = "update stationary set Quantity =
' " & i & " ' where ptype = '" & s & "' "
cmd.ExecuteNonQuery()
MessageBox.Show("Quantity Updated")
conn.Close()
Me.Close()
End If
If Form4.TextBox1.Text = "b" Then
s = ComboBox2.SelectedItem
conn.Open()
da = New OleDbDataAdapter("select Quantity from
dress where ptype='" & s & "' ", conn)
44

dt1 = New DataTable

da.Fill(dt1)
i = dt1.Rows(0).Item(0)
i = i - Val(TextBox1.Text)
conn.Close()
conn.Open()
cmd.CommandText = "update dress set Quantity = ' "
& i & " ' where ptype = '" & s & "' "
cmd.ExecuteNonQuery()
MessageBox.Show("Quantity Updated")
conn.Close()
Me.Close()
End If
If Form4.TextBox1.Text = "c" Then
s = ComboBox2.SelectedItem
conn.Open()
da = New OleDbDataAdapter("select Quantity from
jewellery where ptype = '" & s & "' ", conn)
dt2 = New DataTable
da.Fill(dt2)
i = dt2.Rows(0).Item(0)
i = i - Val(TextBox1.Text)
conn.Close()
conn.Open()
cmd.CommandText = "update jewellery set Quantity =
' " & i & " ' where ptype = '" & s & "' "
cmd.ExecuteNonQuery()
MessageBox.Show("Quantity Updated")
conn.Close()
Me.Close()
End If
End Sub

45

Private Sub ComboBox1_SelectedIndexChanged(ByVal

sender As System.Object, ByVal e As System.EventArgs)
Handles ComboBox1.SelectedIndexChanged
If ComboBox1.SelectedItem = "pen" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("cello")
ComboBox2.Items.Add("pinpoint")
ElseIf ComboBox1.SelectedItem = "notebooks" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("classmate")
ComboBox2.Items.Add("schoolmate")
ElseIf ComboBox1.SelectedItem = "pencil" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("apsara")
ComboBox2.Items.Add("Nataraj")
End If
If ComboBox1.SelectedItem = "churidhar" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("anarkali")
ComboBox2.Items.Add("masakali")
ElseIf ComboBox1.SelectedItem = "sarees" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("pattu")
ComboBox2.Items.Add("cotton")
End If
If ComboBox1.SelectedItem = "earing" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("gold")
ComboBox2.Items.Add("diamond")
ElseIf ComboBox1.SelectedItem = "ring" Then
ComboBox2.Refresh()
ComboBox2.Items.Add("platinum")
ComboBox2.Items.Add("diamond")
End If
End sub
46

End Class
OUTPUT FORMS

47

48

49

INVENTORY DATABASE

RESULT :
Thus the Stock Maintenance System project was
executed successfully.
50

CREDIT CARD PROCESSING

AIM:
To develop a System that can perform credit based
banking transaction.
PROBLEM STATEMENT:
Credit card is used by customers for the transactions and
processing money between customers. When the customer uses
credit card, the administrator enquires about the pin number and
the authentication details. If all the details given by the customer
are valid then the transaction of money takes place. When it is
used for processing money for institutions transactions and
retransactions takes place between the customer and the agent for
sponsoring finance and manage customer account.
1.INTRODUCTION:
The main aim of this project is to define the functional
requirements of the project CREDIT CARD PROCESSING
SYSTEM which includes the project specification and project
goals.
1.1. Purpose:
The main aim of the project is to credit the amount to
the merchants account once the card is swiped by the card
issuer. Also the user receives product.
1.2. Scope of the product:
The Project banking system allows the individual bank
customers who owns current account to get credit up to
certain limit.
51

 Once they reach the limit they have to repay the amount
received as credit along with its interest to the respective

bank.
The account entries and the credit management are done by
the administrator.

1.3. References:
IEEE SRS Format.
1.4. Overview:
This document covers the overall description of what credit
card processing system project is expected to perform.
The project aims at customers and pays for their
requirements, records the credit details, customers pays it
back once the credit is over the limit.
2.GENERAL DESCRIPTION:
This section gives a high level description of the project
and set forth its user requirements. In actual, it provides
background for the requirements.
2.1 Context of the product:
The project is a small subsection of a banking system.
The project aims to reduce the instant payment of cash for any kind
of purchase (within a limit) by making the bank services as
customer friendly.
2.2 Product functions:
Module 1:
Login: The credit card number is entered and is verified by the
authorizer whether the card is accessible or not.
Module 2:
In the transaction form the account number of the
merchant and the amount to be transacted must also submitted.
52

Module 3:
The next process is if the amount to be credited is
within the main balance the process is done and the product is
received by the user.
Storage:
The details entered by the authorizer are stored in
different fields in the database.
2.3 User characteristics:
2.3.1 End Users

No specific knowledge or skills are required from the

end user.

End user should have basic idea about computer

operations and database.

2.3.2 Administrator

Administrator must be having good knowledge of

database management system.

Administrator must be capable to manage user rights.

If the network connection does not work properly than

our system should not work as intended. Also that is
assumed that the product is installed properly at web
server.

This system will not take care of any virus problem,

which might occur either on the client or the server
system. Avoiding the use of pirated software and
ensuring that floppies and other removable media are
scanned for viruses before use could minimize the
possibility of viral infection.
53

Recovery of data after a system crash will be possible

only if backups are taken at regular intervals.

2.4 Assumptions:

The code should be free with compilation errors/syntax

errors.

The product must have an interface which is simple

enough to understand.

3.SPECIFIC REQUIREMENTS:
This section provides technical information about the
product that will be needed to design the software.
3.1 External Interface Requirements:
Describes the user interface characteristics
-user opens the main page which displays option such as
register or cancel.
-Each option is linked to another page where user details and
fees payment details are updated.
-The monitor displays the project.
-The mouse and/or keyboard are used for data entry and/or to
make selections.
3.2. User interface:
Card swapping machine, PC.
3.2.1Hardware interface:
1.128 MB RAM
2. Pentium III processor
3.2.2 Software Interface

54

Front End: Microsoft visual Studio 2008, Rational

Rose software.
Back End: MS Access
3.3 Functional requirements:
The different steps followed in using the project by
the user is described in this section
Login:
The user must have valid credit card number .If
the card is valid the merchant can credit the amount from
user account to merchant account.
Update Details:
The database is updated by the administrator
once the transaction has been made.
3.4 Performance Requirements:
The project is designed for over user at a time. The
number of page will be more or less10.The navigation from one
page to another takes place, within fraction of seconds. Since the
data is stored in database, huge amount of data can be accessed and
data storage is possible.
3.5 Quality requirements:
This session discusses issues related to security and
safety of the product.
3.5.1 Security:
There would be some risk if the credit has exceeded
the limit else delay in repayment
3.5.2 Safety:
The card holder must keep the card safely to prevent
unwanted access .Password must be protected. Each user is
55

provided with username and password using which they can access
their own details. The product is password protected.
4 CONCLUSION:
Future Enhancement:
The project can be upgraded to make it as a self
accessing method, so that users can be accessed easily and
effectively.

Gantt Chart For Credit Card Processing

A Gantt chart is a type of chart that illustrates a project
schedule. Gantt charts illustrate the start and finish dates of
the terminal elements and summary elements of a project.
Terminal elements and summary elements comprise the
work structure of the project. Some Gantt charts also show the

56

dependency (i.e., precedence network) relationships between

activities.

Assumptions:
The card number and pin number generated to the
enrolled customer is unique.

57

 The user has basic knowledge about working of

computers and gives appropriate data for the required
fields.

UML DIAGRAMS FOR CREDITCARD

PROCESSING

USE CASE DIAGRAM:

58

receives the product

swipe
purchase
Merchant
customer

credit card

authorize the transcation

sumbits request

Acquirer bank
sends request to authorize the
transcation
Card issuer

check valid credit or not

authorization code send

valid

bill the customer

CLASS DIAGRAM:

59

credit card system

card number : int
bank name : string
card issuer name : string
card swiper : card swiper
message log : message log
1
card number()
get cardswiper()
get card issuer name()
get message log()

Transaction

customer
name
account number
address
card number
bank balance
phone number
card network

card swiper

card

name
account number
address
bank balance
phone number

card number

number

card swiper()
read card()
retain card()

card()
get card number()

customer()
get card number()
get balance()
1

card number
account number
transaction state
time : date time
message
bank name

merchant

transaction()
create transaction()
perfom transaction()
get message from bank()
complete transaction()

merchant()
get account number()

*
account
account number
bank name
balance amount
account()
get account number()
get balance amount()

1..*
credit
displays

message log
message log()
display log()

STATE CHART DIAGRAM:

60

debit

balance enquiry

amount

amount

account number

credit()
get message from bank()
complete transaction()

debit()
get message from bank()
complete transaction()

balance enquiry()
get message from ban
complete transaction()

Card holder

Merchant
Swipe the card

start

start

submit request to acq

Card holder
Acqurier

Swipe the card

sends req to issuer

Merchant
Card Issuer

submit request to acq

allows authorisation

Acqurier

Card
validated

sends req to issuer

authorize transaction

Card Issuer

Authoriztion code
sent to acqurier

card holder
is billed

card holder receives product

validity

no
stop

yes
Authoriztion code
sent to acqurier

ACTIVITY DIAGRAM:
card holder
is billed

61

card holder receives product

stop

SEQUENCE DIAGRAM:

62

Figure 1: Activity Diagram

Customer

Merchant

Acqurier bank

issuer

request purchase
Swipe and return
sumbits request
request for authorization

authorization code sent

authorize transcation
receive product

batches the sales

request payement

funding

pays to merchant

card holder is billed

COLLABORATION DIAGRAM:
63

4: request for authorization

9: request payement
Acqurier
bank

issuer
5: authorization code sent
10: funding

3: sumbits request
8: batches the sales
12: card holder is billed
6: authorize transcation
11: pays to merchant
2: Swipe and return
7: receive product
Merchant

Customer
1: request purchase

13:

COMPONENT DIAGRAM:

user
interface

Credit card
system

Bank
system

uses

card swiper
customer
accoun...

card is suer

PACKAGE DIAGRAM:
64

bank
database

merchant

submit details

bank db

issues product
to customer.

IMPLEMENTATION
Welcome form
65

Public Class Form1

Private Sub Form1_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Form2.Show()
End Sub
End Class
Credit form coding
Imports System.Data.OleDb
Public Class Form2
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=C:\Documents and Settings\user\My
Documents\Database2.accdb")
Dim cmd As New OleDbCommand
Dim res As OleDbDataReader
Private Sub Label2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs)
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Dim count As Integer
con.Open()

66

cmd = New OleDbCommand("select * from customer",

con)
res = cmd.ExecuteReader
count = 0
While (res.Read)
If TextBox1.Text = res.GetValue(9) Then
count += 1
End If
End While
con.Close()
If count = 1 Then
MessageBox.Show(" card is accessible")
transaction_form.Show()
Me.Close()
Else
MessageBox.Show("enter correct no")
End If
End Sub
Private Sub Form2_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
End Sub
End Class
Transaction coding
Imports System.Data.OleDb
Public Class transaction_form
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da

67

ta Source=C:\Documents and Settings\user\My

Documents\Database2.accdb")
Dim cmd As New OleDbCommand
Dim res As OleDbDataReader
Dim da As New OleDbDataAdapter
Dim dm As New OleDbDataAdapter
Dim bm As DataTable
Dim dt As DataTable
Dim ds As DataSet
Private Sub transaction_form_Load(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
TextBox2.Text = Val(Form2.TextBox1.Text)
'TextBox3.Text = Val(Form2.TextBox2.Text)
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
con.Open()
da = New OleDbDataAdapter("select * from customer
where creditcardno= " & TextBox2.Text & " ", con)
dt = New DataTable()
da.Fill(dt)
dm = New OleDbDataAdapter("select * from merchants
where Accountnumber= " & TextBox3.Text & " ", con)
bm = New DataTable()
dm.Fill(bm)
Dim a As Integer
Dim b As Integer
Dim c As Integer
68

Dim d As Integer
a = dt.Rows(0).Item(6)
c = bm.Rows(0).Item(3)
If Val(TextBox1.Text) <= a Then
b = a - Val(TextBox1.Text)
MessageBox.Show("Amount to be transacted is with in the
available balance")
Else
MessageBox.Show("Credit amt is too low to make a
transaction")
End If
con.Close()
con.Open()
cmd = New OleDbCommand("update customer set
TotalBalance = " & b & " where creditcardno= " &
TextBox2.Text & " ", con)
cmd.ExecuteNonQuery()
MessageBox.Show("updated")
con.Close()
con.Open()
d = c + Val(TextBox1.Text)
MessageBox.Show("Amt is debited")
cmd = New OleDbCommand("update merchants set
CurrentBalance = " & d & " where Accountnumber= " &
TextBox3.Text & " ", con)
cmd.ExecuteNonQuery()
con.Close()
End Sub
End Class
69

OUTPUT FORMS:

70

71

MERCHANTS DATABASE:

72

RESULT :
Thus the Credit Card Processing System project was
executed successfully.

E-BOOK MANAGEMENT SYSTEM

AIM:
To develop a system that can perform E-book
management.
1. INTRODUCTION:
E-book management gives an idea about how are
maintained in the particular concern. The books are to be
purchased and sold are maintained here. Further some
73

additional details of the current e-book list that is available in

the website are also given. E-book management in this project
is done in an authorized way.
1.1 Purpose:
The purpose of E-Book management system is to store
and sell the books in a website effectively.
1.2 Scope of the Product:
The scope of this eBooks management is to maintain the
book details after the purchase and list of reaming books
available in the same book type.
Software provides following facilities to customer:
Facilitates easy shopping online.
Provides information about the products in categories.
Provides e-mail facility for future correspondence.
Provides Backup facility.
Software provides the following facilities to the
merchant.
Manages the Transportation of hard copy of Book.
Look after the payment method.
1.3 Project Overview:
The overview of the project is to Storing of information
about the and updating the eBooks list for each organization
which is using this system, keeps track of all the information
about the purchased that are made by the customers, having
registration feature of adding up new customers to the
organization are provided in this system.
1.4. Acronyms, Abbreviation, Definition:
E-Book-Electronic book
74

 E-Reader-Ebook reader
1.5 References:
IEEE SRS Format.
2. GENERAL DESCRIPTION:
2.1 Product Functions :
Login:
The login is used for security of the customer. The
customer logs in with the user name and the password of the
customer.
Analysis:
The eBooks manager analysis the books. He identifies
the books and keeps track of the books currently read by the
user and also the list of books needed by the customer.
Old book clearance:
The e-book manager clears the old books by selling it at
a offer price.
Order List Preparation:
The e-book manager prepares the list of items to be
bought. Then he calls the company for quotations.
Purchase:
The e-book manager purchases the needed books from
the corresponding websites.
Payment:
The customer pays the bill along with the tax and the
books are delivered.
2.2 User Characteristics:
2.2.1 End User:
75

 The new user can be added to this application by

entering the name, address, email.
The user can order any number of books.
2.2.2 Administrator:
Only the administrator can see the list of persons
those who have ordered the books, the books read
by the user.
The administrator keeps track of the books
purchased, ordered, read by the customer always.
3. SPECIFIC REQUIREMENTS:
3.1. Hardware Requirements:
1. Processor-Intel Pentium IV-2.0 GHZ.
2. Hardware- 40 GB(segate).
3. RAM-512mb.
4. DVD RAM - 1 nos.
3.2 Software Requirements:
1. OS - windows XP/vista.
2. Front end Tool - Rational Rose Enterprise suite.
3. Back end Tool - Oracle 10i.
3.3

Functional Requirements:
Register - Enter details in application form.
Login - Enter Username and Password.
Search - Search book by attribute.
Buy - Download softcopies and order for hard copy.
Payment - Pay for books in different method.
76

 Update - Update User detail.

3.4

Non- Functional Requirements:

Bookmark - Bookmark the Website.
Categories - Book categories in Website.
Most Downloaded - Highest purchased book.
Offers - Offer given by merchant.
Carting - Mark and select multiple books.

3.4.1

Performance Requirement:

It describes the capability of the system to perform the

e-book management system of the store without any error and
performing it efficiently.
3.4.2 Design Constraint:
Many books can be added and all the kinds of books can
be searched. It can either be downloaded or searched. The
design can be extended for any number of users and it is easy
for maintaining the records.
3.4.3 Reliability:
The e-book management system should be able to serve
the customer with correct information and day To day update
of e-book list details.
3.4.4 Portability:
User interface makes the Recruitment system to be
efficient. That is the system will help the applicant to register
easily and helps the companies to recruit the applicant
effectively. The system should be user friendly.
3.4.5 Maintainability:

77

The new books ordered and the books ordered can be

maintained easily with the database. Ebook manager is
responsible for all informations in it.
3.4.6 Quality Requirements:
This section decreases issues related to security and
safety of the product.
3.4.6.1 Security:
Each user is provided with username and password
using which they can access their own details by the orders.
The product is password protected.
3.4.6.2 Safety:
The user must logout before closing the project to
prevent malicious access.

4. CONCLUSION:
Future Enhancement:
The project can be upgraded to make it as an
international accessing of e-book maintenance system that
owner/ manager can access easily and effectively from
anywhere.

78

Gantt Chart For E-Book Management

System
A Gantt chart is a type of chart that illustrates a project
schedule. Gantt charts illustrate the start and finish dates of
the terminal elements and summary elements of a project.
Terminal elements and summary elements comprise the
work structure of the project. Some Gantt charts also show the
dependency (i.e., precedence network) relationships between
activities.

79

Assumptions:

The id generated to the enrolled candidates is unique.

80

 The user has basic knowledge about working of

computers and gives appropriate data for the required
fields.

UML DIAGRAMS FOR EBOOK MANAGEMENT

SYSTEM

USE-CASE DIAGRAM:
81

registration

authorization

search books
user

administrator

get books

<<extend>>
payment

cash

credit
help

CLASS DIAGRAM:

82

books
customer

operating system
computer architecture
dbms
web technology
ooad

name
address
cont no
login()
payment()

select()
buy()

database
operation
store()

STATE CHART DIAGRAM:

Login

Search
Books

ACTIVITY DIAGRAM :

83

View/
Purchase

Logout

s tart

register

login
invalid,id or pas s word

valid id,pas s word

check availability of
book
s earch another book

available
buy book

s elect dis count

pay for the book

end

SEQUENCE DIAGRAM :
84

Request to Buy
the book
Request for registration

system

Database

Registration form

Fill the details and submit

Store into the database

Enter the nam e and password to login

Fill the details and submit

save the details

Search the book

retrive the book details

give the details

Display the book details

Request to buy

pay the am ount

check am ount<Balance

Show the message (your book will delivered soon)

Update

COLLABORATION DIAGRAM:
85

1: Request for registration

3: Fill the details and submit
6: Fill the details and submit
8: Search the book
12: Request to buy
13: pay the amount
system

Request to Buy the

book
2: Registration form
5: Enter the name and password to login
11: Display the book details

16: Update
15: Show the message (your book will delivered soon)

10: give the details

4: Store into the database
7: save the details
9: retrive the book details
14: check amount<Balance

Database

COMPONENT DIAGRAM:

e book homepage
registeration
form

updation
form

login
form

search
form

ordering
form

86

payment
form

DEPLOYMENT DIAGRAM:

e book management

payment
select
book

IMPLEMENTATION
FORM1:
Imports System.Data.OleDb
Public Class Form1
Dim i As Integer
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=E:\suganya\ooadebook.accdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Label3_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Label3.Click
End Sub
Private Sub Button2_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button2.Click
87

con.Open()
cmd.CommandText = "insert into register values('"
& TextBox1.Text & "','" & TextBox2.Text & "'," &
TextBox3.Text & ",'" & TextBox4.Text & "','" &
ComboBox1.Text & "','" & TextBox5.Text & "')"
cmd.ExecuteNonQuery()
MessageBox.Show("inserted")
con.Close()
Form2.Show()
Me.Hide()
End Sub
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
TextBox1.Text = ""
TextBox2.Text = ""
TextBox3.Text = ""
TextBox4.Text = ""
TextBox5.Text = ""
ComboBox1.Text = ""
End Sub
Private Sub
ComboBox1_SelectedIndexChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
ComboBox1.SelectedIndexChanged
End Sub
End Class
88

FORM2:
Imports System.Data.OleDb
Public Class Form2
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=E:\suganya\ooadebook.accdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button2_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button2.Click
TextBox1.Text = ""
TextBox2.Text = ""
End Sub
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
con.Open()
cmd.CommandText = "insert into login values('" &
TextBox1.Text & "','" & TextBox2.Text & "')"
cmd.ExecuteNonQuery()
MessageBox.Show("inserted")
con.Close()
Form3.Show()
Me.Hide()
End Sub
Private Sub TextBox1_TextChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
TextBox1.TextChanged
89

End Sub
End Class
FORM3:
Imports System.Data.OleDb
Public Class Form3
Dim i As Integer
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=E:\suganya\ooadebook.accdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Form3_Load(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
MyBase.Load
End Sub
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
ComboBox1.Text = ""
TextBox1.Text = ""
TextBox2.Text = ""
End Sub
Private Sub TextBox1_TextChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
TextBox1.TextChanged, TextBox2.TextChanged
End Sub
Private Sub Button2_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button2.Click
90

con.Open()
cmd.CommandText = "insert into search values('"
& ComboBox1.Text & "','" & TextBox1.Text & "','" &
TextBox2.Text & "')"
cmd.ExecuteNonQuery()
MessageBox.Show("inserted")
con.Close()
Form4.Show()
Me.Hide()
End Sub
Private Sub
ComboBox1_SelectedIndexChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
ComboBox1.SelectedIndexChanged
End Sub
End Class
FORM4:
Imports System.Data.OleDb
Public Class Form4
Dim i As Integer
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=E:\suganya\ooadebook.accdb")
Dim cmd As New OleDbCommand("", con)

Private Sub Label1_Click(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles
Label1.Click
91

End Sub
Private Sub Button2_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button2.Click
Form5.Show()
Me.Hide()
End Sub
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
MsgBox("your book is downloading")
End Sub
End Class
FORM5:
Imports System.Data.OleDb
Public Class Form5
Dim i As Integer
Dim con As New
OleDbConnection("Provider=Microsoft.ACE.OLEDB.12.0;Da
ta Source=E:\suganya\ooadebook.accdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
MsgBox("PAID!!!!!!.......your book will be
delivered soon")
End Sub
End Class
92

OUTPUT FORMS:

93

94

Result:
Thus the E-book Management system was executed
successfully.
ONLINE TICKET RESERVATION SYSTEM

AIM :
To develop a system that can perform online ticket
reservation.

PROBLEM STATEMENT:
Going to the movie theaters is a fun and enjoyable event.
Unfortunately standing in line to purchase movie tickets can
take forever. You may lose out on a good movie seat and rush
to get your snacks. To buy tickets online and to beat the movie
crowd e-ticketing is necessary.
95

1. INTRODUCTION
1.1

Purpose of the document:

The Online ticket reservation web application is
intended to provide complete solutions for vendors as
well as customers through a single get way using the
internet as the booking medium. It will enable vendors
to setup online reservation centers, customer to browse
through the centers and purchase them online without
having to visit the shop physically. The administration
module will enable a system administrator to approve
and reject requests for new centers and maintain various
lists of ticket category.

1.2

Scope of the product:

Initial functional requirements will be: Secure registration and profile management
facilities for Customers
Browsing through the e-reservation to see the
items that are there in each category of products
like movies, theatres, timings etc.
Adequate searching mechanisms for easy and
quick access to particular trains and services.
Creating a booking number so that customers can
book n no. of tickets and checkout finally with
the entire booking details.
Maintaining database of regular customers of
different needs.
Adequate payment mechanism and gateway for
all popular credit cards.

1.3

Definitions, Acronyms and Abbreviations

HTTP: Hypertext Transfer Protocol is a transaction
oriented client/server protocol between a web browser
& a Web Server.
HTTPS:Secure Hypertext Transfer Protocol is a HTTP
over SSL (secure socket layer).
TCP/IP:Transmission Control Protocol/Internet
Protocol, the suite of communication protocols used to
96

connect hosts on the Internet. TCP/IP uses several

protocols, the two main ones being TCP and IP.
1.4

References
IEEE SRS Format

1.5

Overview
The rest of this SRS is organized as follows: Section 2
gives an overall description of the software. It gives
what level of proficiency is expected of the user, some
general constraints while making the software and some
assumptions and dependencies that are assumed. Section
3 gives specific requirements which the software is
expected to deliver. Functional requirements are given
by various use cases. Some performance requirements
and design constraints are also given.

2.GENERAL DESCRIPTION
2.1Context of the product
Online ticket reservation is aimed towards the vendors
who want to reach out to the maximum cross-section of
customer and common people who can be potential customer.
This project envisages bridging the gap between the seller, the
retailer and the customer. Online ticket reservation should be
user-friendly, quick to learn and reliable software for the
above purpose. Online ticket reservation is intended to be a
stand-alone product and should not depend on the availability
of other software. It run on Windows based platform.
2.2Product functions
User : Administrator
Functions : The Administrator is the super user and has
complete control over all the activities that can be
performed. The application notifies the administrator of
all customer access requests, and the administrator can
then approve or reject them. The administrator also
manages the list of available train route categories. The
administrator can also view and delete entries in the
booked tickets.
97

User : Customer
Functions: A Customer can browse through the
reservation centre and choose trains to place in a virtual
booking cart. The booking cart details can be viewed
and items can be removed from the cart. To proceed
with the booking, the customer is prompted to login.
Also, the customer can modify personal profile
information (such as phone number and shipping
address) stored by the application. The customer can
also view the status of any previous orders, and cancel
any order that has not been shipped yet.
2.3 User characteristics
The user should be familiar with the booking related
terminology
like
booking
number/Checking
out/Transaction etc.
The user should be familiar with the Internet.
2.4Assumptions
There is no maintainability of back up so availability
will get affected.
Limited to HTTP/HTTPS.
Real-life credit card validation and Banking system is
not implemented.
No multilingual support.
3. SPECIFIC REQUIREMENTS:
This section provides technical information about the product
that will be needed to design the software.
3.1 External Interface Requirements:
Describes the user interface characteristics :
-user opens the main page which displays different options
include login form, menu form, shopping details, transaction,
checkout etc.
-Each option is linked to another page where customer details
and reservation details are updated.
98

-Each option has connected with database.

-The monitor displays the project.
-The mouse and/or keyboard are used for data entry and/or to
make selections.

3.1.1 User Interface

Keyboard, Mouse
3.1.2 Hardware Requirements
PC with Windows XP
3.1.3 Software Interface
Front End: Microsoft visual studio 2008
Back End: MS Access
3.2 Functional Requirements
The different steps followed in using the project by the
user is described in this section.
3.2.1 Login
Use case
:
Login
Trigger
:
Menu selection (combo
box),keyboard
Basic path
:
The user feeds the username and
password verified
by the system appropriate message is
displayed.
Post Condition :
The process is navigated to the menu
page.
3.2.2 Menu
Use case
Trigger

:
:

Menu
Menu Selection
99

Basic path
and the user is
Post condition
accordance

The user clicks the different options

navigated to respective pages.

The page displayed next must be in
with the button clicked in the current

page.
3.2.2 Booking Details
Use case
Trigger
Basic path

:
:
:

Post condition

Booking id
Keyboard input
The administrator has the only right
to use this page, but with the details
provided from the customer. The
details are stored to the database.
After the details being stored in
database, the administrator is logged
out.

3.2.3 Logout
Use case
:
Logout
Trigger
:
Button click
Basic path
:
The user must logout from the main
page before closing.
Post condition :
The user is navigated to login page.
3.3 Performance Requirements:
The project is designed for one user at a time. The
number of page will be more or less 10. The navigation from
one page to another page takes place within a fraction of
seconds.
Since the data is stored in database, huge amount of
items can be shopped and data storage is possible. 95% of
credit card transaction shall be processed in less than one
second.
3.4Quality Requirement:

100

This session discusses issues related to security and safety of

the product.
3.4.1 Security:
There would be some risks if the detail of the
customer is gone out. Therefore each user is provided with
username and password, using which they can access their
own details. The product is password protected.
3.4.2 Safety:
The user must logout before closing the project to
prevent malicious access or destruction.
4. CONCLUSION
Future Enhancement:
The project can be upgraded to reserve tickets (for all states in
India). So that customer can reserve movie tickets from
anywhere.

UML DIAGRAMS FOR ONLINE RESERVATION

SYSTEM

USE CASE DIAGRAM

101

LOGIN

MOVIE INFO

TIMING
BUYER

SELLER

TICKET INFO

PAYMENT

CREDIT

DEBIT

CLASS DIAGRAM

LOGIN

view

user name
password

MOVIE INFO
movie name
theatre name

PAYMENT
book
TICKET
class
seat count

TIMINGS
show time

ACTIVITY DIAGRAM

102

mode
date
acc_no
bank name

Enter user
name

Enter
pass word

invalid

valid
Enter theatre
name

Enter movie
name

Enter s how
timing

Select
class

s elect no of
s eats

mode of
payment

debit card

credit card

enter card
no

enter acc
no
enter acc
holder name

enter name

reservation
confirmed

SEQUENCE DIAGRAM
103

:User
1: Login

:Theatre
admin sys

:Theatre Db

2: Authenticate

3: Login successfull
4: Valid or INvalid
5: Enter theatre name
6: Search for theatre name

7: Enter movie name

8: Search for movie name

9: Select show timing

10: Select class

11: Select total no of seats

12: Check for availability

13: Payment
14: receive payment details

15: Reservation status

16: Reservation confirmed

COLLABORATION DIAGRAM
7: Enter movie name
9: Select show timing
10: Select class
11: Select total no of seats
13: Payment

:User

:Theatre
admin sys
3: Login successfull
16: Reservation confirmed

:Theatre
Db

4: Valid or INvalid
2: Authenticate
15: Reservation status
6: Search for theatre name
8: Search for movie name
12: Check for availability
14: receive payment details

COMPONENT DIAGRAM
104

ticket
booking

user reg

authentic
ation

availabilit
y

ticket
payment

response
msg

DEPLOYMENT DIAGRAM

ticket
bo...

user
reg

authen
tic...

availa
bility

ticket
p...

IMPLEMENTATION
105

response
msg

LOGIN:
Imports System.Data.OleDb
Public Class Form1
Dim con As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Dim res As OleDbDataReader
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
Dim c As Integer
con.Open()
cmd = New OleDbCommand("select * from login", con)
res = cmd.ExecuteReader
While res.Read
If TextBox1.Text = res.GetValue(0) And TextBox2.Text
= res.GetValue(1) Then
c += 1
End If
End While
con.Close()
If c = 1 Then
MessageBox.Show("login successful")
Form2.Show()
Me.Hide()
Else
MessageBox.Show("Invalid entry")
End If
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Me.Close()
End Sub
End Class

MOVIE INFO:
106

Imports System.Data.OleDb
Public Class Form2
Dim con As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
con.Open()
cmd.CommandText = "Insert into otherentries values('" &
theatre.Text & "','" & ComboBox2.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
Form3.Show()
Me.Hide()
End Sub
Private Sub Button1_Click(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
Button1.Click
Form1.Show()
End Sub
End Class
TIMINGS:
Imports System.Data.OleDb
Public Class Form3
Dim con As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
If RadioButton1.Checked = True Then
con.Open()
cmd.CommandText = "Insert into timing values('" &
RadioButton1.Text & "')"
cmd.ExecuteNonQuery()
107

ElseIf RadioButton2.Checked = True Then

con.Open()
cmd.CommandText = "Insert into timing values('" &
RadioButton2.Text & "')"
cmd.ExecuteNonQuery()
ElseIf RadioButton3.Checked = True Then
con.Open()
cmd.CommandText = "Insert into timing values('" &
RadioButton3.Text & "')"
cmd.ExecuteNonQuery()
ElseIf RadioButton4.Checked = True Then
con.Open()
cmd.CommandText = "Insert into timing values('" &
RadioButton4.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
End If
Form4.Show()
Me.Close()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Form2.Show()
End Sub
End Class
TICKET INFO:
Imports System.Data.OleDb
Public Class Form4
Dim con As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Me.Hide()
End Sub

108

Private Sub Button2_Click(ByVal sender As System.Object,

ByVal e As System.EventArgs) Handles Button2.Click
If CheckBox1.Checked = True Then
con.Open()
cmd.CommandText = "Insert into ticketinfo values('" &
CheckBox1.Text & "','" & TextBox1.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
ElseIf CheckBox2.Checked = True Then
con.Open()
cmd.CommandText = "Insert into ticketinfo values('" &
CheckBox2.Text & "','" & TextBox1.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
ElseIf CheckBox3.Checked = True Then
con.Open()
cmd.CommandText = "Insert into ticketinfo values('" &
CheckBox3.Text & "','" & TextBox1.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
ElseIf CheckBox4.Checked = True Then
con.Open()
cmd.CommandText = "Insert into ticketinfo values('" &
CheckBox4.Text & "','" & TextBox1.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
End If
Form5.Show()
Me.Hide()
End Sub
Private Sub CheckBox1_CheckedChanged(ByVal sender As
System.Object, ByVal e As System.EventArgs) Handles
CheckBox1.CheckedChanged
CheckBox1.Checked = True
End Sub
End Class
PAYMENT:
Imports System.Data.OleDb
Public Class Form5
109

Dim con As New

OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Form5_Load(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles MyBase.Load
ComboBox1.Items.Add("01")
ComboBox1.Items.Add("02")
ComboBox1.Items.Add("03")
ComboBox1.Items.Add("30")
ComboBox1.Items.Add("31")
ComboBox2.Items.Add("Jan")
ComboBox2.Items.Add("Feb")
ComboBox2.Items.Add("Dec")
ComboBox3.Items.Add("2015")
ComboBox3.Items.Add("2018")
End Sub
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
If RadioButton1.Checked = True Then
con.Open()
cmd.CommandText = "Insert into payment values('" &
RadioButton1.Text & "','" & ComboBox1.Text & "','" &
ComboBox2.Text & "','" & ComboBox3.Text & "')"
cmd.ExecuteNonQuery()
ElseIf RadioButton2.Checked = True Then
con.Open()
cmd.CommandText = "Insert into payment values('" &
RadioButton2.Text & "','" & ComboBox1.Text & "','" &
ComboBox2.Text & "','" & ComboBox3.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
End If
Form6.Show()
End Sub
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Me.Hide()
End Sub
End Class
110

CONFIRMATION:
Imports System.Data.OleDb
Public Class Form6
Dim con As New
OleDbConnection("Provider=Microsoft.Jet.OLEDB.4.0;Data
Source=E:\hamsa\eticket.mdb")
Dim cmd As New OleDbCommand("", con)
Private Sub Button1_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button1.Click
Me.Close()
End Sub
Private Sub Button2_Click(ByVal sender As System.Object,
ByVal e As System.EventArgs) Handles Button2.Click
con.Open()
cmd.CommandText = "Insert into bankinfo values('" &
TextBox1.Text & "','" & TextBox2.Text & "')"
cmd.ExecuteNonQuery()
con.Close()
MessageBox.Show("Your reservation is
successfull!!!!!!!!!!")
End Sub
End Class

111

OUTPUT FORMS

112

113

114

DATABASE

RESULT :
Thus the Online Ticket Reservation System project was
executed successfully.
115