Tuesday, October 24, 2017
Dashboards
Minimize
  RPI provides one of the richest dashboard experiences with over 50 dashboard components. As projects today become more complex, you need a tool that can provide visual indicators that can provide insight to the health of your projects at a glance. RPI dashboard components not only provide you with up to the minute status, but also provides valuable analysis to the health of your organizational process. Visual indicators will direct you to what is not working so that you can focus your attention to those areas. It also shows what is working and should be left alone or deployed to the rest of the organization.
  
Dashboard Components
Requirement Dashboard Componets
Requirement Creation By Resource Requirements Creation By Resources component will show a pie chart that displays the resource names and percentages of requirements created by those resources.
Requirement Creation History The Requirement Creation History component shows the dates and counts of when requirements are created. The spikes indicate an increase of requirement creation for a given day and the valleys show when fewer requirements are created.
Requirement Creation Rate The Requirement Creation Rate component shows the accumulated requirements for a given time period. The chart will always indicate an upward trend to show how many requirements have been created.
Requirements By Collection The Requirement By Collection component is used to display the percentages of user defined groupings of requirements.
Requirements By Components Requirement By Component component is used to display the percentages of requirement groupings in terms of the components within a project.
Requirements By Group Requirement By Group component is used to display the percentages of requirements based on the group that they have been placed.
Requirements By State The Requirements By State component is used to display the states of all requirements for the selected projects and within a given date range.
  *** NEW***
Requirements Level of Effort Estimates
The Requirements Level of Effort Estimates component is used to display the progress the of the estimation process and the accumulated estimation time for the requirements that been already estimated.
Risk Dashboard Components 
Risks By Collection The Risks By Collection component is used to display the percentages of user defined groupings of risks.  
Risks By Component The Risks By Collection component is used to display the percentages of user defined groupings of risks.
Risks By Requirements Groups Risks By Requirements Group component is used to display the percentages of requirements based on the group that they have been placed.
Risks By State The Risks By State component is used to display the states of all risks for the selected projects and within a given date range.
Risks By Status Risks By Status component is used to display the ratio between Risks and Issues.
Risks Entered History The Risk Entered History component shows the dates and counts of when risks are entered. The spikes indicate an increase of risks entered for a given day and the valleys show when fewer risks are entered. Spikes could be an indication that something is impacting a release. Valleys can be an indication that the release is stable.
Risks Entered Rate The Risk Entered Rate component shows the accumulated risks for a given time period. The chart will always indicate an upward trend to show how many risks have been created.
Risks Pareto By Projects Risks Pareto By Project component will identify the top 10 projects that are producing the greatest number of risks. The projects are displayed from the largest group to the next largest group.
Risks Pareto By RPN Count Risks Pareto By RPN Count component will identify the top 10 risk counts grouped by the RPN number. The counts are based on the number of risks, RPN is not used in the selection of data.
Risks Pareto By RPN Value Risks Pareto By RPN value component will identify the 10 highest RPN value groups and list how many risks are in each grouping.
Task Dashboard Components
Tasks By Requirement Group Tasks By Requirements Group component is used to display the percentages of tasks based on the group that they have been placed.
Tasks By Resource Task By Resources component will show a pie chart that displays the resource names and percentages of tasks assigned to those resources. This component can be useful in determining the work load distribution among resources as it pertains to tasks.
Tasks By State The Tasks By State component is used to display the states of all tasks for the selected projects and within a given date range.
Tasks Completed By Component Task Completed By Component will show a pie chart that displays the total tasks marked as completed by a resource.
Tasks Entered History The Task Entered History component shows the dates and counts of when tasks are entered. The spikes indicate an increase of tasks entered for a given day and the valleys show when fewer tasks are entered.
Tasks Entered Rate The Task Entered Rate component shows the accumulated tasks for a given time period. The chart will always indicate an upward trend to show how many tasks have been created.
Test Case Dashboard Components
Test Cases By Author Test Cases By Author component will show a pie chart that displays the resource names and percentages of test cases created by those resources.
Test Cases By Collection The Test Cases By Collection component is used to display the percentages of user defined groupings of test cases.
Test Cases By Requirements Group Test Cases By Requirements Group component is used to display the percentages of test cases based on the group that they have been placed.
Test Cases By State The Test Cases By State component is used to display the states of all test cases for the selected projects and within a given date range.
Test Cases Entered History The Test Cases Entered History component shows the dates and counts of when test cases are entered. The spikes indicate an increase of test cases entered for a given day and the valleys show when fewer test cases are entered.
Test Cases Entered Rate The Test Cases Entered Rate component shows the accumulated test cases for a given time period. The chart will always indicate an upward trend to show how many test cases have been created.
Test Cases Needed The Test Cases Needed component is used to display the total number of test cases that are needed as indicated in the original requirements records. When these test cases are completed, they migrate from the Test Cases Needed slice to the Test Cases Completed slice.
Test Suite Dashboard Components
Test Suite Results The Test Suites By Test Results component is used to display the states of all Test Suites Cases within the Test Suites for the selected projects and within a given date range.
Test Suite Tested By Resources The Test Suite Tested By Resource component will show a pie chart that displays the resource names and percentages of test cases executed by those resources.
Test Suite Testing History The Test Suite Testing History component shows the dates and counts of when test cases were executed. The spikes indicate an increase of test case execution entered for a given day and the valleys show when fewer test cases were executed.
Test Suite Testing Rate The Test Suites Testing Rate component shows the running totals for executed test cases for a given time period. The chart will always indicate an upward trend to show how many test cases have been executed.
Test Suites By State The Test Suites By State component is used to display the states of all test suites for the selected projects and within a given date range.
Defects Dashboard Components
Defect By State The Defect By State component is used to display the states of all defects for the selected projects and within a given date range.
Defect By Type The Defect By Type component is used to display the types of all defects for the selected projects and within a given date range.
Defect Closure Performance The Defect Closure Performance component shows the average time it takes for the defects to go from one State to the next.
Defect Entered History The Defect Entered History component shows the dates and counts of when defects are entered. The spikes indicate an increase of defects entered for a given day and the valleys show when fewer defects are entered.
Defect Find Rate The Defect Find Rate component shows the accumulated defects for a given time period.
Defect Pareto By Collection The Defect Pareto By Collection component will group the defects into the 10 largest groups displayed from the largest group to the next largest group.
Defect Pareto By Component Defect Pareto By Component component will group the defects into the 10 largest groups displayed from the largest group to the next largest group.
Defect Pareto By Project Defect Pareto By Project component will identify the top 10 projects that are producing the greatest number of defects.
Defect Pareto By Type The Defect Pareto By Type component will group the defects into the 10 largest groups displayed from the largest group to the next largest group. Pareto charts do not show all of the groupings, only the ten largest.
Defect Phases Escaped Detailed Defect Phases Escaped Detailed component is extremely useful to evaluate the effectiveness of your quality controls within your software development process.
Defect Phases Escaped Defect Phase Escaped component is useful to evaluate the effectiveness of your quality controls within your software development process.
Defect Phases Found Defect Phase Found component is useful to evaluate the effectiveness of your quality controls for each development phase within your software development process.
Defect Resolution Rate Defect Resolution Rate component will show the historic levels of unresolved Defects over time.
Defect Resolved By Resource Defect Resolved By Resources component will show a pie chart that displays the resource names and percentages of resolved defects by those resources.
Defect Resource Resolution Performance Defect Resource Resolution Performance component shows the average time it takes for a resource to start investigating and then resolve defects.
Defects Aging The Defect Aging component can be configured to identify three age ranges; its purpose is to provide an awareness of aging defects so that they do not fall through the cracks.
Copyright 2010 by SoftEXIT