Cognition Cockpit

Version 5.1

Release Notes

June 20, 2008

Copyright © Cognition Corporation 2008

This document is an internal reference specification that is the sole property of Cognition

Corporation and is not to be distributed outside of Cognition without Cognition s express

permission. Use of this specification is reserved exclusively for Cognition s personnel

and sales and marketing partners. The information and drawings contained herein are the

sole property of Cognition and shall not be divulged to any third party without prior

written consent of Cognition. The information in this specification is subject to change

without notice.

Copyright © 2008 by Cognition Corporation. All rights reserved.

Knowledge Center is a registered trademark of Cognition Corporation.

BasicScript is a registered trademark of Summit Software Company.

ObjectStore is a registered trademark of Progress Software Corporation.

Internet Explorer, Visual C , Windows, Windows XP, and Windows 2000 are trademarks

or registered trademarks of Microsoft Corporation.

Work Object System is a trademark of Process Dynamics, Inc.

General Notice: Some of the product names used herein have been used for

identification purposes only and may be trademarks or registered trademarks of their

respective manufacturers and sellers.

Revision history:

1.0 June 20, 2008 Created

Published and printed in the USA.

Cognition Corporation 213 Burlington Road Suite 109 Bedford, Massachusetts 01730 781-271-9300

1.0 Introduction These release notes describe the enhancements and changes that are part of version 5.1 of the Cognition Cockpit. The major changes include:

• User Interface Improvements

• New options for defining and tracking requirements

• Improved status tracking capabilities for all items

• Introduction of costing within the Cockpit

• Additional analytical capability

The following sections define the detailed functional changes and any user interface that are associated with those changes.

There are also a number of bug fixes that are included as part of this release.

2.0 User Interface Improvements A number of changes have occurred in the user interface to improve the organization of information, making regularly edited items more accessible and providing additional summary information.

2.1 Improved Filtering

The availability of the different Cockpit features can be adjusted to only show those areas that are used. User preferences (with site-wide defaults), control the visibility of the major Cockpit functional areas.

Even when the functional areas are displayed, the availability of items (tables, reports, etc) on item pages is adjusted based on the real-time filter at the top of the window. The filters along the top of the data section (shown below) have been reduced to four topic areas.

Only those topic areas selected for the site and user appear as choices. The items in the tree and data on the pages are adjusted based on what real-time filter is set.

When all filters are off, the system displays the product structure information only.

2.2 Page Reorganization

With this version, the look of the pages has been changed to organize the pages into more obvious sections. Each section now has a clear header that allows you to expand the section, or make the section occupy the entire page.

In addition, requirement and group home page sections have been reorganized to make readily used information more prominent and provide more direct access to children (e.g. Sub requirements).

2.3 Summary Results

Tables have an option to group items by a specific characteristic, available on this section title bar. The available choices are based on the type of items contained in the table.

When items are grouped, the tables automatically display as Pareto graphs based on the characteristic they are grouped by. The items in each group can be displayed by selected the group (e.g. 'Green' in the table below).

2.4 New Page Layouts

New layouts are available to control the location and orientation of the table of contents and data pages. These layouts can be selected from layout control on the right side of the application title bar.

Layouts now include options like a horizontal table of contents, or two tables of contents.

2.5 Multicolumn Table of Contents

The table of contents can now be set to show multi-column data. This is useful when doing tasks like building a costed bill of materials, or otherwise adding attributes to the tree.

The available table layouts are based on what type of item is currently visible at the top of the tree. So, for example, when a group is hoisted to the top of the tree, there are Cost and Weight metric tables available by default. To set the table style, pick the table style control allowing the left edge of the table of contents. Selecting 'Description Only' will turn off the multi-column format.

Below is an example of a horizontal table of contents with the Cost Metrics table style applied. The table allows in-place editing of the fields.

2.6 In-place creation in tables

Adding new items in a table is easier to do, with in-place item creation. Where available, new items can be added by simply typing the item description in the 'Add new...' field as shown below. The new items are created with default values.

3.0 New options for defining and tracking requirements New options are available to improve the definition of requirements and tracking of approved changes. These include the ability to define custom requirement types, to specify confidence levels on values, and to track approved items above and below in the tree.

3.1 Requirement Types

The system administrator can now define new requirement types. The existing requirement types from prior versions of Cockpit are automatically available.

New types are defined via the Requirements tab in the Site Preferences, as shown below.

For each type, the following can be defined:

• Type - a short code for this type

• Type name - the display name for this type

• Availability - this controls whether or not this type is currently available as an option, allowing unused types to be turned off

• Prefix/Suffix - these are used in generating the ID string for the requirements

• Icon Code - this controls what type of icon should be displayed for items of this type (e.g. R, S, X, or Y)

• Valid data - each type can restrict what type of user input is allowed for the target and value of the requirement

A number of new predefined requirement types have been added, including Features, Functions, and Use Cases.

Project Setup can be used to control what data sections each requirement type has available. For example, Features might define several target sections, but no design sections, while component specifications might have no targets. An example of the setup is show below.

3.2 Confidence Levels

When specifying a design or process result for a numeric requirement, a confidence level for the estimate can now be specified. By default the available confidence levels are Low, Medium, High, Actual, but these can be customized via Site Setup. Different confidence level options can defined for different types of metric. For example, cost requirements might use terminology like that below that better capture the estimate type.

For derived values, the confidence level shows as 'Derived'.

3.3 Approval Tracking

When using a working version of a project, an additional version control option is available, Accept for Approval. By default, users with modify access can approve an item using this command:

When this approval occurs, the Cockpit provides the option to send out automatic notifications to the owners of parent and/or child requirements. These notifications are sent when changes occur to the requirement targets or design values. This preference is set on the Requirements page of the Site Preferences, using the option show below:

If this preference is set and a requirement is approved, parent or child requirements will display Stability Notices that shows what the source of the instability is, when the change occurred, and what the change was.

After any impacts of this change are resolved, the stability message can be cleared by clicking the 'Accept' box.

3.4 Enhanced Convergence Reporting

Trends of requirement values and targets can be plotted via the Cockpit using the Convergence Report. This can display the value of a requirement or the current statistical metric used for the project (Cpk, PNC, Z, or DPMO).

The value and target can be plotted against either specified versions, a date range, or specified data sections.

A sample plot of value vs. versions is shown below.

4.0 Workflow Status Workflow status can now be specified for most items in the Cockpit.

The default workflow states are:

New, Accepted, Clarify, Duplicate, Rejected, Started, Waiting, Halted, Tested, Completed, Planned, Approved, Discarded

These default states can be changed to reflect a different workflow process.

4.1 Configuring the Workflow Status

These default states can be changed on the General Page of the Site Preferences, as shown below:

The state name, description and help test can be changed for existing states (note that changing a state name will not update existing consumers of that name). In addition, new states can be created and existing ones removed.

These workflow states can be overridden for different types of items. Structures, Documentation, Voices, Requirements, Risks, Mitigations, and Tests can all have their own unique set of workflow states. If no states are specified for these items, the default values are used.

4.2 Setting Workflow Status

The workflow status can be set in the Status section on the home page of each item (or on the Details page for Documentation).

It can also be set via the large icon at the top of the items page (shown below).

4.3 Grouping Items by State

For requirement tables and option is available to group the items by workflow status. Clicking on the 'group' option on the right side of the section header provides as option group the table by a particular characteristic.

When grouped by status, a table like that below is displayed, providing a summary Pareto.

5.0 Metrics With this version, requirements can now be classified by 'metric' type in addition to requirement type. The metric classification is used to identify all requirements that have to do with a particular product characteristic, like cost, weight, efficiency, etc. Identifying items in this way allows the system to recognize that special relationships may exist between requirements and subrequirement, including providing automatic transfer function definition.

5.1 Metric Definitions

Metric types can be configured on a system-wide basis, and specified for any numeric requirement. The metric definitions are set up on the Requirements page of the site preferences.

For each metric, in addition to the type, there are choices to define:

• If different confidence levels should be used for this metric

• A default calculation that should be used for items of this type

When creating a new numeric requirement, there is an option to select a metric type for the requirement.

After the requirement is created, the metric type can be changed in the 'Value Settings' section on the Details page.

5.2 Automatic Formulas

When a calculation type is defined at the Site level for a metric type, formulas will be automatically generated to calculate these items when there are items of the same type in subordinate groups.

Even when there is no automatic generation, built-in calculations can be assigned to the items. The available built-in calculations are shown below.

When there is a built-in calculation (either automatically or manually defined), the formula is automatically maintained when structural

changes occur. If a metric is defined for a subordinate group (a child group of the current metrics primary group), this metric will automatically get inserted into the current automatic formula.

This automatic formula maintenance eliminates much of the work required to maintain the transfer function when there are structural changes.

5.3 Metric Tables

In addition to automating the maintenance of the analytical relationships between requirements, identifying items as particular metric type allows these items to be shown together in a table.

The system has two built-in tables, for Cost Metrics and Weight Metrics. These tables allow you to view the structure and update the metric values without needing to display them in the tree.

New cost metrics are automatically created as needed when values are entered for the Target or Unit cost values.

6.0 Cost Analysis Significant capability has been added to integrate cost information with other product performance characteristics. The internal capabilities of the Cockpit have been enhanced to allow quantity to be defined and summation roll-ups to be automatically defined. In addition to this capability, an interface to Cognition's Enterprise Cost Management (ECM) system is now available. This integration allows more sophisticated costing to be performed by cost experts in ECM and made available to Cockpit users.

6.1 Cost Metrics

As part of version 5.1, a Cost metric type is automatically defined in the Cockpit. This type is configured with an automatic calculation, such that cost parameters are based on the sum of their subordinate costs (based on the product structure) time quantity. The calculation also allows for an adjustment to the derived value, described in the 'Own Cost' section below.

In addition, there is a built-in Cost Metrics table that allows cost information to be added directly in a view of the product structure.

6.2 Quantity

In order to allow the cost of an assembly to account for the number of each subordinate part, quantity of a part in its next higher assembly is now available in the Cockpit. The quantity parameter is automatically created as needed by a cost calculation. The quantity is available as a special parameter in the system that is always numeric in type. The default quantity is automatically assigned to be '1'.

Quantity parameters share many common characteristics of other parameters, including being able to take on different values for different designs with the project. So, if there are two design data sections 'Design' and 'Alternate Design', different quantities can be assigned to each, and used in calculating the results for that cost (or other metrics).

6.3 Own Value

When the built-in formula "Sum of subordinate metrics (with Qty and Own value) is used, an additional field is available for the current value(s) of the requirement. In addition to the derived value, an editable value is available. When the derived value is calculated for this requirement, the own value is added into the calculation automatically. This is the default calculation used for Cost metrics, so that typically:

Cost = Own_Cost + Qty_1 * Cost_1 + ... + Qty_n * Cost_n

where Qty_i and Cost_i are the subordinate metrics.

6.4 Enterprise Cost Management Integration

Enterprise Cost Management is a stand-alone cost management solution developed by Cognition. Access to cost data developed in ECM by cost professionals is now available within the Cockpit, either as search results or directly driving cost requirements.

6.4.1 Connecting ECM Domains

Multiple ECM domains can be configured to be available to search for cost information. New domains are configured via the General Site Preferences.

6.4.2 Search for Costs

When ECM Search domains are available, the Cockpit Search feature

allows access to Cost information as a search result.

Searches can be performed by part description or part number, and can be executed in a specific ECM domain or across all available domains.

6.4.3 Cost Transfer Functions

In addition to searching for cost information, cost data can be used for directly feed the current values for requirements. This is done via the ECM transfer function. An ECM transfer function is added via the calculation menu for a numeric requirement.

Either a new ECM transfer function can be created, or an existing one can be reused.

When creating a new ECM calculation, the host, domain, ECM project and scenario need to be specified. Either current user credentials or specified credentials can be used.

Whether creating a new transfer function or reusing an existing one, a part number in the ECM system is used to acquire the cost information.

7.0 Analytical Enhancements

7.1 Transfer Function Reuse

With this version there is an option to reuse an existing Excel or Matlab transfer function from the project or from the system-wide library. Formulas can also be copied from the system-wide library.

7.2 Monte Carlo Analysis

Monte Carlo analysis has been reintroduced with version 5.1. It is available on any derived requirement. To run an analysis, simply select the requirement in the table of contents and right click to access the Monte Carlo command.

A choice of data sections is available, along with control over the Monte Carlo execution.

Upon completion, Monte Carlo results are automatically displayed in another window, as shown below.

7.2.1 Entering Distribution Information

By default, requirements use a normal distribution based on the tolerance information associated with value. However, this can be overridden to change the distribution type or parameters. This additional data is available by clicking on the "(more)" link next to name of the value section. This displays the additional information that can be set for the value, as shown below.

7.2.2 Displaying Monte Carlo Results

A summary of the Monte Carlo results is maintained for later examination, even after the analysis window is closed. This can be accessed for a derived requirement by clicking on the "(more)" link next to the value section.

7.3 Sandbox Analysis

A new analysis capability has been introduced with version 5.1 to allow quick 'what-if' simulations to be performed without updating all the information in the requirements tree. To create a new 'Sandbox' for experimenting with the inputs for a requirement, right click on a derived requirement and choose 'Sandbox Analysis'.

In the subsequent dialog (shown below), select the data section to analyze.

The system will then construct a temporary simulation tree based on the current values of all inputs. The available inputs and their initial assumptions are displayed in a new window.

A default variation (as a percent of nominal) can be assumed for those items that don't have an explicit one. Nominal values can be adjusted as desired, without updating the stored values in the system. Then, a Monte Carlo analysis can be conducted to see the impact of the inputs.

The results for the select item and any subordinate derived values are shown in the Sandbox window.

After completing an analysis, any changes to inputs that want to be maintained, can be saved back to the requirement by pressing the disk icon next to the input.

8.0 SPRs fixed with this Release There are numerous individual fixes in this release. A number of these are shown in the tables below.

8.1 Page Definitions

Need to fix the requirements sections on the Group home page 31197

Margin and Statistical value section should be moved to the bottom of the requirement home page 31228

Need to add a "Sub-Requirments" section on the Requirements home page 31247

8.2 Table of Contents Changes

Hoist and Unhoist icons need to be cleaned up 31073

If all filters are off, still show the structure 31062

No longer place the item name in "edit" mode when it gets inserted into the tree. 31170

Folders show requirement section when requirement filter is off, but should not 31243

Create options in site setup for default user preferences for what capabilities are visible 31215

Allow moving a requirement from folder under a group to directly under a group 30708

When risk and test capabilities are turned off, the commands to create them still appear 31214

Need additional information of Requirement Creation dialog 31173

When entering requirements in the table, they should pick up the last type created 31259

Change in TOC to longer ‘flashlight’ through subitems when filters are disabled

8.3 Table View

Need a mechanism for making the TOC display in a table view 30967

would like a custom report that shows parameters in columns 30318

8.4 Cost Management

Allow users to specify part number while "reusing" ECM transfer functions. 31187

Need cost owner listed on ECM TF with change and notify buttons 31183

Need Basic search for costs 31145

Need to add ECM transfer function into Cockpit 31042

Need inputs table for ECM transfer function 31166

Need to add ECM cost search from Cockpit 31041

Add ability to create automatic transfer functions that contain quantity 30922

Allow quantity to be captured and roll up quantity based metrics 30307

Add Cost Maturity to cost table 31150

Allow two values per derived value, both intrinsic and calculated value 30950

Need Contribution Summary window for summation requirements 31167

Cost and Weight metrics need to be added during migration 31272

8.5 New Customizable Requirement Types

Add support for concept of a feature 30802

Would like to support a "Product Feature Requirement" in for use in HOQ 29563

8.6 Requirement Status/Approval Tracking

Provide notification to neighboring requirements when requirements are approved

29865, 29958, 30371, 30370,

30369

Enable status tracking automatically when creating numeric metrics 31109

Allow an expected date of Green (or completion) for a given requirement 30998

Use new default Cpk (and other statistical metrics) red and yellow defaults. For Cpk, show red for less than 1.0, and yellow for less than 1.5 30997

Allow PNC as one of the statistical satisfaction criteria. 29964

When the target is a single number for a numeric requirement, notify the user when producing status information. 30594

8.7 Transfer Functions and Analysis

Support getting Excel transfer functions from Compass 30328

Entering blank for a formula should delete the formula calculation 30984

Develop a new dependency analysis capability to allow improved what-if studies (Sandbox area) 30311

Allow Monte Carlo Analysis by data sections 30301

Prompt for the output cell when adding an existing Excel TF 31200

Editing and saving the active design value for an Excel TF input collapses the section, but should not 31237

Add transfer function library, allowing transfer functions to be organized for reuse with a project or between projects

30305, 27284, 27282, 30306,

27285

Built-in Formulas w/ automatic adjustments, changing a requirements metric type needs to cause it to reassess it's own calculation 31054

8.8 Attachments Need a way to view and organize attachments in a domain. Add an attachment library 30024

8.9 Terminology

Need to rename Surveys to Voice Inputs 31066

The "Project Setup" page is called "Project Preferences" 31264

Change term privileges to 'Access Rights' when picking items 31225

Change title of 'Value Status' gage section to just 'Satisfaction' 31231

Change the title of the 'Version Status' section to just 'Status' 31230

8.10 Import/Export

Allow importing of Pass / Fail requirements from Excel 31078

Importing from Excel doesn't use the X vs. Y setting, it creates Y's 30938

Adding a NEW input to excel using the excel input table should create a NUMERIC requirement type. 31151

Check VOC range as set on project during excel import 30929

Project teams need to be able to be exported/imported 30325

8.11 Markup

Adding a tag markup has problems 31087

Adding markup from body page gives error 31086

Removing a tag markup gives an error 31084

Trying to add a second tag icon thinks that I'm trying to edit the first 31083

Markups don't appear for Survey Events 30723

If a markup is associated with a delete item it breaks project list 30867

8.12 Site Setup Improvements Site setup should show users and groups in the table of contents. Users that are not in any group should appear directly under the Users & Groups folder 31288

Data sections on site preference has some issues 31174

8.12 Feedback

Pressing 'done' on any of the dialogs needs to give feedback that it's busy 31252

Editing a text field should show a busy cursor while the update is made

8.13 Requirement Status/Approval Tracking

Add notification (not colors!) when requirements are approved 29865

Need to know when items are approved above or below 29958

Add back approval and other notification messages 30371

Add indication of approval status above / below and make it a preference 30370

Add back ability to see requirement approval status reasons 30369

Enable status tracking automatically when creating numeric metrics 31109

Allow an expected date of Green (and/or completion) to be entered for a requirement 30998

New Suggested Cpk defaults from David Cronin 30997

Need PNC for satisfaction criteria. 29964

when the target is a single number for a numeric requirement, we should complain when producing status info 30594

8.14 Confidence Levels

Allow confidence level to be assessed for each design value 30949

8.15 Workflow Status

Items need a "Workflow State" field with customizable values 31234

8.16 Action Items and Messages

Need mechanism for messages 30886

Fix ‘My Stuff’ button to have a message indicator 31196

Add new notification states (action item states) 31142

8.17 Access Control/Privileging

Add a user to View, Modify, & Manage voices and they show up repeated many time on privilege report 31024

Need to be able to create users as a Group Admin in the Thin Client 30406

Can't currently set owner of an item to be a group 30991

Project Administrators should be allowed to add or remove items from project team 31152

Delete privileging is not correct for items with subitems 30576

Importing items from flex edit needs to be properly privileged 30566

User groups don't inherit privilege from project team properly in privilege tables 31209

On import, if project team has privileges, they can incorrectly get re-associated 30862

The view privilege should not get unchecked when the modify privilege is unchecked. 31202

8.18 Traceability Fixes Risks in traceability are duplicated under a group if they appear directly and under another item 30716

If a test appears under a requirement and directly under a group, it appears in trace twice 30715

Traceability report for survey questions don't show inputs associated with them 30711

Groups presented as linking option in trace page should not include documents 30906

Traceability report from requirement to group (breakdown) doesn't show all groups 30707

Trace Reports for Requirements-Documentation, Requirements-Groups, Requirements-Breakdown are not correct. 30917

8.19 Other miscellaneous fixes The action' column width for history report for individual item is too narrow 31193

Need to refresh history page after creating a new version 31178

History report on project shows the wrong display name for working versions 31172

Creating a noise factor does not create the correct requirement type 31287

Cannot change threshold values on the requirements detailed page 31292

When an item has been submitted for approval, the state message needs to indicate this 31191

Printing from FlexEdit hangs browser 30986

User Defined Attribute inheritance from a parent class doesn't work properly 31017

Requirement trace reports don't show proper ID for requirements 31033

Hide the custom value section on item home page if there are no items for this project 31229

Document folder associated with project needs to be added to the project version 30946

Confusing Refresh problem and a bug when adding Calculations via the details page for a requirement. 31154

Allow existing customizations to be renamed 31092

Customizations don't allow spaces in their names 31290

Refreshing table of inputs under Excel TF, when design values are changed results in refresh page/section error 31153

Hoisted object show not be remembered when switching projects 31280

Multiple problems updating Excel transfer function 31169

Team setup is not perfect 31126

Allow non alpha-numeric characters in password 31138

Link to parent or sub requirements should use L / M/ H for link type 31246

Don’t allow creation of two groups with same description under the same parent group. 31163

Requirements should have unique description in the scope of their primary group. 31162

Display the part number after group name in the qualified description 31205

Allow creation HOQ on subsystem w/o direct VOCs 30628

Display flex table command menus only appear when hovering over table 30963

Change migration to migrate all items in working versions when domain is migrated 29899

Copying a requirement and choosing not to copy subitems still copies them anyways 31254

The error handling for loading data back from flex edit isn't very pretty 30163

Create master version on a project is not setting both name and description 31171

Need to make sure the back button shows the correct information on the page 30463

Need a project level difference command between two project versions 30373

Several HOQ related bugs reported 30921

Allow drag and drop process steps in site setup or project 31217

Description names needs to be checked for uniqueness after cloning or copying. 31159

Creating a new master version needs to activate the new master 31180

Linking a voice to a voice input throws an error. 30958

The dynamic filter in the linker stops working in IE6 after the first link. 31255

Numbering problem while creating a new sub-section 30539

Need some custom search samples for requirements and parameters 30252