Qa Issues

While trying to test documentation and tools provided by QA group I've found some points that I'd like to discuss in the next meeting.... Some point really needs an immediate attention and some other are just hints for a major discussion about future plans and organization.

• Old Tools & Documentation
  • Main webpage has links that needs to be updated (see for ex. here and here) !!!
  • QaSimTools
    • Has this tools been used/updated/upgraded recently?
    • code and documentation are NOT up to date:
      qasim output:
      %% Information %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      For you information you are using release
      as a reference release.
      The reference releases available are : r6.10.6a r6.10.6a r6.10.13 r6.10.6a r6.6.2c r7.11.2 r7.11.2d r8.8.0c
      %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
      SP4 starts with 881b: has this tool been used after year 1999-2000?
  • QaSimAppTools & QaRecoTools
    • Reference releases are not up to date (same problem as previous tool): what are the changes needed in order to use it now?
    • This can be a powerful tool: who's using it? Who is in charge for updates, upgrades?
  • QA in production: last update in early 2001.
    • Plots (again linked from main webpage) are NOT up to date.
    • How do we use those tools? Who needs them? Who's using them?
    • Here are some plots for SP1 and SP3 validation...... What about SP4 validation? Has been this tool used?
    • Migration of code is needed?
    • SP5 plans?
  • QaBetaTools:
    • The webpage with documentation is not up to date.
    • The tool seems not to be used. Who is using it? Who is in charge for upgrades? What are we trying to do with this tool?
• New Tools:
  • QaOprUtils
    • Migration in order to have it working at padova: who is in charge for that migration?see
    • Migration in order to deal with new Oracle database/OPR: it is needed? Planned?see (same link as before)
  • QaOprCharts
    • Migration to Padova. Again who's taking care of that?see
    • We need to implement the code needed in order to have the right package for a given release
    • We need to etablish once for all duties-responsabilities regarding that package: RQM, people from subsistems, QA people....
  • Tools for charts:
    • Fulvio ported the code to Padova: there is still work to do here?
• Verify:
  • What are we working on now?
  • Who is currently working on what?
  • Who is in charge for updates/upgrades of the tools presented in QaOpr webpage? Do we still need those tools? Who's using them?
  • What have been the concrete upgrades-updates-migrations of our tools in the past 4-8 months? Is manpower sufficient in order to address new/old items?
• Future project plans:
  • Update and upgrade tools, find out who's using them and what can be improved.
  • Revise the script that makes the .ps files for monitornig (change it in order to work under new control system)
  • Develop: Implement some 'automatic' check for the 80 pages of plots.

Those are some relational issues that also I'd like to discuss:

• Relations btw QA group and Rqm:
  • Develop of QaRqmTools package can be shared btw QA and Rqm?
    We need upgrades to port the code on mini and refine quantities dumped and timing issues needs to be investigated
  • QaOprCharts package: who is in charge for what? Needs to pass in QA group hands.
• Relations btw QA group and Collaboration:
  • Do we need to revise purposes of QA group (duties, responsabilities)?
  • What can be improved in relations btw QA group and AWGs (PAC), OPR people?
  • Update BAD 545 and documentation useful for analyst in collaboration
  • Include QA representative in IR2 prod meeting
  • Define a clear shedule and present it to the PAC-AWG group.
  • Include QA representative in PAC-AWG people and plan a monthly report about progresses/issues/problems/tools

Hot items

• Migration and update of OprQaUtils & OprQaCharts packages see
• Change in afs volume: need to put all the QA stuff in the new volume.. (free up space for RQM studies)
• Develop of QaRqmTools package: beta app like tool for collections checks.
• Old tools: we definitely need to update/upgrade code and documentation for tools that we need (and we first need to understand what we need to keep and what to discard!!!!)