SA1 and SA2 Effort Reporting Guide


TSA1.2 - Software Maintenance: effort spent in the analysis and in the implemenation of changes applied to components released in production, either in an EMI distribution or, during the transition period, in one of the separate middleware distributions (ARC, dCache, gLite, UNICORE).

TSA1.3 - Release Management: effort spent in the preparation of releases of the EMI distribution or, during the transition period, of the separate middleware distributions (ARC, dCache, gLite, UNICORE). This includes the coordination of the releases and the maintenance of the package repositories.

TSA1.4 - Quality Control: effort spent in the application of the QA guidelines and directives set by SA2 (e.g. writing and running tests to validate a release for production use). Effort spent in security assessments is also reported in this task.

TSA1.5 - User Support: effort spent in the investigation of incidents and in the interaction with GGUS.


TSA2.1 Work Package coordination Regular coordination and general meetings of the Work Package, reporting and review of milestones and deliverables. And all effort in participating to general EMI meetings and reviews.

TSA2.2 Quality Assurance Process Definition and Monitoring Definition of a standards-compliant software engineering process. Continual activity of monitoring its correct application within the activities of the EMI project. Verification of the availability of an agreed, documented and regularly updated process and the minimization of deviation in its application by the project members

TSA2.3 Metrics and KPIs Definition and Reporting Definition and continual collection and reporting of software quality metrics according to suitable QA models. Provides information to the PEB and other project bodies on status of software as an instrument for corrective actions. Regular production of reports and their use to identify improvement areas.

TSA2.4 Tools and Repositories Selection, Maintenance and Integration Definition and when necessary maintenance of tools required to support the QA process. Support software providers to integrate required information to and from tools maintained outside the EMI project. Setup and maintenance of repositories for storing EMI software packages, tests, build and test reports and metrics generated during all software development activities within EMI

TSA2.5 QA Implementation Review and Support Review activities of QA, test and certification implementations done by the Product Teams Sample review of test plans and tests, compliance with packaging, porting guidelines, validation of documentation, etc. Support Product Teams in effective design and implementation of tests to be used with testing tools such as ETICS. Monitoring of the usage of tools and procedures by all project members by surveys and verifications

TSA2.6 Testbeds Setup, Maintenance and Coordination Setup and maintenance of distributed testbeds for the project continuous integration and testing operations. Coordination and provision of larger-scale testbeds from collaborating resource providers. Verification of availability and reliability metrics of the execution nodes

-- FloridaEstrella - 15-Nov-2010

This topic: EMI > WebHome > EmiProceduresTools > EmiPptGuidelines
Topic revision: r2 - 2012-03-29 - unknown
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback