Requirements management is the cornerstone of the Cockpit Platform, with everything connected. Voices flow down to requirements, sub-requirements are born out of parent requirements, tests are created to verify/validate requirements, and so on. Cockpit makes managing requirements easy. Using allocation matrices, teams can easily allocate requirements to a specific Bill of Materials (BOM) used later in the design process. With a strong requirements core everything else falls easily into place.
Cockpit’s import functions allow teams to easily import existing data from virtually anywhere. Word or Excel documents? Have your requirements in another tool? Not a problem. Cockpit provides Word, Excel, XML, and REST methods of data import to make the transition seamless.
Cockpit provides out-of-the-box mechanisms for integrating simple and complex calculations into the requirements process. Use Matlab or Excel to create complex Transfer Functions to calculate design values or use simple A + B calculations; the Platform supports both methods.
Cockpit provides numerous scorecards to view the current status of requirements or breakdowns of requirements. Out-of-the-box methods for analyzing marginal and statistical variation include Cpk, Z Score, PNC, and DMPO. Set your own threshold scores for each method to match your company’s SOPs.
FLOWUP AND FLOWDOWN
Flowup or flowdown requirements in simple tables built specially for your needs. Trace downstream to lower level requirements or to other items such as risks and tests. Or trace upstream to see parent requirements and the originating voice of the customer. Traces are completely configurable throughout the entire platform.
Requirements Management Features
Cockpit allows you to import requirements from multiple external sources such as Excel, Word, XML, and other tools.
Cockpit computes values throughout the development process using transfer functions, which are then reported in scorecards or stoplight charts used to make decisions and trade-offs
Differences in the requirement and predicted value differ, cause problems. Knowing this early enables you to fix this more cost effectively.
Cockpit uses parent/child linkages to predict which lower level sub-requirements most contribute to the problem, as well as which higher level requirements will be affected by a resulting design change.