development lifecyle coverage gaps in Jazz
As RTC platform today does not address the entire lifecycle, can you confirm my understanding of these areas? Some of these are from early days of pre-beta or even pre-RTC days but I am just brain dumping everything in one shot. For the ones that you need me to submit workitem RFE, please let me know.
Lifecycle coverage
a. Take SAP scenario through Jazz to see how Jazz works with the entire lifecycle
i. Create folder hierarchy (currently we pre-populate the SAP folder hiearchy in CC)
ii. Create requirements NOT SUPPORTED
iii. Tie requirements to design NOT SUPPORTED
iv. Import deliverables (currently we pre-populate CC with design samples and templates documents).
v. Tie deliverable to requirements NOT SUPPORTED, CAN TIE TO WORK ITEM
vi. Track meta-data on deliverables LIMITED, NO EXTENSIBILITY
vii. Work flow through ClearQuest deliverable activity LIMITED TO OUT OF THE BOX WORK FLOW
viii. Report on traceability (requirements linking to downstram artifacts such as design, code, test) NOT SUPPORTED
ix. Show management reports status, in particular states LIMITED REPORT TAILORING (I.E., DATE RANGE)
x. Create and execute tests NOT SUPPORTED
xi. Tie tests to requirements and deliverables (design documents) NOT SUPPORTED
III. Migration considerations
a.Port Accenture ClearQuest Issue procedure to Jazz NOT SUPPORTED
b.Port Accenture ReqPro customizations to Jazz NOT SUPPORTED
c.Port Accenture Project Console report to Jazz LIMITED REPORT TAILORING
d. Port other Accenture customizations to Jazz (not sure if wed want to look at something like customizable lists in ClearQuest) NOT SUPPORTED
e. Impact to hosting (?) what are the ports requirement of the backend components in a distributed environment? - DIDNT LOOK AT
f. What are specific planned migration tools that will help the migration effort? NOT SUPPORTED
g. What is the general migration approach of existing Rational tools to Jazz tools? - NOT SUPPORTED
h. Is there a concept of coexistence between Jazz and existing Rational tools? What are the integration touch points in co-existence scenario? CC/CQ bridges available
IV. Jazz customization and extension framework
a. What can be customized and extended in Jazz. NOT SUPPORTED
b. Can we copy/clone? NOT SUPPORTED
c. Can we deploy single procedure vs. entire schema? NOT SUPPORTED
Testing Support -
- Test management
- Test execution
- Manual testing (RMT or future QM integrated with RTC?)
- Functional test (RFT integrated with RTC?)
- Performance test (RPT integrated with RTC?)
RTC issues (as of beta 2 so far)
CQ-Jazz bridge
- Enable the bridge to point to multiple CQ databases. According to jazz.net forum, Rational says we need to configure multiple instances of the gateway but there are no documented steps to do this.
- The ability to sync records from multiple projects (e.g. we use ADT_Project_Name to tag records) to multiple Jazz categories. I think this can be done but I need to try it out.
CC-Jazz bridge
- bridge is very specific of only synchronizing source code (e.g. only be able to set source code path that contains .project Eclipse file, etc.). We need to bring over documentation a well. I think there is already RFE for this but I am not sure the RFE number.
- In the Jazz web interface, we only can read/view files (e.g. can not check in/out).
Lifecycle coverage
a. Take SAP scenario through Jazz to see how Jazz works with the entire lifecycle
i. Create folder hierarchy (currently we pre-populate the SAP folder hiearchy in CC)
ii. Create requirements NOT SUPPORTED
iii. Tie requirements to design NOT SUPPORTED
iv. Import deliverables (currently we pre-populate CC with design samples and templates documents).
v. Tie deliverable to requirements NOT SUPPORTED, CAN TIE TO WORK ITEM
vi. Track meta-data on deliverables LIMITED, NO EXTENSIBILITY
vii. Work flow through ClearQuest deliverable activity LIMITED TO OUT OF THE BOX WORK FLOW
viii. Report on traceability (requirements linking to downstram artifacts such as design, code, test) NOT SUPPORTED
ix. Show management reports status, in particular states LIMITED REPORT TAILORING (I.E., DATE RANGE)
x. Create and execute tests NOT SUPPORTED
xi. Tie tests to requirements and deliverables (design documents) NOT SUPPORTED
III. Migration considerations
a.Port Accenture ClearQuest Issue procedure to Jazz NOT SUPPORTED
b.Port Accenture ReqPro customizations to Jazz NOT SUPPORTED
c.Port Accenture Project Console report to Jazz LIMITED REPORT TAILORING
d. Port other Accenture customizations to Jazz (not sure if wed want to look at something like customizable lists in ClearQuest) NOT SUPPORTED
e. Impact to hosting (?) what are the ports requirement of the backend components in a distributed environment? - DIDNT LOOK AT
f. What are specific planned migration tools that will help the migration effort? NOT SUPPORTED
g. What is the general migration approach of existing Rational tools to Jazz tools? - NOT SUPPORTED
h. Is there a concept of coexistence between Jazz and existing Rational tools? What are the integration touch points in co-existence scenario? CC/CQ bridges available
IV. Jazz customization and extension framework
a. What can be customized and extended in Jazz. NOT SUPPORTED
b. Can we copy/clone? NOT SUPPORTED
c. Can we deploy single procedure vs. entire schema? NOT SUPPORTED
Testing Support -
- Test management
- Test execution
- Manual testing (RMT or future QM integrated with RTC?)
- Functional test (RFT integrated with RTC?)
- Performance test (RPT integrated with RTC?)
RTC issues (as of beta 2 so far)
CQ-Jazz bridge
- Enable the bridge to point to multiple CQ databases. According to jazz.net forum, Rational says we need to configure multiple instances of the gateway but there are no documented steps to do this.
- The ability to sync records from multiple projects (e.g. we use ADT_Project_Name to tag records) to multiple Jazz categories. I think this can be done but I need to try it out.
CC-Jazz bridge
- bridge is very specific of only synchronizing source code (e.g. only be able to set source code path that contains .project Eclipse file, etc.). We need to bring over documentation a well. I think there is already RFE for this but I am not sure the RFE number.
- In the Jazz web interface, we only can read/view files (e.g. can not check in/out).
One answer
With Respect to CC Connector Issues:
Note that it is not source-code specific, but rather "Eclipse
project-specific". Eclipse allows you to have any kind of project you
want (i.e. a project can have any kind of file in it, including
documentation etc.).
Also note that this is not a CC Connector issue, but rather a Jazz SCM
issue (the CC Connector is happy to bring over any kind of tree, but
Jazz SCM only wants to receive Jazz project trees). The workitem to
relax this Jazz SCM constraint is: workitem 30924
Similarly, the ability to modify version-controlled files through the
Jazz web interface is a Jazz SCM issue, rather than a CC Connector issue.
Cheers,
Geoff (ClearCase Connector team)
gdang wrote:
Note that it is not source-code specific, but rather "Eclipse
project-specific". Eclipse allows you to have any kind of project you
want (i.e. a project can have any kind of file in it, including
documentation etc.).
Also note that this is not a CC Connector issue, but rather a Jazz SCM
issue (the CC Connector is happy to bring over any kind of tree, but
Jazz SCM only wants to receive Jazz project trees). The workitem to
relax this Jazz SCM constraint is: workitem 30924
Similarly, the ability to modify version-controlled files through the
Jazz web interface is a Jazz SCM issue, rather than a CC Connector issue.
Cheers,
Geoff (ClearCase Connector team)
gdang wrote:
RTC issues (as of beta 2 so far)
CC-Jazz bridge
- bridge is very specific of only synchronizing source code (e.g.
only be able to set source code path that contains .project Eclipse
file, etc.). We need to bring over documentation a well. I think
there is already RFE for this but I am not sure the RFE number.
- In the Jazz web interface, we only can read/view files (e.g. can
not check in/out).