Review — Software Processes

A comprehensive review of software processes, covering all fundamental knowledge areas: the three generic process models (waterfall, incremental, reuse-oriented), the four process activities (specification, design and implementation, validation, evolution), coping with change (prototyping, incremental delivery, Boehm's spiral model), and the Rational Unified Process.

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

QUESTION OF

Views #: 23

Questions #: 19

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Four Fundamental Process Activities

1 pts

Please drag and drop the options to sort them

Every software process must include four fundamental activities. Sort them into the order of dependency.

Software validation

Software design and implementation

Software evolution

Software specification

note_alt Add notes

flag Flag

Correct Answer

Explanation

Waterfall Model — Best Use Case

1 pts

volume_mute

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

In what situation should the waterfall model be used?

When the system must be delivered in multiple increments to customers

When the development team is using an agile methodology

When requirements are expected to change frequently during development

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

note_alt Add notes

flag Flag

Correct Answer

Explanation

Incremental Development — Three Benefits

1 pts

volume_mute

Incremental development has three important benefits compared to the waterfall model. Which of the following are those benefits? Select all that apply.

More rapid delivery and deployment of useful software to the customer

Complete system documentation is automatically produced

The system architecture is always more stable than in waterfall

The cost of accommodating changing customer requirements is reduced

It is easier to get customer feedback on development work done

note_alt Add notes

flag Flag

Correct Answer

Explanation

Reuse-Oriented Model — Inevitable Disadvantage

1 pts

volume_mute

The reuse-oriented software engineering approach reduces development cost and risk. What is its inevitable disadvantage?

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

It always takes longer to deliver than developing from scratch

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

It can only be applied to web-based systems

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Engineering Process

1 pts

The diagram below shows the four activities in the requirements engineering process.

Classify each activity under its correct description.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Two Levels of Requirements

1 pts

Requirements are usually presented at two levels of detail. Match each level to its correct audience and 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

Level

User requirements

System requirements

Description

Abstract statements for the customer and end-user of the system

A more detailed description of the functionality to be provided, for system developers

note_alt Add notes

flag Flag

Correct Answer

Explanation

Testing vs Debugging

1 pts

Testing and debugging are two different processes. Classify each statement correctly.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three Testing Stages

1 pts

Software validation uses a three-stage testing process. Complete the sentence about acceptance testing.

In acceptance testing, the system is tested with data supplied by the (1) rather than simulated test data. This is the (2) stage before the system is accepted for operational use.

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

system customer

final

note_alt Add notes

flag Flag

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 conforms to its specification

That a system generates profit for the organisation

That a system meets the expectations of the system customer

That a system was developed on time and within budget

note_alt Add notes

flag Flag

Correct Answer

Explanation

Software Evolution — Modern View

1 pts

volume_mute

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

Development and maintenance are separate disciplines requiring entirely different teams

Maintenance is less important than development and should receive less investment

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

note_alt Add notes

flag Flag

Correct Answer

Explanation

Change Avoidance vs Change Tolerance

1 pts

Two approaches can reduce the costs of rework caused by change. Match each approach to its correct definition.

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

Approach

Change avoidance

Change tolerance

Definition

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 — normally involves incremental development

note_alt Add notes

flag Flag

Correct Answer

Explanation

Prototype — Purpose and Throwaway Risk

1 pts

volume_mute

Why is it generally unwise to deliver a throwaway prototype as the final operational system? Select all that apply.

Non-functional requirements ignored during prototyping cannot be retrofitted

Rapid change during development means the prototype is undocumented — only the prototype code exists as the design specification

The prototype structure has degraded through rapid change, making it difficult and expensive to maintain

Organisational quality standards are normally relaxed for prototype development

Prototypes always cost more to build than production systems

note_alt Add notes

flag Flag

Correct Answer

Explanation

Incremental Delivery — Advantages and Problems

1 pts

Classify each statement as either an advantage or a problem of incremental delivery.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Boehm's Spiral Model — Four Sectors

1 pts

volume_mute

The diagram below shows the four sectors of each loop in Boehm's spiral model.

What is the key feature that distinguishes the spiral model from other software process models?

It explicitly recognises risk and includes risk management activities to reduce those risks in every phase

It represents the process as a strict sequence of non-repeating phases

It is the only model that supports incremental delivery

It requires the complete system specification before any development begins

note_alt Add notes

flag Flag

Correct Answer

Explanation

RUP — Three Perspectives

1 pts

Unlike conventional process models that present a single view, the RUP is described from three perspectives. Complete the sentences.

The (1) perspective shows the phases of the model over time. The (2) perspective shows the process activities (workflows) that are enacted.

note_alt Add notes

flag Flag

Correct Answer

Explanation

RUP Four Phases

1 pts

The diagram below shows the four phases of the RUP.

Match each phase to its primary goal and output on completion.

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

Phase

Inception

Elaboration

Construction

Transition

Goal/Output

Establish a business case; output: go/no-go decision — project may be cancelled if contribution is minor

Understand problem domain, establish architecture; output: requirements model, architectural description, development plan

System design, programming, and testing; output: working software system ready for delivery

Move system to user community; output: documented software system working in its operational environment

note_alt Add notes

flag Flag

Correct Answer

Explanation

RUP — Phases vs Workflows

1 pts

volume_mute

True or False: In the RUP, phases are directly equated with process activities (workflows), just like in the waterfall model.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

RUP — Six Best Practices

1 pts

volume_mute

The RUP's practice perspective recommends six fundamental best practices. Which of the following is not one of the six?

Eliminate all design documentation to maximise coding time

Develop software iteratively

Visually model software

Manage requirements

Use component-based architectures

note_alt Add notes

flag Flag

Correct Answer

Explanation

Classify Techniques by Strategy

1 pts

Classify each technique under the change-management strategy it primarily supports.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Year 11 Year 12 Undergraduate

Four Fundamental Process Activities

Correct Answer

Explanation

Waterfall Model — Best Use Case

Correct Answer

Explanation

Incremental Development — Three Benefits

Correct Answer

Explanation

Reuse-Oriented Model — Inevitable Disadvantage

Correct Answer

Explanation

Requirements Engineering Process

drag and drop the selected option to the right place

Correct Answer

Explanation

Two Levels of Requirements

Level

Description

Correct Answer

Explanation

Testing vs Debugging

drag and drop the selected option to the right place

Correct Answer

Explanation

Three Testing Stages

Correct Answer

Explanation

V&V — Two Goals

Correct Answer

Explanation

Software Evolution — Modern View

Correct Answer

Explanation

Change Avoidance vs Change Tolerance

Approach

Definition

Correct Answer

Explanation

Prototype — Purpose and Throwaway Risk

Correct Answer

Explanation

Incremental Delivery — Advantages and Problems

drag and drop the selected option to the right place

Correct Answer

Explanation

Boehm's Spiral Model — Four Sectors

Correct Answer

Explanation

RUP — Three Perspectives

Correct Answer

Explanation

RUP Four Phases

Phase

Goal/Output

Correct Answer

Explanation

RUP — Phases vs Workflows

Correct Answer

Explanation

RUP — Six Best Practices

Correct Answer

Explanation

Classify Techniques by Strategy

drag and drop the selected option to the right place

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: