Test Management
The Cockpit unified model shines when it comes to test management! Rich capabilities spanning V&V plans, requirement test traces, test submission workflow, and detailed test design and execution tracking help you drive the standardization and consistency that are key to confidence and success in your marketplace and the regulatory agencies who govern it.
Cockpit isn't just about traceability. Incredible efficiencies can be realized via the "enter once and populate many" approach to requirement and test management that is at our system's core. Cockpit knows that the V&V process can be messy and circuitous, but that when the time comes, you need on-demand traceability, dependable "no surprise" results, and consistent (think FDA) formats.
The verification process is often a race against time.
- Finishing the Requirements
- Writing your V&V Plan
- Writing multiple Test Protocols
- Test Setup
- Acceptance Criteria
- Execution Steps
- Execution Results
- Tracing everything…
- Knowing which tests…
- Trace to which requirements…
- In which protocol…
- Completely… without missing anything. It’s tedious and error prone!
- Capturing and discussing the test execution results…
- For status meetings…
- For multiple execution runs and milestones…
- And tracking actions and issues and notes. No wonder we’re late!
Verification and Validation Planning
Regarding V&V, helping you get your V&V Plan done efficiently without errors is what the Cockpit wants to do. It will “pull” requirements out of your requirements docs and include them in your deliverable. No re-typing. No missing items. Safer Audits.
The Cockpit’s Dashboard feature is an illustration of the benefits of a Single Unified Model. When an engineer can see everything that matters in one view, decisions are made a lot quicker…
Whether you have one protocol document or dozens, your verification tests need to be written and the Cockpit’s templates can help.
The FDA (etc) will begin to see standardization and consistency in your process.
Protocol Creation and Operational Efficiency
There’s a lot to do:
- Test Setup
- Acceptance Criteria
- Execution Steps
- Execution Results
Writing Test Protocols in the Cockpit is also supported. Templates can be tweaked to comply with your format and any number of sections can be defined, such as setup, acceptance criteria, execution steps, results, etc.
When you write test methods, Cockpit keeps track and is building libraries of them. They’re reusable and can be incorporated in any number of documents.
Cockpit allows you to define multiple execution “milestones” for the tests in any protocol, for example “Prior to Clinical”, “Prior to Submission”, etc. All the text you write can be general or milestone specific and you can reuse/toggle the document to correspond to the test milestone you are performing.
Cockpit can “auto-populate” acceptance criteria for you based on the links you've defined between tests and requirements. Cockpit can use those links to fill out your documents. If there are changes to the requirements, they will be reflected in real-time.
Similarly, results from each test execution are captured in the Cockpit. There are no restrictions; if a test will verify more than one requirement, the results for each are captured and presented clearly. You can choose any format you like, and the one above shows an action item column making it easy to track issues and activities.
Again, efficiency is important. If you’re having a meeting and you want to have a larger review of the test results, you can toggle the format to show all results from each milestone, as well as action items, notes, etc.
And for that really big meeting, you can show all the results for all the execution runs/milestones at once. Or, you can just use the Cockpit’s “Dashboard” features to get a bird’s eye view of the latest status.
