Documente Academic
Documente Profesional
Documente Cultură
Nitish .J
AMCET
1
INDEX
1 Initial Phase 1
1.0 Introduction 2
1.1 Schedule 4
1.2 S/W development life cycle 5
2 Analysis 7
2.0 Scope 8
2.1 Objective 8
2.2 Problem definition 9
2.3 Environmental requirements 10
2.4 Features of front end 11
2.5 Features of back end 17
2.6 Modules and description 21
3 Design 24
2
4 Coding 43
6.0 Maintenance 68
6.1 70
6.2 Maintenance and its types 71
Software development lifecycle
7 model 72
Software maintenance cost
7.0 73
7.1 Conclusion 73
8 Conclusion 74
Future enhancement
75
Reference 78
Appendix 1 – screenshots
Appendix 2 – DB table data
3
1) INITIAL PHASE
4
1.1) INTRODUCTION
5
delivered through an electronic communication backbone, viz. Internet. But,
in the process it has thrown open issues which have ramifications beyond
what a new delivery channel would normally envisage and, hence, has
compelled regulators world over to take note of this emerging channel.
Unlike its predecessors these internet only banks do not maintain brick and
mortar bank branches. Although to deposit cash or checks, you will still have
to spend time at the bank counter.
6
7
1.1) SCHEDULE
5 Testing 12-10-2010 11
8
9
1.2) SOFTWARE DEVELOPMENT LIFECYCLE
The activity of testing begins during system development and spans all
subsequent phases. Some system development lifecycles describe testing
which is performed after the coding phase, but this may cause the software
to be delivered without sufficient testing.
• The Design phase goes much faster, as designs are only done on the
items in the current release.
• Coding and Testing go much faster because there are fewer items to
code and test. If major design flaws are found, re-work is much faster
since the functional areas have been greatly reduced.
• As the software is implemented, the client can make recommendations
for the next iteration due to experiences learned in the past iteration.
If iterations are closer than that, you spend too much time on convergence
and the project timeframe expands. During the coding phase, code reviews
must be done weekly to ensure that the developers are delivering to
specification and all source code is put under source control. Also, full
installation routines are to be used for each iterative release as it would be
done in production.
• Software design
10
• Programming
• Testing
• Maintenance
Iterative Model
Analysis Design
Testing Maintenanc
e
Analysis
Design
Testing Maintenanc
e
Analysis
Design
Testing
Maintenanc
e
11
ADVANTAGES:
12
2) ANALYSIS PHASE
13
14
2.0) SCOPE OF THE PROJECT
15
16
2.2) PROBLEM DEFINITION
System analysis is a logical process; the objective of this stage is not actually
to solve the problem but to determine what must be done to solve the
problem. The basic objective of the analysis stage is to develop the logical
model of the system using tools such as UML (Unified modeling language).
First let’s take a look at the existing and proposed system.
Existing System:
Proposed System:
Considering the stress and time taken to go to bank and do transaction. The
development of a well structure and secured online banking system will
allow customer to perform objectives like, creating a banking system that is
easily accessible by customers from the comfort of their homes, offices 24/7.
Reduce the flow of human traffic and long queues at banks; Promote efficient
and effective banking for the banks by focusing on those services that still
require physical presence at the banking hall. Provides intra-bank funds
transfer services to their customers. Keep a detailed log of customer
transactions with the bank on his account.
The proposal is then weighed with the existing system analytically and the
best one is selected. The proposal is presented to the user for an
endorsement by the user. The proposal is reviewed on user request and
suitable changes are made. This is loop that ends as soon as the user is
satisfied with proposal. Preliminary study is the process of gathering and
interpreting facts, using the information for further studies on the system.
Preliminary study is problem solving activity that requires intensive
communication between the system users and system developers. It does
various feasibility studies. In these studies a rough figure of the system
activities can be obtained, from which the decision about the strategies to be
followed for effective system study and analysis can be taken
17
18
2.3) ENVIRONMENTAL SPECIFICATION
HARDWARE REQUIREMENTS:
SOFTWARE REQUIREMENT:
19
2.4) FEATURES OF FRONTEND: VB 6.0
There are different type applications we can develop with visual basic
enterprise edition. These types are referred as Projects; in visual basic we
create projects which include different types of modules and many forms. A
good project may have many forms as it can have. Following are the major
type of projects we can have in Visual Basic
2. Active EXE, Active DLL: These types of project are available with the
professional edition. Active X components are basic code building
components that don’t have a visible interface and that can add special
functionality to our applications.
20
3. Active X Control: Using this type of project we can create our own
Visual Basic controls.
7. IIS Applications: Visual Basic allows user to build application that run
on the web server and interact with clients over the internet with the internet
information server.
8. Add-in: We can create our own add-in for the VB IDE. Add-ins is the
special commands we can add to Visual Basic menus. Add-ins helps us to
extend the VB IDE.
21
Label Draws a box to display text
Text box Draws a box that can display text and let the user
type in text
Drive list box Draws a drive list box that displays all
the disk drives available
Directory list box Draws a directory list box that displays a directory
on a particular disk drive
File list box Draws a file list box that displays files in a specific
directory
22
Data control Draws a control to link a program to a database file
Visual Basic's main selling point is the ease with which it allows the user to
create nice looking, graphical programs with little coding by the
programmer, unlike many other languages that may take hundreds of lines
of programmer keyed code. As the programmer works in the graphical
environment, much of the program code is automatically generated by the
Visual Basic program. In order to understand how this happens it is
necessary to understand the major concepts, objects and tools used by
Visual Basic. The main object in Visual Basic is called a form. When you open
a new project, you will start with a clear form that looks similar to this :
23
from the Visual Basic "tool box" with the mouse and inserting them in the
form. Yours may look different, but the basic Visual Basic Tool Box looks like
this:
24
Finally, you can add events to your controls. Events are responses to actions
performed on controls. For example, in the "Hello world" program sample on
this page, when you click on the command button on our form the event that
is triggered is the output of the message "Hello world" to the screen. Code
must be written to create an event. You can do this in Visual Basic's code
window. Yours will look similar to this (except of course, the body of the
sub-procedure where the actions are specified):
Once the code box is open, you select the object to create an event for and
the triggering action ( such as a certain mouse action ) from the drop down
menus in the code box. You can open a code box for a particular form by
choosing it from the project window and selecting the View Code button.
The project window contains a list of objects associated with that project.
Below is an example of a project window :
Once all your objects are created, you can combine them to form a single
executable program that can be run outside of the Visual Basic environment,
in Microsoft Windows.
25
26
2.5) FEATURES OF BACKEND: MS SQL SERVER 2000
Introduction
• The OLAP Services feature available in SQL server version 7.0 is now
called SQL Server 2000 Analysis Services. The term OLAP Services has
been replaced with the term Analysis Services. Analysis Services also
includes a new data mining component. The Repository component
available in SQL Server version 7.0 is now called Microsoft SQL Server
2000 Meta Data Services. References to the component now use the term
Meta Data Services. The term repository is used only in reference to the
repository engine within Meta Data Services.
27
• When evaluating a distributed query, SQL Server interacts with the OLE
DB provider in one or more of these scenarios:
• Remote query
• Indexed access
• INSERT statement
• Pass-through queries
Features of Backend:
Feature Description
Online Restore With SQL Server 2005, database administrators are able to
perform a restore operation while an instance of SQL Server is
running. Online restore improves the availability of SQL Server
because only the data being restored is unavailable; the rest of
the database remains online and available.
Online Indexing The online index option allows concurrent modifications (updates,
Operations deletes, and inserts) to the underlying table or clustered index
data and any associated indexes during index data definition
language (DDL) execution. For example, while a clustered index
is being rebuilt, you can continue to make updates to the
underlying data and perform queries against the data.
Fast Recovery A new faster recovery option improves availability of SQL Server
databases. Administrators can reconnect to a recovering
database after the transaction log has been rolled forward.
28
Standards-based Any object, data source, or business intelligence component can
Information be exposed using standards-based protocols such as SOAP and
Access HTTP—eliminating the need for a middle-tier listener, such as IIS,
to access a Web services interface that is exposed by SQL Server
2005.
SQL Server SQL Server 2005 includes SQL Server Management Studio, a new
Management integrated suite of management tools with the functionality to
Studio develop, deploy, and troubleshoot SQL Server databases, as well
as enhancements to previous functionality.
Feature Description
Hosted Common With SQL Server 2005 developers can create database objects
Language using familiar languages such as Microsoft Visual C# .NET and
Runtime Microsoft Visual Basic .NET. Developers can also create two new
29
objects—user-defined types and aggregates.
Native XML Native XML data can be stored, queried, and indexed in a SQL
Support Server database—allowing developers to build new classes of
connected applications around Web services and across any
platform or device.
ADO.NET version From new support for SQL Types to Multiple Active Result Sets
2.0 (MARS), ADO.NET in SQL Server 2005 evolves dataset access and
manipulation to achieve greater scalability and flexibility.
Security The security model in SQL Server 2005 separate users from
Enhancements objects, provides fine-grain access, and enables greater control of
data access. Additionally, all system tables are implemented as
views, providing more control over database system objects.
Visual Studio Tight integration with Microsoft Visual Studio and the .NET
Integration Framework streamlines development and debugging of data-
driven applications. Developers can build database objects, such
as stored procedures, using any .NET language and can
seamlessly debug across .NET and Transact-SQL (TSQL)
languages.
Web Services With SQL Server 2005 developers can develop Web services in
the database tier, making SQL Server a hypertext transfer
protocol (HTTP) listener and providing a new type of data access
capability for Web services-centric applications.
30
Reports an application at design time.
Full-Text Search SQL Server 2005 supports rich, full-text search applications.
Enhancements Cataloging capabilities provide greater flexibility over what is
cataloged. Query performance and scalability have been
improved dramatically, and new management tools provide
greater insight into the full-text implementation.
System Requirements:
31
2.6) MODULES AND DESCRIPTION
LOGIN:
Allows user to enter his account by providing his ID and password to his
account. If the provided id or password is incorrect the fields are cleared and
user is asked to enter the id and password again.
32
ACCOUNT DETAILS:
This module is directed as soon as the user enters his correct id and
password. It provides the summary of all the accounts with their account
number and the balance available in each account.
TRANSACTION DETAILS:
In this module the admin can see his transaction details also information’s
such as account id, name of the user his balance in a particular account is
displayed. Moreover it displays the users past few transactions done.
33
TRANSACTION CREDIT:
In this module the bank administrator transfers money into users account
when the user wishes to deposit money. This is done after the user deposits
the amount in the bank.
TRANSACTION DEBIT:
In this module the user can transfer amount from his account to another
account. This act can be considered as the transaction to withdraw amount.
34
The balance of the client should decrease by the amount and the recipients
balance should increase by the same.
35
3) DESIGN PHASE
36
3.0) PROJECT SYSTEM ARCHITECTURE
BANKING SYSTEM
37
3.1) UML DIAGRAMS FOR ONLINE BANKING
38
USE CASE SCENARIO:
USER LOGIN:
Allows user to enter his account by providing his ID and password to his
account. If the provided id or password is incorrect the fields are cleared and
user is asked to enter the id and password again.
WITHDRAW CASH:
In this module the user can transfer amount from his account to another
account. This act can be considered as the transaction to withdraw amount.
The balance of the client should decrease by the amount and the recipients
balance should increase by the same.
DEPOSIT CASH:
In this module the bank administrator transfers money into users account
when the user wishes to deposit money. This is done after the user deposits
the amount in the bank.
TRANSACTION DETAILS:
In this module the admin can see his transaction details also information’s
such as account id, name of the user his balance in a particular account is
displayed. Moreover it displays the users past few transactions done.
ACCOUNT DETAILS:
This module is directed as soon as the user enters his correct id and
password. It provides the summary of all the accounts with their account
number and the balance available in each account.
ACCOUNT CREATION:
39
SEQUENCE DIAGRAM FOR LOGIN:
Recieve (passwrd)
validate (login details)
Return (validation result)
Recieve (passwrd)
Account Details
Request (Account Details)
Return Details
View Details
40
SEQUENCE DIAGRAM FOR TRANSACTION DETAILS:
Recieve (usrnam)
Recieve (passwrd)
validate (login details)
Return (validation result)
Transaction details
Return Details
View Details
Recieve (passwrd)
validate (login details)
Return (validation result)
Transaction deposit(ammount)
request (transaction)
update account
41
SEQUENCE DIAGRAM FOR TRANSACTION WITHDRAW:
Recieve (passwrd)
validate (login details)
Return (validation result)
Transaction withdraw(ammount)
request (transaction)
validate(amount)
update account
Display (transaction result)
Show(result)
Recieve (passwrd)
validate (login details)
Return (validation result)
Enter Details
Submit Details
42
COLLABORATION DIAGRAM FOR LOGIN:
CUSTOM
ER
1: Recieve (usrnam)
2: Recieve (passwrd)
5: Display (validation result)
CUSTOM
ER
43
COLLABORATION DIAGRAM TRANSACTION DETAIS:
CUSTOM
ER
CUSTOM
ER
1: Recieve (usrnam)
5: Display (validation result) 2: Recieve (passwrd)
10: Show(result) 6: Transaction deposit(ammount)
8: update account
44
COLLABORATION DIAGRAM FOR TRANSACTION WITHDRAW:
CUSTOM
ER
1: Recieve (usrnam)
2: Recieve (passwrd)
5: Display (validation result) 6: Transaction withdraw(ammount)
11: Show(result) 8: validate(amount)
9: update account
CUSTOM
ER
1: Recieve (usrnam)
2: Recieve (passwrd)
6: Enter Details
5: Account Creation Form
10: View Result 8: Update Database
45
ACTIVITY DIAGRAM:
46
CLASS DIAGRAM:
47
STATECHART DIAGRAM FOR LOGIN:
48
STATECHART DIAGRAM FOR TRANSACTION DETAILS:
Validation
result
Update Enter
database amount
49
STATECHART DIAGRAM FOR TRANSACTION WITHDRAW:
validate
50
3.2) DATABASE RELATIONSHIP
51
3.3) FORM DESIGNS
LOGIN:
ACCOUNT REGISTRATION:
52
DEBIT:
CREDIT:
53
ACCOUNT DETAILS:
SUMMARY:
54
4) CODING
55
4.0) SAMPLE CODING WITH DATABASE CONNECTIVITY
LOGIN:
Private Sub cmdCancel_Click()
End
End Sub
56
txtUserName.Text = ""
txtPassword.Text = ""
Else
MsgBox "Login not success", vbCritical, "Error"
End If
Else
MsgBox "No record Found", vbCritical, "Error"
txtUserName.Text = ""
txtPassword.Text = ""
End If
End If
adoconn.Close
End If
End If
End Sub
57
ACCOUNT REGISTRATION CODE:
58
End If
Else
MsgBox "Passwords doesnt match, Pls type password again", vbCritical,
"ERROR"
Text1.Text = ""
Text2.Text = ""
Text3.Text = ""
Text4.Text = ""
Text5.Text = ""
Text6.Text = ""
Text7.Text = ""
Text8.Text = ""
Text9.Text = ""
Text10.Text = ""
Text11.Text = ""
Text12.Text = ""
Text13.Text = ""
Text14.Text = ""
Combo1.Text = ""
Combo2.Text = ""
End If
Exit Sub
End Sub
DEBIT CODE:
59
adoconn.Open
Dim adorecset As ADODB.Recordset
Dim adorecset1 As ADODB.Recordset
Set adorecset = New ADODB.Recordset
Set adorecset1 = New ADODB.Recordset
adorecset.Open "summary", adoconn, adOpenDynamic, adLockOptimistic,
adCmdTable
adorecset1.Open "balance", adoconn, adOpenDynamic, adLockOptimistic,
adCmdTable
adorecset.AddNew
If (Text5.Text = "" Or Text7.Text = "" Or Text8.Text = "") Then
MsgBox "Enter the missing details", vbCritical
Text5.SetFocus
Else
Text4.Text = Date
a = Text6.Text
b = Text5.Text
If (b > a) Then
MsgBox "Transaction cannot be done"
Else
n=a-b
Y = Val(Text17.Text) + b
Text18.Text = Text8.Text
Dim c As Integer
Adodc2.Recordset.MoveFirst
Do While Adodc2.Recordset.EOF = False
c=0
If (Adodc2.Recordset.Fields("accno") = Text8.Text) Then
c=1
Exit Do
Else
Adodc2.Recordset.MoveNext
End If
Loop
If c = 1 Then
Text19.Text = Adodc2.Recordset.Fields(1)
z = Text19.Text + b
Adodc2.Recordset.Fields(0) = Text18.Text
Adodc2.Recordset.Fields(1) = z
Dim s As Integer
Adodc1.Recordset.MoveFirst
Do While Adodc1.Recordset.EOF = False
s=0
If (Adodc1.Recordset.Fields("toaccno") = Text8.Text) Then
s=1
Exit Do
60
Else
Adodc1.Recordset.MoveNext
End If
Loop
If s = 1 Then
Adodc1.Recordset.AddNew
Adodc1.Recordset.Fields(0) = Text8.Text
Adodc1.Recordset.Fields(1) = Text9.Text
Adodc1.Recordset.Fields(2) = Text4.Text
Adodc1.Recordset.Fields(3) = Text5.Text
Adodc1.Recordset.Fields(4) = "Credit"
Adodc1.Recordset.Fields(5) = z
adorecset.Fields("balance") = n
adorecset1.Fields("balance") = n
adorecset("accno") = Text9.Text
adorecset("toaccno") = Text8.Text
adorecset("date") = Text4.Text
adorecset("amount") = Text5.Text
adorecset("transaction") = Text15.Text
adorecset.Update
adorecset1.Update
Adodc1.Recordset.Update
Adodc2.Recordset.Update
MsgBox "your transaction successfully done", vbInformation
Text6.Text = n
Adodc1.Refresh
Adodc2.Refresh
End If
End If
End If
End If
End Sub
61
CREDIT CODE:
62
63
5) SOFTWARE TESTING
64
5.0) SOFTWARE TESTING AND QUALITY ASSURANCE
SOFTWARE TESTING:
Software testing is an investigation conducted to provide stakeholders with
information about the quality of the product or service under test. Software
testing also provides an objective, independent view of the software to allow
the business to appreciate and understand the risks at implementation of the
software. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs.
Software testing can also be stated as the process of validating and verifying
that a software program/application/product:
Test Strategy:
• Specific
• Practical
• Justified
65
The purpose of a test strategy is to clarify the major tasks and challenges of
the test project. Test Approach and Test Architecture are other terms
commonly used to describe what I’m calling test strategy.
Different software development models will focus the test effort at different
points in the development process. Newer development models, such
as Agile, often employ test driven development and place an increased
portion of the testing in the hands of the developer, before it reaches a
formal team of testers. In a more traditional model, most of the test
execution occurs after the requirements have been defined and the coding
process has been completed.
• A good test case is one that has a high probability of finding an as yet
undiscovered error.
66
67
QUALITY ASSURANCE:
The QA toolbox is filled with things that make validation possible and easier.
It includes automated testing tools and the skills necessary to
validate APPLICATIONS, database values, and workflows when there is no
easy way to validate the correct answer.
Every test script in every test case must be run by hand. This process is
often exhausting but necessary to validate both the software being
developed but also the test scripts themselves. Screen capture utilities and
screen annotation tools can be very helpful in the process of communicating
the errors.
. These tools allow you to run a test script without the need to be manually
banging out keys on a keyboard or clicks of a mouse. These tools come with
recording software to allow you to record a set of steps and convert it into a
scripting language. The scripting language allows the steps to be
customized. By customizing the script from the recorded script it is possible
to parameterize the set of steps so that different data can be used. At least
one automated testing suite should be in your arsenal if you're a serious QA
professional.
Never was it more true that each role is met with good things, bad things,
and truly ugly things as it is in the QA role.
The role in the right environment is a shining example of how one person, or
a few people, can make an impact. However, in the wrong situation it can
leave someone bitter, frustrated, and burnt out. Here are just a few of the
good, bad, and ugly things about the QA role.
68
• Good Involvement - Because all aspects of a system have to be
assured for quality, the QA role often allows a person to be involved in
many phases of a project, including the early ones.
• Bad: Don't shoot the messenger - One of the challenges is that the QA
role is designed to be the bearer of bad news. Because of this it's easy
for others on the software development team to develop a negative
attitude towards the QA professional. That means a lot of work on the
QA professional part to keep everyone in a positive frame of mind.
• Ugly: Balancing the amount of testing done - The ugly part of the QA
role is realizing that there's only a certain amount of quality that is
appropriate for any given program. Some programs, such as those
dealing with life or death situations, require substantial testing.
However, many of the systems that we operate with today are not life-
and-death situations and require only an appropriate level of quality
assurance. The ugly part is that no two people will draw the line; on
how much quality assurance must be done, in the same place.
Testing generally occurs after other things are done. This means that
testing is often close to the deadline of when something is due to be
completed. If others are late in completing their tasks, the QA person
may have their time squeeze d to near nothing.
The quality assurance role is one of the most undervalued and potentially
impact roles in the software development process.
Despite the public failures of software there is little progress in making the
quality assurance role takes its rightful position of importance. Cost
constraints are forcing organizations of all sizes to release earlier and earlier
betas that encourage users to find the quality problems of the software on
their own. In order for the software development industry to gain the
professional respect it needs the position of the quality assurance role must
be elevated.
These standards exist because many large organizations will not buy from
suppliers who cannot give them assurance that they have system which
support quality.
Names of QA Standards:
69
ISO 9001-Quality systems-Model for Quality assurance etc.
70
5.1) TESTING METHODOLOGIES
Testing is a process used to help identify the correctness, completeness and
quality of developed computer software. With that in mind, testing can never
completely establish the correctness of computer software.
• A good test case is one that has a high probability of finding an as yet
undiscovered error.
TYPES OF TESTING:
STATIC TESTING:
The Verification activities fall into the category of Static Testing. During static
testing, you have a checklist to check whether the work you are doing is
going as per the set standards of the organization. These standards can be
for Coding, Integrating and Deployment. Reviews, Inspection's and
Walkthrough's are static testing methodologies.
71
DYNAMIC TESTING:
Dynamic Testing involves working with the software, giving input values and
checking if the output is as expected. These are the Validation activities. Unit
Tests, Integration Tests, System Tests and Acceptance Tests are few of the
Dynamic Testing methodologies.
Knowing the specific function the product has been designed to perform,
tests can be planned and conducted to demonstrate that each function is
fully operational, and to find and correct the errors in it.
Black-box tests are used to demonstrate that the software functions are
operational; that input is properly accepted and output is correctly produced;
and that the integrity of external information (e.g., data files) is maintained.
It enables the developer to derive sets of input conditions (test cases) that
will fully exercise all functional requirements for a program.
It is the test method in which the user always test the application
functionality he need not to bother about the application structure because
of the customer always looks at the screens how it is developed. Usually Test
Engineer will do the Black Box Testing.
72
Knowing the internal working of a product, tests can be conducted to
ensure that the internal operation performs according to specification and all
internal components are being adequately exercised and in the process,
errors if any are eliminated.
Unfortunately, even for few LOC, the numbers of paths become too many
and present certain logistic problems. Due to this, a limited number of
important logical paths can be selected and exercised. Important data
structures can be probed for validity.
White box testing is a test case design method that uses the control
structure of the procedural design to derive test cases.
White box testing needs to be adopted under Unit level testing strategy. It
can be adapted to a limited extent under integration testing if situation
warrants for it. Basis path testing and control structure testing are some of
the most widely used white-box testing techniques.
REQUIREMENTS TESTING:
73
apprenticing, data analysis and many other techniques, we try to snare all of
the requirements in our net.
REGRESSION TESTING:
PARALLEL TESTING:
As a test engineer, you may have explored ways to enhance test system
performance in the past though parallel testing. However, the latest off-the-
shelf test management software tools simplify parallel test system
implementation. These tools increase test throughput and drive down
test system costs.
VOLUME TESTING:
Volume Testing belongs to the group of non-functional tests, which are often
misunderstood and/or used interchangeably. Volume testing refers to testing
a software application for a certain data volume. This volume can in generic
terms be the database size or it could also be the size of an interface file that
is the subject of volume testing. For example, if you want to volume test
your application with a specific database size, you will explode your
database to that size and then test the application's performance on it.
74
STRESS TESTING:
Stress testing deals with the quality of the application in the environment.
The idea is to create an environment more demanding of
the application than the application would experience under normal
workloads. This is the hardest and most complex category of testing to
accomplish and it requires a joint effort from all teams.
Race conditions and memory leaks are often found under stress testing. A
race condition is a conflict between at least two tests. Each test works
correctly when done in isolation. When the two tests are run in parallel, one
or both of the tests fail. This is usually due to an incorrectly managed lock.
A memory leak happens when a test leaves allocated memory behind and
does not correctly return the memory to the memory allocation scheme. The
test seems to run correctly, but after being exercised several times,
available memory is reduced until the system fails.
PERFORMANCE TESTING:
• How much updating should be done to the database server over the
network from the client workstation?
According to Hamilton, the performance problems are most often the result
of the client or server being configured inappropriately. The best strategy for
improving client-sever performance is a three-step process. First, execute
controlled performance tests that collect the data about volume, stress, and
loading tests. Second, analyze the collected data. Third, examine and tune
75
the database queries and, if necessary, provide temporary data storage on
the client while the application is executing.
76
5.2) TEST PLAN
Test Plan is the schedule for entire Testing process. The Test Plan describes
the approach to all development, unit, integration, system, qualification and
acceptance testing needed to complete a project properly. You should be
aware that many people use the term 'test plan' to describe a document
detailing individual tests for a component of a system. We are introducing
the concept of high level test plans to show that there are a lot more
activities involved in effective testing than just writing test cases. Test plan
involves the following stages they are
Test Design:
77
Test Case Format:
During test design, test enggs are preparing test case documents in IEEE
format.
• Test Procedure *: Step by step procedure from base state to end state
• Test Case Pass or Fail Criteria : When this case is pass, when this is
case is fail?
Test Execution:
After completion of all possible test cases writing for responsible modules
and their review, testing team concentrate on test execution to detect defect
in build.
78
• Identify application's higher-risk aspects, set priorities, and determine
scope and limitations of tests
• Perform tests
• Retest as needed
• Maintain and update test plans, test cases, test environment, and
testware through life cycle
79
Feasibility Study : A process that determines whether the solution under
analysis is achievable, given the organization's resources and constraints.
Ad Hoc Testing: A testing phase where the tester tries to 'break' the
system by randomly trying the system's functionality. Can include negative
testing.
80
Acceptance Testing: Testing conducted to enable a user/customer to
determine whether to accept a software product. Normally performed to
validate the software meets a set of agreed acceptance criteria.
81
5.3 TEST CASE TEMPLATE
82
into users be credited credited with the
account. with the amount
amount
83
84
6) MAINTENANCE
85
6.0) MAINTENANCE AND ITS TYPES
MAINTENANCE TYPES:
1.Breakdown maintenance
It means that people waits until equipment fails and repair it. Such a thing
could be used when the equipment failure does not significantly affect the
operation or production or generate any significant loss other than repair
cost.
This is a method in which the service life of important part is predicted based
on inspection or diagnosis, in order to use the parts to the limit of their
service life. Compared to periodic maintenance, predictive maintenance is
condition based maintenance. It manages trend values, by measuring and
analyzing data about deterioration and employs a surveillance system,
86
designed to monitor conditions through an on-line system.
87
6.1 INCREMENTAL DEVELOPMENT – SOFTWARE
MAINTENANCE
88
6.2 MAINTENANCE COST IN SOFTWARE DEVELOPMENT
Software Life Cycle
Requirement Analysis
(3%)
Specification (3%)
Development
Design (5%)
Coding (7%)
Testing (15%)
Operations and
Production Phase
Maintenance (67%)
89
7) CONCLUSION
7.0) CONCLUSION
90
As the world becomes more of a global village being ruined by paperless
systems, the idea of a cashless society is the hope of the future. Thus more
innovations will still evolve which will make cashless transactions easily
accessible and affordable.
“Banking Software " keeps the day by day tally record as a complete banking
system. It can keep the information of bank employee, transactions, loan
solution, ATM information and account information. The exciting part of this
project is; it displays the employee details, payment details, loan details and
transaction details.
91
8) Reference
1. Ayo Charles. K and Babajide Daniel O, 2006, Designing a Reliable
Epayment System
2. www.google.com
3. www.wilkipedia.com
4. www.scribd.com
5. www.onestoptesting.com
6. www.softwaretestinghelp.com
92
APPENDIX-A-SCREENSHOTS
LOGIN:
REGISTRATION:
93
CREDIT:
DEBIT:
94
SUMMARY:
95
APPENDIX 2-DATABASE TABLES
LOGIN:
BALANCE:
96
REGISTRATION:
SUMMARY:
97
98