Index
A
A (active) state type, UCM, 54
Access control
compared with permissions, 3
governance and, 288–289
hook providing security in ClearQuest, 128
rules governing, 11
workflow rules, 46
Accessing records, 114–115
Action hooks, ClearQuest, compared with Jazz Operation Access Control. See also Hooks, Access Control
behavior or extensions, 3
Commit hook. See Hooks, Commit
Initialization hook. See Hooks, Initialization
Notification hook. See Hooks, Notification
Validation hook. See Hooks, Validation
Actions
comparing ClearQuest action with Jazz action, 2
customizing work items, 15
dedicated, 70–76
in Jazz workflow, 67
hooks. See Action hooks
reassignment, 70
roles in automation of, 127
rules governing, 11
workflow rules, 46
ActiveX
applets, 12
integration with ClearQuest and, 171–172
supported in BASIC not Perl, 261
Activities
describing ClearQuest data objects for Agile process, 338
subclasses of, 5–6
workflows in activity diagrams, 44
Activity record type
suggested fields for, 341–343
workflows of, 344
ACWP (actual cost of work performed), 280
Administrative activities, 5
Administrators
dependent integration of IBM administrator with ClearQuest, 158
implementing roles with ClearQuest groups, 133
performance benchmarking by Web administrators, 200
training, 206
Agile development
in ALM schema, 346–349
applying Agile practices to requirements, 28
in ClearQuest. See ClearQuest, Agile schema in
defining, 325–326
in Jazz. See RTC (Rational Team Concert), Scrum process in
overview of, 325
resources for, 350
Scrum framework for, 326–329
summary, 351
use of graphs in metrics strategy, 281
Agreement, getting regarding requirements, 28
ALM (Application Lifecycle Management) schema. See also C/ALM (Collaborative ALM)
Agile development in, 346–349
common schema in development, 222
creating task to fix defect, 370–371
governance in, 297–298
in integrated solution architecture, 367–373
periodic releases in, 371–372
process control in, 297
security context in, 297–298
workflows in, 65–66
ALMRequest, 348–349
ALMRole
comparing Agile and ALM schema, 347
overview of, 140–141
stateless record types in ALM security, 298
ALMRoleLabel
overview of, 140
stateless record types in ALM security, 298
ALMTask, 347–348
Amount of effort. See Effort required
AMStateTypes, 53
Analysis
data providing information for, 81
in workflow item lifecycle, 50
Analysis & Design discipline
choosing database, 32–33
defining client types, 29–30
defining data fields, 35
defining infrastructure architecture, 30–32
defining workflow, 35
design patterns in, 36–40
designing user interface (forms), 36
overview of, 29
resources, 40
reviewing/signing off on design models, 40
schema high-level design in ClearQuest, 33–34
summary, 40–41
Applets, performing background operations, 12
Applications/solutions
ClearQuest example. See ClearQuest, example solution
external impacts and, 89
installing during deployment, 202
integrated. See Integrated solution architecture (ClearCase, ALM, and Build Forge)
Jazz-based C/ALM, 354–356
resources for, 382–383
summary, 384–385
Approval tracking, Jazz, 2
AppScan, integration of RQM and RTLM with, 185–187
Architecture
defining infrastructure architecture, 30–32
for integrated solution. See Integrated solution architecture (ClearCase, ALM, and Build Forge)
JIA (Jazz Integration Architecture), 192–193, 355
Areas
defined, 130
role implementation and, 133–136
user roles in different areas, 131
Asset reuse, 191
Assign action, notification and, 58
Assignees, assigning solution providers, 91
Assignment
auto-assignment, 145–149, 273–274
issues/typical problems addressed by roles, 128–129
members to test tasks, 311–312
reassignment, 70
roles in, 127
Association, by field label in Eclipse Designer, 109
Attachments
data, 100–103
HasAttachment hook, 120–121
Limit Attachment size hook, 121–122
to work items, 11
Auto-assignment, of roles, 145–149, 273–274
Auto-change state, 58–59
Automation
in ClearQuest governance, 290
in governance, 288
in Jazz-based C/ALM solution, 354
roles in, 127
setting choices based on Multiple role, 146–147
setting Responsible based on role object, 147–149
setting Responsible based on Single role, 145–146
Single roles and, 130
B
Back Reference field, in object relations, 110–113
Balking pattern, 36
Baselines
fixing defects and, 370–371
periodic releases and, 371–372
BASIC
choosing scripting language and, 261
creating new ClearQuest integrations, 167–172
storing hooks externally, 249–250
use of session variables, 240
BCWP (budgeted cost of work performed), 280
Benchmarking, performance, 200
Bill of materials (BOM), in preparing for deployment, 201
BIRT (Business Intelligence and Reporting Tools)
as metrics tool, 286
resources for, 303–304
Blocking assignment, 129
BOM (bill of materials), in preparing for deployment, 201
Budgeted cost of work performed (BCWP), 280
Build engines, RTC integrations, 190–191
Build Forge
continuous build and validation process, 369–370
dependent integration with ClearQuest, 161–162
in integrated solution architecture, 367–373
RQM integrations, 187
Build reports, in metrics strategy, 284
Build work items, 6
Builds
continuous build and validation process, 369–370
subflow for build approval, 76–78
Burndown charts, releases and, 345
Business Intelligence and Reporting Tools (BIRT)
as metrics tool, 286
resources for, 303–304
Business rules, 378–379
Buttons, enabling button hooks in Web development, 274–275
C
C/ALM (Collaborative ALM)
Jazz-based, 354–356
overview of, 353–354
reports, 304–305
resources for, 383
C (complete) state type, UCM, 54
Caching choice lists, 267–268
Capability Maturity Model Integration (CMMI), 83, 103
Cardinality, roles in Jazz, 130
Categories
customizing test work items, 318
organizing test information using, 320–321
setting permissions for test customization, 321–322
CCRC (ClearCase Remote Client), 172
Change management
defining change process, 207–208
process diagram, 47–48
roles in, 131
RUP (Rational Unified Process) applied to, 21–22
system elements, 28–29
Unified Change Management. See UCM (Unified Change Management)
Change requests
activities for breaking down into smaller elements, 5
documenting in change management database, 28–29
roles in, 131
types of changes and, 4
Change_State actions, ClearQuest
overview of, 56
subflow for gathering more information, 69
Chart wizard, 285
Charts
comparing ClearQuest and Jazz customization areas, 17
in metrics strategy, 281
Child Control pattern
design, 38
Child records, creating from parent record, 123–126
Choice list, Clear Quest
allowed actions list, 150
caching, 267–268
compared with Jazz Enumeration, 3
creating multiple lists, 268
creating tree-like lists, 268–270
defining requiredness, 361
hard-coded data in, 272–273
hooks, 114, 144, 150, 236-238, 270–271
improving performance of long lists, 265
populating based on role objects, 147–148
populating based on roles, 146–147
recalculating/invalidating, 265–267
in solution example, 358–360
for user-defined roles, 150
activities, 5–6
change requests, 4
overview of, 4
project-related work items, 6–7
test elements, 6
ClearCase
ActiveX controls in establishing integration with, 171–172
CM API and, 172–175
in integrated solution architecture, 367–373
integrating with ClearQuest, 156–157
in managing release promotion, 375
UCM work projects and, 368–369
working on test artifacts, 372–373
ClearCase Bridge
ClearCase Connector compared with, 188–190
connecting to RTC, 188
ClearCase Connector
compared with ClearCase Bridge, 188–190
RTC integrations, 188
ClearCase Remote Client (CCRC), 172
ClearQuest
ALM schema. See ALM (Application Lifecycle Management) schema
comparing ClearQuest and Jazz terminology, 2–3
comparing customization elements and terms with Jazz, 15–17
customizing record types, 18–19
databases supported by, 32–33
design patterns built into, 36
implementation tasks, 198
implementing roles with ClearQuest groups, 132–133
integrations. See Integration, ClearQuest
representation of data in, 117–118
schema high-level design in, 33–34
scripts for data representation in ClearQuest, 120
setting up customizations during deployment, 203–204
setting up environment during deployment, 202–203
ClearQuest, Agile schema in
metrics, 345
overview of, 337–339
requesting required data for, 339–340
suggested fields for Activity record type, 341–343
suggested fields for Sprint record type, 340–341
workflows in, 343–345
ClearQuest Bridge, 180–183
ClearQuest Connector
integration at data-level, 154
Jazz integration with ClearQuest, 177–180
RTC integrations, 188–190
ClearQuest Designer
comparing Eclipse and Windows versions of, 18–19
moving user databases, 214–216
user-defined fields in, 357–358
viewing database properties, 213–214
Windows version, 213
ClearQuest, example solution
defining choice lists, 358–360
defining requiredness, 360–363
SLAs (Service Level Agreements) in, 363–367
user-defined fields, 356–358
ClearQuest, governance in
electronic signatures in, 295–296
monitoring in, 297
permissions in, 290–293
process control and automation in, 290
security context in, 294–295
ClearQuest Maintenance tool
creating test environment with, 214
QATest, 212
ClearQuest MultiSite (CQMS), 253–254
ClearQuest to Project Tracker integration, 158–159
ClearQuest Test Management (CQTM)
overview of, 6
RQM replacing, 307
state-based record types in tests, 309
ClearQuest Tool Mentor
creating test environment with ClearQuest tools, 214–216
creating test environment with database vendor tools, 212–214
importing records with references, 208–210
importing updates, 210–211
overview of, 208
ClearVision Subversion, ClearQuest integration with, 176
CCRC (ClearCase Remote Client), 172
defining client types, 29–30
Eclipse. See Eclipse client
interactions with resources on server, 173
representation of data in ClearQuest and, 117–118
Cloning hook, for creating parent from child record, 123–126
Closing pattern
implementing in ClearQuest, 223–224
implementing in Jazz, 224–225
overview of, 37
suggested fields, 222–223
Closure stage, in workflow item lifecycle, 51
CM (Configuration Management) API, creating new ClearQuest integrations, 172–175
CMMI (Capability Maturity Model Integration), 83, 103
Code generation, list of RTC integrations by category, 191
Code reuse, 105
Collaboration
in Jazz-based C/ALM solution, 354
list of RTC integrations by category, 191
Collaborative ALM. See C/ALM (Collaborative ALM)
Comma-separated value (CSV) format, importing and, 204
Communication diagrams, workflows in, 44
Communication Manager (CM) API, creating new ClearQuest integrations, 172–175
Components
internal impacts on, 88
in promotion process, 376–379
relationships in integrated solution architecture, 368
Convert Full_Name to Login_Name hook, 122–123
Corrective actions
assigning solution providers, 91
data related to, 82
documenting, 92
prioritization of, 91
CQ-ALM schema. See ALM (Application Lifecycle Management) schema
CQ CM API JNI (Desktop) provider, 172–173
CQ CM API WAN (Network) provider, 172
CQMS (ClearQuest MultiSite), 253–254
CQTM (ClearQuest Test Management)
overview of, 6
RQM replacing, 307
state-based record types in tests, 309
Crystal reports, as metrics tool, 285–286
CSV (comma-separated value) format, importing and, 204
Custom Section wizard, 319
Customer role, in defect and change management, 131
Customizing test work items, in RQM
default work items, 317–318
execution states, 322–323
organizing test information using categories, 320–321
overview of, 316–317
setting permissions for customization, 321–322
testing specific work items, 318–320
Customizing work items
ClearQuest record types, 18–19
comparing ClearQuest and Jazz customization elements and terms, 15–17
elements that can be customized, 14
Jazz work items, 17–18
overview of, 13–14
D
Dashboards
comparing ClearQuest and Jazz customization areas, 17
creating monitoring viewlets, 300
in RTC Scrum process, 336–337
Data
accessing records, 114–115
attachments, 100–103
Back Reference field, 110–113
Convert Full_Name to Login_Name hook, 122–123
corrective actions, 91–92
creating parent from child record, 123–126
customizing work items, 14
defining fields, 35
description of work items, 83–86
environment information, 87–88
external impacts, 89–91
hard-coded data in hooks, 272–274
HasAttachment hook, 120–121
history of work items, 96–98
import/export, 163–164
importing initial data during deployment, 204–206
integration at data-level, 154
integration in Jazz-based C/ALM solution, 354
internal impacts, 88–89
Limit Attachment size hook, 121–122
links, 115–116
location information, 86–87
metrics, 284
multiple relationships, 108–109
object relations, 106
ownership of work items, 99
purposes of accumulating, 81–83
quality assurance and, 103–104
references to unique keys and, 113
referencing objects, 114
replacing unique keys, 115
representation in ClearQuest, 117–118
representation in Jazz, 118–119
requestor information, 98–99
scripts for data representation, 120
single relationships, 106–107
state-based objects, 105
stateless objects, 105–106
storing in fields, 7
summary, 126
test artifacts in RQM, 308
test-related, 95–96
time-related, 92–94
Data Hierarchy pattern
implementing, 233
overview of, 39
Data warehouse, in Jazz repository, 303–304
Database servers, in infrastructure architecture, 30
Database vendor tools, for creating test environment, 212–214
Databases
change management database, 28–29
choosing type in Analysis & Design, 32–33
determining number to create, 33
hook for performing lookup on external, 171
moving, 214–216
system test and database size, 200
test configuration for, 251
viewing properties of, 213–214
Dead End pattern
design of, 39
implementing in ClearQuest, 231
implementing in Jazz, 232
Debugging
BASIC utilities for, 261
using MsgBox() function, 255–256
using OutputDebugString() method, 256–258
using tracing information, 258–260
Decision stage, in workflow item lifecycle, 50–51
Dedicated actions, in subflow for gathering more information, 70–76
Default work items, 317–318
Defects
change requests due to, 4
creating task to fix, 370–371
default work items in Jazz, 317
key roles in defect and change management, 131
quality assurance and, 103
test artifacts in RQM, 308–309
tracking, 191
Defect_Validation hook, 147–149
Deferring stage, in workflow item lifecycle, 52
Deleting stage, in workflow item lifecycle, 52
Demilitarized zones (DMZs), defining infrastructure architecture, 30
Dependent integrations, ClearQuest, 158–162
Deployment discipline
following up on system adoption, 207
importing initial data, 204–206
installation phase, 202
overview of, 201
preparation phase, 201
setting up environment, 202–203
training phase, 206
Deployment plan, 201
Description field, for work items, 84
Descriptive data, 83–86
Design. See Analysis & Design discipline
Design models, reviewing/signing off on, 40
in Analysis & Design, 36–40
implementing Child Control pattern, 229–231
implementing Closing pattern, 222–225
implementing Data Hierarchy pattern, 233
implementing Dead End pattern, 231–232
implementing Parent Control pattern, 226–229
implementing Superuser Modification pattern, 233–234
implementing Triage pattern, 224–225
Designing forms and tabs, 243–245
Developer Taskboard, in RTC Scrum process, 336
Developers
data providing historical information for, 81
defining client types, 30
testing releases, 250–252
work on activities in integrated solution, 368–369
Development
being prepared for future requirements, 277
Child Control pattern, 229–231
choosing scripting language, 261
Closing pattern, 222–225
coding hooks for parallel development, 241
with common schema (ALM), 222
comparing/merging schema versions, 245–249
CQMS (ClearQuest MultiSite) issues, 253–254
Data Hierarchy pattern, 233
Dead End pattern, 231–232
dealing with long selection lists, 265–270
debugging using MsgBox() function, 255–256
debugging using OutputDebugString() method, 256–258
debugging using tracing information, 258–260
designing forms and tabs, 243–245
developer testing, 250–252
exporting/importing schema portions, 237–238
hard-coded data and, 272–274
list of RTC integrations by category, 191
naming conventions, 262–263
organizing global scripts by subject, 262
overview of, 221
packages, 238–239
parallel development, 240–241
Parent Control pattern, 226–229
promoting release to production, 252–253
record types in parallel development, 241–243
releasing versions to production, 250
resources for, 277–278
session variables in, 239–240
storing hooks externally, 249–250
storing old_id field for future import, 264
summary, 278
Superuser Modification pattern, 233–234
system testing, 252
Triage pattern, 224–225
understanding when stateless record type is required, 261
unique keys and, 261–262
updating dynamic lists, 271–272
Web-related considerations, 274–276
writing reusable code, 234–237
Diagrams. See also Graphics
defining and documenting requirements, 25
entity relationships. See ERD (entity relationship diagram)
in high-level design, 34
process diagram in change management, 47–48
state transition, 45–46
states, 47
workflows in activity diagrams, 44
Disciplines
Analysis & Design. See Analysis & Design discipline
ClearQuest Tool Mentor and. See ClearQuest Tool Mentor
Deployment. See Deployment
Implementation, 197–199
Jazz Tool Mentor and, 217–219
Maintenance, 207–208
overview of, 197
Requirements. See Requirements discipline
resources for, 220
summary, 220
Testing, 199–200
DMZs (demilitarized zones), defining infrastructure architecture, 30
Documentation
changes affecting, 90
of corrective actions, 92
gathering initial, 23
of requirements, 25–28
DOORS, RQM integrations, 185
Duplicating stage, in workflow item lifecycle, 52–53
Dynamic change state, 60–61
Dynamic lists
adding to choice lists, 273
updating, 271–272
Dynamic workflow
moving automatically between states, 57–59
overview of, 56
record types in, 56
single record type having multiple state machines for each issue type, 59–61
single record type having state machine for each issue, 61–65
state transition and, 56–57
E
E-mail notification. See Notification
E-mail Reader service, example of ClearQuest integration, 164–167
Eclipse client
creating process template using, 217–219
creating project using process template, 217–219
customizing work items, 17
import/export tool in, 163–164, 208
setting permissions for test customization, 321–322
Eclipse Designer
association by field label, 109
comparing/merging schema versions, 241, 245–249
comparing with Windows version of ClearQuest Designer, 18–19
exporting forms with, 244–245
supporting parallel development, 241
Editor presentations, Jazz, 2
Effort required
estimating in requirements gathering, 27–28
storing in work tasks, 93–94
Electronic signatures
in access control and security, 289
in ClearQuest governance, 295–296
Elements, work item
applets, 12
attachments, 11
customizing work items and, 14
data, 7
links to other work items, 11–12
overview of, 7
pictures or graphics, 12
presentation forms, 7–9
roles, 13
rules, 11
workflows, 9–10
Enhancements
change requests due to, 4
test artifacts in RQM, 309
Entities, defining data fields, 35
Entity relationship diagram. See ERD (entity relationship diagram)
Enumeration, Jazz, 3
Environment
creating test environment with ClearQuest tools, 214–216
creating test environment with database vendor tools, 212–214
data related to, 82
fields related to system configuration, 87–88
setting up during deployment, 202–203
ERD (entity relationship diagram)
creating record types in ClearQuest, 198
creating work item types in Jazz, 199
in high-level design, 34
Errors, fixing import. See also Defects, 205–206
Estimation of man-hours, in requirements gathering, 27–28
ETL (extract, transform, load), Insight tool for, 287
Excel, importing record from, 168
Execution states, in RQM test process, 322–323
Export. See Import/export
External impacts
applications and, 89
data related to, 82
documentation affected by changes in, 90–91
training materials impacted by changes, 91
users and, 89
Extract, transform, load (ETL), Insight tool for, 287
F
Features, change requests for adding, 4
Field behaviors, ClearQuest, 3
Field hooks
choice list. See Hooks, choice list
default value. See Hooks, default value
permission. See Hooks, permission
value changed. See Hooks, value changed
validation. See Hooks, validation
Fields, ClearQuest
category fields for organizing information, 320–321
compared with Jazz Work item attribute, 2
customizing edit permission, 15
defining, 35
mapping record fields during import, 210
storing data in, 7
storing test data in, 95–96
time-related, 94
user-defined, 356–358
Fields, making Web forms with dependent fields, 275
Firewalls, 30–32
Forms, ClearQuest
compared with Jazz Editor presentations, 2
designing, 243–245
Presentation forms, 7–9
representation of data in ClearQuest, 117–118
user-defined fields in, 357
Forms, Jazz. See Editor presentations
Forms, making Web forms with dependent fields, 275
Functional requirements, listing, 27
Functional Tester. See RFT (Rational Functional Tester)
Functionality packages, 238
G
GDD (Globally Distributed Development), 253–254
Glossary, in defining and documenting requirements, 25
Governance
in ALM, 298
in ALM schema, 297
in ClearQuest, 290
electronic signatures, 295–296
monitoring and, 289
monitoring in ClearQuest, 297
monitoring in RTC, 300
overview of, 287–288
permissions and, 288–289
permissions in ClearQuest, 290–293
permissions in RTC, 299
process control and automation and, 288
process control in ALM, 297
process control in ClearQuest, 290
process control in RTC, 299
reports, 366
resources for, 301–302
roles in ALM, 298
in RTC, 298
security context in ALM, 297–298
security context in ClearQuest, 294–295
summary, 305
Graphical user interface (GUI), designing forms and tabs and, 243–245
Graphics. See also Diagrams
defining and documenting requirements, 25
in metrics strategy, 280–281
presentation insertions, 12
Group box, ClearQuest, 2
Groups, ClearQuest
implementing roles with, 131–133
query listing members for access control, 144–145
GUI control, ClearQuest, 2
GUI (graphical user interface), designing forms and tabs and, 243–245
H
Hard-coded data, 272–274
Hardware, location information for, 87
HasAttachment hook, 120–121
Headline field, in work item description, 83–84
Hide data, customizing work items, 15
Histograms, in metrics strategy, 280–281
History
data and, 83
reasons for saving history of work items, 96–98
History view, in Eclipse Designer, 245–246
Hooks
Action hooks, in ClearQuest, 3
automation implemented with, 381–382
button hooks in Web development, 274–275
Choice List hook, 114, 144, 150, 236–238, 270–271
cloning hook for creating parent from child record, 123–126
code reuse with, 234–237
coding hooks for parallel development, 241
Commit hook, 230
Convert Full_Name to Login_Name hook, 122–123
default value, 266
external storage in Perl not BASIC, 261
hard-coded data in, 272–274
HasAttachment hook, 120–121
initialization, 64, 70–72, 224, 235
Limit Attachment size hook, 121–122
for lookup on external database, 171
organizing global scripts by subject, 262
storing externally, 249–250
validation, 33, 76–78, 147–149, 228
value changed, 73–75, 84, 135, 266–267
HP Mercury Test Director and Quality Center, 176
I
IBM Administrator, dependent integration with ClearQuest, 158
IBM PureCoverage, 157
IBM Purify, 157
IBM Quantify, 158
IBM Rational Build Forge. See Build Forge
IBM Rational ClearCase. See ClearCase
IBM Rational ClearQuest. See ClearQuest
IBM Rational DOORS, 185
IBM Rational Requirements Composer. See Requirements Composer
IBM RequisitePro. See RequisitePro
IBM RTC. See RTC (Rational Team Concert)
IBM TeamTest, 159
IBM Tivoli. See Tivoli
IBM Unified Change Management (UCM). See UCM (Unified Change Management)
Icons, in Jazz workflow, 68
IDEs (Integrated development environments), list of RTC integrations by category, 191
Idioms. See Design patterns, implementing
Implementation discipline
ClearQuest tasks, 198
Jazz tasks, 199
purpose of, 197–198
Import/export
creating new ClearQuest integrations, 163–164
fixing import errors, 205–206
importing data during deployment, 204–205
importing records with references, 208–210
importing updates, 210–211
Process Template, 217–219
schema portions, 237–238
validating imported data, 206
Import tool, ClearQuest, 205
Independent integrations, ClearQuest, 156–158
Individual level metrics, for productivity and efficiency, 280
Information gathering subflow, 69–76
Infrastructure, defining infrastructure architecture, 30–32
Initialization pattern, ClearQuest, 36
Insight tool
for metrics, 287
release burndown and velocity charts, 345
Installation phase, of deployment, 202
Integrated development environments (IDEs), list of RTC integrations by category, 191
Integrated solution architecture (ClearCase, ALM, and Build Forge)
component relationships in, 368
continuous build and validation process, 369–370
creating task to fix defect, 370–371
developer work on activities in, 368–369
overview of, 367
periodic releases, 371–372
working on test artifacts, 372–373
Integration, ClearQuest
built-in, 156
CM API and, 172–175
creating new, 162
dependent, 158–162
E-mail Reader service example, 164–167
import/export and, 163–164
independent, 156–158
OSLC REST API and, 175–176
overview of, 155–156
Perl and BASIC API and, 167–172
resources for, 195–196
summary, 196
third-party offerings, 176–177
Web services and XML and, 176
Integration, introduction to, 153–155
Integration, Jazz
build engines, 190–191
Build Forge, 187
building new integrations, 192
ClearCase Connector, 188
ClearQuest Bridge, 180–183
ClearQuest Connector, 177–180, 188–190
IBM Rational DOORS, 185
JIA (Jazz Integration Architecture), 192–193, 355
list of RTC integrations by category, 191–192
overview of, 177
Rational test automation tools, 185–187
RequisitePro to RQM, 183–185, 310
resources for, 195
REST API and, 193–195
RQM (Rational Quality Manager) and, 177
RTC (Rational Team Concert) and, 187–188
STAF (Software Testing Automation Framework), 187
summary, 196
SVN (Subversion), 190
Integration packages, 238
Internal impacts
on components, 88
data related to, 82
on releases, 88–89
Interviews, in requirements gathering, 23–24
Issues, data in description of, 81
Iterations
in ALM schema, 346
describing ClearQuest data objects for Agile process, 338
planned effort for, 345–346
in RTC Scrum process, 332–334
J
Java APIs, 172–175
Jazz. See also RTC (Rational Team Concert)
Agile, Realization in RTC, 332–339
C/ALM (Collaborative ALM) and, 354–356
comparing ClearQuest and Jazz terminology, 2–3
comparing customization elements and terms with ClearQuest, 15–17
customizing work items, 17–18
databases supported by, 33
governance and. See RTC (Rational Team Concert) governance
implementation tasks, 199
integrations. See Integration, Jazz
monitoring with Jazz, 302
process control with Jazz, 301
permission with Jazz, 301
report resources, 302–303
representation of data in, 118–119
roles in, 142–143
setting up customizations during deployment, 204
setting up environment during deployment, 202–203
types of links to Jazz work items, 115–116
workflow, 66–68
Jazz Foundation Services, in C/ALM solution, 355
Jazz Integration Architecture (JIA)
building new Jazz integrations, 192–193
in Jazz-based C/ALM solution, 355
Jazz Tool Mentor
creating project using process template, 217–219
overview of, 217
JIA (Jazz Integration Architecture)
building new Jazz integrations, 192–193
in Jazz-based C/ALM solution, 355
L
License servers, defining infrastructure architecture, 30–31
Limit Attachment size hook, 121–122
Links
to attachment files (CQ), 101–102
types of (Jazz), 115–116
to work items, 11–12
List View, Back Reference field and, 110
Lists
choice lists. See Choice list, Clear Quest
dynamic lists. See Dynamic lists
in describing physical artifacts involved in change, 86–87
locating items/components that must be changed, 82
Login name, converting full name to, 122–123
Lookups, hook for performing lookup on external database, 171
M
Maintaining requirements, 28–29
Maintenance discipline
defining change process, 207–208
improving maintainability, 208
ongoing support, 208
overview of, 207
Manage Section wizard, 318
Management (decision makers)
benefits of integration to, 154
data providing information for managers, 81
getting agreement regarding requirements, 28
Manual Tester, RQM replacing, 307
Mastership, in multisite environment
addressing changes to, 253–254
testing, 254
MCIF (Measured Capability Improvement Framework), 287, 301
Members, 311–312
Metrics
BIRT (Business Intelligence and Reporting Tools), 286
categorizing by levels, 280
ClearQuest, creating Agile schema in, 345
Crystal reports, 285–286
data supporting, 284
Insight tool for, 287
overview of, 279–280
Publishing Engine for document generation, 287
Report Server for managing ClearQuest reports, 286–287
resources for, 301–302
strategy for, 280–284
summary, 305
tools for, 284–285
units for time-related data, 94
Microsoft Visual Source Safe, integration with ClearQuest, 161
Modeling. See also UML (Unified Modeling Language)
list of RTC integrations by category, 191
promotion process, 379–382
Monitoring
in ClearQuest, 297
in governance generally, 289
in Jazz, 300
MsgBox() function, debugging with, 255–256
Multiple relationships, object relations in ClearQuest, 106, 108–109
Multiple roles
implementing implicitly, 134
overview of, 130
setting choices based on, 146–147
N
Naming conventions, in schema development, 262–263
New session, notification hook, 58
Notification pattern, 36
Notifications
Assign action and, 58
customizing work items, 16
in debugging, 256
roles in, 127
rules governing, 11
setting environment, 202
SLAs and, 365–366
Not_Resolved state type, 54
O
Objects
relations. See Relationships
state-based, 105
stateless, 104–106
test artifacts, 308–309
old_id field, storing for future reference, 264
Ongoing support, in maintenance discipline, 208
Open Service for Lifecycle Collaboration. See OSLC (Open Service for Lifecycle Collaboration)
Open Unified Process (OpenUP), 45
OpenUP (Open Unified Process), 45
Operating systems (OSs), environment information and, 87–88
Operation behavior or extensions, Jazz, 3
Organization level metrics, for productivity and efficiency, 280
OSLC (Open Service for Lifecycle Collaboration)
building new Jazz integrations, 193–195
in Jazz-based C/ALM solution, 355
REST API compliance with, 175–176
OSs (operating systems), environment information and, 87–88
OutputDebugString() method, debugging with, 256–258
Ownership
assigning solution providers in process of taking corrective actions, 91
data, 99
defined, 130
misassignment of, 128–129
unassigned changes and, 128
P
Packages (in ClearQuest)
creating, 239
enabling for editing, 239
overview of, 238–239
types of, 238
packageutil, creating packages with, 239
Parallel development
coding hooks for, 241
designing forms and tabs, 243–245
overview of, 240–241
record types in, 241–243
storing hooks externally and, 249–250
Parent/Child control, 110–112
Parent Control pattern
design of, 38
implementing, 226–229
Parent records, creating from child record, 123–126
Performance benchmarking, by Web administrators, 200
Performance Tester. See RPT (Rational Performance Tester)
Perl
choosing scripting language and, 261
Convert Full_Name to Login_Name hook, 122–123
creating new ClearQuest integrations, 167–172
HasAttachment hook, 120–121
Limit Attachment size hook, 121–122
storing hooks externally, 249–250
use of session variables, 240
Permissions
in ClearQuest, 290–293
in governance, 288–289
in Jazz, 299
Jazz permissions compared with ClearQuest Access control, 3
for test customization, 321–322
workflow rules, 46
Petri nets, modeling workflows with, 43
Pictures, as presentation insert, 12
Plans, Jazz, 2
Postponing stage, in workflow item lifecycle, 52
Preconditions, Jazz, 3
Preparation phase, of deployment, 201
Presentation
customizing work items, 15
Jazz Presentation compared with ClearQuest GUI control, 2
representation of data, 118
Presentation forms, 7–9
Prioritization
of corrective actions, 91
in requirements gathering, 27
Process Configuration, customizing work items, 317
Process control
in ALM schema, 297
in ClearQuest, 290
in governance, 288
in Jazz, 299
Process entities, in promotion request system, 377–378
Process lifecycle
managing release promotion and, 374–375
promotion requests and, 379
Process Template, Jazz
compared with ClearQuest Schema, 2
creating new project area with imported template, 219
exporting, 217–218
generating, 217
importing, 218–219
Processes
components in promotion process, 376–379
integration at process-level, 154
representation in workflows, 45–49
rules in promotion process model, 379–381
WBM (WebSphere Business Modeler), 47–48
Product backlog
describing ClearQuest data objects for Agile process, 338
ranking Jazz stories in, 330–331
showing Jazz iterations in, 331–332
Project level metrics, for productivity and efficiency, 280
Project management, list of RTC integrations by category, 192
Projects
classification of project-related work items, 6–7
work projects in ClearCase, 368–369
Promotion process
model for promotion process, 379–382
overview of, 374
process components, 376–379
solutions, 375
status assessment, 374–375
Promotion work items, 6
Publishing Engine, for document generation, 287
PureCoverage, integration with ClearQuest, 157
Purify, integration with ClearQuest, 157
Q
Quality assurance
benefits of integration to, 154
Quality indicators, in reports, 284
Quality management, list of RTC integrations by category, 192
Quality Manager. See RQM (Rational Quality Manager)
Quantify, integration with ClearQuest, 158
Queries, comparing ClearQuest and Jazz customization areas, 17
Query wizard, 285
Questionnaires, in requirements gathering, 24–25
Quick Information section, Jazz, 2
R
R (ready) state type, UCM, 54
Ranking stories, in RTC Scrum process, 330–331
Rational AppScan, integration of RQM and RTLM with, 185–187
Rational Build Forge. See Build Forge
Rational ClearCase. See ClearCase
Rational ClearQuest. See ClearQuest
Rational CM API. See CM (Configuration Management) API
Rational DOORS, 185
Rational Functional Tester (RFT)
automating test scripts with, 315
integration of RQM and RTLM with, 185–187
Rational Insight tool. See Insight tool
Rational Performance Tester (RPT)
integration of RQM and RTLM with, 185–187
test simulation with, 200
Rational Publishing Engine, for document generation, 287
Rational Quality Manager. See RQM (Rational Quality Manager)
Rational Requirements Composer (RRC). See Requirements Composer
Rational RequisitePro. See RequisitePro
Rational Team Concert Eclipse client. See Eclipse client
Rational Team Concert (RTC). See RTC (Rational Team Concert)
Rational test automation tools, 185–187
Rational Test Lab Manager. See RTLM (Rational Test Lab Manager)
Rational Unified Process (RUP). See RUP (Rational Unified Process)
Rational University, 206
Reassign action, 70
Recalculate Choice list property, 265–267
Record forms, representation of data in ClearQuest, 117
Record type family, ClearQuest, 2
Record types, ClearQuest
compared with Jazz Work item type, 2
creating parent record from child record, 123–126
customizing, 18–19
in dynamic workflow, 56
in parallel development, 241–243
single record type having multiple state machines for each issue type, 59–61
single record type having state machine for each issue, 61–65
stateful, 56
stateless, 104–106
user-defined roles and, 137–138
using roles stateless record type with static roles, 136–137
Records
accessing via referencing, 114–115
importing updates to existing, 210–211
importing with references, 208–210
mapping fields during import, 210
with more than one field as unique key, 261–262
permissions for access control and security, 289
Security Context and, 293
test artifacts in RQM, 308
Reference_List
Back Reference field and, 110–113
types of object relations in ClearQuest, 106, 108–109
References
importing records with references, 208–210
to objects, 114
pointing to unique keys, 113
types of object relations in ClearQuest, 106–107
Rejecting stage, in workflow item lifecycle, 52
Relationships
accessing records, 114–115
Back Reference field in object relations, 110–113
links, 115–116
multiple, 108–109
overview of, 106
references to unique keys and, 113
referencing objects, 114
replacing unique keys, 115
single, 106–107
between test artifacts, 308–309
Release work items, 6
Releases
burndown and velocity charts, 345
developer testing, 250–252
internal impacts on, 88–89
managing promotion process, 374
model for promotion process, 379–382
overview of, 250
periodic, 371–372
process components, 376–379
promoting to production, 252–253
solutions, 375
status assessment, 374–375
system testing, 252
Reloading records, notification hook for, 58
Reopening stage, in workflow item lifecycle, 51–52
Report Server, for managing ClearQuest reports, 286–287
Reports
comparing ClearQuest and Jazz customization areas, 17
defects, 316
in metrics strategy, 281
test defects, 316
Representation of data
in ClearQuest, 117–118
in Jazz, 118–119
scripts in ClearQuest, 120
Request record type
describing data objects for Agile process, 338
suggested fields for, 339–340
workflows of, 343–344
Requestor information, 98–99
Requirements Composer (RRC)
documenting requirements, 25–26
Requirements discipline
Agile practices applied to, 28
analyzing requirements in establishing test strategy, 310
default work items in Jazz, 317
defining and documenting, 25–28
gathering initial documentation, 23
getting agreement regarding, 28
interviews for gathering, 23–24
maintaining, 28–29
overview of, 23
questionnaires for gathering, 24–25
resources, 40
section of test plan, 311
summary, 40–41
test artifacts in RQM, 308–309
verifying test case coverage of, 315
Requirements management, list of RTC integrations by category, 192
RequisitePro
analyzing requirements in establishing test strategy, 310
dependent integration with ClearQuest, 159
documenting requirements, 25
managing release promotion and, 375
RQM integrations, 183–185
Reserved names, in schema development, 263
Resolution pattern, 40
Resolution stage, in workflow item lifecycle, 51
Resolution states, 53–55
Resolutions
effort required for, 93
in Jazz workflow, 67
Resolved state type, 54
Resources
client interactions with resources on servers, 173
enhancements in Jazz version 2.0, 19
Responsible
defined, 130
setting based on role object, 147–149
setting based on Single role, 145
unassigned changes and, 128
REST API
building new Jazz integrations, 193–195
creating new ClearQuest integrations, 175–176
Results, test artifacts in RQM, 308
Reusable assets
exporting/importing schema portions, 237–238
list of RTC integrations by category, 191
overview of, 234
packages, 238–239
Review, of test plan, 313
RFT (Rational Functional Tester)
automating test scripts with, 315
integration of RQM and RTLM with, 185–187
Risk work items, 6
Role-based access control, 379
Roles
in access control hook, 144–145
in ALM governance, 298
in ALM schema, 140–141
areas and groups and, 131
auto-assignment of, 145–149, 273–274
change request process and, 131
comparing Agile and ALM schema, 346–347
customizing work items, 16
defined, 130
implementing implicitly, 133–136
implementing with groups, 132–133
issues/typical problems addressed by, 128–129
in Jazz, 142–143
in Jazz governance, 299
organizing questionnaires by, 25
overview of, 127
in process model, 376–377
in Scrum process, 334–335
security and, 139
stateless record type and, 136–137
summary, 151
terminology related to and types of, 130
users activities and, 13
workflow rules, 46
RPT (Rational Performance Tester)
integration of RQM and RTLM with, 185–187
test simulation with, 200
RQM (Rational Quality Manager)
Build Forge integration with, 187
ClearQuest Bridge, 180–183
ClearQuest Connector, 177–180
combining with DOORs in Jazz integrations, 185
combining with RequisitePro in Jazz integrations, 183–185
creating dashboard viewlets for monitoring, 300
customizing work items, 17
databases supported by, 33
integration at data-level, 154
integration with ClearQuest, 163, 180–183
integration with Rational test automation tools, 185–187
integration with STAF, 187
integrations, 177
roles in, 142
setting up Jazz environment during deployment, 203
test entities and relationships, 307–310
test plan and test case objects in, 6
testing work items. See Testing work items, in RQM
what it is, 307
RTC (Rational Team Concert)
as ALM tool, 7
Build engines, 190–191
ClearCase Connector, 188
ClearQuest integration with, 188–190
customizing work items, 17
databases supported by, 33
dependent integration with ClearQuest, 163
implementing Closing pattern, 224–225
integrations, 187–188
Jazz integration with ClearQuest, 180–183
listing integrations by category, 191–192
representation of data in Jazz, 118–119
roles in, 142
setting permissions for test customization, 321–322
setting up Jazz environment during deployment, 203
support for customization from Web clients, 119
SVN (Subversion) used for source control, 190
RTC (Rational Team Concert) governance
monitoring in, 300
overview of, 298
permissions in, 299
process control in, 299
RTC (Rational Team Concert), Scrum process in
dashboards, 336–337
Developer Taskboard, 336
iterations and sprint planning, 332–334
Scrum roles, 334–335
setting up multiple teams for multiple releases, 331–332
stories, 330–331
RTLM (Rational Test Lab Manager)
based on RQM, 307
built-in integrations, 177
integration at tools-level, 154
Rules
customizing work items, 16
governing change process, 11
workflow definition, 46
RUP (Rational Unified Process)
applying to change management, 21–22
definition of roles, 127
workflows in software development, 44–45
S
SCCB (Software Change Control Board), 131
Scenarios, in Jazz-based C/ALM solution, 355
Schedules, test artifacts in RQM, 308
Schema packages, 238
Schemas
ClearQuest schema compared with Jazz Process Template, 2
comparing/merging schema versions, 245–249
componentizing, 241–243
exporting/importing schema portions, 237–238
high-level design in ClearQuest, 33–34
upgrading, 253
use in development, 222
Scripts
choosing scripting language, 261
cloning hook for creating parent from child record, 123–126
Convert Full_Name to Login_Name hook, 122–123
for data representation, 120
for executing tests in RQM, 315–316
function Defect_AccessControl, 132
function Defect_Validation, 145, 147
function GetLoginfromFullName, 123
function SetRequiredness, 362
HasAttachment hook, 120–121
import script, 169–171
Limit Attachment size hook, 121–122
organizing global scripts by subject, 262
sub allowedactions_ChoiceList, 150
sub ALMActivity_Validation, 77
sub AssignApprover, 78
sub attachments_ValueChanged, 120
sub Bug_Initialization, 223
sub ChildrenStatus, 228
sub ChoiceList, 236
sub Comp_ChoiceList, 269
sub comp_level2_ChoiceList, 270
sub Defect_Commit, 229
sub Defect_Initialization, 234
sub Defect_Notification, 58
sub Defect_Validation, 227
sub EnhancementRequest_Initialization, 71–72
sub feature_CloneParentCR, 124
sub getEntityURL, 256
sub GetLoginfromFullName, 122
sub GetNextRole, 273
sub Issue_Initialization, 64
sub Issue_Notification, 60, 62
sub keywords_ValueChanged, 271
sub Limit_Attachment, 121
sub note_entry_ValueChanged, 75
sub Populate_list, 360
sub project_ValueChanged, 266
sub resolution_ChoiceList, 273
sub responsible_ChoiceList, 146
sub SetLog, 73
sub ucm_view_Permission, 292
sub userfieldvalue_2_ChoiceList, 267
test artifacts in RQM, 308
Scrum
dashboards, 336–337
Developer Taskboard, 336
framework for Agile development, 326–329
iterations and sprint planning, 332–334
Realization with ClearQuest, 339–348
roles, 334–335
setting up multiple teams for multiple releases, 331–332
stories, 330–331
Section, Jazz
compared with ClearQuest Group box, 2
customizing test work items, 318–320
representation of data and, 118
setting permissions for test customization, 321–322
Security
Access_Control hook in ClearQuest, 128
defining infrastructure architecture, 31
governance and, 288–289
roles and, 139
Security Context feature, ClearQuest
in ALM schema, 297–298
in ClearQuest governance, 293–295
overview of, 139
records and, 293
Security testing, list of RTC integrations, 192
Selection lists. See Choice list, Clear Quest
Sequence diagrams, workflows in, 44
Servers
client interactions with resources on, 173
defining client types, 30–31
installing during deployment, 202
for managing ClearQuest reports, 286–287
Service Level Agreements. See SLAs (Service Level Agreements)
Service Request Manager (SRM), 154, 172
Session variables, 239–240
Single relationships, types of object relations in ClearQuest, 106–107
Single roles
implementing implicitly, 134
overview of, 130
setting Responsible based on, 145–146
SLAs (Service Level Agreements)
activating rules, 365
background and examples, 363–364
defining rules, 364–365
external program for, 366–367
governance reports, 366
notifications, 365–366
overview of, 363
resources for, 383
SME (subject matter expert), 208
Software
internal impacts on components, 88
location information, 87
Software Change Control Board (SCCB), 131
Software development processes
OpenUP (Open Unified Process), 45
RUP (Rational Unified Process), 44–45
Software Testing Automation Framework (STAF), 187
Solution providers
assigning in process of taking corrective actions, 91
data providing information for, 81
key roles in defect and change management, 131
Solutions, in promotion process, 375
suggested fields for, 340–341
workflows of, 344–345
Sprints
in ALM schema, 348–349
describing ClearQuest data objects for Agile process, 338
in Scrum process, 332–334
SQL query
listing group members for access control, 144–145
listing in SLA, 368–369
SRM (Service Request Manager), 154, 172
STAF (Software Testing Automation Framework), 187
Stages, of workflow, 50–53
Stakeholders
getting agreement regarding requirements, 28
interviews for gathering requirements from, 23–24
key roles in defect and change management, 131
questionnaires for gathering requirements from, 24–25
State-based objects, 105
State group, Jazz, 2
State pattern, 36
State transition
diagramming, 45–46
in dynamic workflow, 56–57
moving automatically between states, 57–59
test artifact state transition constraints, 312
State transition matrix, ClearQuest
compared with Jazz Workflow, 2
creating, 49
workflow design with, 9
State transition tables, 9
State type, ClearQuest
compared with Jazz State group, 2
workflow and, 53–56
Stateful record types
ALM Security Context and, 297
overview of, 56
Stateless objects, 105–106
Stateless record types
ALM schema roles, 140
ALM Security Context and, 297
importing, 205
overview of, 104–106
understanding when they are required, 261
user-defined roles and, 137–139
using roles stateless record type with static roles, 136–137
States
auto-change, 58–59
comparing ClearQuest state with Jazz state, 2
customizing test execution states, 322–323
diagramming, 47
dynamic change state, 60–61
in Jazz workflow, 66–67
workflow rules, 46
Static roles, 136
Status assessment, in promotion process, 374–375
Steps to Reproduce field, in work item description, 85
Stories, in Scrum process, 330–331
Storyboards
defining and documenting requirements, 26
for functional requirements, 27
Subflows
for build approval, 76–78
deviation needed to gather more information, 69–76
overview of, 68–69
Subject matter expert (SME), 208
Submission stage, in workflow item lifecycle, 50
Submit forms, representation of data in ClearQuest, 117
Subversion (SVN), 190
Superuser Modification pattern
design of, 39–40
implementing, 233–234
Supplementary specifications, in requirements gathering, 27
Support, in maintenance discipline, 208
SVN (Subversion), 190
System
access permissions in ClearQuest, 290–291
defining scope of in requirements gathering, 26–27
following up on adoption, 207
T
Tabs
comparing ClearQuest with Jazz, 2
designing, 243–245
representation of data in Jazz, 118
Task-Quality, default work items in Jazz, 317
Task record type, in ALM schema, 346, 348
Task-Review, default work items in Jazz, 317
Tasks
activity subclasses, 5
assigning members to, 311–312
creating task to fix defect, 370–371
default work items in Jazz, 317
Team Concert. See RTC (Rational Team Concert)
Team level metrics, for productivity and efficiency, 280
Teams
describing ClearQuest data objects for Agile process, 338
in Scrum process, 331–332
TeamTest, integration with ClearQuest, 159
Telelogic Harmony, 44–45
Termination dates, for actions, 92–93
Test Case field, in work item description, 85–86
Test cases
associating with requirements and verifying coverage, 315
categories for organizing information in, 320–321
creating and associating with test plan, 314
creating scripts for executing, 315–316
creating suite of, 316
customizing test work items, 316
test artifacts in RQM, 308–309
Test elements, in work item classification, 6
Test environment
creating with ClearQuest tools, 214–216
creating with database vendor tools, 212–214
promoting release to production, 252–253
storing hooks externally, 250
Test Lab Manager. See RTLM (Rational Test Lab Manager)
Test plan
assigning members to tasks, 311–312
categories for organizing information in, 320–321
creating, 311
creating test cases and associating with test plan, 314
customizing test work items, 316
reviewing, 313
test artifacts in RQM, 308–309
Test suite
creating, 316
test artifacts in RQM, 308–309
Testers
data providing historical information for, 81
in test process, 312–318
Testing stage, in workflow item lifecycle, 51
Testing work items, in RQM
analyzing requirements and establishing test strategy, 310
assigning members to test plan tasks, 311–312
creating scripts for executing test cases, 315–316
creating suite of test cases, 316
creating test cases and associating with test plan, 314
creating test plan, 311
customizing test execution states, 322–323
customizing test work items, 316–317
default work items, 317–318
executing tests, 316
organizing test information using categories, 320–321
reporting defects found during testing, 316
reviewing test plan, 313
setting permissions for test customization, 321–322
summary, 324
testing specific work items, 318–320
verifying test case coverage of requirements, 315
TestManager, RQM replacing, 307
Tests/testing
data related to, 82–83
developers in, 250–252
effort required for, 93
fields for test data, 95–96
integration of RQM and RTLM with test automation tools, 185–187
key roles in defect and change management, 131
overview of Testing discipline, 199–200
system testing, 252
working on test artifacts for integrated solution, 372–373
Third-party integrations, with ClearQuest, 176–177
Time-related data
amount of effort required, 93–94
overview of, 82
termination dates, 92–93
Tivoli
SRM (Service Request Manager), 154, 172
TPM (Tivoli Provisioning Manager), 163
Tools, for metrics
BIRT (Business Intelligence and Reporting Tools), 286
Crystal reports, 285–286
overview of, 284–285
rational Insight tool for, 287
Rational Publishing Engine for document generation, 287
Report Server for managing ClearQuest reports, 286–287
Tools, integration at tools-level, 154
TPM (Tivoli Provisioning Manager), 163
Tracing information, debugging with, 258–260
Training materials, external impacts on, 91
Training phase, in deployment discipline, 206
Transitions. See also State transition, 67
Transparency, in Jazz-based C/ALM solution, 354
Triage pattern
design of, 37–38
implementing in ClearQuest, 224–225
implementing in Jazz, 225
TSRM (Tivoli Service Request Manager). See SRM (Service Request Manager)
U
UCM (Unified Change Management)
integration with ClearQuest, 160–161
periodic releases, 371–372
state types and, 53–55
work projects in ClearCase, 368–369
working on test artifacts, 372–373
UML (Unified Modeling Language)
in high-level design, 34
modeling workflows with, 43
workflow design with, 9
workflows in, 44
Unified Process. See RUP (Rational Unified Process)
Unique keys
dealing with records with more than one field as unique key, 261–262
references to, 113–115
replacing, 115
Units of work
measuring time-related data, 94
time measurements, 284
Updates
dynamic lists, 271–272
importing, 210–211
User acceptance testing, in release process, 252
User-defined fields
in ClearQuest solution, 356–358
defining requiredness, 361–362
User-defined roles
ChoiceList hook for, 150
overview of, 137–139
User interface
defining, 36
designing forms and tabs, 243–245
Users
benefits of integration to, 154
business rules, 378–379
defining client types, 30
external impacts and, 89
following up on system adoption, 207
getting agreement regarding requirements, 28
ongoing support, 208
permissions for access control and security, 288–289
roles, 13
roles in different areas, 131
training, 206
User’s privileges, ClearQuest, 3
V
Validation
continuous build and validation process, 369–370
hook. See Hoocks, validation
of imported data, 206
Velocity charts, releases and, 345
Version control, list of RTC integrations by category, 192
VersionOne, ClearQuest integration with, 177
Visual Source Safe, ClearQuest integration with, 161
Vocabulary control, glossary in defining and documenting requirements, 25
W
W (waiting) state type, UCM, 54
WBM (WebSphere Business Modeler), 47–48
Web administrators, performance benchmarking by, 200
Web clients
limitations of, 276
support for customization from, 119
testing releases with, 252
Web-related development considerations
enabling button hooks, 274–275
limitations of Web clients, 276
making forms with dependent fields, 275
overview of, 274
Web servers, defining infrastructure architecture, 30
Web services, ClearQuest integration with, 176
WebSphere Business Modeler (WBM), 47–48
Windows version, of ClearQuest Designer, 18–19, 213
Work item attribute, Jazz, 2, 7
Work item type category, Jazz, 2
Work item type, Jazz, 2
Work items
classification of. See Classification of work items
comparing ClearQuest and Jazz terminology, 2–3
customizing. See Customizing work items
defined, 1
elements. See Elements, work item
summary, 20
in test process. See Testing work items, in RQM
what’s new in 2.0 work items, 19
Workflows
in ALM schema, 65–66
in clearQuest, creating Agile schema in, 343–345
customizing work items, 15
defining, 35
dynamic. See Dynamic workflow
Jazz, 66–68
Jazz workflow compared with ClearQuest State transition matrix, 2
process representation, 45–49
software development processes, 44–45
stages in, 50–53
state types, 53–56
subflows. See Subflows
summary, 78–79
Workspace Versioning and Configuration Management (WVCM), 172–173
WVCM (Workspace Versioning and Configuration Management), 172–173
X
XML, ClearQuest integration with, 176