Below are some of the most popular features in DiagZ™. Click
on the thumbnail image of each feature to expand the screenshot:
 | Personalize your Home Page |
| When you login to DiagZ™, you are immediately presented with a personalized ‘dashboard’ of all your key information. All of your active projects, requirements, test cases, test sets, runs, incidents, etc. are consolidated onto a single page so that you can take immediate action.You can then add and remove information from your home page in order to see only the information that is important to you. |
|
 | View the Project Dashboard |
| Each project has a dashboard that summarizes all of the project information into a single comprehensive, easily digestible. The dashboard provides an “at a glance” view for team members interested in understanding the overall status of the project quickly. The dashboard contains summary-level information on requirements, test cases, incidents, etc. that you can use to drill-down into the appropriate section of the application. |
|
 | Manage Risk |
| In addition to the summary tables, charts and graphs displayed on the project dashboard, you can learn more about the risk associated with each requirement by viewing the requirements page. Here you can see the requirement’s name, the current test coverage, and the importance of the requirement. These views help you make risk assessments quickly and at a glance! |
|
 | View Requirements Coverage |
| Furthermore, some reports are specifically designed for managing and mitigating risks, such as the Requirements Coverage report: |
|
 | Create Reports |
| DiagZ lets you create reports that help you communicate the status of each requirement, test case, test execution, issue, etc. in printed form. These reports provide you with everything from an easy to execute printed test case, to the test results associated with a test execution, to a roll-up of the requirement’s status. |
|
 | Create Charts and Graphs |
| With DiagZ™ you can view key project metrics including Requirements Coverage, Test Run Progress, Incident Discovery Rate, Cumulative Artifact Counts, etc. visually and in graphical form! These charts and graphs help you manage risk, assess remaining effort, and the overall health of the project. |
|
 | Manage Requirements |
| Managing requirements can be a complex task. To simplify this task for you, DiagZ™ lets create, edit and manage project scope and requirements in a hierarchical manner. You can move, copy and filter the requirements according to a variety of criteria, and associate them with a specific release, and you can collapse and expand these hierarchies to hide or view information, or filter on something specific. |
|
 | Establish Test Coverage |
| Each requirement is mapped to one or more test cases that can be used to validate that the functionality works as expected. |
|
 | Break Down Requirements into Manageable Tasks |
| Each requirement can then be decomposed into its low-level assignable work items called ‘tasks’. Each can be separately estimated to validate the overall high-level requirement estimate.This technique also allows you to better manage your team’s efforts by prioritizing work items and dividing the labor associated with a given requirement. |
|
 | Manage Test Cases |
| DiagZ provides the ability to create, edit and delete project test cases that are stored in a hierarchical folder structure. With DiagZ, you can easily move, copy, and filter the test cases in any way you want. |
|
 | Manage Test Steps |
| Each test case consists of a set of test steps that represent the individual actions a user must take to complete the test. You can even include other template test steps as steps within your test case, giving the ultimate in reusability. |
|
 | Associate Test Cases and Requirements |
| Each test case is mapped to one or more requirements that the test is effectively validating, providing the test coverage for the requirement. This provides complete traceability from a recorded incident to the underlying requirement that was not satisfied. The relationship is bidirectional, so you can establish test case coverage for each requirement, and requirements coverage for each test case. |
|
 | Create and Manage Test Sets |
| To streamline the assignment and tracking of multiple test cases, DiagZ lets you select groups of test cases and arrange them into test sets.Each test set can contain test cases from a variety of different folders and can be associated with a specific release of the system being tested.Test sets can also be assigned to specific team members and assigned as work items to execute. You can even track the progress of a test set easily right in the Test Set view. |
|
 | Execute Test Cases |
| DiagZ™ provides the ability to execute groups of test cases - along with their test steps – so that the testers can follow the instructions and determine if the system being tested behaves as expected. |
|
 | Automatically Create Issues from Test Step Failures |
| Any deviations from expected behavior can then be recorded, and optionally a new incident created in the system – linked to the test step failure. |
|
 | Review Past Test Runs |
| Every time you execute a test case, DiagZ™ records every pass / failure as well as the associated incidents generated as a ‘Test Run’. These archived Test Runs can be viewed to determine if changes to the system have introduced failures to previously working functionality. |
|
 | Plan your Releases and Iterations |
| When developing a hardware project, you need to plan your releases well ahead of time. With DiagZ, you have the ability to create a master release schedule containing all the major milestone releases together with the individual iterations – smaller releases of the system delivered every 4-6 weeks. |
|
 | Quickly Establish and Assign Tasks |
| Tasks developed during the requirements elaboration can be associated with specific iterations in the release schedule. The system will track the available resources for a given iteration and calculate the available effort as tasks are added. |
|
 | View Incidents by Release |
| Each release provides drill down capability to list the incidents detected, resolved and/or verified in a particular release, enabling a quick determination to be made as to the stability and readiness of a particular release. |
|
 | View Test Runs by Release |
| You can view the list of all of the test runs executed against a specific release. Each test run is listed together with a customizable set of fields as well as a link to the actual test run details. The fields that can be displayed include - date of execution, name, tester, execution status, estimated duration, actual duration or any of the custom properties. |
|
 | Manage Test Cases by Release |
| The various test cases in the project can be associated with different releases, so that test runs and test case coverage can be reported on either in aggregate or separately for each release. This enables you to determine the quality of each release and also manage regression testing with ease. |
|
 | Associate Requirements and Incidents |
| Each Requirement or Incident can be linked to an unlimited number of other Requirements or Incidents. This provides traceability between related artifacts. For example a change request incident that turns into a new requirement can be associated to preserve the history of the requirement. |
|
 | Manage Issues |
| With DiagZ™ you can create, edit, assign, track, manage and close incidents (i.e. bugs, issues, risks, defects, enhancements) that are raised during each hardware validation and verification phase and throughout the life of the product. |
|
 | Create and Modify Incidents |
| Incidents can be categorized into bugs, enhancements, issues, training items, limitations, change requests, and risks, and each type has its own specific workflow and business rules. |
|
 | Resolve and Track Incidents |
| As different users collaborate on the identification, verification and resolution of a particular incident, their comments and resolutions are tracked as a threaded discussion so that the case history is always available. |
|
 | Track the Source of an Incident |
| Unlike a standalone bug/issue tracking tool, you can trace the incidents/defects back to the test case and the underlying requirement that generated them, giving the project manager unprecedented power in analyzing the “in-process” quality of a system during its lifecycle. |
|
 | Customize Incident Fields |
| You can customize each of the fields used in the Incident tracking module to suit your own business needs - including incident type, status, priority and severity. You can even associate your own color schemes with the different priorities and severities. |
|
 | Customize Workflows & Notifications |
| Each of the different incident types can follow its own customized workflow that you can map to the business processes used by your organization. Each workflow consists of a customizable set of steps and transitions. You can set the security on each transition so that only the appropriate user can change the status of an incident. In addition each transition can be used to send email notifications to the detector, owner or users in a certain project group. |
|
 | Add and Remove Attachments |
| You can upload document attachments to Requirements, Test Cases, Releases, and Incidents easily. Each of these artifacts includes an attachment view that allows users to view the existing attachments, delete an existing attachment and upload new documents from their workstation. |
|
|
 | Track Change History |
| All of the changes made to a particular artifact in the system (e.g. Requirement, Test Case, etc.) are tracked by DiagZ, so that at any time you can view the history log of all the changes made to an artifact, including the date of the change, who made the change, and what information was changed. |
|
 | Customize your Properties |
| In addition to the built-in fields that are associated with each type of artifact (Requirements, Test Cases, etc.), you can also define custom properties for each type of artifact in the system, both free-text properties and those where the user has to choose from a predefined list. |
|
 | No IT Staff Required! |
| Once DiagZ™ is set up on your web server it can be fully administered and maintained using only a web browser. No need to install complicated software or have IT staff involved every time you wish to create new project or add a user to the system. |
|
 | Add, Edit, Delete, and Manage Projects |
| DiagZ™ allows you to easily create, edit, copy, and delete projects using a web-based interface. In addition you have the option of creating a new project using the customized settings of an existing template project. |
|
 | Manage Users |
| DiagZ™ allows you to easily create, edit and make inactive users using a web-browser. In addition you can import user profiles from any LDAP compatible directory server (e.g. Microsoft ActiveDirectory). Once imported, DiagZ will authenticate those users against that server, removing the need for users to manage passwords in multiple places. |
|
 | Import Data from Excel |
| The web-based interface of DiagZ™ is ideal for creating and managing requirements, test cases and incidents for a new project. However when migrating requirements, test cases, test steps and incidents for an existing project from another system or Microsoft Office document (e.g. Excel), it is useful to be able to load in a batch of artifacts, rather than having to manually enter them one at a time. To simplify this task, DiagZ™ comes with a Microsoft Excel data importer that can bulk-load requirements, test cases, test steps and incidents from a populated Excel sheet into DiagZ™. |
|