Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Content
System Analysis
Hardware & Software Requirement
Overview of Front-end tool (VB)
Overview of Back-end tool (MS access)
Database Design
Data Dictionary
DFD
System Testing
Design Screenshots
Coding
System Implementation
Conclusion
Bibliography
SYSTEM ANALYSIS
System development can generally be thought of as having two major
components: System Analysis and System Design.
System Design is a process of planning a new system or replace or
complement an existing system. But before the planning can be done, we
must thoroughly understand the existing system and determine how
computer can be best used to make its operation more effective.
System Analysis is, then, the process of gathering and interpreting
facts, diagnosing problems and using the information to recommend
improvements to the system. In brief we can say that analysis specifies that
what the system should do. Design states how to accomplish the objective.
Identification of Need
Identification of the needs is the first step in the analysis
phase. Before developing the actual software firstly we need to analysis all the
need of the user.
Preliminary Investigation
In this phase we collect all the necessary information
related to the requirement of the client.
Feasibility study
A feasibility study is designed to provide an overview of the
primary issue related to a business idea. A feasibility study looks at three
major areas:
Organizational issue
Market issue
Financial issue
Economic Feasibility:
Economic feasibility of the project is very
important feasibility study that has to done .Cost Benefit analysis is
done for this purpose. Economic feasibility for the Project should be
determined before any project under taking as this is important. If the
project is not feasible there is no point in carrying on with the project.
Cost-Benefit analysis is an important phase as this leads to the decision
whether the project is within the budget of the organization. After this
analysis it was found that this project is economically feasible.
Technical Feasibility:
Technical Feasibility centers on the existing
computer system(hardware, software etc) and to what extends it can
support the proposed addition. Under this consideration, it is examined
that the organization is well equipped with all the required hardware and
the software resources like Pentium 4 processor, greater than 512 Mb
RAM., Window XP Professional. Having considered all there aspect can
the system be developed and implemented.
Behavioral Feasibility
By Behavioral Feasibility we find that whether
user will accept the change and whether our project is behaviorally
feasible or not. Automating the bank Management system will help in
computerizing the whole manual system of service and maintaining the
information related to the Customer. Feasibility can be done when the
system is to be implemented at a particular site.
Conclusion
HARDWARE REQUIREMENTS:
This section describes what is needed to use the resultant system on
to stand-alone computers. To run the proposed system in Windows
Environment following components are needed.
A Pentium computer certified for use with Microsoft Windows
A Mouse or a pointing device
At least 16 MB of RAM (32 MB suggested for smooth performance
A minimum of 25 MB of available disk space to install all the features of
the proposed system
200 MB of available disk space for storage of program, database and
ODBC
A minimum of 50 MB swap space in the hard disk
A printer (Laser Jet or Ink Jet) to get the report on hard copy
SOFTWARE REQUIREMENTS:
Microsoft Windows XP or higher version
The Visual Basic Enterprise Edition 6.0 software
The Microsoft Access
Crystal Reports 6.7 (Reporting Tool)
programs.
The
appropriate
device
drivers
for
auto
3.
smaller
independent
modular
segments.
This
makes
or
Applications
containing
multiple
tasks
in
Windows
Environment.
What can Visual Basic do for us?
Visual Basic can serve as an ideal front-end tool for the client to
interact. It has got connectivity mechanism for all types of databases
situated far and wide in a network and so it can cater to the needs of a
large body of clients. Using the latest ActiveX technologies, it can
integrate the functionality provided by other application like Word, Excel
and other Windows. Its Internet capabilities provide easy access to
documents and applications across the Internet. Above all it embodies
the Object Oriented Technology, which is the cutting edge technology for
all the present day developments in the Software World. The final
application is a true EXE file and so can be freely distributed.
Why Visual Basic?
Visual Basic has emerged as one of the standard Windows
Programming Language and it as become a must for all software people
for developing Applications in Visual Environment. In the years since its
introduction, Visual Basic has revolutionized windows programming and
into
one
environment.
In
traditional
programming
environment the code editors, which are used to code program, do not
have any code-checking intelligence, if there is any error in source code
we do not find it until we compile it. At that point editor performs a
syntax check and a logic check. Where as in Visual Basic environment
these
components
are
put
into
one
Integrated
Development
Environment (IDE). As we type the code for the program the editor
performs the syntax check immediately to ensure that we had entered
Finished application is a true .EXE file that uses a runtime Dynamic Link
Library (DLL) that we can freely distributed
ABOUT MS ACCESS
Microsoft Access is a computer application used to create and manage
computer-based databases on desktop computers and/or on connected
computers (a network). Microsoft Access can be used for personal
information management (PIM), in a small business to organize and manage
all data, or in an enterprise to communicate with servers.
This tutorial will help you get started with Microsoft Access and may
solve some of your problems, but it is a very good idea to use the
Help Files that come with Microsoft Access, or go to Microsoft's web
site
located
at
for
further
assistance.
First of all you need to understand how Microsoft Access breaks down
a database. Some keywords involved in this process are: Database
File, Table, Record, Field, Data-type. Here is the Hierarchy that
Microsoft Access uses in breaking down a database.
Datatype) Text
This tutorial will help you get started with Microsoft Access and may
solve some of your problems, but it is a very good idea to use the Help
Files that come with Microsoft Access (or any program you use for that
matter).
DATABASE DESIGN
design
phase
that
functionally
decomposes
the
requirement
DATA DICTIONARY
Data dictionary consists of description of all the data used in the system.
It consists of logical characteristics of current systems data stores including
name, description, aliases, contents and organization. Data dictionary serves
as the basis for identifying database requirements during system design. Data
dictionary is a catalog, a depositary of the elements in the system.
The data dictionary is used to manage the details in the large system,
to communicate a common meaning for all system elements, to document the
future of the system, to locate errors and omission in the system. Data
dictionary contains two types of descriptions for the data flowing through the
system attributes and tables. Attributes are grouped together to make up the
tables. The most fundamental data level is attributes tables are a Set of data
items, data related to one another and that collectively describes a
component in the system. The description of the attributes consists of data
names, data descriptions, aliases, and length and data values. The description
of data structures consists sequence relation ship, selection relation ship,
iteration relationship and operational relationship.
SYSTEM TESTING
SYSTEM INTEGRATION AND TESTING
The proposed system is tested parallel with the software effort that
consists
of
its
own
phases
of
analysis, implementation,
testing
and
maintenance
UNIT TESTING
Unit testing comprises the set of tests performed by an individual
programmer prior to integration of the unit into a large system.
Coding and debugging -> Unit testing -> Integration testing
There are four categories of tests should be performed.
Functional Testing
Performance Testing
Stress Testing
Structure testing
Function test cases involve exercising the code with the nominal input
values for which the expected results are known, as well as boundary values
maximum.
Performance testing determines the amount of execution spent in
various parts of the unit program throughput, response time and device
utilization by the program unit.
Stress tests are those tests designing to initially break the unit.
Structure tests are con concerned with exercising the internal logic of a
program and traversing particular execution path.
Establishing a test completion criterion is another difficulty encountered
in the unit testing of real programs. Unit testing includes.
INTEGRATION TESTING
Integration testing is of three types:
Bottom up Integration
Top down Integration
Sandwich Integration
Bottom up integration testing consists of unit testing followed by system
testing. Unit testing has the goal of testing individual modules in the system.
Subsystem testing is concerned with verifying the operation of the interfaces
between modules in the sub systems.
System Testing is concerned with subtleties in the interfaces, decision
logic, and control flow recovery procedure, throughput, capacity and timing
characteristics.
Top down integration starts with the main routine and one or two
immediately
subordinate
routines
in
the
system
structure.
Top
down
integration requires the use of program stubs to simulate the effect of lower
level routines that are called by those being tested.
Top down method has the fallowing advantages:
LOGIN FORM
Private Declare Function sndPlaySound Lib "winmm.dll" Alias "sndPlaySoundA" (ByVal
lpszSoundName As String, ByVal uFlags As Long) As Long
Private Sub CmdExit_Click()
If MsgBox("Are you sure you want to exit ?", 4 + 32, title) = vbNo Then
GoTo EXITPROCEDURE
Else
End
End If
EXITPROCEDURE:
Exit Sub
End Sub
Private Sub cmdLogin_Click()
On Error GoTo errhandler
If txtPassword.Text = "" Or txtUserName.Text = "" Then
MsgBox "Please enter User Name and password ", vbExclamation, title
txtPassword.SetFocus
GoTo EXITPROCEDURE
End If
txtPassword.Text = LCase(txtPassword.Text)
recUsers.MoveFirst
Do While Not recUsers.EOF
If Trim(recUsers!LoginID) = Trim(txtUserName.Text) And _
Trim(recUsers!Password) = Trim(txtPassword.Text) Then
sndPlaySound App.Path & "\Reminder\reminder.wav", &H1
frmMain.status.Panels("Role").Text = Trim(recUsers!Role)
frmMain.status.Panels("Name").Text = Trim(txtUserName.Text)
UserID = recUsers!EmployeeID
UserName = recUsers!LoginID
UserPassword = recUsers!Password
UserRole = recUsers!Role
Call Enable_Menu
If UserRole = "Employee" Or UserRole = "Teller" Then
DEPOSITE FORM
Private Sub cboAccountNumber_Click()
On Error GoTo errhandler
Call DisplayCustomerDetails(cboAccountNumber.Text)
txtBalance.Text = Balance
txtFirstName.Text = FirstName
txtLastName.Text = LastName
txtGender.Text = Gender
txtAccountType.Text = AccountType
cmdOk.Enabled = True
txtAmount.Enabled = True
txtAmount.SetFocus
Pic.Picture = LoadPicture(App.Path & "\pictures\" & CustomerPicture)
EXITPROCEDURE:
Exit Sub
errhandler:
Pic.Picture = LoadPicture(App.Path & "\Pictures\" & "NA.GIF")
GoTo EXITPROCEDURE
End Sub
Private Sub cboAccountNumber_KeyPress(KeyAscii As Integer)
KeyAscii = 0
End Sub
Private Sub cmdClose_Click()
If MsgBox("Are you sure you want to cancel ?", 4 + 32, title) = vbNo Then
GoTo EXITPROCEDURE
Else
Unload Me
End If
EXITPROCEDURE:
Exit Sub
End Sub
Private Sub cmdOk_Click()
On Error GoTo errhandler
WITHDRAW FORM
Private Sub cboAccountNumber_Click()
On Error GoTo errhandler
Call DisplayCustomerDetails(cboAccountNumber.Text)
txtBalance.Text = Balance
txtFirstName.Text = FirstName
txtLastName.Text = LastName
txtGender.Text = Gender
txtAccountType.Text = AccountType
cmdOk.Enabled = True
txtAmount.Enabled = True
txtAmount.SetFocus
Pic.Picture = LoadPicture(App.Path & "\pictures\" & CustomerPicture)
EXITPROCEDURE:
Exit Sub
errhandler:
Pic.Picture = LoadPicture(App.Path & "\Pictures\" & "NA.GIF")
GoTo EXITPROCEDURE
End Sub
Private Sub cboAccountNumber_KeyPress(KeyAscii As Integer)
KeyAscii = 0
End Sub
Private Sub cmdClose_Click()
If MsgBox("Are you sure you want to cancel ?", 4 + 32, title) = vbNo Then
GoTo EXITPROCEDURE
Else
Unload Me
End If
EXITPROCEDURE:
Exit Sub
End Sub
Private Sub cmdOk_Click()
On Error GoTo errhandler
IMPLEMENTATION
The ultimate goal of the implementation is to write the source code and
internal documentation so that it can be verified easily. The code and
documentation should be written in a manner that eases debugging,
testing and modifications.
During the implementation phase coding, debugging, documentation and
testing of the system were carried out module by module. During coding
design
specifications
were
translated
into
the
source
code.
Implementation of the system was done using Visual Basic 6.0/Ms Access
2003 and Windows XP platform.
An effort has been made to satisfy the following goals:
Accuracy of results
Minimizations of response time
Clarity and Simplicity of Code
Minimization of hard coding
Minimization of the memory used
Various types of errors were discovered while debugging the modules. Proper
documentation of each module was done. Each module was separately
tested and errors were debugged as per the needs.
Testing of reports was carried out to find the response time.
Modifications were made in the reports as per the requirements of the
persons for whom the system is designed.
Changes in data files are recorded along with date and time. This
will help the system manager to find out when the file last modified.
CONCLUSION
Under trial and testing, the project is running very efficiently and seems
to be bug free under standard usage. The test data used simulated the
actual data to be used. We have included a lot of error validation code
which provides interactive message to the user and guides them to make
proper entries if some entries are made in invalid format.
We are sure that the user of this project will find it extremely beneficial
because the project reduce the time wasted in paper work and manual
entries and provides a friendly simply user interface that any one can be
comfortable to work with
BIBLIOGRAPHY
Mastering Visual Basic 6 - Evangelos Petroutsos
Visual Basic 6 Black Book - M. M. Blecjkout
An Introduction to Database System - Vipin C. Desai
System Analysis and Design - Elias M. Awad