Sections 10-11 Flashcards

1
Q

Types of stakeholders in requirements engineering

A

Project (testers, business analysists, project manager, devs etc)
Business (project sponsor, product owner, end users, sme’s)
* Note placement of project manager vs owner

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

Types of requirements

A
  1. General (business constraints, business policies, business continuity, legal)
  2. Technical (hardware, software, interface (interoperability), internet)
  3. Functional (data entry, data maintenance, procedural, data retrieval)
  4. Non-Functional (performance, security, access, backup, recovery, archiving, retention, robustness, availability, usability, accessibility, capacity, scalability)

1 and 2 are business requirements, 3 and 4 are solution requirements

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

What model guides the requirements of the project

A

OSCAR (Objectives, Scope, Constraints, Authority, Resources) helps create the Terms of Reference or Project Initiation Doc or a clear statement of project intent

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

Four types of knowledge

A
  1. Tacit individual
  2. Tacit corporate
  3. Explicit individual
  4. Tacit corporate
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Techniques to get explicit knowledge

A

Workshops, interviews, doc analysis

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

Techniques to get tacit knowledge

A

Protocol analysis, Business activity Model, value stream diagram

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

What language should be kept out of requirements

A

Moscow (must should). Shall is ok to have

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

Two categories of business rules when analysing requirements

A
  1. Constraints
  2. Operational Guidance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Five part framework for requirements establishing

A
  1. Elicitation
  2. Analysis
  3. Validation
  4. Documentation
  5. Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

How to structure class diagrams

A

Class name on top (Upper case for fist letter)
Attributes in middle (first lower, second capital)
Operations (same spelling as attributes)

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

What type of requirements are user stories useful for?

A

Functional requirements

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

Types of models for showing functional and data requirements

A
  1. Use case diagram
  2. Class models
How well did you know this?
1
Not at all
2
3
4
5
Perfectly