Manage Requirements Coverage, Testexecution and Reporting

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. What are requirements? Requirements can be high-level descriptions or formal documentation for your release, depending on your development methodology. For example, you might have a requirement to send an astronaut to Mars and bring them back to Earth, and your backlog will be comprised of a huge number of detailed features, user stories, and tasks. You can also use requirements to document business-oriented information rather than simply defining deliverables. For example, within requirements you might enter business objectives, executive briefs, risk factors, or market opportunities. You can link requirements to tests and defects, providing you with coverage on each requirement. If your team works with both requirements and backlog, the two can be linked to one another, showing which backlog item implements which requirement. How are requirements related to backlog items? 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. Working with requirements First you create a framework of high-level requirements. You then add additional child requirements to break these into manageable parts and give team members a better understanding of the specific objectives. Requirements can also be formed in traditional ways such as goals, use cases, security effects, or performance changes. For more informations: https://admhelp.microfocus.com/octane/en/15.0.60/Online/Content/UserGuide/articles_requirements.htm