Requirements are the foundation for product development
Customer needs (Voice of the Customer) are associated with requirements. These serve as the basis for sub-requirements, product breakdown structures, tests, and so on. Cockpit makes managing requirements easy.
By using matrices, teams can easily assign requirements to a specific BOM (Bill of Material) that is used later in the design process. With a strong foundation based on requirements, everything else falls easily in place.
Cockpit’s import features allow teams to easily import existing data from virtually any location. Word or Excel documents? Do you have your requirements in another tool? No problem. Cockpit provides Word, Excel, XML, and REST data import methods to make the transition transparent.
Cockpit is unique in its functionality to perform simple and complex calculations based on numerical requirements. You can also use Matlab or Excel; The platform supports both methods.
Cockpit offers several scorecards to view the status of requirements or requirements hierarchies. Methods such as CPK, Z Score, PNC and DMPO are supported. Set your own threshold values that match your company’s work processes.
Flow-up and Flow-down
Flow-up or flow-down requirements in simple tables. Relate to requirements at a lower level or to other items, such as risks and tests. Or relate to parent requirements and the original Voice of the Customer. Traces are fully configurable across the entire platform.
Requirements Management Functionalities
With Cockpit, you can import requirements from multiple external sources, such as Excel, Word, XML.
Cockpit calculates values using transfer functions, which are then reported in scorecards or “traffic light diagrams”. These are used to make decisions and choices.
Deviations between requirements and design value can cause problems. The quicker you know this, the more cost-effective you can solve it.
Cockpit uses relationships between top and underlying requirements to identify the impact of design changes.