Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

Requirements Engineering (BCS) > Record Requirements (15%) > Flashcards

Record Requirements (15%) Flashcards

1
Q

Requirement Categories

A

Business & Solution

Business (General & Technical)
Solution (Functional & NFR)

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

What requirements are associated with enterprise level?

A

Business requirements (General & Technical)

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

What requirements are associated with product/service level ?

A

Solution (Functional & NFR)
They tell us what we need the system to do

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

What sits above all requirements?

A

The business objectives (all requirements should vertically align to biz objectives)

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

6 types of General (business) Requirement?

A

Business Constraints: Budget/Timescales/Resources

Business Policies: Standards/ Business rules

Legal: Legislative/Regulatory

Branding: Images/style guide

Cultural: Vision/approach & Management style

Language: International boundaries/spelling

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

4 types of Technical (business) Requirement?

A

Hardware: IT & other hardware

Software: Operating systems/Package applications/Networking/Communications

Interoperability
Standards for communicating between systems and devices

Internet
Policies on internet use & web services / cloud

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

5 types of Functional (solution) Requirement?

A

CRUD + Procedural
Create i.e. data entry

Read/retrieve i.e. reporting & responding

Update i.e. changes to data

Delete

Procedural i.e. Implementation of business rules

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

Relationship between NFR’s & FR’s

A

Non-Functional constrain the Functional requirements (generally)

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

Relationship between Business & Solution Req

A

Business req constrain functional requirements

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

Relationship between Business & Solution Req

A

Business req constrain functional requirements

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

What are Functional Requirements?

A
  • Expressions of stakeholder needs of a system to achieve particular goals
  • They are WHAT the system must do, functionality it must offer
  • Often summarised as CRUD
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Functional Req Examples

A

The system shall:
(Create)
Hold details of all customers including name, address,credit limit, date of first order

(Update)
Allow changes to be made to customer details

(Read)
Report on all orders placed in the last week

(Delete or Update)
Orders can be cancelled

(Procedural, business rule)

An insurance policy can have a maximum of 3 policyholders

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

What are Non-Functional Requirements?

A

Define HOW WELL the functional requirements will be provided

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

10 Types of NFR’s

A

Performance (speed)
Security (data/information)
Access (who - permissions and constraints)
Backup & recovery (protection)
Archiving & retention (duration/methods)
Robustness (reliability)
Business continuity ( disaster) In the book
Availability (99.9% / ad hoc etc)
Usability (ease of use)
Accessibility (insurance)
Capacity (scalability-volume)

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

How to uncover NFR’s?

A

Use both a ‘top-down’ and a ‘bottom-up’ approach
Get the Stakeholders involved

Top down: look at NFR category and ask which applies to the product

Bottom up: Look at functional requirements and ask is this subject to specific constraints

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

NFR’s Examples

A

Only the Accounts Supervisor may change a customer’s credit limit
(access requirement)
Reprint the report on demand
(availability requirement)
Respond to an enquiry on available customer credit within 5 seconds
(performance requirement)

17
Q

Why do we need to document requirements?

A

Communication
Consistency
Validation
Development

18
Q

Which type of project is best suited to BRD?

A

Linear project

19
Q

What type of project is best suited to user story?

20
Q

Narrative Documentation

A
  • BRD (Linear)
  • User Story (Agile)
21
Q

Diagrammatic Documentation

A
  • Data Model
  • Use Case Model
  • Business Process Model
22
Q

Characteristics of BRD

A
  1. ID & Version
  2. Author
  3. Date
  4. Name (short description)
  5. Description (Actor/Verb Phrase/Object). i.e. The receptionist shall be able to view customer name
  6. Status
  7. Acceptance Criteria
  8. Source
  9. Owner
23
Q

What is a user story?

A

Smallest unit of functionality

Brief & Informal

24
Q

User Story format

A

As a [role], I want to [use a feature] so that I can [achieve a goal/rationale]

Who/What/Why

3C’s - Card/Conversation/Confirmation

25
Q

What should a good user story look like?

A

INVEST

Independent (Not linke. Should be discrete & atomic)
Negotiable (Ability to elaborate further for clarification/prioritisation)
Valuable – to users or customers
Estimatable (Effort to take to deliver (relative size etc)
Small (Relative to timeframe (sprint etc))
Testable / Traceable

26
Q

Where are Use Stories held?

A

Product backlog

Requirements Engineering (BCS) (8 decks)

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