Requirements Engineering Flashcards
Requirement Elicitation
What techniques can you use for requirement elicitation?
- Interviews
- Workshops
- Observations
- Surveys
- Prototyping
- Document analysis
- Scenario analysis
Requirements Framework
What does the requirements engineering framework include:
- Elicitation
- Analysis
- Documentation
- Validation
- Management
Requirement Elicitation
What are the two knowledge types?
- Tacit
knowledge, skills, and abilities gained through experience - Explicit
knowledge that can be easily expressed, documented, and shared between people
Requirement Elicitation
What insight can tacit knowledge bring?
- Norms
- Culture
- Back story
- Organisation history
- Community of practice
Requirement Elicitation
What are examples of explicit knowledge?
- Procedures
- Style guides
- Processes
- Organisation structure
- Manuals
- Organisation guidance
Requirement Elicitatiaon
What is the difference between requirement elicitation and requirement analysis?
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.
Requirements Analysis
What are key activities in requirements analysis?
- 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
Requirements Analysis
Why do we need to check that requirements align with business objectives/case?
Requirements should address a root problem and be in scope
out of scope requirements might sit with other projects
Requirements Analysis
What quality attributes should a requirement include?
Requirements should be:
* Clear
* Complete
* Consistent
* Traceable
* Unambigous
* Relevant
* Testable
if it doesnt adhere to these then the wrong thing could be delivered
Requirements Analysis
What categories should we be looking at to ensure something is feasible?
- techincally possible
- possible within business
- financially possible
Requirement Analysis
How might a requirement be prioritised?
**MOSCOW
**
* Must Have
* Should Have
* Could Have
* Won’t Have
Backlog prioritisation
* Dependancies
* Size / Complexity
* Impact
Requirement Analysis
What are the qualities of a well structured requirement?
- Follow a consistent pattern
- Correctly labelled
Linear you might use req catalogue, Agile you might use user stories,
Requirement Analysis
How do you handle overlapping / duplicate requirements?
- Remove duplicates
- Merge requirements
- Break down into smaller requirements
Requirements Analysis
How can Scenario analysis , prototypes & process maps help with requirement analysis?
- visualise the problem
- identify gaps in requirements
Requirements Analysis
What can you use to understand user perspective?
- User/Customer Journeys
- Personas
- Use case diagrams
use case diagrams show who needs to interact with a system
Requirement Validation
How might requirements be validated in a linear delivery?
- Quality Checks
- Informal Reviews
- Formal Reviews
- Sign off by SME’s , Owners, Developers, Testers
Requirement Validation
How are requirements be signed off in an agile delivery?
- Backlog grooming
- Stories refined (3 amigos etc)
- Accepted
Requirement Management
Why is it important to have a well defined set of requirements?
A good set of requirements will support a successful delivery
Requirement Management
What are the key elements of requirements management?
- Identification
- Source
- Owner
- Change Control
- Version Control
- Storage
- Traceability
Requirement Traceability
What is meant by Vertical Traceability?
Requirements that are traceable from the source to the business objectives
eg. we know the ownership
Requirements Traceability
What is meant by Horizontal Traceability?
Traceability from origin to delivery and back.
Requirement Change Control
What are the stages of change control?
- Document
- Analyse
- Consult
- Decide
- Implement or Reject
Requirements Change Control
What can be the source of a change?
- Change in objectives
- Change in stakeholders
- Change of legislation
- Competitor action
- Change in technology
- Change in priorities
- Users develop better understanding of need
Requirements Version Control
What is a baselined version of requirments?
A frozen version of requirements that has been signed off by stakeholders
Requirements Version Control
What must be recorded as part of version control?
- Version number
- Who has signed it off
- every iteration or change but be signed off and assigned a version number
Requirements Version Control
Why should old versions of requirements never be thrown away?
- To enable the ability to roll back if needed
- To provide context to changes made
Requirement Documentation
What is the benefit of linking requirements together?
- It helps to ascertain dependent requirements & cross over
- Changes to one requirements might have a knock on effect to another
Requirements Management
What are the two types of Business requirement?
- General
- Technical
These are at the enterprise/business level
Requirement Management
What are the two types of Solution requirement?
- Functional
- Non-Functional
These are at the product level
Requirement Management
What type of requirement would be classed as a general requirement?
as a type of business requirement
- 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
Requirements Management
What type of requirement would be classed as a Technical requirement?
as a type of business requirement
-
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
Requirements Management
What does a functional requirement represent?
as a type of solution requirement
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
Requirements Management
What does a non-functional requirement represent?
as a type of solution requirement
How we want the solution to behave
* Performance
* Security
* Access
* Backup and Recover
* Archiving & Retentional
* Robustness
* Business Continuity
* Availability
* Usability
* Capacity
* Accessibility
Requirements Management
What legislation do you have to consider when compiling requirements?
- Data Protection
- Disability Access
GDPR, W3C AA
Requirements Documentation
What should be recorded in a requirements document?
- ID/Reference Number
- Name
- Description
- Owner
- Acceptance Criteria
- Priority
- Linked Business Rules
- Traceability
- Status
- Date
- Signed off by
Requirements Documentation
What is the purpose of a User Story?
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.
Requirements Documentation
What format does a User Story take?
**Gherkin Model:
**
AS a business analyst
I Need/Want good reading materials
So that I can pass my exam
Requirements Documentation
What information do you display in a Use Case diagram?
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
What is included in a data model?
- entity - it’s name
- attributes - it’s data items
- relationships - 1to1 etc
Requirement Documentation
What us the purpose of a process map?
A process map outlines:
* the high to low level process
* the inputs and the outputs
* the actors / teams / systems / data involved
How can process maps, use case diagrams and data models, user story’s be used together?
Using a combination of different models can highlight gaps that have not been considered
What is the purpose of a prototype?
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
Documenting Requirements
What does a decision table do?
A decision table, or other cross referencing tools can help to spot gaps and ensure all requirements have been accounted for.
EG. CRUD
