Software Requirement Definition Flashcards

1
Q

the process of establishing the services that the customer requires from a system and the constraint under which it operates and is developed.

A

Requirement Engineering

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

it may range from a high-level abstract statement of a service of a system constraint to a detailed mathematical functional specification.

A

Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

4 TYPES OF REQUIREMENTS

A
  1. Functional Requirements
  2. Non-Functional Requirements
  3. Domain Requirements
  4. User Requirements
  5. System Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

statement of a service should provide how the system should react to particular inputs and how the system should behave in particular situations.

A

Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc.

A

Non-Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

3 Non-Functional Classifications

A

o Product Requirements

o Organizational Requirements

o External Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

requirements which specify the delivered product must behave in particular.

A

Product Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

requirements which are a consequence of organizational policies and procedures.

A

Organizational Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

requirements which arise from factors which are external to the system and its development process.

A

External Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

requirements that come from the application domain of the system and that reflect characteristics of that domain.

A

Domain Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

statements in natural language plus diagrams of the services the system provides.

A

User Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

a structured document setting out detailed description of the systems function, services, and operational constraint.

A

System Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

6 REQUIREMENTS MEASURE

A
  1. Speed
  2. Size
  3. Ease of Use
  4. Reliability
  5. Robustness
  6. Portability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

GUIDELINES FOR WRITING REQUIREMENTS (4)

A
  1. Invent standard format and use it for all requirements
  2. Use language in a consistent way
  3. Use text highlighting to identify key parts of the requirement
  4. Avoid use of computer jargon
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

defines a generic structure for a requirements document that must be instantiated for each specific system.

A

IEEE Requirements Standard

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

5 CONTENTS OF IEEE Requirements Standard

A

o Introduction
o General Description
o Specific Requirements
o Appendices
o Index.

17
Q

REQUIREMENTS DOCUMENT’S STRUCTURE

A
  1. Preface
  2. Introduction
  3. Glossary
  4. User Requirement Definition
  5. System Architecture
  6. System Requirement Specification
  7. System Models
  8. System Evolutions
  9. Appendices
  10. Index
18
Q

is a structures document setting out detailed description of the system services written as a contract between client and contractor.

A

Software Requirement Specification (SRS)

19
Q

7 IMPORTANT CHARACTERISTICS OF SOFTWARE REQUIREMENT SPECIFICATION (SRS)

A
  1. Correct
  2. Unambiguous
  3. Complete
  4. Consistent
  5. Verifiable
  6. Traceable
  7. Modifiable