Software Engineering record

7/31/2019 Software Engineering record

1/141

TAMILNADU COLLEGE OF ENGINEERING

PALANISAME RAVI NAGAR, KARUMATHAMPATTI,

COIMBATORE -641659

LABORATORY RECORD

NAME _______________________

CLASS _______________________

BRANCH _______________________

SUBJECT _______________________

UNIVERSITY REGISTER No. ROLL No.

CERTIFIED THAT THIS IS BONAFIDE RECORD OF WORK DONE BY THE ABOVE STUDENT

LABORATORY DURING THE YEAR / SEMESTER

SIGNATURE OF LAB - INCHARGE SIGNATURE OF HEAD OF DEPT

SUBMITTED FOR THE PRACTICAL EXAMINATION HELD ON _________________________

EXTERNAL EXAMINER INTERNAL EXAMINER


2/141

INDEX

S.No. DATE Name of Experiment Page No. Marks Signature of

Staff


3/141

S.No. DATE Name of Experiment Page No. Marks Signature of

Staff


4/141

Ex. No:

Date :

PAYROLL PROCESSING SYSTEM

PROBLEM STATEMENT:

The Payroll Processing system is mainly designed to replace the manual task of maintaining

employee details and calculating the salary of every employee. This increases the Speed and accuracy of

salary calculation. The Payroll system aims to store all the Details of Employees. A backend is

maintained to store the Name, Employee id, Designation and Basic Salary. Using it Net Salary (The

Sum of Basic Pay, HRA, DA and PF) is calculated. Now the Employee can enter their Employee id and

get to know their net salary. Then they can also generate the Pay Slip by using appropriate options.

SOFTWARE REQUIREMENT SPECIFICATION:

Purpose:

The Purpose of this Project is to replace the Highly Tedious manual Computation of the Net

Pay of Employees by Computerization of Calculation of the Net Salary.

Document conventions:

Emp-ID: The Unique ID is provided to each employee so that each one can access his own Details

Securely.

Basic Pay: The Basic Pay of Employee is provided by the Administrator based on his designation.

HRA, DA, and PF: All the incentives are calculated based on the Basic pay using certain Criteria.

Net pay: The Net Pay of the Employee is Sum of the Basic pay and incentives.

.

Intended Audience:

TheIntendedAudience of this Project is the Accountant of the Firm as

Administrator and employees of the firm as Users.

Project Scope:

The Scope of this Project is to mainly reduce manpower, cost of manipulation and increase

efficiency.


5/141

OVERALL DESCRIPTION:

Product Perspective:

The perspective of this Project is to replace large sized Log Books by Digital Computers and

Details safer in a Hard Disk.

User Classes:

The User Classes are,

Employees who have only the Rights to view and Print the Pay Slip.

Accountant as admin who can view and edit the Calculation System.

Operating Environment:

Hardware Environment:

Server: Client:

RAM: 1 GB or more RAM: 256 MB or more

HDD: 160 GB or more HDD: 40 GB or more

Software Environment:

OS: Windows Server 2003 or higher OS: Windows XP or Higher

Design and Implementation Constraints:

The Design Constraints of the Project are

The GUI Environment may be incompatible with Client Side.

The User might not be able to understand certain functions due to Faulty Design.

Assumptions and Dependencies:

The Assumption of the Project is that the Employees does notdisclose to anybody about his

Emp-id and Password.

The Project Depends mainly upon two Third Party Software

MS-ACCESS as DBMS tool.

VB 6.0 for the Front End Design of Project


6/141

User Interface:

The Project is completely GUI Based hence the user can easily use the Software by using

GUI Based Command Buttons.

Software Interface:

The Software Interface is Between Visual Basic 6.0 which is used as front end application

and is connected to MS-ACCESS Database which acts as Backend to Store the Employee

Information.

System Features:

The Features provided by the System are:

New Employee Details can be registered in the Database.

The Net Pay of Employees can be manipulated.

The Pay slip of Employee can be generated and it can be printed.

Non-Functional Requirements:

Performance Requirements:

The Employees may access the Data at any time and he can be able to generate the Pay Slip and

his details will be updated in the database whenever his informations are edited.

Security Requirements:

The Employee need not know about other employee details. Hence Unique ID & Password is

provided for each employee Security.

The Administrator can access all account details of employees and he is only person who can

edit the Employee Details.


7/141

DATA MODELING:

The project can be explained diagrammatically using the following diagrams:

Use Case Diagram

Class Diagram

Sequence Diagram

Collaboration Diagram

State-transition Diagram

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.

Actors:

An actor is a role that a user plays with respect to the system. The actors are:

Employee

Administrator

Database

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.

Employee

Payment Details

Admin

Company

Database

Employee Details

Authentication

Payment Calculation
http://en.wikipedia.org/wiki/Unified_Modeling_Languagehttp://en.wikipedia.org/wiki/Use-case_analysishttp://en.wikipedia.org/wiki/Actor_(UML)http://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Use_casehttp://en.wikipedia.org/wiki/Actor_(UML)http://en.wikipedia.org/wiki/Use-case_analysishttp://en.wikipedia.org/wiki/Unified_Modeling_Language


8/141

1. Use Case Name: EMPLOYEE DETAILS

Description:

The Employee details like Name, ID, Designation, Age, Address, Date of Birth, Mail-ID are

maintained by the Administrator for both the permanent and temporary employees.

Steps:

Enter the entire details of the Employee

Press the Add Button to add the details in the Database.

Press the view Button to view the details in the Database.

Press the search Button to search the details of the Employee.

Press the Delete Button to delete the details in the Database.

Press the Cancel Button to Quit.

2. Use Case Name: PAYMENT CALCULATION

Description:

The Basic Salary for both permanent and temporary employee and details are entered by the

Administrator with reference to the ID of the employee.

Steps:

Enter the ID of the employee.

Enter the Salary for Each Employee.

Calculate DA, HRA, IT, PF, Net Pay, Gross Pay for Employees.

Press the Add button to add the details in the Database.

Press the View button to view the details in the Database.

Press the Delete button to delete the details in the Database.

Press the Cancel button to Quit.

3. Use Case Name: PAYMENT DETAILS

Description: The Employee can view their Payment details by giving their ID.

Steps:

Enter the ID.

Press the Show Button to view the Details.

Press the Cancel Button to Quit.


9/141

Class Diagram:

A Class diagram describes the types of objects in the System and the various kinds of static relationships

that exist among them.

Description: The classes used in this project are

Company Payroll

Employee Details

Temporary Employee Details

Permanent Employee Details

Payment Details

Salary Calculation for Temporary Employee

Salary Calculation for Permanent Employee


10/141

Sequence Diagram:

A Sequence Diagram is a kind of interaction diagram in which an object is shown as a box at a

top of a dashed vertical line. This vertical line is called as objects lifeline.

The lifeline represents the objects life during the interaction. Object deletion is shown with a

large X. Objects can be destroyed by another message.

Description:

The various scenarios of the sequence diagram used in this project are

Employee

Administrator

Database

Employee AdministratorDatabase

1: Get the Information of the employee

2: Validation Checking

3: Valid

4: Send Acknowledge

5: Store Employee Details

6: Store Payment Details

7: Getting the payment

8: Checking the payment Details

9: Giving the payment


11/141

Collaboration Diagram:

In a Collaboration diagram, objects are shown as icons. As on a sequence diagram, arrow

indicate the message sent within the given Use Case. Numbering the messages indicates the sequence.

Description:

This diagram contains the group of classes created, interfaces and the elements that work

together to provide the overall behavior of the project. It also describes the relationship between eachclasses and how they relate with each other.

Employee

Administrator

Database

3: Valid

1: Get the Information of the employee7: Getting the payment

9: Giving the payment

2: Validation Checking5: Store Employee Details6: Store Payment Details

8: Checking the payment Details

4: Send Acknowledge


12/141

State-transition Diagram:

The state transition diagram(STD) indicates how the system behaves as a consequence of

external events. To accomplish this, the STD represents the various modes of behavior (called states) of

the system and the manner in which transitions are made from state to state. The STD serves as the basisfor behavioral modeling. A state transition diagram indicates how the system moves from state to state.

The state transition diagram represents the behavior of a system by depicting its states and the events

that cause the system to change state.

Description:

A state transition diagram indicates how the system moves from state to state. The state transition

diagram represents the behavior of a system by depicting its states and the events that cause the system

to change state.

start

Payroll

Calculation

Payslip

Gentration

Registratio

n

Canceled

initiate

Login

valid

invalid

Finish

cancel

Enter details

Complete

cancel

cancel


13/141

PROJECT IMPLEMENTATION:

Coding:

Form1:

Dim db As Database

Dim rs As Recordset

Private Sub Command1_Click()

Dim i

Dim n

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n

If rs.EOF = True Then

MsgBox "Invalide Username &Pasword, register ur details"

GoTo a

End If

If Text1.Text = rs("ename") And Text2.Text = rs("eid") Then

Me.Hide

Form2.Show

Form2.Text1.Text = rs("ename")

Form2.Text2.Text = rs("eid")

Form2.Text3.Text = rs("edesign")

Form2.Text4.Text = rs("edoj")

Else

rs.MoveNext

End If

a:

Next

End Sub



14/141

Text1.Text = ""

Text2.Text = ""

End Sub


End

End Sub


Form3.Show

End Sub

Private Sub Form_Load()

Set db = OpenDatabase("C:\Documents and Settings\Administrator\My

Documents\vbexp\payroll\emp1.mdb")

Set rs = db.OpenRecordset("emp1")

End Sub

Form2:

Dim db As Database

Dim rs As Recordset


Me.Hide

Form1.Show

End Sub


Text8.Text = Val(Text5.Text) + Val(Text6.Text) - Val(Text7.Text)

End Sub


rs.AddNew

rs("ename") = Text1.Text

rs("eid") = Text2.Text

rs("edesign") = Text3.Text

rs("edoj") = Text4.Text


15/141

rs("bp") = Val(Text6.Text)

rs("hr") = Val(Text7.Text)

rs("pf") = Val(Text8.Text)

rs("np") = Val(Text9.Text)

rs.Update

MsgBox ("updated successfully")

End Sub


Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Text7.Text = ""

Text8.Text = ""

End Sub


End

End Sub


Me.Hide

Form4.Show

Form4.Text1.Text = rs("ename")

Form4.Text2.Text = rs("eid")

Form4.Text3.Text = rs("edesign")

Form4.Text4.Text = rs("np")


16/141

Form4.Text5.Text = Date

Form4.Text6.Text = Time

End Sub


Dim i

Dim n

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n


MsgBox ("Employee details not in database")

GoTo a

End If

If Text9.Text = rs("eid") Then

Text1.Text = rs("ename")

Text2.Text = rs("eid")

Text3.Text = rs("edesign")

Text4.Text = rs("edoj")

Text5.Text = rs("bp")

Text6.Text = rs("hr")

Text7.Text = rs("pf")

Text8.Text = rs("np")

Else

rs.MoveNext

End If

a:

Next

End Sub


17/141



Documents\vbexp\payroll\Employee.mdb")

Set rs = db.OpenRecordset("Employee")

End Sub

Form3:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n

Dim f As Integer

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n


rs.AddNew

rs("ename") = Text1.Text

rs("eid") = Text2.Text

rs("edesign") = Text3.Text

rs("edoj") = Text4.Text

rs.Update

MsgBox ("updated sucessfully")

GoTo a

End If

If Text1.Text = rs("ename") And Text2.Text = rs("eid") Or Text3.Text = rs("edesign") Or Text4.Text =

rs("edoj") Then

f = 1

Else

rs.MoveNext


18/141

End If

a:

Next

If f = 1 Then

MsgBox "ur details are already registered"

End If

End Sub

Private Sub Label6_Click()

End Sub


Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

End Sub


End

End Sub


Me.Hide

Form1.Show

End Sub



Documents\vbexp\payroll\emp1.mdb")

Set rs = db.OpenRecordset("emp1")

End Sub


19/141

Form4:


Me.Hide

Form1.Show

End Sub


rptpayroll.Show

End Sub


20/141

PROJECT EXECUTION:


21/141


22/141


23/141

RESULT:

Thus the Problem is analyzed, designed and implemented using Rational Rose/Visual Basic/MS

Access. The Result of the project is evaluated by performing unit testing, Integration testing and

Acceptance testing.


24/141

Ex. No:

Date :

ONLINE SHOPPING

PROBLEM STATEMENT:

The project is a simple online shopping portal. The System will allow more than one categories

to be selected and different brands under the segment. The System will allow the customer to make the

payment.

The System would be easy to use and hence making the shopping experience pleasant for the

users.


Purpose:

The main objective of this document is to illustrate the requirements of the project online

shopping system.

To develop an easy to use interface where users can search for products and order the products.

Provide interactive interface through which a user can interact with different areas of application

easily.


Administrator: A log-id representing a user with administrator privileges to the software.

User: A general log-in id assigned to the customers.

Client: Intended user for the software.

MS Access: Back end connection to the application used to access information.

Visual Basic: VB 6.0 is used for designing front end of the software.

Use-Case Diagram: A broad level diagram of the project showing a basic overview.

Data-Flow Diagram: It shows the data flows between the entities.

Unique-key: Used to differentiate entities in a DB.


25/141

Product Characteristics and Specific Requirements:

This System contains the following types of actors:

Customers:

Simplicity

Payment possibilities

End to end functions.

Simple interface for terms and conditions.

Print out of the bill.

Administrator:

Track usage of services.

Ensure simplicity and correctness correspondence of service purchased.

Find approaches to simplify transactions.

Ensure original information is perfectly localized to remove any duplication.

Project Success Criteria:

Our main goal is to complete this project within allotted deadline and also within the budget

allotted.

It is necessary to satisfy the functional and non-functional requirements of the software.



Online shopping project is aimed towards the vendors who want to reach out to the maximum

cross-section of customers.

The Project envisages bridging the gap between the seller and the customer.

Online shopping should be user friendly, quick to learn and reliable software for the above

purpose. This is intended to be a standalone product and should not depend on the availability of

other software.


26/141

Product Features:

There are two different users who will be using this product.

1. Administrator, who can manage the online shopping.

2. Customers, who can use the system.

The features that are available to the administrator of the online shopping system are

o Can access all the accounts of the customers.

o Add the product and information on the DB.

o Can check the availability of the product.

o Can view the payment history of the customers.

The features available to the customers are,

o Can view the different categories of items in the shop.

o Can search a particular item on the shop.

o Facility for online payment by credit card.

o Can own and account in the shop.

User Classes and Characteristics:

The user includes:

Customers who will be using the above features by accessing the online shopping.

Sellers or Vendors will be acting as the controller and he will have all the privileges of an

administrator.


o The product is developed using Visual Basic 6.0. The back end DB connection is done by MS

Access.

o The product is accomplished with log-in facility so that specific function is available to specific

users.


27/141


Assumptions:

o The details related to the product, payment and service transaction provided manually.

o Administrator is created in the system already.

o Roles and tasks are predefined.

o Registration steps will be known by the user.

Dependencies:

o User should get registered one to get the full utilization of the product.

o The registered user only will be getting the updates.

SYSTEM FEATURES:

Database Storage:

Proposed Database is intended to store, retrieve, update and manipulate information related to

shopping which include

o Customer information

o Items and product information

o Payment details

Functional Requirements:

This section gives the list of Functional requirements which are applicable to the online shopping

system.

GUI:

It describes the graphical user interface of the software. It includes the following forms to

illustrate user interface features.

Log-in and Registration

New Customer Registration

Online Shopping Form

Payment Form


28/141

Description:

The user interface must be customizable by the admin.

Criticality:

The issue is essential to overall system. All the modules provided with the software must fit into

this GUI and accomplish to the standard defined.

Technical Issue:

In order to satisfy this requirement the design should be simple and all the different interfaces

should follow a standard template.

Dependencies with other requirements:

All user interfaces should be able to interact with the user management module and a part of the

interface dedicated to log-in and log-out module.



System can withstand even though many number of customers request the desired service.

Access is given to only valid customers.

Safety Requirements:

The database may get crashed at any certain time due to virus or operating system failure.

The product is of 24*7 availability, so there should be power back up for server which provides

the information.


The online payment process should be highly secured.

Sensitive data is protected from unwanted access by users appropriate technology and

implementing strict user-access criteria.

Hardware Interfaces:

Server Side:

Operating System: Windows Server 2003/ Windows Server 2008.

Processor: Intel Pentium Dual-Core 2.8 GHZ or higher.

RAM: 1GB DDR2 or more.

HDD: 160GB or more.


29/141

Client Side:

Operating System: Windows XP or more.

Processor: Intel Pentium IV 2.4 GHZ or higher.

RAM: 256MB DDR2 or more.

HDD:40GB or more.

Software Interfaces:

Database: MS Access 2007

Application: Visual Basic 6.0

Web Server: Internet Information Service (IIS)


30/141

Make purchase

Customer Seller

View Items

Check out

Credit Paymentservice

Client Register

Database

DATA MODELING:


Use Case Diagram

Class Diagram

Sequence Diagram

Collaboration Diagram State-transition Diagram

USE CASE DIAGRAM





ACTORS:


Customer

Seller

Database

Credit payment service

USE CASES:




31/141

1. Use Case Name: View Items

Description:

Web Customer actor uses some web site to make purchases online. Top level use cases are View

Items, Make Purchase and Client Register. View Items use case could be used by customer as top level

use case if customer only wants to find and see some products. This use case could also be used as a part

of Make Purchase use case.

View Items use case is extended by several optional use cases

o Customer may search for items,

o Browse catalog,

o view items recommended for him/her,

o Add items to shopping cart or wish list.

All these use cases are extending use cases because they provide some optional functions allowing

customer to find item.

2. Use Case Name: Check out

Description:

Checkout use case includes several required uses cases. Web customer should be authenticated. It could

be done through

o user login page,

o user authentication cookie ("Remember me") or

o Single Sign-On (SSO).

Web site authentication service is used in all these use cases, while SSO also requires participation ofexternal identity provider.

3. Use Case Name: Client Register

Description:

Client Register use case allows customer to register on the web site, for example to get some

coupons or be invited to private sales.

Steps:

o Enter the Name and Password for the customer.

o Enter the contact number and address for the customer.

o Press the Update button to update the details in the database.

4. Use Case Name: Make Purchase

Description:

This use-case includes the View items use-case and Check out use-case.


32/141

Steps:

o Add the items into the Shopping cart.

o Provide the Credit card number and password.

o Press make payment button to pay money.

Class Diagram:




Login

Shopping

Payment

New Registration


33/141

Customer Online shop Database

Login Verifcation

Search Inventory

Search results

View Item description

Add to shopping cart

Payment

Confirmation

Processing

Acknowledge

Checkout

SEQUENCE DIAGRAM:

A Sequence diagram depicts the sequence of actions that occur in a system. The invocationofmethods in each object, and the order in which the invocation occurs is captured in a Sequence diagram.This makes the Sequence diagram a very useful tool to easily representthe dynamic behavior of asystem.

A Sequence diagram is two-dimensionalin nature. On the horizontal axis, it shows thelife of theobject that it represents, while on the vertical axis, it shows the sequence of the creation or invocation ofthese objects. Because it uses class name and object name references, the Sequence diagram is very useful in elaborating and detailing the dynamic design.

Description:


Customer

Online Shop

DatabaseIt depicts the high level sequence diagram for online shopping. Online customer can search items , viewdescription of a selected item, add item to shopping cart, do checkout.


34/141

Web

CustomerOnline Shop

Inventory

Items

Shopping

cardOrder

Online

shopping

9: Processing DB

1: find items()

8: delivery

4: view description()

2: search() 3: [order complete] update_inventory()

5: make_payment()

6: get items()

7: make_order()

COLLABORATION DIAGRAM:

Description:

A Collaboration diagram is very similar to a Sequence diagram in the purpose it achieves; in

other words, it shows the dynamic interaction of the objects in a system. A distinguishing feature of a

Collaboration diagram is that it shows the objects and their association with other objects in the system

apart from how they interact with each other. The association between objects is not represented in a

Sequence diagram.

A Collaboration diagram is easily represented by modeling objects in a system and representing

the associations between the objects as links. The interaction between the objects is denoted by arrows.

To identify the sequence of invocation of these objects, a number is placed next to each of these arrows.

In this collaboration diagram, the objects are represented as rectangle, the actors are stick figures.

Whereas the sequence diagram illustrates the object and actor interaction overtime, the collaboration

diagram shows the object and actor interaction without reference to time.


35/141




the system and the manner in which transitions are made from state to state. The STD serves as the basis

for behavioral modeling. A state transition diagram indicates how the system moves from state to state. The state transition diagram represents the behavior of a system by depicting its states and the events


Description:



to change state.

Start

Login

Shopping

Payment

Finish

valid

Registratio

n

Canceled

Enter details

cancel

complete

cancel

invalid

invalid

initiate


36/141


Coding:

Form1:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n

If rs.EOF Then

MsgBox ("no records found")

GoTo a

End If

If (Text1.Text = rs("userid") And Text2.Text = rs("password")) Then

Me.Hide

Form2.Show

Else

rs.MoveNext

End If

a:

Next

End Sub


Me.Hide

Form3.Show

End Sub


37/141


End

End Sub


Text1.Text = ""

Text2.Text = ""

End Sub


Set db = OpenDatabase("D:\vbexp\EXP2\login2.mdb")

Set rs = db.OpenRecordset("login2")

End Sub

Form2:

Dim db As Database

Dim rs As Recordset

Private Sub CASH_Click()

MsgBox ("please handover your payment during door delivery")

MsgBox ("Thanks for your visit to our enterprise please come again")

End Sub

Private Sub Combo1_Change()

If Combo1.Text = "TITAN" Then

Label7.Caption = "599"

End If

If Combo1.Text = "SONATA" Then


End If


38/141

If Combo1.Text = "TITAN RAGA" Then


End If

If Combo1.Text = "QUARTZ" Then


End If

If Combo1.Text = "CASIO" Then


End If

End Sub


If Combo2.Text = "HAMAM" Then


End If

If Combo2.Caption = "LUX" Then


End If

If Combo2.Caption = "MARGO" Then


End If

If Combo2.Caption = "POWER" Then


End If

If Combo2.Text = "J&J" Then


End If

If Combo2.Caption = "SKINCARE" Then


End If


39/141

If Combo2.Caption = "CINTOL" Then


End If

End Sub


If Combo3.Text = "5-STAR" Then


End If

If Combo3.Text = "DIARY MILK" Then


End If

If Combo3.Text = "MUNCH" Then


End If

If Combo3.Text = "BARONE" Then


End If

If Combo3.Text = "FRUIT&NUT" Then


End If

End Sub


If Combo4.Text = "TIGER" Then


End If

If Combo4.Text = "MILKBIKES" Then


End If


40/141

If Combo4.Text = "VITA" Then

Label14.Caption "19"

End If

If Combo4.Text = "BOURBON" Then


End If

End Sub


If Combo5.Text = "VVDGOLD" Then

If Val(Text5.Text) = "1" Then


End If

If Val(Text5.Text) = "1.5" Then


End If



End If

End If

If Combo5.Text = "PARACHUTE" Then



End If



End If



End If


41/141

End If

If Combo5.Text = "MEERA" Then



End If



End If



End If

End If

If Combo5.Text = "VATIKA" Then



End If



End If



End If

End If

End Sub


Text11.Text = Val(Text6.Text) + Val(Text7.Text) + Val(Text8.Text) + Val(Text8.Text) +

Val(Text9.Text) + Val(Text10.Text)

End Sub


42/141


Me.Hide

Form1.Show

End Sub


Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Text7.Text = ""

Text8.Text = ""

Text9.Text = ""

Text10.Text = ""

Text11.Text = ""

End Sub

Private Sub CREDITCARD_Click()

Me.Hide

Form4.Show

End Sub


End Sub


If Combo2.Text = "HAMAM" Then



43/141

End If

If Combo2.Text = "LUX" Then


End If

If Combo2.Text = "MARGO" Then


End If

If Combo2.Text = "POWER" Then


End If

If Combo2.Text = "J&J" Then


End If

If Combo2.Text = "SKIN CARE" Then


End If

If Combo2.Text = "cintol" Then


End If

End Sub


If Combo3.Text = "5-STAR" Then


End If

If Combo3.Text = "DIARY MILK" Then


End If

If Combo3.Text = "MUNCH" Then



44/141

End If

If Combo3.Text = "BARONE" Then


End If

If Combo3.Text = "FRUIT&NUT" Then


End If

End Sub


If Combo4.Text = "TIGER" Then


End If

If Combo4.Text = "MILK BIKIES" Then


End If

If Combo4.Text = "VITA" Then


End If

If Combo4.Text = "BOURBON" Then


End If

End Sub


If Combo5.Text = "VVD GOLD" Then



End If



45/141


End If



End If

End If

If Combo5.Text = "PARACHUTE" Then



End If



End If



End If

End If

If Combo5.Text = "MEERA" Then



End If



End If



End If

End If

If Combo5.Text = "VATIKA" Then



46/141


End If



End If



End If

End If

End Sub


If Combo1.Text = "TITAN" Then


End If

If Combo1.Text = "SONATA" Then


End If

If Combo1.Text = "TITAN RAGA" Then


End If

If Combo1.Text = "QUARTZ" Then


End If

If Combo1.Text = "CASIO" Then


End If

End Sub


47/141

Private Sub Text10_Click()

Text10.Text = Val(Text5.Text) * Val(Label15.Caption)

If Text5.Text = "" And Combo5.Text = "" Then

Text10.Text = 0

End If

End Sub




Text6.Text = 0

End If

End Sub




Text7.Text = 0

End If

End Sub




Text8.Text = 0

End If

End Sub


48/141




Text9.Text = 0

End If

End Sub

Form3:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n

Dim f As Integer

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n

If rs.EOF Then

rs.AddNew

rs("name") = Text1.Text

rs("userid") = Text2.Text

rs("password") = Text3.Text

rs("address") = Text4.Text

rs("contact") = Text5.Text

rs.Update

f = 1

Me.Hide

Form2.Show


49/141

GoTo a

End If

If Text1.Text = rs("name") Or Text2.Text = rs("userid") Or Text3.Text = rs("password") Or Text4.Text

= rs("address") Or Text5.Text = rs("contact") Then

MsgBox ("your details already updated")

Else

rs.MoveNext

End If

a:

Next

If f = 1 Then

MsgBox ("successfully registered")

MsgBox ("ready to shop")

End If

End Sub


Me.Hide

Form1.Show

End Sub


Set db = OpenDatabase("D:\vbexp\EXP2\login2.mdb")

Set rs = db.OpenRecordset("login2")

End Sub

Form4:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n


50/141

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n

If rs.EOF Then

MsgBox ("No such records found")

GoTo a

End If

If (Val(Text1.Text) = rs("creditcardno") And Val(Text2.Text) = rs("pinno")) Then

MsgBox ("transaction completed successfully")

MsgBox ("THANKS FOR YOUR VISIT TO OUR ENTERPRISE PLEASE COME AGAIN")

Else

rs.MoveNext

End If

a:

Next

End Sub


End

End Sub


Text1.Text = ""

Text2.Text = ""

End Sub


Set db = OpenDatabase("D:\vbexp\EXP2\credit.mdb")

Set rs = db.OpenRecordset("credit")

End Sub


51/141

PROJECT EXECUTION:


52/141


53/141


54/141

RESULT:



Acceptance testing.


55/141

Ex. No:

Date :

BANKING SYSTEM

PROBLEM STATEMENT:

In Earlier Days Banking Process were more tedious since manual Calculation of Transactions

involved Ledgers, Log Books etc., In order to make the Process simpler the Banking Process are

computerized and it enables customers to carry their transaction through the Internet. The Customers can

withdraw money, Deposit money and can also enquire about their balance amount in the Account via

Internet. The Customers needs to register themselves in order to use the Online Banking System. They

will be provided with unique user name and Password to Provide Security to their account .The

customers can use online Banking for Current account and Savings account. The New customers will be

asked fill up a Form in order to register them for online Banking.


Purpose:

The Purpose of this Project is to replace the older manual methods of Banking Transactions

by newer and more accurate methods of computerized online Banking; Since it would be for Storage of

Personal Details of Customers and also their account Details.


User name: A Unique id is provided to the Account Holder to enable them to access their account

online.

Password: A secure String chosen by the customers to protect their account from being illegally

accessed.

Withdraw: Taking back the money they have deposited in their Account.

Deposit: Saving/Depositing an amount in their account by using their account number.

.Intended Audience:

The Intended Audience of this Project is the customers of the Bank (who have an account in thatBank) and Bankers who are the Administrators, who can access account Details of all customers.

Project Scope:

The Scope of this Software is reduce the time spent in manual calculation of Transactions and

reduces the Space occupied by the Ledgers, Log Books that are used to store the Details of Transaction.

This Software replaces it with Computerized Digital Storage of Data which is more secure than Storing

in Ledgers. One more important Scope is that Customers can do their transaction Online.


56/141



The Perspective of this Project is to enable the online transaction of customers account such as

withdrawal, Deposition of amountand Balance enquiry.

User Classes:

The User classes are the

Customers, who can do the transaction such as withdrawal, Deposit of amount Online.

Bank Employees who can access all the account Details of the Employees.


Hardware Environment:

Server: Client:

RAM: 1 GB or more RAM: 256 MB or more

HDD: 160 GB or more HDD: 40 GB or more

Software Environment:

OS: Windows Server 2003 or higher OS: Windows XP or Higher


The Design Constraints of the Project

Customers may not be able to understand how to operate the Command Buttons.

Customers should be allowed to withdraw the amount only after Proper

Authentication.


The Assumptions of Project is, Bank customers dont disclose any Authentication information to

other users and Unknown People. The Project depends mainly on two third parties Software

o MS-ACCESS as DBMS tool

o VB 6.0 for Front End design of Project


57/141

User Interface:

The Project is completely GUI based. Hence the user can easily use the Software by Clicking on the

Appropriate command Buttons.

Software Interface:

The Software Interface is Between Visual Basic 6.0 which is used as front end application and is

connected to MS-ACCESS Database which acts as Backend to Store the Employee Information.

System Features:

The Features Provided by the System are:

New Customers can register their details in the Bank to enable Internet banking for

their account.

Customer can withdraw, deposit amount and enquire about their balance.

The withdrawal amount cannot be more than Deposited amount.



The customers must be allowed to carry out the transaction at any time and whenever he edits his

details it must be completely updated in the Database.


The Customers need not know about other customer Information so all accounts are secured

using unique user name and Password.

The Administrators can access all account details and he is the only person who can edit the

Customer Details.


58/141

DATA MODELING:


Use Case Diagram

Class Diagram

Sequence Diagram



Use case Diagram:

The Use case diagram is used to identify the primary elements and processes that form the

system. The primary elements are termed as "actors" and the processes are called "use cases." The Use

case diagram shows which actors interact with each use case

A use case diagram captures the functional aspects of a system. More specifically, it captures the

business processes carried out in the system.


59/141

Actors:

o Are NOT part of the systemthey represent anyone or anything that musto Interact with the system.o Only input information to the system.o Only receive information from the system.o Both input to and receive information from the system.o Represented in UML as a stickman

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.

1. Use Case Name: Login

Description: This use-case describes how the user log-in to the banking system.

Use case name: Login

Actor: Bank customer

Pre-conditioners:

The System is idle, displaying a welcome msg

Normal Course of Events: 1. Customer type the username and password in the system.

2. Press the login button to display next options.

Alternatives: Invalid Name/Password.

Post-conditioners: Customer password has been validated

1. Use Case Name: Account Type

Description:

This use-case describes whether the user selects the saving account or Current account.

Use case name: Account Type


Pre-conditioners: The customer is logged-in to the system, System is displaying Account type.

Normal Course of Events:

Customer has to select the account type whether saving account or current account.

Alternatives: None

Post-conditioners: Customer account has been validated.


60/141

1. Use Case Name: Transaction Type

Description:

This use-case describes whether the user selects the Withdraw or Deposit or Balance enquiry.

Use case name: Transaction Type


Pre-conditioners: The customer is logged-in to the system, System is displaying Transaction type.


Customer has to select the Transaction type whether Withdraw or Deposit or Balance enquiry.

Alternatives: None

Post-conditioners: Customer Transaction has been validated.

1. Use Case Name: Withdraw

Description:Customer withdraws a specific amount of funds from a bank account Use case name: Withdraw


Pre-conditioners: The customer is logged-in to the system, System is displaying Withdraw screen.


o Customer selects withdrawal, enter amount to be withdraw,

o Press the withdraw button.

Alternatives: None


1. Use Case Name: Deposit

Description:Customer deposits a specific amount of funds to the bank account Use case name: Deposit


Pre-conditioners: The customer is logged-in to the system, System is displaying deposit screen..


61/141


o Customer selects deposit enter amount to be deposti,

o Press the deposit button.

Alternatives: None


1. Use Case Name: Balance enquiry

Description:Customer enquires about their account balance.Use case name: Balance enquiry


Pre-conditioners: The customer is logged-in to the system, System is displaying Balance enquiry.


o Customer selects Balance enquiry in the list of options,

o Press the withdraw button.

Alternatives: None


1. Use Case Name: New Registration

Description:New Customer can register their account details.Use case name: New Registration


Pre-conditioners: The customer has to select New Register option.


o Enter the customer details in the textboxes,

o Press the Register button.

Alternatives: None

Post-conditioners: Customer account has been validated.


62/141

Class Diagram:




Login

New Registration

Account Type

Transaction Type.

Deposit

Withdraw

Balance enquiry


63/141

Sequence Diagram:

A Sequence diagram depicts the sequence of actions that occur in a system. The invocationofmethods in each object, and the order in which the invocation occurs is captured in a Sequence diagram.This makes the Sequence diagram a very useful tool to easily representthe dynamic behavior of asystem.

A Sequence diagram is two-dimensionalin nature. On the horizontal axis, it shows thelife of theobject that it represents, while on the vertical axis, it shows the sequence of the creation or invocation ofthese objects. Because it uses class name and object name references, the Sequence diagram is very useful in elaborating and detailing the dynamic design.

Description:


Customer

Banking System

Account: current or saving Transaction: withdrawal

Transaction: Deposit

Transaction: Balance enquiry Database

Customer Banking

system

Account:

current,saving

Transaction:

withdrawal

Transaction:

DepositTransaction;

enquiry

DB

LoginSelect

Enter amount

commit(TRANS ID)Successgive amount

show balance

Enter amountcommit(TRANS ID)

Success

show balance

receipt

Select

select balance enquirycommit(TRANS ID)

SuccessReceipt

show balance


64/141

Bank Customer Banking System

Verification

Database Bank

1: Enter username&password

2: Enter Account type

3: Enter Transaction Type

4: Acknowledgement message

5: Amount Transaction

6: updating

7: Verification

8: Processing 10: Updating

11: Maintaining system

9: Updating


Description:





Sequence diagram.








65/141




the system and the manner in which transitions are made from state to state. The STD serves as the basisfor behavioral modeling. A state transition diagram indicates how the system moves from state to state.

The state transition diagram represents the behavior of a system by depicting its states and the events


Description:



to change state.

Start

initiate

Login Registratio

n

Account

type

Transacton

type

Canceled

Complete

cancel

Withdrawal Deposit Balance

enquiry

Enter details

cancel

select

selectselect

valid

invalid

Completed

Finish Finish

Finish


66/141

PROJECT EXECUTION:

Coding:

Form1:


67/141


68/141


69/141


70/141


71/141


72/141

RESULT:



Acceptance testing.


73/141

Ex. No:

Date :

TEXT EDITOR

PROBLEM STATEMENT:

The Text Editor is used Perform Manipulations operations such as Cut, Copy and Paste. The

Text Editor can also be used to Search a Text, Adjust the Font size, Font color and Font type. The basic

operations Such as Opening a Existing Text Document, Saving the Text Document and Create a New

Document can also be done in the Text Editor.


Purpose:

The Purpose of this Document is to create a Text Document and perform all Possible

Manipulations over the Text such as Cut, Copy and Paste. We can also adjust the Font size, Font type

and Font color.


CUT: The CUT command is used to remove the selected text from its original position and place it inClipboard.

COPY: The COPY command is used to copy the Selected Contents on to the Clipboard and original

data is not removed from its Position.

PASTE: The PASTE command is used to place the text that is copied or cut in the desired Place.

Intended Audience:

The Intended Audience of this project is all the users who need to Perform Text Manipulations

and here there is no difference such as Administrator and User.

Project Scope:

The scope of this project is to make manipulations easier for the users.


74/141



The perspective of this Product is make text Manipulations more Easier

User Classes:

The user class is

All the users who perform all Possible Manipulations (Cut, Copy and Paste) over the Text.


The operating Environment is

OS: Windows 2000 or higher

RAM: 128 MBor higher

HDD: 20 GB or higher


The Design Constraints are

The users must be aware of the Sub menus available under each menu.


The Assumptions are that

The user does Manipulations over the Text and he does not include any Multimedia content

in the Editor.

The Project depends only on following third Party Software

Visual Basic 6.0 for the Front End Design of the Text Editor

User Interface:

The Project is completely GUI based. Hence the user can easily use the Software by Clicking on the

Appropriate command Buttons.

Software Interface:

The Software Interface is Between Visual Basic 6.0 which is used as front end application and is

connected to MS-ACCESS Database which acts as Backend to Store the Employee Information.


75/141

System Features:

The featuresprovided by the System are

The users can perform basic manipulations over the Text such as Cut, Copy and Paste.

The users can Search for a particular inside the Text Document they have created.

The userscan change the Font type, Font color and Font size.



The user should be able to manipulate any kind of Text and any large sized files should be

allowed for manipulation.


There is no need for any Special Requirements for this Project since it only manipulation of Text

data.


76/141

DATA MODELING:


Use Case Diagram

Class Diagram

Sequence Diagram Collaboration Diagram


Use case Diagram:



functionality provided by a system in terms of actors, their goals (represented as use cases), and any


Use cases: A use case describes a sequence of actions that provide something of measurable value to anactor 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.


77/141

Class Diagram:


that exist among them. 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. The Solid line between the

classes shows the relationship between them.

Description:

The classes used in this project are

File

Edit

Search

Format

Each class has its own attributes and operations.

File class -The attributes defined are new, open, save, save as, and exit.

Edit class -The attributes it has cut, copy, paste.

Search class - The attributes are find, find again.

Format class - The attributes are font size, font name, and color.
http://en.wikipedia.org/wiki/Software_engineeringhttp://en.wikipedia.org/wiki/Unified_Modeling_Languagehttp://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Class_(computer_science)http://en.wikipedia.org/wiki/Unified_Modeling_Languagehttp://en.wikipedia.org/wiki/Software_engineering


78/141

CLASS DIAGRAM

**

**

*

FILE

New

Open

Save

Save As

Exit

SEARCH

Find

Find Again

EDIT

Cut

Copy

Paste

FORMAT

Font Size

Font Name

Color


79/141

Sequence Diagram:

A Sequence Diagram is a kind of interaction diagram in which an object is shown as a box at a

top of a dashed vertical line. This vertical line is called as objects lifeline.

The lifeline represents the objects life during the interaction. Object deletion is shown with a

large X. Objects can be destroyed by another message.

Description:

The objects used in this sequence diagram are,

User

File

Edit

Search

Format

In text editor,

The user isthe main thing of any project.

The object File performs the sub menu items such as new, Open, Save, Save As, Exit.

The object Edit performs the sub menu items such as Cut, Copy and Paste.

The object Search performs the sub menu items such as Find, Find again.

The object Format performs the sub menu items such as Font size, Font name, Color.


80/141

USER FILE EDIT SEARCH FORMAT

Create or Open the

documentFind the

word

Select the Font

size

Store and exit

the documentAgain find

the word

Select the text Color

SEQUENCE DIAGRAM

Select the Font

name

Cut the

word

Copy the

word

Paste the

word


81/141


In a Collaboration diagram, objects are shown as icons. As on a sequence diagram, arrow

indicate the message sent within the given Use Case. Numbering the messages indicates the sequence.

Description:

This diagram contains the group of classes created, interfaces and the elements that work

together to provide the overall behavior of the project. It also describes the relationship between each

classes and how they relate with each other.

User Text Editor

FileEdit Fomat Search

1: start text editor

2: New,open,save

3: cut,copy,paste,clear,selectall

4: Bold,Italic,underline

5: Find


82/141





for behavioral modeling. A state transition diagram indicates how the system moves from state to state. The state transition diagram represents the behavior of a system by depicting its states and the events


Description:



to change state.

Start

initiate

Text editor

Edit

return

File

return

Format

cut,copy,paste,clear,selectall

new,open,save

bold,italic,underline

Search

Find

return

Completed

Exit

complete


83/141


Coding:

Form1:

Dim a

Private Sub colour_Click()

End Sub

Private Sub Bold_Click()

RTBox.SelBold = True

RTBox.SetFocus

End Sub

Private Sub Bullet_Click()

RTBox.SelBullet = 1

End Sub

Private Sub Clear_Click()

RTBox.SelText = Clear

End Sub

Private Sub Close_Click()

RTBox.Visible = False

End Sub

Private Sub Color_Click()

CDlgBox.ShowColor

RTBox.SelColor = CDlgBox.Color

RTBox.SetFocus

End Sub


84/141

Private Sub Copy_Click()

a = RTBox.SelText

End Sub

Private Sub Cut_Click()

RTBox.SelText = a

RTBox.SelText = Clear

End Sub

Private Sub FlatScrollBar1_Change()

End Sub

Private Sub Size_Click()

End Sub

Private Sub Exit_Click()

End

End Sub

Private Sub Form_Paint()

RTBox.Height = Me.ScaleHeight

RTBox.Width = Me.ScaleWidth

End Sub

Private Sub Italic_Click()

RTBox.SelItalic = True

RTBox.SetFocus

End Sub


85/141

Private Sub Maximized_Click()

Me.WindowState = vbMaximized

End Sub

Private Sub Minimized_Click()

Me.WindowState = vbMinimized

End Sub

Private Sub New_Click()

RTBox.Visible = True

RTBox.SetFocus

RTBox = Clear

End Sub

Private Sub Normal_Click()

Me.WindowState = vbNormal

End Sub

Private Sub Open_Click()

CDlgBox.ShowOpen

RTBox.FileName = CDlgBox.FileName

RTBox.Visible = True

RTBox.SetFocus

End Sub

Private Sub Paste_Click()

RTBox.SelText = a

RTBox.SelText = Clipboard.GetText


86/141

End Sub

Private Sub Regular_Click()

RTBox.SelBold = False

RTBox.SelUnderline = False

RTBox.SelStrikeThru = False

RTBox.SelItalic = False

RTBox.SelColor = RGB(0, 0, 0)

End Sub

Private Sub RTBox_Change()

End Sub

Private Sub Save_Click()

CDlgBox.ShowSave

RTBox.SaveFile CDlgBox.FileName

RTBox.SetFocus

End Sub

Private Sub SelectAll_Click()

RTBox.SelStart = 0

RTBox.SelLength = Len(RTBox.Text)

End Sub

Private Sub Strikethru_Click()

RTBox.SelStrikeThru = True

RTBox.SetFocus

End Sub


87/141


88/141

PROJECT EXECUTION:


89/141


90/141


91/141

RESULT:



Acceptance testing.


92/141

Ex. No:

Date :

ONLINE VOTING SYSTEM

PROBLEM STATEMENT:

A majority of process impact employees presently spend an average of 30 minutes on voting

their opinion about some issues. Before, they must have a meeting in every department to draw a

conclusion. All employees must leave their seat and go to the meeting-room for discussion. It is waste of

time and need a lot of meeting room.

Many employees would request a system that would permit them to vote online such a system

would save those employees voting time. This would improve their quality of work and their

productivity. So we have decided to build an Online Voting System. This system would be used byemployees to poll their opinion.


Purpose:

The main objective of this document is to illustrate the functional and non-functional

requirements of the project Online Voting System.

The intended audience for the SRS includes the users, developers and testers.


Administrator: A log-id representing a user with administrator privileges to the software.

User: A general log-in id assigned to the customers.

Client: Intended user for the software.

MS Access: Back end connection to the application used to access information.

Visual Basic: VB 6.0 is used for designing front end of the software.

Use-Case Diagram: A broad level diagram of the project showing a basic overview.

Data-Flow Diagram: It shows the data flows between the entities.

Unique-key: Used to differentiate entities in a DB.


93/141

Project Success Criteria:

Our main goal is to complete this project within allotted deadline and also within the budget

allotted.

It is necessary to satisfy the functional and non-functional requirements of the software.


This section of the SRS describes the general factors that affect the products and its

requirements. It does not state any specific requirements.

Use-Case Model Survey:

This section contains an overview of the use-case model or the subset of the use-case model that

is applicable for this subsystem or features. This includes a list of names and brief descriptions of all use

cases and actors along with applicable diagrams and relationships.

Introduction:

The use-case model provides a special to let the user know how to operate the system and the

divisions of the software.

Survey Description:

The use-case model can develop to understand the need of the system.

Use-case Model Hierarchy:

This section presents the use-case packages hierarchically, explains the dependencies among

them, and shows the content of each package recursively. If the model has several levels of packages,

those at the top level are represented first. For each package includes

o The Name

o A brief description explaining the packages function

o A list of use-cases owned by the package, including name and brief description of each use-case.

o A list of actors owned by the package.

o A list of relationships owned by the package.

o A list of packages directly owned by the package.


94/141


We assumed that the system is not very much focused on security and there is another system is

as a forum.

All the information inputted by the user is well enough to use.

REQUIREMENTS:

This section contains all the software requirements to enable designers to design a system. By

using use-case modeling, the majority of these requirements are captured in the use-cases.

Log-in/Log-off use-case:

Actor(s):

User, Administrator.

Description:

This use-case describes how the user log-in to the online voting system.

Pre-conditioners:

No Pre-conditioners.

Post-conditioners:

No Post-conditioners.

Priority:

Normal


o The system validates the actors password and logs him/her into the system.

o The system displays the main form and the use-case ends.

Alternative Course:

Invalid Name/Password.

Exceptions:

Any connections to the database but return by an unthinkable result are regarded as an

Exception.


95/141

Voting use-case:

Actor(s):


Description:

The user can vote for a result on the basis of the items listed bellowing list box.

Pre-conditioners:

The user log-in to the Online Voting System so that they can do the voting.

Post-conditioners:

The statistics of the voting system can only be used after other people do the voting.

Priority:

Normal


o User log-in to the voting system.

o User select the thesis that the user want to do the voting.

o Click the vote and finish the voting.

See voting results:

Actor(s):


Description:

The administrator can see the result of the voting.

Pre-conditioners:

The administrator has log-in to the system.

Post-conditioners:

No post-conditioners.

Priority:

High


96/141


o Administrator log-in to the online voting system.

o The voting result can be seen by the admin by clicking the result.

Functional Requirements:

Functional Requirements may include: feature sets, capabilities. Application development tools

are employed to capture the functionality (requirements tools, modeling tools).

GUI:

It describes the graphical user interface of the software. It includes the following forms to

illustrate user interface features.

Log-in Form.

Voting Form.

New User Registration Form.

Results for Voting System.



The proposed system that we are going to develop will be used in various department of the

organization. So that system can withstand even though many number of customers request the desired

service.

Safety Requirements:

The database may get crashed at any certain time due to virus or operating system failure.

Therefore it is required to take the database backup.


The online voting system should be highly secured.

The System should be prevented from unauthorized access.


97/141

Hardware Interfaces:

Server Side:

Operating System: Windows Server 2003/ Windows Server 2008.

Processor: Intel Pentium Dual-Core 2.8 GHZ or higher.

RAM: 1GB DDR2 or more.

HDD: 160GB or more.

Client Side:

Operating System: Windows XP or more.

Processor: Intel Pentium IV 2.4 GHZ or higher.

RAM: 256MB DDR2 or more.

HDD: 40GB or more.

Software Interfaces:

Database: MS Access 2007

Application: Visual Basic 6.0

Web Server: Internet Information Service (IIS)


98/141

Counting votes

Voting results

Login

Administrator

Participants

Selection of Nominees

Authentication

Databaseprocess

verify

Vote for Nominees

update

DATA MODELING:


Use Case Diagram

Class Diagram

Sequence Diagram



Use case Diagram:





Actors:


Participants

Administrator

Database

Use cases:




99/141

1. Use Case Name: Login/Logoff

Actor(s):


Description:

This use-case describes how the user log-in to the online voting system.

Pre-conditioners:

No Pre-conditioners.

Post-conditioners:

No Post-conditioners.

Priority:

Normal


o The system validates the actors password and logs him/her into the system.

o The system displays the main form and the use-case ends.

Alternative Course:

Invalid Name/Password.

Exceptions:

Any connections to the database but return by an unthinkable result are regarded as an

Exception.

2. Use Case Name: Voting use-case:

Actor(s):


Description:

The user can vote for a result on the basis of the items listed bellowing list box.

Pre-conditioners:

The user log-in to the Online Voting System so that they can do the voting.


100/141

Post-conditioners:

The statistics of the voting system can only be used after other people do the voting.

Priority:

Normal


o User log-in to the voting system.

o User select the thesis that the user want to do the voting.

o Click the vote and finish the voting.

3. Use Case Name: Voting Results

Actor(s):


Description:

The administrator can see the result of the voting.

Pre-conditioners:

The administrator has log-in to the system.

Post-conditioners:

No post-conditioners.

Priority:

High


o Administrator log-in to the online voting system.

o The voting result can be seen by the admin by clicking the result.


101/141

Class Diagram:




Online voting

New Registration

Voting Results

Voting


102/141

Participants Administrator Voting System Voting ResultsDatabase

LoginLogin

Displaying Nominees

verify

Vote for NomineesUpdate

counting Votes Displaying results Processing DB

Sequence Diagram:

A Sequence diagram depicts the sequence of actions that occur in a system. The invocationofmethods in each object, and the order in which the invocation occurs is captured in a Sequence diagram.This makes the Sequence diagram a very useful tool to easily representthe dynamic behavior of a

system.A Sequence diagram is two-dimensionalin nature. On the horizontal axis, it shows thelife of the

object that it represents, while on the vertical axis, it shows the sequence of the creation or invocation ofthese objects. Because it uses class name and object name references, the Sequence diagram is very useful in elaborating and detailing the dynamic design.

Description:

It depicts the high level sequence diagram for online voting. The various scenarios of the

sequence diagram used in this project are

Participants

Administrator

Voting System

Voting Results

Database


103/141


Description:





Sequence diagram.








104/141


The state transition diagram(STD) indicates how the system behaves as a consequence ofexternal events. To accomplish this, the STD represents the various modes of behavior (called states) of


for behavioral modeling. A state transition diagram indicates how the system moves from state to state.

The state transition diagram represents the behavior of a system by depicting its states and the eventsthat cause the system to change state.

Description:



to change state.

Start

initiate

Login Registration

Enter details

invalid

complete

Canceled

cancel

Counting

Admin

Voting

Displaying

Results

Completed

complete

complete

Participant


105/141


Coding:

Form1:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n


MsgBox ("Invalid username and password, register your details")

GoTo a

End If

If Text1.Text = rs("username") And Text2.Text = rs("voteid") Then

Me.Hide

Form3.Show

Else

rs.MoveNext

End If

a:

Next

End Sub


106/141


Me.Hide

Form2.Show

End Sub


End

End Sub


If Text1.Text = "administrator" And Text2.Text = "hcl123" Then

Me.Hide

Form4.Show

Else

MsgBox ("Access denied")

End If

End Sub


Set db = OpenDatabase("d:\vbexp\exp5\login.mdb")

Set rs = db.OpenRecordset("login")

End Sub


107/141

Form2:

Dim db As Database

Dim rs As Recordset


Dim i

Dim n

Dim f As Integer

n = rs.RecordCount

rs.MoveFirst

For i = 0 To n

If rs.EOF Then

rs.AddNew

rs("username") = Text1.Text

rs("voteid") = Text2.Text

rs("email") = Text3.Text

rs("addr")