Beruflich Dokumente
Kultur Dokumente
Revision History
Table 1: Revision History
VERSION
1.0 Draft
NAME
Victoria Popescu
Elisabeta Ciora
DATE
Sept. 9, 2011
1.1 Draft
Victoria Popescu
Elisabeta Ciora
Jacqui EhningerCuervo
1.2 Draft
Victoria Popescu
Elisabeta Ciora
1.3 Draft
Jacqui EhningerCuervo
1.4 Draft
Jacqui EhningerCuervo
Jacqui EhningerCuervo
1.6 Draft
Elisabeta Ciora
1.7 Draft
Jacqui EhningerCuervo
1.8 Draft
1.9 Draft
Victoria Popescu
Elisabeta Ciora
1.5 Draft
REASON
Original version sent out for review
1.10 Draft
Mehdi Bendjebbour
1.11 Draft
Elisabeta Ciora
Nov 2, 2011
1.12 Draft
1.13 Draft
Elisabeta Ciora
Mehdi Bendjebbour
Nov 2, 2011
Nov 2, 2011
1.14 Draft
Mehdi Bendjebbour
Nov 3, 2011
1.15 Draft
1.16 Draft
1.17 Draft
Victoria Popescu
Victoria Popescu
Victoria Popescu
Nov 9, 2011
Dec 5, 2011
Dec 21, 2011
TABLE OF CONTENT
REVISION HISTORY......................................................................................................... 2
LIST OF TABLES............................................................................................................. 6
1 INTRODUCTION......................................................................................................... 7
1.1 Objectives.........................................................................................................
1.2 Scope and Limitations...........................................................................................
1.3 Document Conventions.........................................................................................
2 DCT BASICS.............................................................................................................. 9
2.1 Introduction to DCT..............................................................................................
2.2 Authentication and Notification in DCT....................................................................
2.3 Requesting a DCT Account....................................................................................
2.4 Customizing your User Account Information..............................................................
3 CREATING CRS BY SYSTEM TEST AND SUB-SYSTEM.............................................................15
3.1 CR Creation and the CR MAIN tab............................................................................
3.2 The CR Affected Items Tab....................................................................................
3.3 The CR Description Tab........................................................................................
3.4 The CR Detection Info Tab....................................................................................
3.5 The CR Attachments Tab......................................................................................
4 CREATING AND MANAGING CRIS....................................................................................25
4.1 CRI creation by System Test..................................................................................
4.1.1 CRI creation and the CRI Main tab for System Test..................................................
4.1.2 The CRI Auto-Create Tab for System Test.............................................................
4.1.3 The CR CCB Review Tab during ST CRI creation......................................................
4.2 CRI Creation by Subsystem...................................................................................
4.2.1 Subsystem using the Auto-Create_CRI action.....................................................
4.2.1.1 The CRI Auto-Create Tab for Sub-System............................................................31
4.3 Assigning a CRI (ARTS: RFA)...................................................................................
4.3.1 Assigning a CRI created by system test...............................................................
4.3.2 Assigning a CRI created by subsystem.................................................................
4.4 Analyzing a CRI (ARTS: ANA):.................................................................................
4.4.1 Rejecting a CRI (ARTS: CLOSE OUT/NIP/REJECT depending on the Reason For
Closure):..........................................................................................................
4.4.2 Need more info (ARTS: RFI):............................................................................
4.4.2.1 Originator cannot reproduce problem (ARTS: CLOSE NRE):.......................................38
4.4.2.2 Problem is reproducible (ARTS: RFC in ST database, RFA in the sub-system database):.....38
4.5 Correcting a CRI (ARTS: RFC and COR):....................................................................
4.5.1 Creating new DWOs......................................................................................
4.5.2 Submitting the DWO.....................................................................................
4.5.3 Submitting the CRI.......................................................................................
4.6 Testing the Fix..................................................................................................
4.6.1 Moving the CRI into ReadyToVerify state (ARTS: RFT):...........................................
4.6.2 Testing by Subsystem....................................................................................
4.6.2.1 Subsystem-level Test Fails (ARTS: NVAL):............................................................49
4.6.2.1.1
If the CR was created by sub-system:..........................................................................................49
4.6.2.1.2
If the CR was created by ST:.......................................................................................................51
4.6.2.2 Subsystem-level Test passes (ARTS: VAL):...........................................................51
4.6.2.2.1
If the CR was created by the sub-system team:...........................................................................51
4.6.2.2.2
If the CR was created by the ST team:.........................................................................................53
4.6.3 Testing by ST..............................................................................................
4.6.3.1 For a CR created by ST team:.........................................................................54
4.6.3.2 The test didnt pass at ST level (ARTS: NVAL):.....................................................54
4.6.3.3 The test passed at ST level (ARTS: VAL).............................................................56
4.6.3.4 Other TWO states (Cancel, Blocked, Not Conclusive, Passed with Comments)................57
4.7 Delivering and closing the CRI (ARTS: CLOSE REL).......................................................
4.7.1 If the CR was created by the sub-system.............................................................
4.7.2 If the CR was created by ST............................................................................
4.7.3 If the CR was created by CARES........................................................................
5 HANDLING CRS AND CRIS ASSOCIATED WITH CARES............................................................60
6 PROCESS FOR NPO RELATED ISSUES...............................................................................65
7 SPECIAL USE CASES................................................................................................... 66
7.1 How to copy a CR...............................................................................................
7.2 How to create a CR Dependency............................................................................
7.3 How to create a CRI dependency............................................................................
7.4 How to manage a CLOSE DEFERRED situation?...........................................................
7.5 How to manage a CLOSE DUPLICATE situation?...........................................................
7.5.1 Two CRIs created internally by the sub-system:.....................................................
7.5.2 If a CRI was created by ST and the same CRI exists, but created by the subsystem DUPLICATE CASES:....................................................................................
7.6 What if the problem impacts several modules of a sub-system?......................................
7.6.1 If it is known from the beginning (at the CR creation phase) that the problem
impacts several modules........................................................................................
7.6.2 If at the CR creation phase it is not identified that several modules of a subsystem are impacted ...........................................................................................
7.7 What if the problem impacts several release branches?................................................
7.8 What if the problem impacts more than one sub-system?..............................................
7.9 What if the analysis discovers that the problem comes from another subsystem?................
7.10 What if the problem was initially labeled as software is in fact hardware?.........................
7.11 What if a PR needs to be reclassified as a FEAT or ENH?...............................................
7.12 Deferred case from ARTS to DCT (B11/B12 to B11/B12)................................................
8 REFERENCE AND RELATED DOCUMENTS..........................................................................76
9 APPENDIX.............................................................................................................. 77
9.1 Workflows........................................................................................................
9.1.1 CR/CRI creation..........................................................................................
9.1.2 CRI creation after Submit-For-Review................................................................
9.1.3 CRI Assignment...........................................................................................
9.1.4 CRI Analysis...............................................................................................
9.1.5 CRI Correction............................................................................................
9.1.6 Testing a fix...............................................................................................
9.1.6.1 Testing by Subsystem...................................................................................82
9.1.6.2 Testing by System Test..................................................................................83
9.1.7 Delivering and closing the CRI..........................................................................
9.2 List of required fields..........................................................................................
9.2.1 Information required to produce/deliver (1 to 1 mapping)........................................
9.2.2 Information required to produce/deliver (as an aggregation of several DCT
fields)87
10 HELP ON DCT.......................................................................................................... 88
List of Tables
Table 1: Revision History............................................................................................................................
Table 2: Creating a CR MAIN Tab.........................................................................................................
Table 3: Creating a CR AFFECTED ITEMS Tab...................................................................................
Table 4: Creating a CR DESCRIPTION Tab..........................................................................................
Table 5: Creating a CR DETECTION INFO Tab...................................................................................
Table 6: Creating a CRI AUTO CREATION Tab...................................................................................
Table 7: CRs coming from CARES Use Cases.........................................................................................
1 Introduction
1.1 Objectives
The purpose of this document is to capture the recommended DCT processes for the GSM System
Test and Subsystem teams.
In as much as possible, the new DCT processes were aligned with the existing ARTS processes;
however, given the vastly different paradigms of the two systems, direct alignment is not always
possible.
It must be noted that the System Test and the Subsystem processes are quite different for at least part
of the CR lifecycle. The document is structured to contain separate sections for both the System Test
and the Subsystem process where ever the two processes sufficiently diverge to warrant separate
treatment.
The document covers:
Creation and management of Problem Report CRs, CRIs, DWOs and TWOs,
The Table of Contents should provide you with a good outline of how the information is organized.
Note: Should you encounter any situation not covered in this Guide, please speak to DCT experts in
your team or contact one of the GSM Product Group Administrators for help. Also, if you
experience any issues with availability or access to DCT, you should immediately raise a ticket with
the GHD (Global Help Desk).
serves only as a recommendation and as a template. It can be further customized by other subsystem
teams, if required.
Column 2 contains the recommended System Test process and Column 3 the recommended
Subsystem process:
DCT Field Name
(mandatory)
[ARTS: fieldname]
ST Process/CARES
Sub-system Process
Other conventions:
Wherever an important new term is introduced and explained, it will appear in bold within
the text.
2 DCT Basics
The following section introduces the most important concepts in DCT. If you have attended any of
the DCT Overviews, much of this information should already be familiar to you.
Please note that all information about DCT can be found at the DCT Portal:
https://dctportal.app.alcatel-lucent.com/cqweb/
In addition the GSM process and GSM FAQ can be found here:
http://acos.alcatellucent.com/wiki/g/swrdtools/DCT_CQ#PRODUCT_GROUPSx2f.BUSINESS_PROCESSES
(to be added)
The Functional Area Manager, who administers his or her Functional Area in DCT and is
the only one authorized to add members to the FA. The FA Manager can also act on behalf of
all other roles in the FA.
The Screener, who is notified when a new CR has come into the FA. The Screener is
normally a member or delegate of the CCB (Change Control Board) and usually also an
expert for his or her Functional Area. The Screener ensures that a new CR has sufficient
information and initiates an analysis, if required, to make sure that the CR actually belongs
into this Functional Area and that the Product information is correct. The Screener also
The Closer, who is responsible for the delivery of a fix that is associated with a CARES
ticket (CARES is the Customer Problem tracking system).
DCT is project management oriented and has a built-in hierarchy which supports this approach. In
this DCT hierarchy you will find:
1. The Change Request or CR, which represents only the Problem Statement and contains
information about the nature of the problem, who found the problem, when, where and how the
problem was found. The CR can be of different types:
a CR of type Problem Report (PR). This type is the equivalent of the ARTS FR.
a CR of type Feature (FEAT), the equivalent of an ARTS CR coming from the A55 database.
This document deals with CRs of type Problem Report and ENH, but not Features.
An AI can denote anything that is required as part of the solution for the Problem CR (for
features the AI can represent the feature requirements) and can be used differently by
different subsystems, to capture additional information in a flexible manner, depending on the
need.
3. If it is determined that the CR describes a real issue that needs to be resolved, DCT requires
that a Change Request Instance or CRI is opened to actually track the work that is being
done.
4. Design Work Orders or DWOs are optional child records of a CRI and are used to track
changes down to the actual implementation of the Problem, Enhancement or Feature. If there is
an integration between DCT and the businesss configuration management tool (like for
example CC or CC/UCM), the two systems can be connected via the DWO. Each designer has
their own DWO(s), they are not shared.
5. Test Work Orders or TWOs are also optional child records of a CRI and are used if an
organization wants to have detailed and customized records of the verification phase of a
change. Note that if a designer recommends any particular tests on a DWO, this information is
copied to the CRI and is visible from all TWOs, to assist during verification.
Associated to these DCT records described above you will find the following other roles in this
document (anyone can take on these roles as part of their daily activities, they are outside the
Functional Area):
10
The CR Originator and the CR Creator equivalent of the Originator and Author in ARTS.
The CR Analyzer person who has been asked to conduct an depth analysis of a CR before
a CRI is opened. For example if the CR was opened against S/W but it is suspected that it
may actually be a H/W problem.
The CRI Requestor person who opens the CRI, usually the same as the Screener, but it can
also be the CR Creator/Originator.
The CRI Assignee who is responsible for the implementation of a fix. This can be a
manager or team leader who is coordinating the implementation (in that case normally the
designers would use DWOs) or the designer him- or herself (DWOs can still be used in this
case, especially if the fix is comprised of multiple parts).
The DWO Assignee designer who is providing the implemented solution (or a part thereof)
The TWO Assignee the verifier who will be validating implementation of the fix. The
TWO Assignee is notified by the system as soon as a CRI is Ready-to-Verify.
To log into DCT Production (DCTPD) you will require your CSL (or EUID for third party
users) and the corporate password.
The DCT Training database (DCTTR) is not LDAP authenticated and you log in with the
UserId and password both set to your CSL or EUId.
DCT generates a lot of automatic email notifications to alert people that they have items that require
their attention like: New CRs to be screened, CRs to be analyzed, CRIs that require implementation,
CRIs that require approval for closure, TWOs that are ready for testing, just to name a few.
Currently DCT does not have a mechanism to disable some or all of these messages, the only thing
you can do is to filter them using Outlook (caution: Outlook filtering has a bug that can result in
messages multiplying rather than disappearing, depending on the order in which filters are set up!)
If you choose to discard the DCT notifications, you will need to rely on queries to find your DCT
tasks instead.
Note that you should never discard DCT QUEST messages, since these are actually emails sent to
you by other users from within the DCT system.
Use this link to request a DCT accounts on-line. If you are an ALU employee or contractor with a
CSL then select "Internal" for employee type. If you are a third party user who accesses ALU tools
via a Third party gateway, please select "External".
Note: After you have submitted your account request, please wait for account approval (you will be
notified by E-mail); you then will receive another E-mail including instructions on how to activate
your account correctly.
Once you have your account activated you can customize your user account:
12
Enter CSL
here
- double click on the result (line with your name and CSL):
13
Organization : name of your team for ST and subsystem name for subsystem.
click on Save button once you are finished. Now your new CR will open with this
information as default.
14
the following menu will appear; note that mandatory fields, or tabs containing mandatory
fields are marked in red and have an asterisk:
15
ST Process/CARES
Sub-system Process
Headline
(mandatory)
[ARTS: Short
Description ]
Originator to approve
closure
[no ARTS equivalent]
Product Group
(mandatory)
[no ARTS equivalent]
If Y:
If Y:
Select GSM unless you are creating a CR Select GSM unless you are creating a CR
against another Wireless system or against against another Wireless system or
16
Product Line
(mandatory)
[no ARTS equivalent]
Product Name
(mandatory)
[no ARTS equivalent]
Product Release
(mandatory)
[ARTS:
Impacted version]
Product Version:
(conditionally
mandatory)
[no ARTS equivalent]
DCT.
against DCT.
Functional Area
(mandatory)
[no ARTS equivalent]
S/W Load
(conditionally
mandatory)
[no ARTS equivalent]
Component
(conditionally
mandatory)
[ARTS:
Sub System /Function /
SubFunction]
Found by Org
[no ARTS equivalent]
In DCT 3.3.1 can be
found under MAIN TAB
of the CR
Found by Country
[ARTS:
Alcatel Location]
In DCT 3.3.1 can be
found under MAIN TAB
of the CR
Where Found
[ARTS: Alcatel
Location]
In DCT 3.3.1 can be
17
Up to 3 Affected Items can be defined during CR creation (and more can be added later if required):
ST Process
Sub-system Process
18
[ARTS: fieldname]
Category
[ARTS:
Classification ]
Type
(mandatory)
(mandatory)
[no ARTS
equivalent]
Version +
(conditionally
mandatory)
[no ARTS
equivalent ]
Enforce Delivery
(mandatory)
[no ARTS
equivalent]
As defined by SubSystem.
19
20
[ARTS: Detailed
Description]
ST Process
Sub-system Process
Reproducible
(mandatory)
[ARTS:
Problem Type]
Steps to Reproduce
(conditionally mandatory)
Workaround
(mandatory)
[ARTS:
Palliative Correction]
Always/Sometimes/NO/NAUnknown;
Always/Sometimes/NO/NAUnknown;
21
ST Process
Sub-system Process
Detected in Phase
[ARTS:
Found Phase /Activity ]
Detected in Activity
[ARTS:
Found Phase /Activity ]
Detection Method
[ no ARTS
equivalent ?]
Found using TC#
[ARTS: when used
Free Item 3]
Validate;
Test Impact
[no ARTS equivalent]
Integration/Verification/System
Validate;
NOT USED
As required by Subsystem.
If used (as for example by TC) it
corresponds with Free Item 3 from ARTS
the tests number (ID);
Not used.
22
Note: Be careful that when attaching larger traces, your session may time out, in this case you can
use the ARTS way of putting the traces -> put the traces on your local server known by everybody
and just add the URL in DCT.
23
In fact, to get your DCT account activated in Production, you need to have at least one Training CR in the NEW or
OPEN state.
24
- when the screener receives a notification that a new CR was created he has to:
TPR/Screener part:
If the problem is not clear, or could affect more than one subsystem, the Screener
would put the CR into Analysis and assign it to a Subsystem Screener by using the
Analyze-Request action. Once the CR comes back from analysis, the Screener can
now decide if:
1. the CR has been opened against the correct Product and a CRI can be opened
2. the CR must be re-screened to another Product (subsystem) before a CRI is
created.
3. The problem affects multiple subsystems, in which case a CRI must be created
and the CR must be copied to the other Products (Subsystems). In this case
remember to save the copied CR and also submit for review (see Section 7.1
on page 66 for details).
25
Assuming that we have case 1. above (the most likely scenario), meaning that the ST
Screener agrees that the CR is a real problem and was raised against the correct
Product, he/she now has to create the CRI by clicking on CR.Change State: CreateCRI:
4.1.1
CRI creation and the CRI Main tab for System Test
26
1. Correct the CRI Target Info [Free Item 9 from ARTS filled in by SYSTEM] if required:
Product Release: it is automatically filled with the CR.[MainTab].ProductRelease
if it is not consistent, it must be changed;
2. Change the CRI Functional Area from System Test to the impacted Subsystem team, so
that the Subsystem Screeners get notified (e.g. MFS_B12)
4.1.2
Next, move to the CRI.[AUTO CREATE] Tab, to create the system tests TWO, see also
Table 6: Creating a CRI AUTO CREATION Tab on page 32.
27
Once all required fields are filled in remember to SAVE your CRI by clicking on CRI.Save
button!
4.1.3
As part of CRI creation, DCT will prompt for a CCB review status on the parent CR
CCB Review Status: Indicate if a review was required or not and if so, if the change was accepted.
Review Notes: add specific remarks/notes if necessary or any important points from the NCB review
meeting. It is recommended to at least add a note such as: OK for transfer to <x>
subsystem on <date>.
Remember to SAVE your CR! Otherwise the CRI is created but the CR gets stuck in a wrong
state.
Once you click on the CR.Save button, the CR is now transferred to the subsystem and is
ready to be analyzed by the subsystem team
28
29
MFS
Auto-Create_CRI
TC
Auto-Create_CRI
BTS
Auto-Create_CRI
BSC
Auto-Create_CRI
OMC
Auto-Create_CRI
SED
Auto-Create_CRI
Create the CR and use the Submit-for-Review action to submit to the correct Subsystem FA
or use Auto-Create-CRI as per your Subsystem process.
The Subsystem Screener(s) will get notified.
The Subsystem Screener checks the CR for completeness and correctness and updates the AI
if required. If needed the Screener will send the CR for more Info or for Analysis. If a CRI
already exists, the Screener will need to use his own discretion to decide the best course of
action.
If a CRI already exists (CR creator used Auto-Create-CRI) and the information is correct,
the Screener will use the Re-Assign action in the CRI.Modify pull-down menu to assign
the CRI.
30
If no CRI exists the Subsystem Screener will use the Create-CRI action in the
CR.Change State pull-down as a separate step and immediately Assign the CRI on the
Auto-Create tab (this can be done in one step)
o At this point, the Screener can also immediately create a DWO. The DWO can be
assigned or unassigned. If DWOs are created at this step, designers can take them
from the pool of DWOs to be done (basically the designer self-assigns those tasks
they want to work on, but the DWO has already been created for them).
4.2.1
4.2.1.1
31
ST Process
Sub-system Process
N.
Y;
System Test;
click on CR.Save button the CR is now in the Open state , equivalent of OPEN from
ARTS:
32
The screener of the impacted subsystem team should assign the CRI to a DEV assignee by
clicking on CRI.Change State: Assign in the CRI window:
4.3.2
The DEV assignee should be introduced in the CRI.[MainTab].Assignee+ field and then
click on the CRI.Save button:
33
Complete the
new DEV
assignee
34
Figure 4-32 Save the CRI to take into consideration the analysis
Next, Modify the CR and also copy the CRI Analysis to the CR.[NotesTab]InternalNotes
field. This is done so that the analysis is preserved in case the CR was raised against a wrong
product and needs to be re-screened, which results in deletion of the CRI.
Click the CR.Save button
4.4.1
Rejecting a CRI (ARTS: CLOSE OUT/NIP/REJECT
depending on the Reason For Closure):
The decision to reject a CRI is based on the analysis made by the DEV assignee - if no
correction is needed, the DEV assignee will re-assign the CRI to the screener by clicking on
CRI.Modify:Re-Assign button. The screener closes the CRI by selecting CRI.Change State:
Reject:
Select the correct Reason For Closure and if required an Additional Reason for
Closure to indicate why the CRI doesnt need correction (Business Decision / Works As
Designed);
the CRI.Save button must be clicked in this moment the CRI will go to the Closed
state:
Note: The CR will also automatically change to the Closed state, if this was the last
open CRI:
In this scenario, the TWO created by ST will be cancelled and email notification will be
sent.
36
4.4.2
This action is used if the provided description and/or traces are not relevant or insufficient:
the DEV assignee will click on CRI.Change State: Need-Info_OR_Defer button:
the CRI.Save button must be clicked in this moment the CRI is in InMonitor state and
the CR Originator is notified by Email about what information is missing. Make sure that the
37
Remind Originator flag is checked and that a Monitoring Date is entered, so that DCT can
send reminders to the CR Originator.
the CRI.Save button must be clicked in this moment the CRI is in Closed state:
4.4.2.2
Problem is reproducible (ARTS: RFC in ST
database, RFA in the sub-system database):
If the problem can be reproduced, the originator should execute the following steps:
38
Remember to click the CRI.Save button to ensure your changes are applied:
Once the test has been redone and a new set of traces collected the originator returns the
CRI to its previous state by selecting the state change action CRI.Change State:
Return_to_Previous_State. This will notify the CRI Assignee that the requested
information has been provided. Remember to CRI.Save the State change action!
39
Item Type: if not correct, filled in with the necessary information from the pull down
menu;
Item Name: if not correct, fill in with the correct component impacted by the correction;
Target Stream: optional, as used by Subsystem process;
Target S/W Load+: expected delivery software version name (e.g. MFSYAL01K);
after the required information were introduced, the CRI.Save button must be clicked:
40
At this point we need to create DWOs if this has not already been done earlier by the Screener
(optional decision as sub-system process requires):
Subsystem
Use DWO
MFS
Yes
TC
Yes
BTS
No
BSC
Yes
OMC
Yes
SED
Yes
--- CRI.[PROGRESS INFO] Tab --Resolution Description: introduce the information related to the correction (Engineering Solution in
ARTS);
Implementation Impact: will be filled with the unitary tests performed by the DEV assignee in
order to validate its correction and the system impact, if any;
click on CRI.Save button when all the fields are completed:
41
Now, go to 4.5.3;
4.5.1
If the DWO has not been created already, the DEV assignee can do so by clicking on
CRI.Modify: Create-new-DWOs:
now the DWO window will be displayed - the developer will assign the DWO to himself
and the DWO.Save button will be clicked:
42
Complete the
DEV assignee
in this moment the CRI and the DWO are in InProgress state:
After the DWO is created, the correction is made and the DWO can now be promoted to the next
state to indicate that the fix has been implemented:
4.5.2
to put the information related to the correction (Engineering Solution in ARTS), the DEV
assignee must click on DWO.Change State: Submit button:
43
and a new window will appear click on Not Specified from Choice List, Add All button and
OK button:
44
Submitted in Item Version: will be filled with the component label that was delivered (Free Item 2
in ARTS if used);
Submitted in S/W Load: will be filled with the software version in which the delivery was made
(Free Item 9);
Resolution Description: introduce the information related to the correction (Engineering Solution in
ARTS);
Implementation Impact: will be filled with the unitary tests performed by the DEV assignee in
order to validate its correction and system impact, if any;
click on DWO.Save button when all the fields are completed:
45
the DWO.Save button must be clicked in this moment the DWO is in Submitted
state:
4.5.3
in the CRI window, the DEV assignee will click on CRI.Change State:
Submit_Solution button:
46
--- CRI.[PROGRESS INFO] Tab --Packaged In Item Version+: will be filled with the component label that was delivered (Free Item 2
in ARTS);
Delivered In S/W Load+: if the software version is not consistent with the one in which the delivery
was actually made, it will be changed;
Figure 4-55 Complete the component label and the software version in which the delivery will be made.
the CRI.Save button must be clicked the CRIs state is now Submitted:
47
4.6.1
Use DWO
MFS
No
TC
Yes
BTS
No
BSC
No
OMC
No
SED
No
The state change from Submitted to ReadyToVerify state will trigger notification of the
TWO Assignee. If you do not use TWOs, it still indicates that the CRI is ready for testing and the
FA Test Manager is notified (if there is one).
If the CR was raised by ST and Subsystem uses TWOs as well, then the Subsystem TWOs should
be tested while the CRI is still InProgress. This ensures that ST is not notified prematurely.
Only once the Subsystem TWOs are passed should the CRI be set to ReadyToVerify so that the
ST TPR/Screeners are notified that the ST TWOs are now ready for testing.
If the CR was raised by Subsystem, the CRI can be put into ReadyToVerify as soon as the
implementation is done.
4.6.2
Testing by Subsystem
Complete the
TEST assignee
Note: To test the CRI, it is not mandatory to use a TWO -> it remains strictly internal to each
tester team its creation.
4.6.2.1
49
the CRI.Save button must be clicked in this moment the CRI is in ReadyToVerify
state:
If the test didnt pass, the TEST assignee will click on CRI.Change State: Reinvestigate in order
to put NVAL the test result:
--- CRI.[NOTES] Tab --Internal Notes Entry: the test environment will be introduced;
if the CRI was created by ST and a ST TWO exists, the CRI.
[ProgressInfoTab].VerificationStatus field cant be selected for completion, only in case
the CRI was created by the sub-system:
--- CRI.[PROGRESS INFO] Tab --Verification Status: the test result will be selected;
50
the CRISave button must be clicked in this moment the CRI is in InProgress state:
4.6.2.2
If Subsystem Testing has passed and the CR was raised by ST, the CRI can now be moved to
ReadyToVerify.
If the CR was raised by Subsystem, then the CRI can be delivered once Verification is completed.
51
the CRI.Save button must be clicked in this moment the CRI is in ReadyToVerify
state:
- the TEST assignee will click on CRI.Change State: Verified button to introduce the test
environment and the test result:
--- CRI.[NOTES] Tab --Internal Notes Entry: the test environment will be introduced;
--- CRI.[PROGRESS INFO] Tab --Verification Status: the test result will be selected;
52
--- CRI.[NOTES] Tab --Internal Notes Entry: the test environment will be introduced;
Note: The CRI will pass automatically to Verified_Completed state, when the TWO created by de
ST will be closed.
4.6.3
Testing by ST
When the CRI is moved to the ReadyToVerify state the TWO assignee (who is the STs
TPR/screener) is notified that STs TWO for this CRI can now be tested.
the TPR/screener, when they get the notification, make sure that if a sub-system TWO
also exists, then it must be passed first).
the TPR/screener then re-assigns the TWO to a TEST assignee (see Figure 4 -63 Reassign the STs TWO);
in the TWOs window, click on TWO.Modify: Re-assign button:
53
4.6.3.1
The TWO Assignee will update the test result on the TWO.
Note: The CRI will pass automatically to Verified_Completed state, when the TWO created by ST
is Passed.
4.6.3.2
As a prerequisite, before checking the STs TWO, make sure that the sub-system TWO is passed;
the TEST assignee has to test the correction and then put the result in the TWO. For this,
he has to open the TWO, click on TWO.Modify: Modify button and fill in the
information related to the software version used for test:
Figure 4-64 On the TWO Main Tab fill in the software version used for testing
54
if the test is failed, the TEST assignee must click on TWO.Change State: Failed button:
--- [NOTES] Tab --Internal Notes Entry: describe why the test was failed.
55
the CRI goes back into InProgress state and the subsystems screener is informed:
the sub-systems screener has to re-assign the CRI by clicking on CRI.Modify: Reassign button, fill in the CRI.[MainTab].Assignee+ field and then click on CRI.Save
button:
4.6.3.3
56
57
Figure 4-72 Deliver the correction (equivqlent of CLOSE REL from ARTS)
the CRI.Save button must be clicked in this moment the CRI is in Closed state:
4.7.2
- the STs TPR/screener must deliver the CRI, by clicking Change State: Deliver:
58
4.7.3
Need to fill this section on who exactly the CLOSERS are and what process they should follow
(Rene Veyland thinks they should be System Test people, but currently in ARTS this is NOT the
case. We need this part of the process).
59
60
Analyzer sets the Analysis state to Analysis InProgress while the problem is being
analyzed.
Analyzer indicates as part of the analysis which Affected Items are required (or even
better, adds the correct AIs to the CR)
Once complete, Analyzer sets the Analysis state to Analysis completed and uses the CR
change state action Return to previous state.
Screener is notified that the analysis is completed.
After the analysis is completed (and this can take considerable time for a complex issue),
the following scenarios are possible:
Table 7: CRs coming from CARES Use Cases
After the Analysis the Affected Item is corrected and the CRI
against the correct Subsystem as per the normal ST process (s
4.1 on page 25). This CRI will also of course have a ST TWO
61
The CRI(s) for Subsystem2 are created for the copied CR, ag
indicated by the analysis.
The Screener links the ST TWO from the CRI for Product1 to
Product2 since we want to test the whole implementation to
we only want to be notified once all the CRIs are Ready-to-V
62
Case7 The Product is correct, one or The Analysis comes back indicating that the Subsystem(s) do
more Products are involved,
that the problem is a defect and that a fix would require a cha
the problem is reclassified as
specification.
a Feature
The CR is now sent for Re-analysis to the SPEC team.
63
Create a CRI + TWO for the Original CR (you will still need
deliver). The CRI can be of type External indicating that it
used to track the test effort of an implementation that is happe
another CR (Note: Even if DWOs are normally mandatory, th
convention, never made mandatory for type External).
Need to identify the Closers and the process for delivering (what triggers the state change
in CARES CTS:CR to Close/Normal in the current integration with ARTS)
ST will Deliver the CRI when the whole load is sent to outside R&D (to TIS for
example)
64
After the CR is created, it has to be put into the state : SUBMIT FOR REVIEW.
The NPO team will analyze the CR, accept it, change the FA and the AI if necessary and will create
the CRI.
After the NPO finishes the correction will assign the CRI to the originator and set it Ready-toVerify.
The originator is informed and will be able to check correction.
If the CRI is corrected, he has to put the CRI into the state Verified and fill in the required
information from the Progress Info TAB. (verification status = passed )
If the CRI was not corrected as expected, , he has to put the CRI into the state Reinvestigate and
fill in the required information from the Progress Info TAB. (verification status = failed) and put
also into the NOTES tab the reason why the CRI is failed.
If the CRI is passed, the state of the CRI will go into the state Verified Completed, and the Test
Manager from the system test team will have to change state into DELIVER
In order to be able to have this process, some of the system test managers will also have rights on the
NPO product.
65
66
67
the ne newest CRI should be duplicated by the sub-systems screener by clicking in the CRI
on CRI.Utilities: Duplicate button:
the following window will appear the screener should enter in the
DuplicateRecord.SearchKey field the CRI Id of the initial CRI and then click on
DuplicateRecord.OK button:
68
in the CRI window, update the CRI.[NotesTab].InternalNotes field with the reason why this
CRI is duplicated and with whom and then click on CRI.Save button;
automatically, both CRI and CR will change their state into Closed;
the initial CRI will be followed.
7.5.2
If a CRI was created by ST and the same CRI exists, but
created by the sub-system DUPLICATE CASES:
the STs CRI should be kept and the sub-systems CRI must be closed (see Two CRIs created
internally by the sub-system:), even if this CRI is issued earlier;
in this case, the information contained in the sub-systems CRI must be reported in the STs
CRI.
Note: The same scenario should apply also in case that 2 CRs/CRIs are created by different
teams on the same problem.
69
7.6.1
If it is known from the beginning (at the CR creation
phase) that the problem impacts several modules
the originator should create an Affected Item for each impacted module (up to 3 Affected
Items can be added during CR creation time, but as many as required can be added
afterward);
Multiple Affected Items can be addressed by one CRI; if desired each Ai on the CRI can be
tracked by a different DWO;
7.6.2
If at the CR creation phase it is not identified that
several modules of a sub-system are impacted
if after the analysis (see 4.4) it is discovered that several modules are impacted, the DEV
assignee must go on the CR window and click on CR.Modify: Add-New-AIs:
70
the Create CRIs prompt will turn red; click on CR.New button (see Figure 4 -18 Clink
on New to create a CRI.) -> a new CRI window will appear;
in the new CRI window, in CRI.[Maintab], make sure that you associate the AI to the CRI;
71
the DEV assignee needs first to select the AI number and then click on CRI.Add to CRI
button (see Figure 4 -19 Associate the AI to the CRI);
the DEV assignee should be introduced in the CRI.[MainTab].Assignee+ field and the
priority should be introduced in the CRI.[MainTab].Priorityfield and then click on the
CRI.Save button (see Figure 4 -30 Complete the new assignee);
72
73
ATENTION: a dependency between these two CRs must be created! (See section 7.2 on page 66)
7.9 What if the analysis discovers that the problem comes from
another subsystem?
Ideally the System Test Manger would have assigned the CR for analysis to a subsystem expert
BEFORE creating a CRI. If the analysis shows that the wrong subsystem was identified in the
Found-In info, the ST manager would simply modify the CR Product hierarchy before creating a
CRI.
If a CRI was already created, the Subsystem should:
Make sure that all the Analysis Notes are available on the CR.
Add a new AI to the CR and then reject the CRI (adding a new AI first will prevent the CR
from auto-closing), or
simply return the CRI to the NEW state with a comment in the Internal Notes so that the
ST manger can do a re-screen of the CR and the CR Product hierarchy can be corrected.
The ST Manager then Re-screens the CR to the correct subsystem, which will delete the
wrong CRI.
74
change the CRI Category as well and re-assign it to the proper H/W Functional Area.
2.
if the CR needs to be copied to the SPEC team (then this becomes more like
Case4), or
3.
if we allow CRIs for SPEC under a Subsystem CR. The problem with option
3. is that once you turn this option on, you have no control whether it will be abused
for other cases.
If, after the CR has been reviewed at the NCB, everyone agrees that the request is not fix for
free, then (this is the equivalent of an A55 CR in ARTS):
o
75
Open a new ticket in DCT , and fill in [CR MAIN TAB] Ref. CR Tool: with ARTS
and Ref. CR Id: with ARTS number
close the FR in ARTS with comments (Close REJECT) and add in Free Item 4 the
DCT number
76
DOCUMENT REFERENCE ID
[1]
[2]
[3]
[4]
System CR Management Helper Guide for Release B11 8BL 14304 0029 ASZZA
[5]
[8]
RELATED DOCUMENTS
# TITLE
[a]
DOCUMENT REFERENCE ID
8BL 14050 0003 ADZZA
http://awwmnd.alcatel.com/technic/competence/Int/indexintcc.htm
Process & Quality
77
9 Appendix
9.1 Workflows
9.1.1
CR/CRI creation
78
9.1.2
79
9.1.3
CRI Assignment
80
9.1.4
CRI Analysis
81
9.1.5
CRI Correction
82
9.1.6
Testing a fix
9.1.6.1
Testing by Subsystem
83
9.1.6.2
84
9.1.7
85
List_of_Required_Fie
ld_In-DCT_20111026.xls
OBS: A new xls will be added with the summary of mandatory information.
86
9.2.1
These fields match the information exchanged by Sybsystem, ST and TIS to produce a fix.
87
9.2.2
Information required to produce/deliver (as an aggregation of several DCT
fields)
The information below is used by Sybsystem, ST and TIS and a combination of DCT fields is used to retrieve it.
88
10 HELP on DCT
1. DCT HELP :
http://acos.alcatel-lucent.com/wiki/g/swrdtools/DCT_HELP
2. DCT_Support_And_FAQ
This page contains the list of most Frequent Asked Questions about DCT:
http://acos.alcatel-lucent.com/wiki/g/swrdtools/DCT_Support_And_FAQ
3. DCT FAQ forum
If you are not sure whether you have seen a problem or you simply have a question. http://acos.alcatellucent.com/forum/forum.php?forum_id=926&group_id=104
4. FAQ on Queries
http://acos.alcatel-lucent.com/wiki/g/swrdtools/FAQ_On_Queries
5. How to
Please refer to the tutorials on how to use and manage DCT.
http://acos.alcatel-lucent.com/wiki/g/swrdtools/DCT_Training_General
89
More information
1. DCT Roles and privileges :
http://acos.alcatel-lucent.com/wiki/g/swrdtools/DCT_Roles_and_Privileges
90