Brainscape's Knowledge GenomeTM

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


See full index

Business Analysis > Chapter 10 - Establishing the Requirements > Flashcards

Chapter 10 - Establishing the Requirements Flashcards

1
Q

At what stage are the largest proportion of errors introduced into an IT project?

A

Requirements analysis

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

What are typical problems with requirements?

A

Lack of clarity

Conflicts

Uncertainty amongst business users about what they need

Business users failing to identify all requirements

Business users and analysts taking knowledge for granted

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

What is a duckrabbit?

A

Different views of the same business depending on perspectives

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

What are the stages of Requirements Engineering?

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
5
Q

What is Requirements Elicitation?

A

Drawing out information and requirements from the business stakeholders.

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

What is Requirements Analysis?

A

Scrutinise initial requirements list to ensure they are well formed and align with business objectives.

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

What is Requirements Validation?

A

External stakeholders review requirements to sign off

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

What is Requirements documentation ?

A

Development of well-organised requirements document.

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

What is Requirements management?

A

Activities needed to manage any changes to the requirements.

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

What is explicit knowledge?

A

Can easily be articulated and is at the front of user’s mind

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

What is tacit knowledge?

A

Aspects of work a user is unable to explain or articulate.

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

Give examples of common individual tacit knowledge

A

Skills

Taken-for-granted information

Front-story/back-story - giving more positive view than is actually the case.

Conceptualising Requirements for new business system

Cultural and language differences

Intuitive understanding

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

Give examples of common organisational tacit knowledge

A

Norms of behaviour/comms

Organisational culture

Organisation stories

Formal and informal networks

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

Give examples of individual explicit knowledge

A

Task definitions

Job descriptions

Targets

Volumes

Frequencies

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

Give examples of explicit organisational knowledge

A

Procedures

Style guides

Knowledge sharing repositories

Manuals

Company reports

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

Give examples of Requirements Elicitation methods for uncovering tacit knowledge

A

Apprentice

Observe

Recount

Enact

17
Q

What techniques are covered by Apprentice?

A

Shadowing

Protocol analysis

18
Q

What techniques are covered by Observe?

A

Observation

Shadowing

19
Q

What techniques are covered by Recount?

A

Story-telling

Scenario

20
Q

What techniques are covered by Enact?

A

Prototype

Scenario role-play

21
Q

What is the purpose of the Requirements list?

A

Ensure everything is documented and source identified

22
Q

What models can be used in Requirements analysis to ensure requirements are in scope?

A

Use case diagram

Business process model

Data model

23
Q

What tasks are included in Requirements Analysis?

A

Categorisation of Requirements

Models of requirements elicited

Filters to ensure requirements are well defined

24
Q

What four categories should Requirements be put in?

A

General (business)

Technical

Functional

Non-functional

25
Q

What filters should be used to examine requirements?

A

Overlap/duplicates

Unraveling multiple requirements

Confirming relevance

Feasibility evaluation (technical, business, financial)

Removing conflicts

Checking for solutions (pre-determined)

Quality

26
Q

What quality criteria should be applied to requirements?

A

Clear

Concise

Consistent

Relevant

Unambiguous

Correct

Testable

Traceable

27
Q

What are the potential outcomes of requirements analysis?

A

Accept requirement

Re-word to remove jargon/ambiguity

Merge duplicated/overlapping

Split into individual entries

Take unclear, ambiguous or conflicting requirements back to users for clarification

28
Q

What representatives should be included in review group for Requirements Validation?

A

Business sponsor

Business owners of requirements

Subject matter expert

Developers

Testers

PMO for compliance

29
Q

What are the there possible outcomes to a Requirements review?

A

Document confirmed as satisfactory

Document requires some amendment

Document requires significant re-work

30
Q

What is the difference with Requirements Elicitation when using agile development?

A

Agile evolves requirements during development so not as much detail is specified in advance.

31
Q

What questions should be answered in User Stories?

A

Who?
What?
Why?

Business Analysis (14 decks)

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