Scribd
Upload
37 views

Week 2 Study Guide: Topic 2 - Analysing and Documenting Requirements

The document provides an overview of analyzing and documenting requirements for business analysis. It discusses how requirements fuel business analysis activities and guide efforts to implement them. Proper documentation is important for leveraging requirements to drive positive business change. The documentation needs to be done well since so much depends on the effectiveness of the requirements. The intended learning is for students to understand how requirements are defined, analyzed, documented, and recorded in business analysis. It includes questions to guide understanding of key principles such as the purpose of requirements streams, filters, and catalogs.

Uploaded by

KENMOGNE TAMO MARTIAL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
37 views

Week 2 Study Guide: Topic 2 - Analysing and Documenting Requirements

The document provides an overview of analyzing and documenting requirements for business analysis. It discusses how requirements fuel business analysis activities and guide efforts to implement them. Proper documentation is important for leveraging requirements to drive positive business change. The documentation needs to be done well since so much depends on the effectiveness of the requirements. The intended learning is for students to understand how requirements are defined, analyzed, documented, and recorded in business analysis. It includes questions to guide understanding of key principles such as the purpose of requirements streams, filters, and catalogs.

Uploaded by

KENMOGNE TAMO MARTIAL
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Week 2 Study Guide

Topic 2 – Analysing and Documenting Requirements


Description
Requirements are the fuel that powers business analysis activities, and they are the guiding force
that steers the efforts and investment that goes into bringing them to life. Requirements need to
be clear, concise and effective – and this requires detailed analysis. The role of business analysis
is to distill the value and the truth from requirements and turn them into a powerful force for
change within the business.

Doing this requires careful recording of those requirements. Proper documentation is not just
about record keeping, it is about leveraging the truth in those requirements to bring about positive
change. Since so much rests on the effectiveness of this documentation it needs to be done well.

Intended Learning
Students will explore the details of how requirements are defined and analysed by business
analysis. We will explore methods of requirement analysis as well as the ways in which
requirements are properly documented and recorded.

Questions to Ponder
Consider the following questions as a guide to understanding this topic. Ask yourself how well
you understand these principles and how comfortably you could explain them to someone else.

1. What is the purpose of dividing requirements into vertical streams?


2. What are requirements filters and how do they help us refine our requirements?
3. What is the role and function of the requirements catalogue?
4. Why is it so important that so many details about requirements are tracked and recorded?
5. What is the purpose and function of a use case diagram in contrast to other UML
diagrams?

Considerations
As we explore this topic take these considerations into account when forming your own opinions.

 Not every requirement is worth the same to the business, but before we can prioritise
them we need a way to categorise them.
 Categorising requirements helps us to align them with business stakeholders.
 The analysis process is all about distilling the requirements into a concise and useful set
of requirements.
 The final requirements document includes business, functional and data models as well
as the actual requirements catalogue.
 We need to be careful to be clear on what type of UML diagram we are using to
understand a process, system, scenario or situation.

Listening
Download and listen to the following pre-recorded audio lectures for this topic.

You might also like