Improve Quality Through the Lifecycle
Gain confidence with integrated tools to complete the verification and validation processes
Verify the system built meets the previously validated design requirements and system models with Test Center. Test Center uses a hierarchical document-like display of Test Case entities with collapsible sections, status roll-up, and inline entity editing.
Verification Method Labels
Innoslate‘s default database schema provides five different verification method labels for requirements: Analysis, Demonstration, Inspection, Modeling & Simulation, and Test. Trace these requirements to the verification methods in Test Center.
Innoslate can now capture the results from simulations and tests as X-Y Plots using the new Charts View. Import output from other tools to create the Innoslate objects automatically. Click off lines to see other lines that represent a smaller scale. Insert these charts into documents as needed.
Beginning the validation process early in the lifecycle enhances the probability of success by identifying errors early in the development phase and preparing for the verification process later in the lifecycle.
Innoslate provides integrated tools to help automate requirements validation such as the Quality Check feature of Requirements View. The Quality Check feature is used to assess a requirement’s clarity, completeness, consistency, design implications, traceability, and verifiability.
Use the Traceability Matrix with its NLP/ML-driven Traceability Assist and Suspect Assist to ensure that the requirements trace correctly. Use them to identify missing information between the requirements, models, and test cases.
Innoslate provides integrated tools to help automate model validation as well such as the NLP/ML-driven Intelligence View assess a model’s traceability, construction, naming conventions, and more.
“Discrete Event Simulator” and the “Monte Carlo Simulator” ensure a model executes and produces analytics for cost, schedule, and performance. These simulators detect errors in logic and potential bottlenecks in the design early in the lifecycle.