Requirements engineering

Question 1

3 large parts of requirements engineering.

Answer 1

1. Inception.
2. Elicitation.
3. Elaboration.
4. Negotiation.
5. Specification.
6. Validation.

Question 2

2 methods of requirement elicitation.

Answer 2

1. Interviewing customers.

2. Prototyping.

Question 3

Ways of interviewing customers.

Answer 3

1. Unstructured (informal, chat).
2. Structural (formal, questions are prepared, has agenda).
3. Focus groups (early stages).
4. Questionnaires (Many involved, not deep).

Question 4

When prototyping should be used?

Answer 4

When requirements are unclear or conflicting.

May demonstrate new functionality or technology.

Question 5

Requirements Dependency Matrix

Answer 5

A table with rows and columns marked (indexed) by requirements and the cells containing descriptions of dependencies between the requirements if there are any.

Question 6

What is Requirements Traceability?

Answer 6

It’s establishing of clear links between requirements and design and code elements. It helps maintenance when requirements change to find what should be changed and estimate time and cost if change.

Question 7

Traceability tables

Answer 7

1. Features TT
2. Source TT
3. Dependency TT
4. Subsystem TT
5. Interface TT

Question 8

Elicitation work products

Answer 8

1. Statement of need and feasibility
2. Statement of scope
3. List of stakeholders
4. Description of systems’ environment
5. Usage scenarios
6. Any developed prototypes.

Question 9

Analysis model practice

Answer 9

1. High level of abstraction
2. Put in only necessary elements (to understand the system)
3. No infrastructure or non-functional models
4. Minimize coupling.
5. Must provide value to the customer
6. KISS

Question 10

Use case parts

Answer 10

1. Name
2. Primary actor
3. Goal in context
4. Preconditions
5. Post-conditions
6. Invariants
7. Trigger
8. Main success scenario
9. Exceptions
10. Open issues