November-2018

Q.1)

c) Short Answer- Define the following :-

1. Quality:- Software quality is defined as a field of study and practice that describes the
desirable attributes of software products. There are two main approaches to software quality:
defect management and quality attributes.

2. Software Testing:- Software testing is the process of evaluating and verifying that a
software product or application does what it is supposed to do. The benefits of testing
include preventing bugs, reducing development costs and improving performance.

3. Quality Assurance :- Quality Assurance is the maintenance of a desired level of quality

in an application or software by means of giving attention to every stage of the software
development process.

4. Defect Reporting :- Defect report communicate the issue to the development team .
When a defect is first report it need not always be a valid defect, it can be misunderstanding
of requirement by the tester or a change request which was not documented. Therefore it is
important to be brought to the developer’s attention.

5. Software Safety :- i)Defined as software quality assurance activity that focuses on

identifying potential hazards that may cause a software system to fail.

ii)early identification of software hazards allows developer to specify design features can
eliminate or at least control the impact of potential hazards.

Q.2) Attempt the following (Any three ) (each of 5 marks)

a) Explain any five desirable software qualities

Ans:-.

b) Give the concept of software reviews, Inspection and Walkthrough.

Ans :- Software review:-

i) Reviews can formal or in formal . In an in formal review there are no fixed phase or
process, it is conducted to get a feedback from colleagues about a work product .

ii) In contrast to informal review, formal review has a fixed process. A typical formal review
consist of six main steps:

Software Review Steps:

1. Planning

2. Kick-off

3. Preparation

4. Review Meeting

a) Logging phase

b) Discussion

c) Decision

5. Rework

6. Follow-up

1.Planning :-Planning is the first step of formal review .Review is generally initiated by author
Who put in request for review of a document or any other artifact . Moderator has to take
care of the scheduling like date, time ,place invitation of the review.

2. Kick-off :- This is an optional step .The main of this meeting to get everyday on the same
page regarding the document and decide on the time to be sent reviewing. Entry and exit
criteria are also discussed.

3. Preparation:- The participant work individually on the document under review using : the
related document , procedures, rules and checklists provided.

4. Review Meeting :-

a) Logging Phase : All the defect and issues that have been identified during the
preparation step are recorded page by page by the author or the scribe. Every defect
and its severity should be logged . Three severity classes should be considered while
logging every defect i.e. Critical, Major, Minor . Meeting the logging rate in the formal
review should be between one to two defect logged per minute.

b) Discussion Phase : If any issue needs discussion than that issue is handled in
this phase .It is the responsibility of the moderator to take care of people issue and
prevent the discussion from getting personal and aggressive .

c) Decision Phase : A decision has to be made by the participant on the document

under review at the end of the meeting, sometimes based on exit criteria (average
number of critical defect found per page).
5.Rework :- in this stage, if the number of defect found in each page exceeds the certain
level than the document has to be reworked. It is the responsibility of the author to judge
whether the defect needs to be fixed because not every defect leads to rework .

6. Follow-up :- the moderator is responsible for ensuring that satisfactory action have been
taken on all (logged) defects, process improvement suggestion and change requests.

Inspection :-

i) It is the most formal type of review . During inspection the document are prepared and
checked thoroughly by reviewers before the meeting .

ii) A separate preparation is carried out which the product is examined and the defects are
found . The defects found are document in a logging list or issue log.

Walkthrough :-

i) This is a process where the authors of the document as well as other associates are
gathered at one place to discuss the document to achieve a common understanding and
gather feedback .

ii) In walkthrough the author does most of the study of the document and the participant are
not expected to know the document in advance. The participant are selected from different
department and background so that they can bring in different viewpoints.

c) List Black Box Testing Types. Explain any two.

Ans:-

Black box testing involves testing a system with no prior knowledge of its internal workings.
A tester provides an input, and observes the output generated by the system under test. This
makes it possible to identify how the system responds to expected and unexpected user
actions, its response time, usability issues and reliability issues.

Types Of Black Box Testing

Black box testing can be applied to three main types of tests: functional, non-functional, and
regression testing.

Functional Testing:-

Black box testing can test specific functions or features of the software under test. For
example, checking that it is possible to log in using correct user credentials, and not possible
to log in using wrong credentials.

Functional testing can focus on the most critical aspects of the software (smoke
testing/sanity testing), on integration between key components (integration testing), or on the
system as a whole (system testing).
Non-Functional Testing:-

Black box testing can check additional aspects of the software, beyond features and
functionality. A non-functional test does not check “if” the software can perform a specific
action but “how” it performs that action.

Black box tests can uncover if software is:

● Usable and easy to understand for its users

● Performant under expected or peak loads
● Compatible with relevant devices, screen sizes, browsers or operating systems
● Exposed to security vulnerabilities or common security threats

Regression Testing:-

Black box testing can be used to check if a new version of the software exhibits a
regression, or degradation in capabilities, from one version to the next. Regression testing
can be applied to functional aspects of the software (for example, a specific feature no
longer works as expected in the new version), or non-functional aspects (for example, an
operation that performed well is very slow in the new version).

d) Discuss levels of testing .

Ans:-There are three level of testing, i.e. , three individual modules in the entire software
system.

i) Unit Testing :-

a)A Unit is a smallest testable portion of system or application which can be

compiled, liked, loaded, and executed. This kind of testing helps to test each module
separately.

b)The aim is to test each part of the software by separating it. It checks that
component are fulfilling functionalities or not. This kind of testing is performed by
developers.

ii) Integration Testing :-

a) Integration means combining. For Example, In this testing phase, different

software modules are combined and tested as a group to make sure that integrated
system is ready for system testing.

b)Integrating testing checks the data flow from one module to other modules. This
kind of testing is performed by testers.

iii) System Testing :-

a) System testing is performed on a complete, integrated system. It allows checking

system’s compliance as per the requirements. It tests the overall interaction of
components. It involves load, performance, reliability and security testing.

b)System testing most often the final test to verify that the system meets the
specification. It evaluates both functional and non-functional need for the testing.
iv) Acceptance Testing :- Acceptance testing is a test conducted to find if the requirements of
a specification or contract are met as per its delivery. Acceptance testing is basically done by
the user or customer. However, other stockholders can be involved in this process.

e) Distinguish between verification and validation .

Verification Validation

i) verification is to check whether the i) validation is to check whether the

software conforms to the specification software meets the customer expectation
and requirements.

ii) Verifying process include checking ii) It is a dynamic mechanism of testing

documents, design, codes and program and validating the actual product.

iii) It does not involve executing the code iii) It always involves executing the code.

iv) Verification use method like iv) it is use method like Black box testing,
reviews,walkthrough, inspections and desk- White box testing technique.
checking etc.

v) check “Are we building the product right v) checks” Are we building the right
“? product “?

vi) QA team does verification and make vi) With the involvement of testing team
sure that the software is as per the validation is executing on software code
requirement in the SRS document.

f) write a note on SDLC.

Ans:-

It is a framework that defines activity that are performed throughout the software
development process.

The development process adopted for a project will depend on the project aims and goals
there are numerous development lifecycles that have been developed in order to achieve
different required object.

The most appropriate development process should be applied to each project the models
specify the various stages of process and the order in which they are carried out.
Phases of SDLC

i) Requirement gathering:- this is the most important phase in software development life
cycle . In this phase requirement for the software are collected from the customer/ client.
This requirement are provided in a document called Business Requirements
Specification(BRS) or System Requires Specification(SRS).

ii)Design:- it has two step

1)HLD high level design

2)LLD low level design

HLD high level design :- it gives the architecture of the software product to be developed
and it is done by architects and senior developers

LLD low level design:- it is done by senior developer. It describes how each and every
feature in the product should work and how every component should work. Here, only the
design will be there and not the code. The outcome from this phase is High Level Document
and Low Level Document which works as an input to the next phase.

iii) Coding :- It mean translating the design into a computer readable language.
Development team does the actual coding based on design software and write it unit tests
for each component to test the new code written by them. This is the longest phase of the
software development lifecycle.

iv)Testing :- After the code is developed testing is carried out to verify the entire
requirement specified by customer have been implemented. The aim of the tester is to find
out the gaps or defects within the system and also to verify that the software work as
expected according to the requirement. It include Unit testing, Integration testing and System
testing.

v)Deployment:- After successful testing the product is delivered/deployed to the customer

for their use. The size of the project will determine the complexity of deployment. The user
can be trained on, or aided with the document on how to operate the software. And small
round of testing is also performed production to make sure of any environmental issue and
any impact of new release.

vi)Maintenance:- Once when the customers start using the developed system then actual
problem will come up and need to be solved from time to time. Fixing the issue found by the
customer comes in the maintenance phase
Q.3) Attempt the following (Any three ) (each of 5 marks)

a) Write a note on Unit Testing .

Ans:-

i) Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation.
This testing methodology is done during the development process by the software
developers and sometimes QA staff. The main objective of unit testing is to isolate written
code to test and determine if it works as intended.

ii) Unit testing is an important step in the development process, because if done correctly, it
can help detect early flaws in code which may be more difficult to find in later testing stages

iii) Unit testing is a component of test-driven development (TDD), a pragmatic methodology

that takes a meticulous approach to building a product by means of continual testing and
revision. This testing method is also the first level of software testing, which is performed
before other testing methods such as integration testing. Unit tests are typically isolated to
ensure a unit does not rely on any external code or functions. Testing can be done manually
but is often automated

iv) Unit tests can be performed manually or automated. Those employing a manual method
may have an instinctual document made detailing each step in the process; however,
automated testing is the more common method to unit tests. Automated approaches
commonly use a testing framework to develop test cases. These frameworks are also set to
flag and report any failed test cases while also providing a summary of test cases.

v) Advantages and disadvantages of unit testing

Advantages to unit testing include:

● The earlier a problem is identified, the fewer compound errors occur.

● Costs of fixing a problem early can quickly outweigh the cost of fixing it later.
● Debugging processes are made easier.

Disadvantages include:

● Tests will not uncover every bug.

● Unit tests only test sets of data and its functionality—it will not catch errors in
integration.
● More lines of test code may need to be written to test one line of code—creating a
potential time investment
b) Explain categories of software Metrics.

Ans:- The three types of metrics you should collect as a part of your quality assurance
process are source code metric, Development metrics and Testing metrics.

i)Source code metrics:-

a) These are the measurement of source code that make up all your software. Source code
is the fundamental building block of which your software is made, so measuring it is the key
to making sure your code is high-caliber.( not to mention there is almost always room for
improvement). Look closely enough at even your best source code, and you might spot a
few areas that you can optimize your even better performance.

b) When measuring source code quality make sure you are looking at the number of lines of
food you have, which will ensure that you have the appropriate amount of code and it no
more complex than it needs to be,

ii) Development metrics :-

a) These matrix measure the custom software development processes itself. Gather
development metrics to look for ways to make your operation more efficient and reduce
incidents of software error.

b) Measuring number of detect with within the code and time to fix them tell you a lot about
the development process itself. start by tallying up the number of defects that appearing in
the code and note the time it take to fix them.

iii)Testing metrics :-

a) These metrics help you evaluate how functional your product is.

b) There are two major testing metrics one of them is “test coverage” that collect data about
which part of the software program are executed when it runs a test. the second part is the
test of the testing itself. Its is called “defect removal efficiency” and it checks your success
rate of for spotting and removing defect.

c) Discuss Defect Management Process in detail.

Ans:-

i) Defect is an unexpected behavior of the software. All software has some defect. 100%
defect free software is not possible. Elimination of bugs from the system depends upon how
efficiently is testing process is carried out. A defect is basically the difference between the
expected and actual result.

b) The cost of finding and correcting defect is a very expensive activity of the software
development process. defects should be found as early as possible to reduce the cost of
fixing the defect.

c) While defect may be inevitable, we can minimize their number and impact on our project.
to do this, project management team need to implement a defect management process
(DMP) that focus on preventing defect, finding defects as early as possible in the processing,
and minimizing the impact of defect.

Defect Management Process

a) Defect Prevention :- this is a process in which defects are prevented to improve the
productivity and quality of the software. As discussed earlier, it is not Possible to eliminate all
defect.

b) Deliverable Baseline :- when a deliverable i.e. system or a software reach its predefined
then the deliverable become baseline. A product should be considered baselined when
developer pass it to the testes for testing.

c) Defect Discovery :- in this phase defect are identified.

steps involved in defect discovery are:

finding a defect :- should be identified as earlier as possible before they became major

report defect:- as soon as the tester identify the defect, it should be communicated to the
development team as they have to identify and fix them

acknowledgement defect:- this development team must acknowledge the defect as start to
working on it, if it is a valid defect.

d) Defect Resolution :- once the testing team has identified and inform the development
team about the defect, development team should start work towards resolving it. the project
manager must prioritize the defect and fix it. higher priority defects are fixed first. once the
defect is fixed, the testing team should be informed so that the resolution can be tested and
verified.

e) Process Improvement :- for the improvement, everyone in the project needs to look and
back and check from where the defect was originated. based on that what you can you make
change in the validation process base-lining in document review process which may catch
defect earlier in the process where are less expensive.

d) What are Smoke Testing and its benefits ?

Ans:-

Smoke testing is a type of software testing which ensures that the major functionalities of
the application are working fine. This testing is also known as ‘Build Verification testing’. It is
a non-exhaustive testing with very limited test cases to ensure that the important features
are working fine and we are good to proceed with the detailed testing.

The term ‘smoke’ testing is originated from the hardware testing, where a device when
first switched on is tested for the smoke or fire from its components. This ensures that the
hardware’s basic components are working fine and no serious failures are found.

Similarly, when we do smoke testing of an application then this means that we are trying to
ensure that there should NOT be any major failures before giving the build for exhaustive
testing.

● The purpose of the smoke testing is to ensure that the critical functionalities
of an application are working fine.
● This is a non-exhaustive testing with very limited number of test cases.
● It is also known as Build verification testing where the build is verified by
testing the important features of the application and then declaring it as good
to go for further detailed testing.
 ● Smoke testing can be done by developers before releasing the build to the
testers and post this it is also tested by the testing team to ensure that the
build is stable enough to perform the detailed testing.
● Usually smoke testing is performed with positive scenarios and with valid
data.
● It is a type of shallow and wide testing because it covers all the basic and
important functionalities of an application.
● Usually the smoke testing is documented.
● Smoke testing is like a normal health checkup of the build of an application.

Examples for Smoke Testing

Let us assume that there is an application like ‘Student Network’ which has 15 modules.
Among them, there are 4 important components like Login page, Adding student details,
Updating it and Deleting it. As a part of smoke testing we will test the login page with valid
input. After login we will test the addition, updating and deletion of records. If all the 4 critical
components work fine then the build is stable enough to proceed with detailed testing. This
is known as Smoke testing.

Advantages of Smoke testing

· It helps in finding the bugs in the early stage of testing.

· It helps in finding the issues that got introduced by the integration of components.

Disadvantages of Smoke testing

· Smoke testing does not cover the detailed testing.

· It’s a non-exhaustive testing with small number of test cases because of which
we not are able to find the other critical issues.

e) Give the concept of the Complexity Metrics.

Ans:-

i) Complexity of a code is directly depend on the understandability of the code and relate to
ease of comprehension.

ii) All the factors that make program difficult to understand are responsible for complexity
when we analyze a program code please we find that the number of line( size), total
occurrence of operate operators and operand (size), numbers of control structure (control
flow structures), functional call (coupling) are the factor which directly affect the complexity.

iii) In general these primitives are major independently by the different complexity measure
and each one of this assumed to represent overall complexity of the software.

iv) when we look at the most of the complexity measure we can observe the close relation
between the number of lines operators and operands count, and basic control structure.
consequently this primitive of software may constite the component of unified
comprehensive complexity measure

v) In our opinion the complexity of software system depend on following factors:

a) complexity of a program depend on the size of code. Therefore, the complexity due to a
single line of code is assumed to be one unit.

b) complexity of a program depend on size of code. we suggest that the size of the code can
be measured by total occurrence of operator and operands. Therefore, the complexity due to
ith line of code can be calculated as

SOOi =Ni1 + Ni2 where

Ni1 : the total number of occurrences of operator at line i.

Ni2 : the total number of occurrences of operands at line i.

c) complexity of the program is directly proportional to the cognitive weight of basic control
structure (BSC).cognitive weight of software[19] is extended of difficulty or relative time and
effect for comprehending given software modeled by a number of basic control structure
BCS sequence branch

f) Explain Bottom-up Integration Testing.

Ans:-

i) Low level component are combined in cluster that perform a specific software function.

ii) A driver (control program) is written to coordinate test case input and output.

ii) The test test cluster is tested .

iv) Driver are removed and the cluster are combined moving upward in the program structure

v) Regression testing (check for defect propagated to other module by change made-up
two existing program).

vi) Representative samples of existing test case is used to exercise all software function .

vii) Additional test case focusing software functions like to be affected by the change.

viii)test case that focus on changed software components.

Q.4) Attempt the following (Any three ) (each of 5 marks)

a) Discuss any five guideline for formal technical review.

Ans:-

i)The guideline for conducting formal technical review must be established in advance,
disturbed to all reviewers, agreed upon and then followed.

ii) A review that is uncontrolled can often be worse than no review at all.

The following data set of guidelines for FTR:

1)Review the product, not the producer.

2)Set an agenda and maintain it

3)Limit debate and contradiction.

4)Pronounce the problem area, but don’t attempt to solve every problem noted.

5)Take written notes.

6)Limit the number of participants and insist upon advanced preparation.

7)Developer checklist for each product that is likely to be reviewed.

8)Allocate resources and schedule time for FTRs.

9)Conduct meaningful training for all reviewers.

10)Review your early review .

b) what are the advantage of ISO 9000 standards?

Ans:-

i) A quality assurance system may be defined as the organizational structure,

responsibilities, procedures, process, and resource for implementing quality management.
quality assurance systems are created to help organizations ensure their product and
service satisfy customer expectation by meeting their specifications.

ii) These system cover a wide variety of activity and encomposing a product’s entire life
cycle including planning, controlling, measuring, testing and reporting ,and improving quality
level throughout the development and manufacturing the process.

iii) ISO 9000 describe quality assurance element in generic term that can applied to any
business regardless of the product or service offered.

iv)To become registered to one of the quality assurance system model contained in ISO
9000 a companies quality system and operation are third party auditors for compliance to the
standard and for effective operation.
v) Upon successful registration, a company issued a certificate from a registration body
representation by the auditor. semiannual surveillance audit ensure continued compliance to
the standard.

vi) The requirement defined by ISO 9001:2000 address topics such as management
responsibility, quality system, contract review, design control, document and data control,
product identification traceability process control, inspection and testing, collectiveness and
preventive action, control of quality record, internal quality audit, training service, and
statistical technique.

vii) In order for a software organization to become registered to ISO 9001: 2000 its must be
established policy and procedure to address each of the requirements just noted( and
another) and then be able to demonstrate that this policy and procedure are being followed.

c)write a short notes on SQA plan.

Ans:-

i)The SQA plan service as a template for SQA activities planned for each software project.
the SQA group and the project team developed the SQA plan. the initial two section of the
plan described the purpose and a reference of the SQA plan .

ii) The next section record details of the roles and responsibility for maintaining software
product quality.

iii) the documentation section of the SQA plan describe each of the work product produced
during the software process. this section defines the minimum set of work product or
acceptable to achieve high quality.

iv) the documentation section consist of:

a) the project documents such as project plan, requirement document, test case, reports ,
user manual and administrative manual.

b) model such as ERDs, class hierarchies.

c) the technical documentation such as specification, test plan.

d) user documents such as help file.

v) all applicable standard to be used in project are listed in the standard guidelines section of
SQA plan. the standard and practice applied are document standards, coding standards,
and review guideline.

d) how to measure quality cost?

Ans:-

i)Every project activity has cost and it must yield excellent business value and software
testing is no exception.

ii) Test manager should be testing in a way that is business value is maximized. too much of
testing would cause unnecessary delay and end up incurring more costs.

iii) Cost of quality is one of the most established, effective measures of quantifying and
calculating the business value of testing.
vi) two measure this, the project and its budget expenses must be classified into four
categories:

a) prevention cost:- this include cost of training developer on writing secure and easily
maintainable code.

b) detection cost:- this include cost of creating test cases, setting up testing environments,
revisiting testing requirements.

c) internal failure cost:- this include cost of incurred in fixing defect just before delivery.

d) external failure cost:- this includes product support cost incurred by delivering poor quality
software.

v) normally, cost of detecting defects is a major part of total cost. this is the cost which is
incurred even if no defects are found by testing team. whereas remainder cost is incurred
on fixing the defect i.e. internal failure cost .

vi) However, the total of these two cost is always significantly less than the external failure
cost so, testing always provide good business value .

vii) test manager should be able to create a strong case for taking out testing activity while
evaluating these four category of cost.

e) what are the element of software reliability? state factor affecting it.

Ans:-

Reliability metrics are used to quantitatively expressed the reliability of the software product.
The option of which metric is to be used depends upon the type of system to which it applies
& the requirements of the application domain.

Some reliability metrics which can be used to quantify the reliability of the software product
are as follows:

1. Mean Time to Failure (MTTF)

MTTF is described as the time interval between the two successive failures. An MTTF of 200
mean that one failure can be expected each 200-time units. The time units are entirely
dependent on the system & it can even be stated in the number of transactions. MTTF is
consistent for systems with large transactions.

For example, It is suitable for computer-aided design systems where a designer will work on
a design for several hours as well as for Word-processor systems.

To measure MTTF, we can evidence the failure data for n failures. Let the failures appear at
the time instants t1,t2.....tn.

MTTF can be calculated as

2. Mean Time to Repair (MTTR)

Once failure occurs, some-time is required to fix the error. MTTR measures the average time
it takes to track the errors causing the failure and to fix them.

3. Mean Time Between Failure (MTBR)

We can merge MTTF & MTTR metrics to get the MTBF metric.

MTBF = MTTF + MTTR

Thus, an MTBF of 300 denoted that once the failure appears, the next failure is expected to
appear only after 300 hours. In this method, the time measurements are real-time & not the
execution time as in MTTF.

4. Rate of occurrence of failure (ROCOF)

It is the number of failures appearing in a unit time interval. The number of unexpected events
over a specific time of operation. ROCOF is the frequency of occurrence with which
unexpected role is likely to appear. A ROCOF of 0.02 mean that two failures are likely to occur
in each 100 operational time unit steps. It is also called the failure intensity metric.

5. Probability of Failure on Demand (POFOD)

POFOD is described as the probability that the system will fail when a service is requested. It
is the number of system deficiency given several systems inputs.

POFOD is the possibility that the system will fail when a service request is made.

A POFOD of 0.1 means that one out of ten service requests may fail.POFOD is an essential
measure for safety-critical systems. POFOD is relevant for protection systems where services
are demanded occasionally.

6. Availability (AVAIL)

Availability is the probability that the system is applicable for use at a given time. It takes into
account the repair time & the restart time for the system. An availability of 0.995 means that
in every 1000 time units, the system is feasible to be available for 995 of these. The percentage
of time that a system is applicable for use, taking into account planned and unplanned
downtime. If a system is down an average of four hours out of 100 hours of operation, its
AVAIL is 96%.

f) Write in brief about any three reliability metrics

Ans:-

1. Mean Time to Failure (MTTF)

MTTF is described as the time interval between the two successive failures. An MTTF of 200
mean that one failure can be expected each 200-time units. The time units are entirely
dependent on the system & it can even be stated in the number of transactions. MTTF is
consistent for systems with large transactions.

For example, It is suitable for computer-aided design systems where a designer will work on
a design for several hours as well as for Word-processor systems.

To measure MTTF, we can evidence the failure data for n failures. Let the failures appear at
the time instants t1,t2.....tn.

MTTF can be calculated as

2. Mean Time to Repair (MTTR)

Once failure occurs, some-time is required to fix the error. MTTR measures the average time
it takes to track the errors causing the failure and to fix them.

3. Mean Time Between Failure (MTBR)

We can merge MTTF & MTTR metrics to get the MTBF metric.

MTBF = MTTF + MTTR

Thus, an MTBF of 300 denoted that once the failure appears, the next failure is expected to
appear only after 300 hours. In this method, the time measurements are real-time & not the
execution time as in MTTF.

Q.5) Attempt the following (Any three ) (each of 5 marks).

a) differentiate between white box and black box testing.

Ans:-

Black Box Testing White Box Testing

i) It is the way of software testing in which i) it is a way of testing the software in

the internal structure or the program or the which the tester has knowledge about the
code is hidden and nothing is known internal structure or the product of the
program of the software

ii) implementation of code is not needed for ii) code implementation is necessary for
black box testing white box testing

iii) it is mostly done by software tester iii)It is mostly done by software developer

iv) No knowledge of implementation is iv) knowledge of implementation is

needed required.

v) it can be referred to as outer or external v) it is the inner or internal software testing

software testing

vi) it is the functional of the software vi) it is a structural test of the software

b) how to use defect for process improvement

Ans:-

i)When the testing team executes the test case, they come across a situation where the
actual test result is different from the expected result. This variation is termed as defect.
ii) Defect must be identified as early as possible in the life cycle of a project so that the cost
of fixing the bugs reduces. without a doubt, the best approach to defect is to eliminate them
altogether.

iii)While that would be ideal, it is virtually impossible to develop a 100% bug free system
however we can identify the implement way to prevent defects. defect prevention should be
considered as a critical activity.

iv)It begins with studying the already found defect and finding the risk area. getting the
critical risk defined allow people to know the types of defects that are most likely to occur
and the ones that can have the greatest system impact

v)Strategies can then be implemented to prevent them. based on all the defects found,
testing team should go to check the process implemented throughout the lifecycle to
understand what originated the defect

vi)The process should then be modified and updated. the valuable insight gain should be
used to strengthen the review process

c) what are activities under quality movement

Ans:-

i)The first step of quality movement is to develop a process (in the case the software
process) that is visible, repeatable and measurable.

ii)The second step examines intangibles that affect the process and work to optimize their
impact on the process. For example, the software process may be affected by high staff
turnover, which itself is caused by constant reorganization within a company. Maybe a stable
organizational structure could do much to improve the quality of software.

iii)While the first two steps focus on the process, the next step concentrates on the user of
the product (in this case, software). in essence, by examining the way the user leads to
improvement in the product itself and potentially to the process that created it.

iv)Final step extends the management concern beyond the immediate product. this is
business-oriented step that looks for opportunity in related area identified by observing the
use of the product in the marketplace.

d) explains cyclomatic complexity with the example.

Ans:-

e) Write in brief about test case design given example.

Ans:-

i) The test case is defined as a group of conditions under which a tester determines whether
a software application is working as per the customer's requirements or not. Test case
designing includes preconditions, case name, input conditions, and expected result. A test
case is a first level action and derived from test scenarios.

ii) It is an in-details document that contains all possible inputs (positive as well as negative)
and the navigation steps, which are used for the test execution process. Writing of test cases
is a one-time attempt that can be used in the future at the time of regression testing.
Iii) Test case gives detailed information about testing strategy, testing process,
preconditions, and expected output. These are executed during the testing process to check
whether the software application is performing the task for that it was developed or not.

iv) Test case helps the tester in defect reporting by linking defect with test case ID. Detailed
test case documentation works as a full proof guard for the testing team because if
developer missed something, then it can be caught during execution of these full-proof test
cases.

v) To write the test case, we must have the requirements to derive the inputs, and the test
scenarios must be written so that we do not miss out on any features for testing. Then we
should have the test case template to maintain the uniformity, or every test engineer follows
the same approach to prepare the test document.
April-2019

Q.2) Attempt the following (Any three ) (each of 5 marks)

a)What is software testing? explainTesting principle .

Ans:-

b)Define the following term QA,QC, QM.

Ans:-

Quality Assurance:-

i) Quality assurance is the maintenance of desire level of quality in an application or software

by means of giving attention to every stage of software development process

ii) It ensures that the approaches, technique, method and process designed for projects are
implemented correctly.

iii) Quality assurance activity monitor and verify that the process used to manage and create
the deliverable have been followed and are operative.

Quality Control:-

i)Quality control ensures that approaches, techniques, method and process are designed in
the project if followed correctly.

ii) It is a procedure or a set of procedures intended to ensure that an application or system

adheres to find a defined set of quality criteria or meet the requirement of the client or
customer.

iii) Quality control activities monitor and verify that the project deliverable meets and the
defined quality standards. It is product oriented and focuses on different identification.

Quality Management:-

i)Quality management is the act of overseeing all activities and tasks need to maintain a
desired level of excellence. It ensure that a required level of quality is achieved. The
software quality management comprises of quality planning .Quality assurance control
process

ii) In the planning process standards are determined that are relevant to the software product
and the organization and the means to achieve them. Once the standards are defined and
building the products starts.
iii) It is very important to have a process to evaluate the project performance and aim to
assure that the quality standards are being followed and the final product will be in
compliance.

c)Write a note on the “nature of error”.

Ans:- A Mistake made in coding is known as error. An error is a human action that produce
incorrect results.

Types of error

i) syntax error :-

a)These are the error related to syntax of the code

b)for example:- missing semicolon at the end of statement in C programming language.

c)every statement in C programming language end with semicolon, a statement ending
without a semi colon will lead to an error while running the program and this types of error is
known as syntax error

d)A syntax error can be identified at the time of compiling by the compiler this error are easy
to find and correct as a compiler find them

ii) logical or semantic error :-

a)It is a mistake in the source code of the software that result is unexpected output which is
different than the actual output expected. It is an error that produces wrong output or may
even lead the program to crash.

b) for example:- using wrong looping conditions. consider the below code which is used to
print hello five times.

c)the loop condition is given is i>5 Instead of i<5. the loop condition became false as the
value of I initialized to 0 which is not greater than 5 as in the loop condition and hence the
loop will executed.

d) this code will compile successful, however the unexpected result will to be achieved.
e) logical error are difficult to find as the compiler does not recognize them and it can be
found only at the runtime when it the expected output is not achieved to find such types of
error are user need to debug the code

iii) runtime error:-

a)This error are identified at the runtime when the program executes .these error are
generally anticipated by the coder but there is nothing that the coder can do .

b)for example: running out of memory will cause a runtime error.

c) in such case coder tried to resolve the error by throwing a runtime error to the userthe
error are given by software not by the operating system.

d)Discuss software quality factor.

Ans:-

Factors of quality for user include

Functionality:- functionality is the conformity of the software with the actual requirement of
and specification. An application should provide all the required functionality are specified in
the requirement.

Reliability:- the ability of an application or system to consistently perform is its intended or

required function on demand and without degradation or failure.

Performance:- performance is mostly about the response time of the software. this
response time should be inescapable interval (e.g. Max. a few seconds), and should not
increase if the transaction count increase.

Flexibility:- it is normally referred to as the ability of application or the system to adapt to

possible or future changes in its requirement. flexibility is the ability of software to
add/modify/ remove functionality without damaging the current system. change is inevitable
so flexibility became an important aspect of quality

Usability:- Usability is a ease of use and learning ability of an application or system .

Security:-The degree to which the application is protected against the malicious attack and
other potential risks. security is very important especially when the application is dealing
with sensitive user data like bank detail.

e)Write in brief about test case design.

Ans:-
i) The test case is defined as a group of conditions under which a tester determines whether
a software application is working as per the customer's requirements or not. Test case
designing includes preconditions, case name, input conditions, and expected result. A test
case is a first level action and derived from test scenarios.

ii) It is an in-details document that contains all possible inputs (positive as well as negative)
and the navigation steps, which are used for the test execution process. Writing of test cases
is a one-time attempt that can be used in the future at the time of regression testing.

Iii) Test case gives detailed information about testing strategy, testing process,
preconditions, and expected output. These are executed during the testing process to check
whether the software application is performing the task for that it was developed or not.

iv) Test case helps the tester in defect reporting by linking defect with test case ID. Detailed
test case documentation works as a full proof guard for the testing team because if
developer missed something, then it can be caught during execution of these full-proof test
cases.

v) To write the test case, we must have the requirements to derive the inputs, and the test
scenarios must be written so that we do not miss out on any features for testing. Then we
should have the test case template to maintain the uniformity, or every test engineer follows
the same approach to prepare the test document.

f) Write a note on black box testing.

Ans:-

Q.3) Attempt the following (Any three ) (each of 5 marks)

a)Explain strategic approach to software testing.

b)What is validation testing? Give examples.

c)Write a note on unit testing.

Ans:-

i) Unit testing is a software development process in which the smallest testable parts of an
application, called units, are individually and independently scrutinized for proper operation.
This testing methodology is done during the development process by the software
developers and sometimes QA staff. The main objective of unit testing is to isolate written
code to test and determine if it works as intended.

ii) Unit testing is an important step in the development process, because if done correctly, it
can help detect early flaws in code which may be more difficult to find in later testing stages

iii) Unit testing is a component of test-driven development (TDD), a pragmatic methodology

that takes a meticulous approach to building a product by means of continual testing and
revision. This testing method is also the first level of software testing, which is performed
before other testing methods such as integration testing. Unit tests are typically isolated to
ensure a unit does not rely on any external code or functions. Testing can be done manually
but is often automated

iv) Unit tests can be performed manually or automated. Those employing a manual method
may have an instinctual document made detailing each step in the process; however,
automated testing is the more common method to unit tests. Automated approaches
commonly use a testing framework to develop test cases. These frameworks are also set to
flag and report any failed test cases while also providing a summary of test cases.

v) Advantages and disadvantages of unit testing

Advantages to unit testing include:

● The earlier a problem is identified, the fewer compound errors occur.

● Costs of fixing a problem early can quickly outweigh the cost of fixing it later.
● Debugging processes are made easier.

Disadvantages include:

● Tests will not uncover every bug.

● Unit tests only test sets of data and its functionality—it will not catch errors in
integration.
● More lines of test code may need to be written to test one line of code—creating a
potential time investment

d)Explain the concept and roles of software metrics.

Ans:- The three types of metrics you should collect as a part of your quality assurance
process are source code metric, Development metrics and Testing metrics.

i)Source code metrics:-

a) These are the measurement of source code that make up all your software. Source code
is the fundamental building block of which your software is made, so measuring it is the key
to making sure your code is high-caliber.( not to mention there is almost always room for
improvement). Look closely enough at even your best source code, and you might spot a
few areas that you can optimize your even better performance.

b) When measuring source code quality make sure you are looking at the number of lines of
food you have, which will ensure that you have the appropriate amount of code and it no
more complex than it needs to be,

ii) Development metrics :-

a) These matrix measure the custom software development processes itself. Gather
development metrics to look for ways to make your operation more efficient and reduce
incidents of software error.
b) Measuring number of detect with within the code and time to fix them tell you a lot about
the development process itself. start by tallying up the number of defects that appearing in
the code and note the time it take to fix them.

iii)Testing metrics :-

a) These metrics help you evaluate how functional your product is.

b) There are two major testing metrics one of them is “test coverage” that collect data about
which part of the software program are executed when it runs a test. the second part is the
test of the testing itself. Its is called “defect removal efficiency” and it checks your success
rate of for spotting and removing defect.

e)Explain cyclomatic complexity with the example.

Ans:-

i) Complexity of a code is directly depend on the understandability of the code and relate to
ease of comprehension.

ii) All the factors that make program difficult to understand are responsible for complexity
when we analyze a program code please we find that the number of line( size), total
occurrence of operate operators and operand (size), numbers of control structure (control
flow structures), functional call (coupling) are the factor which directly affect the complexity.

iii) In general these primitives are major independently by the different complexity measures
and each one of these is assumed to represent overall complexity of the software.

iv) when we look at most of the complexity measures we can observe the close relation
between the number of line operators and operands count, and basic control structure.
consequently this primitive of software may constitute the component of unified
comprehensive complexity measure

v) In our opinion the complexity of software system depend on following factors:

a) complexity of a program depends on the size of code. Therefore, the complexity due to a
single line of code is assumed to be one unit.

b) complexity of a program depends on the size of code. We suggest that the size of the
code can be measured by total occurrence of operator and operands. Therefore, the
complexity due to ith line of code can be calculated as

SOOi =Ni1 + Ni2 where

Ni1 : the total number of occurrences of operators at line i.

Ni2 : the total number of occurrences of operands at line i.

c) complexity of the program is directly proportional to the cognitive weight of basic control
structure (BSC).cognitive weight of software[19] is extended of difficulty or relative time and
effect for comprehending given software modeled by a number of basic control structure
BCS sequence branch

f)How to use defects for process improvement?

Ans:-

i)When the testing team executes the test case, they come across a situation where the
actual test result is different from the expected result. This variation is termed as defect.

ii) Defects must be identified as early as possible in the life cycle of a project so that the cost
of fixing the bugs reduces. Without a doubt, the best approach to defect is to eliminate them
altogether.

iii)While that would be ideal, it is virtually impossible to develop a 100% bug free system
however we can identify the implementable way to prevent defects. defect prevention should
be considered as a critical activity.

iv)It begins with studying the already found defect and finding the risk area. getting the
critical risk defined allow people to know the types of defects that are most likely to occur
and the ones that can have the greatest system impact

v)Strategies can then be implemented to prevent them. based on all the defects found,
testing team should go to check the process implemented throughout the lifecycle to
understand what originated the defect

vi)The process should then be modified and updated. the valuable insight gain should be
used to strengthen the review process

Q.4) Attempt the following (Any three ) (each of 5 marks)

a)What is quality movement?

Ans:-
i)The first step of quality movement is to develop a process (in the case the software
process) that is visible, repeatable and measurable.

ii)The second step examines intangibles that affect the process and work to optimize their
impact on the process. For example, the software process may be affected by high staff
turnover, which itself is caused by constant reorganization within a company. Maybe a stable
organizational structure could do much to improve the quality of software.

iii)While the first two steps focus on the process, the next step concentrates on the user of
the product (in this case, software). in essence, by examining the way the user leads to
improvement in the product itself and potentially to the process that created it.

iv)Final step extends the management concern beyond the immediate product. this is
business-oriented step that looks for opportunity in related area identified by observing the
use of the product in the marketplace.

b)Explain any five quality assurance activity.

c)What is 6 Sigma? explain it core step.

Ans:-

i)Six Sigma is the most widely used strategy for statistical quality assurance in industry
today.

ii)originally popularized by Motorola in the 1980s Sigma strategy” is a hard and well-
organized methodology that uses data and statistical analysis to measure and improve a
company's operational performance by identifying and eliminating the defects in
manufacturing and service related processes”[ISO08].

iii) The term six Sigma is derived from 6 standard deviations -3.4 instant (defects) per million
occurrence- implying an extremely high quality standard.

The six Sigma methodology defined 3 core steps:

a)Define customer requirements and deliverables project goal via well-defined method of
customer communication.

● Measure the existing process and its output to determine current quality performance
collect defect metric
● analyze the defect matrix and determine the vital few causes.

b) If an existing software process is in place, but improvement is required.

c)Six Sigma suggests two additional step:

● Improve the process by eliminating the root cause of defects.

 ● Control the process to ensure that the future work does not reintroduce the cause of
defects.

d) Discord and additional steps are sometimes referred to as DMAIC(define, measure,

analyze, improve, and control) method.

e)If an organization is developing a software process (rather than improving an existing

process), the core step or augment as follows:

● Design the process to (1) avoid the root cause of defect and (2)to meet customer
requirements.
● Verify that the process model will, in fact, avoid defect and meet customer
requirements.

f)This variation is sometimes called the DMADV(define, measure, analyze,design, and

verify) method.

d)What is FTR? discussed objectives.

Ans:-Formal technical review (FTR) is a software quality control activity performed by

software engineer

The objective of an FDR are:

i) To find error in function, logic ,or implementation for any representation of software

ii)To verify that the software under review meets it requirement.

iii) To ensure that the software has been represented according to predefined standards .

iv) To achieve software that is developed in a uniform manner .

v) To make project more manageable .

vi) In addition, the FTR service as a training ground, enabling junior engineer to observe
different approach of software analysis, designs and implementation.

vii) FTR also helps to promote backup and continuity because a number of people become
familiar with the parts of software that they may not have seen.

viii) The FTR is actually a class of review that include walkthrough and inspection. Each
FTR is conducted as a meeting and will be successful only if a properly planned, controlled
and attended.

e)State type of quality cost. explains any one of them.

Ans:-

Types of quality cost:

The cost of quality or quality of cost does not mean the use of expensive or very highly
quality material to manufacture our product the term referred to costs that are incurred to
prevent detect and remove defect from product

Quality costs are categorized into four main type:

1. Preventions cost
2. Appraisal costs
3. internal failure costs
4. External failure costs

1. Preventions costs:-

i)It is much better to prevent defects rather than finding and removing them from products.
The costs incurred to avoid or minimize the number of defects in the first place are known as
prevention costs.

ii)some example of preventions cost are improvement of manufacturing process workers

training quality engineering statistical process control etc

2.Appraisal costs:-

i) the appraisal cost also known as inspection cost are those costs that are incurred to
identify defective product before they are shipped to customers all associated all costs
associated with the activities that are performed during manufacturing the process to ensure
required quality standards are also included in this category

ii) Identification of defective products involves maintaining a team of inspections. it may be

very costly for some organization

3.Internal failure costs:-

i) Internal failure costs are those costs that are incurred to remove defects from products
before shipping them to customers.

ii)Examples of internal failure costs include cost of rework, reject products, scrap etc.

4.External failure costs:-

i) If defective product has been shipped to customer the external failure costs arise external
failure costs include warranty replacements loss sale because of bad reputation payment for
damage arising from the use of defective product etc
ii) The shipment of defective product can dissatisfied customer, damage goodwills and
reduce sales and profit

f)Write notes on quality tools.

Q.5) Attempt the following (Any three ) (each of 5 marks)

a)Discuss the face of formal review .

b)What are test plans and test case ?explain with an example.

c)Write a note on software reliability.

Ans:-

i)Software Reliability means Operational reliability. It is described as the ability of a

system or component to perform its required functions under static conditions for a
specific period.

i)Software reliability is also defined as the probability that a software system fulfills
its assigned task in a given environment for a predefined number of input cases,
assuming that the hardware and the input are free of error.

iii)Software Reliability is an essential connection of software quality, composed with

functionality, usability, performance, serviceability, capability, installability,
maintainability, and documentation. Software Reliability is hard to achieve because
the complexity of software turns out to be high.

iv)While any system with a high degree of complexity, containing software, will be hard
to reach a certain level of reliability, system developers tend to push complexity into
the software layer, with the speedy growth of system size and ease of doing so by
upgrading the software.
d)Write in brief about defect life cycle.

Ans:-Once the defect is identify it must be reported .defect goes through different states
from the time it is reported till the time it is fixed.

1.New:- this is the first state of the defect life cycle. when any defect is identified and logged,
it is in the new state.

2.Open:- i)the newly locked effect then assigned to the development team for solving this is
generally done by the project manager for the development team.

ii)In an open state the developer goes through the defect to analyze it. If the developer feels
that the defect is not valid or a similar defect has been logged then the defect is transferred
to the reject state. The defect can also be transferred to a deferred state for future solving.

3. Fixed:- if the developer has worked on the defect and resolved it then the defect moves to
fixed state. The test team later needs to test and verify whether the defect is actually fixed.

4.Retest:-In this state the development is waiting for the test team to test the resolved defect
to check whether the defect has been resolved accurately. The team also checks whether
the fixed defect or issue has led to any other new defect.

5.Open:-If the tester while retesting feel the defect is not resolved or partially resolved then
the defect state is changed to reopen and the development team will have to rework on the
issue to resolve it

6.Closed:-When the testing team has checked and verified the defect are not sure that
defect does not exist any longer the defect is then moved to closed state
e)Explain SQA plan.

Ans:-

i)The SQA plan service as a template for SQA activities planned for each software project.
the SQA group and the project team developed the SQA plan. the initial two section of the
plan described the purpose and a reference of the SQA plan .

ii) The next section record details of the roles and responsibility for maintaining software
product quality.

iii) the documentation section of the SQA plan describe each of the work product produced
during the software process. this section defines the minimum set of work product or
acceptable to achieve high quality.

iv) the documentation section consist of:

a) the project documents such as project plan, requirement document, test case, reports ,
user manual and administrative manual.

b) model such as ERDs, class hierarchies.

c) the technical documentation such as specification, test plan.

d) user documents such as help file.

v) all applicable standard to be used in project are listed in the standard guidelines section of
SQA plan. the standard and practice applied are document standards, coding standards,
and review guideline.
November-2019

Q.2) Attempt the following (Any three ) (each of 5 marks)

a)Write in brief about QA,QC,QM.

Ans:-

Quality Assurance:-

i) Quality assurance is the maintenance of desire level of quality in an application or software

by means of giving attention to every stage of software development process

ii) It ensures that the approaches, technique, method and process designed for projects are
implemented correctly.

iii) Quality assurance activity monitor and verify that the process used to manage and create
the deliverable have been followed and are operative.

Quality Control:-

i)Quality control ensures that approaches, techniques, method and process are designed in
the project if followed correctly.

ii) It is a procedure or a set of procedures intended to ensure that an application or system

adheres to find a defined set of quality criteria or meet the requirement of the client or
customer.

iii) Quality control activities monitor and verify that the project deliverable meets and the
defined quality standards. It is product oriented and focuses on different identification.

Quality Management:-

i)Quality management is the act of overseeing all activities and tasks need to maintain a
desired level of excellence. It ensure that a required level of quality is achieved. The
software quality management comprises of quality planning .Quality assurance control
process

ii) In the planning process standards are determined that are relevant to the software product
and the organization and the means to achieve them. Once the standards are defined and
building the products starts.

iii) It is very important to have a process to evaluate the project performance and aim to
assure that the quality standards are being followed and the final product will be in
compliance.
b)Discuss role and responsibilities in review.

c)Write note on black box testing

d) Differentiate between inspection and walkthrough

Ans:-

Inspection Walkthrough

i)It is informal i)It is informal

ii)Initiated by project team ii)Initiated by author

iii)A group of relevant person from different iii)Usually team member of the same project
department participated in the inspection take participation in the walkthrough author
himself act as walkthrough leader

iv) Checklist is used to find faults iv)No checklist is used in the walkthrough

v)Inspection process includes overview, v)Walkthrough process include overview,

preparation, inspection, and reworks and little or no of preparation, little or no of
follow up. preparation examination (actual
walkthrough meeting), and rework and
follow up

vi) Formalized procedure in each step vi)No formalized procedures in the step.

e)Write note on basic part testing

f)Discuss types of software quality factor

Ans:-

Factors of quality for user include

Functionality:- functionality is the conformity of the software with the actual requirement of
and specification. An application should provide all the required functionality are specified in
the requirement.

Reliability:- the ability of an application or system to consistently perform is its intended or

required function on demand and without degradation or failure.
Performance:- performance is mostly about the response time of the software. this
response time should be inescapable interval (e.g. Max. a few seconds), and should not
increase if the transaction count increase.

Flexibility:- it is normally referred to as the ability of application or the system to adapt to

possible or future changes in its requirement. flexibility is the ability of software to
add/modify/ remove functionality without damaging the current system. change is inevitable
so flexibility became an important aspect of quality

Usability:- Usability is a ease of use and learning ability of an application or system .

Security:-The degree to which the application is protected against the malicious attack and
other potential risks. security is very important especially when the application is dealing
with sensitive user data like bank detail.

Q.3) Attempt the following (Any three ) (each of 5 marks)

a)Write a short note on alpha and beta testing validation testing

b)Define software metrics .Give it purpose. Explain it types

c)Explain the steps of defect management process

Ans:-

i) Defect is an unexpected behavior of the software. All software has some defect. 100%
defect free software is not possible. Elimination of bugs from the system depends upon how
efficiently is testing process is carried out. A defect is basically the difference between the
expected and actual result.

b) The cost of finding and correcting defect is a very expensive activity of the software
development process. defects should be found as early as possible to reduce the cost of
fixing the defect.

c) While defect may be inevitable, we can minimize their number and impact on our project.
to do this, project management team need to implement a defect management process
(DMP) that focus on preventing defect, finding defects as early as possible in the processing,
and minimizing the impact of defect.

Defect Management Process

a) Defect Prevention :- this is a process in which defects are prevented to improve the
productivity and quality of the software. As discussed earlier, it is not Possible to eliminate all
defect.
b) Deliverable Baseline :- when a deliverable i.e. system or a software reach its predefined
then the deliverable become baseline. A product should be considered baselined when
developer pass it to the testes for testing.

c) Defect Discovery :- in this phase defect are identified.

steps involved in defect discovery are:

finding a defect :- should be identified as earlier as possible before they became major

report defect:- as soon as the tester identify the defect, it should be communicated to the
development team as they have to identify and fix them

acknowledgement defect:- this development team must acknowledge the defect as start to
working on it, if it is a valid defect.

d) Defect Resolution :- once the testing team has identified and inform the development
team about the defect, development team should start work towards resolving it. the project
manager must prioritize the defect and fix it. higher priority defects are fixed first. once the
defect is fixed, the testing team should be informed so that the resolution can be tested and
verified.

e) Process Improvement :- for the improvement, everyone in the project needs to look and
back and check from where the defect was originated. based on that what you can you make
change in the validation process base-lining in document review process which may catch
defect earlier in the process where are less expensive.

d)Discuss strategic approach to software testing

e)What is the format of default reporting? Explain

Ans:-

f)Explain top down integration testing

Ans:-

Top down integration testing

i)Mainly control module use as test driver and stubs are substituted for component directly
subordinate to it

ii)Someone subordinate stubs are replaced one at time with the real component following the
depth first or breadth first approach

iii_Tests are conduct as each component is integrated

iv)On completion of each set of tests and other steps is replaced with real component

v)Regression testing may be used to ensure that new error not introduced

Q.4) Attempt the following (Any three ) (each of 5 marks)

a)Write a short note on SQA plan.

Ans:-

i)The SQA plan service as a template for SQA activities planned for each software project.
the SQA group and the project team developed the SQA plan. the initial two section of the
plan described the purpose and a reference of the SQA plan .

ii) The next section record details of the roles and responsibility for maintaining software
product quality.

iii) the documentation section of the SQA plan describe each of the work product produced
during the software process. this section defines the minimum set of work product or
acceptable to achieve high quality.

iv) the documentation section consist of:

a) the project documents such as project plan, requirement document, test case, reports ,
user manual and administrative manual.

b) model such as ERDs, class hierarchies.

c) the technical documentation such as specification, test plan.

d) user documents such as help file.

v) all applicable standard to be used in project are listed in the standard guidelines section of
SQA plan. the standard and practice applied are document standards, coding standards,
and review guideline.

b)Explain pareto diagrams with examples.

c)List type of quality cost.explain in detail.

Ans:-

Types of quality cost:

The cost of quality or quality of cost does not mean the use of expensive or very highly
quality material to manufacture our product the term referred to costs that are incurred to
prevent detect and remove defect from product
Quality costs are categorized into four main type:

1. Preventions cost
2. Appraisal costs
3. internal failure costs
4. External failure costs

1. Preventions costs:-

i)It is much better to prevent defects rather than finding and removing them from products.
The costs incurred to avoid or minimize the number of defects in the first place are known as
prevention costs.

ii)some example of preventions cost are improvement of manufacturing process workers

training quality engineering statistical process control etc

2.Appraisal costs:-

i) the appraisal cost also known as inspection cost are those costs that are incurred to
identify defective product before they are shipped to customers all associated all costs
associated with the activities that are performed during manufacturing the process to ensure
required quality standards are also included in this category

ii) Identification of defective products involves maintaining a team of inspections. it may be

very costly for some organization

3.Internal failure costs:-

i) Internal failure costs are those costs that are incurred to remove defects from products
before shipping them to customers.

ii)Examples of internal failure costs include cost of rework, reject products, scrap etc.

4.External failure costs:-

i) If defective product has been shipped to customer the external failure costs arise external
failure costs include warranty replacements loss sale because of bad reputation payment for
damage arising from the use of defective product etc

ii) The shipment of defective product can dissatisfied customer, damage goodwills and
reduce sales and profit
d)Define six Sigma explained basic steps.

Ans:-

i)Six Sigma is the most widely used strategy for statistical quality assurance in industry
today.

ii)originally popularized by Motorola in the 1980s Sigma strategy” is a hard and well-
organized methodology that uses data and statistical analysis to measure and improve a
company's operational performance by identifying and eliminating the defects in
manufacturing and service related processes”[ISO08].

iii) The term six Sigma is derived from 6 standard deviations -3.4 instant (defects) per million
occurrence- implying an extremely high quality standard.

The six Sigma methodology defined 3 core steps:

a)Define customer requirements and deliverables project goal via well-defined method of
customer communication.

● Measure the existing process and its output to determine current quality performance
collect defect metric
● analyze the defect matrix and determine the vital few causes.

b) If an existing software process is in place, but improvement is required.

c)Six Sigma suggests two additional step:

● Improve the process by eliminating the root cause of defects.

● Control the process to ensure that the future work does not reintroduce the cause of
defects.

d) Discord and additional steps are sometimes referred to as DMAIC(define, measure,

analyze, improve, and control) method.

e)If an organization is developing a software process (rather than improving an existing

process), the core step or augment as follows:

● Design the process to (1) avoid the root cause of defect and (2)to meet customer
requirements.
● Verify that the process model will, in fact, avoid defect and meet customer
requirements.
f)This variation is sometimes called the DMADV(define, measure, analyze,design, and
verify) method.

e)How to measure quality cost.

Ans:-

i)Every project activity has cost and it must yield excellent business value and software
testing is no exception.

ii) Test manager should be testing in a way that is business value is maximized. too much of
testing would cause unnecessary delay and end up incurring more costs.

iii) Cost of quality is one of the most established, effective measures of quantifying and
calculating the business value of testing.

vi) two measure this, the project and its budget expenses must be classified into four
categories:

a) prevention cost:- this include cost of training developer on writing secure and easily
maintainable code.

b) detection cost:- this include cost of creating test cases, setting up testing environments,
revisiting testing requirements.

c) internal failure cost:- this include cost of incurred in fixing defect just before delivery.

d) external failure cost:- this includes product support cost incurred by delivering poor quality
software.

v) normally, cost of detecting defects is a major part of total cost. this is the cost which is
incurred even if no defects are found by testing team. whereas remainder cost is incurred
on fixing the defect i.e. internal failure cost .

vi) However, the total of these two cost is always significantly less than the external failure
cost so, testing always provide good business value .

vii) test manager should be able to create a strong case for taking out testing activity while
evaluating these four category of cost.

f)Discuss formal technical review in detail.

Ans:-

Formal technical review (FTR) is a software quality control activity performed by software
engineer

The objective of an FDR are:

i) To find error in function, logic ,or implementation for any representation of software

ii)To verify that the software under review meets it requirement.

iii) To ensure that the software has been represented according to predefined standards .

iv) To achieve software that is developed in a uniform manner .

v) To make project more manageable .

vi) In addition, the FTR service as a training ground, enabling junior engineer to observe
different approach of software analysis, designs and implementation.

vii) FTR also helps to promote backup and continuity because a number of people become
familiar with the parts of software that they may not have seen.

viii) The FTR is actually a class of review that include walkthrough and inspection. Each
FTR is conducted as a meeting and will be successful only if a properly planned, controlled
and attended.

Q.5) Attempt the following (Any three ) (each of 5 marks)

a)Explain different phases of SDLC.

Ans:-

It is a framework that defines activity that are performed throughout the software
development process.

The development process adopted for a project will depend on the project aims and goals
there are numerous development lifecycles that have been developed in order to achieve
different required object.

The most appropriate development process should be applied to each project the models
specify the various stages of process and the order in which they are carried out.

Phases of SDLC

i) Requirement gathering:- this is the most important phase in software development life
cycle . In this phase requirement for the software are collected from the customer/ client.
This requirement are provided in a document called Business Requirements
Specification(BRS) or System Requires Specification(SRS).

ii)Design:- it has two step

1)HLD high level design

2)LLD low level design

HLD high level design :- it gives the architecture of the software product to be developed
and it is done by architects and senior developers

LLD low level design:- it is done by senior developer. It describes how each and every
feature in the product should work and how every component should work. Here, only the
design will be there and not the code. The outcome from this phase is High Level Document
and Low Level Document which works as an input to the next phase.

iii) Coding :- It mean translating the design into a computer readable language.
Development team does the actual coding based on design software and write it unit tests
for each component to test the new code written by them. This is the longest phase of the
software development lifecycle.

iv)Testing :- After the code is developed testing is carried out to verify the entire
requirement specified by customer have been implemented. The aim of the tester is to find
out the gaps or defects within the system and also to verify that the software work as
expected according to the requirement. It include Unit testing, Integration testing and System
testing.

v)Deployment:- After successful testing the product is delivered/deployed to the customer

for their use. The size of the project will determine the complexity of deployment. The user
can be trained on, or aided with the document on how to operate the software. And small
round of testing is also performed production to make sure of any environmental issue and
any impact of new release.

vi)Maintenance:- Once when the customers start using the developed system then actual
problem will come up and need to be solved from time to time. Fixing the issue found by the
customer comes in the maintenance phase

b)What is system testing? explain it in any two types.

Ans:-

i)System testing of software or hardware is testing conduct on a whole, integrated system to

estimate the following compliances with its specified set of requirements.

ii) The only thing testers should be testing at the system test stage are things that he and
she could not test before

iii)It is done to check how the system as a whole is functioning here the functionality and
performance of the system is validated

iv) The user is not involved in system testing

v)It is performed before acceptance testing

vi) System testing involves both functional and non functional testing.
c)Explain the following ISO ISO 9000 ISO 9000 series.

Ans:-

d)differentiate between verification and validation .

Ans:-

Verification Validation

i)Verification is to check whether the i)Validation is to check whether the

software conform to the specification software meets the customer
expectation and requirement

ii)It does not involve executing the code ii)It always involved in executing the
code

iii)Verifying process include checking iii)It is a dynamic mechanism of testing

documents, design, codes and program and validating the actual product

iv)Verification uses methods like review, iv)It is use method like black box texting
walkthrough, inspection and desk and white box testing technique
checking etc.

v)Checks are we building the right v)Checks are we building the right
product products

vi)QA team does not verification and vi)With the involvement of testing team
make sure that the software is as per the validation is executed on software code
requirement in SSRS document

e)What are the majors of reliability and availability? explain.