1. CQ Best Practise and Collaboration Team © 2006 IBM Corporation Version: 0.1 (DRAFT) GDALM Architecture Elevator Pitch Bob Myers

2. CQ Best Practise and Collaboration Team © 2006 IBM Corporation 2December 2006 Schema Description  Customer Complete Development Lifecycle  Developed for Single and Multisite ClearQuest Briefly describe the schema in one or two sentences.

3. CQ Best Practise and Collaboration Team © 2006 IBM Corporation 3December 2006 Key Features Of This Schema 1.Role-based record structure –Less hook code, smaller record, faster performance, distributed parallel development, flexible but finite process 2.Largely Multisite and Optimistic locking agnostic –No need to have mastership or single Ownership to do most updating 3.Surfaces Fix in build status to tester –Minimizes Development-Tester-Doc communication List up to three key features of your schema which provide benefit to the teams that use it. For each feature describe the benefit associated with the feature.

4. CQ Best Practise and Collaboration Team © 2006 IBM Corporation 4December 2006 Lessons Learned 1.CQ does support mastership and ODBC Optimistic agnostic updating and same solution works for both –Record_Script_Alias Actions to create records, BackReferencing to link them is supported OOTB 2.Ownership is an important concept in design –Ownership may be by a single or multiple individuals and the design needs to accommodate both 3.CQ Data Pathing and Parent Child Controls for Reference_List fields with BackReferences are useful –The design of a CQ schema should use these as building blocks What lessons (up to three) have you learned from developing this schema? For each lesson describe how this will affect how you approach things next time around.

5. CQ Best Practise and Collaboration Team © 2006 IBM Corporation 5December 2006 Key Features of ClearQuest List up to three key features of ClearQuest which provide benefit to the teams that use it. For each feature describe the benefit associated with the feature. 1.Parent Child Controls with BackReferences and Data Pathing –Relates role-based record types and surfaces entity relationships in a User-friendly way 2.Record_Script_Alias Actions –Makes process CQMS mastership and Optimistic locking non-restricting 3.Ownership is important –Single and multiple Owners are both important in different ways