Requirements Engineering

Question 1

Requirements Engineering Process

Answer 1

• analyzing the problem
• documenting the resulting observations in a variety of representation formats
• checking the accuracy of the understanding gained

Question 2

Requirements Engineering

Answer 2

• common agreement among all parties
• describes “what the product will do, but not how to do it”

Question 3

What is a requirement?

Answer 3

1. condition/capability needed by the user to solve a problem or achieve an objective
2. condition/capability that must be met by system or system component to satisfy customer needs
3. documented representation of condition/capability

Question 4

Types of Requirements

Answer 4

1. User requirements
2. System requirements

Question 5

User Requirement

Answer 5

Written for customers. Statements in natural language of system services and constraints. Overall system goal

Question 6

System Requirements

Answer 6

Written for contract. Structured document with detailed descriptions of the system functions, services, and constraints. Specific system features

Question 7

Functional Requirement

Answer 7

• describe functionality or overall system services
• high-level statements of what system should do

Question 8

Domain Requirements

Answer 8

Depends on where product is used. Constraints on system from domain of operation. (must be ferpa compliant)

Question 9

Non-Functional Requirement

Answer 9

Gives rise to functional requirements.
- constraints on services or functions offered by the system.
- often apply to whole system instead on individual feature
- more critical then functional requirements, wo them system may be useless

Question 10

Goal

Answer 10

• general intention of the user (such as ease of use)
• help to define non-functional requirements

Question 11

Requirements Engineering Activities

Answer 11

• elicitation
• analysis
• specification
• verification
• management

Question 12

Requirements Elicitation

Answer 12

Process through which customers and developers discover, review, articulate, and understand the user needs and system constraints

Question 13

Requirements Analysis

Answer 13

Process of analyzing user needs to arrive at definition of software requirements

Question 14

Requirements Specification

Answer 14

Development of a document the clearly and precisely records each requirement

Question 15

Requirements Verification

Answer 15

Process of ensuring the software requirements specification is in compliance with the system requirements

Question 16

Requirements Management

Answer 16

Planning and controlling of the requirements elicitation specification, analysis, and verification activities

Question 17

Requirements Evaluation

Answer 17

• validity
• consistency
• completeness
• realism/feasibility
• verifiability
• unambiguous
• traceable

Question 18

Requirements Evaluation - Unambiguity

Answer 18

Whether it has only one possible interpretation

Question 19

Requirements Evaluation - Completeness

Answer 19

Whether all required functions and design constraints are present and fully developed

Question 20

Requirements Evaluation - Consistency

Answer 20

Whether no other requirements are conflicting with it

Question 21

Requirements Evaluation - Testable

Answer 21

Whether requirement can be tested

Question 22

Requirements Evaluation - Traceable

Answer 22

Whether origin of requirement is clear

Question 23

Requirements Engineering Participants

Answer 23

• customer
• user
• requirements engineer/analyst
• developer
• v&v agent

Question 24

Artifacts

Answer 24

Includes:
* Requirements Specification: what does the system do?, who identified the requirement, contextual information
* Validation/verification audit reports
* Output of requirements management tool

Question 25

Requirements Change Management

Answer 25

Deciding if a requirement change should be accepted:
* Problem analysis and change specification
* Change analysis and costing
* Change implementation

Question 26

Natural Language Specification

Answer 26

• Requirements are written as natural language sentences
• Supplemented by diagrams and tables
• Can be understood by users/customers

Question 27

Guidelines for Writing Requirements

Answer 27

• Invent standard format and use for all reqs
• Use language in a consistent way across reqs
• Use text highlighting to identify keys parts of reqs
• Avoid use of computer jargon
• Include explanation of req

Question 28

Problems with Natural Language

Answer 28

• Lack of clarity
• Improper classification
• Requirements amalgamation (several reqs improperly combined together)