4. Requirements Definition

Question 1

Why do we document requirements

Answer 1

To ensure there is an understanding between all parties involved in a project of the business needs, projects can be scheduled accordingly, and solutions are aligned with business strategy and objectives

Question 2

What is a requirement

Answer 2

A requirement in the context of Business Analysis is a statement provided by a stakeholder about what they believe they need in order to solve a particular business problem, carry out an activity related to their role or respond to a specific business need.

Question 3

Why do we prioritise requirements

Answer 3

By prioiritising our requirements we can identify those that are vital to our processes from those that the stakeholders could do without, or with a workaround. This allows us to deliver requirements in increments or reduce our requirements list if required.

Question 4

Name a method for Prioritising requirements

Answer 4

MOSCOW

Question 5

How do we gather requirements

Answer 5

Through requirement elicitation with stakeholders, there are many techniques to do this, such as workshops, interviews, shadowing, document analysis

Question 6

What are the characteristics of a good requirement

Answer 6

Specific
Measurable
Achievable
Relevant
Time-bound

Question 7

Name some common problems with requirements

Answer 7

Lack of relevance to project objectives
Ambiguity
Duplication
Not specific
Difficult to test
Assume solutions

Question 8

What are the 5 steps to the business analysis framework

Answer 8

Investigate situation
Consider perspectives
Analyse needs
Evaluate options
Define Requirements (can be being gathered throughout)

Question 9

Name a technique used to elicit requirements

Answer 9

Interviews
Workshops
Observation
Shadowing
Questionnaires
Document analysis
Focus groups
Sampling
Special purpose records
Scenarios
Prototyping

Question 10

Why is it important to plan and estimate requirement engineering

Answer 10

Requirement gathering and analysis is often undervalued in a project plan.
This requirement documentation stage of a project is vital to its success and therefore sufficient time needs to be allocated to the process.

Question 11

What is the SDLC

Answer 11

Software development life cycle

Question 12

Give 5 steps of a SDLC

Answer 12

Design
Development
Acceptance testing
Implementation
Maintenance

Question 13

What are the 5 elements of Requirements engineering

Answer 13

Req Elicitation
Req analysis
Req validation
Req documentation
Req management

Question 14

What different types of knowledge are there

Answer 14

Tacit

Explicit

Question 15

Explain Tacit knowledge

Answer 15

Tacit knowledge is knowledge that is difficult for a stakeholder to explain or articulate, such as skills, actions, culture norms, things they take for granted

Question 16

Explain Explicit knowledge

Answer 16

Explicit knowledge is knowledge that can be evidenced such a processes, procedures, reports, targets

Question 17

Give a technique for eliciting Tacit knowledge

Answer 17

Observation or shadowing

Question 18

Give a technique for eliciting Explict knowledge

Answer 18

Document analysis, interviews, workshops, MOST elicitation techniques

Question 19

What is the difference between Req’ elicitation and Req’ analysis

Answer 19

Requirement elicitation is the gathering of information in order to document requirements, requirement analysis is the analysis that is needed to be done against the requirements to ensure that they are organised, non-conflicting, well-formed and of quality to the business and the projet

Question 20

Name 3 tasks involved in Req’ analysis

Answer 20

Checking congruence with business objectives and the business case
Checking feasibility
Structuring the requirements
Prioritising requirements
Packaging requirements for delivery
Use of scenarios and prototyping in requirements analysis
Dealing with overlapping, duplicate and conflicting requirements

Question 21

How would you deal with overlapping, duplicate and conflicting requirements

Answer 21

Identify each stakeholders perspective to highlight the reasons for the conflict
gather involved stakeholders and decision makers together to discuss the conflict

Question 22

What is requirement prioritisation

Answer 22

Prioritisation – the structure and application of a technique to allocate a priority to each requirement. This can then be used to allow for interations of packages of requirements to be delivered and to identify requirements that are not vital to the business objectives and solution

Question 23

What characteristics should a requirement be, name 3

Answer 23

Testable
Unambiguous
Relevant
Clear
Complete
Consistent
Traceable

Question 24

How do we validate requirements

Answer 24

…

Question 25

Which stakeholders may be involved in the requirement engineering process

Answer 25

Project stakeholders

• Project Manager
• Business Analysts
• Solution developers
• Testers
• System Architects

Business stakeholder

• Project Sponsor
• SMEs (Business and Industry)
• End users and managers (For who the solution is designed)

Question 26

What is Requirement elicitation

Answer 26

Gathering info from stakeholders and creating req list

Question 27

What is requirement validation

Answer 27

Getting requirements signed off as correct and covering business need by key stakeholders

Question 28

What is requirement management

Answer 28

Requirements Management is an iterative set of activities that help ensure that elicitation, documentation, refinement, and changes of requirements is adequately dealt with during a project lifecycle

Question 29

What is requirement documentation

Answer 29

Requirement documentation is the chosen template within which requirements are documented, with information supporting the user story, in order to be published to the project team for use

Question 30

What is requirement analysis

Answer 30

The work done to confirm a requirement is of quality, non-conflicting, well-structured and well-formed for use of all those in the project.