it is a set of activities that define and assess the adequacy of software process to provide evidence which establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended processes.

Software developers and their organizations rely on this. Software bugs can have immediate impacts on clients or customers.

Reputation

Poor quality software tends to be expensive to develop and maintain, which can negatively affect organizations or end up maintaining the software in the longer term. These costs are often referred to as “technical debt.”

Limiting Technical Debt

The development and use of the software might require some form of certification, which can often require evidence of the application of various quality control and assessment measures.

Software Certification

There may be overriding legal obligations that apply to organizations that use the software. As such, every practicable measure must be taken to demonstrate that the software system does not pose a risk to its users.

Legality

In cases where a software system is not covered by software certification and legislation, and where its failure is not necessarily business or safety-critical, there can remain moral obligation to the users. This implies that software engineers should do whatever is possible to maximize the quality of their software and to prevent it from containing potentially harmful bugs.

Ethical Codes of Practice

It displays the functionality of the product under development, but may not actually hold the exact logic of the original software

Software prototyping

Prototyping software is used to achieve which of the following?

Allow users to evaluate the software system design and how the software actually works, Clarify the functionalities of the software to both users and developers., Reduce cost and time relative to building software product and iterating the process., Reduce the need to recreate the software system due to some gaps on the implementation.

Which statement is NOT TRUE about Throwaway Prototyping

The prototypes on this paradigm are reused after the testing in a way that they are altered according to the test results and then reused in a new test cycle

Which statement is NOT TRUE about Evolutionary Prototyping

This is used in early design stages where the gathered requirements are still unclear

It pertains to how it conveys the look and feel of the final product

Prototype Fidelity

Its role is to check and test the visual appearance and user flows of a software.

Low-Fidelity Prototyping

This prototyping technique is used to create a prototype based on hand drawings that represent user interfaces of the software. This allows developers to explore ideas and refine designs quickly.

Paper-Based Prototyping

It is a visual representation of a product page that developers can use to arrange pages of user interfaces. These are used to create interactive prototypes by linking them together.

Wireframing

Which statement is NOT TRUE about High-Fidelity Prototyping

Its role is to check and test the visual appearance and user flows of a software.

It is a formalized peer review process for detecting and correcting defects or bugs in software artifacts.

Software inspection or software review

Which statement is NOT TRUE about Fagan inspection methodology?

It is a structured approach to improve software quality.

Who developed the Fagan inspection methodology

Michael Fagan

S/He leads the inspection team and takes care of logistics.

Moderator

In Fagan inspection methodology, S/He is the creator of the software artifacts under inspection. S/He will actively answer all the questions regarding the artifacts during the inspection meeting. S/He is responsible for fixing identified defects and bugs in the artifacts.

Author

In Fagan inspection methodology, S/He is an experienced peer who can be a subject matter expert on the software artifacts under inspection.

Reader

In Fagan inspection methodology, S/He is responsible for writing and executing test cases for the software module or product. This role is focused on how the product would be tested.

Tester

What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of requirements and raise questions or concerns. The moderator records identified defects

Requirements

What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of design, compare it to requirements, and raise questions or concerns.

Design Inspection

What is the Inspection Type, Based on the Procedure stated? Inspectors review the code, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

Code Inspection

What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of test plan or specification, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

Test Plan Inspection

Which statement is NOT TRUE about Structured Walkthrough?

it is the act of systematically convening with fellow programmers to check each other’s code for faultsto ensure the code meets quality standards.

Which statement is NOT TRUE About Code Reviewing or Inspection?

It is the degree to which a software product meets the gathered requirements

This approach uses automated code analysis techniquesthat can pick out problematic patterns within the source code.

Tool-Driven Code Review

Which statement BEST DESCRIBES Developer-Driven Code Review?

The developers In this approach, the developers themselves reviews the code to pick out problems. Reviews the code to pick out problems.

a lightweight variant of the code inspections because it does not rely on face-to-face meetings. This operates on tools and development processes.

Modern Code Review

In Modern Code Review, it integrates reviewing tools such as Google’s Gerrit and Microsoft’s CodeFlow with version repositories to act as gatekeepers to commits.

Tool-Driven Code Review

In Modern Code Review, This development approach enforces modern code review and does not use code reviewing tools. This revolves around a mechanism known as a “pull request.”

Pull-Based Development

in Tool-Driven Code Review, What is the first Step?

The developer checks out a version from the repository and makes changes.

in Tool-Driven Code Review, What is the second Step?

This change is then submitted for review. This is often automatically initiated when the developer tries to push his/her change to the central version repository

in Tool-Driven Code Review, What is the third Step?

Before the commit can be finalized, the patch submitted by the developer is subject to review by a pool of reviewers.

in Tool-Driven Code Review, What is the fourth Step?

If the reviewers accept the patch, it is then passed to someone who verifies it by testing it, and finally commits the reviewed, verified code fragment to the version repository.

in Pull-Based Development, What is the first Step?

A developer who does not have the privileges to push his/her changes directly to the central repository takes a clone of the code from the repository then makes changes.

in Pull-Based Development, What is the second Step?

The developer then submits his/her proposed changes to the repository as a pull request.

in Pull-Based Development, What is the third Step?

A developer with appropriate privileges (referred to as “integrator”) examines the proposed changes, integrates them with their own clone of source code, and makes the commit