5. Requirements Management and Documentation Flashcards
What is Requirement Management
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
Why must we manage our requirements
A set of requirements sets a good basis for a project however should the requirements change in any form it can be very hard to track this, a good approach to requirement management will make any changes to requirements or queries regarding them easy to deal with.
Name 3 elements of requirement management
Identifying requirements Recording the source of the requirement Requirement owner Related Requirements Change control Version control Requirement storage
What are the two type of requirement traceability
Vertical traceability (To business objectives) Horizontal (From origin to delivery)
What is the Change Control process
Submission of change request Review and logging of request Determination of feasibility of request Approval/denial Implementation of change request
Why do we use version control
For traceability, to identify where changes have been made to a requirement should we be challenged on them
What tools are there for requirement management and what functionality can these provide
Anything from a basic excel or word document through to developed software such as Jira - most well known
Useful throughout lifecycle of project from documentation through to delivery, provides transparency to all involved
Functionality provided by tools o Storage of documentation and models o Linkage and cross-referencing o Change and version control o Access restrictions
What are the 4 main types of requirement
General Business Requirement
Technical requirement
Functional Requirement
Non-Functional Requirement
Name 3 types of Non-Functional Requirements
Performance Security Access Backup & recovery Data archiving and retention Maintainability Business continuity Availability Usability Accessibility Scalability Capacity
What Legal issues should be considered when managing requirements?
Data protection
Disability access
Why should we consider data protection as a business analyst
When documenting our requirements we must ensure they fall in line with the principles of GDPR, particularly thinking about retention, access and ensuring any customer data is used for intended purpose any ensuring the ability to meet these regulations is built into our requirements
Why should we consider disability access as a business analyst
It is an area that is often overlooked, 1 in 5 people have some sort of disability, be it visual, audible or other and we must ensure the requirements for our solution do not exclude and instead include any persons with a disability. Employers have a duty to make adjustments for those with a disability where reasonable, if these are factored into the initial requirements it helps to resolve these issues should they arise.
Name 2 styles of requirement documentation
Use case diagram
User stories
Data Model
Requirements catalogue
Name 5 items you may find against each requirement in a requirement catalogue
identifier name description business area type of requirement author source owner priority rationale/justification cross-referenced requirements cross-referenced documents acceptance criteria status/resolution version number and date
Why do we model requirements
It is very difficult to write unambiguous requirements as a text statement, when supported with a model it becomes much easier for all to understand and generates questions where items are not understood
