Anda di halaman 1dari 111

ANNA UNIVERSITY, COIMBATORE

DEPARTMENT: COMPUTER SCIENCE AND ENGINEERING


SUBJECT CODE & NAME: OBJECT ORIENTED DESIGN LABORATORY
LIST OF EXPERIMENTS
Program list:
Solving Simple problems using CASE tools for design, testing with structure analysis
And design method and object oriented analysis and design method

i) SRS DOCUMENT (IEEE Standard)


ii) Design document
iii) Implementation
iv) Test case generation and test document preparation

1. Payroll system
2. Online shopping
3. Online voting system
4. Banking system

ONLINE VOTING
SOFTWARE REQUIREMENT SPECIFICATION:
1.INTRODUCTION:
To perform an project for online voting using visual basic to calculate votes in
online by selecting the nominees and display the results after voting .

1.1 Purpose:
The purpose of this document is to present a detailed description of the online voting
system.It will explain the features of the system, the interfaces provided by the system
and what the system will do.

1.2 Scope:
The scope of this project is to perform online voting. This is designed to display the
nominees to select for the customers to vote and display the result accurately and easily.
To store the databases of the nominees and the result, using MS-access.

1.3 Reference:
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software
Requirements Specifications. IEEE Computer Society, 1998.

1.4 Definition and Abbreviation:


Participant the members those who vote in the online for their favorite nominees.
Nominees the members for whom the vote has been given by the participants.
Database the software used to store the data and its transactions carried out in the
project.
UML Unified Modeling Language
VB Visual Basics

2.OVERALL DESCRIPTION:
The application is a fully functional voting software.It consists of three

modules.In the first module the voter logins and enters into the project.In the second
module a list of nominees for voting is displayed and vote for the favourite nominee.In
the third module display the results for all the nominees and displays the nominee with
the leading votes.

2.1 Product Perspective:


The overall description of the document gives an overview of the functionality of
the product. it describes the informal requirements and is used to establish a context for
the requirement specification.
Requirement Specification is primarily written for developers and describes in
technical terms and the details of functionality of the product.

2.2 Product Functions:


In the first module the voter logins and enters into the project.In the second
module a list of nominees for voting is displayed and vote for the favourite nominee.In
the third module display the results for all the nominees and displays the nominee with
the leading votes

2.3 User Characteristics:


Participant or customer a customer must know all the details of the online
voting, details about the nominees.
Database database should contain the details of the nominees and the no of
votes and the detail of the nominee who is leading.

2.4 General Constraints:


Login customer must enter a valid e-mail id
Voting a customer cannot vote for more than two nominees at a time.
Display display the number of votes for the nominees and the nominee with
leading votes.

3. SPECIFIC REQUIREMENTS:
Software Requirement specification is a document that describes all the functions
of a proposed system and the constraints under which it must operate.

3.1 External Interface Requirement:


external interfaces are nothing but what the developers know about the system or
about the project externally.

3.1.1 User Interfaces:


This is the interface that the user interacts with the system. Here coding acts as a
User interface.

3.1.2 Hardware Interfaces:


It describes the physical and logical characteristics between the software
products.
The hardware used in this project are
System
Printer etc

3.1.3 Software interfaces:


It describes the connection between the software and other components
VB
Ado control

3.1.4 Communication Protocol:


The protocol used for communication in this project is the database (i.e) msaccess in which details of nominees and voting transactions are carried out.

3.1.5 Memory Constraints:


320 GB of memory for hard disk space
1 GB of RAM
This project requires 271 Kb

3.1.6 Operation:
We should perform online voting in various operating environments. We perform
it by using VB and .net etc but its back end must be only MS - access for storing the
databases of the nominees and the result.

3.1.7 Product Functions:


Login and enter into the voting form.
Vote for your favorite nominees
Displaying the results.

3.2 Software Product Features:


In the past, voting was done by the people manually which had high complexity
in counting and announcing the results. The main feature of the online voting is that does
not require any complexity viewing the results instantly.

3.3 Software System Attributes:


3.3.1 Reliability
The system authenticates the voters to vote for their favorites. A
voter cannot vote more than once for a nominee. Another reliability of the system is that
it displays the nominee with the leading votes.

3.3.2 Availability
The voting server system is stable for voting at all times. Databases can
act as a server to display the results at all times.

3.3.3 Security
The system should require a valid e-mail id to login. Each and every
user should know their own email ids for their login.

3.3.4 Maintainability
The source code shall be available to the developers. Each updating
process can be added to the website and displayed simultaneously.

3.3.5 Portability
This online voting project is executable in all platforms such as internet
possessing systems.

3.3.6 Performance
:
The project well equipped with the recent networking technologies and
will result in high performance.

3.4 Database Requirements:


The database requirement of the project is Ms-access

4.DESIGNING:
Designing phase involves many UML diagrams

UML DIAGRAMS:
4.1 Use Case Diagram
4.2 Sequence Diagram
4.3 Collaboration Diagram
4.4 Class Diagram
4.5 Activity Diagram

4.1USE CASE DIAGRAM


DESCRIPTION:
A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases.
Usecases: A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse
Actors: An actor is a person, organization, or external system that plays a role in one or
more interactions with the system

STEPS FOR GENERATING USECASE DIAGRAM:


1. Double-click on the Main diagram in the use case view in the browser to open the
diagram.
2. Click to select an actor in the browser and drag the actor onto the diagram..
3. Repeat step 2 for each additional actor needed in the diagram.
4. Click to select a use case in the browser and drag the use case onto the diagram.
5. Repeat step 4 for each additional use case needed in the diagram.

Login

Selection of

Vote for nominees


<<uses>>
Participant

nominees
Calculate votes

Display votes
The use case for online voting describes the information about the

Login
Vote for nominees
Calculation of votes
Displaying the no of votes

4.2SEQUENCE DIAGRAM
DESCRIPTION:
A sequence diagram in Unified Modeling Language (UML) is a kind of
interaction diagram that shows how processes operate with one another and in what
order. It is a construct of a Message Sequence Chart.
The objects used in this sequence diagram are,
Participant
login
Display
Control
Database
7

In our voting system,


The participant logins by giving his/her details using the object login.
The object Display will then display the names of the nominees. Then the participant
chooses
the nominee to vote.
The object Control performs the duty of calculating the votes based on the selection of
nominees given by the participant.
Finally the result will be displayed by the object Display.

STEPS FOR GENERATING SEQUENCE DIAGRAM:


1. Right-click to select the use case in the browser and make the shortcut menu
visible.
2. Select the New Sequence Diagram menu choice. An unnamed sequence diagram
is added to the browser.
3. With the new sequence diagram selected, enter the name of the sequence diagram.

SEQUENCE DIAGRAM
Participant

Display

login

Control

Database

Enter details

Send data

Send control

Display the nominees

Choose the nominee


Send data

Check the answer with database

Calculate votes

Send data

Display the votes

4.3 COLLABORATION DIAGRAM:


DESCRIPTION:

In software engineering A collaboration diagram, also called a communication


diagram or interaction diagram, is an illustration of the relationships and interactions
among software objects in the Unified Modeling Language (UML)In this collaboration
diagram, the objects are represented as rectangle, the actors are stick figures.collaboration
diagram shows the object and actor interaction without reference to time.

STEPS FOR GENERATING COLLABORATION DIAGRAM:


1. Double-click on the sequence diagram in the browser to open the diagram.
2. Choose the Browse: Create Collaboration Diagram menu choice or press the F5
key.
3. Rearrange the objects and messages on the diagram as needed
COLLABORATION DIAGRAM

3: Display nominee name


9: Display votes

4: Choose the nominee


Participant

Display
7: Calculate votes

Control

8: Send data

5: Send data

1: Enter details

6: Check the answer with database

login

Database

10

4.4 CLASS DIAGRAM:


DESCRIPTION:
In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, and the relationships between the classes.
In our class diagram, the classes identified are
Participant
Controller
Display
Database
login
Each class has its own attributes and operations.
Participant class -The attributes defined are name and email id.The operations involved
are login
Controller class -The attributes it has is result, votes, nominees, name, email id.The
operations carried out by this class are login, voting.
Display class - The attributes are option, nominees. The operations identified are
Display_nom, Display_ vote.
Database class - The attributes are nominees, vote, result. The operation defined is store
_ details.
Login class - The attributes defined is name and email id. The method identified is
login_details.
The Solid line between the classes shows the relationship between them.

STEPS FOR GENERATING CLASS DIAGRAM:


Rose automatically creates the Main class diagram in the Logical View of the model.
To add packages to the Main class diagram:
1. Double-click on the Main diagram in the browser to open it.
2. Click to select the package in the browser.
3. Drag the package onto the diagram.
4. Repeat the preceding steps for each package that is to be added to the diagram.

11

CLASS DIAGRAM
Display
qno
opt
nominees
*
Display_nom()
Display_vote()

Controller
name
Email id
nominees
opt

1
Participant
name
Email

id

votes
results

login()

Database
nominees
vote
1

*
results

login()
nom()
votes()

store_details()
*

login
name
Email id
1

1
login_details()

12

4.5ACTIVITY DIAGRAM:
DESCRIPTION:
It provides a way to model the workflow of a development process. An activity
represents the performance of a task on duty. It represent the execution of statement.

STEPS FOR GENERATING ACTIVITY DIAGRAM:


1. Right-click to select the class in the browser and make the shortcut menu
visible.
2. Select the State Diagram menu choice. This will automatically create and open
the diagram.
3. To open the diagram at another time, click the + to expand the class in the
browser, and double-click on its state transition diagram in the browser

logi
n

Selection of
nominees

Vote for
nominees

databases

13

Display
the result

5 .PROJECT IMPLEMENTATION

CODING:
Form1:
Private Sub Command1_Click()
If Text1.Text = "" Or Text2.Text = "" Then
a = MsgBox("PLEASE FILL ALL THE REQDETAILS", vbExclamation, "WARNING")
Text1.SetFocus
ElseIf Text1.Text = "" Then
Text2.Text = ""
Else
Form3.Show
End If
End Sub
Private Sub Command2_Click()
End
End Sub
Private Sub Command3_Click()
Form2.Show
End Sub

Form2:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
End
End Sub
Private Sub Form_Load()
Set db=OpenDatabase("C:\Documentsand Settings\bhuvaneswari\Desktop\v1\mon.mdb")
Set rs = db.OpenRecordset("cricket voting")
sachin.Text = Val(rs("sachin"))
dhoni.Text = Val(rs("dhoni"))
shewag.Text = Val(rs("shewag"))
dravid.Text = Val(rs("dravid"))
If (Val(rs("sachin")) > Val(rs("dhoni")) And Val(rs("sachin")) > Val(rs("shewag")) And
Val(rs("sachin")) > Val(rs("dravid"))) Then
Text5.Text = Val(rs("sachin"))
Label6.Caption = sachin.Name
ElseIf (Val(rs("sachin")) < Val(rs("dhoni")) And Val(rs("dhoni")) > Val(rs("shewag"))
And Val(rs("dhoni")) > Val(rs("dravid"))) Then
Text5.Text = Val(rs("dhoni"))
Label6.Caption = dhoni.Name

14

ElseIf (Val(rs("dravid")) > Val(rs("dhoni")) And Val(rs("dravid")) > Val(rs("shewag"))


And Val(rs("sachin")) < Val(rs("dravid"))) Then
Text5.Text = Val(rs("dravid"))
Label6.Caption = dravid.Name
Else
Text5.Text = Val(rs("shewag"))
Label6.Caption = shewag.Name
End If
End Sub

Form3:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
Dim f As Integer
If Option1.Value Then
f=1
ElseIf Option2.Value Then
f=2
ElseIf Option3.Value Then
f=3
ElseIf Option4.Value Then
f=4
End If
Select Case (f)
Case 1:
rs.Edit
rs("sachin") = Val(rs("sachin")) + 1
rs.Update
Case 2:
rs.Edit
rs("dhoni") = Val(rs("dhoni")) + 1
rs.Update
Case 3:
rs.Edit
rs("shewag") = Val(rs("shewag")) + 1
rs.Update
Case 4:
rs.Edit
rs("dravid") = Val(rs("dravid")) + 1
rs.Update
End Select
MsgBox ("THANX 4 VOTING!")
Me.Hide
Form1.Show
15

End Sub
Private Sub Command2_Click()
Me.Hide
Form1.Show
End Sub
Private Sub Form_Load()
Setdb=OpenDatabase("C:\Documents and Settings\bhuvaneswari\Desktop\v1\mon.mdb")
Set rs = db.OpenRecordset("cricket voting")
End Sub

STEPS FOR CODE GENERATION:


1. Open your model and display the Class Diagram that contains the
classes and packages for which you want to generate Java source.
2. Select one or more classes or packages in the diagram.
3. Optionally, use the syntax checker before generating your Java
source.
4. On the Tools menu, point to Java, and then click Generate Java.
5. If a package or component hasnt been mapped to an entry in your
classpath settings (for example, this is the first time youve generated
code for a component or package), the Component Mapping dialog
appears enabling you to set up the appropriate associations.
6. Check the Rose Log window to view the results of the Java
generation, including any errors that occurred.
7. Correct any errors and repeat step 4 until no errors are returned.
8. View and edit the generated code.

CODE:
Public class logintovote
{
private int name;
private int e-mail id;
/**
@roseuid 4D84867D0057
*/
private int logintovote()
{
}
/**
@roseuid 4D84867E0056

16

*/
Public void login_details()
{
}
}

6.TEST CASE GENERATION:


CONTROL

Login

Vote

Results

INPUT

OUTPUTDESCRIPTION

Ent If the username and password


and are correct then the voting form
will be displayed
If the username and password
Are not filled the a message box
displays please fill the req
details
Click vote command button
If the appropriate person is
chose to vote then it displays a
msg box thanks for voting
and then goes to form1
er
your
password

Click
button

username

results

17

command The result is displayed with the


leading person

PROGRAM EXECUTION:

Fig: 3.1 LOGIN DETAILS

18

Fig:3.2 NOMINEE DETAILS

19

Fig:3.3 CHOOSING NOMINEE

20

Fig:3.4 RESULT DISPLAY

21

RESULT:
Thus the Online voting project was implemented using Visual Basic, Designed
using Rational Rose Software and Executed Successfully

22

PAYROLL SYSTEM
SOFTWARE REQUIREMENT SPECIFICATION:
1 INTRODUCTION:
It is an office automation software. It contains the details of an employee
such as name, designation, basic pay, HRA, DA, TA, SSS, PAG-Ibig, Daily net pay, total
net pay, no. hours worked, rate per hour, total no. of days, etch. Daily net pay can be
calculated by multiplying no.hrs worked with rate per hour. Total net pay can be
calculated by the following formula,
Total net pay=Daily net pay*(no. of days-no. of days absent)-(basic
pay+HRA+SSS+DA+TA+PAG- Ibig)

Purpose:
The purpose of this document is to present a detailed description of the Payroll
System. It will explain the purpose and features of the system, the interfaces of the
system, what the system will do, the constraints under which it must operate and how the
system will react to external stimuli. This document is intended for both the employee
and the manager of the system.

1.2 Scope:
This software system will be a Payroll Calculating System for an employee in a
large industry. This system will be designed to calculate the salary of all employees in a
firm in an easy manner. will be easily understand by all. This system can be used in large
industries and also in small industries.

1.3 Reference:
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998.

1.4 Definitions and Abbreviations:


Term
Employee
Administrator

Definition
The person who works for a particular firm.
The person who maintains all employees detail.
23

Database
Field
Software Requirements
Specification
User

Collection of all the information monitored by this system.


A cell within a form.
A document that completely describes all of the functions
of a proposed system and the constraints under which it
must operate. For example, this document.
Employee

2. OVERALL DESCRIPTION:
The application is a fully functional payroll calculation software.It consists of
three modules.In the first module the customer logins and enters into the main menu.In
the second module the user will select either input form or output form.In the third
module the user must enter his salary details and will get the result of his salary
calculation.

2.1 Product perspective:


The next chapter of this document gives an overview of the functionality of
the product. It describes the informal requirements and is used to establish a context for
the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the
functionality of the product.
Both sections of the document describe the same software product in its entirety,
but are intended for different audiences and thus use different language.

2.2 Product functions:

Search()

Save()

Print()

Delete()

Add()

2.3 User Characteristics:

The employee must know how to enter the details.

24

The employee must know how to use the payroll system.

The employee must be able to enter his/her details.

The administrator must know how to calculate the salary of an employee.

The administrator must also know how to use the payroll sysytem.

2.4 General Constraints:

The employee will enter the valid username and password.

The employee must enter his name and designation.

The employee must enter the salary details.

3. SPECIFIC REQUIREMENTS:
Specific Requirements is a document that describes all the functions of a proposed
system and the constraints under which it must operate.

3.1 External interface requirement:


External interfaces are nothing but what the developers know about the system
or about the project externally.

3.1.1 User Interfaces:


This is the interface that the user interacts with the system. Here coding acts as a User
interface. The system must contain visual basic, MS Access database, rational rose
software for generating UML diagrams, e.t.c. This can be used in any operating system.

3.1.2 Hardware Interfaces:

System.

A good processor.

128mb RAM(minimum).

25

3.1.3 Software Interfaces:

Visual Basic

Microsoft Access

Rational rose

3.1.4 Communication Protocols:

Database

3.1.5 Memory Constraints:

320 GB hard disc space.

34 MB for software.

1MB for product.

3.1.6 Operation:
The Payroll System has two active actors. They are employee and administrator. The
employee will be able to enter his details only. The administrator will access the entire
system. He will calculate the salary information of an employee and publish the result.
Then the employee can view his salary calculation.

3.1.7 Product function:

Search()

Save()

Print()

Delete()

Add()

26

3.2 Software Product Features:


This software contains the features like

adding a new employee,

deleting an existing employee,

calculating the salary for employee,

Printing the pay slip.

3.3 Software System Attributes:


3.3.1 Reliability:
This system performs and maintains its functions in routine circumstances, as well as
hostile or unexpected circumstances.

3.3.2 Availability:
This system will be in a specified operable and committable state at the start, when
it is called for at an unknown, i.e., a random, time.

3.3.3 Security:
This system provides protection against damage, loss, and criminal activity.

3.3.4 Maintainability:
This system can

correct defects
meet new requirements
make future maintenance easier, or
cope with a changed environment

3.3.5 Portability:
This system has the property of interoperability (i.e the system can run in any
operating system).
27

3.3.6 Performance:
The performance of the system is fast and efficient.

3.4 Database Requirements:


Microsoft Access 7.0

3.5 Other Requirements:


Printer

DESIGNING:
4. UML DIAGRAMS:
4.1 Use Case Diagram
4.2 Sequence Diagram
4.3 Collaboration Diagram
4.4 Class Diagram
4.5 Activity Diagram
4.6 Component Diagram

4.1 USE CASE DIAGRAM:


A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases.
Use cases :A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse
Actors :An actor is a person, organization, or external system that plays a role in one or
more interactions with the system
The actors involved in this Use Case:
EMPLOYEE

28

ADMINISTRATOR(for storing and calculating the details)


The payroll use cases in our system are:
Employee information.
Time card information.
Purchase orders.
Payment method details.
Reports.

STEPS FOR GENERATING USE CASE DIAGRAM:


1. Double-click on the Main diagram in the use case view in the browser to open the
diagram.
2. Click to select an actor in the browser and drag the actor onto the diagram.
3. Repeat step 2 for each additional actor needed in the diagram.
4. Click to select a use case in the browser and drag the use case onto the diagram.
5. Repeat step 4 for each additional use case needed in the diagram.
Note: Actors and use cases may also be created directly on a use case diagram by
using the toolbar.

29

employeeinformation

timecardinformation

employee

purchaseorders

paymentmethoddetails

reports
administrator
managementandupdation

payrollgeneration

4.2 SEQUENCE DIAGRAM:


A sequence diagram represents the sequence and interactions of a given use case
or scenario. Sequence diagrams can capture most of the information about the system. It
is also represented by the order in which things occur and how the objects in the system
send message to one another. The sequence diagram for each use-case that exists when a
user logs in, adds, views, updates or deletes records in the system

STEPS FOR GENERATING SEQUENCEDIAGRAM


1. Right-click to select the use case in the browser and make the shortcut menu
visible.
2. Select the New Sequence Diagram menu choice. An unnamed sequence diagram
is added to the browser.

30

3. With the new sequence diagram selected, enter the name of the sequence diagram.
employee

automatedresponse
(administrator)

projectmanager

administrator

send details
access and update database
submit card information,hours worked,purchase orders and reports

request payment
if hourly employee then pay on hourly rate
payment for who worked more than 8 hours on friday
pay flat salary on the last day of the month
submit time card and purchase orders
pay commission based on sales
access database to notify changes

SEQUENCE DIAGRAM

4.3 COLLABORATION DIAGRAM:


Collaboration diagram and sequence diagrams are alternate representations of an
interaction. A collaboration diagram is an interaction diagram that shows the order of
messages that implement an operation or a transaction.
When we work in either a sequence or collaboration diagram, it is possible to view the
corresponding diagram by pressing F5 key

STEPS FOR GENERATING COLLABORATION DIAGRAM


1. Double-click on the sequence diagram in the browser to open the diagram.
31

2. Choose the Browse:Create Collaboration Diagram menu choice or press the F5


key.
3. Rearrange the objects and messages on the diagram as needed.

1: enter employee id and information


5: submit card information,hours worked,purchase orders and reports
6: request payment
10: submit time card and purchase orders
employee
automatedresponse
(administrator)
7: if hourly employee then pay on hourly rate
8: payment for who worked more than 8 hours on friday
9: pay flat salary on the last day of the month
11: pay commission based on sales

4: access and update database


2: verify employee details
12: access database to notify changes

3: send details

projectmanager

administrator

COLLABORATION DIAGRAM

4.4 CLASS DIAGRAM:


In software engineering, a class diagram in the Unified Modeling
Language (UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, and the relationships between the
classes

STEPS FOR GENERATING CLASS DIAGRAM:


Rose automatically creates the Main class diagram in the Logical View of the model.
To add packages to the Main class diagram:
1. Double-click on the Main diagram in the browser to open it.
2. Click to select the package in the browser.

32

3. Drag the package onto the diagram.


4. Repeat the preceding steps for each package that is to be added to the diagram.

administrator
employee

(from payroll)

(from payroll)

empname : string
age : integer
sex : string
address : string

name : string
age : integer
sex : string
address : string
n

1..n

work()
enterworkingdb()
receivepayment()
1..n

1..n
employeedatabase

maintaininformation()
add()
delete()
update()
assign()
1

1
projectmanagementdb

(from payroll)

empmane : string
empid : integer
projectname : string

(from payroll)

projectname : string
projectid : string
timelimit : integer

startingdate()
reoprt()
finishingdate()

changeproject()
changenumber()

CLASS DIAGRAM

4.5 ACTIVITY DIAGRAM:


Activity diagram provides a way to model the workflow of a development Process.
An activity represents the performance of a task on duty. It may also represent the
execution of a statement in a procedure.

STEPS FOR GENERATING ACTIVITY DIAGRAM:


1. Right-click to select the class in the browser and make the shortcut menu
visible.
2. Select the State Diagram menu choice. This will automatically create and open
the diagram.
3. To open the diagram at another time, click the + to expand the class in the
browser, and double-click on its state transition diagram in the browser

33

e m p lo ye e

a d m i n i s tr a to r

p r o j e c tm a n a g e m e n t d b e m p l o y e e d b

s t a rt

lo g in

s u b m it id , t im e c a rd a n d
p a y m e n t d e t a ils

m a i n t a in e m p lo y e e i n fo
a n d a s s ig n p r o je c t

c h e c k fo r
s c h e d u le

p a y ro ll
g e n e ra t i o n

s to p

ACTIVITY DIAGRAM

34

4.6 COMPONENT DIAGRAM:


STEPS FOR GENERATING COMPONENT DIAGRAM:
1. Double-click on the Main Diagram under the Component View package on
the browser to open the diagram.
2. Click to select a package and drag the package onto the diagram.
3. Repeat step 2 for each additional package.
4. Dependency relationships are added by selecting the dependency icon from
the toolbar, clicking on the package representing the client, and dragging the
arrow to the package representing the supplier.
employee

automated
response

administrat
or

COMPONENT DIAGRAM

5. IMPLEMENTATION:
CODE GENERATION STEPS:
There are code generation properties associated with the project, the class, the roles, the
attributes, and operations. Project properties concern file name, default container, and
placement of the generated code. Class properties concern constructors etc. Operation
properties deal with the operation kind (abstract, static etc.) and allow the operation to be
made constant. The property set for roles deals with the generation of get/set methods,
visibility of methods, and the container class to be used.
1. Select the Tools:Option menu choice
35

2. Select the cg tab


3. Click on the arrow to make the drop-down menu visible
4. Select the desired type of property set.
5. Click the Clone button to make the Clone Property Set window
visible.
6. Enter the name of the new property set.
7. Click the OK button to close the Clone Property Set window.
8. Click to select the property to change.
9. Click the Edit Value button to place the property in edit mode.
10. Enter the new value or select the new value from the drop-down
menu if one is provided.
11. Repeat steps 8 through 10 for each property to be changed.
12. Click the Apply button to apply changes.
13. Repeat the preceding steps for each new property set.
14. Click the OK button to close the Options window.

JAVA CODE:
package payroll;
public class administrator
{
private string name;
private integer age;
private string sex;
private string address;
public projectmanagementdb theProjectmanagementdb;
/**
@roseuid 4D84867D0057
*/
public administrator()
{
}
/**
@roseuid 4D410CC6039A
*/
public void maintaininformation()
{
}
/**

36

@roseuid 4D410CD901B5
*/
public void add()
{
}
/**
@roseuid 4D410CE1005D
*/
public void delete()
{
}
/**
@roseuid 4D410CE902AF
*/
public void update()
{
}
/**
@roseuid 4D410CF7027F
*/
public void assign()
{
}
}

Coding:
FORM1: LOGIN FORM
Option Explicit
Public LoginSucceeded As Boolean
Private Sub Command2_Click()
LoginSucceeded = False
End
End Sub
Private Sub Command1_Click()
If Text1.Text = "cse" Or Text2.Text = "cse" Then
LoginSucceeded = True
Call Form2.Show
Me.Hide

37

Else
MsgBox "USERNAME PASSWORD ARE NOT MATCHING", vbExclamation,
"LOGIN"
Text1.Text = ""
Text2.Text = ""
Text1.SetFocus
SendKeys "{Home}+{End}"
End If
End Sub

FORM2: MAIN MENU


Private Sub Command3_Click()
Form3.Show
Form3.Text1.SetFocus
Me.Hide
End Sub
Private Sub Command4_Click()
End
End Sub
Private Sub Command5_Click()
Form3.Show
Form3.Text1.SetFocus
Me.Hide
End Sub
Private Sub Form_Load()
Frame4.Visible = True
End Sub
Private Sub Label3_Click()
Frame4.Visible = True
End Sub

FORM3: PAYROLL I/P AND O/P


Dim B, c As Integer
Dim a As VbMsgBoxResult
Private Sub Command1_Click()
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""

38

Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
End Sub
Private Sub Command2_Click()
On Error Resume Next
If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or
Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Then
a = MsgBox("RECORDS NOT SAVE.. PLS COMPLETE..", vbCritical, "WARNING")
Text1.Text = ""
Text1.SetFocus
ElseIf Text1.Text <> "" Or Text2.Text <> "" Or Text3.Text <> "" Or Text4.Text <> ""
Or Text5.Text <> "" Or Text6.Text <> "" Or Text7.Text <> "" Then
Data1.Recordset.AddNew
Data1.Recordset(0) = Text1.Text
Data1.Recordset(1) = Text2.Text
Data1.Recordset(2) = Text6.Text
Data1.Recordset(3) = Text7.Text
Data1.Recordset(4) = Text8.Text
Data1.Recordset(5) = Text9.Text
Data1.Recordset(6) = Text10.Text
Data1.Recordset(7) = Text11.Text
Data1.Recordset(8) = Text12.Text
Data1.Recordset(9) = Text13.Text
Data1.Recordset(10) = Text3.Text
Data1.Recordset(11) = Text4.Text
Data1.Recordset(12) = Text5.Text
Data1.Recordset.Update
'Command6.Enabled = False
'Command2.Enabled = False
'Command3.Enabled = False
'Command5.Enabled = False
End If
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""

39

Text12.Text = ""
Text13.Text = ""
End Sub
Private Sub Command3_Click()
On Error Resume Next
a = MsgBox("ARE YOU SURE?", vbYesNo, "DELETE")
If a = vbYes Then
Data1.Recordset.Delete
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
End If
'Command2.Enabled = False
Command3.Enabled = False
'Command5.Enabled = False
Text1.SetFocus
End Sub
Private Sub Command4_Click()
Form2.Show
End Sub
Private Sub Command5_Click()
On Error Resume Next
If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or
Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Then
a = MsgBox("RECORDS NOT PRINT.. TRY AGAIN..", vbCritical, "WARNING")
Text1.Text = ""
Text1.SetFocus
ElseIf Text1.Text <> "" Or Text2.Text <> "" Or Text3.Text <> "" Or Text4.Text <> ""
Or Text5.Text <> "" Or Text6.Text <> "" Or Text7.Text <> "" Then
Form5.Show
Form5.Text1.Text = Text1.Text
Form5.Text2.Text = Text2.Text
Form5.Text3.Text = Text6.Text

40

Form5.Text4.Text = Text7.Text
Form5.Text5.Text = Text8.Text
Form5.Text6.Text = Text9.Text
Form5.Text7.Text = Text10.Text
Form5.Text8.Text = Text11.Text
Form5.Text9.Text = Text12.Text
Form5.Text10.Text = Text13.Text
Form5.PrintForm
'Printer.EndDoc
End If
End Sub
Private Sub Command6_Click()
On Error Resume Next
If Data1.Recordset(0) = "" Or Text1.Text = "" Then
a = MsgBox("RECORDS NOT FOUND .. TRY AGAIN..", vbCritical, "WARNING")
Text1.Text = ""
Text1.SetFocus
Else
Data1.RecordSource = "select * from payrol where name =" & Text1.Text & " and desig
=" & Text2.Text
Text1.Text = Data1.Recordset(0)
Text2.Text = Data1.Recordset(1)
Text6.Text = Data1.Recordset(2)
Text7.Text = Data1.Recordset(3)
Text8.Text = Data1.Recordset(4)
Text9.Text = Data1.Recordset(5)
Text10.Text = Data1.Recordset(6)
Text11.Text = Data1.Recordset(7)
Text12.Text = Data1.Recordset(8)
Text13.Text = Data1.Recordset(9)
Text3.Text = Data1.Recordset(10)
Text4.Text = Data1.Recordset(11)
Text5.Text = Data1.Recordset(12)
'Command5.Enabled = True
'Command3.Enabled = False
Command2.Enabled = False
End If
End Sub
Private Sub Form_Load()
c=0
Command3.Enabled = False
Data1.Enabled = False
End Sub
Private Sub Text1_Change()

41

On Error Resume Next


Data1.RecordSource = "select * from payrol where name = '" & Text1.Text & "'"
Data1.Refresh
End Sub
Private Sub Text10_Change()
Text13.Text = Val(Text13.Text) - Val(Text10.Text)
End Sub
Private Sub Text11_Change()
Text13.Text = Val(Text13.Text) - Val(Text11.Text)
End Sub
Private Sub Text12_Change()
Text13.Text = Val(Text13.Text) - Val(Text12.Text)
End Sub
Private Sub Text13_Change()
Text13.Text = Val(Text6.Text) * (Val(Text7.Text) - Val(Text8.Text)) - (Val(Text9.Text)
+ Val(Text10.Text) + Val(Text11.Text) + Val(Text12.Text))
End Sub
Private Sub Text3_Change()
Text5.Text = Val(Text3.Text) * Val(Text4.Text)
Text6.Text = Val(Text3.Text) * Val(Text4.Text)
End Sub
Private Sub Text4_Change()
Text5.Text = Val(Text3.Text) * Val(Text4.Text)
Text6.Text = Val(Text3.Text) * Val(Text4.Text)
End Sub
Private Sub Text5_Change()
Text5.Text = Val(Text4.Text) * Val(Text3.Text)
Text6.Text = Text5.Text
End Sub
Private Sub Text6_Change()
Text5.Text = Val(Text4.Text) * Val(Text3.Text)
Text13.Text = Val(Text6.Text) * (Val(Text7.Text) - Val(Text8.Text))
End Sub
Private Sub Text7_Change()
Text13.Text = Val(Text6.Text) * (Val(Text7.Text) - Val(Text8.Text))
End Sub
Private Sub Text8_Change()
Text13.Text = Val(Text6.Text) * (Val(Text7.Text) - Val(Text8.Text))
End Sub
Private Sub Text9_Change()
Text13.Text = Val(Text13.Text) - Val(Text9.Text)
End Sub

42

6. TESTING:
Control

Input

Output Description
If the Username and Password are

Login

Enter Username

correct then the Main Menu will be

and Password

displayed. Otherwise it will display


login is incorrect.
If the payroll report is incomplete then

Save

Click Save

displays the record is incomplete

command button.

please complete the record. Otherwise


the record will be saved.

Search

Delete

Print

If the given name is not exist then it

Click Search
command button.

displays the record is not found.


Otherwise details will be shown.
If the given name is not exist then it

Click Delete
command button.

displays the record is not found.


Otherwise the record will be deleted.
If the payroll report is incomplete then

Click Print
command button

43

it displays Record will not print.


Otherwise the record will be printed.

OUTPUT SCREEN:

LOGIN FORM

44

MAIN MENU

45

PAYROLL INPUT AND OUTPUT FORM

46

PRINT FORM

47

RESULT:
Thus the Payroll system project was implemented using Visual Basic,
Designed using Rational Rose Software and Executed Successfully

48

49

BANKING SYSTEM
SOFTWARE REQUIREMENT SPECIFICATION:
INTRODUCTION:
1.1 Purpose:
The purpose of this document is to present a detailed description of the Banking
System. It will explain the purpose and features of the system, the interfaces of the
system, what the system will do, the constraints under which it must operate and how the
system will react to external stimuli. This document is intended for manager of the
system.

1.2 Scope:
This software will be a Online Banking System for the users in world wide. This
system will be designed to maintain the account of all users in an easy manner.This will
be easily understand by all.This system can be used in money banks.

1.3 Reference:
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software
Requirements Specifications. IEEE Computer Society, 1998

1.4 Definitions and Abbreviation


Term
user
Administrator
Database
Field
Software Requirements
Specification

Definition
The person who has account in the bank
The person who maintains all userss detail.
Collection of all the information monitored by this system.
A cell within a form.
A document that completely describes all of the functions
of a proposed system and the constraints under which it
must operate. For example, this document.

2.OVERALL DESCRIPTION:
2.1 Product Perspective:

50

The next chapter, the Overall Description section, of this document gives an
overview of the functionality of the product. It describes the informal requirements and is
used to establish a context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the
functionality of the product.
Both sections of the document describe the same software product in its entirety,
but are intended for different audiences and thus use different language

2.2 Product Functions:

Account creation()
Withdraw()
Deposit()
Report()
Account deletion()

2.3 User Characteristics:

The user must know how to enter the details.

The user must know how to use the banking system.

The administrator must know how to view the account details of a user.

The administrator must also know how to use the banking system.

2.4 General Constraints:


The user has been authenticated properly.
The user must have an account for transactions.
The user must have sufficient account balance for withdrawal
UpdateBalanceNeeded flag has been set for the appropriate account
If the user is validated, the banking system is logged in and ready for the user to
access their account
If the user was not validated, then the banking system is at the welcome screen
waiting for a new customer
51

3. SPECIFIC REQUIREMENTS
3.1 External Interface Requirements:
3.1.1 User Interfaces:
Server: This server will have a very simple set of commands. It will run in a console.
Upon initial server initialization the server will prompt the user for the port number and
the name of the bank.

3.1.2 Hardware Interfaces:

System.
Good processor.
128mb RAM(minimum).

3.1.3 Software Interfaces:

Visual Basic
Microsoft Access
Rational rose

3.1.4 Communications Interfaces:


The client and server will be communicating through the internet via a
Transmission Control Protocol of the TCP/IP Suite. This protocol is particularly
suited for this application because it is a connection oriented protocol that
allows for an ordered and reliable delivery of packets. The use of a non
connection oriented protocol would not be well suited for this application due tothe
complications of dropped packets and unordered delivery of packets

3.1.5 Memory Constraints:


It occupies 3 mb space in hard disk and 4 mb RAM

3.1.6 Operation:
The Banking System has two active actors. They are user and administrator. The user will
be able to enter the transaction details and view their amount balance only. The
administrator will access the entire system. He will view all the activities of the bank and
the users.

52

3.1.7 Product function:


This product is based on the transactions like deposit and withdraw the money
from their own separate bank accounts.

3.2 Software Product Features


Server Requirements
The server shall Load data at startup
The server shall save data at shutdown
The server shall save account and user data anytime it is modified (i.e. after a
deposit, withdraw, creation of account, etc.)
The server shall handle requests in a separate thread
The server shall lock accounts/user to prevent errors due to simultaneous
access

3.3 Software System Attributes:


3.3.1 Reliability:
The system shall save the data of an active user whenever that user has just
completed a deposit transaction. The system shall save the data of an active user
whenever that user has just completed a withdraw transaction. The system shall save the
data of an active user whenever a new account is created.

3.3.2 Availability:
The Bank Server shall be available and running in a stable state at all times.
The Bank Officer Software shall be available at all times.

3.3.3 Security:
The system shall require a password to allow a user to logon. The system shall
require the user to know their own password and account
number.

3.3.4 Maintainability:
The source code shall be available to the developers.

3.4 Database Requirements:


Ms access 2007

53

4.DESIGNING:
UML DIAGRAMS:
1.
2.
3.
4.
5.
6.

Use case diagram


Sequence diagram
Collaboration diagram
Class diagram
State diagram
Component diagram

4.1 USE CASE DIAGRAM:


A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases.
Use cases :A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse
Actors :An actor is a person, organization, or external system that plays a role in one or
more interactions with the system

The actors involved in this Use Case:


USER
MANAGER
STAFF

The banking use cases in our system are:

User information.
Account information.

Transaction order

54

Branch details.

Reports.
Management and updating.

STEPS FOR GENERATING USE CASE DIAGRAM:


1. Double-click on the Main diagram in the use case view in the browser to open the
diagram.
2. Click to select an actor in the browser and drag the actor onto the diagram.
3. Repeat step 2 for each additional actor needed in the diagram.
4. Click to select a use case in the browser and drag the use case onto the diagram.
5. Repeat step 4 for each additional use case needed in the diagram.
Note: Actors and use cases may also be created directly on a use case diagram by
using the toolbar.

55

USE CASE DIAGRAM


56

4.2 SEQUENCE DIAGRAM:


A sequence diagram represents the sequence and interactions of a given use case
or scenario. Sequence diagrams can capture most of the information about the system. It
is also represented by the order in which things occur and how the objects in the system
send message to one another. The sequence diagram for each use-case that exists when a
user logs in, adds, views, updates or deletes records in the system

STEPS FOR GENERATING SEQUENCEDIAGRAM


1. Right-click to select the use case in the browser and make the shortcut menu
visible.
2. Select the New Sequence Diagram menu choice. An unnamed sequence diagram
is added to the browser.
3. With the new sequence diagram selected, enter the name of the sequence diagram.

SEQUENCE DIAGRAM

57

4.3 COLLABORATION DIAGRAM:


Collaboration diagram and sequence diagrams are alternate representations of an
interaction. A collaboration diagram is an interaction diagram that shows the order of
messages that implement an operation or a transaction.
When we work in either a sequence or collaboration diagram, it is possible to view the
corresponding diagram by pressing F5 key

STEPS FOR GENERATING COLLABORATION DIAGRAM


1. Double-click on the sequence diagram in the browser to open the diagram.
2. Choose the Browse: Create Collaboration Diagram menu choice or press the F5
key.
3. Rearrange the objects and messages on the diagram as needed.

COLLABORATION DIAGRAM

4.4 CLASS DIAGRAM:


In software engineering, a class diagram in the Unified Modeling
Language (UML) is a type of static structure diagram that describes the structure of a
system by showing the system's classes, their attributes, and the relationships between the
classes

58

STEPS FOR GENERATING CLASS DIAGRAM:


Rose automatically creates the Main class diagram in the Logical View of the model.
To add packages to the Main class diagram:
1. Double-click on the Main diagram in the browser to open it.
2. Click to select the package in the browser.
3. Drag the package onto the diagram.
4. Repeat the preceding steps for each package that is to be added to the diagram.

59

CLASS DIAGRAM

4.5 STATE DIAGRAM:


State diagram provides a way to model the workflow of a development Process. A
state represents the performance of a task on duty. It may also represent the execution of
a statement in a procedure.

STEPS FOR GENERATING STATE DIAGRAM:


Creating State Transition Diagrams
1. Right-click to select the class in the browser and make the shortcut menu
Visible.
2. Select the State Diagram menu choice. This will automatically create and open
the diagram.
3. To open the diagram at another time, click the + to expand the class in the

60

browser, and double-click on its state transition diagram in the browser.

61

4.6 COMPONENT DIAGRAM:


STEPS FOR GENERATING COMPONENT DIAGRAM:
1. Double-click on the Main Diagram under the Component View package on
the browser to open the diagram.
2. Click to select a package and drag the package onto the diagram.
3. Repeat step 2 for each additional package.
4. Dependency relationships are added by selecting the dependency icon from
the toolbar, clicking on the package representing the client, and dragging the
arrow to the package representing the supplier.

62

COMPONENT DIAGRAM

5. IMPLEMENTATION:
CODE GENERATION STEPS:
There are code generation properties associated with the project, the class, the roles, the
attributes, and operations. Project properties concern file name, default container, and
placement of the generated code. Class properties concern constructors etc. Operation
properties deal with the operation kind (abstract, static etc.) and allow the operation to be
made constant. The property set for roles deals with the generation of get/set methods,
visibility of methods, and the container class to be used.
1. Select the Tools:Option menu choice
2. Select the cg tab
3. Click on the arrow to make the drop-down menu visible
4. Select the desired type of property set.
5. Click the Clone button to make the Clone Property Set window
visible.
6. Enter the name of the new property set.
7. Click the OK button to close the Clone Property Set window.
8. Click to select the property to change.
9. Click the Edit Value button to place the property in edit mode.
10. Enter the new value or select the new value from the drop-down
menu if one is provided.
11. Repeat steps 8 through 10 for each property to be changed.
12. Click the Apply button to apply changes.
13. Repeat the preceding steps for each new property set.
14. Click the OK button to close the Options window.

JAVA CODE:
package banking;
public class administrator
{
private string name;
private integer accno;
private string init_bal;
public projectmanagementdb theProjectmanagementdb;
/**
63

@roseuid 4D84867D0057
*/
public administrator()
{
}
/**
@roseuid 4D410CC6039A
*/
public void maintaininformation()
{
}
/**
@roseuid 4D410CD901B5
*/
public void add()
{
}
/**
@roseuid 4D410CE1005D
*/
public void delete()
{
}
/**
@roseuid 4D410CE902AF
*/
public void update()
{
}
/**
@roseuid 4D410CF7027F
*/
public void assign()
{
}

64

PROJECT IMPLEMENTATION:
Coding:
CODING:
Form Login1:
Option Explicit
Public LoginSucceeded As 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 = "y" And txtUserName = "y" Then
'place code to here to pass the
'success to the calling sub
'setting a global var is the easiest
LoginSucceeded = True
Me.Hide
frmmaaainmenu.Visible = True
frmLogin1.Visible = False
Else
MsgBox "Invalid Password, try again!", , "Login"
txtPassword.SetFocus
'SendKeys "{Home}+{End}"
End If
End Sub
Form adminview:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
frmwithdraw.Visible = True
frmadminview.Visible = False
End Sub
Private Sub Command2_Click()
frmdeposit.Visible = True
frmadminview.Visible = False
End Sub
Private Sub Command3_Click()
frmmaaainmenu.Visible = True
65

frmadminview.Visible = False
End Sub
Private Sub Command4_Click()
If Text2.Text <> "" Then
rs.FindFirst "[accountnumber] = '" & Text2.Text & "' "
If rs.NoMatch Then
MsgBox "no customer by that name was found ", vbExclamation
Else
Text3.Text = rs.Fields(0)
Text4.Text = rs.Fields(2)
Command1.Enabled = True
Command2.Enabled = True
End If
Else
MsgBox "PLEASE ENTER THE DETAILS"
End If
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("D:\PGMS\vb pgm\BANKY\main.mdb")
Set rs = db.OpenRecordset("newaccount", dbOpenDynaset)
Text3.Enabled = False
Text4.Enabled = False
Command1.Enabled = False
Command2.Enabled = False
End Sub
Form create:
Dim db As Database
Dim rs As Recordset
Private Sub Command1_Click()
rs.AddNew
txtname.Enabled = True
txtaccno.Enabled = True
txtiniamt.Enabled = True
CREATE.Enabled = True
Command1.Enabled = False
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("D:\PGMS\vb pgm\BANKY\main.mdb")
Set rs = db.OpenRecordset("newaccount", dbOpenDynaset)
txtname.Text = ""
txtaccno.Text = ""
txtiniamt.Text = ""
CREATE.Enabled = False
txtname.Enabled = False

66

txtaccno.Enabled = False
txtiniamt.Enabled = False
End Sub
Private Sub CANCEL_Click()
frmmaaainmenu.Visible = True
frmcreate.Visible = False
Command1.Enabled = True
CREATE.Enabled = False
End Sub
Private Sub CREATE_Click()
If txtname.Text <> "" Or txtaccno.Text <> "" Or txtiniamt.Text <> "" Then
rs.FindFirst "[ACCOUNTNUMBER]<>'" & txtaccno.Text & "'"
If rs.NoMatch Then
rs.Update
txtname.Text = ""
txtaccno.Text = ""
txtiniamt.Text = ""
Else
c = MsgBox("ACCOUNT CREATED", vbOKOnly)
End If
Else
a = MsgBox("Please fill in all details")
End If
CREATE.Enabled = False
Command1.Enabled = True
frmmaaainmenu.Visible = True
frmcreate.Visible = False
txtname.Enabled = False
txtaccno.Enabled = False
txtiniamt.Enabled = False
End Sub
Private Sub RESET_Click()
txtname.Text = ""
txtaccno.Text = ""
txtiniamt.Text = ""
End Sub
Form delete:
Dim db As Database
Dim rs As Recordset

67

Private Sub Command1_Click()


If Text1.Text <> "" Then
rs.FindFirst "[accountnumber] = '" & Text1.Text & "' "
If rs.NoMatch Then
MsgBox "no customer by that name was found ", vbExclamation
Else
rs.Delete
End If
MsgBox "account deleted", vbExclamation
End If
End
End Sub
Private Sub Command2_Click()
End
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("D:\PGMS\vb pgm\BANKY\main.mdb")
Set rs = db.OpenRecordset("newaccount", dbOpenDynaset)
End Sub
Form deposit:
Dim db As Database
Dim rs As Recordset
Dim ys As Recordset
Private Sub Command1_Click()
End
End Sub
Private Sub Command2_Click()
If frmadminview.Text2.Text <> "" Then
rs.FindFirst "[accountnumber] = '" & frmadminview.Text2.Text & "' "
If rs.NoMatch Then
MsgBox "no customer by that name was found ", vbExclamation
Else
rs.Edit
ys.Edit
ys.AddNew
ys("withdrawed") = 0
ys("deposited") = 0
ys("deposited") = Text2.Text
ys("initialamt") = Val(rs("initialamount"))
rs("initialamount") = Val(rs("initialamount")) + Val(Text2.Text)
Text2.Text = rs("initialamount")
ys("date") = frmmaaainmenu.Label1

68

ys("name") = frmadminview.Text3
ys("transaction") = "Deposited"
ys("accno") = frmadminview.Text2
ys("balance") = Text2.Text
ys.Update
rs.Update
c = MsgBox("AMOUNT DEPOSITED", vbOKOnly)
If c = vbOK Then
frmmaaainmenu.Visible = True
frmdeposit.Visible = False
Else
frmwithdraw.Visible = False
frmadminview.Visible = True
End If
End If
End If
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("D:\PGMS\vb pgm\BANKY\main.mdb")
Set rs = db.OpenRecordset("newaccount", dbOpenDynaset)
Set ys = db.OpenRecordset("report", dbOpenDynaset)
End Sub
Form withdraw:
Dim db As Database
Dim rs As Recordset
Dim ys As Recordset
Private Sub Command1_Click()
frmmaaainmenu.Visible = True
frmwithdraw.Visible = False
End Sub
Private Sub Command2_Click()
If frmadminview.Text2.Text <> "" Then
rs.FindFirst "[accountnumber] = '" & frmadminview.Text2.Text & "' "
If rs.NoMatch Then
MsgBox "no customer by that name was found ", vbExclamation
Else
rs.Edit
ys.Edit
ys.AddNew
ys("withdrawed") = 0
ys("deposited") = 0
ys("withdrawed") = Text2.Text

69

ys("initialamt") = Val(rs("initialamount"))
rs("initialamount") = Val(rs("initialamount")) - Val(Text2.Text)
Text2.Text = rs("initialamount")
ys("date") = frmmaaainmenu.Label1
ys("name") = frmadminview.Text3
ys("transaction") = "Withdrawed"
ys("accno") = frmadminview.Text2
ys("balance") = Text2.Text
ys.Update
rs.Update
c = MsgBox("AMOUNT WITHDRAWED", vbOKOnly)
If c = vbOK Then
frmmaaainmenu.Visible = True
frmwithdraw.Visible = False
Else
frmwithdraw.Visible = False
frmadminview.Visible = True
End If
End If
End If
End Sub
Private Sub Form_Load()
Set db = OpenDatabase("D:\PGMS\vb pgm\BANKY\main.mdb")
Set rs = db.OpenRecordset("newaccount", dbOpenDynaset)
Set ys = db.OpenRecordset("report", dbOpenDynaset)
End Sub
Form report:
Dim db As Database
Dim rs As Recordset
Private Sub Form_Load()
Set db = OpenDatabase("f:\yo bank\main.mdb")
Set rs = db.OpenRecordset("report", dbOpenDynaset)
End Sub
Private Sub Command2_Click()
rs.AddNew
End Sub
Private Sub Command1_Click()
Command1.Caption = "GENERATED"
Call Command2_Click
End Sub
Form main menu:

70

Private Sub Command1_Click()


frmadmindeposit.Visible = True
frmmaaainmenu.Visible = False
End Sub
Private Sub Command2_Click()
frmmaaainmenu.Visible = False
frmadminwithdraw.Visible = True
End Sub
Private Sub Command3_Click()
frmadminview.Visible = True
frmmaaainmenu.Visible = False
End Sub
Private Sub Command4_Click()
End
End Sub
Private Sub Command5_Click()
frmcreate.Visible = True
frmmaaainmenu.Visible = False
frmcreate.txtname.Text = ""
frmcreate.txtaccno.Text = ""
frmcreate.txtiniamt.Text = ""
End Sub
Private Sub Command6_Click()
frmdelete.Visible = True
frmmaaainmenu.Visible = False
End Sub
Private Sub Command7_Click()
frmreport.Visible = True
frmmaaainmenu.Visible = False
End Sub
Private Sub Form_Load()
Label1.Caption = Format$(Now, "hh:mm:ss AM/PM mm-dd-yy")
End Sub

71

6.TEST CASE GENERATION:


Control

Input

Output Description
If the Username and Password are

Login

create

Delete

Enter Username

correct then the Main Menu will be

and Password

displayed. Otherwise it will display

Click create

login is incorrect.
A new account is created if the account
number does not conflict with the
existing account else, the account
already exists is displayed.

command button

If the given name is not exist then it

Click Delete
command button.

displays the record is not found.


Otherwise the record will be deleted.

View

Enter the account The details of the account number are


number and click displayed.
the view button.

Deposit

Enter the amount to The particular amount gets deposited


be withdrawal and in that account.
click the withdraw
button.

Withdraw

Enter the amount to The particular amount gets withdrawal


be withdrawal and from that account.
click the withdraw
button.

Report

The empty box is The database is opened which has the


clicked.
ledger report.

72

PROJECT EXECUTION:

Form Login:

Form Main:

73

Form Create:

74

Form Delete:

Form Deposit:

75

Form Withdraw:

Form View:

76

Form Report:

77

RESULT:
Thus the Banking System was Designed, Implemented and Executed Successfully using
Rational Rose software and visual basic.

78

ONLINE SHOPPING
SOFTWARE REQUIREMENT SPECIFICATION:
1. INTRODUCTION:
To perform a project for online shopping using html for purchasing things in
online. Gives the details of things which we purchase in online.

1.1 Purpose:
The purpose of this document is to present a detailed description of the online
shopping .It will explain the features of the system, the interfaces provided by the system
and what the system will do.

1.2 Scope:
The scope of this project is to perform online shopping. This is designed to display the
products selected by the customers to purchase and display the purchase details
accurately and easily. To store the databases of the products and the result, using HTML.

1.3 Reference:
IEEE STD 830-1998 IEEE recommended practice for software requirements
specifications IEEE computer society, 1998.

1.4 Definitions and Abbreviations:

Customer: The Members who are purchasing the products.


Database: Software used to store the Account Details, Product Details.

2. OVERALL DESCRIPTION:
The overall description of the document gives an overview of the functionality of
the product. it describes the informal requirements and is used to establish a context for
the requirement specification.

2.1 Product Perspective:


The application is fully functional shopping software. It consists of three modules.
In the first module the customer logins and enters into the product list. In the second
module a list of products for purchasing is displayed and purchases the favorite product.
In the third module display the results for all the purchase details and displays the
products.

79

2.2 Product Functions:

Login and enter to purchase the products.


Place Orders
Pay Details

2.3 User Characteristics:

Customer: Customer should know about their account name and


password also with knowledge on online shopping
Database: Database should contain each product details such as
specification, price, shipping details.

2.4 General Constraints:

Customer: Users should enter their valid account name and password.
Database: Database should posses all the valid details about User
Accounts details, Product details, Place Orders details.

3. SPECIFICATION REQUIREMENT:
Software Requirement specification is a document that describes all the functions
of a proposed system and the constraints under which it must operate.

3.1 External Internal Requirement:


External interfaces are nothing but what the developers know about the system or
about the project externally.

3.1.1 User Interfaces:


This is the interface that the user interacts with the system. Here coding acts as a
User interface.

3.1.2 Hardware Interfaces:


It describes the physical and logical characteristics between the software products.
The hardware used in this project are
o System
o Printer etc

3.1.3 Software Interfaces:


It describes the connection between the software and other components
o HTML,

80

o INTERNET.

3.1.4 Communications Protocols


This project has the communication protocols with the internet only. All the
transactions are carried out through online.

3.1.5 Memory Constraints


This Project requires
500GB of Hard disk space.
2GB of RAM.
The Project posses
1.5MB of the file size.

3.1.6 Operation
We should perform online shopping in various operating Systems.We perform it
by using HTML and .net etc but its back end must be only MS - access for storing the
databases of the products and the purchase details.

3.1.7 Product Function


The Product is based on Online System which the Product Purchasing is carried
out. The Product verifies and authenticates the users. The Purchasing and Placing Orders
are carried out with users preference and choices.

3.2 Software Product Features


In the past, Shopping was done through various trade methods which has much
manual work and Complexity. In this project, the purchasing process is reduced and the
customers can buy the product easily.

3.3 SOFTWARE SYSTEM ATTRIBUTES


3.3.1 Reliability
The Reliability is much higher in this project. Since, all processes are carried out
through online and each process is verified instantly.

3.3.2 Availability
This Online Shopping System is available at all times since the project
implemented through internet connection.

81

3.3.3 Security
The Project provides much security to the Product sellers which transactions are
carried out through online and fake users cannot be able to place orders.

3.3.4 Maintainability
The Project can be well maintained with the help of the developers. Each updating
process can be added to the website and displayed simultaneously.

3.3.5 Portability
The Online Shopping is implemented through online and so can be executable in
all platforms such as internet possessing systems.

3.3.6 Performance
The Project well equipped with the recent networking technologies and will result
in high performance.

3.4 Database Requirements


The project requires the online database systems with the implementation of
HTML and java scripts.

3.5 Other Requirements


The project doesnt require any other requirements for the implementation of
Online Shopping.

4. DESIGNING:
Designing phase involves many UML diagrams

4 UML DIAGRAMS:
Use case diagram
4.1 Sequence diagram
4.2 Collaboration diagram
4.3 Class diagram
4.4 State diagram
4.5 Component diagram

82

4.1USE CASE DIAGRAM:

DESCRIPTION
A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. Its purpose is to
present a graphical overview of the functionality provided by a system in terms of actors,
their goals (represented as use cases), and any dependencies between those use cases.
Usecases: A use case describes a sequence of actions that provide something of
measurable value to an actor and is drawn as a horizontal ellipse
Actors: An actor is a person, organization, or external system that plays a role in one or
more interactions with the system

STEPS FOR GENERATING USECASE DIAGRAM:


6. Double-click on the Main diagram in the use case view in the browser to open the
diagram.
7. Click to select an actor in the browser and drag the actor onto the diagram..
8. Repeat step 2 for each additional actor needed in the diagram.
9. Click to select a use case in the browser and drag the use case onto the diagram.
10. Repeat step 4 for each additional use case needed in the diagram.

83

84

4.1.2 SEQUENCE DIAGRAM

4.1.2.1 DESCRIPTION:
A sequence diagram in Unified Modeling Language (UML) is a kind of interaction
diagram that shows how processes operate with one another and in what order. It is a
construct of a Message Sequence Chart.

acto r
S :sh o p cart

P lace o rd er
< < create> >

S u b m it o rd er

85

O :o rd er

STEPS FOR GENERATING SEQUENCE DIAGRAM:


1. Right-click to select the use case in the browser and make the shortcut menu
Visible.
2. Select the New Sequence Diagram menu choice. An unnamed sequence diagram
is added to the browser.
3. With the new sequence diagram selected, enter the name of the sequence diagram.

86

T :tr a cSk :inS ge a r c

A c to r

c u sto m e r

tr a c k s o r ds e ar r c h e s
co n n ec
87

4. 3 COLLABORATION DIAGRAM:
DESCRIPTION:
In software engineering A collaboration diagram, also called a communication
diagram or interaction diagram, is an illustration of the relationships and interactions
among software objects in the Unified Modeling Language (UML)In this collaboration
diagram, the objects are represented as rectangle, the actors are stick figures.
Collaboration diagram shows the object and actor interaction without reference to time.
In our Online Sopping System, each object interacts with each other or collaborates with
each other; it gets represented by the solid line drawn between them.

STEPS FOR GENERATING COLLABORATION DIAGRAM:


1. Double-click on the sequence diagram in the browser to open the diagram.
2. Choose the Browse: Create Collaboration Diagram menu choice or press the F5
key.
3. Rearrange the objects and messages on the diagram as needed

4 :

i e w

r o d

c t
p d b : P

r o d u c t D

5 : C o n n e c t c u s t o m
p r o d u c t d a t a b a s e
c : C

s t o

1 :

r p : R

i g n

e g i s t r a t i o n

i n

6 :

7 :

I t e m

i t e 1 m 1 : ( sS ) e n d
s ec lu e s c t to e m d

c o n

a t a b a s e

e r

t o

s d : S

h ip p i n g D

f i r m

a t i o n

e r

1 0 :
f o r

S e n d
s h i p p

3 : C o n n e c t c u s t o m
e r
t o
c u s t o m
e r d a t f a d b: F a i n s ae n c i n g D
r o c e s s o

b : C

e p

a d d
i n g
r t m

2 : M
a t c h e s
c u s t o m
e r
d a t a b a s e
c d

e p a r t m

t o

u s t o

8 : C
f o r
e

88

r D

t a

b a

9 : A c c e p
c r e d i t
h e c k
c r e d i t
c u s t o m
e r
s e

e n

r e s

4.4 CLASS DIAGRAM:


DESCRIPTION:
In software engineering, a class diagram in the Unified Modeling Language
(UML) is a type of static structure diagram that describes the structure of a system by
showing the system's classes, their attributes, and the relationships between the classes.
In our class diagram, the classes identified are
Participant
Controller
Display
Database
login
Each class has its own attributes and operations.
Participant class -The attributes defined are name and email id.The operations involved
are login
Controller class -The attributes it has is result, votes, nominees, name, email id.The
operations carried out by this class are login, voting.
Display class - The attributes are option, nominees. The operations identified are
Display_nom, Display_ vote.
Database class - The attributes are nominees, vote, result. The operation defined is store
_ details.
Login class - The attributes defined is name and email id. The method identified is
login_details.
The Solid line between the classes shows the relationship between them.

STEPS FOR GENERATING CLASS DIAGRAM:


Rose automatically creates the Main class diagram in the Logical View of the model.
To add packages to the Main class diagram:
1. Double-click on the Main diagram in the browser to open it.
2. Click to select the package in the browser.
89

3. Drag the package onto the diagram.


4. Repeat the preceding steps for each package that is to be added to the diagram.

4.5 ACTIVITY DIAGRAM:


DESCRIPTION:
It provides a way to model the workflow of a development process. An activity
represents the performance of a task on duty. It represent the execution of statement.

90

STEPS FOR GENERATING ACTIVITY DIAGRAM:


1. Right-click to select the class in the browser and make the shortcut menu visible.
2. Select the State Diagram menu choice. This will automatically create and open the
diagram.
3. To open the diagram at another time, click the + to expand the class in the browser,
and double-click on its state transition diagram in the browser

91

5. IMPLEMENTATION:
STEPS FOR CODE GENERATION:
1. Open your model and display the Class Diagram that contains the classes and packages
for which you want to generate Java source.
2. Select one or more classes or packages in the diagram.
3. Optionally, use the syntax checker before generating your Java source.
4. On the Tools menu, point to Java, and then click Generate Java.
5. If a package or component hasnt been mapped to an entry in your classpath settings
(for example, this is the first time youve generated code for a component or package),
the Component Mapping dialog appears enabling you to set up the appropriate
associations.
6. Check the Rose Log window to view the results of the Java generation, including any
errors that occurred.
7. Correct any errors and repeat step 4 until no errors are returned.
8. View and edit the generated code.

CODE:
Public class
{
Public Productlist()
{
}
Public optionlist()
{
}
Public productdetails()
{
}
Public Optiondetails()
{
}
92

Coding:
Page 1:
<html>
<head>
<h3><I><marquee><MARQUEE DIRECTION ="LEFT" BEHAVIOUR="alternate"
scrolldeley=80 bgcolor="ORANGE">THE WORLD OF ONLINE
SHOPPING</MARQUEE>
Welcome To The Web World</marquee></h3><I>
<div ><div id="840118827707463697" align="left" style="width: 100%; overflow-y:
hidden;"><!-- this script got from www.htmlfreecodes.com coded by: Krishna Eydat-->
<html>
<head>
<script language="javascript" type="text/javascript">
alert("Welcome to online shopping")
</script>
</head>
</html>
<font face="Tahoma"><a target="_blank" href="http://www.htmldodes.com/"><span
style="font-size: 8pt; text-decoration: none"></span></a></font>
</div>
<CENTER><IMG SRC="D:\photos\WALLPAPER\games\red_alert2_4_1024x768.jpg"
ALIGN="right" WIDTH=250 HEIGHT=250 BORDER=10></CENTER>
<BR><BR>Enter name <INPUT TYPE="NAME" SIZE=34 <BR><BR>
<BR><BR>Enter credit card no <INPUT TYPE="NUMBER" SIZE=24<BR><BR>
<BR><td align="center"><input name="submit" type="submit" value="Submit"/>
</td><BR>
</head>
</html>

Page 2:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
93

<head>
<title>Website Design, Web Design Companies and Designers Directory</title>
<meta name="Description" content="Directory of top website design companies and web
designers providing professional web design and development services.">
<meta name="Keywords" content="web website design companies designer">
<meta name="robots" CONTENT="index, follow" />
<meta name="googlebot" CONTENT="index, follow" />
<link rel='stylesheet' href='style.css' type='text/css'>
</head>
<body topmargin="0" bottommargin="0" leftmargin="0" rightmargin="0"
marginheight="0" marginwidth="0">
<table width='776' cellpadding="0" cellspacing="0" class="main">
<tr>
<td align="left" bgcolor="#ffffff">
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td colspan="2" bgcolor="FF9608" leftmargin="0" rightmargin="0" align="left"><a
href="/"><img src="images/design-logo.gif" border="0" alt="Online Shopping
Directory"></a></td>
</tr>
<tr>
<td colspan="2" bgcolor="ffffff" leftmargin="0" rightmargin="0" height="1">
</td>
</tr>
<tr><td colspan=2 bgcolor="#d4d4d4"><table class=headmenu align="right"><tr>
<td><a href="C:\Documents and Settings\Sabareesh\Desktop\pro1\title.html"
class=headmenu>More products</a></td><td width="1" height="21"><img
src="images/spacer.gif" width="1" height="21"></td><td><a href="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" class=headmenu>Policies</a></td><td
width="1" height="21"><img src="images/spacer.gif" width="1"
height="21"></td><td><a href="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" class=headmenu>if we are Free</a></td><td
width="1" height="21"><img src="images/spacer.gif" width="1"
height="21"></td><td><a href="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" class=headmenu>Contact Us</a></td><td
width="1" height="21"><img src="images/spacer.gif" width="1"
height="21"></td><td><a href="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" class=headmenu>About
us</a>&nbsp;&nbsp;&nbsp;</td> </tr></table></td></tr>
<tr>
94

<td colspan="2" width="776" bgcolor="ffffff"><img src="images/spacer.gif"


width="776" height="10"></td>
</tr>
<tr>
<td colspan="2">
<table width="776" height="480" cellpadding="0" cellspacing="0" border="0"
align="center">
<tr>
<td bgcolor="#ffffff" width="164" valign="top" align="left">
<div id=leftbar>Shopping Lists</div>
<div class="navleft2"><img src="images/arrow.gif"><a
href="http://www.ebay.com">Electronics</a></div>
<div class="navleft2"><img src="images/arrow.gif"><a href="http://www.onlineShopping.com">Electricals</a></div>
<div class="navleft2"><img src="images/arrow.gif"><a href="http://www.Shopping
world.com">Books </a></div>
<div class="navleft2"><img src="images/arrow.gif"><a
href="http://www.ebay.com">Computer Goods </a></div>
<div class="navleft2"><img src="images/arrow.gif"><a
href="http://www.ebay.com">Medicines </a></div>
<div class="navleft2"><img src="images/arrow.gif"><a
href="http://www.ebay.com">Stationories </a></div>
<img src="images/spacer.gif" width="1" height="10"><br>
<div id=leftbar>Web Resources</div>
<div class="navleft2"><img src="images/arrow.gif"><a href="www">Online
Hosting</a></div>
<div class="navleft2"><img src="images/arrow.gif"><a href="Shopping designdirectory.html">site Design</a></div>
<div class="navleft2"><img src="images/arrow.gif"><a href="onlineshopping.html">Credit Submission</a></div>
<div class="navleft2"><img src="images/arrow.gif"><a href="search-engine-marketingreview.html">SEO</a></div>
</td>
<td width="1" bgcolor="ededed"></td>
<td width="614" valign="top" align="left" height="100%">
<table width="610" cellpadding="0" cellspacing="0">
<tr>
<td width="10" height="1"><img src="images/spacer.gif" width="10" height="1"></td>
<td colspan="2" valign="top">
<table cellpadding="0" width="600">
95

<tr>
<td class="text">
<h1><font size="4"><strong>Web Shopping Details &amp; Website Shopping
Companies Directory</strong></font></h1>
<img src="images/website-design-image.gif" alt="Website Designs" align="right">
Online shopping is a method to buy a products in your home with a smile.
lets take a charm with us. surely we will satisfy you soon.
it gives you a joyable experience in shopping whatever you buy as we can do soon.
</td>
</tr>
</table>
<!-- featured -->
<table width="100%" cellspacing=0 cellpadding=0>
<tr>
<td width="20%" align="center" valign="middle" class="reviewheading2"
height="50">WEB DESIGN FIRM</td>
<td width="20%" align="center" valign="middle" class="reviewheading2"
height="50">EDITOR'S RATINGS</td>
<td width="30%" align="center" valign="middle" class="reviewheading2"
height="50">REVIEW</td>
</tr>
<!-- Online Shopping design 1 Begin Here -->
<tr>
<table width="100%" cellspacing=0 cellpadding=0>
<tr>
<td align="left">
<img src="images/spacer.gif" height="1" width="3">
</td>
<td align="left">
<li><b>system shopping</b></li>
<li><b>Flash/Animation</b></li>
<li><b>Web Analytics</b></li>
<li><b>Online Hosting</b></li>
</td>
</tr>
</table>
</td>
<td width="30%" align="left" valign="top" class="reviewdetail" height="50">
<table width="100%" cellspacing=0 cellpadding=0>
<br>
<tr>
96

<td width="10" align="left"><img src="images/spacer.gif" height="1"


width="10"></td>
<td align="left">
<table width="100%" cellspacing=0 cellpadding=0>
<tr>
<td align="left"><B>OVER ALL SCORE</B></td>
</tr>
<tr>
<td align="left"><img src="images/spacer.gif" height="5" width="1"></td>
</tr>
<tr>
<td align="left">Needs Analysis</td>
</tr>
<tr>
<td align="left">Experience</td>
</tr>
<tr>
<td align="left">Quality</td>
</tr>
<tr>
<td align="left">Customer Service</td>
</tr>
<tr>
<td align="left">Value</td>
</tr>
</table></td>
<td align="left">
<table width="100%" cellspacing=0 cellpadding=0>
<tr>
<td align="left"><font color="cc0000" size="2" face="arial black">98.6%
(A+)</font></td>
</tr>
<tr>
<td align="left"><img src="images/spacer.gif" height="5" width="1"></td>
</tr>
<tr>
<td align="left">100%</td>
</tr>
<tr>
<td align="left">97%</td>
</tr>
97

<tr>
<td align="left">97%</td>
</tr>
<tr>
<td align="left">100%</td>
</tr>
<tr>
<td align="left">100%</td>
</tr>
</table>
</tr>
<tr>
<td width="1" align="left" colspan="3"><img src="images/spacer.gif" height="15"
width="1"></td>
</tr>
4:40 PM 10/11/2010
<tr>
<td colspan="3" align="center"><img src="images/award.gif"></td>
</tr>
<tr>
<td width="1" align="left" colspan="3"><img src="images/spacer.gif" height="15"
width="1"></td>
</tr>
<tr>
<td colspan="3" align="center"><a href="http://www.opengatewebdesign.com"><img
src="images/quote.gif" border="0"></a></td>
</tr>
<tr>
<td width="1" align="left" colspan="3"><img src="images/spacer.gif" height="10"
width="1"></td>
</tr>
</table>
</td>
<td width="25%" align="left" class="reviewdetail" height="50" valign="top">
<table width="100%" cellspacing=0 cellpadding=0>
<br>
<tr>
<td width="10" align="left"><img src="images/spacer.gif" height="1"
width="10"></td>
<td align="left"> lets give a chance to us</td>
98

<td width="5" align="left"><img src="images/spacer.gif" height="1" width="5"></td>


</tr>
<tr>
<td width="1" align="left"><img src="images/spacer.gif" height="10" width="1"></td>
</tr>
<tr>
<td align="center"><a href="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" >type=button<strong></strong></a></td>
</tr>
<tr>
<td width="1" align="left"><img src="images/spacer.gif" height="10" width="1"></td>
</tr>
</table>
</td>
</tr>
</table>
<!-- FORM START -->
<form method="post" action="C:\Documents and
Settings\Sabareesh\Desktop\pro1\title.html" >
<table cellpadding="0" cellspacing="0" width="590" class="featured">
<tr>
<td width="10" valign="center" ><img src="images/spacer.gif" height="1"
width="10"></td>
<td width="580">
<table cellpadding="0" cellspacing="0" width="580">
<tr>
<td height="7"><img src="images/spacer.gif" height="7" width="1"></td>
</tr>
<tr>
<td class="texthead">FREE Online Referral Service</td>
<tr>
<tr>
<td height="3"><img src="images/spacer.gif" height="3" width="1"></td>
</tr>
<td class="text2">It can be extremely difficult to determine which web design company
or designer is best qualified to handle your web design project. Let us simplify the
process. Simply fill out the form below and we'll refer you to the web design firm that is
most qualified to handle your project.</td>
</tr>
</table>
<table width="580" cellpadding="0" cellspacing="0">
99

<tr>
<td><img src="images/spacer.gif" height="10" width="1"></td>
</tr>
</table>
<table width="580" cellpadding="0" cellspacing="0">
<tr>
<td align="left" width="240" class="text2" valign="top">
<table width="240" cellpadding="0" cellspacing="0">
<tr>
<td class="text2"><strong><font face="arial">Contact
Name:</font></strong>&nbsp;&nbsp;<font color="ff0000" size="1"
face="arial">(required)</font><br><input id="contactname" name="contactname"
type="text" size="30" style="font-family: arial; font-size: 13px; float: left;"></td>
</tr>
<tr>
<td class="text2"><strong><font face="arial">Address:</font></strong><br><input
id="address" name="address" type="text" size="30" style="font-family: arial; font-size:
13px; float: left;"></td>
</tr>
<tr>
<td class="text2"><strong><font face="arial">Contact Phone
Number:</font></strong>&nbsp;&nbsp;<font color="ff0000" size="1"
face="arial">(required)</font><br><input id="phone" name="phone" type="text"
size="30" style="font-family: arial; font-size: 13px; float: left;"></td>
</tr>
<tr>
<td class="text2"><strong><font
face="arial">Email:</font></strong>&nbsp;&nbsp;<font color="ff0000" size="1"
face="arial">(required)</font><br><input id="email" name="email" type="text"
size="30" style="font-family: arial; font-size: 13px; float: left;"></td>
</tr>
<tr>
<td class="text2">
<strong><font face="arial">Do you already have a website?</font></strong><br>
<select style="font-family: arial; font-size: 13px;" id="currentsite"
NAME="currentsite">
<option SELECTED value="select">Select one...</option>
<option value="yes">Yes</option>
<option value="no">No</option>
</select></td>
</tr>
100

<tr>
<td class="text2"><strong><font face="arial">If yes, what is your URL?
</font><br><input id="url" name="url" type="text" size="30" style="font-family: arial;
font-size: 13px; float: left;"></strong></td>
</tr>
<tr>
<td class="text2">
<strong><font face="arial">When would you like to begin?</font></strong><br>
<select style="font-family: arial; font-size: 13px;" id="start" NAME="start">
<option SELECTED value="select">Select one...</option>
<option value="now">Immediately</option>
<option value="oneweek">1 week</option>
<option value="twoweeks">2 weeks</option>
<option value="onemonth">One month</option>
<option value="twomonths">2 months</option>
<option value="threemonths">3 or more months</option>
</select></td>
</tr>
<tr>
<td class="text2">
<strong><font face="arial">What is your budget?</font></strong><br>
<select style="font-family: arial; font-size: 13px;" id="price" NAME="price">
<option SELECTED value="price">Select one...</option>
<option value="200">$200 to $500</option>
<option value="500">$500 to $1000</option>
<option value="1000">$1000 to $3000</option>
<option value="3000">$3000 to $5000</option>
<option value="5000">$5000+</option>
</select></td>
</tr>
</table>
</td>
<td width="340" valign="top">
<table width="340">
<tr>
<td class="text"><b>our products Services Required:</b>&nbsp;&nbsp;<font
color="ff0000" size="1" face="arial">(check all that apply)</font></td>
</tr>
<tr>
<td class="text2">
101

<input type="checkbox" name="ServicesRequired_1" id="ServicesRequiredInformationSite" value="checked" />


Information of Site <br />
<input type="checkbox" name="ServicesRequired_2" id="ServicesRequiredEcommerceSite" value="checked" />
Ecommerce Web Site (Shopping Cart)<br />
<input type="checkbox" name="ServicesRequired_3" id="ServicesRequiredProfessionalSite" value="checked" />
Professional Web Site (Doctor, Lawyer, etc.) <br />
<input type="checkbox" name="ServicesRequired_4" id="ServicesRequiredWebAnimation" value="checked" />
Flash / Web Animation<br />
<input type="checkbox" name="ServicesRequired_5" id="ServicesRequiredLogoDesign" value="checked" />
Logo Design<br />
<input type="checkbox" name="ServicesRequired_6" id="ServicesRequired-SEO"
value="checked" />
Search Engine Optimization (SEO)<br />
<input type="checkbox" name="ServicesRequired_7" id="ServicesRequiredWebAnalytics" value="checked" />
Web Stats / Analytics<br />
<input type="checkbox" name="ServicesRequired_8" id="ServicesRequiredOtherServices" value="checked" />
Other Web Design Services<br />
<img src="images/spacer.gif" width="1" height="7"><br>
<div class="textsmall">Please give us any other relevant details (what you're looking for,
# of pages, sample links, etc.) so we can find the best firm for your project.</div>
<img src="images/spacer.gif" width="1" height="1"><br>
<textarea name="ProjectDescription" cols="38" rows="5" class="optional"
id="ProjectDescription" title="Your detailed project description"></textarea>
</td>
<td width="8" valign="center" ><img src="images/spacer.gif" height="1"
width="8"></td>
</tr>
</table>
</td>
</tr>
</table>
<table cellpadding="0" cellspacing="0" width="580" align="center">
<tr>
<td height="15"><img src="images/spacer.gif" height="15" width="1"></td>
102

</tr>
<tr>
<td align="center"><input name="submit" type="submit" value="Submit"/>
<input name="button" type="button" onClick="valid.reset(); return false"
value="Reset" />
</td>
</tr>
<tr>
</tr>
</table>
</td>
</tr>
</table>
</form>
<!-- FORM END -->
<!-<table cellpadding="0" width="600">
<tr>
<td colspan="4"><h4>Website Design Companies by State</h4></td>
</tr>
<tr>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="arizona-web-design.html"
class="middlenav">Arizona</a><br>
<img src="images/black-arrow.gif"><a href="california-web-design.html"
class="middlenav">California</a><br>
<img src="images/black-arrow.gif"><a href="colorado-web-design.html"
class="middlenav">Colorado</a><br>
</td>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="delaware-web-design.html"
class="middlenav">Delaware</a><br>
<img src="images/black-arrow.gif"><a href="florida-web-design.html"
class="middlenav">Florida</a><br>
<img src="images/black-arrow.gif"><a href="idaho-web-design.html"
class="middlenav">Idaho</a><br>
</td>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="michigan-web-design.html"
class="middlenav">Michigan</a><br>

103

<img src="images/black-arrow.gif"><a href="new-york-web-design.html"


class="middlenav">New York</a><br>
<img src="images/black-arrow.gif"><a href="ohio-web-design.html"
class="middlenav">Ohio</a><br>
</td>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="oregon-web-design.html"
class="middlenav">Oregon</a><br>
<img src="images/black-arrow.gif"><a href="texas-web-design.html"
class="middlenav">Texas</a><br>
<img src="images/black-arrow.gif"><a href="washington-web-design.html"
class="middlenav">Washington</a><br>
</td>
</tr>
</table>
-->
<!-<table cellpadding="0" width="600">
<tr>
<td colspan="4"><h4>Website Design Companies by Category</h4></td>
</tr>
<tr>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="real-estate-web-design.html"
class="middlenav">Real Estate</a><br>
<img src="images/black-arrow.gif"><a href="flash-websites.html"
class="middlenav">Flash</a><br>
</td>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="custom-website-design.html"
class="middlenav">Custom</a><br>
<img src="images/black-arrow.gif"><a href="small-business.html"
class="middlenav">Small Business</a><br>
</td>
<td width="140" valign="top">
<img src="images/black-arrow.gif"><a href="wedding-website-design.html"
class="middlenav">Wedding</a><br>
<img src="images/black-arrow.gif"><a href="photography-websites.html"
class="middlenav">Photography</a><br>
</td>
104

<td width="140" valign="top">


<img src="images/black-arrow.gif"><a href="ecommerce-website-design.html"
class="middlenav">Ecommerce</a><br>
<img src="images/black-arrow.gif"><a href="law-website-design.html"
class="middlenav">Law</a><br>
</td>
</tr>
</table>
-->
</td>
</tr>
</table>
</td>
</tr>
<tr>
<td colspan="14" width="776" bgcolor="ffffff"><img src="images/spacer.gif"
width="776" height="10"></td>
</tr>
<tr>
<td colspan="14" width="776" bgcolor="FF9608" align="center" height="20"
class="copyright"> 2004-2008
Free-Website-Hit-Counters.com. All Rights Reserved.</td>
</tr>

</table>
</td>
</tr>
</table>
<script language="Javascript"> if(document.referrer&&document.referrer!="")
document.write("<img src='http://www.inteliture.com/cgi-bin/statcount.pl?a=18&t=" +
document.title + "&r="+escape(document.referrer)
+"&w="+screen.width+"&h="+screen.height+"' height='1' width='1' border='0' />");
else document.write("<img src='http://www.inteliture.com/cgi-bin/statcount.pl?a=18&t="
+
document.title + "&r=x&w="+screen.width+"&h="+screen.height+"' height='1' width='1'
border='0' />");</script>
</body>
105

</html>

6. TEST CASE GENERATION:

No

Error
Description
Invalid credit card
Number.

Output Description
Entered credit number must invalid
Characters.

106

Username and
Password
mismatch.

Products Not
Available.

The Specified products not available in


the shopping.

Invalid Details

The Details for purchasing a Products


was not a valid Details .

Searching Errors

Given type of data mismatch.

Sometimes a customer can search a


undefined Products.

107

SAMPLE OUTPUT SCREENS:


Page1:

108

Page2:

Page3:

109

110

RESULT:
Thus the Online Shopping Project was Implemented using Visual Basic , Designed
using Rational Rose and Executed Successfully.

111

Anda mungkin juga menyukai