|
||||||||||
|
Cockpit For Requirements Management
Cognition Cockpit brings Requirements Management into a whole new realm by including all of the important contributors of a requirement together in one single, seamless Web 2.0 user interface.
Older tools for Requirements Management are strictly text based meaning a requirement is nothing more than a sentence, paragraph, or picture. Validation & Verification events, such as test protocols and test items, are no more than documents attached to the requirement. A deliverable such as the Product Requirements Document is a hand made word processing file that is stored on a shared drive somewhere and is not easily available for real time collaboration by multiple users in scattered locations.
Older tools for Requirements Management are mostly built as individual "silos" of functionality which means a different tool, and therefore a different interface, for each fnction. This makes tasks like Configuration Management take on a choppy or unconnected feeling to the user since it is often a combination of two or more tools trying to work together. Most of thes older tools are built on older technologies and are therefore not Web 2.0 based or at best have some sort of afterthought "web interface" bolted onto the application.
Cognition Cockpit uses the newest Web 2.0 technology to bring all of the common Requirements Management functions together. Cockpit provides users with instant, live access to all information about a requirement. It offers a common user interface for all functions, single database for all project data, and product development process templates to guide users through each step with "bite sized" morsels of appropriate steps within each of your stage gates.Cockpit does all this:
Older tools for Requirements Management are strictly text based meaning a requirement is nothing more than a sentence, paragraph, or picture. Validation & Verification events, such as test protocols and test items, are no more than documents attached to the requirement. A deliverable such as the Product Requirements Document is a hand made word processing file that is stored on a shared drive somewhere and is not easily available for real time collaboration by multiple users in scattered locations.
Older tools for Requirements Management are mostly built as individual "silos" of functionality which means a different tool, and therefore a different interface, for each fnction. This makes tasks like Configuration Management take on a choppy or unconnected feeling to the user since it is often a combination of two or more tools trying to work together. Most of thes older tools are built on older technologies and are therefore not Web 2.0 based or at best have some sort of afterthought "web interface" bolted onto the application.
Cognition Cockpit uses the newest Web 2.0 technology to bring all of the common Requirements Management functions together. Cockpit provides users with instant, live access to all information about a requirement. It offers a common user interface for all functions, single database for all project data, and product development process templates to guide users through each step with "bite sized" morsels of appropriate steps within each of your stage gates.Cockpit does all this:
IN ONE SINGLE, NATIVE WEB 2.0 APPLICATION
1. Go to the INCOSE Systems Engineering Tools Vendor Database to see the chart for Cognition Cockpit. These functions are a good baseline for Requirements Management but Cockpit goes much farther by combining Risk Management, Voice Management, Cost Management, and Critical Parameter Management/DFSS in one single Web 2.0 user interface for concurrent distributed use.
2. Take a look at various Requirements Management tools and ask these questions of each:
1. Is it a native Web 2.0 tool with real time simultaneous remote access to all information?
2. Does it have a single user interface for every function (configuration management, risks...?
3. Is this a tool for everyone? Can a casual user get around without being and expert?
4. Are deliverables (documents, traces, etc.) automatically generated by the system?
5. Can it track requirements with numerical targets and provide live statistical feedback?
6. Is it provided as a single package with all functions in one price?
7. Does it include Risk Management as an integrated process with requirements?
8. Are there process templates to guide users through each step?
9. Is there a simple pricing model that is inexpensive and flexible to meet my needs?
10. Will my engineers want to use this system?
You should be able to answer a clear 'yes' to every question. For Cockpit, we expect you will answer 'yes' to all with the biggest 'yes' on question 10. Probably the most important question for a Requirements Management tool (or any tool) is "will they use it?" Are users going to look forward to interacting with the software or will it be just another burden to them? If they don't enjoy using the software they won't use it.
2. Take a look at various Requirements Management tools and ask these questions of each:
1. Is it a native Web 2.0 tool with real time simultaneous remote access to all information?
2. Does it have a single user interface for every function (configuration management, risks...?
3. Is this a tool for everyone? Can a casual user get around without being and expert?
4. Are deliverables (documents, traces, etc.) automatically generated by the system?
5. Can it track requirements with numerical targets and provide live statistical feedback?
6. Is it provided as a single package with all functions in one price?
7. Does it include Risk Management as an integrated process with requirements?
8. Are there process templates to guide users through each step?
9. Is there a simple pricing model that is inexpensive and flexible to meet my needs?
10. Will my engineers want to use this system?
You should be able to answer a clear 'yes' to every question. For Cockpit, we expect you will answer 'yes' to all with the biggest 'yes' on question 10. Probably the most important question for a Requirements Management tool (or any tool) is "will they use it?" Are users going to look forward to interacting with the software or will it be just another burden to them? If they don't enjoy using the software they won't use it.
3. Try out Cognition Cockpit. It is an intuitive web-based application that empowers your Product Development Process (PDP). Using its core Active Requirements Management technology, Cockpit enables your teams to dynamically manage customer inputs and voices, features and requirements, risks, costs, and critical parameters. Cockpit's next-generation approach uses the best practices from systems engineering and requirements management, together with simple yet powerful collaborative technology to seamlessly weave together all the critical steps in your PDP for instant traceability, analysis, and reporting.
Active Requirements Management means dynamically linking all your product requirements together with all associated information, such as team meeting minutes and notes, formal VOC input (surveys, interviews), risks, FMEA, risk mitigations, test protocols, documents, and mathematic analyses. These analyses, also called transfer functions, are a key a function of Cockpit, enabling you to create relationships and compute sensitivity between a requirement and its driving parameters. Only Cognition Cockpit delivers this active approach to requirements management.
Active Requirements Management means dynamically linking all your product requirements together with all associated information, such as team meeting minutes and notes, formal VOC input (surveys, interviews), risks, FMEA, risk mitigations, test protocols, documents, and mathematic analyses. These analyses, also called transfer functions, are a key a function of Cockpit, enabling you to create relationships and compute sensitivity between a requirement and its driving parameters. Only Cognition Cockpit delivers this active approach to requirements management.
If you currently use another tool for Requirements Management have no fear; Cockpit can import all of the information you have with a simple, rapid upload. Many users of tools such as Doors and Requisite Pro have successfully imported all of their information into Cockpit for a rapid, seamless transition to the new Web 2.0 technology used by Cockpit. You can do it yourself without any extra fess or assitance from Cognition. Why not give it a try?
Cognition Cockpit Brings Requirements Management To A Whole New Level
With Web 2.0 Technology
With Web 2.0 Technology
"Cognition Cockpit", "ECM", "Enterprise Cost Management", the Cockpit Logo, and Cognition graphics are all
copyright 2009 Cognition Corporation and are used here by permission | Terms of use | Privacy Policy
copyright 2009 Cognition Corporation and are used here by permission | Terms of use | Privacy Policy
Requirements Management
Automatically Generate Your Program Deliverables With:
From Cognition Corporation
Cognition Cockpit Is A Requirements Management Tool
Use It For Software, Hardware, And Total Systems
Ready To Use "out Of The box"
100% Web 2.0 Application
Multiple, Simultaneous Remote Users
Automatic Generation Of Document Deliverables
Online Process Steps Guide Users
"You Don't Have To Be An Expert"
Use It For Software, Hardware, And Total Systems
Ready To Use "out Of The box"
100% Web 2.0 Application
Multiple, Simultaneous Remote Users
Automatic Generation Of Document Deliverables
Online Process Steps Guide Users
"You Don't Have To Be An Expert"
Click here to go to INCOSE for information about Cognition Cockpit
at the 2008 Annual Symposium
at the 2008 Annual Symposium