App Dev

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 quality assurance

Software quality

Software prototyping

Software certification

Poor quality software tendsto 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

Limiting Technical Debt

Software Certification

Legality

Ethical Codes of Practice

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

Legality

Ethical Codes of Practice

Reputation

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

Ethical Codes of Practice

Reputation

Limiting Technical Debt

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

Reputation

Limiting Technical Debt

Software Certification

G refers to building software application prototypes which displays the functionality of the product under development, but may not actually hold the exact logic of the original software.

Software prototyping

Software quality

Software quality assurance

Software certification

(find right ans) Prototyping software is used to achieve 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.

This is a relatively fast method of prototyping that focuses on employing prototypes to generate insights about the software design idea. The created prototypes on this paradigm are discarded after testing and after obtaining feedback. This is used in early design stages where the gathered requirements are still unclear.

Throwaway Prototyping

Evolutionary Prototyping

Low-Fidelity Prototyping

High-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

High-Fidelity Prototyping

Low-Fidelity Prototyping

Wireframing

Its role is to check and test the visual appearance and user flows of a software. A throwaway prototype can be created in low-fidelity

Wireframing

High-Fidelity Prototyping

Low-Fidelity Prototyping

Paper-Based Prototyping

Are created when developers have a solid understanding of what they are going to build. They need to test it with the actual users.

High-Fidelity Prototyping

Low-Fidelity Prototyping

Paper-Based Prototyping

Wireframing

Is a structured approach to improve software quality. It involves defect prevention, detection, and removal, as well as defect containment activities.

Software quality assurance

Software inspection

Software review

Fagan inspection methodology

Software testing and inspection are the two (2) commonly used methods to detect defects in software, while software inspections and reviews are concerned with the review of software artifacts.

Software quality assurance

Software inspection

Software review

Fagan inspection methodology

Is a formalized peer review process for detecting and correcting defects or bugs in software artifacts. Software artifacts are any things that have been documented and stored during the software development process, such as requirements document, source code, user documentation, and test plans and test cases.

Software quality assurance

Software inspection

Software review

Fagan inspection methodology

The objectives of this methodology are to identify and remove errors in the software products and to identify any systematic defects in the processes that are used to create software products.

Fagan inspection methodology

Software review

Software inspection

Software quality assurance

S/He is the creator of the software artifacts under inspection.________will actively answer all the questions regarding the artifacts during the inspection meeting.______is responsible for fixing identified defects and bugs in the artifacts.

Author

Moderator

Reader

Tester

What Activity and Role is this????

• Identify inspectors and roles.
• Verify if the materials are ready for inspection.
• Distribute inspection materials to participants.
• Arrange meeting place and time

Planning/Moderator

Overview/Author

Preparation/Inspectors

Inspection Meeting/Moderator and Inspectors

What Activity and Role is this????

• Participants prepare for the meeting.
• Checklists may be employed to facilitate the preparation.
• Read through the deliverables and mark up issues and questions.

Preparation/Inspectors

Inspection Meeting/Moderator and Inspectors

Process Improvement/ Inspectors

Rework/Author

What Activity and Role is this????

• Continuously improve the development and inspection process.
• Record the causes of major identified defects.
• Perform root cause analysis to identify any systemic defect with development or inspection process.
• Determine corrective action to address any systemic defects in the software process. • Make recommendations to the process improvement team.

Process Improvement/ Inspectors

Rework/Author

Follow-up/Moderator and Author

Planning/Moderator

What Activity and Role is this????

• The moderator sets the time limit for inspection and keeps the meeting focused.
• The inspectors perform their roles to find defects. The emphasis is to identify as many possible defects, not solutions.
• Record and classify defects.
• An inspection outcome is agreed.

Inspection Meeting/Moderator and Inspectors

Process Improvement/ Inspectors

Rework/Author

Follow-up/Moderator and Author

Find the right arrangement of the following steps of a structured walkthrough:

Step 1: The author circulates the deliverable, either physically or electronically, to the review audience.

Step 2: The author schedules a meeting with the reviewers.

Step 3: The reviewers familiarize themselves with the deliverable.

Step 4: The review leader chairs the meeting.

Step 5: The author brings the review audience through the deliverable, explains what each section aims to achieve, and requests comments from them as to its correctness.

Step 6: The scribe records errors, decisions, and any action items.

Step 7: A meeting outcome is agreed, and the author addresses all agreed items. If the meeting outcome results in a second review, then go back to Step 1.

Step 8: The deliverable is circulated to reviewers for sign off, and the reviewers sign off indicating that the author has correctly amended the deliverable.

Step 9: The author or project leader stores the comments and sign-offs.

1, 2, 3, 4, 5, ,6 ,7, 8, 9

1, 3, 5, 6, 7, 2, 4, 9

9, 3, 5, 6, 1, 2, 4, 7

9, 8, 7, 6, 5, 4, 3, 2, 1

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

Code reviewing or inspection

Tool-Driven Code Review

Developer-Driven Code Review

Modern code review

This approach uses automated code analysis techniquesthat can pick out problematic patterns within the source code. The source code analysis drive automated code reviews. The code checkers are often built-in into Integrated Development Environments (IDEs).

Tool-Driven Code Review

Developer-Driven Code Review

Modern code review

Code reviewing or inspection

Some properties of code quality are difficult to assess automatically. In this approach, the developers themselves reviews the code to pick out problems. Then, the reviewers manually assess source codes before deployment.

Developer-Driven Code Review

Tool-Driven Code Review

Modern code review

Code reviewing or inspection

Is 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

Developer-Driven Code Review

Tool-Driven Code Review

Code reviewing or inspection

To enable code reviews, integrate reviewing tools such as Google’s Gerrit and Microsoft’s CodeFlow with version repositories to act as gatekeepers to commits. A repository is a central file storage location.

Tool-Driven Code Review

Code reviewing or inspection

Developer-Driven Code Review

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

Tool-Driven Code Review

Pull-Based Development

Developer-Driven Code Review

Code reviewing or inspection

Unlock and Upgrade

Remove all limits from your Quizzes

App Dev

More Quizzes