Eliciting and Writing Effective Requirements
-
In the beginning, its little rushed but the group were experienced mostly so it was the right choice probably but in the end, the coach gives great examples and answer most of the question asked.
← | →
Course
Inhouse
Description
-
Type
Course
-
Methodology
Inhouse
-
Start date
Different dates available
You will learn to identify your audience, determine their requirements, and provide them with adequate and appropriate information. You will learn the technical writing techniques that apply directly to writing requirements documents and you will learn to apply the five Cs of writing-correct, clear, concise, comprehensive, and cohesive-to writing requirements. You will use lists, tables, and graphs to structure requirements information for clarity. And you will use white space, information chunking, and headings to improve readability. This course covers the “Requirements Documentation” knowledge area of the Business Analysis Body of Knowledge (BABOK®).
Facilities
Location
Start date
Start date
About this course
Upon completion of this course, you will be able to:Facilitate requirements-gathering sessions with Business and System Use-Cases.Examine the impact of the project on the enterprise through business use-case analysis.Create detailed textual requirements using a Use-Case Description Template.Decrease software bugs and omissions introduced in the analysis phase of your project – by employing advanced use-case techniques that reduce redundancies and inconsistencies in the documentation.Facilitate communication of user requirements between business stakeholders and the solution provider.Model who-does-what with use-case diagrams.Understand how use-cases are used in the context of iterative development.Link other relevant material to use-cases – such as business entities, non-functional requirements and activity diagrams.
* Business Analysts* IT Project Managers* Requirements analysts* Technical writers* Systems analysts* Developers* Software engineers* Project leaders* Senior project managers* Team leaders* Program managers* Testers* QA specialists
None – This course suitable for both novices and experienced people who need to elicit and write effective requirements. It is recommended that participants complete the BA01 – Business Analysis Essentials course prior to enrolling or have equivalent experience.
Successful projects are built on the foundation of well-written requirements. This course provides the skills to write well-formed, testable, verifiable user requirements so that you can translate client needs into clear and measurable metrics. These metrics provides a means to track success throughout your development cycle to ensure that business and user requirements are implemented in your final product.
Reviews
-
In the beginning, its little rushed but the group were experienced mostly so it was the right choice probably but in the end, the coach gives great examples and answer most of the question asked.
← | →
Course rating
Recommended
Centre rating
Lak Shon
This centre's achievements
All courses are up to date
The average rating is higher than 3.7
More than 50 reviews in the last 12 months
This centre has featured on Emagister for 6 years
Subjects
- CS
- Writing
Course programme
#text-block-10 { margin-bottom:0px; text-align:left; }
Section 1: Introduction
* Requirements and types of requirements
* Requirements in the product life cycle
* Project roles and requirements
* The role of the Business Analyst (BA)
Section 2: Writing Effective Requirements
* Attributes of effective requirements
* Audiences of the requirements and the audiences’ needs
* Level of detail
* Business vs. technical point of view
* Need for formality
Section 3: Knowing Your Audience and Their Needs
* Specific needs of business stakeholders and management
* Specific needs of Subject Matter Experts (SME)
* Specific needs of the technical team (developers, testers, etc.)
* Establishing a roles and responsibilities matrix
Section 4: Preparing to Gather Effective Requirements
* Functional requirements
* Quality of Service (QoS) requirements
* Assumptions and constraints
* General techniques used
Section 5: Conducting Requirements Elicitation Activities
* Tracing requirements
* Metrics used
* Capturing requirements attributes
* General techniques used
#text-block-11 { margin-bottom:0px; text-align:left; }
Section 6: Confirming Elicitation Results
* Managing scope and stakeholder expectations
* Managing requirements that conflict
* How to structure requirements for review
* General techniques used
Section 7: Capturing and Communicating Requirements
* The 5 Cs
* Bulleted and numbered lists
* Tables and graphs
* Models and other graphics
* Using white space and fonts
* Chunking requirements information and the use of headings
Section 8: Assessing Requirements Have Been Met
* Validation vs. verification
* Goals and participants in verification activities
* Goals and participants in validation activities
* Holding formal review sessions
Section 9: Additional Information
* Useful books and links on writing effective requirements
Eliciting and Writing Effective Requirements