1. Write a short note on Software Testing process.

Software testing may be defined as a process whose objective is to find the problem in implementation of a
program. Execution of this program is very much needed for the software project. According to IEEE testing
means, the process of exercise or evaluating a system or its component by manual or automated means to
Audit about the necessary needs completed by software testing.
Get the value of difference between proposed result and actual result.
For making the simple process of software testing it is required that activities are broken in small size.
Generally this method is used and system is divided in sub systems. All those sub system tested individually
before the process of system testing start. Under the process of software testing three steps are taken.
Individual module is the main part of focus during unit testing step. After the unit testing, all individual
modules are combined with each other. After this step software testing process start and developer have focus
on complete software system.
Unit testing
This is the first step of the process of software testing and on this step programmer confirm about the function
performed by the module. The software have smallest unit which is called module. After the development of
source code unit testing start and it verifies for the right syntax. The primary goal of the unit testing is to get
the minimum unit which will be able to taste and confirm that it works or not. Every single module tested
separately. After testing all individual modules are combined with each other. Some tests are taken under the
process of unit testing process which is:
Nature test of module - In the test of a module nature we verify that the flow of information is
positive in tested module under that situation which is specified for the unit test.
Performable test - This checkout point have the objective to calculate the time period of response,
started time, last time and during the whole process time and communication between links.
Local data structure test - Storage of local data is checked under this step that all the data and
information collected in systematic way or not.
Boundary test - This test is performed for the surety that the information provided by the software is
true or not under those conditions which are given by the users.
Independent path test - Under this test it is checked that the given task is properly executed or not and
working ok. Only with the help of this test can check it.
Error handling test - The error which occurred during the process is properly handled or not. This
type of information provided under this test.
Process of unit testing
In the process of unit testing there is need to required data or information about other module. With the help of
driver and stubs we can easily get. A programmer which gives the test and passes it to where module tested is
called driver. Which programs used to replace module and subordinates of the module being tested is called
stubs. Stubs and driver are the need of unit testing process. Quantity of stubs and drives can be reduced if they
have the quality of simplicity.

Integration test
Integration testing is the next step of software testing. In this test much kind of modules which are individual
tested are combined with each other in to subsystem which is then tested. The main objective of unit testing is
to get the information about the independent module working condition is positive but the main drawback of
unit testing has no such condition which gives the guaranty that these modules provide the positive result after
the attachment as a whole system. So this is reason of performing integration test. We need to check following
errors which can affect the integration of module.

Outside data can create the problem.

Out of module testing could be away from the expectation.
It is possible that integration result is not in favor of that process or module.
Generally integration testing has use two method.
Top down Integration Testing
This type of method has a wide area of thought. It's needed a high level module after testing and integrated
first. Under this approach module replaced and providing new stubs. This process continues at that level till
time it integrates all modules and tested. In this approach high level logic and flow of data used which decrease
the drivers need.

BENEFITS

Firstly up level modules tested.

Both approach "breadth and depth" supported.

One driver at the most is required.

DRAW BACKS

Low level modules take long time for verification.

Not proper data find in the stub for feedback in the favor of calling module.

Level of supporting is low for the limited functionality.

Complicates test management required for the stub.

Bottom up Integration Testing

This approach gives the importance to lower level modules. In this level modules tests first and with the help
of a driver integrated first. We can add one or more modules combined or jointed with each other. After the
integration of all the modules this process became closed.

BENEFITS

When we start this process with actual module then stubs not required.

Low level module verified early in this approach.

DRAW BACKS

Complicates test management required for drivers.

Release of limited functionality supported by low level.

Verification of high level module time taken.

System testing
The system testing process is the base of a software system. The main objective of system testing is that the
software satisfied the client requirement. System testing is a series of that entire test with fully exercise which
base is computer system. Every task has a separate objective and series of different test its clear that all part of
system are combined with a systematic way and doing their work very well. There are three types of testing in
system testing.
1. Recovery Testing - The base of designed in Recovery testing is that type we can observed easily that
how much quick a system covers its points if the system became fail. We have many kind of program
which recovers quickly from the errors and started at time or operated at given time. A fault has much
cause but recovery testing clarified that system covered all fault and performing well. A human always
desired that a system have the capacity to recover very fast without human touch. The recovery system
determined that the repair condition is acceptable or not.
2. Security testing
o

A protective application made in software, with the help of this application it provide safety
from local and those person who have not right to use the system.

With the help of security testing other computer cannot get the benefit to access this and its
information.

3. Stress testing - Stress testing cannot be performed in normal condition. With the help of this a system
use in that condition when demand increased or decreased quickly.
o

How a input function performed when the speed of input became more than expectations.

More excessive search and hunting of data on click is also involved in stress testing.

2. Explain the term Configuration management.

Software configuration management, SCM is an activity which is used at every level and every part of the
process of software Engineering. Every improvement takes the shape of better control. This is a discipline
which controls betters and according to client need in software Engineering. With the help of this many types
are changes which play an important role in software Engineering and development process.
In the simple way if we define the term configuration of management, this is the tool which makes better
control, easy maintenance during the whole process of software development. With the help of software
configuration management we can easily find out what modification and controlling required by the developer.
SCM have the capacity to control all those effects which comes in software projects. The main objectives of
SCM is increase the production by reduce the errors.
When a software development process start then SCM take change by identification, control, alteration, audit
and etc. after that the output of total process provided to our customer. We can clarify the action of SCM as:
1. Software configuration identification - Normally software is used in various kinds of programs and
documentation and data related to each program is called configuration identification. With the help of
C.I we can make a guide line which will be helpful in software development process, several time the
requirement of guideline for check the document and design of software. Document related to SCM are
the useful item, with the help of this we can make better control and take a basic unit for configuration.
2. Software configuration control - This is the process of deciding with the help of this we make
coordination between the changes which is necessary and apply them as per mentioned in guideline.
Configuration control board gives the permission for any kind of change or modification which is
necessary for the project. Many times CCB take advice of those members which are the part of
software development process.
3. Accounting status of Software configuration - The process of maintaining record of all data which is
necessary for the software is called accounting status of software. It has all the data related to the old
software to new software that what changes are done or required for the fulfillment of the customer
need.
4. Auditing of software configuration - Auditing of software configuration is may be defined as an art
with the help of this we can understand that the required actions or changes are done by the developer
or not. Some of the item involved in the process of verifying or auditing.
o

Function is properly performed by the software.

The process of documentation, data is completed or not.

Benefits
o

With the help of SCM we can easily control all changes which are done in development
process.

It gives the surety to check that changes are done on required area.

It is helpful to generate the new software with old components.

SCM has the capacity to explain everything about the process of software development.

3. What are the differences between verification and validation in software development?
Sr.No
.

Verification

This is process of deciding that the

1

product on particular step of the

software development meets the
expected need.

This is process of deciding that the

valuation of the software at the end of the
process is as per the actual need.

Verification includes valuations in

Validation includes actual test results and

terms of plan, code, need and quality.

use of software when verification process

Checklist and inspection are part of it.

gets completed.

Verification decides that result of one

3

Validation

phase of development confirms the ok

status of previous phase.

Validation decides that developed product

meets required needs.

Verification insures that process makes Validation insures that software being
4

quality product at every stage of

developed fulfills functional as well as non-

software development.

functional needs.

Verification is done at each step and it

5

provides the assurance of regularity

with the end result of previous phase.

Validation process insures that user needs

are covered completely.