PROJECT CHARTER

PURPOSE OF THE DOCUMENT:

This project is aimed at developing a school administration system which

can streamline the administration of school. Its often felt that the school
management is chaotic in nature. It involves many administrative work and
co-ordination. This project is to develop and deploy a web based application
so that the different aspects of a school administration become easy to
handle.

For Internal Use Only

Page 1

PROJECT CHARTER

Project Name: Development of a

Project Number:PN101

web based school administration system

Date:03/16/2013

1.

Revision Number:1

PROJECT GOALS

developing a school administration system which can streamline the

administration of school

2.

SCOPE DEFINITION

Following are the requirements:

1. Users are administrator, teacher, student and parent.
2. It maintains the student profile.
3. Student profile has the personal details of the student, Current standard, History since he/she
took admission, progress report.
4. Teacher Profile.
5. Teacher profile has the personal details of each teacher, skill set etc.
6. Parent is a user who is attached to each student. Parents e-mail address is stored.
7. Administrator has privilege to edit anybodys profile.
8. It publishes the syllabus and that can be up-versioned by teachers.
9. Provision for publishing the progress report by teachers.
10. Bulletin Board for publishing the events.

For Internal Use Only

Page 2

11. Facility to find the weak areas of each student.

12. Facility to find out teacher who can help the student with his/her expertise and who has
bandwidth to do so.

This project can be divided in 3 tier where the back end is database tables. The middle tier is the
applications written in C++ on Unix which handles the database queries and fetch relevant data.
The front end represents the User Interface and sends the query to middle tier.

4.

PROJECT MILESTONES
1

Requirement
Specifications

1. Collecting Requirements

High Level
Design

1.Document detailing the design

2. GUI snapshots
3. Requirement traceability
matrix.
4 Restrictions / Limitations
4. Design test cases for each
requirement

Detailed Design

Document detailing the

following points
1. List of design options, pros
and cons of each option, which
option is taken and the rational
behind that.
2. Design details broken
functionality wise.
3. List of class and the interfaces
of that class.
4. File names. ( Have to follow
standard naming convention )

For Internal Use Only

Page 3

5.

ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES

None

6.

RELATED DOCUMENTS

Use cases

7.

PROJECT ORGANIZATIONAL STRUCTURE

Identify the key stakeholders and team members by function, name and role.
Function

Name

Role

Managing the project

Project Manager

Designing the architecture

Architect

Developing the application

Developer

8.

PROJECT AUTHORIZATION

Approved by:

Business Manager

2/16/2013

Approved by:

Project Manager

3/12/2013

For Internal Use Only

Page 4