
Part 1 – Getting started with Requirements
Authoring and Management Mode
Build Overview Tab
Import from Excel
Flat format
Pre-formatted, including snapshots
Define Requirement Templates
Provide | Define Template Structure
Part 2 – Requirement Coverage
Define Coverage
Create Tests, add steps
Execution in Draft | Normal mode
Defect Tracking
Reporting (ongoing)
Learn how to bulk assign multiple requirements to a release in ALM Octane via the requirements module, selecting all, updating to release 2.0, and using add-to-existing-value for coverage.
Identify requirements with no test coverage for release 2.0 by applying a quick filter on the all requirements screen, revealing the uncovered 41 items to inform test planning.
Identify requirements that are covered by tests but have no execution, using Release 2.0 filters to reveal test cases with no execution coverage.
If you are an experienced ALM Quality Center user, you may want to check out the ALM Octane for ALM Quality Center Users Course on Udemy.
The Requirements module provides you with a central repository for documenting and tracking all aspects of your project, from conception to delivery. This can include business goals, customer requests, functional requirements, or any other requirements whose approval and progress you want to track. Requirements can be high-level descriptions or formal documentation for your release, depending on your development methodology.
From a use-case perspective, the Backlog module is project-management oriented. Backlog items are defined in a hierarchy of epics, features, and stories, and different backlog items are created for different teams (for example back-end vs. client).
Requirements contain the overall story of what you want to deliver, rather than a hierarchy of tasks. For example, you might define a requirement as "Multi-language support," and this could be mapped to ten different items in the backlog.
This is also reflected in the personas using these modules; backlog items may be written by project owners or PMOs, while requirements may be written by business analysts or PMs.
From the perspective of test coverage, you could work with both backlog and requirements in parallel. Alternatively, you could choose one of these modules to reflect quality implementation, and link your tests to that module.
Part 1 – Getting started with Requirements
Authoring and Management Mode
Build Overview Tab
Import from Excel
Flat format
Pre-formatted, including snapshots
Define Requirement Templates
Provide | Define Template Structure
Part 2 – Requirement Coverage
Define Coverage
Create Tests, add steps
Execution in Draft | Normal mode
Defect Tracking
Reporting (ongoing)
Upon successful completion of this course, you will be eligible to:
be more productive
better collaborate
use agile methodologies in a smarter way
support the software delivery lifecycle
take on lead roles in your projects and advance in your career