Chapter 11: Documenting and Modelling Requirements (10%)

Question 1

what are the 2 documentation styles and what type of models do they involve?

Answer 1

Text -based:
- requirements catalogue (linear)
- user story (agile)

Diagrammatic:
- data model
- use case model
- business process model

Question 2

elements of a requirements catalogue

Answer 2

———initially needed——–
Requirements identifier

Requirement name

Requirement description

Source

Author
—- for detailed requirements analysis —-
Owner

Type of requirement

Priority (MoSCoW)

Business area

Stakeholders

Associated non-functional requirements

Acceptance criteria

Related requirements

Related documents (e.g. PID)

Comments

Rationale

Resolution (outcome of requirement - implemented, deferred, merged, dropped)

Version history

Question 3

key underlying principles for user story development

Answer 3

3 C’s framework:

Card (each story documented in card format - limits amount of info)

Conversation (each story is basis for a convo where it’s explored in more depth)

Confirmation (confirm defined acceptance criteria have been met)

Question 4

user story format

Answer 4

As a …(user)

I want… (capability/function needed by user)

So that (why is user story beneficial to user?)

Question 5

Acceptance criteria BDD format

Answer 5

Given…
When
Then

Question 6

use case diagrams are often created during…

Answer 6

a workshop or following interviews with business stakeholders

Question 7

elements of use case diagram

Answer 7

actors

use case (something that an actor wants the system to do)

system boundary

associations (lines drawn linking actors with appropriate use cases)

Question 8

format of Use case description

Answer 8

• actor name
• use case name + identifier
• goal
• actions (to conduct the work of the use case)
• alternative scenarios

Question 9

elements in a fully described use case description

Answer 9

• name of actor
• use case name + identifier
• goal
• triggering event
• preconditions
• post conditions
• actions (+ ‘happy day’ scenario)
• alternative flows
• priority
• frequency + volumes

Question 10

what are epics

Answer 10

complex user stories (or contain compound requirements)

may be broken down into individual user stories

reflects a more holistic view

may drive changes to all of the POPIT

Question 11

Define the structure of the business requirements document

Answer 11

1. intro + background
2. business process model
3. function model
4. data model
5. requirements catalogue/user story
6. glossary of terms

Question 12

describe elements of a class model

Answer 12

Class (1st letter capital)

Attributes (1st word lower, constituent parts with capital letter e.g. orderNumber)

Operations (a message sent to a class by other classes which invokes a response)

Question 12

Entity relationship diagrams contain a representation of…

Answer 12

the entity and its attributes

Question 13

what type of model used for:

illustrates how work is to be conducted + flow of the process

Answer 13

business process model

Question 14

what type of model used for:

defines scope of the system and features to be delivered (+ stakeholders engaged with it)

Answer 14

use case diagram

Question 15

what type of model used for:

represents data held within system, attributes, links between groups of data + business rules

Answer 15

data model (ERD or class)