Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

BCS Business Analysis 2024 > Chapter 10: Establishing the Requirements (10%) > Flashcards

Chapter 10: Establishing the Requirements (10%) Flashcards

1
Q

typical problems with requirements

A
  • Lack of relevance to the project objectives
  • Lack of clarity in the wording
  • Ambiguity
  • Duplication and conflict between requirements
  • Poorly expressed requirements
  • Requirements that assume a solution (rather than stating what is needed from the solution)
  • Uncertainty from the users about what they expect
  • Users omit requirements
  • Varying and inconsistent requirements
  • users and analysts taking knowledge for granted
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

how can we address the problem of :
Lack of relevance to the project objectives

A

OSCAR
Objectives
Scope
Constraints
Authority
Resources

  • don’t assume knowledge
  • recognise different stakeholder viewpoints
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

core activities in the Requirements Engineering framework

A

Requirements elicitation

Requirements analysis

Requirements validation

Requirements documentation

Requirements management

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

Requirements Elicitation is concerned with

A

gathering requirements from stakeholders

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

Requirements Analysis is concerned with

A

review/analyse requirements to:

  • remove duplication/error
  • negotiate conflicts and contradictions
  • evaluate feasibility
  • allocate priorities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requirements Validation is concerned with

A

stakeholders review requirements (to assure they’re defined at required level of quality)

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

Requirements Documentation is concerned with

A

producing narrative + diagrammatic definitions of requirements (at varying levels of accuracy + completion)

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

Requirements Management is concerned with

A

managing changes to defined requirements + ensuring desired level of traceability is achieved

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

2 main groups of actors in RE:

A

business representatives

project team

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

roles in business representatives group

A

project sponsor

product owner

SME

business staff (people who apply the new business processes + use new IT system)

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

what responsibilities does project sponsor have

A
  • agree PID (project initiation document)
  • make funds + resources available
  • resolve conflicting requirements
  • sign off requirements document
  • accept deliverables at project end
  • deliver the benefits
  • confirm benefits have been realised
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

product owners responsibilities:

A
  • manage product backlog (ensure priorities have been identified + align with business needs)
  • identify backlog items to be developed in each product development iteration
  • make decisions on behalf of organisation regarding product development + resolve requirement conflicts
  • ensure product development stays on track
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

SME responsibility is to give business advice regarding requirements, particularly when the organisation wishes to…

A
  • adopt latest industry best practise/innovations
  • introduce a new product/process that isn’t fully understood
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Business staff responsibilities

A

articulate both

  • functional requirements
  • non-functional requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

actors in project team

A

project manager

business analyst

developers

software testers

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

project manager responsibilities

A
  • planning project
  • allocating work
  • monitoring progress
  • taking corrective action
17
Q

BA responsibilities

A
  • carrying out RE work (ensure requirements are defined, in line with project approach/standards, provide basis to solution)
  • work closely with business staff (elicitation, analysis, documentation of requirements)
18
Q

developer responsibilities

(creates the software product in line with business requirements)

A
  • check technical feasibility of requirements
  • help analyst understand implication of requirements
  • produce prototypes
  • help business users visualise what they’ve requested
19
Q

tester responsibilities

A
  • tyring to prove the system does not work + identify where this is the case
  • review requirements to ensure they’re feasible
  • ensure acceptance criteria properly defined
20
Q

categories within General requirements (business)

A
  • business constraints (budget, timescale, resources)
  • business policies
  • business continuity (ability to recover from incidents that hinder continued operation)
  • legal
  • branding
  • cultural
  • language
21
Q

categories within Technical requirements (business)

A

hardware

software

interface

internet (technical policies governing the use of internet/ web-enabled services)

22
Q

categories within Functional requirements (solution)

A

data entry (+ processing, reporting)

data maintenance

procedural

retrieval requirements

23
Q

categories within Non-functional requirements (solution)

A

performance (speed)

security + access

backup + recovery

archiving + retention

robustness

availability

usability

accessibility

capacity + scalability (volumes of data to be stored/ transactions to be processed/ no. stakeholders to be supported)
(increase scale of coverage of solution to accommodate more transactions/ stakeholders)

(think ‘ilities’)

24
Q

most effective requirement elicitation techniques in a workshop

A
  • visulations
  • modelling

CSF analysis

scenario analysis

prototyping

25
Q

other requirement elicitation techniques

A

interviews

document analysis

26
Q

approaches for uncovering tacit knowledge and key techniques used:

A

Observe: observation, shadowing

Recount: storytelling, scenario analysis

Enact: prototyping, scenario role-play

26
Q

4 tasks included in requirements analysis:

A
  1. categorising requirements
  2. modelling requirements (using Class models or Use case diagrams)
  3. prioritising requirements (can use RAG or MoSCoW)
  4. Defining requirements (can apply filters)
27
Q

are these individual level of knowledge tacit or explicit?

task definitions, job descriptions, targets, volumes, frequencies

A

explicit

28
Q

are these individual level of knowledge tacit or explicit?

skills, values, taken-for-granted knowledge, intuitiveness

A

tacit

29
Q

are these corporate level of knowledge tacit or explicit?

norms, culture, networks, organisation history, back story

A

tacit

30
Q

are these corporate level of knowledge tacit or explicit?

procedures, style guides, processes, knowledge sharing repositories, manuals, company reports

A

explicit

31
Q

define MoSCoW

A

Must have (mandatory, solution not acceptable w/o)

Should have (mandatory, but may be deferred to 2nd increment)

Could have (desirable but solution acceptable w/o)

Want to have (but won’t have this time)

32
Q

requirement filters are used to examine elicited requirements and produce well-formed set.

what are the key analysis filters?

A
  • unravel multiple requirements
  • check for overlapping/duplicates
  • confirm relevance
  • evaluate feasibility (technical, business + financial)
  • remove conflicts
  • check for solutions
  • confirm quality (clear, concise, consistent, relevant, unambiguous, correct, testable, traceable)
32
Q

what does INVEST stand for

A

each user story/backlog item should be:

Independent

Negotiable

Valuable (to users/ customers)

Estimatable

Small (suitable size for iteration planning)

Testable (have specific measure to evaluate if it’s been achieved)

33
Q

what is INVEST used for

A

provides quality check to evaluate + improve user stories

34
Q
A
34
Q

2 categories of business rules to consider + their sub-categories

what techniques are helpful to elicit and document the rules?

A

Constraints
- Action governance (use narrative statements)
- Data constraints (use data models + definitions, CRUD matrices)

Operational guidance
- decision conditions (activity diagrams, BPM, decision tables, tables, matrices)
- calculations (arithmetical formulae, structured English, pseudocode)

35
Q
A
36
Q
A

BCS Business Analysis 2024 (15 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions