Iteration Plan. LEMA Pilot School Integrated Scheduling System. Team No. 12. Name Primary Role Secondary Role

Size: px

Start display at page:

Download "Iteration Plan. LEMA Pilot School Integrated Scheduling System. Team No. 12. Name Primary Role Secondary Role"

Lester Todd
5 years ago
Views:

1 Iteration Plan LEMA Pilot School Integrated Scheduling System Team No. 12 Name Primary Role Secondary Role Neelima Agarwal Life Cycle Planner Project Manager Aakash Shah Prototyper Feasibility Analyst Madhulika Mazumdar Operation Concept Engineer Project Leader Harsimran Singh Benipal Requirements Engineer Life Cycle Planner Eunyoung Hwang Software Architect Requirements Engineer Tianyin Zhou Developer Prototyper Louis Demaria IIV&V Developer 12/02/2011

2 Version History Date Author Version Changes made Rationale 12/02/2011 Neelima Agarwal 1.0 Completed section 1 DC package ii

3 Table of Contents ITERATION PLAN... 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... 8 iii

4 Table of Tables Table 1: Capabilities to be implemented in iteration 1..7 Table 2: Capabilities to be implemented in iteration 2..8 IP_DCP_F11a_T12_V1.0.doc iv Version Date: 12/02/2011

5 Table of Figures Figure 1: <Figure Title>... IP_DCP_F11a_T12_V1.0.doc v Version Date: 12/02/2011

6 1. Iteration Overview This document specifies the iteration plan for the development phase construction iteration for the LEMA Integrated Scheduling System. The development phase starts after the rebaselined foundations phase when team re-formation is done (since only two members are continuing to 577b, new members will be required and new roles will be assigned to them). The construction iteration of the development phase starts in the second week of February 2012 and continues till the second week of April The construction iteration of the development phase consists of two iterations. Iteration 1 starts from second week of February 2012 and continues till the last week of March Iteration 2 starts from first week of April 2012 and continues till the second week of April Core capability drivethrough is conducted at the end of iteration 1. The development phase has a transition iteration which comes after the construction iteration. It begins at the end of the construction iteration 2 and continues till the end of the semester. The transition iteration accounts for the transition of the system and training if the users and clients. A detailed plan for the construction and transition iterations of the development phase has been documented in the project plan. Major milestones and products for each iteration can be found in the life cycle plan. 1.1 Capabilities to be Implemented Iteration 1: The capabilities to be implemented in the first iteration will be the capability requirements that have a high priority, with low ease of implementation or are required for development of other capability requirements. Also, since the system needs to be integrated with the system being developed by team 4, the capabilities which are required for integration of the two systems are also implemented during the first iteration. 6

7 Table 1: Capabilities to be implemented in the iteration 1 Capability Requirement Description Priority CR- 1 : Online application for students subject registration Students should be able to fill in their choices for various subjects. CR-2 : locking certain classes. The administration should be able to lock certain classes to certain time CR-3 : Authentication to the system CR-4: Integration with family accountability system CR-5: Student course requests are viewed/approved/rejected by counselor CR-6: Schedule generation CR- 9: map teachers to course sections CR-10: view alternate schedules CR- 12 : LAUSD constraints CR- 13 : Detailed Database CR- 14: Providing Information to team 04 frames The user logs in from the interface from team 04 and in an authenticated session from where it is redirected to our system. Thus we check the cookie to confirm that they were in an authenticated session. The cookie would have user type, user id and authentication key. The system should interact with the system being developed by team 04 and get teacher information, student information, authenticated use cases The counselor can review all the courses requested by the student and can edit or approve or disapprove the student request Helps the administration in scheduling a time table for the school Teachers are assigned a particular course section by the scheduler The administrator can view alternate schedules The various LAUSD constraints should be entered into the database through a simple UI Database to contain student details, course details and teachers details Provide team with the teacher course list, student course list and/or overall course list. 7

8 Iteration 2: The capabilities to be implemented in the second iterations are all the remaining capability requirements. Table 2: Capabilities to be implemented in the iteration 2 Capability Requirement Description Priority CR- 7 : Track the progress of a particular student Track student progress from A-G requirements for mapping CR- 8: Student Progress Enhanced Ability of students to see how many more credits they need to complete a particular S (Should CR-11: GPA for various universities grade Displays how much GPA is required for Cal States,CSU and other universities S (Should 1.2 Capabilities to be Tested All the capability requirements that are implemented need to be tested. The list is the same as given in tables above respective to the iterations for which they have been mentioned. 1.3 Capabilities not to be tested There is no capability that doesn t need to be tested. All capabilities require testing and modules need to be integrated and tested as well. 2. CCD Preparation Plans 8

Regression Test Package (RTP)

Regression Test Package (RTP) LEMA Pilot School Integrated Scheduling System Team Number 12 Name Primary Role Secondary Role David Wiggins Project Manager Developer Aakash Shah Prototyper Developer Kushalpreet