Iteration Plan (IP) Version 3.2 Version No X.Xx

Iteration Plan (IP) Version 3.2 Version no x.xx

Iteration Plan

PROJECT TITLE
LEMA FAMILY ACCOUNTABILITY SYSTEM
TEAM NO
#04
TEAM MEMBERS & ROLES
NAME / ROLES
Teawon Han / Project Manager
Zhen Huang / Feasibility Analyst
Ziming Wei / Operational Concept Engineer
Xiali Ma / Life Cycle Planner
Ying Yang / Life Cycle Planner
Ian Williams / Requirements Engineer
Kimberly Krause / IIV&V /
System Requirements Engineer

12/11/2011

Version History

Date / Author / Version / Changes made / Rationale /
12/02/11 / Ying Yang / 1.0 / · Initial version, filled in the sections / · Initial version of the DC package
12/05/11 / Ying Yang / 1.0 / · Edit the test plan part / · To provide detail of what will be tested
12/11/11 / Ying Yang / 3.2 / · Added must-have CRs
· Changed the version number to be 3.2 / · In SSRD 3.2 there are a couple more must-have requirements added
· The version number should start from 3.1 in the previous version as it’s in foundation phase

Iteration Plan i

Version History ii

Table of Contents iii

Table of Tables iv

Table of Figures v

1. Iteration Overview 6

1.1 Capabilities to be Implemented 6

1.2 Capabilities to be Tested 7

1.3 Capabilities not to be tested 8

2. CCD Preparation Plans 8

IP_DCP_F11a_T04_V3.2.doc Version Date: 12/11/11

Table of Contents

Table of Tables

Table 1: <Table Name> 错误！未定义书签。

IP_DCP_F11a_T04_V3.2.doc Version Date: 12/11/11

Table of Contents

Table of Figures

Figure 1: <Figure Title> 错误！未定义书签。

IP_DCP_F11a_T04_V3.2.doc Version Date: 12/11/11

Iteration Plan (IP) Version 3.2 Version no

1. Iteration Overview

This is the first iteration of the development phase. The two iterations – construction iteration and the transition iteration will be divided by the Core Capability Drive-through. The first iteration will be implementing all the core capabilities and by the Core Capability Drive-through all must-have requirements need to be fulfilled.

1.1 Capabilities to be implemented

1.2 Capabilities to be Tested

Id
(Autogenerated)
CR # / Requirement Name / Description / Priority
CR - 1 / Multi-School Support / In the future, there may be more than one LEMA school, so school codes must be added to each student's data to break data down according to school. / M (Must have)
CR - 2 / Scatterplot Reporting / The system must show scatterplots that show students where they stand for attendance and grades. / M (Must have)
CR - 3 / Reservation System / System must keep track of all materials, such as books, that have been borrowed by students. / M (Must have)
CR - 4 / Statistical Data / System must have aggregate student data calculations such as average and standard deviation for grades. / M (Must have)
CR - 5 / Pie Chart for Grade Magnitude / System must have a chart that shows how much of a student's grade is made up of each category of work (projects, test, hw, etc.) / M (Must have)
CR - 6 / Daily Reporting / System must have the ability to update student grade/
attendance reports daily. / M (Must have)
CR - 7 / Student Progress Over Time / System must show data for student GPA, number of credits completed, and attendance rate for the current term and for previous months / M (Must have)
CR - 8 / Data Format / Number of missing assignments, tardies, and absences must be a whole number, not a percentage. / M (Must have)
CR - 9 / Track Parent Notifications / The system must keep track of all communication between teachers and between teachers/parents that goes through this system. / M (Must have)
CR - 10 / Parent Communication Page / The system must support sending email and text messages between teachers and teachers/parents. / M (Must have)
CR - 11 / Levels of Access / The system must offer 5 levels of access: student, parent, 2 levels of teachers, and admin. / M (Must have)
CR - 12 / Export from Easy Grade PRO / The system must accept a text file (including XML), parse the information it contains, and store that information in a database. / M (Must have)
CR - 14 / Missing Assignments / The system must store missing assignments for each student separated by class / M (Must have)

1.3 Capabilities not to be tested

All capabilities to be implemented need to be tested since they’re all must-have capabilities and they need to be ensured functioning.

2. CCD Preparation Plans

Users that will be involved in the Core Capability Drive-through will be Beth and Scott. Both of them will login to the system as supervisor and regular teacher to test the system’s capability. They will be testing generating student performance report and exporting student data, inputting student attendance data as main purpose. They will be provided a test plan which covers the following:

· UC-3: Teachers input students’ data into system

· TC-01-01 Enter attendance information (Nominal)

· TC-01-02 Enter attendance information (Database error)

· UC-2: Student and parents check the performances (grade and attendance) in school

· UC-4 : Notify parents the students’ school performances

· TC-04-01 Generate Reports

· TC-04-02 Report Database Error

· UC-6: access resources

· UC-5: Manage resources

· TC-03-01 Update the allocations of resources to students

· TC-03-02 Resources Database Error

Beth and Scott should be following the test plan to test all the must-have capabilities. All the cases are for different purpose so not following the exact order will not impact on testing the performance.

IP_DCP_F11a_T04_V3.2.doc Version Date: 12/11/11