Requirements Engineering Flashcards

1
Q

Where does RE start?

A

Starts with defining a problem to be tackled.

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

What is the key task of Problem Definition

A

Formulating a well defined problem so it can be reasonably solved

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

What is a stakeholder?

A

an Individual, Team, Organization with interests in, or concerns relating to the system to be

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

Do all stakeholders coalesce harmoniously?

A

No, you will have to make compromises and tradeoffs to satisfy all different stakeholders.

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

What are the components of RE?

A
  • Requirements Elicitation.
  • Requirements Analysis
  • Requirements Specification
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Define Requirements Elicitation

A

Help customer define what’s required, what is to be accomplished, how the system fits their needs, and how it will be used on a daily basis.

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

Define Requirements Analysis

A

Refining and modifying the gathered requirements

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

Define Requirements Specification

A

Documenting system requirements in a semi-formal or formal matter, to ensure clarity, consistency and completeness.

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

What are the different types of requirements

A
  • Functional

- Non-functional

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

Define functional requirements

A

FRs are those that provide fundamental reason for the product’s existence.

Specifies what the product must do.

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

Define non-functional requirements

A

Quality of the entire system.

  • Look and feel
  • Usability (ease of use/learning)
  • Performance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Define parts of the SRS

A

Open Issues
Off the shelf solutions (existing product, Ready made components, something to follow or copy)
New Problems (in the environment, existing users, limitations in the environment.)

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

Properties of Requirements

A
Abstract
Unambiguous
Traceable
Validatable
Complete
Consistent
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Tools for Requirements?

A

Most popular tool is the Use Case modelling

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

What are Use Cases?

A

step-by-step description of how a user will use a system to accomplish business goals.
Specifies what the system needs to accomplish.
Detailed use cases are written in usage scenarios or scripts.

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

What is an Actor

A

Person or other system that interacts with a system.

There are:
Initiating actors who initiate the use case.
Supporting Actors help the system complete the use case
Offstage actor, passively participates in the use case.

17
Q

Detailed Use cases

A

Text stories that detail what happens when an actor attempts to obtain a service from a system.

A scenario is called a use case instance

Don’t mistake a use case for the diagram.

18
Q

Use case format

A
Req.
initiating actor
actor goal
participating actors
Pre cond.
Post cond.

Scenarios

Alt. scenarios

19
Q

Who is interested in the SRS?

A
  • Customers and Users
  • Developers
  • Testers
  • Project Management