Coping with Change Review

Why Change Is Inevitable

1 pts

volume_mute

Change is described as inevitable in all large software projects. Which of the following are identified as sources of change? Select all that apply.

The business procuring the system responds to external pressures and management priorities change

System requirements change as the business environment evolves

New technologies become available, opening new design and implementation possibilities

The development team runs out of budget

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Rework and Its Cost

1 pts

volume_mute

Complete the sentence.

Change adds to the costs of software development because it usually means that work which has already been completed has to be redone. This is called (1). For example, if requirements in a system have been analysed and new requirements are then identified, some or all of the requirements analysis has to be (2).

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Change Avoidance vs Change Tolerance

1 pts

volume_mute

Descriptions

×The software process includes activities that can anticipate possible changes before significant rework is required — e.g. developing a prototype

×The process is designed so that changes can be accommodated at relatively low cost — normally involves some form of incremental development

Change avoidance

Change tolerance

Two approaches can reduce the costs of rework. The diagram below shows how they both lead to lower overall costs.

Classify each description under the correct approach.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Prototype — Primary Purpose

1 pts

volume_mute

Which statement best describes the primary purpose of a software prototype?

To replace requirements documentation entirely

To be used exclusively for user interface design

To demonstrate concepts, try out design options, and find out more about the problem and its possible solutions

To serve as the final delivered system after some final polishing

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Throwaway Prototype — Why Unwise as Final System

1 pts

volume_mute

Why is it generally unwise to deliver a throwaway prototype as the final operational system?

Because non-functional requirements ignored during prototyping cannot be retrofitted, the prototype is undocumented, its structure has degraded, and quality standards were relaxed

Because prototypes are built using programming languages that cannot be deployed

Because prototypes always cost more than production systems

Because customers are legally prohibited from using prototype software

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

First Increment — What It Contains

1 pts

volume_mute

In incremental delivery, what does the first increment typically contain, and why?

The lowest-priority features, to save the most important ones for later when the team is more experienced

A complete prototype of the final system, which is then refined in later increments

The highest-priority services, so customers can gain value and use the system immediately while also gaining experience that informs later increments

Only documentation and installation scripts, with no working functionality

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Incremental Delivery — Testing Benefit

1 pts

volume_mute

True or False: Because the highest-priority services are delivered first and increments are then integrated, the most important system services receive the most testing throughout the delivery process.

False

True

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Spiral Model — Risk-Driven Nature

1 pts

volume_mute

The spiral model is described as a risk-driven software process framework. What does this mean in practice?

The project is cancelled whenever a risk is identified

The development model chosen for each phase depends on an explicit assessment of the risks identified, and activities are carried out to reduce those risks

Only the highest-risk systems are allowed to use the spiral model

Risk is measured purely in financial terms and drives the project budget

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Waterfall Model — When to Use

1 pts

volume_mute

The diagram below shows the waterfall model's cascading stages.

Requirements DefinitionSystem & Software DesignImplementation & Unit TestIntegration & System TestOperation & Maintenance

In what situation should the waterfall model be used?

When the development team is using an agile methodology

When requirements are expected to change frequently throughout development

When the system must be delivered in multiple increments

When the requirements are well understood and unlikely to change radically during system development

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Reuse-Oriented — Requirements Compromise

1 pts

volume_mute

What is an inevitable disadvantage of the reuse-oriented software engineering approach?

It requires the complete system to be specified before any components can be reused

It always takes longer to deliver than developing from scratch

It can only be used for web-based systems

Requirements compromises are inevitable because available components rarely match requirements exactly, and some control over system evolution is lost

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Requirements Validation — What It Checks

1 pts

volume_mute

What does the requirements validation activity check requirements for?

Whether the code compiles and runs correctly

Whether the system architecture matches the database design

Whether the requirements are realistic, consistent, and complete

Whether the acceptance test plans have been formally signed off

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Feasibility Study — Key Characteristics

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Characteristic

Cost

Purpose

Description

Should be relatively cheap and quick

To inform the decision of whether or not to go ahead with a more detailed requirements analysis

Match each characteristic of a feasibility study to its correct description.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Interface Design — Why Unambiguous

1 pts

volume_mute

Why must an interface specification in software design be unambiguous?

So that end-users can read and validate the interface specification directly

So that the database schema can be auto-generated from the interface

So that it can be automatically converted into executable code

So that a component can be used without other components needing to know how it is implemented, enabling components to be designed and developed concurrently

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Debugging vs Testing — Distinction

1 pts

volume_mute

Statements

×Establishes the existence of defects in a program

×Concerned with locating and correcting those defects

Testing

Debugging

Testing and debugging are two different processes. Classify each statement under the correct process.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Acceptance Testing — Data Source

1 pts

volume_mute

What makes acceptance testing distinct from earlier testing stages?

It uses data supplied by the system customer rather than simulated test data

It is the only testing stage that checks component interfaces

It focuses exclusively on non-functional requirements such as performance

It is performed only by an independent external testing team

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Software Engineering as Evolutionary Process

1 pts

volume_mute

Which statement best reflects the modern view of the relationship between software development and software maintenance?

It is more realistic to think of software engineering as an evolutionary process where software is continually changed over its lifetime, making the development/maintenance distinction increasingly irrelevant

Only safety-critical systems require ongoing software evolution

Development and maintenance are completely separate disciplines requiring different teams

Maintenance is less important than development and should receive less investment

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Classify Approaches by Strategy

1 pts

volume_mute

Techniques

×System prototyping

×Incremental delivery

×Boehm's spiral model

Change avoidance

Change tolerance

Both

Classify each of the following techniques under the strategy it primarily supports.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Four Fundamental Process Activities

1 pts

volume_mute

Please drag and drop the options to sort them

Every software process must include four fundamental activities. Sort them into the order in which they are typically addressed in terms of dependency.

Software validation

Software design and implementation

Software evolution

Software specification

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

Three Generic Process Models

1 pts

volume_mute

To complete the line match

Click on an item in the first group
Click on an item in the second group
To delete a match, double click on a line

Model

Waterfall

Incremental development

Reuse-oriented

Characteristic

Takes fundamental process activities and represents them as separate sequential phases

Interleaves specification, development and validation; system developed as a series of versions each adding functionality

Based on a large base of reusable components; focuses on integrating these into a system rather than developing them from scratch

Match each generic process model to its defining characteristic.

note_alt Add notes

flag Flag

volume_mute

Correct Answer

Explanation

V&V — Two Goals

1 pts

volume_mute

Software Verification and Validation (V&V) is intended to show two things. Which two? Select both.

That a system has been developed on time and within budget

That a system conforms to its specification

That a system is profitable to operate

That a system meets the expectations of the system customer

note_alt Add notes

flag Flag

volume_mute

Why Change Is Inevitable

Correct Answer

Explanation

Rework and Its Cost

Correct Answer

Explanation

Change Avoidance vs Change Tolerance

Correct Answer

Explanation

Prototype — Primary Purpose

Correct Answer

Explanation

Throwaway Prototype — Why Unwise as Final System

Correct Answer

Explanation

First Increment — What It Contains

Correct Answer

Explanation

Incremental Delivery — Testing Benefit

Correct Answer

Explanation

Spiral Model — Risk-Driven Nature

Correct Answer

Explanation

Waterfall Model — When to Use

Correct Answer

Explanation

Reuse-Oriented — Requirements Compromise

Correct Answer

Explanation

Requirements Validation — What It Checks

Correct Answer

Explanation

Feasibility Study — Key Characteristics

Characteristic

Description

Correct Answer

Explanation

Interface Design — Why Unambiguous

Correct Answer

Explanation

Debugging vs Testing — Distinction

Correct Answer

Explanation

Acceptance Testing — Data Source

Correct Answer

Explanation

Software Engineering as Evolutionary Process

Correct Answer

Explanation

Classify Approaches by Strategy

Correct Answer

Explanation

Four Fundamental Process Activities

Correct Answer

Explanation

Three Generic Process Models

Model

Characteristic

Correct Answer

Explanation

V&V — Two Goals

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: