BCS RE Flashcards

1
Q

Activity Sampling

A

An investigation technique carried out to determine the amount of time individuals spend on different aspects of their work. Activity sampling is a form of observation and involves the collection of data that may be used for statistical analysis.

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

Special purpose records

A

A technique that involves the business users in keeping a record about a specific issue or task. e.g the number of customer approaches per day, and classify them – perhaps using a five-bar gate notation – according to whether they are complaints, queries or returned goods.

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

Protocol analysis

A

A technique used to elicit, analyse and validate requirements. Protocol analysis involves requesting the users to perform a task and describe each step as they perform it.

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

Scenarios

A

A technique used to elicit, analyse and validate requirements. A scenario traces the course of a transaction from an initial business trigger through each of the steps needed to achieve a successful outcome. Alternative scenarios, for example, where specific conditions are not met, are also traced.

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

Prototyping

A

A technique used to elicit, analyse and validate requirements. Prototyping involves building simulations of documents, processes or systems in order to enable the business users to visualise any proposed changes and hence increase understanding about the system requirements.

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

Shadowing

A

A technique used to find out what a particular job entails. Shadowing involves following a user as they carry out their job for a period such as a day or two days.

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

Workshop

A

An investigation technique whereby a meeting is held with business actors from a range of business areas in order to elicit, analyse or validate information. An agenda is prepared prior to the workshop and distributed to participants. The workshop is run by a facilitator; actions and decisions are recorded by a scribe.
Gain a broad view of the area under investigation
Increase speed and productivity
Obtain buy-in and acceptance for the project:
Gain a consensus view or group agreement:

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

Business sponsor

A

A senior person in an organisation who is accountable for delivering the benefits of a business change. The sponsor is also responsible for providing resources to the project team.

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

Business event

A

A business event triggers the business system to do something. Typically this is to initiate the business process that forms the business system response to the event. In effect, the business events tell us when a business activity should be initiated; it fires into life the process that carries out the activity. There are three types of business event: external, internal and time-based business events.

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

SMART

A

A mnemonic used to ensure that objectives are clearly defined in that they are specific, measurable, achievable, relevant, time-framed.

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

Shadowing

A

Shadowing involves following a user for a period, such as one or two days, to find out what a particular job entails. This is a powerful way to understand a specific user role.

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

ACTORS

A

An actor is an individual or group who is fulfilling a particular role. There are some roles we would expect to be represented during the requirements work and they represent two broad stakeholder groups:
the business representatives; y the project team.

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

Project sponsor

A

The project sponsor represents the business in ensuring that business objectives are met. The sponsor has the following responsibilities:
-to agree the project initiation document that approves the requirements engineering study
-to deliver the specific and agreed business benefits predicted in the business case;
-to make funds and other resources available for the project;
-to accept the deliverables at the end of the project;
-to approve and sign off the requirements document as a true statement of the business needs;
-to rule on any conflicting requirements where the business analyst cannot negotiate agreement;
-to confirm that the benefits in the business case have been realised as promised.

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

Project manager

A

The project manager is mindful of the need to meet the business requirements and satisfy the business imperatives that drive the project. The project manager will report to the project sponsor and will be concerned to:
y break the project down into identifiable and measurable pieces of work, each with its deliverable;
-allocate the pieces of work to competent people to perform;
-schedule the tasks with their start and end times, recognising dependencies
between tasks;
-monitor the progress of the various tasks and be alerted of any likely slippage;
-take any corrective action should there be slippage, or risk of non-completion of a task for any reason;
-ensure that the project is completed on time and within the agreed budget.

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

SME

A

The SME brings a breadth of understanding to RE, and should have experience and knowledge of industry best practice. Their level of knowledge of the business domain should help analysts distinguish between what the business and the project need and what a particularly forceful individual user wants. The SME may be an internal expert or may be an external consultant, brought in for the duration of the project. While an external SME can bring in fresh views and insights from industry, drawing on best practice as used elsewhere, there are some risks associated with their use:

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

Business Users

A

The business users are the individuals or groups who will need to apply the new business processes and use the new IT system. They comprise the group for whom the solution is designed. They are required to describe current procedures and documentation, highlight any difficulties they experience with current processes and identify new requirements for the system. They should be able to help the business analyst to define the requirements in detail, by providing specific, clear information. They will be able to assist with the definition of non-functional requirements that apply to their tasks, although some specific aspects may need management involvement. For example, decisions about archiving information and the length of retention of data are likely to require the involvement of middle or senior managers.

17
Q

The project team

A

comprises the project manager, the business analyst and the developers or technical architects.
There will also be communication with representatives from the project support office and with the software testers.
The project manager is mindful of the need to meet the business requirements and satisfy the business imperatives that drive the project.

The project manager will report to the project sponsor and will be concerned to:
-break the project down into identifiable and measurable pieces of work, each with its deliverable;
-allocate the pieces of work to competent people to perform;
-schedule the tasks with their start and end times, recognising dependencies
between tasks;
-monitor the progress of the various tasks and be alerted of any likely slippage;
-take any corrective action should there be slippage, or risk of non-completion of a task for any reason;
-ensure that the project is completed on time and within the agreed budget.

18
Q

The Business Analysts

A

The business analysts will be responsible for carrying out the requirements engineering work. Their key objective is to ensure that the requirements are well-formed, well- documented, complete and aligned with the business objectives. Working closely with the business staff, they gather and analyse the requirements, and are responsible to the sponsor for the quality of the requirements document.
Many organisations assign the project manager role to the business analyst on a project, but this can be problematic as the two roles call for different aptitudes, priorities and skills. There may be conflicting priorities and interests to be reconciled, which will be problematic if one individual is assigned both of these roles. The project manager is most concerned with meeting cost and time targets, while the business analyst’s primary consideration is satisfying the quality criteria.

19
Q

Business Requierments - General

A

These are the requirements that define business policies, standards and needs.
Business constraints
Business policies
Legal
Branding
Cultural
Language

20
Q

Business Requierments - Technical

A

These are the requirements that state the technical policies and constraints to be adopted across the organisation and apply to a range of change projects. These requirements may refer to the artefacts that describe the technical infrastructure for the organisation. The specific sub-categories of technical requirements are:
Hardware
Software
Interoperability
Internet

21
Q

Solution Requierments - Functional

A

The functional requirements set out the features that any solution should provide
Data entry
Data maintenance
Procedural
Retrieval

22
Q

Solution Requierments Non - Functional

A

The non-functional requirements are concerned with how well the solution will operate and answers questions such as: ‘how quickly will it respond?’ and ‘how easy will it be to use?’
Performance
Security
Access
Backup and recovery
Archiving and retention
Maintainability
Business continuity
Availability
Usability
Accessibility
Capacity

23
Q

‘Backwards from’ traceability

A

involves the ability to trace the source of a requirement from any later point in the business change or software development lifecycle. It answers the question ‘what was the source requirement for this feature of the solution and who raised it?’ We need to be able to identify where a requirement originated so that we can seek clarification from the source where necessary. This is particularly important when requirements are in conflict or there are conflicting views as to the priority of a requirement.

24
Q

Forwards to’ traceability

A

involves the ability to identify any requirement and track where it has been further developed and ultimately implemented. It answers the question ‘what happened to this requirement?’ and should show that each requirement has been resolved satisfactorily.

25
Q

Vertical traceability

A

concerns tracing a requirement up or down the hierarchy so answers the questions about alignment with business values, strategy and objectives

26
Q

Requirements filters

A

Check for / to
-Overlapping or duplicate requirements
-Unravelling multiple requirements
-Confirming relevance of the requirement
Removing conflicts
Checking for solutions
Confirm standard of quality

27
Q

Good / Robust / Well Filtered requirements are:
ƒ

A

Clear
ƒ Concise
ƒ Consistent
ƒ Relevant
ƒ Unambiguous
ƒ Correct
ƒ Testable
ƒ Traceable

28
Q

REQUIREMENTS VALIDATION

A

-The business sponsor should review the document to ensure that the requirements are all in alignment with the business objectives and do not address areas that are outside the scope of the project.
-The business owners of the individual requirements, or their representatives, should review the requirements to ensure that they express the business needs clearly and correctly, without ambiguity. It is the business representatives’ responsibility – and their last opportunity – to be satisfied with the requirements before accepting them.
-The subject matter expert should review the requirements to ensure that they reflect correct business practice.
-The developers should review the requirements to ensure that they are technically feasible.
-The testers should review the requirements to ensure that they are testable.
-Project office representatives should ensure that the requirements are compliant with business standards and policies, and that correct quality review procedures have been followed.