Software Engineering record

(1)

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 - IN – CHARGE SIGNATURE OF HEAD OF DEPT

SUBMITTED FOR THE PRACTICAL EXAMINATION HELD ON _________________________

(2)

INDEX

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

(3)

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

(4)

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:

The Intended Audience 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

(5)

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 not disclose to anybody about his Emp-id and Password.

 The Project Depends mainly upon two Third Party Software  MS-ACCESS as DBMS tool.

(6)

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 information’s 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)

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 <includes> Payment Calculation <includes>

(8)

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.

(9)

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)

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 object’s lifeline.

The lifeline represents the object’s life during the interaction. Object deletion is shown with a large X. Object’s can be destroyed by another message.

Description:

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

 Employee

 Administrator

 Database

Employee Administrator

Database 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

(11)

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 each classes and how they relate with each other.

Employee

Administrator

Database 3: Valid

1: Get the Information of the employee 7: Getting the payment

9: Giving the payment

2: Validation Checking 5: Store Employee Details

6: Store Payment Details 8: Checking the payment Details 4: Send Acknowledge

(12)

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 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 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)

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)

Text1.Text = "" Text2.Text = "" End Sub

Private Sub Command3_Click() End

End Sub

Private Sub Command4_Click() 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

Private Sub Command1_Click() Me.Hide

Form1.Show End Sub

Private Sub Command2_Click()

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

Private Sub Command3_Click() rs.AddNew

rs("ename") = Text1.Text rs("eid") = Text2.Text rs("edesign") = Text3.Text rs("edoj") = Text4.Text

(15)

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

Private Sub Command4_Click() Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Text6.Text = "" Text7.Text = "" Text8.Text = "" End Sub

End Sub

Private Sub Command6_Click() 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)

Form4.Text5.Text = Date Form4.Text6.Text = Time End Sub

Dim n

n = rs.RecordCount rs.MoveFirst For i = 0 To n

If rs.EOF = True Then

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)

Set db = OpenDatabase("C:\Documents and Settings\Administrator\My Documents\vbexp\payroll\Employee.mdb") Set rs = db.OpenRecordset("Employee") End Sub Form3: Dim db As Database Dim rs As Recordset

Private Sub Command1_Click() Dim i Dim n Dim f As Integer n = rs.RecordCount rs.MoveFirst For i = 0 To n

If rs.EOF = True Then 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

(18)

End If a: Next

If f = 1 Then

MsgBox "ur details are already registered" End If

End Sub

Private Sub Label6_Click() End Sub

Private Sub Command2_Click() Text1.Text = ""

Text2.Text = "" Text3.Text = "" Text4.Text = "" End Sub

End Sub

Form1.Show End Sub

Set db = OpenDatabase("C:\Documents and Settings\Administrator\My Documents\vbexp\payroll\emp1.mdb")

Set rs = db.OpenRecordset("emp1") End Sub

(19)

Form4:

Form1.Show End Sub

Private Sub Command2_Click() rptpayroll.Show

(20)

PROJECT EXECUTION:

(21)

(22)

(23)

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)

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.

SOFTWARE REQUIREMENT SPECIFICATION:

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.

Document conventions:

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.

(25)

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.

OVERALL DESCRIPTION:

Product Perspective:

 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)

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.

Design and Implementation Constraints:

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)

Assumptions and Dependencies:

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)

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.

Non-Functional Requirements:

 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 user’s 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.

(29)

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

(30)

Make purchase Customer Seller View Items <<include>> Check out <<include>> Credit Payment service Client Register Database

DATA MODELING:

 Class 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:

 Customer

 Seller

 Database

 Credit payment service

USE CASES:

(31)

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 of external 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:

(32)

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:

Description: The classes used in this project are  Login

 Shopping

 Payment

(33)

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 invocation of methods 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 represent the dynamic behavior of a system.

A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the life of the object that it represents, while on the vertical axis, it shows the sequence of the creation or invocation of these 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

 Database

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

(34)

Web Customer Online Shop Inventory Items Shopping card Order 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)

State-transition Diagram:

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 Login Shopping Payment Finish valid Registratio n Canceled Enter details cancel complete cancel invalid invalid initiate

(36)

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

Form3.Show End Sub

(37)

End Sub

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 Label7.Caption = "999"

(38)

If Combo1.Text = "TITAN RAGA" Then Label7.Caption = "1243"

End If

If Combo1.Text = "QUARTZ" Then Label7.Caption = "1999"

End If

If Combo1.Text = "CASIO" Then Label7.Caption = "880"

End If End Sub

Private Sub Combo2_Change() If Combo2.Text = "HAMAM" Then Label12.Caption = "19"

End If

If Combo2.Caption = "LUX" Then Label12.Caption = "39"

End If

If Combo2.Caption = "MARGO" Then Label12.Caption = "24"

End If

If Combo2.Caption = "POWER" Then Label12.Caption = "22"

End If

If Combo2.Text = "J&J" Then Label12.Caption = "32" End If

If Combo2.Caption = "SKINCARE" Then Label12.Caption = "38"

(39)

If Combo2.Caption = "CINTOL" Then Label12.Caption = "25"

End If End Sub

Private Sub Combo3_Change() If Combo3.Text = "5-STAR" Then Label13.Caption = "5"

End If

If Combo3.Text = "DIARY MILK" Then Label13.Caption = "10"

End If

If Combo3.Text = "MUNCH" Then Label13.Caption = "10"

End If

If Combo3.Text = "BARONE" Then Label13.Caption = "5"

End If

If Combo3.Text = "FRUIT&NUT" Then Label13.Caption = "10"

End If End Sub

Private Sub Combo4_Change() If Combo4.Text = "TIGER" Then Label14.Caption = "6"

End If

If Combo4.Text = "MILKBIKES" Then Label14.Caption = "20"

(40)

If Combo4.Text = "VITA" Then Label14.Caption "19"

End If

If Combo4.Text = "BOURBON" Then Label14.Caption = "15"

End If End Sub

Private Sub Combo5_Change()

If Combo5.Text = "VVDGOLD" Then If Val(Text5.Text) = "1" Then Label15.Caption = "38" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "98" End If If Val(Text5.Text) = "2" Then Label15.Caption = "177" End If End If

If Combo5.Text = "PARACHUTE" Then If Val(Text5.Text) = "1" Then Label15.Caption = "80" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "198" End If If Val(Text5.Text) = "2" Then Label15.Caption = "277" End If

(41)

End If

If Combo5.Text = "MEERA" Then If Val(Text5.Text) = "1" Then Label15.Caption = "169" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "198" End If If Val(Text5.Text) = "2" Then Label15.Caption = "297" End If End If

If Combo5.Text = "VATIKA" Then If Val(Text5.Text) = "1" Then Label15.Caption = "79" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "169" End If If Val(Text5.Text) = "2" Then Label15.Caption = "227" End If End If End Sub

Private Sub Command1_Click()

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

(42)

Form1.Show End Sub

Private Sub Command3_Click() 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

Private Sub Form_Load() End Sub

Private Sub Label12_Click()

If Combo2.Text = "HAMAM" Then Label12.Caption = "19"

(43)

End If

If Combo2.Text = "LUX" Then Label12.Caption = "39"

End If

If Combo2.Text = "MARGO" Then Label12.Caption = "24"

End If

If Combo2.Text = "POWER" Then Label12.Caption = "22"

End If

If Combo2.Text = "J&J" Then Label12.Caption = "32" End If

If Combo2.Text = "SKIN CARE" Then Label12.Caption = "38"

End If

If Combo2.Text = "cintol" Then Label12.Caption = "25"

End If End Sub

Private Sub Label13_Click() If Combo3.Text = "5-STAR" Then Label13.Caption = "5"

End If

If Combo3.Text = "DIARY MILK" Then Label13.Caption = "10"

End If

If Combo3.Text = "MUNCH" Then Label13.Caption = "10"

(44)

End If

If Combo3.Text = "BARONE" Then Label13.Caption = "5"

End If

If Combo3.Text = "FRUIT&NUT" Then Label13.Caption = "10"

End If End Sub

Private Sub Label14_Click() If Combo4.Text = "TIGER" Then Label14.Caption = "6"

End If

If Combo4.Text = "MILK BIKIES" Then Label14.Caption = "20"

End If

If Combo4.Text = "VITA" Then Label14.Caption = "19"

End If

If Combo4.Text = "BOURBON" Then Label14.Caption = "15"

End If End Sub

Private Sub Label15_Click()

If Combo5.Text = "VVD GOLD" Then If Val(Text5.Text) = "1" Then

Label15.Caption = "38" End If

(45)

Label15.Caption = "98" End If If Val(Text5.Text) = "2" Then Label15.Caption = "177" End If End If

If Combo5.Text = "PARACHUTE" Then If Val(Text5.Text) = "1" Then Label15.Caption = "80" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "198" End If If Val(Text5.Text) = "2" Then Label15.Caption = "277" End If End If

If Combo5.Text = "MEERA" Then If Val(Text5.Text) = "1" Then Label15.Caption = "169" End If If Val(Text5.Text) = "2" Then Label15.Caption = "198" End If If Val(Text5.Text) = "2" Then Label15.Caption = "297" End If End If

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

(46)

Label15.Caption = "79" End If If Val(Text5.Text) = "1.5" Then Label15.Caption = "169" End If If Val(Text5.Text) = "2" Then Label15.Caption = "227" End If End If End Sub

Private Sub Label7_Click() If Combo1.Text = "TITAN" Then Label7.Caption = "599"

End If

If Combo1.Text = "SONATA" Then Label7.Caption = "999"

End If

If Combo1.Text = "TITAN RAGA" Then Label7.Caption = "1243"

End If

If Combo1.Text = "QUARTZ" Then Label7.Caption = "1999"

End If

If Combo1.Text = "CASIO" Then Label7.Caption = "880"

End If

(47)

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 = Val(Text1.Text) * Val(Label7.Caption) If Text1.Text = "" And Combo1.Text = "" Then Text6.Text = 0

End If End Sub

(48)

Text9.Text = Val(Text4.Text) * Val(Label14.Caption) If Text4.Text = "" And Combo4.Text = "" Then Text9.Text = 0 End If End Sub Form3: Dim db As Database Dim rs As Recordset

Private Sub Command1_Click() 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)

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

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

(50)

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 Sub

Text2.Text = "" End Sub

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

(51)

(52)

(53)

(54)

RESULT:

(55)

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.

SOFTWARE REQUIREMENT SPECIFICATION:

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.

Document conventions:

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 that Bank) 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)

OVERALL DESCRIPTION:

Product Perspective:

The Perspective of this Project is to enable the online transaction of customers account such as withdrawal, Deposition of amount and 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.

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

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

Assumptions and Dependencies:

The Assumptions of Project is, Bank customers don’t 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

(57)

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.

Non-Functional Requirements:

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)

DATA MODELING:

 Class 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)

Actors:

o Are NOT part of the system – they represent anyone or anything that must o 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:

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

(60)

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. Normal Course of Events:

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. Normal Course of Events:

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

(61)

Normal Course of Events:

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. Normal Course of Events:

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. Normal Course of Events:

o Enter the customer details in the textboxes, o Press the Register button.

Alternatives: None

(62)

Class Diagram:

Description: The classes used in this project are  Login  New Registration  Account Type  Transaction Type.  Deposit  Withdraw  Balance enquiry

(63)

Sequence Diagram:

A Sequence diagram depicts the sequence of actions that occur in a system. The invocation of methods 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 represent the dynamic behavior of a system.

A Sequence diagram is two-dimensional in nature. On the horizontal axis, it shows the life of the object that it represents, while on the vertical axis, it shows the sequence of the creation or invocation of these 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: Deposit Transaction; enquiry DB Login _Select Enter amount commit(TRANS ID) Success give amount show balance Enter amount commit(TRANS ID) Success show balance receipt Select select balance enquiry commit(TRANS ID) Success Receipt show balance

(64)

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

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.

(65)

State-transition Diagram:

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 initiate Login Registratio n Account type Transacton type Canceled Complete cancel

Withdrawal Deposit Balance enquiry Enter details cancel select select select valid invalid Completed Finish Finish Finish

(66)

PROJECT EXECUTION:

Coding:

(67)

(68)

(69)

(70)

(71)

(72)

RESULT:

(73)

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.

SOFTWARE REQUIREMENT SPECIFICATION:

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.

Document conventions:

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

Clipboard.

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:

(74)

OVERALL DESCRIPTION:

Product Perspective:

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.

Operating Environment:

The operating Environment is

OS: Windows 2000 or higher RAM: 128 MB or higher HDD: 20 GB or higher

Design and Implementation Constraints:

The Design Constraints are

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

Assumptions and Dependencies:

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)

System Features:

The features provided 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 users can change the Font type, Font color and Font size.

Non-Functional Requirements:

 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)

DATA MODELING:

 Class 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.

Use cases: A use case describes a sequence of actions that provide something of measurable value to an

actor and is drawn as a horizontal ellipse

Actors: An actor is a person, organization, or external system that plays a role in one or more

(77)

Class Diagram:

A Class diagram describes the types of objects in the System and the various kinds of static relationships 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.

(78)

CLASS DIAGRAM

* * * * * FILE New Open Save Save As Exit SEARCH Find Find Again EDIT Cut Copy Paste FORMAT Font Size Font Name Color

(79)

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 object’s lifeline.

The lifeline represents the object’s life during the interaction. Object deletion is shown with a large X. Object’s 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 is the 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.

(80)

USER _FILE EDIT SEARCH FORMAT

Create or Open the document

Find the word

Select the Font size

Store and exit the document

Again find the word

Select the text Color

SEQUENCE DIAGRAM

Select the Font name Cut the word Copy the word Paste the word

(81)

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 each classes and how they relate with each other.

User Text Editor

File _Edit _Fomat _Search

1: start text editor

2: New,open,save

3: cut,copy,paste,clear,selectall

4: Bold,Italic,underline 5: Find

(82)

State-transition Diagram:

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 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)

PROJECT IMPLEMENTATION:

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

(84)

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)

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

(86)

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

(87)

Private Sub UnderLine_Click() RTBox.SelBold = True

RTBox.SetFocus End Sub

(88)

(89)

(90)

(91)