Iteration Plan (IP) Leamos. Team number 7. Name Address Primary Role Secondary Role

Transcription

1 Iteration Plan (IP) Leamos Team number 7 Name Address Primary Role Secondary Role Monty Shah montysha@usc.edu Project Manager Life Cycle Planner David Wiggins dgwiggin@usc.edu IIV&V Off-campus Shaper Pragya Singh pragyasi@usc.edu System Architect Prototyper Shantanu Sirsamkar sirsamka@usc.edu Requirements Engineer Feasibility Analyst Suchita Doshi suchitad@usc.edu Prototyper Operational Concept Engineer Swapnil Savdekar savdekar@usc.edu Life Cycle Planner System Architect i

2 Version History Date Author Vers ion Changes made 11/21/11 Swapnil 1.0 Original template for Section 1. 12/12/11 Swapnil 1.1 Changes in capabilities plan Rationale Initial draft. Updated for DCR ARB, updated version ii

3 Table of Contents ITERATION PLAN (IP)... I VERSION HISTORY... II TABLE OF CONTENTS... III TABLE OF TABLES... IV TABLE OF FIGURES... V 1. Iteration Overview Capabilities to be Implemented Capabilities to be Tested Capabilities not to be tested CCD Preparation Plans iii

4 Iteration Plan Version 3.1 Table of Tables Table 1: Capabilities to be Implemented (CR)... 6 Table 2 : Capabilities to be Tested... 7 Table 3 : Capabilities not to be tested... Error! Bookmark not defined. iv

5 Iteration Plan Version 3.1 Table of Figures None v

6 1. Iteration Overview In the development phase of the Leamos project, there will be two iterations in the Construction Iteration. This document corresponds to the first iteration. This iteration begins at the end of Rebaselined Development Commitment Review (RDCR), and the milestone is Core Capability Drive-through. At the end of this iteration, we ll have a list of deliverables including executable core capabilities, executable system and Initial Operational Capability Working Set. 1.1 Capabilities to be Implemented In the first iteration, we will implement all the must-have capability requirements listed in the OCD Section OC-1 Simple username and password for the users Table 1: Capabilities to be Implemented No. Description Priority Increment There should be simple username and password for the students so that they can remember the credentials easily. OC-2 Flash to HTML 5 conversion OC-3 Data Migration OC-4 Integrate the current system with third party merchant system OC-5 Availability of username and password immediately after buying courses OC-6 Report generation The old lessons, currently in Flash format should be converted in HTML 5 format which will allow the users to watch the lessons on any HTML 5 supported browser The old database, currently in MS SQL, needs to be migrated in the new Database in MySQL which will help the system admins to maintain only a single database instead of two. The current system should allow the users to buy the course licenses online. This will help the users to get faster access to the courses. The customers buying the licenses should be provided with an immediate automated username and password. The admin should be able to generate reports to track the progress of the students and maintain various other records. 6

7 OC-7 Documentation / Video Tutorials Easy to understand documentation and video tutorials should be provided to the admin which will help them in maintaining the site easily (how to add/ remove courses etc.) without the requirement to hire another set of developers to do the same task. Must Have 2 OC-8 Forgot Password functionality OC-9 Videos in HTML 5 format OC-10 User Management to other organizations OC-11 Sales Website The system should provide the users a forgot password option if they forget their passwords, which will provide them their respective passwords on confirming their identity instead of contacting the admin every time to provide them with their passwords. The system should be able to allow the students to watch lectures online on the Leamos website on HTML 5 supported devices and browsers. Organizations will be able to manage their own students. Could Have 2 Could Have 2 Website for online sale of courses. Must have 1 Level of Service Goals LOS-1: Availability: The system should be up and running at all possible times except for maintenance time or system shut down LOS-2 Security: The system should be able to provide secure transfer of funds when a customer buys license(s) and pays online. This is done by Course Merchant. LOS-2 Ease of use: The system should be easy to use so that it is easier for the students to adapt the system Priority Level Must have Must have Must have 1.2 Capabilities to be Tested All the capabilities listed in Table 1 in Table 2 will be tested in this iteration. Capabilities to be tested are listed as follows. Table 2 : Capabilities to be Tested No. Description Priority Increment 7

8 OC-1 Simple username and password for the users OC-2 Flash to HTML 5 conversion OC-3 Data Migration OC-4 Integrate the current system with third party merchant system OC-5 Availability of username and password immediately after buying courses OC-6 Report generation OC-7 Documentation / Video Tutorials There should be simple username and password for the students so that they can remember the credentials easily. The old lessons, currently in Flash format should be converted in HTML 5 format which will allow the users to watch the lessons on any HTML 5 supported browser The old database, currently in MS SQL, needs to be migrated in the new Database in MySQL which will help the system admins to maintain only a single database instead of two. The current system should allow the users to buy the course licenses online. This will help the users to get faster access to the courses. The customers buying the licenses should be provided with an immediate automated username and password. The admin should be able to generate reports to track the progress of the students and maintain various other records. Easy to understand documentation and video tutorials should be provided to the admin which will help them in maintaining the site easily (how to add/ remove courses etc.) without the requirement to hire another set of developers to do the same task. Must Have 2 OC-8 Forgot Password functionality OC-9 Videos in HTML 5 format OC-10 User Management to other organizations The system should provide the users a forgot password option if they forget their passwords, which will provide them their respective passwords on confirming their identity instead of contacting the admin every time to provide them with their passwords. The system should be able to allow the students to watch lectures online on the Leamos website on HTML 5 supported devices and browsers. Organizations will be able to manage their own students. Could Have 2 Could Have 2 8

9 OC-11 Sales Website Website for online sale of courses. Must have Capabilities not to be tested All capabilities listed above will be tested. 9

10 CCD Preparation Plans The core capability drive through will be part of the next semester. So this will be completed in the next semester. << Identify the clients and other users who will be involved in the Core Capability Drive-through, the usage scenarios that it will support, and the specific CCD preparation plans and milestones. These may include - user context-setting - site preparation dry runs, - feedback forms, and - CCD risk management plans. >> To be defined later in the Development phase. 10