Iteration Plan (IP) Transportation Grant Fund Database. Team 14

Transcription

1 Iteration Plan (IP) Transportation Grant Fund Database Team 4 Muruganantham Raju Project manager Ayman Khalil Operational Concept Engineer Karim Sacre - Prototyper Kirill Khistayev System Architect Reza B Far IIV&V Stephen Rice IIV&V Zhanna Seitenova Lifecycle Planner December 4th, 0

2 Iteration Plan (IP) Version.3 Version History Date Author Version Changes made Rationale // ZS.0 Original template Updated section Initial draft // MR. Updated section Draft DCP // KK. Populated Tables, Draft DCP /30/ KK. CCD Preparation Plans Draft DCP /04/ KK.3 CCD Preparation Plans and Iteration Overview were updated DCR ARB Comments IP_DCP_Fa_T4_V.33 /04/ ii

3 Iteration Plan (IP) Version.3 Table of Contents VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES...IV TABLE OF FIGURES...V. Iteration Overview...6. Capabilities to be Implemented...6. Capabilities to be Tested Capabilities not to be tested...7. CCD Preparation Plans...8 IP_DCP_Fa_T4_V.33 /04/ iii

4 Iteration Plan (IP) Version.3 Table of Tables Table : Construction iteration capabilities to be implemented...6 Table : Construction iteration capabilities to be tested...7 IP_DCP_Fa_T4_V.3 iv /04/

5 Iteration Plan (IP) Version.3 Table of Figures Элементы списка иллюстраций не найдены. IP_DCP_Fa_T4_V.3 v /04/

6 Iteration Plan (IP) Version.3. Iteration Overview There are 3 iterations planned in the Development phase of the Transportation Grant Fund Database project. Estimated dates are as follows: - construction iteration : /5/-3/9/ - construction iteration : 3/9/- 4/3/ - transition iteration: 4/4/- 5/4/ During the first increment of construction iteration the most important features will be developed, which are must requirements. At the end of this iteration pilot run with system demonstration to the client will be executed. Intermediate feedback forms will be collected from the customers at the end of pilot run. The second increment of the construction iteration will be developing the remaining should and could capabilities, as well as glue coding and debugging already existent functionalities to get ready for the main milestone Core Capability Drive-through. The transition iteration is accountable for the transition of the executable system to the client s production server and training of the users, client and maintainers.. Capabilities to be Implemented Table : Construction iteration capabilities to be implemented Functionality ID Description Priority Increment OC- Role-based access control (RBAC) The system provides the capability of assigning predefined security roles to users OC- Administrators approved user registration OC-3 Electronically storing all project information OC-4 Attaching documents OC-5 Report Generation OC-6 Export project data The system provides the capability to the administrator to selectively approve user registration The system provides the capability of storing all project information and related attached documents electronically The system provides the capability of attaching physical files to the grant fund projects The system provides the capability of generating reports in easy to print format (Quarterly & progress reports) The system is capable of exporting grant fund projects data into XML standard format Could IP_DCP_Fa_T4_V.33 /04/ 6

7 Iteration Plan (IP) Version.3 OC-7 Deadlines & notifications OC-8 Sending s The system provides the capability of setting deadlines for projects and sending reminders before certain due dates by The system provides the functionally of sending s to the users of the system Could Should. Capabilities to be Tested Table : Construction iteration capabilities to be tested Functionality ID Description Priority Increment OC- Role-based access control (RBAC) The system provides the capability of assigning predefined security roles to users OC- Administrators approved user registration OC-3 Electronically storing all project information OC-4 Attaching documents OC-5 Report Generation OC-6 Export project data OC-7 Deadlines & notifications OC-8 Sending s The system provides the capability to the administrator to selectively approve user registration The system provides the capability of storing all project information and related attached documents electronically The system provides the capability of attaching physical files to the grant fund projects The system provides the capability of generating reports in easy to print format (Quarterly & progress reports) The system is capable of exporting grant fund projects data into XML standard format The system provides the capability of setting deadlines for projects and sending reminders before certain due dates by The system provides the functionally of sending s to the users of the system Could Could Should.3 Capabilities not to be tested All capabilities listed above will be tested in either first or second construction increments. IP_DCP_Fa_T4_V.33 /04/ 7

8 Iteration Plan (IP) Version.3. CCD Preparation Plans At the end of the construction phase, Core Capability Drive-through will be organized. Following outlines high level preparation plan of CCD. Hardware Preparation. Minimum hardware required in order to perform CCD: x64 processor; 8GB memory; 80 GB hard disk. Software Preparation. Minimum software required in order to perform CCD: Microsoft Sharepoint 00 Enterprise Edition; MS SQL 008; Microsoft Visual Studio 00; All these setup on Windows 008 R x64 system. SharePoint Login credentials. Required SharePoint login will be enabled for all CCD participants from LADOT. CCD participants. Following LADOT employees will participate in CCD. Maintainers; Program Managers; LADOT Project Managers; Accountants. At least one representative from each of above listed category will take part in the CCD. Additional participants will be identified and included during construction phase. Release notes. The participating LADOT employees will be provided with the release notes which will highlight the following. Increment number; List of features available in current release; List of known bugs; List of workarounds, if any; Other special instructions. Feedback form. Following provides general outline of feedback form. Participant name; Capability tested; List of defects captured; Generic improvement comments; Rate the feature out of 5. IP_DCP_Fa_T4_V.33 /04/ 8

9 Iteration Plan (IP) Version.3 CCD process flow. Core Capability Drive-through will begin at the end of construction phase and it spans for two weeks. The development team will provide a demo of features developed. Each participant will be asked to assess specific features available in the release. Two weeks of time will be given for the participants to independently assess the delivered capabilities. Participants will be encouraged to report bugs through mail as soon as they catch any. At the end of two week duration, each participant will be given a feedback form to provide their official feedback. Intermediate feedback forms can be used as well. CCD follow up plan. The bugs reported by customers will be addressed (within 3 weeks of reporting time) based on severity. The CCD feedback report will be analyzed collectively to identify the list of defects, enhancement requests and improvement plan. Project plan will be updated based on activities identified as a part of CCD follow ups. Customers will be given periodic update on progress of CCD feedback. IP_DCP_Fa_T4_V.33 /04/ 9