|
Product Change Requests
Changes to Cadence products are identified by a Cadence Change Request (CCR).
A CCR is a unique identifier and tracking mechanism within the Cadence Change
Management System (CCMS) to document a product issue or enhancement. CCR's are
identified by a unique number in the CCMS database and this is cross-referenced
to a Service Request. CCR status is viewable on SourceLink.
CCR Severity
Severity is an objective indicator of how bad a problem is technically.
Severity is an attribute of the problem itself as characterized by Cadence
and the requester and has the following 3 levels of distinction.
|
0 - No Workaround ("S0")
- A production-stopping software bug with no workaround that is acceptable to the customer
- Associated Service Request remains open until the CCR is resolved and customer has
confirmed the fix
- For faster resolution of your issue, please provide a test case to the SR owner
1 - Workaround ("S1")
- A production-stopping defect with an acceptable workaround
- Severely production limiting defect having negative impact on customer productivity
- Associated Service Request remains upon until it has been confirmed that the customer has
been notified of the fix
2 - Minor ("S2")
- An enhancement to existing functionality that will improve the use of the product
- Once assigned, Service Request is closed.
|
CCR URGENCY
Urgency addresses the need for quicker than standard response and has the
following 2 levels of distinction.
|
|
U - Urgent
- Immediate help getting customer working is required
- Issue is stopping tape out at the customer site
- Issue has a huge financial impact on the customer and/or Cadence
- Workaround is unacceptable to the customer because it requires many error-prone, often
repeated, manual steps
- Workaround adds significant time to customer's design efficiency
- Performing the workaround requires additional engineering resources
D - Default
- Fix needed when available under standard maintenance planning/fixing cycles
|
| 
