Cockpit - a unified model for product development

Parent Reqs Action Items Mitigations

Tests

Risks

In a Web 2.0 world, requirements should not be isolated. Documentation Attachments VOCs, Hazards, FMEAs, mitigation Sub Reqs plans, tests, test methods, protocols, critical parameters, action items, etc., everything can Copyright 2010 Cognition Corporation http://www.cognition.us be unified.

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.

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
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 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
Copyright 2010 Cognition Corporation http://www.cognition.us

Single System where everything is connected in a Unified Model

Users will want to use it

* International Council on Systems Engineering

Requirements Management in the Cockpit

Like most other Requirements Management tools on the market, Cockpit allows you to import requirements from multiple external sources such as Excel, Word, XML, ReqPro, DOORs, etc. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

This is a typical Requirements Document in the Cockpit. It is a dynamic page produced from data in the database. It supports requirement creation, editing, reviewing, approving, markups, spell-checking, etc. This format is tabular in style, but you can have any format you like. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

At the top of each document, there is an Export command. When clicked, the Cockpit produces a Word document, identical to the on-line version. Headers, footers, table of contents, images, tables, etc. are all supported properly.
Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Copyright 2010 Cognition Corporation http://www.cognition.us

Privileging in the Cockpit is fully supported. Pick any item: requirement, document, folder, project, etc. and select 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

Copyright 2010 Cognition Corporation http://www.cognition.us

Configuration management is supported in the Cockpit. This is true at all levels: item, document, folder, and project levels. The state transition is shown above, but basically, versions are baselined and revisioned as needed and each time an Approval process may be invoked.

Requirements Management in the Cockpit

Visual differencing is also supported. Clicking on the Diff command at the top of the page will open a new window with redlines for deleted text, green for newly added text, and so on. All versions of a document may be compared Copyright 2010 Cognition Corporation http://www.cognition.us in this way.

Requirements Management in the Cockpit

From a higher perspective, such as the Project level, differences can also be tracked. To start, a project is baselined, and thereafter, multiple working versions can be created and further baselined. A complete audit of new, deleted, and modified items is retrieved from the projects history page.
Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Flowing down top level requirements into lower level subsystem/component requirements is completely supported. Trace matrices are automatically generated and change (stability) notices are propagated through the requirement hierarchy. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Whatever you are trying to model in the Cockpit, you can create a breakdown for it. In this case, the Cockpit is being used to create a use-case model. Additionally, the Cockpit has a bi-direction link with Microsofts Visio product. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Next, the Requirements Management functionality in the Cockpit is directly connected to its Verification and Validation functionality. The V&V Plan, for example, is very efficient to create, because templates allow requirements written earlier (in the PRD) to be automatically included. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Subsequently, allocating requirements to tests is also supported. Many to many relationships can be captured, either through clicking allocation matrices or through many other supported means in the Cockpit. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Again, traceability is one of the Cockpits greatest strengths. Getting a tabular trace from requirements to tests or vice versa is a simple mouse click. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Writing Test Protocols in the Cockpit is also supported. Templates can be tweaked to comply with your format and any number of sections can be defined, such as setup, acceptance criteria, execution steps, Copyright 2010 Cognition Corporation http://www.cognition.us results, etc.

Requirements Management in the Cockpit

Copyright 2010 Cognition Corporation http://www.cognition.us

The Cockpit will auto-populate the acceptance criteria section for you. How? Earlier, you linked tests and requirements togetherand the Cockpit can use those links to fill out this section. If there are changes to the requirements, they will be reflected in this document as well.

Requirements Management in the Cockpit

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. Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

The Cockpit allows you to define multiple execution milestones for the tests in any protocol, for example Prior to Clinical, Prior to Submission, etc. All the text you write can be general or milestone specific and you can reuse/toggle the document to correspond to the test milestone you are performing.

Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

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 presented clearly. 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

Again, efficiency is important. If youre having 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.

Copyright 2010 Cognition Corporation http://www.cognition.us

Requirements Management in the Cockpit

Finally, to support quick decisions and review, Cockpit has many builtin reports showing the current status of items: for example, test coverage, number of failures, etc. These reports can be run from any level, such as document, folders, or project level. Copyright 2010 Cognition Corporation http://www.cognition.us

So, how does the Cockpits baseline capabilities compare to other Requirements Management systems?

Copyright 2010 Cognition Corporation http://www.cognition.us

Baseline Requirements Management Features

We believe you should review each of your Requirements Management tool choices. INCOSE (International Council on Systems Engineering) has a reference available comparing many vendors. The link below will take you to the full report, and weve included a subset of that report in the next few slides.
Copyright 2010 Cognition Corporation http://www.cognition.us

INCOSE TOOLS SURVEY

Copyright 2010 Cognition Corporation http://www.cognition.us

Copyright 2010 Cognition Corporation http://www.cognition.us

Copyright 2010 Cognition Corporation http://www.cognition.us

Copyright 2010 Cognition Corporation http://www.cognition.us

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...

Copyright 2010 Cognition Corporation http://www.cognition.us

Trouble
The trouble is that traditional systems are not doing the job.

Copyright 2010 Cognition Corporation http://www.cognition.us

The selection criteria needs to be broader

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:
Traditional Software-centric Criteria And Hardware/Process-centric Criteria

Traditional Requirements Management has evolved from software-centric needs focused on careful documentation and traceability Textual Reqs & Specs Textual V&V Tests Trace Matrices

Modern Requirements Management is driven by the additional goals of achieving lean execution of the full Product Development 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 Copyright 2010 Cognition Corporation http://www.cognition.us

Would you benefit from the Cockpit?

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
Imp. DOORS
10 10 6 3 2 0* 0*

ReqPro
8 8 5 3 2 0* 0*

COCKPIT
10 10 10 7 7 8 8

Textual Requirement/Specification Definition Textual Validation Tests Broad PDP Trace Matrices Market data analysis (Segmentation, KJ, etc.) VOC/VOB/VOT/VOR assessment and prioritization Critical Parameter identification through HOQ & Hazard Analyses Design Concept Exploration and Selection (Pugh)

100 70 100 80 80 90 50

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 / Scorecard Reporting Design of Experiments and Test Management Product Cost Estimation and Initiative Management

100 80 60 90
60 90 80

0* 0* 0* 0*
0* 5 0*

0* 0* 0* 0*
0* 5 0*

9 7 10 10
9 7 8

* function not supported

3180

2710

9710

Copyright 2010 Cognition Corporation http://www.cognition.us

Would you benefit from the Cockpit?

If you have a Requirements Management system, you may

observe the following: Fewer people than expected are willing to use it. Updating data has been assigned to a small group of people who can handle the complexity of the tool. You spend an enormous amount of time administering links and traces. Regarding ease of use and deployment:
Imp.
Intuitive user interface for easy adoption by all project personnel 100% Browser based for ALL actions (read/write) Ease of Customization to Meet SOP Template Deliverables Ease of integration with SolidWorks, Goldfire, Windchill 100 90 100 70

DOORS
4 2 2 2

ReqPro
5 2 1 1

COCKPIT
9 10 10 9

920

850

3430

Copyright 2010 Cognition Corporation http://www.cognition.us

So, what specifically is different about the Cockpit?

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Parent Reqs Action Items Mitigations

Tests

Risks

The Cockpit provides a superset of functionality handling the needs of hardware, software, and process groups.

Attachments Sub Reqs

Copyright 2010 Cognition Corporation http://www.cognition.us

Documentation

Cockpit - a unified model for product development

Parent Reqs Action Items Mitigations

The Cockpit runs entirely in Tests Risks your Web browser and users actually enjoy using it. Everything is Attachments connected and Documentation Sub Reqs everything has a Dashboard. Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Unified Model for Product Development

The Cockpit is a Unified Model for capturing, tracing, and managing all the product development data of your projects.

Where the lines are even more important than the circles.
Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Marketing

Engineering

Just like email, everyone is plugged in. Changes in the Requirements Document are propagated to the other departments and change notifications are directly visible.
Risk/Reliability

Unified Model

Test/Quality

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Proposal
Market Spec

Definition

Development
Product Spec Design Freeze Design Verification

Validation

VOC, RM, Risk and Critical Parameter functions are all needed.

Market Spec Product Spec

Flowing-down customer requirements and Risk Mitigation into product & process design (specs & drawings)

Flowing-up process capability & predicted performance up to customer requirements

Assembly Spec Component Spec Process Spec

Its all connected in the Cockpit

Market Spec Product Performance Assembly Performance Component Performance Process Capability

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

For example, VOC management is critical to delivering a market success.

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Capturing and analyzing your market research data is fully supported in the Cockpit. You can import interview survey data and look for market segment trends using the DataCube functionality built into the Cockpit. Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

The Cockpits affinity grouping tool is an electronic rendition of sticky notes. The Cockpit creates them, and your team groups them by similarity. In the end, marketing has a much better understanding of the dominant customer needsand they also have a great tool for communicating with engineering. Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Prioritizing customer needs is also an important part of marketings communication with engineering. Cockpit templates offer a number of voting tools to do this. Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Flowing VOC requirements down methodically into lower level System Requirements and further into Sub System Requirements is fully supported with best practice methods. Shown here is a typical QFD approach. 2010 Cognition Corporation http://www.cognition.us Copyright

Cockpit - a unified model for product development

Pugh concept exploration using Cockpits templates is very convenient. Here, four concepts are being evaluated against System Requirements criteria defined earlier. And the weighting of the criteria came from the QFD template using VOC importance. Corporation http://www.cognition.us Copyright 2010 Cognition

Cockpit - a unified model for product development

Copyright 2010 Cognition Corporation http://www.cognition.us

Next, if you want to configure a master trace of your own design, you can click on the details page of any document and define the columns the way you want them.

Cockpit - a unified model for product development

And this is how it looks. You can then right click and create a template out of your settings and other engineers can use it at any time Copyright 2010 Cognition Corporation http://www.cognition.us in their project.

Cockpit - a unified model for product development

In many projects, more than 50% of the requirements are mitigating risks of some kind. Managing risks and requirements separately in different tools is not only difficult, but the source of many compliance problems. In the Cockpit, they are completely interconnected.
Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

FMEA Level 1
Functional Requirement Potential Failure Mode(s) Potential Effect(s) Potential Cause(s) Current Design or Process Controls

OCC

RQMT 1

Failure 1

Assy Failure 1

Possibly None

FMEA Level 2
Functional Requirement Potential Failure Mode(s)

OCC

The Cockpit supports unlimited levels of risk FMEA Level 3 decomposition. Hazards, harms, hazardous Potential Potential Current Design or Potential Failure Functional Effect(s) Cause(s) Process Controls Mode(s) Requirement situations, etc. are See supported, and completely Next Slide 0 Assy Failure 1 Sub-Assy Failure 1 Component Failure 1 RQMT 3 libraries of these items can be stored and reused from project to project. Copyright 2010 Cognition Corporation http://www.cognition.us
OCC RPN SEV DET

RQMT 2

Assy Failure 1

Failure 1

Sub-Assy Failure 1

Possibly None

RPN 0

SEV

DET

Potential Effect(s)

Potential Cause(s)

Current Design or Process Controls

RPN 0

SEV

DET

Cockpit - a unified model for product development

And all risks are connected to their mitigations and resulting controls (requirements). Residual risk is calculated automatically and FMEA reports for Design, Process, Use, etc. are Copyright 2010 Cognition Corporation http://www.cognition.us fully supported.

Cockpit - a unified model for product development

Proposal
Market Spec

Definition

Development
Product Spec Design Freeze Design Verification

Validation

VOC, RM, Risk and Critical Parameter functions are all needed.

In addition to risk mitigation, a large number of requirements exist because they are critical to quality or product performance. For a Requirements Management system to be helpful to the entire organization, it must support numeric requirements as well as allow the analysis of their statistical variation and predicted compliance. Cockpit is the only tool supporting this, yet it is critical to achieving predictable quality.

Flowing-up process capability & predicted performance up to customer requirements

Market Spec Product Performance Assembly Performance Component Performance Process Capability

Copyright 2010 Cognition Corporation http://www.cognition.us

There are two approaches to design

NOMINAL APPROACH:
Simple Margin Calculation Current =X%
Value

A simple margin calculation does not tell us enough about the design. STATISTICAL APPROACH:

Upper Limit Target

A simple, yet statistical approach allows us to predict short and long term product performance and manufacturing capability. Good Design
Sufficient Margin

Variation is the root of all evil. DFSS Principle

Bad Design
Not Sufficient Margin

Copyright 2010 Cognition Corporation http://www.cognition.us

Corporate-wide RM Systems must provide more

Critical Parameter Management (CPM) is the analytic capability of predicting product performance by statistically assessing the impact of lower-level design variation all the way up to customer experience.
CPM Exposes Performance Risks
Ys

Design

CPM exposes design risks and opportunities.

Ys

Xs

And Savings Opportunities (over-design) Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

For example, the requirement shall be between .09 and .17 inches. Yet, the current predicted value is .1325 +/.05026which is a problem. If we know this early, we can fix it more cost Copyright 2010 Cognition Corporation http://www.cognition.us effectively.

Cockpit - a unified model for product development

So, in addition to the customer target for each requirement, there is also an assessment of the current specified or predicted design value. The Cockpit computes this value throughout the development process using transfer functions, which are then reported in scorecards or stoplight charts used to make decisions Copyright 2010 Cognition Corporation http://www.cognition.us and tradeoffs.

Cockpit - a unified model for product development

The Cockpit then uses its parent/child linkages to predict which lower level subrequirements most contribute to the problem, as well as which higher level requirements will be affected by a resulting design change.

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Copyright 2010 Cognition Corporation http://www.cognition.us

Time consuming and expensive design of experiments (DOEs) are often performed in order to predict performance. Cockpit supports electronic DOEs and Monte Carlo analyses 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

The Cockpit allows engineers to see when their designs are getting more robust. Similarly, they show when items are overdesigned and therefore more costly than necessary.2010 Cognition Corporation http://www.cognition.us Copyright

Cockpit - a unified model for product development

So, whether youre asking Risk, VOC, CPM, V&V, or Requirement related questions, the Cockpit connects them all. Its Dashboard feature allows engineers and managers to see everything that is connected to any particular item, including verification tests, risk mitigations, parent and sub requirements, action items, notebook entries, and where-used documentation. Copyright 2010 Cognition Corporation http://www.cognition.us lot quicker With this info, impact analysis is made a

Cockpit - a unified model for product development

And finding data is important also. The Cockpit incorporates both hardware and software support for fast searching. Users can search for items in the Cockpit in the same way they search for lawn mowers.

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:

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

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 specification every 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.

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

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 specification every 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.

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Copyright 2010 Cognition Corporation http://www.cognition.us

Lastly, managing Meetings Minutes and Action Items is also unified inside the Cockpit. We know you have other tools for this, but if you use the Cockpit, you can have direct linkages between your data and the meetings/actions that discuss them.

Cockpit - a unified model for product development

In the end
Functions cannot be isolated; department tools cannot be isolated; and your requirements cannot be isolated. The Cockpit is the one system that brings them all togethersatisfying the needs of your hardware, software and process development groups.
Need Cockpit

VOC Management
Requirements Management Test Management (V&V) Critical Parameter Mgt Risk Management

X
X X X X

Where, ease of use and Others ease of deployment are key: One environment X One database One interface One price One installation One partner

Copyright 2010 Cognition Corporation http://www.cognition.us

Our conclusion
Companies need a Single Unified Model that handles all of it a

system for capturing, tracing, and managing all the product development data of their world.
Single Unified Model

Where the linesare even more important than the circles. Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Users Marketing

Finance

MFG Systems Engineering

Development Project
Supply Chain

Risk Quality Subject Matter Experts Design Standards/ Regulations

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

With the Unified Model, where:

Everything is connected Everything is templated

Everything is indexed

We address: RIGHT PRODUCT COMPLIANCE TIME TO MARKET

QUALITY/PERFORMANCE

Copyright 2010 Cognition Corporation http://www.cognition.us

The Cockpit is the go-to place for product development

A major competitive advantage.

Copyright 2010 Cognition Corporation http://www.cognition.us

Cockpit - a unified model for product development

Start with a pilot. Your users will embrace it like nothing youve seen before.

Cognition Corporation 213 Burlington Road, Suite 109 Bedford, MA 01730 http://www.cognition.us [email protected] 781-271-9300 x241

Copyright 2010 Cognition Corporation http://www.cognition.us