Project Report Sample Last Part (Test Plan, Testing Methods, Levels of Testing, Testing of Forms, Debugging, Implementation, Implementation Tools, Software Maintenance, Project Legacy, Future recommendations, Conclusion, Bibliography)
System
Testing
INTRODUCTION:
During earlier development phases an
attempt is made to build software from an abstract concept to tangible
implementation. Software testing is a critical element of software quality
assurance and represents ultimate review of specification; design and coding
notion of “correctness” of the software just developed and overcome a conflict
of interest that occur sheen errors are recovered. A thorough testing of system
before any implementation is mandatory. This is because implementing a new
system is a major job, which requires a lot of man-hours and other resources,
so an error not detected before implementation may cost a lot. Effective
testing early in a process is also necessary because in some cases a small
error not detected and corrected early before installation may explore into
much large problems.
After programming and testing comes
the stage of installing the computerized system. It has the enormous
responsibilities of detecting any type of error that may be in the software.
Actual implementation of the system can begin at this point using either of
parallel or direct change over plan or a blend of the two.
Programmers often do all these
factors mean that testing cannot be done on the fly, as. It has to be carefully
planned and the plan has to be properly executed. The testing process focuses
on how testing should proceed for a particular project.
Testing the system:
Testing can be done with two types of data. Live data and
test data.
- Live Data: Live data is the data actually to be used in the proposed system.
- Test Data: Test data is previously designed sample input to achieve predictable results.
Test Objective:
- Testing is a process of execution a program with the intent of finding error.
- A good test case is one that has a high portability of finding an undiscovered error.
- A successful test is one that uncovers an as-yet-discovered error.
Testing Principles:
- All tests should be traceable to customer requirements.
- Test should be planned long before testing begins.
- Testing should begin” in small” and progress towards testing in the large.
- To be most effective an independent third party should conduct testing.
Test Plan:
The first step
in the system testing is to prepare a plan that will retest all aspects of the
system in a way that promotes its credibility among potential users. There is a
psychology in testing:
- Programmers usually do a better job in unit testing because they are expected to do documentation and prepare report on the method and extent of their testing.
- Programmers are involved when they become aware of the user problems and expectations.
Testing Methods
White box testing:
White box
testing of software is predicated on close examination of procedural details.
Providing test cases that exercise specific sets of conditions and loop tests
logical is a test case design method that uses the control structure of the
procedural design to derive test cases.
- Guarantee that all independent paths within module have been exercised at least once.
- Exercise all logical decisions on their true and false sides. Execute all loops at their boundaries and within their operational bounds.
- Exercise internal data structures to assure their validity.
- The errors that can be encountered while conducting white box testing are logic errors incorrect assumptions or typographical errors.
Black box testing:
Black box
testing is carried out check the functionality of the various modules. Although
they are designed to uncover error black box testing use to demonstrate that
software function are optional that input is corrected accepted and output is
corrected produced and that the integrity of the external information is
maintained. A black box test examines some fundamental aspects of the system
with little regard for the internal logical structure of the software.
- Incorrect or missing function
- Interface errors
- Errors in data structure or external database access.
- Performance errors
- Initialization and termination errors.
Levels of Testing
A strategy for s/w testing integrates s/w test case designs methods in
well-planned series of steps that results in the successful construction
software. An important software testing planned in advance and conducted
systematically. Verification is performed on the output of each phase but some
faults are likely to remain undetected by these methods. These faults will be
eventually reflected in the code. Testing is usually relied on to detect these
faults, in addition to the faults introduced during the coding phase it self.
Due to this different levels of testing are used in the testing process; each
level of testing aims to test different aspects of the system.
|
|
 |
|||||
 |
 |
||||
 |
 |
 |
|||||
 |
|
||||
|
|
 |
- Unit Testing:
This is the first level of testing. In this
different modules are tested against the specifications produced during design
for the modules. Unit testing is essential for verification of the code
produces during the coding phase, and hence the goal is to test the internal
logic of the modules. The programmers of the module typically do it. Others
consider a module for integration and use only after it has been unit tested
satisfactorily. Due to its close association with coding the coding phase is
frequently called “coding & unit testing”. As the focus of this testing
level is on testing the code structured testing is best suited for this level.
- Structural Testing:
It is an approach to testing where the tests are derived from knowledge
of the software’s structure and implementation this approach can analyze the
close and use knowledge about the structure of a component to derive test data.
The analysis of the code can be used to find how many test cases are needed to
guarantee that all of the statements in the program or components are executed
at least once during the testing process.
 |
Tests Derives
 |
 |
||
Component
Test Outputs
Code
- Integration Testing:
Integration Testing is the next level of testing. In this many
unit-tested modules are combined into subsystems, which are then tested. The
goal here is to see if the modules can be integrated properly. Hence the
emphasis is on testing interfaces between modules. This testing activity can be
considered testing the design.
- System and Acceptance Testing:
The next levels are system testing & acceptances testing. Here the
entire software system is tested. The reference document for this purpose is
the requirements document and the goal is to see if the software meets its
requirements. This is essentially a validation exercise, and in many situations
it is the only validation activity. Acceptance testing is sometimes performed
with realistic data of the client to determine that the software is working
satisfactorily. Testing here focus on the external behavior of the system; the
internal logic of the program is not emphasized.
Activity Network for System Testing:
Test plan entails
the following activities:
ü Prepare
Test Plan
ü Specify
conditions for User Acceptance Testing.
ü Prepare
Test Data for Program Testing.
ü Prepare
Test Data for Transaction Path Testing.
ü Plan
User Training.
ü Compile/Assemble
Programs
ü Prepare
job performance aids
ü Prepare
operational documents.
Testing of Forms
Forms are the
interface between the user and database system. Testing of forms was extensive
task. All data entry and query formats are designed using forms. Forms were
tested to ensure that they are performing the tasks well they are designed for
and correction and modification we made found to be necessary.
System testing
is designed to uncover weakness that was not found in the earlier tests. This
includes forced system failure and its users in the operational environment
will implement validation of the total system as it is. The total system is
tested for recovery and fallback after various major failures to ensure that
data lost during the emergency is retained. All this is done with the old
system still in operation.
After a
successful testing of the individual programs and forms the whole system was
through a series of test to ensure the proper working of the system as a whole.
The activities involved in the
system testing are:
Ø Integration
Testing
Ø Acceptance
Testing
In integration testing the entire
system is tested and acceptance testing involves planning and execution of
functional tests, implemented system satisfied its requirements.
Security
Test:
The functional environment of the system posed no real security threat
but the system was developed considering the entire data to be highly critical
and thus denying free access to anyone without proper access rights. The entire
system is password protected and session id is given to each user, which is
carried by him throughout his working on the site.
Debugging:
Programmers carry out some testing of the code they have developed. This
often reveals program defects that must be removed from the program. This is
called Debugging. Debugging is concerned with locating and correcting these
defects. The debugging process is often integrated with other verification and
validation activities. There is no simple method for debugging. Skilled
debugging looks for patterns in the tested output where the defect is exhibited
and uses knowledge of the type of defect. It uses the programming language and
the programming process to locate the defect.
The Debugging Process:
|
|
|
 |
|
||||
 |
|||||
 |
Implementation
Of
Project
INTRODUCTION:
An important
aspect of a system analyst’s job is to make sure that the new design is
implements to established standards. The term implementation has different
meaning, ranging from the conversion of a basic application to a complete
replacement of a computer system application. Implementation means a process of
converting a new or a revised system design into an operational one. Conversion
is one aspect of implementation. The other aspects are the post implementation
view and software maintenance. There are three types of implementation:
Ø
Implementation of a computer system to replace a
manual system.
Ø
Implementation of a new computer system to
replace an existing one.
Ø
Implementation of a modified application to
replace an existing one using the same computer.
Implementation tools:
The developed
system will be implemented on the administrator’s side that can give rights to
other users and can do modification and on user’s side because he has to make
the ultimate queries either for sell or buy or renting a house. The various
phases of implementing new system are as following:
·
Conversion:
This means the
changing from one system to another. The objective is to put the tested system
into operation. The method adopted for conversion of this system is parallel
system. Under this method both the system old and new are operated parallel.
This is the safest method. Error can be prime concern during the conversion
this will be done on site. The data will be entered to the database from the
existing registers.
·
Training:
The quality or
training received by the personnel involved with the system in various
capacities helps or hinders, and may even prevent the successful implementation
of an information system. Those who will be associated with or affected by the
system need to be trained. Training the personnel will be in house. The user of
the system will be trained that what the system can be and what cannot.
·
Post Implementation Review:
After the system
is implemented and conversion is complete a review of the system of the system
will be done. It is a formal process to determine how well the system is
working how it has been accepted and whether adjustments are needed.
Software Maintenance:
Maintenance is the enigma of system development. It holds the software
industry captive tying up programming resource. Analysts and programmers spend
far more time maintaining programs than they do writing them. The environment
is the supra system within which an organization operates. It is the source of
the external elements that impinge on the system. Infect it often determines
how a system must function. Though maintenance is not considered a part of
software development, it is activity an extremely important in the life of
software product. Maintenance is one form of change or software development is
completed and the software has been deployed.
System maintenance can be
classified into three types of activities. These are as following:
Ø Corrective
maintenance: -
Almost software that is developed has residual errors, or bugs, in them.
Many of these surfaces only after the system have been in operation, sometimes
for long time. These errors once discovered need to be removed leading to the
software getting changed.
Ø Perfective
maintenance: -
Sometime changes have to be done according to user’s requirement. This
type of changes to the software is called perfective maintenance.
Ø Adaptive
maintenance: -
Software often must be upgraded and enhanced to include more features
and provide more services. This also requires modification of software. The
change in environment by deploying the software also leads to changes in the
software.
Future recommendations:
Ø Online
Ø Use new technology.
Ø Use new more short coding method in JAVA language for this
software.
Ø Modification in Customer Requirements.
Ø Modification in Database.
Ø More User friendly.
Ø More Robust.
Ø Maintain all Property Dealing process.
Ø Add updated deals for ease of customer.
Ø Add Multimedia in this project.
CONCLUSION
The computerized
version of the existing system of the company will be able to serve its client
and prospective clients in a more efficient manner, as this would save
tremendous time energy and effort of doing such tedious tiring and repetitive
paperwork.
It will be designed to offer
easy accessible to all records to provide better maintainability and to enable
the user to make the required modification as and when necessary.
Execution of
this project would enable the user to seek, use and manipulation the records
pertaining to nay and every client. This project would, in short, increment the
efficiency and the quality and quantity of productivity of the organization as
well as decrement the work effort, energy and duration of time required by user
staff.
Bibliography
Sr. No.
Name of the Book Author’s Name
- Complete Reference of Java Herbert Shield
- Project Management John M. Nicholas
- MS-SQL Server 2000 Microsoft
- System Analysis and Design Elias M. Awad.
Websites:
Comments
Post a Comment