Scribd
Upload
33 views6 pages

SQA - QB Ans

Uploaded by

karthiksince11102001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views6 pages

SQA - QB Ans

Uploaded by

karthiksince11102001
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 6

1.

Product quality vs Process quality

2. List some of the quality challenges of SQA.


● The uniqueness of software quality assurance
● The environments for which SQA methods are developed
● The uniqueness of the software development process
■ High complexity, as compared to other industrial products
■ Invisibility of the product
■ Opportunities to detect defects (“bugs”) are limited to the product
development phase
3.

Verification Validation

It includes checking documents, design, It includes testing and validating the


codes and programs. actual product.

Verification is the static testing. Validation is dynamic testing.

It does not include the execution of the It includes the execution of the code.
code

Methods used in verification are reviews, Methods used in validation are Black
walkthroughs, inspections and Box Testing, White Box Testing and
desk-checking. non-functional testing.

Quality assurance team does verification. Validation is executed on software


code with the help of the testing team.

It comes before validation. It comes after verification.

4. Software Portability:
Software portability is the possibility to use the same software in different
environments. It applies to the software that is available for two or more
different platforms or can be recompiled for them.
Common Portability kinds are
● Application,
● Source Code and
● Data Portability.
5. Software Configuration Version:
A software system, document, or approved, chosen set of documented SCI
versions at a specific time, where the actions to be taken are governed by
software configuration management protocols. According to the cited methods,
new software configuration versions are released.

6. Outline the issues related to the storage of documents.


● Wasted space
● Increased security risk
● Lack of searchability
● Threat of natural disaster

7.
8. Define software quality metrics.
Measurement of the various aspects of software quality is considered to be
an effective tool for the support of control activities and the initiation of process
improvements during the development and the maintenance phases. These
measurements apply to the functional quality, productivity, and organizational
aspects of the project.

9. Types of SQA Committees:


● Permanent committees
● Ad hoc committees

10. Types of QA audit:

1. Planned: A planned audit is primarily aimed at ensuring consistency of quality so

that the customer feels a sense of assurance.

2. Project based: A project is divided into various stages, hence each stage’s

review is analyzed to capture a better view of the project as a whole.

3. Custom:Such an audit is conducted as per the requirement of a company’s

project needs.
PART B

The contribution of templates to software quality Template use is quite advantageous to


development teams and to review teams. For development teams, template use:

■ Facilitates the process of preparing documents by saving the time and energy
required to elaborate the report’s structure. Most organizations allow templates to be
copied from a SQA public file or downloaded from the organization’s intranet files, which
even saves keying the table of contents to the new document.

■ Ensures that documents prepared by the developer are more complete as all the
subjects to be included in the document have already been defined and repeatedly
reviewed by numerous professionals over the course of the template’s use. Common
errors, such as overlooking a topic, are less likely to occur.

■ Provides for easier integration of new team members through familiarity. The
document’s standard structure, prepared according to templates that may be known to
the new member from previous work in another of the organization’s units or teams,
makes finding information much easier. It also smoothes ongoing document preparation
in cases where parts of the document have been prepared by another team member
who may or may not have left.

■ Facilitates review of documents by eliminating the need to study a document’s


structure and confirm its completeness, if the document is based on the appropriate
template. It also simplifies review of the completed document as its structure is standard
and reviewers are familiar with its expected contents (chapters, sections and
appendices). As a result of this consistency, the review is expected to be more thorough
yet less time-consuming.

You might also like