Software Project Management Plan
Version 1.0
1/29/04

Major Field Achievement Test Grading System

Kiran Gandu

Submitted in partial fulfillment
Of the requirements of
Masters Studio Project
Jacksonville State University

Change History

|Major Field Achievement Test |
|SPMP Version 1.0 |Release date: 1/29/04 |Baseline Version |
| | | |
| | | |

Preface

The purpose of this document is to specify the project plan to develop the Major Field Achievement Test (MFAT) grading system. The primary audience is the project advisor, Dr Dennis S. Martin, and other members of the studio committee, Dr Chi-Chin Chao and Dr Jan Case. This document outlines a brief plan about how the project is to be shaped and also includes the milestones and deliverables. The SPMP document will serve as a guide for the student, developing the product as part of the project. Updates of this document will serve to record the progress of the project.

Table of Contents

Change History ii
Preface iii
Table of Contents iv
List of Figures v
1.0. Overview 1 1.1. Project Summary 1 1.1.1. Scope, Purpose and Objectives 1 1.1.2. Assumptions and Constraints 3 1.1.3. Project Deliverables 3 1.1.4. Schedule and Budget Summary 4 1.2. Evolution of the Plan 5
2.0. References 6
3.0. Glossary 7
4.0. Project Organization 8 4.1. External Interfaces 8 4.2. Internal Interfaces 8 4.3. Roles and Responsibilities 8
5.0 Managerial Process Plans 9 5.1. Work Plan 9 5.1.1. Work Activities 9 5.1.2. Schedule Allocation 9 5.1.3. Resource Allocation 10 5.1.4. Budget Allocation 10 5.2. Control Plan 10 5.2.1. Requirements Control Plan 10 5.2.2. Schedule Control Plan 10 5.2.3. Budget Control Plan 10 5.2.4. Quality Control Plan 10 5.2.5. Reporting Plan 11 5.2.6. Metrics Collection Plan 11 5.3. Risk Management Plan 11 5.4. Closeout Plan 12
6.0 Technical Process 13 6.1. Process Model 13 6.2. Methods, Tools, and Techniques 13 6.3. Infrastructure Plan 13 6.4. Product Acceptance Plan 13
7.0 Support Process Plans 14 7.1. Configuration Management Plan 14 7.2. Validation & Verification Plan 14 7.3. Documentation Plan 14 7.4. Quality Assurance Plan 15 7.5. Review and Audits 15 7.6. Problem Resolution Plan 15 7.7. Subcontractor Management Plan 15 7.8. Process Improvement Plan 15

List of Figures

1. Figure.1 Schedule 2. Figure 2. Gantt Chart

1.0. Overview

1 Project Summary

1 Scope, Purpose and Objectives

The CMMI is a model for improving and appraising the performance of development organizations. It stands for “Capability Maturity Model Integration”. It is published and developed by the Software Engineering Institute in Pittsburgh, PA. The CMMI is best known for its five levels of organizational maturity namely initial, managed process, defined process, and quantitatively managed process and optimizing process. Each level represents a coherent set of best practices organizations are expected to implement as they become better at what they do.

CMMI methodology at Level 5 (optimizing process) of requires that an organization assess its performance against certain parameters and use this information for process improvement. This applies to university programs as well as to the software development organizations.

For Computer Science there is a nationally nor med test developed by the Educational Testing Service, which will provide comparative national results. Dr.