1

1. ATM SYSTEM
CONTENTS
1. PROBLEM STATEMENT
2. PROBLEM DOMAIN GLOSSARY
3. SYSTEM DESIGN DESCRIPTION
4. USE CASE ANALYSIS SOLUTION
4.1 Use Case Diagram
4.2 Class Diagram
4.3 Sequence Diagram
4.4 Collaboration Diagram
4.5 Activity Diagram
5. IMPLEMENTATION
5.1 Code Generation
6. SCREEN SHOTS
7. TESTING
8. CONCLUSION


2


3

1. PROBLEM STATEMENT

The project entitled ATM system has a drastic change to that of the older
version of banking system, customer feel inconvenient with the transaction method as it
was in the hands of the bank employees.
In our ATM system, the above problem is overcome here, the transactions
are done in person by the customer thus makes the customers feel safe and secure.
Thus the application of our system helps the customer in checking the
balance and transaction of the amount by validating the pin number therefore ATM
system is more user friendly.
2. PROBLEM DOMAIN GLOSSARY
2.1 Introduction
Auto teller machine is developed for the benefits of the customers. The system
must provide facilities for the customer to deposit and withdraw amount. The display
design must be easy to understand and at the end of the transaction confirmation message
must be displayed.
Action
 Accept a relevant cash card
 Interact with the user
 Communicate with the central system to carry out transaction
 Dispense cash
 Print results
2.2 Definition
The bank client must be able to deposit or withdraw an amount to/from the
account using ATM. Access to the bank account of bank client is to be provided by the
PIN code.

4

Hardware requirements:
 512 MB RAM
 Windows XP
 Intel processor
Software requirements:
 Microsoft Visual basic 6.0
 Oracle
 Rational rose Enterprise edition



















5



3. SYSTEM DESIGN DESCRIPTION

3.1 USE CASE SPECIFICATION - DEPOSIT MODULE
Brief Description:
This allows client to deposit the amount to his/her account.
Flow of Events:
1. Basic Flow:
The client should enter the pin number and amount to the system. The
system checks the pin no. If it is valid then the amount will be deposited
successfully.
1. Alternative Flow:
If the given pin number is not valid, then the error message will be
displayed.
Precondition:
Client should enter valid pin number and amount to deposit.
Post condition:
Amount will be deposited successfully and client can select another
transaction.

3.2 USE CASE SPECIFICATION - WITHDRAW MODULE
Brief Description:
This allows client to withdraw amount from his/her account.
Flow of Events
1. Basic Flow:
6

The client should enter the pin number and amount to the system.
The system checks the pin no. If it is valid then the amount will be
withdrawn successfully.

2. Alternative Flow:
If the given pin number is not valid, then the error message will be
displayed.
Precondition:
Client should enter valid pin number and amount to withdraw.
Post condition:
Amount will be withdrawn successfully and client can select another
transaction
3.3 USE CASE SPECIFICATION - CHECK BALANCE MODULE
Brief Description:
This allows client to view the current balance amount in his/her account.
Flow of Events
1. Basic Flow:
The client should enter the pin number to the system. The system checks
the pin no, If it is valid then current balance will be displayed in the message box.
2. Alternative Flow:
If the given pin number is not valid, then the error message will be
displayed.
Precondition:
Client should enter valid pin number.
Post condition:
Current balance will be displayed and client can select another transaction
3.4 USE CASE SPECIFICATION - CHANGE PIN NUMBER MODULE
7

Brief Description:
This allows client to change the pin number in his/her pin number




Flow of Events
1. Basic Flow:
The client should enter the old pin number and new pin number. The
system checks the old pin no. If it is valid then the new pin number will be
updated.
2. Alternative Flow:
If the given pin number is not valid, then the error message will be
displayed.
Precondition:
Client should enter the old pin number and new pin number.
Post condition:
Pin number will be changed successfully and client can select another
transaction









8








4. USE CASE ANALYSIS SOLUTION
4.1 USECASE DIAGRAM FOR ATM



deposit
withdraw
balance enquiry
change pin no
client
check pin no login
admin
9










4.2 CLASS DIAGRAMS

4.2.1 CLASS DIAGRAM FOR DEPOSIT



4.2.2 CLASS DIAGRAM FOR WITHDRAW

10



4.2.3 CLASS DIAGRAM FOR CHECKING BALANCE




4.2.4 CLASS DIAGRAM FOR CHANGE PIN NO

11






4.3 SEQUENCE DIAGRAMS
4.3.1 SEQUENCE DIAGRAM FOR DEPOSIT
12




bank client
atm
account current
account
1: insert atm card
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: request kind
7: enter kind
8: request amount
9: enter amount
10: process transaction
11: current deposit
12: deposit successfull
13: transaction successful
14: dispense cash
15: request take card
16: take cash
17: terminate
13

4.3.2 SEQUENCE DIAGRAM FOR WITHDRAW



bank client
atm
account current
account
1: insert atm card
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: request kind
7: enter kind
8: request amount
9: enter amount
10: process transaction
11: current withdraw
12: withdraw successfull
13: transaction successful
15: request take card
14: take cash
16: terminate
14



4.3.3 SEQUENCE DIAGRAM FOR CHECKING BALANCE


client atm
current
account
1: insert atm card
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: requested kind
7: enter kind
8: enter the account number
9: checking balance
10: informed balance
11: display balance amount
12: exit
13: request take card
14: terminate
15





4.3.4 SEQUENCE DIAGRAM FOR CHANGE PIN NUMBER


client atm
current
account
1: insert atm card
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: requested kind
7: enter kind
8: enter pin number
9: check pin number
10: valid pin
11: enter new pin
12: new pin
13: register new pin
14: pin no changed
15: request take card
16: terminate
16

4.4 COLLBORATION DIAGRAMS
4.4.1 COLLABORATION DIAGRAM FOR WITHDRAW










account
bank
client
atm
checking
account
11: withdraw checking
12: withdraw successfull
1: insert atm card
2: request pin
3: enter pin
6: request kind
7: enter kind
8: request amount
9: enter amount
14: dispense cash
15: request take card
16: take cash
17: terminate
4: verify pin
5: pin ok
10: process transaction
13: transaction successful
17


4.4.2 COLLABORATION DIAGRAM FOR DEPOSIT



4.4.3COLLABORATION DIAGRAM FOR CHECKING BALANCE
bank
client
atm
account current
account
1: insert atm card
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: request kind
7: enter kind
8: request amount
9: enter amount
10: process transaction
11: current deposit
12: deposit successfull
13: transaction successful
14: dispense cash
15: request take card
16: take cash
17: terminate
18



4.4.4 COLLABORATION DIAGRAM FOR CHANGE PIN NO

client atm
checking
account
2: request pin
3: enter pin
4: verify pin
5: pin ok
6: requested kind
7: enter kind
8: enter the account number
9: checking balance
10: informed balance
11: display balance amount
12: exit
13: request take card
14: terminate
19
















client atm
current
account
2: request pin
4: verify pin
5: pin ok
6: requested kind
7: enter kind
8: enter pin number
9: check pin number
10: valid pin
11: enter new pin
12: new pin
13: register new pin
14: pin no changed
15: request take card
16: terminate
20

4.5 ACTIVITY DIAGRAMS
4.5.1 ACTIVITY DIAGRAM FOR DEPOSIT


insert the
card
choose the
option
deposit
remove the
card
enter the pin
number
invalid pin
Amount deposited
21

4.4.2 ACTIVITY DIAGRAM FOR WITHDRAW





insert the
card
enter the
pin no
choose the
option
withdraw
remove the
card
withdraw completed
more transaction
invalid pin
22


4.4.3 ACTIVITY DIAGRAM FOR BALANCE CHECKING



insert the
card
choose the
option
balance
checking
remove the
card
enter the pin
number
more transaction
balance checking completed
invalid pin
23




4.4.4 ACTIVITY DIAGRAM FOR CHANGE PIN NUMBER

24




5. IMPLEMENTATION
insert the
card
choose the
option
change pin
number
remove the
card
enter the pin
number
more transaction
pin number changed
invalid pin
25

LOGIN FORM
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cms As New ADODB.Command
Private Sub Command1_Click()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
Set rs = New ADODB.Recordset
If (Text1.Text = "") Then
MsgBox ("ENTER YOUR PIN")
Else
rs.Open "select pinno from client1 where pinno=" & Text1.Text, con
If (rs.EOF) Then
MsgBox ("INVALID PINNO")
Text1.Text = ""
Else
If (Text1.Text = rs(0)) Then
MsgBox ("VALID")
login.Hide
menu.Show
rs.Close
End If
End If
End If
con.Close
End Sub




26


ACCOUNT TYPE FORM
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim acctype As String
Private Sub Command1_Click()
rs.Open "select acctype from client1 where pinno=" & login.Text1.Text, con
acctype = rs(0)
If (acctype = "savings") Then
menu.Hide
savingmenu.Show
Else MsgBox ("YOU ARE NOT BELONGS TO SAVINGS ACCOUNT")
End If
rs.Close
End Sub
Private Sub Command2_Click()
rs.Open "select acctype from client1 where pinno=" & login.Text1.Text, con
acctype = rs(0)
If (acctype = "current") Then
menu.Hide
currentmenu.Show
Else MsgBox ("YOU ARE NOT BELONGS TO CURRENT ACCOUNT")
End If
rs.Close
End Sub
Private Sub Form_Load()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
End Sub

27




MENU FORM
Dim cmd As New ADODB.Command
Private Sub Command1_Click()
con.Close
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
rs.Open "select balance from client1 where pinno=" & login.Text1.Text, con
MsgBox Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
("YOUR BALANCE IS:" & rs(0))
rs.Close
End Sub
Private Sub Command2_Click()
currentmenu.Hide
currentwithdraw.Show
End Sub
Private Sub Command3_Click()
login.Text1.Text = ""
MsgBox "TAKE YOUR CARD"
welcome.Show
End Sub
Private Sub Command4_Click()
currentdeposit.Show
End Sub
Private Sub Command5_Click()
changepin.Show
End Sub
28

Private Sub Form_Load()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
End Sub
DEPOSIT FORM
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cmd As New ADODB.Command
Private Sub Command1_Click()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
rs.Open "select balance from client1 where pinno=" & login.Text1.Text, con
a = Text1.Text
If (Text1.Text = "") Then
MsgBox ("PLEASE ENTER THE AMOUNT TO DEPOSIT")
ElseIf (Text1.Text < 100) Then
MsgBox ("YOU CANNOT DEPOSIT AMOUNT LESS THAN 100")
Else
b = rs(0) + Val(a)
cmd.ActiveConnection = con
cmd.CommandText = "update client1 set balance=" & b & "where pinno=" & login.Text1.Text
cmd.Execute
rs.Close
rs.Open "select balance from client1 where pinno=" & login.Text1.Text, con
MsgBox ("NOW YOUR BALANCE IS : " & rs(0))
rs.Close
Text1.Text = ""
currentdeposit.Hide
currentmenu.Show
29

End If
con.Close
End Sub
WITHDRAW FORM
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cmd As New ADODB.Command
Private Sub Command1_Click()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
rs.Open "select balance from client1 where pinno=" & login.Text1.Text, con
a = Text1.Text
If (Text1.Text = "") Then
MsgBox ("PLEASE ENTER THE AMOUNT TO WITHDRAW")
ElseIf (Text1.Text < 100) Then
MsgBox ("YOU CANNOT WITHDRAW AMOUNT LESS THAN 100")
Else
b = rs(0) - a
If (b < 1000) Then
MsgBox ("YOU CANNOT WITHDRAW , MINIMUM 500 SHOULD MAINTAIN IN YOUR
ACCOUNT")
Else
cmd.ActiveConnection = con
cmd.CommandText = "update client1 set balance=" & b & "where pinno=" & login.Text1.Text
cmd.Execute
rs.Close
rs.Open "select balance from client1 where pinno=" & login.Text1.Text, con
MsgBox ("NOW YOUR BALANCE IS : " & rs(0))
rs.Close
Text1.Text = ""
30

currentwithdraw.Hide
currentmenu.Show
End If
End If
con.Close
End Sub
CHANGE PINNO FORM
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cmd As New ADODB.Command
Dim pin As Integer
Private Sub Command1_Click()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
If (Text1.Text = "") Then
MsgBox ("ENTER YOUR OLD PIN")
Else
rs.Open "select pinno from client1 where pinno=" & Text1.Text, con
If (rs.EOF) Then
MsgBox ("INVALID PIN, ENTER CORRECT PINNO")
Else
If (Text1.Text = rs(0)) Then
Label4.Visible = True
Text2.Visible = True
Label5.Visible = True
Text3.Visible = True
Command2.Visible = True
Else
MsgBox ("INVALID PINNO")
End If
31

End If
End If
con.Close
End Sub
Private Sub Command2_Click()
con.ConnectionString = "Provider=MSDAORA.1;User ID=exam01;password=exam01;Data
Source=sonamcc;Persist Security Info=False"
con.Open
If (Text2.Text = Text3.Text) Then
cmd.ActiveConnection = con
cmd.CommandText = "update client1 set pinno=" & Text2.Text & "where pinno=" & login.Text1.Text
cmd.Execute
cmd.CommandText = "commit"
cmd.Execute
login.Text1.Text = Text2.Text
pin = Text2.Text
MsgBox ("YOUR PINNO HAS BEEN CHANGED SUCCESSFULLY")
rs.Open "select acctype from client1 where pinno=" & pin, con
If (rs(0) = "savings") Then
changepin.Hide
savingmenu.Show
Else
changepin.Hide
currentmenu.Show
End If
rs.Close
Else
MsgBox ("RE-ENTER YOUR PINNO")
Form4.Show
End If
Text1.Text = ""
32

Text2.Text = ""
Text3.Text = ""
con.Close
End Sub







6.SCREEN SHOTS
WELCOME FORM


LOGIN FORM
33



ACCOUNT TYPE FORM

34


MENU FORM


BALANCE ENQUIRY FORM
35



DEPOSIT FORM


36

WITHDRAW FORM


CHANGE PINNO FORM


37



7.TESTING
TEST OBJ ECTI VE:
A process of executing a program with the intention to find error is called testing.
A good test is one that has high probability of finding errors. A test uncovers
undiscovered is said to be a successful test.
If testing is done successful, then it will uncover error in the software testing
demonstrates the software function appear to be working according to the specification
that behavioural and performance requirement appear to have met. Data collected as
testing is conducted to provide good indication of software reliability and some indication
of software quality as a hole.
TEST PLAN:
Before testing is to be done, test plan must be done in order to identify which testing
methods to implement for the project. The test cases must be identified.
STABI LI TY TEST:
Usability test is the test of effectiveness, efficiency and satisfaction. The stability
testing process includes all of software‟s components. Quick, iterative test can be user
identify 80-90 percent of the design problem.
Stability test can be conducted in a one-on-one fasion, as a demonstration or as a
„walk through‟ in which the users are taken through a set of samples scenarios.
Stability testing measures the case use as well as the degree of comfort and satisfaction
users with the software. Usability test cases begin with the identification if use cases that
can specify the target audience, tasks and test goals.
USER SATISFACTI ON TEST:
38

User satisfaction test is the process of quantifying the usability test with some
measurable attributes of the test, such a functionality cost or ease of use.
User satisfaction testing includes working with the users or client to find out what
attribute to be included in the test. It provides a periodic indication of divergence of
opinion about the design.







8. CONCLUSION

Thus the project for ATM System has been developed with the help of visual
basic. In this project the customer details like pin number, account number and balance
are stored in database. By using this system customer can view their available balance
and make transactions like withdraw and deposit.






39








2. QUIZ SYSTEM

CONTENTS
1. PROBLEM STATEMENT
2. PROBLEM DOMAIN GLOSSARY
3. SYSTEM DESIGN DESCRIPTION
4. USE CASE ANALYSIS SOLUTION
4.1 Use Case Diagram
4.2 Class Diagram
4.3 Sequence Diagram
4.4 Collaboration Diagram
4.5 Activity Diagram
5. IMPLEMENTATION
5.1 Code Generation
40

6. SCREEN SHOTS
7. TESTING
8. CONCLUSION



1. PROBLEM STATEMENT
QUIZ SYSTEM is a software developed to conduct an Quiz based . Quiz System is
accessed by entering the username and e-mail id which is added to the database. Before
start of the Quiz, the rules and regulations are displayed that includes description of time
limit, number of questions to be answered and scoring methods. Quiz is started by
displaying ten questions with four options each based on category chosen ie General
Knowledge, Verbal Reasoning and Computer Science. If the answer is correct, score is
incremented by two and no negative marks for wrong answers. All the questions are
answered the quiz is stopped .Final score will be displayed and updated in the database
with username.
2. PROBLEM DOMAIN GLOSSARY
2.1 Introduction
The main objective of the system is to enable the users to play Quiz through online where
they gain knowledge based on their areas of interest.
41

2.2 Definition
The Online Quiz System promotes the users to update their knowledge. The user has to
login the system by providing the name and the e-mail id. Game is started by choosing
the category of their interest. Finally the score is evaluated based on the answers and
displays the score card.
2.3 SYSTEM REQUIREMENTS
Hardware Requirements
Apart from the standard personal computer no additional hardware.


Software Requirements
1. Microsoft Visual Basic 6.0
2. Oracle: SQL Plus
3. Rational Rose Enterprise Edition.

3. SYSTEM DESIGN DESCRIPTION
3.1 USE CASE SPECIFICATION - NEW USER LOGIN MODULE
Description
The user has to start the quiz through Online Quiz System by giving the
name, e-mail id, age and gender which will be added to database for future
verification.
Flow of Events
1. Basic flow:
The user has to provide the details needed by the quiz system to
login which includes name, e-mail id, age and gender.
2. Alternative flow:
42

None
Post-condition
The user has been registered.
3.2 USE CASE SPECIFICATION - LOGIN MODULE
Description
The user has to start the quiz through Online Quiz System by giving the
name and e-mail id which will be added to database for future verification.
Flow of Events
1. Basic flow:
The user has to provide the details needed by the quiz system to login which
includes name and e-mail id.


2. Alternative flow:
If the login information is invalid, then it displays a message saying provide
exact data.
Post-condition
The user now start the quiz.
3.3 CATEGORY MODULE
Description
The user has to choose the category which includes general knowledge,
verbal reasoning and computer science based on his areas of interest
Flow of Events
1. Basic flow:
Once the category is chosen, the system provides the questions with four options
each.
43

2. Alternative flow:
Appropriate category has to be chosen.
Post-condition
The questions are displayed accordingly.
3.4 USE CASE SPECIFICATION ANSWER MODULE
Description
The user has to answer the question according to the questions displayed,
based on the category chosen. The chosen answers are evaluated with the
database.



Flow of Events
1. Basic flow:
Based on the questions displayed, the user is required to answer by choosing
the options provided.
2. Alternative flow:
No negative marks for wrong answers.
Post-condition
The answers are evaluated.
3.5 USE CASE SPECIFICATION - DISPLAY SCORE MODULE
Description
44

A score card is displayed which shows the performance of the user who played
the quiz.
Flow of Events
1. Basic flow:
Answers are evaluated with the database and display the final score.
2. Alternative flow:
None
Post-condition
Score is displayed and can continue the game by choosing the category
otherwise quit.





4. USECASE ANALYSIS SOLUTION
4.1 USECASE DIAGRAM
45


4.2 CLASS DIAGRAM
4.2.1 NEW USER MODULE



4.2.2 LOGIN MODULE
Answer questions
New user register
Login
Participant
Display Score
Verify username & password
<<include>>
Choose category
Controller
46


4.2.3 CATEGORY MODULE

4.2.4 DISPLAY SCORE MODULE



47


4.3 SEQUENCE DIAGRAM
4.3.1 NEW USER MODULE

4.3.2 LOGIN MODULE
QuizParticipant Database Administrator
Enter the user details
Add details to the database
Details added
Successfully logined & start the quiz
48


4.3.3 CATEGORY MODULE

4.3.4 DISPLAY SCORE MODULE
QuizParticipant Admin Database
Enter name & email
Checks Validity
Invalid details
Reenter the details
Enter name & email
Checks Validity
Valid Information
Choose category
Participant Administrator Database
Choose the category
Get the questions
Provide the questions
Display questions
49




4.4 COLLABORATION DIAGRAM
4.4.1 NEW USER MODULE
Participant Administrator Database
Answer the questions
Evaluate the answers
Valid answers
Add credit
Display score
50


4.4.2 LOGIN MODULE






QuizPartici
pant
Database
Administra
tor
1: Enter the user details
4: Successfully logined & start the quiz
2: Add details to the database
3: Details added
QuizPartici
pant
Admin
Database
1: Enter name & email
5: Enter name & email
4: Reenter the details
8: Choose category
2: Checks Validity
6: Checks Validity
3: Invalid details
7: Valid Information
51

4.4.3 CATEGORY MODULE

4.4.4 DISPLAY SCORE MODULE







Participant Administra
tor
Database
1: Choose the category
4: Display questions
2: Get the questions
3: Provide the questions
Participant Administra
tor
Database
1: Answer the questions
5: Display score
2: Evaluate the answers
3: Valid answers
52

4.5 ACTIVITY DIAGRAM
4.5.1 NEW USER MODULE


4.5.2 LOGIN MODULE

Enter the
name,age,gender,email
Registration is
completed
Enter the username
and email
check validity
Renter the
information
false
Login to the
system
true
53



4.5.3 CATEGORY MODULE


4.5.4 DISPLAY SCORE MODULE
Choose
category
Display the
questions
54



5 IMPLEMENTATION
FORM 1:
Dim con As New ADODB.Connection
Dim rs As New ADODB.Recordset
Dim cms As New ADODB.Command
Private Sub Command1_Click()
con.ConnectionString = "provider=MSDAORA.1;user id=orait34;password=orait34;Data
source=oracle"
con.Open
Display questions based on
category chosen
Answer the
questions
Evaluate
answers
Add credit
correct
No credit added
Display Score
55

Set rs = New ADODB.Recordset
If (Text1.Text = "") Then
MsgBox ("enter ur name")
Else
rs.Open "select name from regi where no=" & Text1.Text, con
MsgBox ("registered")
Form1.Hide
Form2.Show
rs.Close
End If
con.Close
End Sub

Private Sub Command2_Click()
Text1.Text = ""
End Sub



FORM 2:
Private Sub Command1_Click()
Form2.Hide
Form3.Show
End Sub

56

FORM 3:
Private Sub Option3_Click()
Form3.Hide
Form4.Show
End Sub

FORM 4:
Private Sub Command2_Click()
Form4.Hide
Form5.Show
End Sub

Private Sub Option1_Click()
Form6.Label2.Caption = Option1.Caption
Form6.Label5.Caption = "correct"
Form6.Label9.Caption = 5
End Sub

Private Sub Option2_Click()
Form6.Label2.Caption = Option2.Caption
Form6.Label5.Caption = "wrong"
Form6.Label6.Caption = 0
End Sub

Private Sub Option3_Click()
57

Form6.Label2.Caption = Option3.Caption
Form6.Label5.Caption = "wrong"
Form6.Label10.Caption = 0
End Sub

FORM 5:
Private Sub Command1_Click()
Form5.Hide
Form6.Show
End Sub
Private Sub Option1_Click()
Form6.Label3.Caption = Option1.Caption
Form6.Label6.Caption = "wrong"
Form6.Label10.Caption = 0
End Sub
Private Sub Option2_Click()
Form6.Label3.Caption = Option2.Caption
Form6.Label6.Caption = "correct"
Form6.Label10.Caption = 5
End Sub


Private Sub Option3_Click()
Form6.Label3.Caption = Option3.Caption
Form6.Label6.Caption = "wrong"
58

Form6.Label10.Caption = 0
End Sub

FORM 6:
Private Sub Command1_Click()
Label8.Caption = Val(Label9.Caption) + Val(Label10.Caption)
If Val(Label8.Caption) >= 10 Then
MsgBox "Congratulations", vbInformation
Else
MsgBox ("Better Luck Next Time")
End If
End Sub

Private Sub Command2_Click()
End
End Sub








6.SCREEN SHOTS
59

Login Form:



60


Instruction Form:


Category Form :
61



Questions Form:

62




Result Form:
63



64


7.TESTING
TEST OBJ ECTI VE:
A process of executing a program with the intention to find error is called testing.
A good test is one that has high probability of finding errors. A test uncovers
undiscovered is said to be a successful test.
If testing is done successful, then it will uncover error in the software testing
demonstrates the software function appear to be working according to the specification
that behavioural and performance requirement appear to have met. Data collected as
testing is conducted to provide good indication of software reliability and some indication
of software quality as a hole.
TEST PLAN:
Before testing is to be done, test plan must be done in order to identify which testing
methods to implement for the project. The test cases must be identified.
STABI LI TY TEST:
Usability test is the test of effectiveness, efficiency and satisfaction. The stability
testing process includes all of software‟s components. Quick, iterative test can be user
identify 80-90 percent of the design problem.
Stability test can be conducted in a one-on-one fasion, as a demonstration or as a
„walk through‟ in which the users are taken through a set of samples scenarios.
Stability testing measures the case use as well as the degree of comfort and satisfaction
users with the software. Usability test cases begin with the identification if use cases that
can specify the target audience, tasks and test goals.
USER SATISFACTI ON TEST:
User satisfaction test is the process of quantifying the usability test with some
measurable attributes of the test, such a functionality cost or ease of use.
65

User satisfaction testing includes working with the users or client to find out what
attribute to be included in the test. It provides a periodic indication of divergence of
opinion about the design.








8. CONCLUSION

Thus the project “quiz system” helps in test the user for particular fields effectively when
compare to manual testing. The user details are stored in the database so that the retrieval
is made easier.







66





3. EMPLOYEE INFORMATION SYSTEM
CONTENTS
1. PROBLEM STATEMENT
2. PROBLEM DOMAIN GLOSSARY
3. SYSTEM DESIGN DESCRIPTION
4. USE CASE ANALYSIS SOLUTION
4.1 Use Case Diagram
4.2 Class Diagram
4.3 Sequence Diagram
4.4 Collaboration Diagram
5. IMPLEMENTATION
5.1 Code Generation
6. SCREEN SHOTS
7. TESTING
8. CONCLUSION
67








1. PROBLEM STATEMENT

This system is built for employee and manager. The employee can view their
salary and the manager can add a new employee, update employee details and calculate and
credit the salary.
The employee and manager can log into the system providing their respective user
names at login, if the entered input is incorrect an appropriate message is displayed.

2. PROBLEM DOMAIN GLOSSARY
2.1 Introduction
This system has been developed for automating the process of “Employee payroll
system” which takes lot of time if done manually, this system will hail the automation
which saves a lot of time when compared with manual system.
Action
1. Accept the user name and password
2. Add employee
3. Calculate salary
4. View employee details
5. Logout

2.2 Requirement Analysis
Hardware requirements:
68

 512 MB RAM
 Windows XP
 Intel processor
Software requirements:
 Java
 Oracle
 Rational rose Enterprise edition
3. SYSTEM DESIGN DESCRIPTION

3.1 Use Case Specification - Login
Brief Description:
This allows user to logs into Employee payroll System.
Flow of Events:
1. Basic Flow:
The actor should enter the user name and password to the system. The
system validates the entered name and password and logs the actor into the system
2. Alternative Flow:
Without the username and password user cannot enter the system
Precondition:
The username and the password are the precondition required for a user to log in
Post condition:
If use case was successful, the actor is now logged into the system. If not, the
system change is unchanged.

3.2 Use Case Specification – Add Employee
Brief Description:
This allows user to add the Employee profile.
Flow of Events:
69

1. Basic Flow:
 The actor should enter the employee name, address, Designation, Basic
Pay.
 The details will add in the database.
2. Alternative Flow:
The system returns to the beginning
Precondition:
Oracle database

Post condition:
If the use case was successful the employee name will be added into the
Employee database else Employee name is unchanged.

3.3 Use Case Specification – Delete Employee
Brief Description:
This allows user to Delete the Employee profile.
Flow of Events:
1. Basic Flow:
Verify whether the employee is resigned his/her job
2. Alternative Flow:
The names of the employee should not be deleted unless they found
resigned.
Precondition:
They found resigned
Post condition:
After delete the salary details of other employees viewed as usual

3.4 Use Case Specification – View Employee
Brief Description:
This allows user to view the Employee profile.
70

Flow of Events:
1. Basic Flow:
 The employee details like the employee name, address, Designation,
Salary details.
 The details is displayed.
2. Alternative Flow:
If the employee id and name is wrong informed to the user as invalid
detail.


Precondition:
The employee details like name, Id are the precondition checked to calculate
the Salary of each employee.
Post condition:
The employee HRA, DA,PF, Net salary salary are the next required condition
to calculate the Gross salary. This must be updated in the database.














71














4. USE CASE ANALYSIS SOLUTION
4.1 Use Case Diagram

4.2. Class Diagram
72



4.3 Sequence Diagram


4.4 Collaboration Diagram
73




5.IMPLEMENTATION
import java.io.*;
import java.awt.*;
import javax.swing.*;
import java.awt.event.*;
import java.sql.*;
import java.util.*;
Form 1:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
{
String user=jTextField1.getText();
String pwd= new String (jPasswordField1.getPassword());
if (user.equals("e") && pwd.equals("d")) {
74

JOptionPane.showMessageDialog(jOptionPane1," Login Successfully.");
new epayUI1().setVisible(true);
setVisible(false);
}
else
{
JOptionPane.showMessageDialog(jOptionPane1,"Wrong User Name or Password");
} }
Form 2:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value1=jTextField1.getText();
String value2=jTextField2.getText();
String value3=jTextField3.getText();
String value4=jTextField4.getText();
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45"))
{
System.out.println(value1+value2+value3+value4);
PreparedStatement st=con.prepareStatement("insert into
employee45(eid,ename,eadd,salary) values(?,?,?,?)");
st.setString(1,value1);
st.setString(2,value2);
st.setString(3,value3);
st.setString(4,value4);
st.executeUpdate();
Component jOptionPane2;
75

Component jOptionPane1 = null;
JOptionPane.showMessageDialog(jOptionPane1,"Inserted");
}
}
catch( ClassNotFoundException | SQLException e){
Component jOptionPane2;
Component jOptionPane1 = null;
JOptionPane.showMessageDialog(jOptionPane1,"not inserted");
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
new epayUI2().setVisible(true);
setVisible(false);
}
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText("");
}
Form 3:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value1=jTextField1.getText();
try {
Class.forName("oracle.jdbc.driver.OracleDriver");
76

try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
PreparedStatement st=con.prepareStatement("DELETE FROM employee45
WHERE eid = ?");
st.setString(1,value1);
st.executeUpdate();
}
}
catch( ClassNotFoundException | SQLException exp3)
{
}
Form 4 :
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value=jTextField1.getText();
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
PreparedStatement st=con.prepareStatement("select * from employee45 where
eid=?");
st.setString(1,value);
ResultSet res=st.executeQuery();
res.next();
jTextField1.setText(Integer.toString(res.getInt(1)));
jTextField2.setText(res.getString(2));
jTextField3.setText(res.getString(3));
jTextField4.setText(Integer.toString(res.getInt(4)));
}
77

}
catch( ClassNotFoundException | SQLException e)
{
} }

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
String value1=jTextField1.getText();
String value2=jTextField2.getText();
String value3=jTextField3.getText();
String value4=jTextField4.getText();
Statement st=con.createStatement();
int executeUpdate = st.executeUpdate("update employee45 set ename='"+value2+"',
eadd='"+value3+"', salary='"+value4+"' where eid='"+value1+"'");
} }
catch( ClassNotFoundException | SQLException e){ }
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
new epayUI2().setVisible(true);
setVisible(false);
}
Form 5
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
78

String value=jTextField1.getText();
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
PreparedStatement st=con.prepareStatement("select * from employee45 where
eid=?");
st.setString(1,value);
ResultSet res=st.executeQuery();
res.next();
jTextField1.setText(Integer.toString(res.getInt(1)));
jTextField2.setText(res.getString(2));
jTextField3.setText(res.getString(3));
jTextField4.setText(Integer.toString(res.getInt(4)));
} }
catch( ClassNotFoundException | SQLException e) { }
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
new epayUI2().setVisible(true);
setVisible(false); }

private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText(""); }
Form 6 :
79

System.exit(0);









































6.SCREEN SHOTS

Form1 :

80


Form 2

Reset :
81



Form 3 :

82

Form 4:



83



Form 5:

84















85

7.TESTING
TEST OBJ ECTI VE:
A process of executing a program with the intention to find error is called testing.
A good test is one that has high probability of finding errors. A test uncovers
undiscovered is said to be a successful test.
If testing is done successful, then it will uncover error in the software testing
demonstrates the software function appear to be working according to the specification
that behavioral and performance requirement appear to have met. Data collected as
testing is conducted to provide good indication of software reliability and some indication
of software quality as a hole.
TEST PLAN:
Before testing is to be done, test plan must be done in order to identify which testing
methods to implement for the project. The test cases must be identified.
STABI LI TY TEST:
Usability test is the test of effectiveness, efficiency and satisfaction. The stability
testing process includes all of software‟s components. Quick, iterative test can be user
identify 80-90 percent of the design problem.
Stability test can be conducted in a one-on-one fasion, as a demonstration or as a
„walk through‟ in which the users are taken through a set of samples scenarios.
Stability testing measures the case use as well as the degree of comfort and satisfaction
users with the software. Usability test cases begin with the identification if use cases that
can specify the target audience, tasks and test goals.
USER SATISFACTI ON TEST:
User satisfaction test is the process of quantifying the usability test with some
measurable attributes of the test, such a functionality cost or ease of use.
86

User satisfaction testing includes working with the users or client to find out what
attribute to be included in the test. It provides a periodic indication of divergence of
opinion about the design.


















8.CONCLUSION

Thus the project for employee payroll analysis has been developed with the help of
Java. In this project the employee can view his salary and the manager can add a new
employee, Update employee details and calculate and credit the salary.







87






4. INVENTORY CONTROL SYSTEM

CONTENTS

1. PROBLEM STATEMENT
2. PROBLEM DOMAIN GLOSSARY
3. SYSTEM DESIGN DESCRIPTION
4. USE CASE ANALYSIS SOLUTION
4.1 Use Case Diagram
4.2 Class Diagram
4.3 Sequence Diagram
4.4 Collaboration Diagram
4.5 State/Activity Diagram
5. IMPLEMENTATION
5.1 Code Generation
88

6. SCREEN SHOTS
7. TESTING
8. CONCLUSION


89

1. PROBLEM STATEMENT

The project entitled Inventory System has a drastic change to that of the
older version of inventory system, customer feel inconvenient with the transaction
method as it was in the hands of the customers.
In our inventory system , the above problem is overcome here, the
purchase are done in person by the customer thus makes the customers feel safe and
secure.
Thus the application of our system helps the customer in checking the
product availability and amount by validating the password therefore this inventory
system is more user friendly.
2.PROBLEM DOMAIN GLOSSARY
2.1 Introduction
Inventory system is developed for the benefits of the customers. The system must
provide facilities for the customer to Check available products and the price details. The
display design must be easy to understand.
Action
1. Accept the user name and password
2. Add new product
3. View Product details
4. Logout
2.2 Requirement Analysis
Hardware requirements:
 512 MB RAM
 Windows XP
 Intel processor
Software requirements:
 Java Swing
90

 Oracle
 Rational rose Enterprise edition

3. SYSTEM DESIGN DESCRIPTION
3.1 1 Use Case Specification - Login
Brief Description:
This allows user to logs into Inventory System.
Flow of Events:
3. Basic Flow:
The actor should enter the user name and password to the system. The
system validates the entered name and password and logs the actor into the system
4. Alternative Flow:
Without the username and password user cannot enter the system
Precondition:
The username and the password are the precondition required for a user to
log in
Post condition:
If use case was successful, the actor is now logged into the system. If not, the
system change is unchanged.
3.2 USE CASE SPECIFICATION – ADD NEW PRODUCT
Brief Description:
This allows user to add new products.
Flow of Events:
91

1.Basic Flow:
 The actor should enter the product name, id, price,Reorder level.
 The details will add in the database.
2. Alternative Flow:
The system returns to the beginning
Precondition:
Oracle database
Post condition:
If the use case was successful the employee name will be added into the
Product database.
3.4 USE CASE SPECIFICATION – VIEW PRODUCT DETAILS
Brief Description:
This allows user to view the Product Details.
Flow of Events:
1Basic Flow:
 The employee details like the Product name, id, Quantity, Price.
 The details is displayed.
2. Alternative Flow:
If the Product id and name is wrong informed to the user as invalid detail
Precondition:
The Product details like name, Id are the precondition checked to check the
availability
Post condition:
None
92






4. Use Case Analysis Solution
4.1 USECASE DIAGRAM


93









4.2 CLASS DIAGRAM


4.3 SEQUENCE DIAGRAM


94




4.4 COLLABORATION DIAGRAM



95















5.IMPLEMENTATION
import java.io.*;
import java.awt.*;
96

import javax.swing.*;
import java.awt.event.*;
import java.sql.*;
import java.util.*;
Form1
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
{
String user=jTextField1.getText();
String pwd= new String (jPasswordField1.getPassword());
if (user.equals("e") && pwd.equals("d")) {
JOptionPane.showMessageDialog(jOptionPane1," Login Successfully.");
new epayUI1().setVisible(true);
setVisible(false);
}
else
{
JOptionPane.showMessageDialog(jOptionPane1,"Wrong User Name or Password");
} }

Form2:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value1=jTextField1.getText();
String value2=jTextField2.getText();
String value3=jTextField3.getText();
String value4=jTextField4.getText();
97

try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45"))
{
System.out.println(value1+value2+value3+value4);
PreparedStatement st=con.prepareStatement("insert into
product45(pid,pname,pcost,availability) values(?,?,?,?)");
st.setString(1,value1);
st.setString(2,value2);
st.setString(3,value3);
st.setString(4,value4);
st.executeUpdate();
Component jOptionPane2;
Component jOptionPane1 = null;
JOptionPane.showMessageDialog(jOptionPane1,"Data Successfully
Inserted");
}
}
catch( ClassNotFoundException | SQLException e){
Component jOptionPane2;
Component jOptionPane1 = null;
JOptionPane.showMessageDialog(jOptionPane1,"Data Not inserted");
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
98

new epayUI2().setVisible(true);
setVisible(false);
}
private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText("");
}

Form 3:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value1=jTextField1.getText();
try {
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
PreparedStatement st=con.prepareStatement("DELETE FROM Product45
WHERE pid = ?");
st.setString(1,value1);
st.executeUpdate();
}
}
catch( ClassNotFoundException | SQLException exp3)
{ }
99

Form 4 :
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value=jTextField1.getText();
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
PreparedStatement st=con.prepareStatement("select * from product45 where
pid=?");
st.setString(1,value);
ResultSet res=st.executeQuery();
res.next();
jTextField1.setText(Integer.toString(res.getInt(1)));
jTextField2.setText(res.getString(2));
jTextField3.setText(res.getString(3));
jTextField4.setText(Integer.toString(res.getInt(4)));
}
}
catch( ClassNotFoundException | SQLException e)
{
}
}
private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
100

try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
String value1=jTextField1.getText();
String value2=jTextField2.getText();
String value3=jTextField3.getText();
String value4=jTextField4.getText();
Statement st=con.createStatement();
int executeUpdate = st.executeUpdate("update product45 set pname='"+value2+"',
pcost='"+value3+"', available='"+value4+"' where pid='"+value1+"'");
} }
catch( ClassNotFoundException | SQLException e){ }
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
new epayUI2().setVisible(true);
setVisible(false);
}

Form 5:
private void jButton1ActionPerformed(java.awt.event.ActionEvent evt) {
String value=jTextField1.getText();
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
try (Connection con =
DriverManager.getConnection("jdbc:oracle:thin:@10.20.9.4:1521:oracle","orait45","orai
t45")) {
101

PreparedStatement st=con.prepareStatement("select * from product45 where
pid=?");
st.setString(1,value);
ResultSet res=st.executeQuery();
res.next();
jTextField1.setText(Integer.toString(res.getInt(1)));
jTextField2.setText(res.getString(2));
jTextField3.setText(res.getString(3));
jTextField4.setText(Integer.toString(res.getInt(4)));
}
}
catch( ClassNotFoundException | SQLException e) { }
}

private void jButton2ActionPerformed(java.awt.event.ActionEvent evt) {
new epayUI2().setVisible(true);
setVisible(false); }

private void jButton3ActionPerformed(java.awt.event.ActionEvent evt) {
jTextField1.setText("");
jTextField2.setText("");
jTextField3.setText("");
jTextField4.setText("");
}

Form 6 :
102

System.exit(0);






6.SCREEN SHOTS
Form 1

103

Form2

Form 3
104


Form 4

105

Form 5













106



7. TESTING
TEST OBJ ECTI VE:
A process of executing a program with the intention to find error is called testing.
A good test is one that has high probability of finding errors. A test uncovers
undiscovered is said to be a successful test.
If testing is done successful, then it will uncover error in the software testing
demonstrates the software function appear to be working according to the specification
that behavioural and performance requirement appear to have met. Data collected as
testing is conducted to provide good indication of software reliability and some indication
of software quality as a hole.
TEST PLAN:
Before testing is to be done, test plan must be done in order to identify which testing
methods to implement for the project. The test cases must be identified.
STABI LI TY TEST:
Usability test is the test of effectiveness, efficiency and satisfaction. The stability
testing process includes all of software‟s components. Quick, iterative test can be user
identify 80-90 percent of the design problem.
Stability test can be conducted in a one-on-one fasion, as a demonstration or as a
„walk through‟ in which the users are taken through a set of samples scenarios.
Stability testing measures the case use as well as the degree of comfort and satisfaction
users with the software. Usability test cases begin with the identification if use cases that
can specify the target audience, tasks and test goals.
USER SATISFACTI ON TEST:
107

User satisfaction test is the process of quantifying the usability test with some
measurable attributes of the test, such a functionality cost or ease of use.
User satisfaction testing includes working with the users or client to find out what
attribute to be included in the test. It provides a periodic indication of divergence of
opinion about the design.













8.CONCLUSION


Thus the project for Inventory system analysis has been developed with the help of
Java. In this project the customer can view the Product availability, Price details and the
Admin can add a new Product, Update Product details.