EMI SA1 Project Wiki Area

Only public material in here

SA1 Summary

SA1 Material

SA1 Useful Links

SA1 Task Details

TSA1.1 – Work Package coordination

Actions

TSA1.2 – Software Maintenance (Task leader: INFN. All partners allocate effort to maintenance according to their technical expertise)

This task deals with the analysis and correction of software defects found in released components by users and infrastructure technicians. This task includes the definition of the Software Maintenance, Problem Management and Change Management processes and the continuous execution of the related procedures. The success of this task is measured by its compliance with the agreed procedures and the defect handling trends (average time to close defects, response times, etc).

TSA1.3 – Release Management (Task leader: INFN. Participants: CERN, CINECA, UPJS)
This task deals with release management and coordination and the maintenance of the package repositories,
defining policies and release cycles. This task also covers the smooth transition from many middleware
distributions to one, so that the production infrastructures stay functional without noticeable discontinuity.

TSA1.4 – Quality Control (Task leader: CINECA. All partners allocate effort to the continuous QC tasks according to their technical expertise; CSIC is responsible for the security assessment)
This task consists in the application of QA processes and procedures defined by SA2. All the releases of EMI
components need to satisfy well-defined certification and validation criteria before being included in a stable
EMI distribution, sufficient to guarantee to a high degree of confidence that all EMI products meet or exceed the
requirements set by EGI and that no regression are introduced. The Product Teams are responsible to perform
the QC task as part of their standard maintenance activities. This task also deals with security assessments
of selected EMI components under the coordination of CSIC. The main success criterion of this task is the
availability of regression tests for each resolved software defect.

TSA1.5 – User Support (Task leader: JUELICH. All partners allocate effort to support according to their technical expertise and the defined support shifts) This task consists in the provision of 3rd-level user support for incidents and requests escalated from the user support channels of the customer infrastructures and user communities. The support services and based on Service Level Agreements detailing the services and their expected quality attributes like the response times. The task coordinator is responsible to define the User Support and escalation processes and monitor the correct execution and respect of the SLAs. The main success criteria for this task are average response times for first reply and the average time needed to complete the analysis of an incident, providing either a workaround or filing a defect in the MW tracker.

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2011-07-28 - GiuseppeGiacomoFiameniExCern
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EMI All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2023 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