Incremental Delivery

Incremental Delivery — Core Concept

1 pts

volume_mute

The diagram below shows the incremental delivery process, where the loop repeats until the system is complete.

Which statement best describes incremental delivery?

An approach where the entire system is developed and then delivered to the customer in a single release

An approach where customers write their own requirements for each increment

An approach where only the user interface is delivered incrementally while the backend is built in one phase

An approach where some of the developed increments are delivered to the customer and deployed for use in an operational environment

note_alt Add notes

flag Flag

Correct Answer

Explanation

Service Priority in Incremental Delivery

1 pts

volume_mute

In an incremental delivery process, how are services allocated to increments?

All services are allocated to increments simultaneously and developed in parallel

The lowest-priority services are delivered first to allow time to develop critical features

The allocation depends on service priority, with the highest-priority services implemented and delivered first

Services are allocated randomly to ensure fair distribution of work

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Changes During Incremental Delivery

1 pts

Complete the sentence about how requirements are handled during incremental delivery.

Once an increment is under development, requirements changes for the (1) increment are not accepted. However, further requirements analysis for (2) increments can take place.

Please drag and drop the selected option in the right place or type it instead

current

later

note_alt Add notes

flag Flag

Correct Answer

Explanation

Advantages of Incremental Delivery

1 pts

volume_mute

Which of the following are stated advantages of incremental delivery? Select all that apply.

Customers do not have to wait until the entire system is delivered before gaining value from it

The most important system services receive the most testing because they are delivered first and integrated throughout

Customers can use early increments as prototypes and gain experience that informs their requirements for later increments

The complete system specification is always available from the start of the project

Incremental delivery guarantees zero defects in the final system

note_alt Add notes

flag Flag

Correct Answer

Explanation

Incremental Delivery vs Incremental Development

1 pts

volume_mute

What is the key difference between incremental delivery and incremental development?

In incremental delivery, developed increments are actually deployed for use in an operational environment; in incremental development, a system may be developed incrementally but not necessarily deployed with each increment

Incremental development uses sprints; incremental delivery does not

Incremental delivery applies only to web systems; incremental development applies to all systems

There is no difference — the two terms mean exactly the same thing

note_alt Add notes

flag Flag

Correct Answer

Explanation

Problems with Incremental Delivery — Common Facilities

1 pts

volume_mute

What problem arises with common facilities in an incremental delivery approach?

Most systems require basic facilities used by different parts of the system, but since requirements are not defined in full detail until each increment is implemented, it can be hard to identify common facilities needed by all increments

Common facilities can only be built by specialised teams not involved in increment development

Common facilities are automatically generated by CASE tools in incremental approaches

Common facilities are always built in the first increment, leaving no time for other features

note_alt Add notes

flag Flag

Correct Answer

Explanation

Replacement Systems and Incremental Delivery

1 pts

volume_mute

Why is incremental delivery particularly difficult when a replacement system is being developed?

Replacement systems always have more requirements than new systems

Legal regulations prohibit incremental delivery of replacement systems

Replacement systems must always use the waterfall model

Users want all the functionality of the old system and are often unwilling to experiment with an incomplete new system, making useful customer feedback difficult to obtain

note_alt Add notes

flag Flag

Correct Answer

Explanation

Procurement Contracts and Incremental Delivery

1 pts

volume_mute

How does the incremental delivery approach conflict with the procurement model of many organisations?

Procurement rules prohibit delivering software before it is fully tested

Incremental delivery always exceeds budget because each increment is billed separately

Incremental delivery requires more staff than most organisations can afford

In the incremental approach, there is no complete system specification until the final increment is specified, but many organisations' procurement models require the complete system specification as part of the development contract

note_alt Add notes

flag Flag

Correct Answer

Explanation

When Incremental Delivery Is Not Appropriate

1 pts

volume_mute

Incremental delivery is not always the best approach. Which types of system are identified as unsuitable for incremental delivery? Select all that apply.

Small single-user desktop applications

Very large systems where development involves teams working in different locations

E-commerce web applications

Embedded systems where the software depends on hardware development

Critical systems where all requirements must be analysed to check for interactions that may compromise safety or security

note_alt Add notes

flag Flag

Correct Answer

Explanation

Both Change Avoidance and Change Tolerance

1 pts

Incremental delivery is unique among the two approaches to coping with change because it supports both strategies. Match each strategy to its correct description.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Strategy

Change avoidance

Change tolerance

Description

The software process includes activities that anticipate possible changes before significant rework is required

The process is designed so that changes can be accommodated at relatively low cost

note_alt Add notes

flag Flag

Incremental Delivery — Core Concept

Correct Answer

Explanation

Service Priority in Incremental Delivery

Correct Answer

Explanation

Requirements Changes During Incremental Delivery

Correct Answer

Explanation

Advantages of Incremental Delivery

Correct Answer

Explanation

Incremental Delivery vs Incremental Development

Correct Answer

Explanation

Problems with Incremental Delivery — Common Facilities

Correct Answer

Explanation

Replacement Systems and Incremental Delivery

Correct Answer

Explanation

Procurement Contracts and Incremental Delivery

Correct Answer

Explanation

When Incremental Delivery Is Not Appropriate

Correct Answer

Explanation

Both Change Avoidance and Change Tolerance

Strategy

Description

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: