Software Engineering Record

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 _________________________
EXTERNAL EXAMINER
INTERNAL EXAMINER
INDEX
S.No. DATE Name of Experiment Page No. Marks Signature of Staff
S.No.
DATE
Name of Experiment
Page No.
Marks
Signature of Staff
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 efficiency.
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: RAM: 1 GB or more HDD: 160 GB or more Client: RAM: 256 MB 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. VB 6.0 for the Front End Design of Project
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.
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: 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 Administrator Database
Employee Details <includes>
Admin
<includes> Authentication Company Database Payment Calculation
Employee
Payment Details
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.
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
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
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
9: Giving the payment
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
1: Get the Information of the employee 7: Getting the payment Administrator 9: Giving the payment
4: Send Acknowledge 3: Valid
Database
2: Validation Checking 5: Store Employee Details 6: Store Payment Details 8: Checking the payment Details
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.
initiate
start
Enter details invalid
Login
Complete
Registratio n
valid
cancel
Payroll Calculation
cancel
Canceled
cancel
Finish
Payslip Gentration
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
Private Sub Command2_Click()
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
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
Private Sub Command5_Click() End 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")
Form4.Text5.Text = Date Form4.Text6.Text = Time End Sub
Private Sub Command7_Click() Dim i 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
Private Sub Form_Load() 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 rs.MoveNext
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
Private Sub Command4_Click() Me.Hide Form1.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
Form4: Private Sub Command1_Click() Me.Hide Form1.Show End Sub
Private Sub Command2_Click() rptpayroll.Show End Sub
PROJECT EXECUTION:
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.
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.

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: User: Client: MS Access: Visual Basic: A log-id representing a user with administrator privileges to the software. A general log-in id assigned to the customers. Intended user for the software. Back end connection to the application used to access information. 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.
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.
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.

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
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.
Performance 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. Security Requirements: 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: RAM: HDD: Intel Pentium Dual-Core 2.8 GHZ or higher. 1GB DDR2 or more. 160GB or more.
Client Side: Operating System: Windows XP or more. Processor: RAM: HDD: Intel Pentium IV 2.4 GHZ or higher. 256MB DDR2 or more. 40GB or more.
Software Interfaces:
Database: MS Access 2007
Application: Visual Basic 6.0 Web Server: Internet Information Service (IIS)
DATA MODELING:
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: 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.
Customer Seller Database Credit payment service
View Items <<include>> Database
Make purchase <<include>> Customer Check out Seller
Credit Payment service Client Register
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 o o o Customer may search for items, Browse catalog, view items recommended for him/her, 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: This use-case includes the View items use-case and Check out use-case.
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 New Registration
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: The various scenarios of the sequence diagram used in this project are 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.
Customer Login Search Inventory
Online shop Verifcation Processing Acknowledge Search results
Database
View Item description
Add to shopping cart Payment Confirmation
Checkout
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.
Inventory Online shopping 2: search() 3: [order complete] update_inventory()
9: Processing DB 1: find items() Web Customer 8: delivery 5: make_payment() 7: make_order() 6: get items() Order Shopping card Online Shop 4: view description() Items
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.
initiate Start Enter details
invalid complete Login Registratio n
valid
cancel cancel Canceled
Shopping
invalid Finish Payment

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 Private Sub Command3_Click() Me.Hide Form3.Show End Sub
Private Sub Command5_Click() Text1.Text = "" Text2.Text = "" End Sub
Private Sub Form_Load() 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" 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 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" End If
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" 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 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
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) End Sub
Private Sub Command2_Click() Me.Hide 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"
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"
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 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 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
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
End Sub
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
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
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 Private Sub Command2_Click() Me.Hide Form1.Show End Sub Private Sub Form_Load() Set db = OpenDatabase("D:\vbexp\EXP2\login2.mdb") Set rs = db.OpenRecordset("login2") End Sub
Form4: 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 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 Private Sub Command2_Click() End End Sub
Private Sub Command3_Click() Text1.Text = "" Text2.Text = "" End Sub
Private Sub Form_Load() Set db = OpenDatabase("D:\vbexp\EXP2\credit.mdb") Set rs = db.OpenRecordset("credit") End Sub
PROJECT EXECUTION:
RESULT:
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.

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

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.
Hardware Environment:
Server: RAM: 1 GB or more HDD: 160 GB or more Client: RAM: 256 MB 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
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:
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.
Performance 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. Security Requirements: 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.
DATA MODELING:
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.
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: 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: Actor: 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. Login Bank customer
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: Actor: Account Type Bank customer
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.
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 Actor: Bank customer
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 Actor: Bank customer
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 Post-conditioners: Customer Transaction has been validated.
1. Use Case Name: Deposit Description: Customer deposits a specific amount of funds to the bank account Use case name: Deposit Actor: Bank customer
Pre-conditioners: The customer is logged-in to the system, System is displaying deposit screen..
Normal Course of Events: o Customer selects deposit enter amount to be deposti, o Press the deposit button. Alternatives: None Post-conditioners: Customer Transaction has been validated.
1. Use Case Name: Balance enquiry Description: Customer enquires about their account balance. Use case name: Balance enquiry Actor: Bank customer
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 Post-conditioners: Customer Transaction has been validated.
1. Use Case Name: New Registration Description: New Customer can register their account details. Use case name: New Registration Actor: Bank customer
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 Post-conditioners: Customer account has been validated.
Class Diagram:
Description: The classes used in this project are Login New Registration Account Type Transaction Type. Deposit Withdraw Balance enquiry
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: The various scenarios of the sequence diagram used in this project are
Customer Banking System Account: current or saving Transaction: withdrawal Transaction: Deposit Transaction: Balance enquiry Database
Customer
Banking system Login
Account: current,saving
Transaction: withdrawal
Transaction: Deposit
Transaction; enquiry
DB
Select Enter amount commit(TRANS ID)
give amount
Success show balance
Select
Enter amount commit(TRANS ID) Success receipt show balance
select balance enquiry commit(TRANS ID) Receipt Success show balance
3: Enter Transaction Type 2: Enter Account type Bank Customer 1: Enter username&password
Verification
Banking System
4: Acknowledgement message 5: Amount Transaction 8: Processing 10: Updating
11: Maintaining system 7: Verification 6: updating Database 9: Updating Bank
initiate
Start
Enter details
invalid Login Complete valid Account type cancel Registratio n
Transacton type select select select
cancel
Canceled
Withdrawal
Deposit
Balance enquiry
Finish
Finish Finish
Completed
PROJECT EXECUTION: Coding:

Form1:
RESULT:
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.

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 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:
The scope of this project is to make manipulations easier for the users.

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 MB or 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:
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.
Performance Requirements: The user should be able to manipulate any kind of Text and any large sized files should be allowed for manipulation.
Security Requirements: There is no need for any Special Requirements for this Project since it only manipulation of Text data.
DATA MODELING:
Use case Diagram:

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. Use cases: A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse Actors: An actor is a person, organization, or external system that plays a role in one or more interactions with the system.
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. Format class - The attributes are font size, font name, and color.
CLASS DIAGRAM
FILE New
*
Open Save Save As Exit
EDIT Cut Copy Paste
SEARCH Find Find Again

*
FORMAT Font Size Font Name Color
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 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. The object Format performs the sub menu items such as Font size, Font name, Color.
SEQUENCE DIAGRAM
USER
FILE
EDIT
SEARCH
FORMAT
Create or Open the document Find the word
Cut the word
Select the Font size
Store and exit the document Again find the word
Select the Font name
Copy the word
Select the text Color Paste the word
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.
1: start text editor User Text Editor
5: Find 2: New,open,save
4: Bold,Italic,underline 3: cut,copy,paste,clear,selectall File
Edit
Fomat
Search
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.
initiate
Start
Edit return cut,copy,paste,clear,selectall Text editor
bold,italic,underline Format
Find return new,open,save return Search File Exit Completed complete

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
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
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
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
Private Sub UnderLine_Click() RTBox.SelBold = True RTBox.SetFocus End Sub
PROJECT EXECUTION:
RESULT:
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 by employees to poll their opinion.

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.

OVERALL DESCRIPTION:
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.

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 Normal Course of Events: 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.
Voting use-case:
Actor(s): User, Administrator. 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 Normal Course of Events: 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): User, Administrator. 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
Normal Course of Events: 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 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.
Performance Requirements: 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. Security Requirements: The online voting system should be highly secured. The System should be prevented from unauthorized access.
Server Side: Operating System: Windows Server 2003/ Windows Server 2008. Processor: RAM: HDD: Client Side: Operating System: Windows XP or more. Processor: RAM: HDD: Intel Pentium IV 2.4 GHZ or higher. 256MB DDR2 or more. 40GB or more. Intel Pentium Dual-Core 2.8 GHZ or higher. 1GB DDR2 or more. 160GB or more.
DATA MODELING:
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: 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. Participants Administrator Database
<<include>>
Login
Authentication
verify
update
Participants
Vote for Nominees process Database
<<extend>>
Counting votes
Administrator
Selection of Nominees <<extend>> Voting results
1. Use Case Name: Login/Logoff 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 Normal Course of Events: 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): User, Administrator. 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 Normal Course of Events: 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): User, Administrator. 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 Normal Course of Events: o Administrator log-in to the online voting system. o The voting result can be seen by the admin by clicking the result.
Class Diagram:
Description: The classes used in this project are Online voting New Registration Voting Results Voting
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: 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
Participants
Administrator
Voting System
Voting Results verify
Database
Login
Login
Displaying Nominees Vote for Nominees Update
counting Votes
Displaying results
Processing DB
initiate
Start
Enter details
invalid
Login
complete
Registration
Participant Admin cancel
Voting
Counting
Canceled
complete Displaying Results
complete
Completed

Private Sub Command1_Click() Dim i Dim n n = rs.RecordCount rs.MoveFirst For i = 0 To n If rs.EOF = True Then 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
Private Sub Command2_Click() Me.Hide Form2.Show End Sub
Private Sub Command4_Click() If Text1.Text = "administrator" And Text2.Text = "hcl123" Then Me.Hide Form4.Show Else MsgBox ("Access denied") End If End Sub
Private Sub Form_Load() Set db = OpenDatabase("d:\vbexp\exp5\login.mdb") Set rs = db.OpenRecordset("login") End Sub
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("username") = Text1.Text rs("voteid") = Text2.Text rs("email") = Text3.Text rs("addr") = Text4.Text rs.Update MsgBox ("updated successfully") GoTo a End If If Text1.Text = rs("username") Or Text2.Text = rs("voteid") Or Text3.Text = rs("email") Or Text4.Text = rs("addr") Then MsgBox ("your details already updated") Else rs.MoveNext End If
a: Next End Sub
Private Sub Command3_Click() Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" End Sub
Private Sub Form_Load() Set db = OpenDatabase("d:\vbexp\exp5\login.mdb") Set rs = db.OpenRecordset("login") End Sub
Private Sub Label1_Click() End Sub
Private Sub Picture1_Click() Me.Hide Form1.Show End Sub
Form3:
Dim db As Database Dim rs As Recordset
Private Sub Command1_Click() Dim f As Integer If Option1.Value Then f=1 ElseIf Option2.Value Then f=2 ElseIf Option3.Value Then f=3 ElseIf Option4.Value Then f=4 End If Select Case (f) Case 1: rs.Edit rs("jeeva") = Val(rs("jeeva")) + 1 rs.Update Case 2: rs.Edit rs("surya") = Val(rs("surya")) + 1 rs.Update Case 3: rs.Edit
rs("karthi") = Val(rs("karthi")) + 1 rs.Update Case 4: rs.Edit rs("dhanush") = Val(rs("dhanush")) + 1 rs.Update End Select MsgBox ("Thanks for voting") Me.Hide Form1.Show End Sub
Private Sub Form_Load() Set db = OpenDatabase("d:\vbexp\exp5\voting.mdb") Set rs = db.OpenRecordset("vote") End Sub
Private Sub Command1_Click() If (Val(rs("jeeva")) > Val(rs("surya")) And Val(rs("jeeva")) > Val(rs("karthi")) And Val(rs("jeeva")) > Val(rs("dhanush"))) Then MsgBox ("jeeva is leading") ElseIf (Val(rs("surya")) > Val(rs("jeeva")) Val(rs("surya")) > Val(rs("dhanush"))) Then MsgBox ("Surya is leading") ElseIf (Val(rs("karthi")) > Val(rs("surya")) Val(rs("karthi")) > Val(rs("dhanush"))) Then MsgBox ("karthi is leading") Else MsgBox ("dhanush is leading") End If End Sub And Val(rs("karthi")) > Val(rs("jeeva")) And And Val(rs("surya")) > Val(rs("karthi")) And
Private Sub Form_Load() Set db = OpenDatabase("d:\vbexp\exp5\voting.mdb") Set rs = db.OpenRecordset("vote") End Sub
PROJECT EXECUTION:
RESULT:
Ex. No: Date :
LIBRARY MANAGEMENT SYSTEM
PROBLEM STATEMENT:
Borrowing books, returning books or viewing the available books at the library of the local University is currently done manually where in the student has to go to the library and check the available books at the library. It is waste of time for the student to come to the library if the student doesnt get the book. Then the librarian checks the students id and allows the member to check out the book and the librarian then updates the student database and also the books database. This takes at least one hours approximately. We have decided to investigate the use of an online Library Management System. This system would be used by members who may be students or professors of that University to check the availability of the books and borrow the books, and by the librarian to update the library databases.

The purpose of the SRS document is to describe the external behavior of the Library Management System. Requirement specification defines and describes the operations, interfaces, performance and quality assurance requirements of the Library Management System. The document also describes the non-functional requirements such as user interfaces. The SRS captures the complete software requirements for the system.
Product Characteristics and Requirements:

Secured Database. User tracking Search Feature Calculating fines. Checking the availability of books Students will get a message before the due date in order to avoid fines.


The Library Management System will provide a search functionality to facilitate the search of resources. This search will be based on various categories viz. book name or the ISBN. Further the library staff personnel can add/update/remove the resources and the resource users from the system.
Product Features:
There are two different users who will be using this product. 1 Librarian, who will be acting as the administrator. 2 Students, who will be accessing the Library.
The features that are available to the Librarian are o A Librarian can issue a book to the students. o Can view the different category of books available. o Can take the books returned from students. o Add books and their information of the books to the database. o Edit the information of the existing books. o Can check the report of the issued book. o Can access all the accounts of the student. The features available to the students are, o Can view the different categories of books available in the library. o Can own an account in the library. o Can view the books issued to him. o Can search a particular book.
User Classes and Characteristics:

The user includes: Students, Staff who will be using the features by accessing this System. Librarian who will be acting as the controller and he will have all the privileges of an administrator.

The product is developed using Visual Basic 6.0. The backend connection is done by MS Access. The product is accomplished with log-in facility so that specific function is available to specific students.
Assumptions and Dependencies: o The users have sufficient knowledge of computers. o The users know the English language, as the user interface will be provided in English. o The product can access university student database.
SYSTEM FEATURES: Database Storage:

Proposed Database is intended to store, retrieve, update and manipulate information related to shopping which include o Books availability. o Staff information. o Student details. o Calculation of fines.
This section gives the list of functional requirements which are applicable to the Library Management 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: - Student Log-in and Staff Log-in. Library Book details. Student details. Return of Books. New user Form.
Performance Requirements: The proposed system that we are going to develop will be used as the chief performance system within the different campuses of the university which interacts with the university staff and students. Therefore it is expected that the database would perform all the functional requirements that are specified by the university. 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.
Security Requirements: We are going to develop a secured database for the university. There are different categories of users namely teaching staff, administrator, library staff, students etc Depending upon the category of the user the access rights are decided. Software Quality Attributes: The quality of the database is maintained in such a way that it can be very user friendly to all the users of the database.
Server Side: Operating System: Windows Server 2003/ Windows Server 2008. Processor: RAM: HDD: Client Side: Operating System: Windows XP or more. Processor: RAM: HDD: Intel Pentium IV 2.4 GHZ or higher. 256MB DDR2 or more. 40GB or more. Intel Pentium Dual-Core 2.8 GHZ or higher. 1GB DDR2 or more. 160GB or more.
DATA MODELING:
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: 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. The Use-cases in the Library Management System are Login Issue Books Search Books View Books Returning Book Member Librarian Database
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 Library Member Librarian Supplier
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: It depicts the high level sequence diagram for online voting. The various scenarios of the sequence diagram used in this project are Member Librarian Database Supplier
Database Supplier
Member Enter ID
Librarian
Authendication
Access Verified
Acknowledgement
Searching Book Book available Book Available
Lend Books Issue Book
Update DB
Order Books Update
Supply Books
Exit from library LogOut
1: Search Book 3: Lend Books 2: Enter ID Member 4: Verified message Librarian
5: Place Orders 6: Check Authentication 8: Supply Books 7: Update
Database
Supplier

Login Form: Private Sub cmdcancel_Click() Unload Me End Sub
Private Sub cmdok_Click() If txtusername.Text = "tce" And txtpassword.Text = "cse" Then frmmenu.Visible = True frmlogin.Visible = False Unload Me Else MsgBox ("Please Check Your Username and Password") txtusername.SetFocus End If End Sub
Main menu form: Private Sub Command1_Click() End Unload Me End Sub
Private Sub mnubookdetails_Click() book.Show
frmmenu.Hide End Sub
Private Sub mnuborrow_Click() borrow.Show frmmenu.Hide End Sub
Private Sub mnureturn_Click() frmreturn.Show frmmenu.Hide End Sub
Book details form: Dim a As VbMsgBoxResult
Private Sub Command1_Click() Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Text6.Text = "" Text8.Text = "" Text1.SetFocus Command3.Enabled = False Command4.Enabled = False End Sub
Private Sub Command2_Click() On Error Resume Next If Text1.Text = "" Or Text2.Text = "" Or Text3.Text = "" Or Text4.Text = "" Or Text5.Text = "" Or Text6.Text = "" Or Text7.Text = "" Then a = MsgBox("RECORDS NOT SAVED.. PLS COMPLETE..", vbCritical, "WARNING") Text1.Text = "" Text1.SetFocus ElseIf Text1.Text <> "" Or Text2.Text <> "" Or Text3.Text <> "" Or Text4.Text <> "" Or Text5.Text <> "" Or Text6.Text <> "" Or Text7.Text <> "" Then Data1.Recordset(0) = Text1.Text Data1.Recordset(1) = Text2.Text Data1.Recordset(2) = Text3.Text Data1.Recordset(3) = Text4.Text Data1.Recordset(4) = Text5.Text Data1.Recordset(5) = Text6.Text Data1.Recordset(6) = Text8.Text Data1.Recordset.Update MsgBox ("Record Saved") End If Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Text6.Text = "" Text8.Text = "" Command2.Enabled = False End Sub
Private Sub Command3_Click() On Error Resume Next a = MsgBox("ARE YOU SURE?", vbYesNo, "DELETE") If a = vbYes Then Data1.Recordset.Delete MsgBox ("Record Deleted") Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" Text6.Text = "" Text8.Text = "" Text1.SetFocus End If End Sub
Private Sub Command4_Click() Data1.Recordset.Edit Data1.Recordset(0) = Text1.Text Data1.Recordset(1) = Text2.Text Data1.Recordset(2) = Text3.Text Data1.Recordset(3) = Text4.Text Data1.Recordset(4) = Text5.Text Data1.Recordset(5) = Text6.Text Data1.Recordset(6) = Text8.Text Command2.Enabled = True
End Sub
Private Sub Command5_Click() Unload Me frmmenu.Show End Sub
Private Sub Command6_Click() Command2.Enabled = True Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = True Text5.Enabled = True Text6.Enabled = True Text8.Enabled = True Data1.Recordset.AddNew End Sub
Private Sub Command7_Click() Text1.Enabled = True Text2.Enabled = True Text3.Enabled = True Text4.Enabled = True Text5.Enabled = True Text6.Enabled = True Text8.Enabled = True Dim n_strsearch, e_strsearch As String
Dim namecheck, edicheck As Long n_strsearch = InputBox("Enter the Book Name to find", "Book Name") e_strsearch = InputBox("Enter the Edition", "Edition") If n_strsearch = "" Or e_strsearch = "" Then Exit Sub Dim n As Integer n=1 Data1.Recordset.MoveFirst If Data1.Recordset(0) = "" Then Exit Sub While n < Data1.Recordset.RecordCount namecheck = InStr(1, Data1.Recordset(0), n_strsearch, vbTextCompare) edicheck = InStr(1, Data1.Recordset(2), e_strsearch, vbTextCompare) If namecheck > 0 And edicheck > 0 Then Text1.Text = Data1.Recordset(0) Text2.Text = Data1.Recordset(1) Text3.Text = Data1.Recordset(2) Text4.Text = Data1.Recordset(3) Text5.Text = Data1.Recordset(4) Text6.Text = Data1.Recordset(5) Text8.Text = Data1.Recordset(6) Command3.Enabled = True Command4.Enabled = True Exit Sub Else n=n+1 Data1.Recordset.MoveNext End If Wend namecheck = InStr(1, Data1.Recordset(0), n_strsearch, vbTextCompare)
edicheck = InStr(1, Data1.Recordset(2), e_strsearch, vbTextCompare) If namecheck > 0 And edicheck > 0 Then Text1.Text = Data1.Recordset(0) Text2.Text = Data1.Recordset(1) Text3.Text = Data1.Recordset(2) Text4.Text = Data1.Recordset(3) Text5.Text = Data1.Recordset(4) Text6.Text = Data1.Recordset(5) Text8.Text = Data1.Recordset(6) Command3.Enabled = True Command4.Enabled = True Exit Sub Else MsgBox ("No records match your search") End If End Sub
Private Sub Form_Load() Text1.Enabled = False Text2.Enabled = False Text3.Enabled = False Text4.Enabled = False Text5.Enabled = False Text6.Enabled = False Text8.Enabled = False Command2.Enabled = False Command3.Enabled = False Command4.Enabled = False
End Sub
Retrieving Form: Private Sub Command1_Click() Data1.Recordset(0) = Text1.Text Data1.Recordset(1) = Text2.Text Data1.Recordset(2) = Text3.Text Data1.Recordset(3) = Text4.Text Data1.Recordset.Update MsgBox ("Record updated") Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Data1.Recordset.AddNew End Sub
Private Sub Form_Initialize() Data1.Recordset.AddNew Text2.Text = Format(Now, "dd-mm-yyyy") Text4.Text = Format(Now + 15, "dd-mm-yyyy") End Sub
Return Form: Option Explicit Dim t_strsearch As String Sub func() Dim tokennocheck As Long t_strsearch = InputBox("Enter The Token Number", "Token Number") If t_strsearch = "" Then Exit Sub Dim n As Integer n=1 Dim achk As Boolean achk = False borrow.Data1.Recordset.MoveFirst While n < borrow.Data1.Recordset.RecordCount tokennocheck = InStr(1, borrow.Data1.Recordset(0), t_strsearch, vbTextCompare) If tokennocheck > 0 Then Text1.Text = t_strsearch Text2.Text = Format(Now, "dd-mm-yyyy") Text3.Text = borrow.Data1.Recordset(3) Text4.Text = borrow.Data1.Recordset(2) achk = True Exit Sub Else n=n+1 borrow.Data1.Recordset.MoveNext End If Wend tokennocheck = InStr(1, borrow.Data1.Recordset(0), t_strsearch, vbTextCompare) If tokennocheck > 0 Then
Text1.Text = t_strsearch Text2.Text = Format(Now, "dd-mm-yyyy") Text3.Text = borrow.Data1.Recordset(3) Text4.Text = borrow.Data1.Recordset(2) achk = True Exit Sub End If If achk = False Then MsgBox ("Incorrect token number") End If End Sub
Private Sub Command2_Click() Data1.Recordset.AddNew Data1.Recordset(0) = Text1.Text Data1.Recordset(1) = Text2.Text Data1.Recordset(2) = Text3.Text Data1.Recordset(3) = Text4.Text Data1.Recordset.Update MsgBox ("Records updated") Text1.Text = "" Text2.Text = "" Text3.Text = ""
Text4.Text = "" End Sub
Private Sub Command3_Click() Call func End Sub Private Sub Form_Load() Call func End Sub
PROJECT EXECUTION:
LOGIN FORM:
MAIN MENU:
BOOK DETAILS FORM:
RETRIEVING FORM:
RETURN FORM:
RESULT:

Software Engineering Record

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Software Engineering Record

Hochgeladen von

Copyright:

Verfügbare Formate

TAMILNADU COLLEGE OF ENGINEERING

PALANISAME RAVI NAGAR, KARUMATHAMPATTI, COIMBATORE -641659

BRANCH _______________________ SUBJECT _______________________

UNIVERSITY REGISTER No.

SIGNATURE OF LAB - IN CHARGE

SIGNATURE OF HEAD OF DEPT

SUBMITTED FOR THE PRACTICAL EXAMINATION HELD ON _________________________

Ex. No: Date :

PAYROLL PROCESSING SYSTEM

SOFTWARE REQUIREMENT SPECIFICATION: Purpose:

OVERALL DESCRIPTION: Product Perspective:

Design and Implementation Constraints:

Assumptions and Dependencies:

Use case diagram:

Employee Administrator Database

Employee Details <includes>

<includes> Authentication Company Database Payment Calculation

6: Store Payment Details

7: Getting the payment 8: Checking the payment Details

9: Giving the payment

4: Send Acknowledge 3: Valid

Enter details invalid

PROJECT IMPLEMENTATION: Coding:

Private Sub Command2_Click()

Private Sub Command5_Click() End End Sub

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

Private Sub Command3_Click() End End Sub

Form4: Private Sub Command1_Click() Me.Hide Form1.Show End Sub

Private Sub Command2_Click() rptpayroll.Show End Sub

Ex. No: Date :

SOFTWARE REQUIREMENT SPECIFICATION: Purpose:

Product Characteristics and Specific Requirements:

Project Success Criteria:

OVERALL DESCRIPTION: Product Perspective:

User Classes and Characteristics:

Design and Implementation Constraints:

Assumptions and Dependencies:

SYSTEM FEATURES: Database Storage:

USE CASE DIAGRAM

Customer Seller Database Credit payment service

View Items <<include>> Database

Make purchase <<include>> Customer Check out Seller

Credit Payment service Client Register

Customer Login Search Inventory

Online shop Verifcation Processing Acknowledge Search results

View Item description

Add to shopping cart Payment Confirmation

Inventory Online shopping 2: search() 3: [order complete] update_inventory()

initiate Start Enter details

invalid complete Login Registratio n

cancel cancel Canceled

invalid Finish Payment

PROJECT IMPLEMENTATION: Coding:

Private Sub Command4_Click() End End Sub

Private Sub Command5_Click() Text1.Text = "" Text2.Text = "" End Sub

Private Sub Form_Load() Set db = OpenDatabase("D:\vbexp\EXP2\login2.mdb") Set rs = db.OpenRecordset("login2") End Sub

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

Private Sub Command2_Click() Me.Hide Form1.Show 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"

Form3: Dim db As Database Dim rs As Recordset

BRANCH _ SUBJECT _