copyright otice€¦ · running a simple report ......

$: COPYRIGHT OTICE€¦ · Running a Simple Report ... Files\Starbase\CaliberRMPROExplorer\OnlineGuides\EN\BusinessObjects51EN.pdf. Components Minimum Recommended CPU PII 233MHz PIII$
I

CALIBERRM DATAMART & DATAMART EXPLORER USER GUIDE

COPYRIGHT NOTICE

Made In Borland® Copyright © 1998-2003 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners.

CORPORATE HEADQUARTERS

100 Enterprise WayScotts Valley, CA 95066-3249831-431-1000 www.borland.com

OFFICES IN:

Australia, Brazil, Canada, China, Czech Republic, France, Germany, Hong Kong, Hungary, India, Ireland, Italy, Japan, Korea, the Netherlands, New Zealand, Russia, Singapore, Spain, Sweden, Taiwan, The United Kingdom, and the United States.

Doc. #: R04IMR1202

Table of Contents

Chapter 1: Introduction ............................................................................................... 5Overview .....................................................................................................................5Your CaliberRM Datamart & Datamart Explorer Package ..........................................6Borland Support ..........................................................................................................6System Requirements .................................................................................................7

CaliberRM Datamart Extractor Server ....................................................................7Database Server (MS Access or MS SQL Server) .................................................8CaliberRM Datamart Extractor Server and Database .............................................8CaliberRM Datamart Explorer .................................................................................8

Product Documentation ...............................................................................................8

Chapter 2: Configuring Databases and Data Sources ............................................. 9Configuring Microsoft Access ......................................................................................9Configuring Microsoft SQL Server ............................................................................10

Configuring a Userid and Password in CaliberRM ................................................10Configuring MS SQL Server ..................................................................................11Configuring a System Data Source Name (DSN) .................................................12

Multi-Extraction Naming Conventions .......................................................................13

Chapter 3: CaliberRM Datamart................................................................................ 14Overview ...................................................................................................................14CaliberRM Datamart Configurator .............................................................................14CaliberRM Datamart Extractor ..................................................................................17

Examples of CaliberRM Datamart Extractor Command Line Interface .................18CaliberRM Datamart Synchronizer ...........................................................................18

Examples of CaliberRM Datamart Synchronizer Command Line Interface ..........19

Chapter 4: CaliberRM Datamart Explorer ................................................................ 21Overview ...................................................................................................................21Configuring the CaliberRM Datamart Explorer DSN .................................................21

For Microsoft Access: ............................................................................................21For Microsoft SQL Server: ....................................................................................22

Configuring the CaliberRM Datamart Universe Location ..........................................23Running a Simple Report ..........................................................................................24Getting Started in CaliberRM Datamart Explorer ......................................................24Opening a Report ......................................................................................................25Creating a New Query ...............................................................................................25

Table of Contents 3

Chapter 5: CaliberRM Datamart Explorer Reports.................................................. 29Attribute Distribution ..................................................................................................29Impact Analysis .........................................................................................................29Project Scorecard ......................................................................................................30Requirement Volatility ...............................................................................................30Status Summary ........................................................................................................30Traceability Complexity .............................................................................................30User Deployment ......................................................................................................31

Appendix A: Universe Parameters ......................................................................... 32

Appendix B: Report Samples ................................................................................. 41

Appendix C: Sample CaliberRM Datamart Extraction Times ............................... 45

Appendix D: CaliberRM Datamart Explorer Restrictions ..................................... 46

Glossary...................................................................................................................... 49

Index............................................................................................................................ 50

Table of Contents 4

Chapter 1: Introduction

OVERVIEW

CaliberRM Datamart & Datamart Explorer are Borland’s requirements-based decision support systems that allow advanced query and analysis of project requirements.

The products allow team members to review, correlate and compare requirement metrics data from multiple projects in their CaliberRM repository. This enables them to make informed decisions that influence project success.

CaliberRM Datamart & Datamart Explorer’s robust query and analysis capabilities are powered by BusinessObjects, the market-leading business intelligence solution from Business Objects. By incorporating BusinessObjects’ easy-to-use interface and proven technology into CaliberRM Datamart & Datamart Explorer, Borland provides users leverage within their requirement data so they can make sound business decisions.

There are two main components of CaliberRM Datamart & Datamart Explorer:

1. The CaliberRM Datamart – extracts data from the CaliberRM operational repository, transforms that data, and loads it into a relational database. The CaliberRM Datamart is comprised of the CaliberRM Datamart Extractor, the CaliberRM Datamart Configurator and the CaliberRM Datamart Synchro-nizer. It also contains two CaliberRM Datamart Explorer universes and two templates.

2. The CaliberRM Datamart Explorer – an integrated query and analysis environment powered by BusinessObjects.

As illustrated in the diagram on the following page, CaliberRM Datamart extracts data from CaliberRM operational database, transforms that data and then loads it into a relational database where it can be accessed by the CaliberRM Datamart Explorer.

Overview 5

YOUR CALIBERRM DATAMART & DATAMART EXPLORER PACKAGE

Please make sure your CaliberRM Datamart & Datamart Explorer package contains the items listed below. If any item is missing or damaged, please contact support. Contact information is given in the section below.

• CaliberRM CD-ROM

• Installation Guide

• License key

• A copy of the Software License and Limited Warranty Agreement

• A copy of the Release Notes

BORLAND SUPPORT

Borland offers a variety of support options. These include free services on the Internet, where you can search our extensive information base and connect with other users of Borland products. In addition, you can choose from several categories of support, ranging from support on installations of the Borland product to fee-based consultant-level support and extensive assistance.

Your CaliberRM Datamart & Datamart Explorer Package 6

For more information about Borland's support services, see our web site at http://www.borland.com/devsupport/. From the Web site, you can access many newsgroups where CaliberRM users exchange information, tips and techniques.

Refer also to the Borland Community site at http://community.borland.com. It provides access to lots of information, articles, code examples, and upcoming news about CaliberRM.

When contacting support, be prepared to provide complete information about your environment, the version of the product you are using, and a detailed description of the problem.

For support on third-party tools or documentation, contact the vendor of the tool.

SYSTEM REQUIREMENTS

Before installing CaliberRM Datamart & Datamart Explorer, please make sure your computer meets the following system requirements:

CaliberRM Datamart Extractor ServerIf CaliberRM Datamart Extractor is installed alone and the database is installed on another machine:

Components CaliberRM Datamart Caliber RM Datamart Explorer

Operating System Windows NT 4.0 (Service Pack 4 or higher) and Windows 2000

Windows NT 4.0 (Service Pack 4 or higher), Windows 2000 and Windows XP

Other CD-ROM CD-ROM

Microsoft Data Access Component (MDAC) 2.50, 2.52 or 2.60. MDAC 2.51 and 2.53 are NOT supported.

Components Minimum Recommended

CPU PIII 500MHz PIII 800MHz

RAM 250MB 512MB

Hard Drive N/A 125MB

System Requirements 7

Database Server (MS Access or MS SQL Server)If the database is installed alone and the CaliberRM Datamart Extractor is installed on another machine:

CaliberRM Datamart Extractor Server and Database If CaliberRM Datamart Extractor and the database are installed on the same machine:

CaliberRM Datamart Explorer

PRODUCT DOCUMENTATION

In addition to this document, you can find more detailed information on how to create reports in the BusinessObjects User Guide located where you installed CaliberRM Datamart Explorer. The default location is C:\Program Files\Starbase\CaliberRMPROExplorer\OnlineGuides\EN\BusinessObjects51EN.pdf.


CPU PII 233MHz PIII 500MHz

RAM 256 MB 512 MB

Hard Drive NA Dependent on database size


CPU PIII 800MHz Dual PIII 500MHz

RAM 512 MB 1 GB

Hard Drive NA Dependent on database size

Components Recommended

CPU 200 MHz Pentium or higher

RAM 128 MB

Hard Drive 150 MB

Other Drives CD-ROM

Product Documentation 8

Chapter 2: Configuring Databases and Data Sources

Before you can begin using the CaliberRM Datamart, you must first create and configure a data source name (DSN) and a database on the server the CaliberRM Datamart resides, if:

• during the installation process, you chose not to create a MS Access DSN and database,

• you need to create another MS Access database and DSN, or

• you want to use a Microsoft SQL Server database.

CONFIGURING MICROSOFT ACCESS

There are two steps to configuring Microsoft Access: creating a DSN, which also selects or creates the database.

To configure MS Access:

1. Open the control panel on the machine that will run the extraction program.

2. Double-click on ODBC Connections or Data Sources (ODBC).

Note: For Windows 2000, open the subfolder Administrative Tools, then ODBC Connections.

3. Select the System DSN tab.

4. Click Add. The Create New Data Source dialog box is displayed.

5. Select Microsoft Access Driver (*.mdb) from the list and click Finish. The ODBC Microsoft Access Setup dialog box is displayed.

6. Enter a name and description for the DSN.

Note: Borland recommends “RMMSA.” See the section “Multi-Extraction Naming Conventions” on page 13 for information on structure and naming conventions for multiple extractions.

7. To create a new database, click Create. The New Database dialog box is displayed. Go to Step 8.

OR

To open an existing database, click Select. The Select Database dialog box is displayed. Select the MS Access file and click OK. Go to Step 10.

8. Enter a name for the .mdb file and navigate to the location you want to save the file.

Note: Borland recommends you save it in a subfolder in the CaliberRM Datamart directory.

9. Click OK to exit the New Database dialog box.

10. Click OK to exit the ODBC Microsoft Access Setup dialog box.

Configuring Microsoft Access 9

11. Click OK to exit the Create New Data Source dialog box.

Your DSN and database are created. Proceed to “Chapter 3: CaliberRM Datamart” for information on configuring the CaliberRM Datamart.

CONFIGURING MICROSOFT SQL SERVER

There are three steps to configuring CaliberRM Datamart for Microsoft SQL Server:

• configuring a userid and password in the CaliberRM Framework Administrator,

• configuring the MS SQL server, and

• configuring the data source name (DSN).

Configuring a Userid and Password in CaliberRM1. In the CaliberRM Framework Administrator, create a new user that will be specific to CaliberRM

Datamart Explorer.

Note: The user id and password need to match the user id and password in MS SQL Server exactly.

2. On the Group Membership tab, assign the user to a group.

3. On the Password tab, assign the user a password.

Note: The userid and password are case sensitive.

Configuring Microsoft SQL Server 10

4. Click the Project View button to display project information. On the Group Assignment tab, assign the user to the group(s) and project(s) that are going to be extracted.

For more detailed instructions for creating a CaliberRM user, see “Chapter 5: Users and Groups” in the CaliberRM User’s Guide.

Configuring MS SQL Server1. Select Start > Programs > Microsoft SQL Server from the Windows Start menu to open the

Enterprise Manager.

2. Create a database in MS SQL Server.

Note: If you are unsure about how to create a SQL Server database, consult your Microsoft SQL Server documentation or SQL Server Administrator.

3. Create a SQL Server Login (user) in SQL Server that matches the user created in CaliberRM Datamart Explorer (same userid and password).

Note: If you are unsure about how to create a MS SQL Server Login, consult your Microsoft SQL Server documentation or MS SQL Server Administrator.

Note: The userid and password are case sensitive.

4. On the Database Access tab, ensure that the MS SQL Server user has public and db_owner access in the Database roles for section.

Note: For more detailed instructions for creating a MS SQL Server user, see your Microsoft docu-mentation or MS SQL Server Administrator.

5. Click OK. The user and database are created.

6. Exit the MS SQL Server Enterprise Manager.


Configuring a System Data Source Name (DSN)The system Data Source Name selects which database CaliberRM extracts.

To create a system DSN:

1. Open the control panel from the server that will run the extraction program.

2. Double-click on ODBC Connections or Data Sources (ODBC).

Note: For MS Windows 2000, open the sub folder Administrative Tools, then ODBC Connections.


4. Click Add. The Create New Data Source dialog box is displayed.

5. Select SQL Server from the list and click Finish. The Create a New Data Source to SQL Server screen is displayed.

Enter a Name, Description and select the SQL Server to which you want to connect. This should be the server that contains the SQL database.

Note: Borland recommends “RMMSSQL.” See the section “Multi-Extraction Naming Conventions” on page 13 for information on structure and naming conventions for multiple extractions.

Note: For MS SQL Server, the DSN name must include the letters “SQL.”

6. Click Next.

7. Select the With SQL Server authentication... option button.

8. Click the Client Configuration button. The Add Network Library Configuration dialog box is displayed.

9. In the Network libraries section, make sure the TCP/IP option button is selected.

10. Click OK.

11. Enter the userid and password that you created for CaliberRM and the MS SQL Server.

12. Click Next.

13. Select the Change the default database to check box, and select the SQL database from the list.

14. Click Next.

15. Click Finish. The ODBC Microsoft SQL Server Setup dialog box is displayed.

16. Click Test Data Source. When the test is complete, click OK.

Note: If the test does not respond, check with your MS SQL Server administrator to ensure the SQL Server is set up properly.

17. At the last setup box select OK, and at the ODBC box, select OK.

Your system DSN is created. Proceed to “Chapter 3: CaliberRM Datamart” for information on configuring the CaliberRM Datamart.


Nam*.ini Ln

Syst Ln

Univ Ln

*.md

SQL Ln

.bat (com

Ln

ConNamUniv

Ln

MULTI-EXTRACTION NAMING CONVENTIONS

It is recommended that you follow the following structure and naming conventions for multiple CaliberRM Datamart Explorer extractions.

First Extraction Second Extraction Third Extraction n Extractione Access SQL Access SQL Access SQL Access SQLfile RMMSA RMMSSQL RMMSA2 RMMSSQL2 RMMSA3 RMMSSQL3 RMMSAn RMMSSQ

em DSN RMMSA RMMSSQL RMMSA2 RMMSSQL2 RMMSA3 RMMSSQL3 RMMSAn RMMSSQ

erse file RMMSA.unv

RMMSSQL.unv

RMMSA2.unv

RMMSSQL2.unv

RMMSA3.unv

RMMSSQL3.unv

RMMSAn.unv

RMMSSQ.unv

b file RMMSA.mdb

N/A RMMSA2.mdb

N/A RMMSA3.mdb

N/A RMMSAn.mdb

N/A

database N/A RMMSSQL N/A RMMSSQL2 N/A RMMSSQL3 N/A RMMSSQ

file mand file)*

RMMSA RMMSSQL RMMSA2 RMMSSQL2 RMMSA3 RMMSSQL3 RMMSAn RMMSSQ

nection e (in erse)

RMMSA RMMSSQL RMMSA2 RMMSSQL2 RMMSA3 RMMSSQL3 RMMSAn RMMSSQ

Multi-Extraction Naming Conventions 13

Chapter 3: CaliberRM Datamart

OVERVIEW

The CaliberRM Datamart extracts data from a CaliberRM repository, transforms that data and loads it into a relational database. The CaliberRM Datamart program can be run from a command prompt or in a batch file.

The CaliberRM Datamart is comprised of three components:

• CaliberRM Datamart Configurator – a wizard that enables you to create or edit a configuration file for the CaliberRM Datamart Extractor to use

• CaliberRM Datamart Extractor – the component of the CaliberRM Datamart that extracts the data

• CaliberRM Datamart Synchronizer – a behind-the-scenes module of the CaliberRM Datamart that keeps the objects in the CaliberRM Datamart universe in sync with the user-defined attributes (UDAs) in CaliberRM.

CALIBERRM DATAMART CONFIGURATOR

To launch the CaliberRM Datamart Configurator Wizard:

1. Select Start > Programs > CaliberRM > Configurator from the Windows Start menu.

Type of Program Input Output

CaliberRM Datamart Configurator

A wizard-based program Selection: CaliberRM projects, baseline information, choice to extract history, traceability or discussions*

A *.ini file (* = the file name)

CaliberRM Datamart Extractor

A command-line program The file name .ini, the Data Source Name (DSN) that points to the database and the server that holds the database

A loaded MS Access or SQL Server database

CaliberRM Datamart Synchronizer

A command-line program The universe name and the DSN

An updated universe with UDAs from CaliberRM (RMMSA.unv or RMMSSQL.unv

* To decrease the extraction time, do not extract discussions.

Overview 14

Step 1 of the CaliberRM Datamart Configuration Wizard is displayed.

To create a new configuration file, select the Create a new configuration file option button.

OR

To open an existing configuration file, select the Open an existing configuration file option button. Click the Browse button to navigate to the location of the file you want to use.

2. Click Next. Step 2 of the CaliberRM Datamart Configuration Wizard is displayed.

Enter the CaliberRM server Host that contains the information you want to export, your User name and Password.

Note: Click Back to change any options on the previous screen if necessary. Click Cancel to end the process without saving any changes.

CaliberRM Datamart Configurator 15


Select the check box beside the baselines you want to export. If you chose to create a new file, the current baseline versions are selected. If you chose to use an existing configuration file, the baselines included in that file are automatically selected.


Select the check box next to the objects you want to export. If you chose to create a new file, all of the objects are selected. If you chose to use an existing configuration file, the objects included in that file are automatically selected.

CaliberRM Datamart Configurator 16

5. Click Next. Step 5 of the CaliberRM Datamart Configuration Wizard is displayed, providing a preview of the configuration file you are about to create.

6. Click Finish. The Save As dialog box is displayed.

7. Navigate to the location in which you want to save the configuration file. Enter a name for your file.

Note: Please read the section “Multi-Extraction Naming Conventions” on page 13 for information on structure and naming conventions for more than one extraction.

8. Click Save. The configuration file is saved as a *.ini. file.

Note: It is recommended that you save it in a subfolder in the CaliberRM Datamart directory.

CALIBERRM DATAMART EXTRACTOR

The CaliberRM Datamart Extractor is the program that exports the data. It is a command line executable that accepts arguments for specifying a configuration file, logging options, a data source name, server name or syntax help.

The syntax is:

Extractor.exe [parameters]

-c configfile.ini – specifies the configuration file; required

-l turns on logging; optional

-d dsnname – specifies data source name; required

-s server name (required; for MS SQL Server only)

-? Displays the syntax

CaliberRM Datamart Extractor 17

CALIBERRM DATAMART SYNCHRONIZER

The CaliberRM Datamart Synchronizer keeps the user-defined attribute (UDA) objects in the CaliberRM Datamart universe in sync with the UDAs in CaliberRM. The CaliberRM Datamart Synchronizer is a behind-the-scenes program that should be run after the CaliberRM Datamart is run. It needs to be run once, and then only after a user-defined attribute is created, modified or deleted in CaliberRM. The CaliberRM Datamart Synchronizer may also be run independently by using a command prompt.

IMPORTANT! WHEN USING A MS SQL DATABASE, THE CALIBERRM USER THAT EXTRACTS THE DATA MUST HAVE AN IDENTICAL USERID WITH PER-MIT IN DATABASE: PUBLIC AND DB_OWNER RIGHTS IN THE MS SQL SERVER.

IMPORTANT! FOR SQL SERVERS, THE DSN NAME MUST INCLUDE “SQL,” EXAMPLE: RMMSSQL

Examples of CaliberRM Datamart Extractor Command Line InterfaceEXTRACTOR -c configfile.ini -d RMMSA

Runs Extractor.exe and reads the configuration from the file configfile.ini

EXTRACTOR -c configfile.ini -l -d RMMSA

Runs Extractor.exe and reads the configuration from the file configfile.ini. Turns on logging. Uses the data source named RMMSA

Extractor -? Displays the Extractor.exe syntax

EXTRACTOR -c configfile.ini -l -d RMMSSQL -s sqlserver

Runs Extractor.exe and reads the configuration from the file configfile.ini; logging is on and the server is specified.

The syntax is:

Synchronizer.exe [parameters]

-u Universe Name – specifies which CaliberRM Datamart Explorer universe to synchronize

-d DSN – specifies the data source name to the database with which it is synchronized

CaliberRM Datamart Synchronizer 18

1. Navigate to c:\Program Files\Starbase\CaliberRMPRO Explorer\BusinessObjects 5.0 (or wherever you installed CaliberRM Datamart Explorer).

2. Double-click the file named Designer.exe. Designer is launched.

Note: If the Designer Wizard launches, click Cancel.

3. Select File > Open. The Open dialog box is displayed.

4. Navigate to c:\Program Files\Starbase\CaliberRMPRO Explorer\BusinessObjects 5.0\Universe (or wherever you installed CaliberRM Datamart Explorer) and select the universe you want to work with (RMSSA for MS Access or RMMSSQL for MS SQL Server).

5. Click Open. The universe is displayed.

6. Select File > Parameters. On the Definition tab, locate and note the Connection name. Then select the Edit button and locate and note the Data Source Name. Click OK.

7. If you want to do a multi-extraction, change the connection name and select the corresponding DSN. Otherwise, click OK again.

Note: See the section “Multi-Extraction Naming Conventions” on page 13 for more information on structure and naming conventions for multi-extractions.

-n User Name – your BusinessObjects user name; default is CaliberPRO User; optional; only used when a BusinessObjects security model is used

-p Password – your BusinessObjects password; default is Analytics; optional; only used when a BusinessObjects security model is used

-? Displays the syntax

Examples of CaliberRM Datamart Synchronizer Command Line InterfaceSYNCHRONIZER -u RMMSA -d RMMSA MS Access example; synchronizes the universe RMMSA and

specifies the data source RMMSA.

SYNCHRONIZER -u RMMSSQL-d DSN=RMMSSQL; UID=username; pwd=pwd

MS SQL Server example; synchronizes the universe RMMSSQL and specifies the data source RMMSSQL, as well as the user name UID and the password.

IMPORTANT! BEFORE RUNNING THE CALIBERRM DATAMART SYNCHRONIZER, YOU MUST COMPLETE THE FOLLOWING STEPS ONE TIME FOR EACH UNIVERSE FILE!

The syntax is:


Note: If the connection user name and password are filled in take note of them, as you will need them in Step 11.

8. Select Tools > Connections. The Connections dialog box is displayed.

Note: If the connection name noted in Step 6 appears in the Connections dialog box, proceed to Step 13.

9. Click Add. The Add a Connection dialog box is displayed.

10. Select ODBC Drivers and click OK. The ODBC Drivers dialog box is displayed.

11. In the Name box, type the same connection name noted in Step 6. In the Data Source Name box, select same DSN name noted in Step 6, from the drop-down list box. In the Type box, select Shared from the drop-down list box.

12. Enter the user name and password (for MS SQL Server).

13. Click OK. The Connections dialog box is displayed. Click OK.

You may now run the CaliberRM Datamart Synchronizer.


Chapter 4: CaliberRM Datamart Explorer

OVERVIEW

The CaliberRM Datamart Explorer is an integrated query and analysis environment powered by BusinessObjects. It enables you to create queries based on CaliberRM universes that are contained in the product CD and loaded with the product.

CONFIGURING THE CALIBERRM DATAMART EXPLORER DSN

For Microsoft Access:The system DSN allows CaliberRM Datamart Explorer to access the data in the MS Access database.

1. On the machine where CaliberRM Datamart Explorer is installed, open the Control Panel from the Windows Start menu.

2. Double-click ODBC Connections or Data Sources (ODBC). The ODBC Data Source Administrator dialog box is displayed.



4. Click Add.

5. Select Microsoft Access Driver (*.mdb) from the list.

6. Click Finish. The ODBC Microsoft Access Setup dialog box is displayed.

7. Contact your CaliberRM Datamart Explorer Administrator for the DSN name used on the Datamart machine. Enter that as the Data Source Name.


IMPORTANT! BEFORE RUNNING CALIBERRM DATAMART EXPLORER , YOU MUST:

• CONFIGURE THE CALIBERRM DATAMART EXPLORER DATA SOURCE NAME (DSN)

• CONFIGURE THE CALIBERRM DATAMART EXPLORER UNIVERSE LOCATION

• RUN A SIMPLE TEST REPORT

SEE THE FOLLOWING INSTRUCTIONS.

Overview 21

8. Click Select. The Select Database window is displayed.

9. In the Directories section, navigate to the MS Access database. Select it in the list and click OK.

Note: This may require that you map a network drive to the Datamart machine.

10. Click OK to exit the ODBC Microsoft Access Setup dialog box.

11. Click OK to exit the ODBC Data Source Administrator dialog box.

The DSN is created. Proceed to the section “Configuring the CaliberRM Datamart Universe Location” on page 23.

For Microsoft SQL Server:The system DSN allows CaliberRM Datamart Explorer to access the data in the MS SQL Server database.

1. On the machine where CaliberRM Datamart Explorer is installed, open the Control Panel from the Windows Start menu.

2. Double-click ODBC Connections or Data Sources (ODBC). The ODBC Data Source Administrator dialog box is displayed.



4. Click Add.

5. Select SQL Server from the list. Click Finish. The Create a New Data Source to SQL Server wizard is displayed.

6. Contact your CaliberRM Datamart Explorer Administrator for the DSN name used on the Datamart machine. Enter that as the Data Source Name.


Note: For MS SQL Server, the DSN name must include the letters “SQL”.Example: RMMSSQL

7. If you want, enter a Description for the data source.

8. Select the server that contains the SQL database.

9. Click Next. The next wizard screen is displayed.

10. Select the With SQL Server authentication... option button.

11. Click the Client Configuration button. The Add Network Library Configuration dialog box is displayed.

12. Verify that the TCP/IP option button is selected and click OK.

13. Enter the user id and password created for CaliberRM and SQL Server.

Configuring the CaliberRM Datamart Explorer DSN 22

Note: If you do not know the user id and password, ask your CaliberRM Datamart Administrator.


15. Select the Change the default database to: check box and select the SQL database from the list.


17. Click Finish. A screen is displayed indicating your configuration settings.

18. Click Test Data Source. When the test is complete, click OK.

Note: If the test does not respond, check with your SQL Server administrator to ensure the SQL Server is set up properly.

19. Click OK to exit the configuration settings window.

20. Click OK to exit the ODBC Data Source Administrator dialog box.

The DSN is created. Proceed to the section “Configuring the CaliberRM Datamart Universe Location” below.

CONFIGURING THE CALIBERRM DATAMART UNIVERSE LOCATION

The CaliberRM Datamart Explorer must be configured to “point” to the universe folder that contains the CaliberRM Datamart Explorer universes. The universes are installed with the Datamart.

To configure the universe location:

1. Select Start > Programs > CaliberRM > CaliberRM Datamart Explorer from the Windows Start menu.

Note: If the New Report Wizard is displayed, click Cancel.

2. Select Tools > Options.

3. Select the File Location tab.

4. Select Universes from the File Types list.

5. Click Change.

6. Navigate to the folder that contains the CaliberRM Datamart Explorer universes. The universes are installed with Datamart.

Note: This may require that you map a drive.

7. Click OK.

8. Click OK to exit the Options dialog box.

CaliberRM Datamart Explorer is ready to run reports. However, you may want to run a simple report to verify everything is configured properly.

Configuring the CaliberRM Datamart Universe Location 23

RUNNING A SIMPLE REPORT

1. In CaliberRM Datamart Explorer, select File > New Query. The New Report Wizard is displayed.

2. Click Begin.

3. In the Specify Data Access screen, verify that the Universe option button is selected, and click Next.

4. In the Available Universes list, select either MS Access or MS SQL Server.

5. Click Finish. The Query Panel opens.

6. Open the Requirements Reports folder.

7. Open the Projects folder.

8. Drag and drop the Project Name object from the Classes and Objects panel to the Result Objects panel.

9. Click Run. A list of extracted projects is displayed.

CaliberRM Datamart Explorer is connected properly and reporting on data from the extracted database.

GETTING STARTED IN CALIBERRM DATAMART EXPLORER

When you first launch CaliberRM Datamart Explorer, the CaliberRM Datamart Explorer Remote Control is displayed. The CaliberRM Datamart Explorer Remote Control is a floating window that gives you access to the most common CaliberRM Datamart Explorer functions. It is always available and always on top, unless minimized.

From the Remote you can:

• Click on the Explorer logo to connect to Borland’s CaliberRM Share website. This is a knowledge base containing information about CaliberRM integrations, tips, techniques, report templates and other valuable insights.

• Change the View mode of the Remote from Full (shown at left) to Compact, Minimize and Exit the Remote.

• Open Reports, Close reports and create a New Query.

• Navigate through open reports using the navigation arrows.

Running a Simple Report 24

OPENING A REPORT

To open a report:

1. Click the Open icon. An Open dialog box is displayed.

Note: If the Remote is not expanded, click Reports on the panel. This will expand the panel and dis-play the Open icon.

2. Navigate to the location of the report and click Open.

CaliberRM Datamart Explorer launches and displays the report.

CREATING A NEW QUERY

To create a new query:

1. Click New Query on the Remote Control. CaliberRM Datamart Explorer opens and displays the Cre-ate New Report screen of the New Report Wizard.

If the wizard does not appear, select Tools > Options > New Document tab. Select the Invoke the New Report Wizard with the following settings option button. You can select the Prompt User option buttons selected to use the full Wizard capability beginning with Step 2. Or, you may select the Use Default options buttons, detailed below, to skip to Step 5.

Click OK, close CaliberRM Datamart Explorer, and begin at Step 1 again.

Select this option to invoke the Wizard

Select either the caliberrm landscape or the caliberrm portrait template

Select either the MS Access Universe or the SQL Server Universe

Opening a Report 25

2. If you chose to use the Prompt User options, the following Wizard appears. Select the Generate a Standard Report option button. Click Begin.

3. The Specify Data Access screen is displayed. Select the Universe option button and click Next.

Note: Click Back to change any options on the previous screen if necessary. Click Cancel to end the process without saving any changes.

4. The Select Universe screen is displayed. Select a universe and click Finish.

Creating a New Query 26

Note: Select the Set as My Default Universe check box if you want the universe to be the default.

The Query Panel is displayed.

Each object type is designated by a symbol:

Dimension

Detail

Measure

See the Glossary for descriptions of these objects.


5. From the Classes and Objects pane, select an object you want to include in your query. Drag and drop it onto the Result Object pane.

Note: For detailed information on each object, refer to “Appendix A: Universe Parameters” on page 32.

Note: For more in-depth instruction about creating and manipulating reports, click the Help button to view BusinessObjects Help.

6. Complete Step 5 for all of the objects you want to include in your query. When you have added all of your objects, click Run.

7. The resulting report is displayed. You may now save the report by selecting File > Save from the menu, or by clicking the Save button.

Note: For more detailed information on creating reports or on BusinessObjects errors, see the documents BusinessObjects51EN.pdf or Errors51EN.pdf. These can be found in the location where you installed CaliberRM Datamart Explorer. The default location is C:\Program Files\Starbase\CaliberRMPRO Explorer\OnlineGuides\EN.


Chapter 5: CaliberRM Datamart Explorer Reports

CaliberRM Datamart Explorer has a series of pre-defined report templates that are included when you install the product. These report templates are intended to be used as the starting point for developing more complete and detailed reports. The standard queries are defined below and detailed further in the following sections. See “Appendix B: Report Samples” on page 41 for examples of these reports. You may download more templates from Calibershare as Borland develops them.

• Attribute Distribution – shows the way attributes are distributed throughout the repository

• Impact Analysis – shows the number of traces, both direct and implied, related to a set of requirements

• Project Scorecard – a number-focused report that gives indicators to the overall soundness of a project(s)

• Requirement Volatility – shows the number of changes that are made to a requirement within a project(s) over time

• Status Summary – shows the number of requirements broken down by project, baseline, requirement type, status and priority

• Traceability Complexity – shows the number of traces that link a user-defined number of “Top 10” requirements within projects and Automated Software Quality (ASQ) applications

• User Deployment – shows users assigned to a specific project(s)

ATTRIBUTE DISTRIBUTION

The Attribute Distribution report is primarily designed for CaliberRM administrators. This report details the way attributes are distributed throughout the repository. It shows both the distribution of an attribute across projects as well as the attributes contained in each project. The data is broken down by attribute, requirement type and project. The report shows a tabular and a graphical representation of the data and presents different levels of detail on several different tabs. It also shows which UDAs are not used in any of your projects.

IMPACT ANALYSIS

The Impact Analysis report is primarily designed for Project Managers, Quality Managers and Change Management Assessors. This report shows the number of traces, both direct and implied, related to a set of requirements both upstream and downstream. It also shows the types of elements that the traces relate. The

Attribute Distribution 29

number of traces are broken down by project, baseline, requirement type, status and priority. Suspect traces are flagged and the “average depth” of traces are shown. The report presents the different levels of detail of several tabs.

PROJECT SCORECARD

The Project Scorecard report is a numbers-focused report that gives several indicators to the overall well-being of your project(s). This report is designed for Project managers and Project Team Members. Data is available by project and requirement type and is run for the current version’s baseline or other baselines, depending on the data. This report contains the following indicators:

• Length of trace chains (maximum, average)• Number of requirements broken down by status and total• Number of requirements broken down by owner• Number of requirements broken down by responsible person• Average length of time from creation to current status broken down by status.• Total number of suspect links• Total number of requirement’s growth time, broken down by year, month and week

REQUIREMENT VOLATILITY

The Requirement Volatility report is designed primarily for Project Managers and Project Team Members. This report shows the number of minor and major changes that are made to a requirement within a project or projects over time. It shows the rate of change as well as the cumulative total number of changes. The data is broken down by project, current baseline, requirement type, status, priority, owner and requirement ID. The data is further broken down by year, month, week and day. The report shows a tabular and a graphical representation of the data and presents different levels of detail on several different tabs.

STATUS SUMMARY

The Status Summary report is designed primarily for Development Managers. This report shows the number of requirements broken down by project, baseline, requirement type, status and priority. It shows the percentage of total requirements represented by each status in each project and requirement type. Its information is presented on several different tabs.

TRACEABILITY COMPLEXITY

The Traceability Complexity report is designed primarily for Project Managers and Project Team Members. It shows the number of traces that link to a user-defined number of most frequently observed

Project Scorecard 30

requirements within and between projects and ASQ applications. It includes upstream and downstream traces, as well as direct and implied traces. It shows the type of object to or from which a requirement traces. All data is grouped by project.

USER DEPLOYMENT

The User Deployment report is designed for Project Managers and CaliberRM Administrators. It shows the users that are assigned to a specified project. The report also shows which users are assigned to a group and the security profiles for each user, group and project.

User Deployment 31

Appendix A: Universe Parameters

This appendix details the universe objects, including the object description and type, as they appear in the BusinessObjects query panel.

REQUIREMENT REPORTS CLASS

These objects give information about requirement-centric data. The information must be broken by project and baseline if the CaliberRM Datamart has multiple projects and baselines.

The information in these folders cannot be combined in a queries with information from the Administration Reports or Glossary folders.

Projects Class

Object Description Type / Qualification

Project Name The name of the CaliberRM project Character; Dimension

Description The project's description Long text; Detail

TestDirector Integration Enabled A flag signifying whether the TestDirector integration is turned on or off

Character; Dimension

Select Integration Enabled A flag signifying whether the Select Enterprise integration is turned on or off


SCM Integration Enabled A flag signifying whether the Source Code Management integration is turned on or off


Security Enforced A flag signifying whether security is turned on or off for the project


Requirements Mapped Enabled A flag signifying whether a requirement can be mapped for the project (Yes=Mapped)


Requirements Shared Enabled A flag signifying whether a requirement can be shared for the project (Yes=Mapped)


Number of Projects A count of the number of projects Number; Measure

Baselines Class Baseline Name The baseline name within a CaliberRM

projectCharacter; Dimension

Description The baseline's description Long text; Detail

Requirement Reports Class 32

Baselines Class, cont.


Baseline locked A flag signifying whether the baseline is locked or unlocked


Number of Baselines A count of the number of baselines Number; Measure

Requirement Types Class Requirement Type Name The requirement type name within a

CaliberRM projectCharacter; Dimension

Description The requirement type's description Long text; Detail

Tag The tag is a short name of the requirement type (6 character max)


Number of Requirement Types A count of the number of requirement types Number; Measure

Requirements ClassHierarchy CaliberRM hierarchy number. (1.0, 1.1, etc.) Character; Dimension

Hierarchy Index An object that properly sorts the Hierarchy number

Number; Dimension

Requirement Name The name of the requirement Character; Dimension

Requirement ID The requirement's unique number Number; Dimension

Tag ID The combination of the Requirement Type Tag and Requirement Unique Number


Version The actual version of the requirement Character; Dimension

Owner The person that is defined in CaliberRM as the owner (last name, first name) of the requirement


Owner’s User Name The owner’s CaliberRM user name Character; Dimension

Owner’s Location The location of the owner Character; Dimension

Status The Status of the requirement (System Attribute)


Priority The Priority of the requirement (System Attribute)


Description The Description of the requirement Long text; Dimension

Validation A requirement's validation Long text; Dimension


Requirements Class, cont.


Shared A flag signifying whether the requirement is mapped from another requirement (Yes=Mapped)


Shared From The requirement is shared from this requirement ID

Number; Dimension

Number of requirements A count of unique requirements Number; Measure

Requirement References ClassFile Name The reference files link to a requirement Character; Dimension

Description The reference file's description Long text; Detail

Reference Type The reference type (file or web) Character; Dimension

Number of References A count of the number of references Number; Measure

Requirement Traces ClassRoot ID The root requirement's identification number Number; Dimension

Root Project Name The root requirement's project name Character; Dimension

Root Name The root requirement's name Character; Dimension

Root Description The root requirement's description Long text; Dimension

Root Type The root requirement's type (Requirement, TestDirector, StarTeam, other, etc.)


Root Owner The root requirement's owner Character; Dimension

Root Test Status The root requirement's status for Mercury's TestDirector Tests


Trace ID The trace requirement's identification number

Number; Dimension

Trace Project Name The trace requirement's project name Character; Dimension

Trace Name The trace requirement's name Character; Dimension

Trace Description The trace requirement's description Long text; Dimension

Trace Type The type of trace Character; Dimension

Trace Owner The trace requirement's owner Character; Dimension

Trace Priority The trace requirement's priority Character; Dimension


Requirement Traces Class, cont.


Trace Status The trace requirement's status Character; Dimension

Trace Test Status The requirement's status for Mercury's TestDirector Tests


Direction The direction of the root/trace (to or from) Character; Dimension

Direct or Implied Signifies whether the trace is direct or implied


Circular A flag set that indicates a root/trace is in a circular path


Suspect A flag set that indicates a root/trace is suspect


Depth The total number of direct and indirect traces

Number; Measure

Number of Traces A count of the number of traces Number; Measure

Number of Direct Traces A count of the number of direct traces Number; Measure

Number of Circular Traces A count of the number of circular traces Number; Measure

Number of Non-suspect Traces A count of the number of non-suspect traces Number; Measure

Number of Suspect Traces A count of the number of suspect traces Number; Measure

Requirement Discussions Class


Subject The subject of the discussion Long text; Dimension

Discussion Date The date and time the discussion was posted

Date; Dimension

Day of Week The day of the week the discussion was posted


Discussion Week The week the discussion was posted Number; Dimension

Discussion Month The month the discussion was posted Character; Dimension

Discussion Year The year the discussion was posted Number; Dimension

Discussion Posted By The person who posted the discussion Character; Dimension

User Name The user name of the person who posted the discussion



Requirement Discussions Class, cont.


Location The location of the person who posted the discussion


Body The content of the discussion Long Text; Dimension

Discussion Depth The depth of the discussion Number; Measure

Number of Total Discussions A count of the number of discussions Number; Measure

Requirement Responsibility ClassResponsible Member The name of the responsible user Character; Dimension

Responsible User Name The user name of the responsible person Character; Detail

Location The location of the responsible person Character; Detail

Number of Responsible Members A count of the number of responsible members

Number; Measure

Requirement Version ClassRequirement ID The requirement’s ID Number; Dimension

Version Actual The actual version of the requirement Character; Dimension

Major or Minor change Indicates whether the change is a major or minor change


Version Change Date The date the version changed Date; Dimension

Change Owner The owner of the requirement change Character; Dimension

Day of Week The day of the week the version changed Character; Dimension

Version Change Week The week the version changed Number; Dimension

Version Change Month The month the version changed Character; Dimension

Version Change Year The year the version changed Number; Dimension

Comment A comment about the change Long text; Dimension

Field Changed The field to which a change was made Character; Dimension

Old Value The old value of the field changed Long text; Dimension

New Value The new value of the field changed Long text; Dimension


ADMINISTRATION REPORTS CLASS

These objects give information about non requirement-centric data that is beneficial to an Administrator.

Requirement Version Class, cont.Requirement Day Age Shows the age of the requirement from v1.0

to the max version (USE ONLY WITH OBJECTS IN THE REQUIREMENT VERSION CLASS FOLDER)

Number; Dimension

Number of Changes A count of the total number of changes (not by version)

Number; Measure

Project Discussion ClassProject Name Use this project name object when running

reports on project discussionCharacter; Dimension

Posted By The user who posted the discussion Character; Dimension

Subject of Project Discussion The subject of the discussion Long text; Dimension

Body of Project Discussion The content of the discussion Long text; Dimension

Discussion Depth The depth of the discussion Number; Dimension

Project Discussion Date The date the discussion was posted Date; Dimension

Number of Project Discussions A count of the total number of discussions Number; Measure

Caliber User Class


User Name The CaliberRM userid Character, Dimension

First Name CaliberRM user's first name Character; Dimension

Last Name CaliberRM user's last name Character; Dimension

Email Address CaliberRM user's Email address Character; Dimension

Location CaliberRM user's location Character; Dimension

Phone Number CaliberRM user's phone number Character; Dimension

Fax Number CaliberRM user's fax number Character; Dimension

Pager Number CaliberRM user's pager number Character; Dimension

Administration Reports Class 37

Caliber User Class, cont.


Department Name CaliberRM user's department Character; Dimension

Must Change Password A flag set on the user’s account so he/she must change the password


Cannot Change Password A flag set on the user’s account so he/she cannot change the password


Password Never Expires A flag set on the user’s account allowing a password that never expires


Account Disabled A flag set on the user’s account that disables the account


Number of CaliberRM Users A count of the total number of CaliberRM users

Number; Measure

Caliber Groups ClassGroup Name The CaliberRM group name Character; Dimension

Description The CaliberRM group's description Long text; Dimension

Group Email Address The CaliberRM group's Email address Character; Dimension

Number of Groups A count of the total number of groups Number; Measure

Project Security Admin ClassProject Name The CaliberRM project Character; Dimension

Project Description The CaliberRM project description Long text; Detail

Security Profile Name The CaliberRM security profile name Character; Dimension

Security Profile Description The CaliberRM security profile description Long text; Detail

Group Name The CaliberRM group name Character; Dimension

Full Name The CaliberRM user Character; Dimension

User Name The CaliberRM user name Character; Detail

Department Name The CaliberRM department name Character; Dimension

Number of Security Profiles A count of the total number of security profiles

Number; Measure


Requirement Type Security Admin Class


Security Profile Name The CaliberRM security profile name Character; Dimension

Security Profile Description The CaliberRM security profile description Long text; Detail

Requirement Type Name The requirement type name within a CaliberRM project


Description The requirement type's description Long text; Detail

Requirement Type Access The security access for the requirement type (None, List, Read, Create)


Requirement Type Delete Permission

The security delete access for the requirement type (None, Owned, Any)


UDA Name The name of the UDAs in the requirement type


UDA Access The security access for the UDA (None, Owned, Any)


Requirement Types Admin ClassProject Name The name of the CaliberRM project Character; Dimension

Project Description The project's description Long text; Detail

Requirement Type Name The requirement type name within a CaliberRM project


Tab Name The name of the tab within a CaliberRM project


UDA Name The name of the UDAs in the requirement type


UDA Description The description of the UDA Long text; Detail

UDA Type The type of the UDA Character; Dimension

System Attribute A flag set that indicates the attribute as a system attribute


Causes Version Change A flag set to change the version to a major increment


Change Makes Trace Links Suspect

A flag set to make the trace suspect Character; Dimension

Inherit From Parent A flag set for the UDAs to inherit the default value from the parent



GLOSSARY CLASS

This class remembers Glossary Terms that are global to all projects.

Requirement Types Admin Class, cont.


Mandatory Set on Create A flag set for the UDAs to make the default value mandatory


Accept Default Setting A flag set for the UDAs to accept a default value



Glossary Word The glossary word Character; Dimension

Glossary Definition The definition of the glossary word Character; Dimension

Number of Glossary Words A count of the number of glossary words Number; Measure

Glossary Class 40

Appendix B: Report Samples

This appendix consists of examples of data generated using CaliberRM Datamart Explorer reports.

ATTRIBUTE DISTRIBUTION .REP

Report Samples 41

IMPACT ANALYSIS.REP

PROJECT SCORECARD.REP

Report Samples 42

STATUS SUMMARY.REP

TRACEABILITY COMPLEXITY.REP

Report Samples 43

USER DEPLOYMENT .REP

Report Samples 44

Sample CaliberRM Datamart Extraction Times 45

Appendix C: Sample CaliberRM Datamart Extraction Times

This appendix provides multiple examples of extraction times of six separate databases. These times were produced by selecting all projects, traces, discussion and history from each test database. Times are approximations from multiple extraction runs, and may vary based on your network. These tests were based on the recommended specifications detailed in the section “System Requirements” on page 7.

Total # of: Test DB 1 Test DB 2 Test DB 3 Test DB 4 Test DB 5 Test DB 6

Requirements; All Baselines

3,120 13,250 3,270 31,000 9,650 24,170

Requirement History 17,340 49,070 6,480 87,030 25,290 90,050

Traces 6,600 6,320 13,110 129,100 41,210 184,370

Requirement Discussions

430 480 3270 3270 60 60

MS Access 2000 Time (Hour:Minutes)

0:09 2:30 0:08 5:48 1:40 3:20

MS SQL Server 7 Time (Hour:Minutes)

:25 4:20 :25 7:00 2:10 4:40

Appendix D: CaliberRM Datamart Explorer Restrictions

This appendix details certain restrictions when using CaliberRM Datamart Explorer.

DOCUMENT REFERENCES

In CaliberRM Datamart, the extraction of document references is not available.

REPORTING DOMAINS

There are seven “domains” in the CaliberRM Datamart that dictate how data can be accessed. Each of these domains contains information that correlates to information in the Classes on the CaliberRM Datamart Explorer Query Panel.

VI. Requirement information, contained in the classes: • Project • Baseline • Requirement Type • Requirements

Traceability information, contained in the classes:

• Project • Baseline • Requirement Type • Requirement Traces

Responsibility information, contained in the classes:

• Project • Baseline • Requirement Type • Requirements • Requirement Responsibility

Requirement Discussion information, contained in the classes:

• Project • Baseline • Requirement Type • Requirements • Requirement Discussions

CaliberRM Explorer/Datamart Restrictions 46

VII. Requirement Change information, contained in the classes:

• Project

• Baseline

• Requirement Type

• Requirements

• Requirement Change

VIII. Project Discussions information, contained in the class:

• Project Discussion

IX. Projects (Users, Groups & Security Profiles) information, contained in the classes:

• Caliber User

• Caliber Group

• Project Security Admin

X. Requirement Type & Security Profiles information, contained in the class:

• Requirement Type Security Admin

XI. Requirement Type Structure information, contained in the class:

• Requirement Types Admin

XII. Glossary information

A query can only be created in the context of a single domain. Reporting across these domains with a single query is not supported because there is no correlation in the data. That is, a single query across domains does not make sense. For example, you cannot create a single query that shows which requirement type(s) have a certain security profile and how many requirements are in each requirement type. If you needed to display this information, you would use two queries.

If you attempt to create a query that spans domains, the following error message appears:


For advance reporting, a printout of the database schema can be obtained using Business Objects Designer. In the directory BusinessObjects 5.0, double-click Designer.exe. Once Designer is open, select File > Open, navigate to the universe RMMSA.unv and open it. Select Tools > Options > Print tab to select the information you want to display in the graphical structure. Click OK. Select File > Print to print the universe.

LIST OF VALUES

When running a query with the a prompt and selecting the Values button, always remember to select the Refresh button. If a query is run with older values it may not return any data.

REQUIREMENT TYPES AND PROJECTS

There is no relationship between requirement types and projects unless there are requirements in the requirement type. That is, you cannot show the requirement types assigned to a project if the requirement type is “empty.”

SECURITY ON GROUPS

There is no relationship between security profiles and groups in projects. You can show security profile information on requirement types and UDAs, but you cannot relate that to a specific group in a project.

USERS IN GROUPS

There is no relationship between users in groups. The relationship is users in groups in projects. You can show which users are assigned to which groups in which projects.A report showing which groups a user is a member of (outside of the context of a project) is provided in CaliberRM.

USER-DEFINED ATTRIBUTES

Only the first 230 UDAs associated with the projects selected will be extracted to the database. To optimize space in the table, only the UDAs associated with projects selected are extracted into the database. Also, only UDAs with values are extracted into the database.

WARNING: PLEASE DO NOT MODIFY THE CONTENT OF THE ORIGINAL UNIVERSES.


Glossary 49

Glossary

Attributes: Characteristics that help define requirements

Baseline: A static snapshot of a group of requirements or a project at specific versions or a specific point in time

CaliberRM: A collaborative, Internet-based requirements management system that enables project teams to deliver higher quality applications that meet end-user specifications

Class: A logical grouping of data elements called objects

Dimension: Key data elements that are the parameters of a query

Detail: Data elements that provide a description of a dimension object; these are always associated with dimension objects and do not form the basis of a query

Group: A set of users with similar responsibilities (i.e., managers, developers, engineers, etc.)

Measure: Numeric data that convey information that is a result of calculations on the database

Object: An element in a universe that corresponds to a selection of data in the database; objects are used to build queries that retrieve data for reports; there are three types of objects: Dimension, Detail and Measure

Project: Any application or system under development; projects consist of several layers of information, including users and groups, requirement types and requirements

Query: A request for information from a database

Requirements: Specifications that the application or system being built must meet; requirements can originate from many sources such as business rules, business process models, product marketing, prototypes, development meetings and more

Requirement ID Numbers: These numbers, also called Serial numbers, are displayed to the right of the requirement name; these are static and automatically generated by CaliberRM; each ID number is unique in the system; if a requirement is deleted, that ID number is not reused

Requirement Types: High-level groups of requirements; requirement types are typically classified by their function (i.e., Marketing, Functional, GUI, Software, Testing, etc.)

Traceability: CaliberRM supports requirement traceability to allow you to see requirement relationships easily; requirements may trace to or trace from other requirements, as well as object modeling and test entities; suspect links, which indicate a change in a requirement that may affect other objects, are shown when a requirement is changed

Universe: The file that creates the relationship between the database tables; it also provides the mapping between business level terms and database level elements

User-Defined Attributes: An attribute that a user defines and assigns to a custom tab in a requirement type

User: Any person who has access to and uses CaliberRM or the Framework Administrator system; users can be developers, managers, testers, CEOs and others.

Index 50

Index

A

administration reports class 37

C

CaliberRM Datamart 14–20Configurator 14Extractor 17overview 14Synchronizer 18

CaliberRM Datamart Explorergetting started 24overview 21Reports 29

configuringCaliberRM Datamart Explorer DSN 21data source name 12databases and data sources 9–12Microsoft Access 9Microsoft SQL Server 10MS SQL Server 11universe location 23userid, password 10

creating a new query 25

E

extractionnaming conventions 13

extraction timessample 45

G

glossary class 40

I

introduction 5

O

opening a report 25overview 5

R

report samples 41–44requirement reports class 32running a report 24

S

system requirements 7database server 8datamart explorer 8datamart extractor 7

U

universe parameters 32–40

copyright otice€¦ · running a simple report ......

Documents