Music Database Management System

Project Plan
Project Code: MDMS09
Document Code: MDMS09-PP <version 1.3>

The group:
To Viet Anh, Team leader
Tran Cong Phan Vinh, Member
Dao Duy Thanh, Member
Vu Minh Phong, Member
Le Gia Cuong, Member

Instructor and Evaluator

Mr Nguyen Tat Trung

Hanoi, September 11th

MDMS09-Project Plan v 1.3

RECORD OF CHANGE

*A - Added M - Modified D - Deleted

Effective A*
Changed Items Change Description New Version
Date M, D

Sep 10th Project plan A Newly created 1.0

Sep 10th Project plan M Constraints and assumptions 1.1

Sep 11th Project plan M Project schedule 1.2

M Project risks

Sep 11th Project plan A Project work breakdowns 1.3

A Project Communication

MDMS Project Plan/MDMS09/FU v1.3 Internal use 2/12

MDMS09-Project Plan v 1.3

SIGNATURE PAGE

ORIGINATOR: Tô việt Anh Sep 11th

Project Manager

REVIEWERS: Nguyễn Tất Trung Sep 11th

Software Engineering Teacher

APPROVAL: Tô việt Anh Sep 11th

Project Manager

MDMS Project Plan/MDMS09/FU v1.3 Internal use 3/12

MDMS09-Project Plan v 1.3

TABLE OF CONTENTS

1. INTRODUCTION........................................................................................6

1.1. Project description...............................................................................6

1.2. Assumptions and constraints................................................................6

2. PROJECT ORGANIZATION........................................................................7

2.1. Organizational structure.......................................................................7

2.2. Project team.......................................................................................7

3. PROJECT RISKS........................................................................................8

4. TOOLS AND INFRASTRUCTURE................................................................9

4.1. Software.............................................................................................9
4.2. Hardware............................................................................................9
4.3. Others infrastructures..........................................................................9

5. PROJECT WORK BREAKDOWN.................................................................9

5.1. Critical Dependencies...........................................................................9

5.2. Milestones...........................................................................................9
5.3. Deliverables.......................................................................................10

6. PROJECT SCHEDULE...............................................................................11

7. PROJECT COMMUNICATION...................................................................12

7.1. Internal project communication..........................................................12

7.2. Communication with management board of department.......................12
7.3. Communication with customer............................................................12
7.4. Others...............................................................................................12

MDMS Project Plan/MDMS09/FU v1.3 Internal use 4/12

MDMS09-Project Plan v 1.3

DEFINITIONS AND ACRONYMS

Table 1: Definitions and Acronyms

Acronym Definition Note

PM Project Manager

PTL Project Technical Leader

TL Team Leader

QA Quality Assurance Officer

CC Infrastructure Configuration Controller

DV Developer

URD User Requirement Document

SRS Software Requirement Specification

ADD Architecture Design Document

DDD Detail Design Document

TP Test Plan

TC Test Case

SC Source Code

CM Configuration Management

CSCI Computer Software Configuration Items

CI Configuration Item

PVCS VM PVCS Version Manager

VSS VM Visual SourceSafe Version Manager

MDMS Music Database Management System

MDMS Project Plan/MDMS09/FU v1.3 Internal use 5/12

MDMS09-Project Plan v 1.3

1. INTRODUCTION

1.1. Project description

Project name : Music Database Management system

Project Code: MDMS09

Customer: Music lovers

Project manager: Tô Việt Anh

Project category: X New development  Maintenance  Other

Business domain:
Scope and Objective
Free-ware
The purpose of the project is to deliver a new and efficient
MDMS to the music lovers. This MDMS must be a free-ware and
contains enough functions to meet the need of the users.
What is the product, result of the project?
The scope of this project is to create a new MDMS and deliver it to the
user.

Committed billable effort Free

Committed calendar effort 14 days

Committed effort usage (man-

2.0 man- month
month1):

Project start date: Sep 7th 2009 Expected end date: Sep 28th 2009

Planned duration: 21 days

1.2. Assumptions and constraints

1.2.1. Constraints

Table2: Constraints

No Description Type2

1 The interface of MDMS should be simple enough for users to be able to use it Product
easily after using the system for no more than 10 minutes.

2 The size of database must be large enough to store information which increases Product
when used.

3 Delivery on time and at the appropriate place. Organization

4 The software must be run from .exe file extension (in Windows version). Product

1
1 man-month equals 25 man-day
2
These are type normally: staff, budget, equipment, schedule, infrastructure, business, ...

MDMS Project Plan/MDMS09/FU v1.3 Internal use 6/12

MDMS09-Project Plan v 1.3
1.2.2. Assumptions

Table3: Assumptions

No Description Type3

1 Communication available between members and teacher through mobile phone Business
and email.

2 No late submitting of documents Schedule

2. PROJECT ORGANIZATION

2.1. Organizational structure

2.2. Project team

Table4: Project team

3
These are type normally: staff, budget, equipment, schedule, infrastructure, business, ...

MDMS Project Plan/MDMS09/FU v1.3 Internal use 7/12

MDMS09-Project Plan v 1.3
No. Name Position Start Date End Date Working time4

1 Tô Việt Anh PM Sep 7th 2009 Sep 28th 2009 2 hours per day

2 Đào Duy Thanh DV1 Sep 18th 2009 Sep 19th 2009 2 hours per day

3 Trần Công Phan Vinh DV2 Sep 18th 2009 Sep 19th 2009 2 hours per day

4 Tô Việt Anh DV3 Sep 18th 2009 Sep 19th 2009 2 hours per day

5 Lê Gia Cường Designer 1 Sep 15th 2009 Sep 17th 2009 2 hours per day

6 Vũ Minh Phong Designer 2 Sep 15th 2009 Sep 17th 2009 2 hours per day
th th
7 Vũ Minh Phong Analyst 1 Sep 14 2009 Sep 14 2009 2 hours per day

8 Lê Gia Cường Analyst 2 Sep 14th 2009 Sep 14th 2009 2 hours per day

9 Đào Duy Thanh Tester 1 Sep 18th 2009 Sep 23th 2009 2 hours per day

10 Trần Công Phan Vinh Tester 2 Sep 18th 2009 Sep 23th 2009 2 hours per day

11 Vũ Minh Phong Tester 3 Sep 18th 2009 Sep 23th 2009 2 hours per day

3. PROJECT RISKS
Table5: Project Risks
Risk Description Probability Impact Trigger Status Mitigation Plan Contingency Plan

- Time constraints High Serious N/A Open 1. More work from team 1. Extend schedule of
are 2 weeks, which members. requirement phase.
is too short. The
project may not 2. Frequent relaxing is 2. Reduce time of the
finish on time. needed. not yet necessary phase.

Requirement Medium Tolerable Teacher Open Team members need to A requirement plan
changes: New ideas gives generate ideas at first stage. needs to be seriously
may turn up during more considered first.
project advices
development. Some about the
can change the project
whole structure of
the project

Compatibility: Mac High Tolerable When Close a future version for different N/A
OS, UNIX and deliver the OS is planned
Linux users may not product to
run the application the users
due to the fact that
the program is
written in VS on
Windows

People: the team High Serious N/A Close the team needs constant N/A
consists of 5 guidance from the instructors
inexperienced in
software project
members

4
Fill here any note about working time as % of total effort or how many hours per day or per week.

MDMS Project Plan/MDMS09/FU v1.3 Internal use 8/12

MDMS09-Project Plan v 1.3
4. TOOLS AND INFRASTRUCTURE

4.1. Software

Visual C++ 9.0 Express Edition.

MS Word 2007.
MS Excel 2007.
MS Visio 2007.
MS Project 2007.

4.2. Hardware

Laptops and desktop computers are needed for designing, coding and testing.

4.3. Others infrastructures

- A room is needed for team meeting.

- Internet and mobile phone services are needed for communication.

5. PROJECT WORK BREAKDOWN

5.1. Critical Dependencies

Table6: Critical dependencies

No Critical dependency Expected Delivery Note

Date

1 Dependence on other media players NA The MDMS needs to be integrated into

another media player to make full use
of it. Possible candidates are Foobar or
Winamp.

5.2. Milestones
5
Table7: Project milestones
No Milestone Milestone date Objectives, Notes

1 Project Startup Sep 7th

2 Feasibility Study Submit Sep 9th Review and Submitting

3 Project Plan Submit Sep 11th Group’s review, approval and Submit

4 Requirements Submit Sep 16th Review Requirements paper and submit

5 Test Documents Writing and Sep 22nd Create Test-cases

Submitting

6 Project Complete Sep 23rd

5
This table and other tables in this project plan may be referred to appendixes. It’s permitted to replace tables by text but this
information in table should be required.

MDMS Project Plan/MDMS09/FU v1.3 Internal use 9/12

MDMS09-Project Plan v 1.3
5.3. Deliverables
6
Table8: Project deliverables to customer
No Deliverable Delivery date Delivery location Note

1 Feasibility Study Sep 9th Instructor

th
2 Project Plan Sep 11 Instructor

3 Requirements Paper Sep 16th Instructor

4 Test Paper Sep 22nd Instructor

6
This table and other tables in this project plan may be referred to appendixes. It’s permitted to replace tables by text but this
information in table should be required.

MDMS Project Plan/MDMS09/FU v1.3 Internal use 10/12

MDMS09-Project Plan v 1.3
6. PROJECT SCHEDULE

MDMS Project Plan/MDMS09/FU v1.3 Internal use 11/12

MDMS09-Project Plan v 1.3
7. PROJECT COMMUNICATION

7.1. Internal project communication

- Project Topic, Documents must be approved by all members of the team. All team are free to
raise ideas and opinions.
- Communication is via mobile phone, instant messengers, emails as well as face-to-face
- Meetings for progress reports are held twice a week. If serious problems occur, unplanned
meetings are held.

7.2. Communication with management board of department

- The team receives frequent supervising from project leader and subject lecturer.

7.3. Communication with customer

- The software written is free and reviewed by interested users.

- Users’ reviews include requirements, requirement changes and feedbacks.
- Serious complaints are solved immediately. Others may be solved during the maintenance
phase.

7.4. Others

N/A

MDMS Project Plan/MDMS09/FU v1.3 Internal use 12/12