💜

SQA
1.Define software error, software fault and software failure. Explain the differences between these undesirable
software statuses.
https://www.javatpoint.com/bug-vs-defect-vs-error-vs-fault-vs-failure

2.List and briefly describe the various causes of software errors.

💡 page 46 - 2.3 [make short notes and try a flowchart]

1. faulty definition of requirements

2. client developer communication failures

3. deviations from software requirements

4. logical design errors

5. coding errors

6. non compliance with documentation and coding instruction

7. shortcomings of the testing process

8. procedure errors

9. documentation errors

3. (1) What are the three factor categories belonging to McCall’s factor model? (2) What factors are included in
each of the categories

💡 https://www.geeksforgeeks.org/mccalls-quality-model/

product operation - CURIE

product revision - MFT

product transition - RIP

4. (1) What are the three factor categories belonging to McCall’s factor model? (2) What factors are included in
each of the categories

https://www.tutorialspoint.com/software_quality_management/software_quality_management_factors.htm#:~:text=McCall's
Factor Model&text=The 11 factors are grouped,revision%2C and product transition factors.

5. South cottage Inc. is a manufacturer of washing machines and dishwashers. The requirements document for
the new control unit included the following specifications: (a) The firmware should be suitable for all six variations
of model 2002 washing machines. (b) The water level control module of the washing machine should be suitable for
use as a water level control module in the new model 2002 dishwasher. (1) To which of the factors do the above
requirements belong? (2) Explain your answer.

SQA 1
SQA 2
SQA 3
 6.Discuss the SQA Architecture with the help of a diagram.

💡 page 84 - 4.1

Pre-project quality components

Project life cycle quality components

Infrastructure error preventive and improvement components

Software quality management components

Standardization, certification and SQA assessment components

Organizing for SQA – the human components

7. Discuss Project life cycle components

💡 page 88 - 4.3 [make a flowchart for this question]

reviews

formal design reviews

peer reviews

expert opinions

software testing

software maintenance

corrective maintenance

adaptive maintenance

functionality improvement maintenance

pre maintenance components

maintenance contract review

maintenance plan

software development life cycle components

infrastructure SQA components

■ Maintenance procedures and instructions
■ Supporting quality devices
■ Maintenance staff training, retraining, and certification
■ Maintenance preventive and corrective actions
■ Configuration management
■ Control of maintenance documentation and quality records.

managerial control SQA components

SQA 4
 ■ Maintenance service control
■ Maintenance quality metrics
■ Maintenance quality costs.

8. Discuss software maintenance components

https://www.geeksforgeeks.org/components-of-software-maintenance-process/

9.Discuss the contract review objectives

💡 page 107 - 5.3

Proposal draft review objectives

1. Customer requirements have been clarified and documented.

2. Alternative approaches for carrying out the project have been examined.

3. Formal aspects of the relationship between the customer and the software
firm have been specified.

4. Identification of development risks.

5. Adequate estimation of project resources and timetable have been prepared.

6. Examination of the firm’s capacity with respect to the project.

7. Examination of the customer’s capacity to fulfill his commitments.

8. Definition of partner and subcontractor participation conditions.

9. Definition and protection of proprietary rights.

Contract draft review objectives

1. No unclarified issues remain in the contract draft.

2. All understandings reached subsequent to the proposal are correctly

documented.

3. No “new” changes, additions, or omissions have entered the contract draft.

10. what are the elements of a quality plan? Explain in detail.

💡 page 128 - 6.3

1. List of quality goals

■ The scope of the review activity

■ The type of the review activity
■ The schedule of review activities (as defined by its priority and the
succeeding activities of the project process)
■ The specific procedures to be applied
■ Who is responsible for carrying out the review activity?

2. Planned Software tests

■ The unit, integration or the complete system to be tested

■ The type of testing activities to be carried out, including specification of computerized software tests to be applied
■ The planned test schedule

■ The specific procedures to be applied

■ Who is responsible for carrying out the test.

3. Review activities

■ The scope of the review activity

■ The type of the review activity

SQA 5
 ■ The schedule of review activities
■ The specific procedures to be applied
■ Who is responsible for carrying out the review activity?

4. Acceptance tests for software externally developed

5. Configuration management tools and procedures

11. Explain the Risk Management Process in detail.

💡 page 142 - 6A.3

identification of SRI

team, project, customer situations

start of the project

periodic repetition of checklists

evaluation of SRI

estimating probability of risk

estimating damages

planning RMA

factors to be considered

priority of SRI

expected result of RMA

costs and efforts

implementation

1 RMA per staff member

monitoring

efficiency determination of RMA

update risk evaluation

12. Explain the Spiral in detail

💡 link:

https://www.geeksforgeeks.org/software-engineering-spiral-model/

14.Discuss the object oriented model with the help of a diagram;

💡 https://www.geeksforgeeks.org/software-engineering-object-oriented-life-cycle-model/

15. Explain the SQA defect Removal model using the following table information.

💡 page 171 (4), page 164 - 7.4.2, page 162 - 7.4.1 for table explanation

16. Discuss the formal design process with the help of a neat labelled diagram

SQA 6
 💡 diagram - page 186, page 179 (read after frame 8.2) - PRACTICE THE DIAGRAM ON A PAPER

focus on:

The participants

review leader

review team

prior preparations

review leader prep

review team prep

development team prep

DR session

design presentation

comments ⇒ review
verification and validation

decisions

full approval

partial approval

denial of approval

recommended post-DR activities

DR report

follow up process

17. Discuss the various testing strategies and differences between them.

💡 page 209, page 236 (2) - question

big bang testing

incremental testing

top down testing

bottom up testing

SQA 7
 18. Explain Stubs and drivers for Incremental testing.

💡 page 211, page 209 - incremental testing

19. For the given Taxi Service scenario draw the flowchart of the module and Program flow graph and give the full
lists of paths. Imperial Taxi Services (ITS) serves one-time passengers and regular clients (identified by a taxi card).
The ITS taxi fares for one-time passengers are calculated as follows: (1) Minimal fare: $2. This fare covers the
distance traveled up to 1000 yards and waiting time (stopping for traffic lights or traffic jams, etc.) of up to 3
minutes. (2) For every additional 250 yards or part of it: 25 cents. (3) For every additional 2 minutes of stopping or
waiting or part thereof: 20 cents. (4) One suitcase: no charge; each additional suitcase: $1. (5) Night supplement:
25%, effective for journeys between 21.00 and 06.00.

💡 page 219

20. Explain McCabe’s cyclomatic complexity metrics for the Taxi service example.

💡 page 221 - 9.4.4

21. Discuss the advantages and disadvantages of White Box Testing.

SQA 8
 💡 page 237 (3), page 216

white box testing

testing every program statement and comment

data processing

path coverage

line coverage

calculations correctness tests

line coverage since path coverage is very costly

weaker concept

flowchart and program flow graph

software qualification tests

code structure instructions and procedures

code style procedures

documentation and help sections

maintainability tests

reusability tests

reduces resources

shortens development period

standards of reusability packages must be conformed

growth of software reuse

Advantages:

statement-by-statement checking of code

processing paths

performance of line coverage follow-up

ascertains quality of coding

coding standards.

Disadvantages:

vast resources utilized

inability to test software performance in terms of availability, reliability, load durability, and other testing classes
related to operation, revision and transition factors.

22. Describe the various types of black box tests.

💡 237 (5) - explain each type in short page 224 - 9.5

Black box testing involves testing a system with no prior knowledge of its internal workings

Operation factor testing classes (ADOORSS)

output correctness tests

test cases applied

test cases and boundary values

SQA 9
 CURIE operations (correctness. usability, reliability, interoperability, efficiency)

Documentation tests

functional description of system

installation manual

user manual

programmer manual

Availability tests

reaction time

required ⇒ combining class of tests with load tests, performing combined tests adjustments
reliability tests

deals with features

relate to hardware

less expensive, speedy

basis ⇒ statistical model

stress tests

load tests

maximal transactions per minute

computerized tests

durability tests

in physically extreme operating conditions

real time firmware required

security tests

access control

backup of databases

logging of transactions, system usage, access trials etc.

training usability tests

defined by the resources needed to train a new employee

operational usability tests

focus on operator’s productivity

quantitatively and qualitatively

performed manually by means of time

studies

Revision factor testing classes (MFT)

Maintainability tests

system structure abides by the standards or not

support of future maintenance activities

programmer’s manual according to standards or not

internal documentation

Flexibility tests

such as adequate modular structure and application of parametric options to provide a wide range of possible
applications.

SQA 10
 Testability tests

deal with the ease of testing the software system

Transition factor testing classes (REPS)

Portability tests

variables ⇒ the operating systems, hardware and communication equipment standards,

Reusability tests

define reusable components

important for OOP

Software interoperability tests

deals with software capabilities of interfacing

equipment and other software packages, to enable them to operate jointly as
one complex computerized system

Equipment interoperability tests

deals with the equipment’s firmware interfacing

other equipment units

23. Explain the Alpha and Beta tests

💡 page 272 - 10.4

24, Describe the process of planning and designing tests

💡 page 274 (1), page 247

Determining the test methodology

The tests to be planned include:
■ Unit tests
■ Integration tests
■ System tests.

issues to be considered

■ What to test?
■ Which sources to use for test cases?
■ Who is to perform the tests?
■ Where to perform the tests?
■ When to terminate the tests?

Planning unit and integration tests

SQA 11
 Planning the system test
test case data

test case sources

test cases for reused software

Designing the tests.

SQA 12
 25. List the main types of automated software tests.

💡 page 275 (3), page 271 - frame 10.7, page 269 - 10.3.3, page 268 - frame 10.6

Automated testing is a process that validates if software is functioning appropriately and meeting requirements
before it is released into production.

SQA 13
 26.Explain the implementation of alpha and beta site test and discuss their advantages and disadvantage

SQA 14
 💡 page 276 (5) - also read page 272

27. list the major objectives of software maintenance contract reviews

💡 page 288

Customer requirements clarification

Type of corrective maintenance services required

user population and types of applications

location of users

Adaptive and functionality improvement maintenance

Review of alternative approaches to maintenance provision

Subcontracting for sites or type of service

Performance of some services by the customer

Review of estimates of required maintenance resources

examined on the basis of the required maintenance services

clarified by the proposal team

availability of maintenance teams

Review of maintenance services to be provided by subcontractors and/or the customer

definition of the services

quality assurance

follow-up procedures

Review of maintenance costs estimates

reviewed on the basis of required resources

28. List the infrastructure tools that support maintenance quality assurance.

💡 page 301 (4) - read along with managerial control

Software maintenance procedures and work instructions

■ Remote handling of requests for service in cases of software failure

■ On-site handling of customer requests for service in cases of software failure
■ User support service
■ Quality assurance control of software correction and user support activities
■ Customer satisfaction surveys
■ Certification of corrective maintenance and user support team members.

Training and certification of maintenance teams

functional improvements

motivated by the need to supply the services specified in maintenance contracts

rigorous programs

Quality-supporting devices

■ Checklists for location of causes for a failure – to be applied by the maintenance technician.
■ Templates for reporting how software failure were solved, including findings of the correction process.
■ Checklists for preparing a mini testing procedure document.

SQA 15
 Preventive and corrective actions

■ Changes in content and frequency of customer requests for user support services
■ Increased average time invested in complying with customer’s user support requests
■ Increased average time invested in repairing customer’s software failures
■ Increased percentage of software correction failures.

Configuration management

failure repair

group replacement

decision making, type of contracts

planning, allocating resources

determining timetable

Software maintenance documentation and quality records

■ Supply vital data for preventive and corrective actions (as mentioned earlier)
■ Support the handling of future customer failure reports and user
support requests
■ Provide evidence in response to future customer claims and/or complaints.

29. List the main managerial tools for controlling software maintenance quality and explain their importance.

💡 page 301 (5)

Performance controls for software maintenance services

software correction

■ Increased resources utilization

■ Decreased rate of remote failure repairs (low cost repairs) versus customer’s on-site repairs
■ Increased rate of on-site repairs at long-distance locations and overseas services
■ Increased percentage of failures to meet repair schedule requirements
■ Increased rate of faulty repairs, and list of specific “model” cases of
extreme failure situations
■ Lower customer satisfaction based on customer satisfaction surveys.

user support

■ Increased rates of requests for service for a specific software system,

for service type, etc.
■ Increased resource utilization in user support services
■ Increased rate of failures to provide requested consulting services
■ Increased rate of faulty consulting, and specific cases of “outstanding” failures
■ Customer satisfaction information based on customer satisfaction
surveys.

Quality metrics for software maintenance

■ Estimation of resource requirements when preparing maintenance plans

for the next period
■ Comparison of methods of operation
■ Initiation of preventive and corrective actions
■ Estimation of resource requirements as a basis for proposals for new or adjusted maintenance services.

Costs of software maintenance quality

cost of prevention

costs of appraisal

costs of managerial preparation and control

costs of internal failure

SQA 16
 costs of external failure

costs of managerial failure

Costs of external failure of software corrective maintenance activities

software corrections:

external quality costs initiated by users

corrections during contracted maintenance

cost of re-correction

user support services:

inherent during warranty period

regular service during warranty period

second consultation in case of initial consultation

30. The main component of real CASE tools is the repository.” (1) Define “repository” in your own words. (2) List
the functions a repository fulfills and explain their impact on software development productivity. (3) List the
functions a repository serves and explain their impact on software quality

💡 page 326

contains project information

maintains consistency of documentation

computerized management

guarantees standardization according to style and structure procedures

repository query display parts of design texts, charts and cross-referencing queries and requirement tracing

roles of repository:

Read: Recommended for non-code contributors who want to view or discuss your project

Triage: Recommended for contributors who need to proactively manage issues and pull requests without write
access

Write: Recommended for contributors who actively push to your project

Maintain: Recommended for project managers who need to manage the repository without access to sensitive or
destructive actions

Admin: Recommended for people who need full access to the project, including sensitive and destructive actions
like managing security or deleting a repository

impact on software productivity:

workflow control

code reviews for new updates

integration with other collaboration systems

great interface

great pricing

SQA 17
 31. Explain the contribution of procedures to software quality assurance.

SQA procedures are assumed to reflect the most adequate method known to date for the performance of design and
maintenance activities. SQA procedures that are
up-to-date and fully implemented by developers and maintenance teams assure conformity of their activities to the
software’s quality requirements and performance of the associated activities in an efficient and effective performance. At
the same time, uniform development and maintenance enables easier and more effective professional review together
with better communication with the maintenance team. It likewise facilitates cooperation and coordination between all the
bodies, internal and external, involved in the project. Not less important is the reduction in errors made possible by
uniformity.

32.List the activities involved in maintaining an organization’s procedures manual. List some of the contents of
procedures manual

💡 page 340

The activities involved include the activities for preparing new procedures, updating existing procedures and
implementing new and updated procedures. Involved in these efforts are the organization’s SQA team members in
addition to members of ad hoc committees gathered to prepare a new or update an existing procedure. Participants in
the implementation process include unit leaders and SQA trustees.

SQA 18
 preparing new procedures

conceptual and organizational frameworks that determine the menu of the proposed procedures

appointment of an ad hoc committee

consulting

reduced applicability

implementation of procedures

distribution of materials

insufficient instructions to the team

follow up and individual instructions

disregard to new procedures

update procedures

■ Technological changes in development tools, hardware, communication equipment, etc.

■ Changes in the organization’s areas of activity
■ User proposals for improvement
■ Analysis of failures as well as successes
■ Proposals for improvements initiated by internal audit reports
■ Learning from the experience of other organizations
■ Experiences of the SQA team

33. What are Templates? Explain the main contribution of templates to software quality assurance

What are templates?

💡 page 353

a template is “a gauge, pattern or mold (as a thin plate or board) used as a guide to the form of a piece
being made” (Webster’s New College Dictionary). When applied to software engineering, the term template
refers to a format (especially tables of contents) created by units or organizations, to be applied when
compiling a report or some other type of document. Application of templates may be obligatory for some
documents and elective for others; in some cases, only part of a template (e.g., specific chapters or general
structure) is demanded.

Explain the main contribution of templates to software quality assurance.

Facilitates the process of preparing documents

saves time

copying allowed

SQA 19
 Ensures that documents prepared by the developer are more complete

overlooking a topic is impossible

important stuff already defined

Provides for easier integration of new team members

easy finding of information

smooths ongoing document prep

Facilitates review of documents

no need to study document structure

less time consuming

simplifies review of completed documents

Enables easier location of the information

34. Discuss the objectives of Training and certification and list the activities of Training and certification process
with a neat diagram.

SQA 20
 35. Discuss what is needed to prepare a training and updating program.

💡 page 364

■ Determine the professional knowledge requirements for each position

■ Determine the professional training and updating needs
■ Plan the professional training program
■ Plan the professional updating program
■ Define positions requiring certification
■ Plan certification processes
■ Deliver training, updating and certification programs
■ Perform follow-up of trained and certified staff.

The three activities to be performed prior to planning a program are as follows:

■ Determine the knowledge requirements for each position. These include knowledge obtained while acquiring a
general professional education with the addition of the internally generated knowledge and skills required within the
organization.
■ Determine training and professional updating needs. These needs are ascertained through comparisons of the
staff’s knowledge with the state of the art.
These should be specified for three populations:
– New employees (training)
– Employees assigned to new position (retraining)
– Other staff (professional updating).
Training and updating needs should also be determined by performance requirements, based on feedback transmitted by
the organization’s various units.

SQA 21
 ■ Plan training and updating programs. These programs will respond to the following issues:
– The use of in-house training teams and facilities or outsourcing
– The timing of the training and updating activities (whenever possible)
– The use of e-learning programs.

36. List the main components of a certification program.

💡 page 365

A certification program defines position requirements and responsibilities for carrying out the program and its revision.
Certification requirements may include some or even all of the following components, depending on their relevance to the
task or position:

Professional education

skills and knowledge

relevant procedures and instructions

Internal training courses

training ⇒ new employees

retraining ⇒ for employees assigned new roles

updating ⇒ for staff members

planning

defining positions requiring training

activities involved

SQA 22
 Professional experience in the current organization or another organization

education

internal training courses

assessment of achievements

evaluation by direct superior

Evaluation of the candidate’s achievements and ability as found in periodic performance assessments

demonstration

assessment

mentor’s supervision

37. Study SKF Advanced Software is a medium-sized software house. The firm’s certification requirements
document for programming team leader is presented in Frame 16.2

page 369

38. Explain The corrective and preventive actions process(CAPA)

page 379 of book

💡 read summary questions on page 388 (all of them)

SQA 23
 39.List the participants in the CAPA process and their contribution to its successful implementation

💡 page 388 of the book

The CAPA process is carried out by the joint efforts of a permanent CAPA body together with ad hoc team
participants. The permanent CAPA body, commonly called the CAB, activates the CAPA process by screening
information, appointing members of targeted ad hoc CAPA teams, promoting implementation and following up
the process. The ad hoc CAPA team’s task is to analyze information about a given topic in addition to
developing solutions and a CAPA process. The team members are expected to implement the CAPA and use
CAB-provided assistance, if needed. Most members of ad hoc CAPA teams are department staff members
experienced in the subject matter.

41. Define software configuration version and list the main tasks of software change control.

💡 Software configuration version

An approved selected set of documented SCI versions that constitute a

software system or document at a given point of time, where the activities
to be performed are controlled by software configuration management
procedures. The software configuration versions are released according to
the cited procedures.

Software change management controls the process of introducing changes

mainly by doing the following:

Examining change requests and approving implementation of appropriate requests.

the factors affecting the decision whether to implement a change include:

Expected contribution of the proposed change

Urgency of the change

Effect of the proposed change on project timetables, level of service, etc.

Efforts required in making the change operational

SQA 24
 Required software quality assurance efforts

Estimated required professional resources and cost of performing the change.

Quality assurance efforts are required at two levels:

Quality assurance of each of the changed SCIs

reviews and testing plans to be carried out by professional testers

Quality assurance of the entire new software system version (that includes changed SCIs).

changed SCIs replace the former SCIs

The main tasks of software change management can be described as:

Examining change requests and approving implementation those requests that

qualify.

Controlling the changes and assuring the quality of approved changes.

Documenting the approved changes.

Applying mechanisms that prevent more than one team from simultaneously
introducing changes into the same SCI.

42.Explain software change control and discuss the factors affecting the decision to implement a change.
https://www.guru99.com/change-control-business-analyst.html

43.Discuss the issues covered by documentation control procedures.

https://www.isotracker.com/blog/top-5-document-control-mistakes/

44.Discuss components of project progress control in detail.

Control of risk management activities

software development risk items identified in the pre project stage

systematic risk management activities ⇒ lower risks

control ⇒ periodic risk assessment
Project schedule control

compliance with its approved and contracted

timetables

Follow-up is based mainly on milestones

focus of control activities on critical delays, those that may

substantially affect final completion of the project.

milestone reports and other periodic reports

Project resource control

professional human resources

software development and testing demand more control

internal composition or allocation

review of itemized expenditures

Project budget control

human resources

development and testing facilities

purchase of COTS software

payments to subcontractors

SQA 25
 45.Compare the KLOC and function points measures for the size of a software system

💡 page 443. read the metrics as well, page 462 - (4)

46.Explain how software quality metrics are categorized.

💡 page 462 - (3), description - page 443

47. Explain Function point method with the help of an example.

💡 page 469

48. Discuss HD quality metrics.

💡 page 449

49. Explain the process of defining new software quality metrics.

💡 page 455. diagram also

50. Explain the classic software quality costs model

💡 page 478

51. Write short note on Implementation of a cost of software quality system.

💡 page 485

52. Write short note on Problems in the application of cost of software quality metrics

💡 page 460, 459

53. Explain The ISO 9000-3 certification process.

https://www.geeksforgeeks.org/iso-9000-certification-in-software-engineering/

SQA 26
 54. Discuss The CMM model levels and key process areas (KPAs)

https://www.geeksforgeeks.org/levels-of-capability-maturity-model-cmm/

https://www.tutorialspoint.com/cmmi/cmmi-process-areas.htm

55. Discuss The Bootstrap methodology.

💡 page 517 - 23.5,

56. List the actors in a typical quality assurance organizational framework.

💡 page 578 - (1)

57.What is Management review? Elaborate on management review report.

SQA 27
 💡 page 575 - frame 25.3

Management review is the name given to the periodic meeting convened to allow executives to obtain an
overview of their organization’s software quality issues. Management reviews tend to be scheduled for once or
twice a year. A management review report, prepared by the SQA unit, sets the stage for the discussions by
providing items that appear on the meeting’s agenda

58. Illustrate with the help of a diagram model for an SQA unit’s organizational structure.

💡 page 567 - VII.2

59. Describe the typical tasks of the head of an SQA unit

https://www.tutorialspoint.com/software_quality_management/software_quality_management_sqa_unit.htm

60. IEEE/EIA Std 12207 – software life cycle processes

💡 page 537 - 24.2

Describe the tasks involved in establishment and maintenance of a controlled documents list.

💡 page 422 - (2)

SQA 28