Short Guides to IDA Quality Assurance Guidelines. Development and Validation Phase. Issue 2.0

Transcription

1 Short Guides to IDA Quality Assurance Guidelines Development and Validation Phase Issue 2.0

2 Short Guide Development and Validation Phase Page ii TABLE OF CONTENTS 1 PREFACE Purpose of this document DEVELOPMENT AND VALIDATION PHASE SHORT DESCRIPTION Development and Validation phase objectives Main activities Discipline Mapping...5

3 Short Guide Development and Validation Phase Page 1 1 PREFACE 1.1 PURPOSE OF THIS DOCUMENT #1 This document is a short guide to be used by IDA Projects as part of the IDA Quality Assurance Guidelines. It is intended to assist the relevant management or technical staff, whether client or contractors, in establishing proper ways of working within each project life-cycle phase. It is also useful background reading for anyone involved in developing or monitoring the IDA Quality Assurance Guidelines.

4 Short Guide Development and Validation Phase Page 2 2 DEVELOPMENT AND VALIDATION PHASE Purpose: To develop the service or tool according to requirements and to test that the result is as expected. To effectively monitor contractors, risks progress and changes within the project. Development and Validation Input: Main activities: Output: GIP Project Definition System requirements User requirements Contracts Construct the service or tool Perform tests Manage change Manage risks Manage plans and replan Report on progress Manage contractors Global Implementation Plan (Revised) Operational Quality Plan (First Issue) Service Level Agreement (First Issue) Test records Revised time plans Progress reports Tested service or tool

5 Short Guide Development and Validation Phase Page 3 3 SHORT DESCRIPTION 3.1 DEVELOPMENT AND VALIDATION PHASE OBJECTIVES The goal of the development and validation phase is to clarify the remaining requirements and to complete the development of the service or tool based upon the base lined and selected architecture (IDA Architecture Guidelines). This phase is in some sense a manufacturing stage, where the emphasis is on managing the contractors (if any), control and monitoring of progress, renegotiation with users and managing change in general. The development effort will concentrate on developing the service or tools and installing appropriate hardware. The phase ends when the service or tool is considered to be mature enough to release into user community. The primary objectives of the development and validation phase include: Minimising development costs by optimising by adequate resource planning. Monitoring and controlling fulfilment of requirements (quality, risk, safety etc.) Achieving fully functional versions of the service or tools as rapidly and often as practicable Completing the analysis, design, development and testing of all required functions. To iteratively and incrementally develop a complete service or tool that is ready to deliver to its user community. This implies describing the remaining outstanding requirements, establishing the correct design, completing software implementation and testing the software. To assure that the adequate prerequisites are established in order to receive the service or tool in the user community. To assure that the users and sites are prepared to receive the service or tool To monitor and control. 3.2 MAIN ACTIVITIES Develop service or tool. This involves the basics of software development and includes design and analysis activities and test activities. Project Management should monitor and control the contractor s progress towards agreed activity plan according to well-defined work-breakdown structure based on functionality and requirements. A robust and agreed upon architecture is essential if any significant benefits are to be achieved. Perform tests. This involves creating test scenarios and descriptions that cover the requirements and to perform basic tests and system tests, mainly in the development environment.

6 Short Guide Development and Validation Phase Page 4 Manage Changes. To effectively set up a change management process that includes the proper authorization required for correct decision-making; further, to define what is to be an approved change and what is not. Manage Risks. This involves continuous monitoring of risks and to address them at each project meeting. Mitigation plans should be followed. Report on progress. This involves reporting, at defined intervals, on the progress and status of the project and its deliverables. All information is to be made available to all stakeholders and other parties involved. Manage contractors. This involves monitoring, change management and communication with the contractor. It also implies monitoring the contractors processes and reviewing and approving deliverables from the contractor, and also includes the performance of joint reviews.

7 Short Guide Development and Validation Phase Page DISCIPLINE MAPPING Discipline Activity Reference Template/Checklist Project Management Manage change Project Risk Management Project Planning Requirements Management Technical Definition Report on progress Manage contractors IDA-MS-MPR-i1 IDA-MS-QPR-i1 01PMM_gGIP031a IDA-MS-PMQP-i3 Project Definition Document Monthly Report Quarterly Report Global Implementation Plan Project Management and Quality Plan Change Control Plan IDA-MS-CCP-i1 Manage risks IDA QAG Risk Project Risk Management Management Plan and Risk Matrix Manage plans and 01PMM_gGIP031a Global Implementation Plan replan Project Definition Document Work breakdown structure Manage changes IDA-MS-UR-i1 User Requirements Develop the service or tool IDA-MS-TD-i1 IDA-MS-PMQP-i3 IDA-MS-UG-i1 IDA-MS-CMP-i1 Verification and Develop the service IDA-MS-RTP-i1 validation or tool IDA-MS-TS-i1 Deployment Prepare for roll-out IDA-MS-OQP-i2 Phase output Decision point 6 IDA-MS-SLA-i2 IDA-QAG-SGIntro Technical Description Project Management and Quality Plan User Guide Configuration Management Plan Review and Test Plan Test Specification Operational Quality Plan (First Issue) Service Level Agreements (First Issue) Global Implementation Plan (Revised) Operational Quality Plan (First Issue) Service Level Agreements (First Issue) Test records Revised time plans Progress reports Tested service or tool

8 Short Guide Development and Validation Phase Page 6 DOCUMENT CONTROL Title: Issue: Issue 2.0 Date: 11 November 2002 Author: Distribution: Reference: Filename: Control: Short Guide for Development and Validation Phase Maria Johnson Kjällström EC DG Enterprise Joris Heeren Project Team IDA-QAG-SG IDA-QAG-SG-Dev Re-issue as complete document only DOCUMENT SIGNOFF Nature of Signoff Person Signature Date Role Authors Maria Johnson Kjällström 11 November 2002 Senior Consultant Reviewers Klas Johansson Åke Norman 11 November 2002 Framework Mgr Senior Consultant DOCUMENT CHANGE RECORD Date Version Author Change Details 13 October Maria Johnson Kjällström First Issue 20 October Maria Johnson Kjällström Changes made after review with Mr Joris Heeren 06 November Maria Johnson Kjällström Changes made after meetings with DG AGRI and EEA 13 November Maria Johnson Kjällström Changes made after internal TietoEnator review 14 November Klas Johansson Changes after review of IDA 11 November Maria Johnson Kjällström Changes made after updates of in IDA QAG