Download - Cognition Requirements Management
-
8/3/2019 Cognition Requirements Management
1/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
Risks
Mitigations
Documentation
Sub Reqs
Attachments
Tests
Action ItemsParent Reqs
In a Web 2.0 world,requirements should not be isolated.VOCs, Hazards, FMEAs, mitigation
plans, tests, test methods, protocols,
critical parameters, action items, etc.,everything can be unified.
-
8/3/2019 Cognition Requirements Management
2/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Bottom line
Selecting a Requirements Management tool is tricky
You have many choices Some are safe
Being the oldest
Most widely installed
Some are client/server
Some are Web-based Some are tuned for software development
Some are tuned for additional development
Some have module pricing and some a single price
Whichever you choose, your users will tell you if you got it right
They will either want to use it or they will avoid it at all cost
If they want to use it, you did well.
If not, you should try again.
-
8/3/2019 Cognition Requirements Management
3/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Introduction
Cognition Cockpit Web 2.0 Enterprise System Meets and exceeds baseline INCOSE* Requirements Mgt. standards
Configuration management Verification and validation System modeling Document standards Import and export
Single System where everything is connected in a Unified Model Requirements Management V&V Test Management Voice of the Customer (VOC)/Needs Management Risk Management Critical Parameter and Cost/Affordability Management
Meeting and Action Item Management Users will want to use it
One intuitive web interface for all functions Easy to learn and get stuff done Guided templates for deliverables and process steps Automatic output of deliverables and generation of trace matrices
* International Council on Systems Engineering
http://www.incose.org/http://www.incose.org/ -
8/3/2019 Cognition Requirements Management
4/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Requirements Management in the Cockpit
Like most other RequirementsManagement tools on themarket, Cockpit allows you to
import requirements frommultiple external sources suchas Excel, Word, XML, ReqPro,
DOORs, etc.
-
8/3/2019 Cognition Requirements Management
5/71
Copyright 2010 Cognition Corporation http://www.cognition.us
This is a typical Requirements
Document in the Cockpit. It is adynamic page produced from data inthe database. It supports requirementcreation, editing, reviewing, approving,
markups, spell-checking, etc. Thisformat is tabular in style, but you can
have any format you like.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
6/71
Copyright 2010 Cognition Corporation http://www.cognition.us
At the top of each document, thereis an Export command. When
clicked, the Cockpit produces aWord document, identical to the
on-line version. Headers, footers,table of contents, images, tables,
etc. are all supported properly.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
7/71Copyright 2010 Cognition Corporation http://www.cognition.us
Privileging in the Cockpit is fullysupported. Pick any item: requirement,
document, folder, project, etc. andselect the Access Rights. A page will
appear allowing you to set view,modify, delete and other privileges.You can also create and manage
privileges by groups of users.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
8/71Copyright 2010 Cognition Corporation http://www.cognition.us
Configuration management issupported in the Cockpit. This is trueat all levels: item, document, folder,
and project levels. The state transitionis shown above, but basically,
versions are baselined and revisionedas needed and each time an Approval
process may be invoked.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
9/71Copyright 2010 Cognition Corporation http://www.cognition.us
Visual differencing is also
supported. Clicking on the Diffcommand at the top of the pagewill open a new window with
redlines for deleted text, green fornewly added text, and so on. Allversions of a document may be
compared in this way.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
10/71
Copyright 2010 Cognition Corporation http://www.cognition.us
From a higher perspective, such as the
Project level, differences can also betracked. To start, a project is baselined, andthereafter, multiple working versions can becreated and further baselined. A complete
audit of new, deleted, and modified items isretrieved from the projects history page.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
11/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Flowing down top level requirements into lowerlevel subsystem/component requirements is
completely supported. Trace matrices areautomatically generated and change (stability)
notices are propagated through the requirement
hierarchy.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
12/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Requirements Management in the Cockpit
Whatever you are trying tomodel in the Cockpit, you
can create a breakdownfor it. In this case, theCockpit is being used to
create a use-case model.Additionally, the Cockpit
has a bi-direction link with
Microsofts Visio product.
-
8/3/2019 Cognition Requirements Management
13/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Next, the Requirements Managementfunctionality in the Cockpit is directly
connected to its Verification and Validationfunctionality. The V&V Plan, for example, isvery efficient to create, because templatesallow requirements written earlier (in the
PRD) to be automatically included.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
14/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Subsequently, allocatingrequirements to tests is
also supported. Many tomany relationships can becaptured, either through
clicking allocation
matrices or through many
other supported means in
the Cockpit.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
15/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Again, traceability is one of theCockpits greatest strengths.
Getting a tabular trace fromrequirements to tests or vice
versa is a simple mouse click.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
16/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Writing Test Protocols in theCockpit is also supported.Templates can be tweaked to
comply with your format and anynumber of sections can be defined,such as setup, acceptance criteria,
execution steps, results, etc.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
17/71
Copyright 2010 Cognition Corporation http://www.cognition.us
The Cockpit will auto-populatethe acceptance criteria section
for you. How? Earlier, youlinked tests and requirements
togetherand the Cockpit canuse those links to fill out this
section. If there are changes tothe requirements, they will bereflected in this document as
well.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
18/71
Copyright 2010 Cognition Corporation http://www.cognition.us
When you write test methods,the Cockpit keeps track and is
building libraries of them.Theyre reusable and can be
incorporated in any number of
documents.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
19/71
Copyright 2010 Cognition Corporation http://www.cognition.us
The Cockpit allows you to definemultiple execution milestones
for the tests in any protocol, forexample Prior to Clinical, Prior
to Submission, etc. All the textyou write can be general or
milestone specific and you canreuse/toggle the document to
correspond to the test milestone
you are performing.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
20/71
Copyright 2010 Cognition Corporation http://www.cognition.us
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 presentedclearly. You can choose any format you like, and
the one above shows an action item column
making it easy to track issues and activities.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
21/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Again, efficiency is important. If yourehaving 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.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
22/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Finally, to support quickdecisions and review,
Cockpit has many built-in reports showing thecurrent status of items:
for example, testcoverage, number offailures, etc. These
reports can be run fromany level, such as
document, folders, or
project level.
Requirements Management in the Cockpit
-
8/3/2019 Cognition Requirements Management
23/71
Copyright 2010 Cognition Corporation http://www.cognition.us
So, how does the Cockpits baseline capabilities
compare to other Requirements Management systems?
-
8/3/2019 Cognition Requirements Management
24/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Baseline Requirements Management Features
We believe you should review each ofyour Requirements Management tool
choices. INCOSE (International Council
on Systems Engineering) has a referenceavailable comparing many vendors. Thelink below will take you to the full report,
and weve included a subset of that
report in the next few slides.
INCOSE TOOLS SURVEY
http://www.incose.org/ProductsPubs/products/INCOSERMToolSurveyConsolidatedResults.xlshttp://www.incose.org/ProductsPubs/products/INCOSERMToolSurveyConsolidatedResults.xls -
8/3/2019 Cognition Requirements Management
25/71
Copyright 2010 Cognition Corporation http://www.cognition.us
-
8/3/2019 Cognition Requirements Management
26/71
Copyright 2010 Cognition Corporation http://www.cognition.us
-
8/3/2019 Cognition Requirements Management
27/71
Copyright 2010 Cognition Corporation http://www.cognition.us
-
8/3/2019 Cognition Requirements Management
28/71
Copyright 2010 Cognition Corporation http://www.cognition.us
-
8/3/2019 Cognition Requirements Management
29/71
Copyright 2010 Cognition Corporation http://www.cognition.us
-
8/3/2019 Cognition Requirements Management
30/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Conclusion?
But, what do you conclude from all of this?
Are the top tools really the same?
If so, why not select the oldest one with the largest user base?
No one gets fired for doing that...
-
8/3/2019 Cognition Requirements Management
31/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Trouble
The trouble is that traditional systems are not doing the job.
-
8/3/2019 Cognition Requirements Management
32/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Modern Requirements Management is driven by theadditional goals of achieving lean execution of the full ProductDevelopment Process, across hardware, software and process.
Market data analysis (Segmentation, KJ, etc.)
VOC/VOB/VOT/VOR assessment and prioritization Critical Parameter identification through HOQ and Hazard Analyses Design Concept Exploration and Selection (Pugh) System Tree / Functional Tree / Risk Tree Creation and Linkage Bottoms-up FMEA, Mitigation, and Control Plan Management 1st Eng. Principle Computation and Transfer Functions Critical Parameter Flow-down and Design Prediction Flow-up Statistical Variation Target Assessment / DCM Reporting Design of Experiments and Test Management
Product Cost Estimation and Initiative Management
Traditional RequirementsManagement has evolved
from software-centricneeds focused on carefuldocumentation andtraceabilityTextual Reqs & Specs Textual V&V Tests Trace Matrices
Traditional Software-centric Criteria And Hardware/Process-centric Criteria
The INCOSE baseline criteria is a great starting point
Numeric requirements need to be addressed
Voice of the Customer analysis needs to be addressed
Critical Parameter Management needs to be addressed
FMEA, Hazard and Requirement unification needs to be addressed
SW-centric criteria and HW/Process-centric criteria must combine:
The selection criteria needs to be broader
-
8/3/2019 Cognition Requirements Management
33/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Would you benefit from the Cockpit?
Textual Requirement/Specification Definition 100 10 8 10
Textual Validation Tests 70 10 8 10
Broad PDP Trace Matrices 100 6 5 10
Market data analysis (Segmentation, KJ, etc.) 80 3 3 7
VOC/VOB/VOT/VOR assessment and prioritization 80 2 2 7
Critical Parameter identification through HOQ & Hazard Analyses 90 0* 0* 8
Design Concept Exploration and Selection (Pugh) 50 0* 0* 8
System Tree / Functional Tree / Risk Tree Creation and Linkage 100 0* 0* 9
Bottoms-up FMEA, Mitigation, and Control Plan Management 80 0* 0* 7
1st Eng. Principle Computation and Transfer Functions 60 0* 0* 10
Critical Parameter Flow-down and Design Prediction Flow-up 90 0* 0* 10
Statistical Variation Target Assessment / Scorecard Reporting 60 0* 0* 9
Design of Experiments and Test Management 90 5 5 7
Product Cost Estimation and Initiative Management 80 0* 0* 8
Imp. DOORS ReqPro COCKPIT
3180 2710 9710
We suggest that a full evaluation should include a lot more than baseline functions
Look at your development deliverables and add your own additional items
* function not supported
-
8/3/2019 Cognition Requirements Management
34/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Would you benefit from the Cockpit?
Intuitive user interface for easy adoption by all project personnel 100 4 5 9
100% Browser based for ALL actions (read/write) 90 2 2 10
Ease of Customization to Meet SOP Template Deliverables 100 2 1 10
Ease of integration with SolidWorks, Goldfire, Windchill 70 2 1 9
Imp. DOORS ReqPro COCKPIT
920 850 3430
If you have a Requirements Management system, you mayobserve the following:
Fewer people than expected are willing to use it.
Updating data has been assigned to a small group of peoplewho can handle the complexity of the tool.
You spend an enormous amount of time administering links
and traces. Regarding ease of use and deployment:
-
8/3/2019 Cognition Requirements Management
35/71
Copyright 2010 Cognition Corporation http://www.cognition.us
So, what specifically is different about the Cockpit?
-
8/3/2019 Cognition Requirements Management
36/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
Risks
Mitigations
DocumentationSub Reqs
Attachments
Tests
Action ItemsParent Reqs
The Cockpitprovides a supersetof functionality
handling the needsof hardware,software, and
process groups.
-
8/3/2019 Cognition Requirements Management
37/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
Risks
Mitigations
DocumentationSub Reqs
Attachments
Tests
Action ItemsParent Reqs
The Cockpitruns entirely in
your Webbrowser and
users actuallyenjoy using it.Everything is
connected andeverything has
a Dashboard.
-
8/3/2019 Cognition Requirements Management
38/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Unified Model for Product Development
Where the lines are even more important than the circles.
Cockpit - a unified model for product development
The Cockpit is a
Unified Model forcapturing, tracing, and
managing all theproduct developmentdata of your projects.
C
-
8/3/2019 Cognition Requirements Management
39/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
Engineering
Test/QualityRisk/Reliability
Marketing
Unified Model
Just like email,everyone is pluggedin. Changes in the
RequirementsDocument are
propagated to theother departments
and change
notifications aredirectly visible.
C k i ifi d d l f d d l
-
8/3/2019 Cognition Requirements Management
40/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Flowing-down customerrequirements and Risk
Mitigation into product &process design (specs& drawings)
MarketSpec
ProductSpec
AssemblySpec
ComponentSpec
ProcessSpec
MarketSpec
ProductPerformance
AssemblyPerformance
ComponentPerformance
ProcessCapability
Proposal Definition ValidationDevelopment
Product Spec Design Freeze Design VerificationMarket Spec
Cockpit - a unified model for product development
Flowing-up processcapability & predicted
performance up tocustomer requirements
VOC, RM, Risk and Critical Parameter functions are all needed.
Its all connectedin the Cockpit
C k i ifi d d l f d d l
-
8/3/2019 Cognition Requirements Management
41/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
For example, VOCmanagement is critical to
delivering a market success.
C k it ifi d d l f d t d l t
-
8/3/2019 Cognition Requirements Management
42/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Capturing and analyzing yourmarket research data is fully
supported in the Cockpit. You canimport interview survey data andlook for market segment trends
using the DataCube functionality
built into the Cockpit.
Cockpit - a unified model for product development
C k it ifi d d l f d t d l t
-
8/3/2019 Cognition Requirements Management
43/71
Copyright 2010 Cognition Corporation http://www.cognition.us
The Cockpits affinity grouping tool is an
electronic rendition of sticky notes. TheCockpit creates them, and your team groups
them by similarity. In the end, marketing has amuch better understanding of the dominant
customer needsand they also have a great
tool for communicating with engineering.
Cockpit - a unified model for product development
C k it ifi d d l f d t d l t
-
8/3/2019 Cognition Requirements Management
44/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Prioritizing customerneeds is also animportant part of
marketings
communication withengineering. Cockpit
templates offer anumber of voting
tools to do this.
Cockpit - a unified model for product development
C k it ifi d d l f d t d l t
-
8/3/2019 Cognition Requirements Management
45/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Flowing VOC requirements downmethodically into lower level SystemRequirements and further into Sub
System Requirements is fullysupported with best practice
methods. Shown here is a typical
QFD approach.
Cockpit - a unified model for product development
C k it ifi d d l f d t d l t
-
8/3/2019 Cognition Requirements Management
46/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
Pugh concept exploration usingCockpits templates is very
convenient. Here, four concepts arebeing evaluated against System
Requirements criteria definedearlier. And the weighting of the
criteria came from the QFD
template using VOC importance.
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
47/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Next, if you want to configure amaster trace of your own
design, you can click on thedetails page of any documentand define the columns the
way you want them.
Cockpit - a unified model for product development
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
48/71
Copyright 2010 Cognition Corporation http://www.cognition.us
And this is how it looks. Youcan then right click and createa template out of your settingsand other engineers can use it
at any time in their project.
Cockpit - a unified model for product development
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
49/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
In many projects, more than50% of the requirements are
mitigating risks of somekind. Managing risks and
requirements separately indifferent tools is not onlydifficult, but the source of
many compliance problems.In the Cockpit, they are
completely interconnected.
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
50/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
RQMT 3 Assy Failure 1 Component Failure 1 See Next Slide 0
RPN
PotentialCause(s)
OCC
Current Design orProcess Controls
DET
FunctionalRequirement
Potential FailureMode(s)
PotentialEffect(s)
SEV
RQMT 1 Failure 1 Assy Failure 1 Possibly None 0
RPN
PotentialCause(s)
OCC
Current Design orProcess Controls
DET
FunctionalRequirement
Potential FailureMode(s)
PotentialEffect(s)
SEV
FMEA Level 3
RQMT 2 Assy Failure 1 Failure 1
Sub-Assy Failure 1
Possibly None 0
RPN
PotentialCause(s)
OCC
Current Design orProcess Controls
DET
FunctionalRequirement
Potential FailureMode(s)
PotentialEffect(s)
SEV
FMEA Level 2
Sub-Assy Failure 1
FMEA Level 1
The Cockpit supportsunlimited levels of risk
decomposition. Hazards,
harms, hazardoussituations, etc. are
completely supported, andlibraries of these items canbe stored and reused from
project to project.
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
51/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
And all risks are connected to
their mitigations and resultingcontrols (requirements).
Residual risk is calculatedautomatically and FMEA
reports for Design, Process,
Use, etc. are fully supported.
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
52/71
Copyright 2010 Cognition Corporation http://www.cognition.us
MarketSpec
ProductPerformance
AssemblyPerformance
ComponentPerformance
ProcessCapability
Proposal Definition ValidationDevelopment
Product Spec Design Freeze Design VerificationMarket Spec
Cockpit - a unified model for product development
Flowing-up processcapability & predicted
performance up tocustomer requirements
VOC, RM, Risk and Critical Parameter functions are all needed.
In addition to risk mitigation, a largenumber of requirements exist
because they are critical to qualityor product performance.
For a Requirements Managementsystem to be helpful to the entire
organization, it must support
numeric requirements as well asallow the analysis of their statisticalvariation and predicted compliance.Cockpit is the only tool supportingthis, yet it is critical to achieving
predictable quality.
There are two approaches to design
-
8/3/2019 Cognition Requirements Management
53/71
Copyright 2010 Cognition Corporation http://www.cognition.us
There are two approaches to design
Simple MarginCalculation
= X %
NOMINAL APPROACH:
STATISTICAL APPROACH:
Upper Limit TargetCurrent
Value
A simple, yet statistical approachallows us to predict short and longterm product performance and manufacturing capability.
SufficientMargin
Good Design
NotSufficientMargin
Bad Design
A simple margincalculation does not tellus enough about the design.
Variation is
the root of allevil. DFSS
Principle
Corporate wide RM Systems must provide more
-
8/3/2019 Cognition Requirements Management
54/71
Copyright 2010 Cognition Corporation http://www.cognition.us
And Savings Opportunities
(over-design)
CPMExposes
Performance
Risks
Xs
Ys
Ys
Critical Parameter Management (CPM) is the analytic capability of
predicting product performance by statistically assessing the impactof lower-level design variation all the way up to customer experience.
Design
Corporate-wide RM Systems must provide more
CPM exposesdesign risks andopportunities.
Cockpit a unified model for product development
-
8/3/2019 Cognition Requirements Management
55/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
For example, therequirement shall be
between .09 and .17inches. Yet, the
current predicted
value is .1325 +/-.05026which is aproblem. If we knowthis early, we can fix
it more cost
effectively.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
56/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
So, in addition to the customer target for each
requirement, there is also an assessment of thecurrent specified or predicted design value. The
Cockpit computes this value throughout thedevelopment process using transfer functions,
which are then reported in scorecards or stoplight
charts used to make decisions and tradeoffs.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
57/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit - a unified model for product development
The Cockpit then usesits parent/child
linkages to predictwhich lower level sub-
requirements most
contribute to theproblem, as well aswhich higher level
requirements will beaffected by a resulting
design change.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
58/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
Time consuming and expensive design of
experiments (DOEs) are often performed inorder to predict performance. Cockpit
supports electronic DOEs and Monte Carloanalyses directly. It also links with Crystal Ball,Mini-Tab, Excel and other tools. Ask your team
if they do these analyses.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
59/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
The Cockpit allows
engineers to see when theirdesigns are getting more
robust. Similarly, they showwhen items are over-
designed and therefore
more costly than necessary.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
60/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
So, whether youre asking Risk, VOC, CPM, V&V, or Requirement relatedquestions, the Cockpit connects them all. Its Dashboard feature allows
engineers and managers to see everything that is connected to anyparticular item, including verification tests, risk mitigations, parent and sub
requirements, action items, notebook entries, and where-used
documentation. With this info, impact analysis is made a lot quicker
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
61/71
Copyright 2010 Cognition Corporation http://www.cognition.us
And finding data is important also.The Cockpit incorporates bothhardware and software support
for fast searching. Users cansearch for items in the Cockpit in
the same way they search forlawn mowers.
Cockpit a unified model for product development
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
62/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
For example, lets say you want to
find all requirements for a particular subject:
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
63/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Everything you put in the Cockpit
will be automatically crawled and indexed each night.(with a supplied Google Appliance on your network, not public)
Every piece of research,
every interview, every VOC,
every requirement, every specificationevery test, every protocol and V&V plan,
every risk, hazard, mitigation, PowerPoint, Visio,Excel, meeting minutes, marketing document, business plan,
characterization study, etc.
The next morning and for months and years thereafter,
you will have sub-second retrieval of all of it.
Cockpit a unified model for product development
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
64/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Everything you put in the Cockpit
will be automatically crawled and indexed each night.(with a supplied Google Appliance on your network, not public)
Every piece of research,
every interview, every VOC,
every requirement, every specificationevery test, every protocol and V&V plan,
every risk, hazard, mitigation, PowerPoint, Visio,Excel, meeting minutes, marketing document, business plan,
characterization study, etc.
The next morning and for months and years thereafter,
you will have sub-second retrieval of all of it.
Cockpit a unified model for product development
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
65/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
Lastly, managing Meetings Minutes
and Action Items is also unified insidethe Cockpit. We know you have other
tools for this, but if you use theCockpit, you can have direct linkages
between your data and the
meetings/actions that discuss them.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
66/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Cockpit a unified model for product development
Need Cockpit Others
VOC Management X
Requirements Management X X
Test Management (V&V) X
Critical Parameter Mgt X
Risk Management X
Functions cannot be isolated;department tools cannot be isolated;and your requirements cannot be isolated.
The Cockpit is the one system thatbrings them all togethersatisfying the needs of
your hardware, software and process development groups.
In the end
Where, ease of use andease of deployment arekey: One environment
One database One interface One price One installation One partner
Our conclusion
-
8/3/2019 Cognition Requirements Management
67/71
Copyright 2010 Cognition Corporation http://www.cognition.us
Companies need a Single Unified Model that handles all of it asystem for capturing, tracing, and managing all the product
development data of their world.
Companies need a Single Unified Model that handles all of it asystem for capturing, tracing, and managing all the product
development data of their world.
Ou co c us o
Single Unified Model
Where the lines are even more important than the circles.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
68/71
Copyright 2010 Cognition Corporation http://www.cognition.us
DevelopmentProject
Marketing
SystemsEngineering
SubjectMatterExperts Design
Standards/Regulations
Quality
SupplyChain
MFG
Risk
FinanceUsers
p p p
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
69/71
Copyright 2010 Cognition Corporation http://www.cognition.us
RIGHT PRODUCT
QUALITY/PERFORMANCE
TIME TO MARKET
COMPLIANCE
We address:
With the Unified Model, where: Everything is connected
Everything is indexed
Everything is templated
p p p
The Cockpit is the go-to place for product development
-
8/3/2019 Cognition Requirements Management
70/71
Copyright 2010 Cognition Corporation http://www.cognition.us
p g p p p
A major competitive advantage.
Cockpit - a unified model for product development
-
8/3/2019 Cognition Requirements Management
71/71
p p p
Start with a pilot.
Your users will embrace it like nothing youve seen before.
Cognition Corporation213 Burlington Road, Suite 109
Bedford, MA 01730http://www.cognition.us
781-271-9300 x241
http://www.cognition.us/http://www.cognition.us/