Requirements Engineering Flashcards

1
Q

What is Requirements Engineering

A

The process of establishing the services required of a system and the constraints of its development

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

What is a Requirement

A

A statement that defines a need and the conditions with it

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

Are Requirements detailed

A

They don’t have to be

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

What are the 2 types of Requirements Documents

A
  1. User Requirements - Described in plain English and/or abstract visual diagrams; useful as bids for contracts
  2. System Requirements - Structured document covering all functions and constraints; can be the contract
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Who are the 5 types of readers for User Requirements

A
  1. Client Managers
  2. System End-Users
  3. Client Engineers
  4. Contractor Managers
  5. System Architects
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Who are the 4 types of readers for System Requirements

A
  1. System End-Users
  2. Client Engineers
  3. System Architects
  4. Software Developers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the types of System Stakeholders and who are they

A

Anybody affected by and/or has an interest in the system:
1. End Users
2. System Managers
3. System Owners
4. External Stakeholders

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

What are the 2 types of Requirements

A
  1. Functional Requirements - WHAT actions users can take and what the system should do; description of the service, expected behavior
  2. Non-Functional Requirements - HOW to implement; constraints, processes, environments, tools, limits
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What 2 words should you avoid in Requirements

A

Will and Must

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

What are the 4 characteristics of good Requirements

A
  1. Complete
  2. Consisten
  3. Affordable
  4. Bounded
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How do you produce a complete and consistent Requirements Document

A

You cannot - It is impossible due to complexity

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

What are the 3 Non-Functional Classifications

A
  1. Product Requirements
  2. Organizational Requirements
  3. External Requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are the 6 metrics for specifying non-functional requirements

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

What are the 4 Requirements Engineering activities

A
  1. Elicitation / Discovery / Analysis
  2. Specification
  3. Validation
  4. Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What are the 4 stages of Requirements Elicitation

A
  1. Discovery
  2. Classification and Organization
  3. Prioritization and Negotiation (fix conflicts)
  4. Specification (generate document)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q
A