Brainscape's Knowledge GenomeTM

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


See full index

BCS Oral Exam > Requirements Engineering > Flashcards

Requirements Engineering Flashcards

1
Q

Requirement Elicitation

What techniques can you use for requirement elicitation?

A
  • Interviews
  • Workshops
  • Observations
  • Surveys
  • Prototyping
  • Document analysis
  • Scenario analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Requirements Framework

What does the requirements engineering framework include:

A
  • Elicitation
  • Analysis
  • Documentation
  • Validation
  • Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Requirement Elicitation

What are the two knowledge types?

A
  • Tacit
    knowledge, skills, and abilities gained through experience
  • Explicit
    knowledge that can be easily expressed, documented, and shared between people
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Requirement Elicitation

What insight can tacit knowledge bring?

A
  • Norms
  • Culture
  • Back story
  • Organisation history
  • Community of practice
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Requirement Elicitation

What are examples of explicit knowledge?

A
  • Procedures
  • Style guides
  • Processes
  • Organisation structure
  • Manuals
  • Organisation guidance
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Requirement Elicitatiaon

What is the difference between requirement elicitation and requirement analysis?

A

Elicitation is around collecting information and data, documenting and understanding business needs, process, assumptions and risks

Analysis refines the requirements to ensure that they are clear, complete & represent the business and user needs.

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

Requirements Analysis

What are key activities in requirements analysis?

A
  • aligning with business objectives/case
  • aligning with quality measures
  • feasible
  • prioritised
  • correctly structured
  • has handled duplicate requirements
  • collated for delivery
  • include prototypes
  • includes user analysis
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Requirements Analysis

Why do we need to check that requirements align with business objectives/case?

A

Requirements should address a root problem and be in scope

out of scope requirements might sit with other projects

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

Requirements Analysis

What quality attributes should a requirement include?

A

Requirements should be:
* Clear
* Complete
* Consistent
* Traceable
* Unambigous
* Relevant
* Testable

if it doesnt adhere to these then the wrong thing could be delivered

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

Requirements Analysis

What categories should we be looking at to ensure something is feasible?

A
  • techincally possible
  • possible within business
  • financially possible
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Requirement Analysis

How might a requirement be prioritised?

A

**MOSCOW
**
* Must Have
* Should Have
* Could Have
* Won’t Have

Backlog prioritisation
* Dependancies
* Size / Complexity
* Impact

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

Requirement Analysis

What are the qualities of a well structured requirement?

A
  • Follow a consistent pattern
  • Correctly labelled

Linear you might use req catalogue, Agile you might use user stories,

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

Requirement Analysis

How do you handle overlapping / duplicate requirements?

A
  • Remove duplicates
  • Merge requirements
  • Break down into smaller requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Requirements Analysis

How can Scenario analysis , prototypes & process maps help with requirement analysis?

A
  • visualise the problem
  • identify gaps in requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Requirements Analysis

What can you use to understand user perspective?

A
  • User/Customer Journeys
  • Personas
  • Use case diagrams

use case diagrams show who needs to interact with a system

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

Requirement Validation

How might requirements be validated in a linear delivery?

A
  • Quality Checks
  • Informal Reviews
  • Formal Reviews
  • Sign off by SME’s , Owners, Developers, Testers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Requirement Validation

How are requirements be signed off in an agile delivery?

A
  • Backlog grooming
  • Stories refined (3 amigos etc)
  • Accepted
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Requirement Management

Why is it important to have a well defined set of requirements?

A

A good set of requirements will support a successful delivery

19
Q

Requirement Management

What are the key elements of requirements management?

A
  • Identification
  • Source
  • Owner
  • Change Control
  • Version Control
  • Storage
  • Traceability
20
Q

Requirement Traceability

What is meant by Vertical Traceability?

A

Requirements that are traceable from the source to the business objectives

eg. we know the ownership

21
Q

Requirements Traceability

What is meant by Horizontal Traceability?

A

Traceability from origin to delivery and back.

22
Q

Requirement Change Control

What are the stages of change control?

A
  • Document
  • Analyse
  • Consult
  • Decide
  • Implement or Reject
23
Q

Requirements Change Control

What can be the source of a change?

A
  • Change in objectives
  • Change in stakeholders
  • Change of legislation
  • Competitor action
  • Change in technology
  • Change in priorities
  • Users develop better understanding of need
24
Q

Requirements Version Control

What is a baselined version of requirments?

A

A frozen version of requirements that has been signed off by stakeholders

25
Q

Requirements Version Control

What must be recorded as part of version control?

A
  • Version number
  • Who has signed it off
  • every iteration or change but be signed off and assigned a version number
26
Q

Requirements Version Control

Why should old versions of requirements never be thrown away?

A
  • To enable the ability to roll back if needed
  • To provide context to changes made
27
Q

Requirement Documentation

What is the benefit of linking requirements together?

A
  • It helps to ascertain dependent requirements & cross over
  • Changes to one requirements might have a knock on effect to another
28
Q

Requirements Management

What are the two types of Business requirement?

A
  • General
  • Technical

These are at the enterprise/business level

29
Q

Requirement Management

What are the two types of Solution requirement?

A
  • Functional
  • Non-Functional

These are at the product level

30
Q

Requirement Management

What type of requirement would be classed as a general requirement?

as a type of business requirement

A
  • Business constraints budget, timescales, resources
  • Business policies
    Standards, business rules
  • Legal
    Legislative and regulatory constraints
  • Branding
    Image, style guide
  • Cultural
    Vision, approach, management style
  • Language
    If operating across international boundarys
31
Q

Requirements Management

What type of requirement would be classed as a Technical requirement?

as a type of business requirement

A
  • Hardware
    IT and other hardware
  • Software
    Operatinve systems, package applications, networking , communications
  • Interoperability
    Standards for communicating between systems and devices
  • Internet
    Policies on internet user and web services
32
Q

Requirements Management

What does a functional requirement represent?

as a type of solution requirement

A

What we want the solution to do.

  • Data Entry
    Changes to data including deletion
    Procedural
    Implementation of business rule
  • Retrieval Requirements
  • Reporting, responding to enquiries
  • CRUD

The system shall -
As a User

33
Q

Requirements Management

What does a non-functional requirement represent?

as a type of solution requirement

A

How we want the solution to behave
* Performance
* Security
* Access
* Backup and Recover
* Archiving & Retentional
* Robustness
* Business Continuity
* Availability
* Usability
* Capacity
* Accessibility

34
Q

Requirements Management

What legislation do you have to consider when compiling requirements?

A
  • Data Protection
  • Disability Access

GDPR, W3C AA

35
Q

Requirements Documentation

What should be recorded in a requirements document?

A
  • ID/Reference Number
  • Name
  • Description
  • Owner
  • Acceptance Criteria
  • Priority
  • Linked Business Rules
  • Traceability
  • Status
  • Date
  • Signed off by
36
Q

Requirements Documentation

What is the purpose of a User Story?

A

A user story provides information on The action/outcome that a user needs to acomplish and why.

It ensure thats that the requirement addresses the users why and not the how.

37
Q

Requirements Documentation

What format does a User Story take?

A

**Gherkin Model:
**
AS a business analyst
I Need/Want good reading materials
So that I can pass my exam

38
Q

Requirements Documentation

What information do you display in a Use Case diagram?

A

A use case diagram helps to understand the scope of a system - it displays:
* the system
* the action within the system
* the actors / other systems that interact with the activity within the system
* the association with other actions
* NFR’s that can be linked to each action

39
Q

What is included in a data model?

A
  • entity - it’s name
  • attributes - it’s data items
  • relationships - 1to1 etc
40
Q

Requirement Documentation

What us the purpose of a process map?

A

A process map outlines:
* the high to low level process
* the inputs and the outputs
* the actors / teams / systems / data involved

41
Q

How can process maps, use case diagrams and data models, user story’s be used together?

A

Using a combination of different models can highlight gaps that have not been considered

42
Q

What is the purpose of a prototype?

A

A high/low fidelity model can show how the solution COULD work.

Benefits:
* Easily to visualise & spot gaps

Risk:
* When sharing people can be fixated on the wrong thing
* Difficult to throw away if spent a long time on them

43
Q

Documenting Requirements

What does a decision table do?

A

A decision table, or other cross referencing tools can help to spot gaps and ensure all requirements have been accounted for.

EG. CRUD

BCS Oral Exam (5 decks)

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