Cognition Cockpit System Administrator...

System Administrator Guide

Cognition Cockpit, version 5.2February 2009

Copyright © Cognition Corporation, 2009All Rights Reserved

COGNITION COCKPITTM

C O R P O R A T I O N

Cognition Cockpit System Administrator Guide - February 2009

This document, as well as the software described in it, is provided under the terms of Cognition Corporation’s Program License Agreement (PLA), which sets forth Cognition’s sole warranty.

COGNITION CORPORATION DISCLAIMS ALL OTHER WARRANTIES EITHER EXPRESS OR IMPLIED, INCLUDING ALL WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILL COGNITION CORPORATION BE LIABLE FOR CONSEQUENTIAL DAMAGES EVEN IF COGNITION HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE WARRANTY AND REMEDIES SET FORTH IN SAME ARE EXCLUSIVE AND IN LEIU OF ALL OTHERS.

Except as permitted by license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form by any means without the prior written permission of Cognition Corporation.

Use of this document is reserved exclusively for Cognition’s customers, potential customers, and personnel. The information and graphics contained herein are the sole property of Cognition and shall not be divulged to any third party without prior written permission of Cognition.

The information in this document is subject to change without notice. Cognition assumes no responsibility for errors that may appear in this document, although every effort has been made to ensure correctness.

Knowledge Center is a registered trademark of Cognition Corporation.Cognition Cockpit is a trademark of Cognition Corporation.

Adobe Acrobat is a registered trademark of Adobe Systems Incorporated.BasicScript is a registered trademark of Summit Software.InstallShield is a registered trademark of InstallShield Corporation.iPlanet is a trademark of Sun Microsystems, Inc.Microsoft, Windows, and Windows XP are registered trademarks of Microsoft.Microsoft Word and Microsoft Excel are either trademarks or registered trademarks of Microsoft.MATLAB is a registered trademark of The MathWorks, Inc.Minitab is a registered trademark of Minitab, Inc.ObjectStore is a registered trademark of Progress Software CorporationWOS is a trademark and Work Object System is a registered 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.

Published and printed in the USA.

Cognition Corporation 213 Burlington Road, Suite 109 Tel 781-271-9300 Email [email protected] Bedford, Massachusetts 01730-1468 Fax 781-271-0813 Internet http://www.cognition.us

System Administration

Overview

Cognition Cockpit Site AdministrationThe Cognition Cockpit will need to know something about its users before they can login and begin to use it. The purpose of the site setup is to allow the admin-istrator or lead user to create user accounts, define groups, set permissions, and perform other customizations that are specific to your company.

AssumptionsThe following instructions assume that:

• You have installed the Cognition Cockpit and that the KC Web Portal is running. If not, please see the Cognition Cockpit Installation Guide.

• You have Internet Explorer (version 6 or later) with network access to the web portal.

• You know the names and other relevant data about the users, groups and customizations that you’ll be adding to the system.

Getting StartedThere are many features to the Cockpit, but initially you’ll be most interested in:

• Logging In• Entering Site Setup• Adding Users• Configuring Login Settings• Adding User-Defined Attributes

Following that, you may want to explore other areas of site preferences and customizations that are covered in this book.

Cognition Cockpit System Administrator Guide - February 2009 1

http://www.cognition.us/download/files/cockpit/docs/Cockpit_Installation.pdf

Logging In

The first step is for you, the administrator or a lead user, to log into the Cognition Cockpit. To begin, open an Internet Explorer browser and enter the following address:

http://HOSTNAME/Cockpit

where HOSTNAME is the host on which the KC Web Portal is running. For example, if the web portal host name is Engineering1 you would enter:

http://Engineering1/Cockpit

If the web portal has been set up to use a port number other than the default value of 80, you should enter:

http://HOSTNAME:PORT/Cockpit

where PORT is the port number. For example, if the web portal host name is Engineering1 and the port number is 8080, you would enter:

http://Engineering1:8080/Cockpit

You should see a page that includes the login region:

Enter the administrator name (the default is admin) and the administrator pass-word in their respective fields. The person that performed the installation specified the administrator name and password during installation (see step 12, page 12 in the Cognition Cockpit Installation Guide). You can also log in as a user that has been granted the Administrator privilege (see “Privileges” on page 25).

2 Cognition Cockpit System Administrator Guide - February 2009

http://www.cognition.us/download/files/cockpit/docs/Cockpit_Installation.pdf

Logging In

Once login has completed, the system will display your home page (“My Stuff”), which will look similar to the following:

You can enter more information about the administrator here simply by clicking on any field (either the existing text or the dimmed “Enter value...” placeholder) and typing a new value. After entering new text, you can press Tab or Enter to go to the next field or click in a blank space to complete the edit. Changes are made immediately; there’s no need for a save or submit button.


Entering Site Setup

All system-wide configuration is done in the area called Site Setup. To begin setting up the site, click on the “Main Menu”:

Choose “Site Setup” to enter the setup mode.


Entering Site Setup

The main page for site setup provides access to additional pages that allow you to specify the site preferences, define users and groups, set permissions, create process templates, and perform other customizations.

The following sections cover each of these areas. You can watch a brief video introduction to the site setup features by viewing the tutorial. Click the Tutorials link at the upper right of the Cockpit screen as shown below.

Expand the Administration entry at the bottom of the table of contents at the left of the screen and click on the Site Setup link to view the tutorial.


Site Setup

The main page for Site Setup provides access to information about active and inactive sessions, and allows you to run some system-wide reports.

Home Page

The home page provides tools for managing active and inactive sessions.

Active Sessions. This section lists all sessions that are currently active (logged in). If a session was somehow terminated abnormally, for example if the server crashed, you can manually terminate it here. Terminating a session for a user who is currently logged in will not log out the user. The terminate command should only be used if the user is no longer logged in.

Inactive Sessions. This section lists all past sessions that are no longer logged in. You can delete old session records that are no longer needed.


Site Setup

Reports Page

The reports page provides access to several system wide reports:

Daily User Count Report. This report will display a calendar indicating the number of users of the Cockpit for each day within a specified date range.

Error Report. This report will display a log of all errors that took place in the specified date range.

Project/User Report. This report will display the number of projects and users in the Cockpit and list basic information about each member.

Usage Report. This report will display all Cockpit usage that took place in the specified date range.


Site Preferences

This area of the site setup allows you to specify preferences that apply globally to your Cockpit installation. They allow you to configure the Cockpit to match the way your company works. To change the Site Preferences, click on the entry in the table of contents and the main window will show the General preferences, as shown below.

General PageThere are a number of sub-areas covered by the general page. You can expand or collapse a subsection by clicking on the subsection name or the small triangle to the right of its name.

Workflow States. This section is used to define the possible workflow states. The default states area includes states for all item types. States specific to any group in a group structure and states for sections of a document can also be defined here. All other item specific states are defined on the page for that type.

Versioning Preferences. This section is used to control whether Approvals are included in the item versioning process and whether or not to show the navigation control when differencing Cockpit document versions.

Document Formats. Use this section to select which documentation formats will be available when creating documents. Some of these formats simply provide formatting of the items in the document section while others provide guidance in the development process.

Notification Preferences. Use this section to indicate whether notifications should be done as part of the version approval process. If notifications are to be sent by email, the mail server information must be provided in order to send email notifications. Notifications are sent when an item’s status is changed to Approved.

ECM Search Domains. If the Cockpit installation also includes the Enterprise


Site Preferences

Cost Management option, use this section to define cost domains that can be searched through to find similar cost estimates.

File Storage Preferences. Use this section to specify whether documents should be stored internally or externally, and if they are stored externally, where they should be placed. Use of external storage is recommended if you anticipate that the documents will be more than one gigabyte in aggregate; it is required if they will amount to two or more gigabytes.

Research Preferences. Use this section to define the web query to make when using the research tool.

Default System Preferences. Use this section to note if you are using a version of Microsoft Office from 2000 or earlier.

Default User Preferences. Use this section to define the default preferences to be assigned when creating new users.


Voices Page

Importance Range. The importance range values are used to define the minimum and maximum VOC importance. These values are also used to deter-mine the normalized scores for requirements when calculated from the VOC importance. The site preference specifies the default importance for new projects, but each project can have its own importance range.

VOC Auto Numbering. The auto numbering section determines if new items are automatically assigned a unique ID number, a prefix value to the number, and a suffix for the number. The site preference specifies the default value for new projects and then each project can have its own settings.

Workflow States. This section is used to define the possible workflow states that are specific to Voices.


Site Preferences

Requirements Page

Thresholds. The thresholds section is used to define when a requirement is reported as red, yellow, green, or blue. These values only apply if the satisfaction is being tracked on a requirement. There are separate threshold values depending on the type of metric. The thresholds can be overridden at the project level and also on a specific requirement.

Sigma Range. The sigma range is used to determine the standard deviation when upper and lower limits are entered for a value. The standard deviation is calculated as:

(Upper_limit - Lower_Limit)/(2 * Sigma_Range).

Workflow States. This section is used to define the possible workflow states that are specific to Requirements.

Documentation Preferences. Use this section to specify whether requirements must be documented. If checked, the requirement will show a red Needs docu-mentation note in all trace reports that include the requirement, unless the requirement is part of a document.

Requirement Display Mode. Check this option to indicate that a requirement is to be shown with X and Y icons, where Y is an output requirement and X is an input requirement. If the box is not checked, the icon code is either "R" for a high level requirement or "S" for a lower level specification. If this box is checked, specifi-cation type requirements will be shown with an X or Y icon instead of an S icon.

Requirement Metric Types. Requirement metric types are used to classify a requirement so it can be shown as a specific value on a group or structural element. Cost and Weight are the two metrics provided out of the box as these are common metrics for any structure. Metrics can be displayed as columns in a multicolumn structure view and can also be automatically derived from the sub-elements in a structure. The calculation can be a summation or product of the sub-metrics including a quantity multiplier. Also, in the summation case the parent can add its “own” value to the summation of the subitems.


Confidence Levels. Confidence levels are an indication of the accuracy for a specific metric value. A default set of values is provided for all metrics, but metric specific confidence levels can be added for any metric type.

Technical Risk Levels. The first house of quality results in a requirement score based on the voice importance and the impact of the voices on the requirement. In addition, technical risk levels can be assigned with a value and a description. The value is multiplied by the house of quality score to get a score that includes both importance and difficulty.

Data Sections. Each requirement can have any number of data sets (or sections) associated with it. You define the default project data sections here and specify on what requirement types each section will be shown. There are four types of data sections that can be defined:

• Target – Target value for the requirement• Design – Design data including a mean and standard deviation. These

values can be calculated with a transfer function.• Process – Same as design.• Test – This is a place to enter results from testing. It is not derived but

entered separately for each requirement.

Project specific data sections can be defined once a project has been created.

Requirement Types. Use this section to define the allowable requirement types. The columns in the table are:

• Type – This is a unique, short code used to identify the requirement type. Predefined Cockpit types start with COG.

• Type Name – This is the name that will be shown to choose or indicate the current type.

• Availability – This indicates whether new requirements of the type can be created. Disabled types can still exist in the system, but you cannot create or change to disabled types.

• Prefix / Suffix – These are prefix and suffix text that are displayed with the ID number of the requirement.

• Icon Code – This must be either R for a high level requirement, S for a sub-requirement or specification, or N for a noise parameter. Additional codes may be supported in a future release. Only requirements with the R icon code can be associated with customer voices.

• Valid Data Types – This indicates the data types that are valid for the requirement type.

Requirement Auto Numbering. Requirements are always assigned an ID. This section determines the starting number and the increment for new IDs. It also


Site Preferences

specifies how and if the ID is displayed on the requirement. The site preference specifies the default value for new projects and then each project can have its own settings.

Notification Preferences. Check this box if you want to notify parent and child requirement owners when approving a requirement with a value change. Notifi-cations must be enabled and the mail server configured on the General page for this to take effect.


Risks Page

Workflow States. This section is used to define the possible workflow states that are specific to Risks.

Severity Levels. This section allows you to choose the allowable severity levels for risks or failures. For each level specify a numeric value, a name, and a help description.

Probability Levels (Occurrence). This section is used to specify the rating, name, and help text for each of the allowable probability levels for risks or fail-ures. There are five predefined levels and you can add more or remove those that are not needed. For the risk matrix to work properly, the number of probability levels must match the number of severity levels.

Color Settings. Specify whether to use a simple color change based on the risk score (severity * probability) or use a risk matrix. For the simple method you will need to enter the score thresholds for a yellow display and a red display. If using a risk matrix, you choose a color value for each cell of the risk matrix.

Score Settings. Specify whether to calculate the score based on multiplying the severity and probability or to use a risk matrix. If the matrix is used, a score value must be entered for each cell of the matrix.

Risk Auto Numbering. The auto numbering section determines if new items are automatically assigned a unique ID number, a prefix value to the number, and a suffix for the number. The site preference specifies the default value for new projects and then each project can have its own settings.

Mitigation Auto Numbering. The auto numbering section determines if new items are automatically assigned a unique ID number, a prefix value to the number, and a suffix for the number. The site preference specifies the default value for new projects and then each project can have its own settings.


Site Preferences

Tests Page

Workflow States. This section is used to define the possible workflow states that are specific to Tests.

Test Auto Numbering. The auto numbering section determines if new items are automatically assigned a unique ID number, a prefix value to the number, and a suffix for the number. The site preference specifies the default value for new projects and then each project can have its own settings.

Documentation Preferences. Use this section to specify whether tests must be documented. If checked, the test will show a red Needs documentation note in all trace reports that include the test, unless the test is referenced in a document.


Users & Groups

The Users & Groups portion of site setup is the area devoted to creating and managing Cockpit users and groups of users. Expanding this item in the table of contents reveals the user groups, their members, and any users that are not members of any group.

Selecting a user or group displays the home page for that item and these are covered in the following pages. The menu for Users & Groups (shown by right-clicking on Users & Groups in the table of contents) includes commands for creating new users and groups, importing and exporting users and groups from or to Microsoft Excel, and configuring login settings. The latter requires further explanation.

Configuring Login Settings

The Configure Login Settings command is used to choose how user logins are authenticated. There are two options: Internal Login uses the Cockpit’s database entry for the user and their password to validate a connection. LDAP Login uses your system’s directory services to validate the user’s credentials.

LDAP Configuration The LDAP Login choice presents several additional fields that must be completed to configure Cockpit to use this protocol.

Auto Create. If you check this box, a Cockpit user is automatically created (if need be) upon successful LDAP login. This saves you from having to explicitly pre-create all potential Cockpit users. Further, if you have created a user group with the name “Default Users,” new users created this way are automatically assigned to this group and are granted the permissions and access rights of the group.

Server Host. The name of the computer running the LDAP server.

Port. The port number for communication with the LDAP server. The default value is 389 and is rarely changed.

LDAP Type. Choose whether to use Windows Active Directory or iPlanet Direc-tory Server.

Use Encryption. Leave this box checked to use Kerberos encryption during transmission. The server must support encryption; if not, uncheck this box.


Users & Groups

There are additional fields when the LDAP Type is the iPlanet Directory Server.

Bind Format. This option is only displayed if a search for the bind format is not required. In this case, enter the bind format required to authenticate the user. The default bind string used when connecting to the LDAP server is:

uid=%user%, DC=DOMAIN_2, DC=DOMAIN_1

where:

• %user% is the name of the user entered in the Cockpit login box.• DOMAIN_1 is the last part of the fully qualified domain name (e.g., for cognition.us it would be “us”)

• DOMAIN_2 is the second part of the fully qualified domain name (e.g., for cognition.us it would be “cognition”)

If the default string does not work for your LDAP server, you can use any string with a %user% in it and the Cockpit will replace the %user% with the actual user name and pass that bind string to the LDAP server.

Search for Bind DN. Check this option if your LDAP server does not validate the user directly. This will search for a Bind DN based on the user name and a Base DN. The base DN is usually based on the domain (for example, “dc=cognition,dc=us”).

Search Filter. This specifies the filter to use when a search must be done for a Bind DN.

Bind DN for Search. The attribute to search for (“DN” is a special case and returns the “distinguished name” for the query).

Search Requires Authentication. Check this option if the search requires an admin user name and password. Enter the user name and password required for the search.

Username. The user name if search requires authentication.

Password. The password if search requires authentication.


Home PageThe home page for Users & Groups is where you add new Cockpit users to the system and define user groups to aid in assigning privileges. Groups are generally recommended for privilege assignment as it makes management much easier as users come and go.

Adding Users Users. Displays a table that lists all the users defined in the Cockpit. You can click on a user to see details for that user. Click on the menu icon in the upper left corner to add new users or modify the display of the table. In order for the menu icon to appear, the cursor must be within the borders of the table.

Choose Create New from the menu and then fill in the user’s name, password, and other info. Click done to create the user and have it added to the table:

Click on a user to go his or her home page where you can edit information about the user, view messages and action items, and much more. See “User” on page 19.

User Groups. Displays a table that lists all the user groups defined in the Cockpit. You can click on a group to see details for that group. Click on the menu icon in the upper left corner to add new groups or modify the display of the table.

Some common groups created by project teams include: engineering, marketing, operations, and core team leaders. Having an Administrators group can be handy if there are multiple people responsible for administration of the system.


User

User

The user pages provide access to everything there is to know about a Cockpit user. Each user is a unique person in the database who may be assigned to one or more projects. Users are assigned privileges to control their level of access to each project.

Home PageThe home page for a user is where you go to update information entered when the user was created or to add additional information such as phone numbers. You can also view, add or remove messages and action items for the user.

Messages. Displays the messages for the user. Here you can change the status, delete old messages, send new messages, and so on.

Action Items. This section includes all the action items that are related to this specific person. Action items are useful for assigning tasks to users such as “Obtain new quote from supplier for this item.” Action items have a due date, level of importance, expected level of effort, and other related fields.


Action Items PageThe action items page lets you view and create action items for users of the project. Each action item is associated with a particular item in the project (for example, a certain parameter) and with a particular person on the project team.

Action items are tracked by due date, completion status, importance, and expected level of effort.

See the prior page for a description of Action Items and Messages.


User

Traceability PageThe Traceability page is one of the most powerful pages in the Cognition Cockpit. It shows the connections that the user has with his or her surrounding world.

Use the traceability page to explore how the user interacts with other items in the project. Use the traceability page to create and study the many connections between items in a project.

View Graphically. Click this link to switch to the FlexEdit view mode. This is a very powerful mode for many users because it gives them a more meaningful visual representation of the data than the traditional table and tree modes.

Voices. Voices associated with this user.

Requirements. Requirements associated with this user.

Risks. Risks associated with this user.

Mitigations. Mitigations associated with this user.

Tests. Tests associated with this user.

Groups I Am In. Groups that this user currently belongs to.

Groups I Can Manage. Groups that this user can manage, that is, groups for which this user can create and modify the user members.


Reports Page

Available Reports. This section lists all of the reports that can be run on this user item.

Attachments Page

Attachments owned by User. List the attachments that are associated with the user. From here, the user can navigate to an attachment to view it, change it, etc.


User

Preferences PageThe Preferences page shows the user specific preferences. Here, the user can choose what the system should show upon login, what information the system should display for products, defaults to use when the user creates an item, and much more.

Login. This section allows the user to choose what the system should show when he or she logs in. The user can choose between the last project he or she was working with, to show a specific project, or even a specific report in a project.

Interface. This section allows the user to specify if the system should automati-cally complete variable names when he or she is editing formulas. This is off by default because automatic completion can be expensive in a large project.

My System Preferences. This section allows the user to inform the system if he or she is using a version of Microsoft Office that is version 2000 or older.

Product Information Displayed. This section allows the user to control what information about products to display. Not all users are interested in all aspects of a product; using this section allows the user to narrow the display to just those areas that he or she is interested in. There are a number of check boxes that control whether the system should display voices, requirements, critical parameters, risks, tests, and so on.

Default Privileges and Ownership. This section allows the user to instruct the system whom to make the owner of an item (project, requirement, etc.) when the user creates that item. The user can also specify to whom the system should addi-tionally grant view and/or modify privileges when the user creates a project, attachment, or transfer function.

Messages. This section allows the user to specify if email should be used for sending messages and if the “new message” indicator should be displayed when the user has a new message. The new message indicator is an alternate My Stuff icon when a message is waiting.


User Group

You can organize a project team into various user groups. This is useful when you want to assign project privileges based on group membership. Some common groups created by project teams include: engineering, marketing, operations, and core team leaders.

User groups are hierarchical. That is, a user group can be a member of another group, just as a user can be. You can add users and/or groups to a user group via the menus in the Team Members or User Groups section. Alternatively, you can add existing users and/or groups to a user group by dragging and dropping in the table of contents.

Home PageThe home page displays the name and description of the group, which can be edited. In addition, there are sections listing the user and group members of this group.

Team Members. This section lists the users that are members of the group. The menu provides commands for adding new users or assigning other existing users to the group. You can also remove users from a group here.

User Groups. This section lists the groups that are members of the group. The menu provides commands for adding new groups or assigning other existing groups to the group. You can also remove groups from a group here.


Privileges

Privileges

Home PageThe privileges item facilitates the management of access rights. Here you can see the privileges that have been granted to each user and user group. You can click on the check boxes in the matrix to assign or remove particular rights.

Create Project. Users need this privilege in order to be able to create new projects. Without the Create Project privilege, users can only access existing projects based on their privileges within each project. The commands to import a project and copy a project also require this privilege.

ASE Builder. This is a special privilege that allows users to create and modify site customizations. Normally, customizations are done only by a user who has been trained in adding customizations to the Cockpit.

Administrator. The Administrator privilege gives a user full access to everything in the Cockpit. An administrative user can create or modify users and has full access to all projects in the Cockpit. You should be very selective as to which users are given the Administrator privilege.


Process Templates

This area of site setup is used to define process templates that are globally avail-able and can be used in any project. There can also be project specific processes. A process template defines specific steps and procedures that can be used to guide your team through a project. Once templates are created here, they are available when adding a process in a project.

The menu for Process Templates in the table of contents has a command for creating a new process templates. Once you have a process template, its menu provides commands for adding phases (such as “Concept”) and for adding tasks or activities. Phases and tasks can be hierarchical.

The order of phases can be modified simply by dragging the icon of the phase that you want to reorder to a new location in the list. The same is true for activities.

Home Page

Process Templates. This section lists your existing process templates. The menu allows you to create additional templates, just as in the table of contents. Click on any template item to go to its home page.


Process Template, Phase, Task

Process Template, Phase, Task

Home PageThe home page for a process template, phase, and task are essentially identical.

The name of the item is shown, and below that is a drop list with choices for the type of the item. An item’s type can only be changed to a lower level type. That is, a process template can be changed to a phase or activity, and a phase can be changed to an activity.

Detailed Description. The detailed description can contain simple text or a combination of rich text and graphics. Click the Edit button to display a rich editor used to format and modify the detailed description.

Phase Entry Questions. This section lists the questions that should be answered before work begins on this particular phase or activity. Answering these questions ensures that all prerequisites for starting the task have been completed.

Phase Exit Questions. This section lists the questions that should be answered before work on this particular phase or activity can be considered to be complete. Answering these questions helps verify that all aspects of the phase or task have been performed and you are ready to move on to the next stage.


Customizations

The customizations area of site setup has numerous subcategories that allow you tailor the look of many areas of the Cockpit, add custom attributes to items, create templates for email, and much more.

Most of these areas require advanced training and are beyond the scope of this manual, however, the following pages explain how to create custom attributes, one of the most frequently implemented customizations.


Attribute Definitions


Creating a custom attribute, also known as a user-defined attribute (UDA), is a data related customization. A custom attribute allows you to extend the informa-tion about items in the Cockpit to contain additional fields that your company considers important. These attributes can be of different data types, such as strings, numbers, dates, and so on. You can specify what it applies to, such as Voices, Requirements, Risks, and many others. You can even specify the allow-able values. Once you have defined a custom attribute, it can be utilized in searches, reports, and most other areas that the built-in attributes can be referenced.

Adding User-Defined Attributes

To create a custom attribute, navigate to the Attribute Definitions subfolder beneath the Data Related folder.

Home PageSelect the Attribute Definitions folder to display its home page. Initially, there are no custom attributes.


To add a user-defined attribute, click on the menu in the table (or right click on the folder in the table of contents) and choose the command Create New (Create a new UDA in table of contents). The system presents the following form for you to fill in.

As an example, the following shows how to add an Importance value to a Require-ment. Fill in the form as shown:

Some points to keep in mind:

• Name – this must be a single alphanumeric string with no spaces. This restriction facilitates its use in formulas and other database operations.

• Description – this can be anything you want, but be aware that this text is shown in the table of contents, so you probably don’t want it to be too long.

• Type – this can be one of five possible values: String, Integer, Real, Boolean, or Date.

• Class – this can be one of over two dozen choices that cover nearly all aspects of Cockpit data, from persons and groups through voices, require-ments, and tests. There are even some meta-data choices, such as All Project Data Items.

Click done when you have finished entering the data. The system will display the new attribute in the table.



Click on the new UDA in the table or in the table of contents. The system displays the home page for the new attribute.

Here you can edit the UDA’s name and description. You can enter a default value if appropriate, and specify whether the values are restricted, and if so, in what way.

To continue the example, the following shows how to restrict the Importance value to be in the range from 1 to 10.

1. Click on Range Limited. The system displays additional choices.

2. Enter 1 as the Lower Limit.

3. Enter 10 as the Upper Limit.



Date post:	12-Jun-2018
Category:	Documents
Upload:	lamanh
View:	226 times
Download:	0 times

Cognition Cockpit System Administrator...

Documents