The Software Requirements Document

This quiz covers the purpose and nature of the Software Requirements Specification (SRS), its diverse users and how each uses it, the level of detail required in different contexts, the standard structure of a requirements document based on the IEEE standard, and the debate between traditional requirements documents and agile approaches

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

QUESTION OF

Views #: 10

Questions #: 10

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

What Is the SRS?

1 pts

volume_mute

The Software Requirements Document (also called the software requirements specification or SRS) is best described as:

An official statement of what the system developers should implement, including both user requirements and a detailed system requirements specification

A technical design document describing the system architecture

A project schedule showing when each feature will be implemented

A test plan describing how the system will be validated after delivery

note_alt Add notes

flag Flag

Correct Answer

Explanation

Agile Argument Against Formal Requirements Documents

1 pts

volume_mute

Agile development methods argue against producing detailed requirements documents because:

Requirements change so rapidly that a requirements document is out of date as soon as it is written, so the effort is largely wasted

Formal requirements documents are only legally required for government contracts

Requirements documents are too expensive to print and distribute

Agile teams do not employ requirements engineers

note_alt Add notes

flag Flag

Correct Answer

Explanation

Value of a Short Supporting Document in Agile

1 pts

volume_mute

Even when using an agile approach for business systems with unstable requirements, why might it still be useful to write a short supporting requirements document?

To satisfy regulatory requirements that all projects must produce a full SRS

To replace user stories entirely in later iterations of the project

To define the business and dependability requirements for the system, which are easy to forget when focusing on functional requirements for the next release

To provide a detailed implementation specification for developers

note_alt Add notes

flag Flag

Correct Answer

Explanation

Users of the Requirements Document

3 pts

Match each user of a requirements document to how they primarily use it.

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

User

System Customers

Managers

System Engineers

System Test Engineers

System Maintenance Engineers

Primary Use

Use the requirements to understand the system and the relationships between its parts

Use the requirements to understand what system is to be developed

Specify the requirements and check that they meet their needs; specify changes to requirements

Use the requirements to plan a bid for the system and to plan the system development process

Use the requirements to develop validation tests for the system

note_alt Add notes

flag Flag

Correct Answer

Explanation

Level of Detail Required

2 pts

volume_mute

Which of the following factors influence how detailed a requirements document needs to be? Select all that apply.

The number of pages the project manager prefers

Whether the system is safety- or security-critical (requiring detailed analysis)

Whether an in-house iterative development process is used (allowing less detail since ambiguities can be resolved during development)

The color scheme chosen for the document

Whether the system is being developed by a separate company through outsourcing (requiring more precise specifications)

note_alt Add notes

flag Flag

Correct Answer

Explanation

IEEE-Based Requirements Document Structure

3 pts

Please drag and drop the options to sort them

Sort the following chapters of an IEEE-based requirements document into their correct order.

Preface

Introduction

Glossary

User Requirements Definition

System Architecture

System Requirements Specification

System Models

System Evolution

Appendices

Index

note_alt Add notes

flag Flag

Correct Answer

Explanation

Purpose of Each Document Section

2 pts

Match each requirements document section to its primary purpose.

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

Section

Preface

Glossary

System Evolution

Appendices

Purpose

Provides detailed, specific information related to the application being developed, such as hardware requirements and database descriptions

Defines the expected readership and describes version history including rationale for new versions and summary of changes

Describes fundamental assumptions on which the system is based and anticipated changes due to hardware, user needs, etc.

Defines the technical terms used in the document without assuming expertise from the reader

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Include System Evolution Information

2 pts

volume_mute

The System Evolution section of a requirements document is particularly useful for which of the following reasons? Select all that apply.

It helps system designers avoid restrictive design decisions that would make future changes difficult

It provides a warranty against all future changes to the system

It eliminates the need for requirements management processes

It allows designers to include support for future system features

It helps system maintenance engineers who have to adapt the system to new requirements

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Document as a Compromise

1 pts

volume_mute

True or False: Because the requirements document has such a diverse set of users, it must be a compromise that communicates requirements to customers, defines requirements in precise detail for developers and testers, and includes information about possible system evolution.

False

True

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements Documents for Large Hardware-Software Systems

1 pts

volume_mute

When the software is part of a large system project that includes interacting hardware and software systems, it is usually necessary to:

Use only graphical models and no natural language descriptions

Define the requirements to a fine level of detail and include most of the chapters shown in the IEEE standard structure

Skip the requirements document and go directly to system design

Produce only a brief user requirements document and let developers decide the details

note_alt Add notes

flag Flag

Correct Answer

Explanation

Undergraduate Professional

What Is the SRS?

Correct Answer

Explanation

Agile Argument Against Formal Requirements Documents

Correct Answer

Explanation

Value of a Short Supporting Document in Agile

Correct Answer

Explanation

Users of the Requirements Document

User

Primary Use

Correct Answer

Explanation

Level of Detail Required

Correct Answer

Explanation

IEEE-Based Requirements Document Structure

Correct Answer

Explanation

Purpose of Each Document Section

Section

Purpose

Correct Answer

Explanation

Why Include System Evolution Information

Correct Answer

Explanation

Requirements Document as a Compromise

Correct Answer

Explanation

Requirements Documents for Large Hardware-Software Systems

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: