Software Specification

RE Process Criticality

1 pts

volume_mute

Software specification (requirements engineering) is described as a particularly critical stage of the software process. Why?

Because it requires the largest development team

Because it always takes the longest time of any process stage

Because errors at this stage inevitably lead to later problems in system design and implementation

Because it is the most expensive stage to carry out

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 the correct description to each level.

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 of requirements 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

Feasibility Study Purpose

1 pts

volume_mute

What is the primary purpose of the feasibility study in the requirements engineering process?

To write the complete system requirements document

To estimate whether user needs can be satisfied using current technology and within budget, informing the decision of whether to proceed

To test the system against customer data

To derive requirements through observation and discussions with users

note_alt Add notes

flag Flag

Correct Answer

Explanation

Feasibility Study Characteristics

1 pts

volume_mute

A feasibility study should be:

Performed after requirements specification is complete

Comprehensive and take several months

Relatively cheap and quick

Carried out by an external consulting firm only

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Elicitation and Analysis

1 pts

Complete the sentence using the correct terms.

Requirements elicitation and analysis is the process of deriving the system requirements through (1) of existing systems, discussions with potential users and procurers, (2), and so on.

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

observation

task analysis

retiring

note_alt Add notes

flag Flag

Correct Answer

Explanation

System Models in Elicitation

1 pts

volume_mute

During requirements elicitation and analysis, one or more system models and prototypes may be developed. What is their purpose?

To generate executable code automatically

To replace the requirements document entirely

To help you understand the system to be specified

To test the final system with real customer data

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Specification Activity

1 pts

volume_mute

Requirements specification is the activity of translating the information gathered during the analysis activity into a document that defines a set of requirements. Which two types of requirements may be included in this document?

User requirements

System requirements

Design specifications

Acceptance test plans

Code documentation

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Validation Purpose

1 pts

volume_mute

What does the requirements validation activity check for?

Whether the system design matches the architecture

Whether the code compiles correctly

Whether the requirements are realistic, consistent, and complete

Whether acceptance test plans have been written

note_alt Add notes

flag Flag

Correct Answer

Explanation

RE Activities — Strictly Sequential?

1 pts

volume_mute

True or False: The activities in the requirements engineering process are carried out in a strict sequence, one after the other, with no overlap.

False

True

note_alt Add notes

flag Flag

Correct Answer

Explanation

RE in Agile Methods

1 pts

volume_mute

How are requirements handled in agile methods such as extreme programming?

Requirements are defined solely by the project manager without user involvement

Requirements are fully documented before any development starts

Requirements are skipped entirely in favour of working code

Requirements are developed incrementally according to user priorities, with users who are part of the development team eliciting them

note_alt Add notes

flag Flag

RE Process Criticality

Correct Answer

Explanation

Two Levels of Requirements

Level

Description

Correct Answer

Explanation

Feasibility Study Purpose

Correct Answer

Explanation

Feasibility Study Characteristics

Correct Answer

Explanation

Requirements Elicitation and Analysis

Correct Answer

Explanation

System Models in Elicitation

Correct Answer

Explanation

Requirements Specification Activity

Correct Answer

Explanation

Requirements Validation Purpose

Correct Answer

Explanation

RE Activities — Strictly Sequential?

Correct Answer

Explanation

RE in Agile Methods

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: