Facebook Storyteller

Project Management Plan

EEL5881, Fall 2008

Modification history:

Team Name: Facebook Storyteller.

Team Members:

• Joan Baldriche -baldriche85@gmail.com
• Pete Clements -fltvvocds@gmail.com
• Anusha Kotha -anushakotha@gmail.com
• Sean Williams -Sean Williams 

Contents of this Document

Project 0verview

Reference Documents

Applicable Standards

Project Team Organization

Deliverables

Software Life Cycle Process

Tools and Computing Environment

Configuration Management

Quality Assurance

Risk Management

Table of Work Packages, Time Estimates, and Assignments

PERT Chart

Technical Progress Metrics

Plan for tracking, control, and reporting of progress

Project 0verview

Our project deals with the development of a facebook application that allows a set of friends to tell a round-robin story. That is, one user will contribute one part of the story, and then pass it to a friend, who will then continue the story. The last user to receive the story will be able to determine the user who will receive it next, and if the next user refuses, should be able to choose another user. At any time, all of the involved users should be able to look at the full story.

Reference Documents

• Concept of Operations
• Software Requirements Specification
• Test Plan

Applicable Standards

• Coding Standards

• The source code for the application will be written in PHP language and team should follow the PHP code conventions given by http://www.dagbladet.no/development/phpcodingstandard/.

• Document Standards

  • The documentation will be written using the templates provided by the EEL5881 Software Engineering Course at the University of Central Florida.
  • Font: Times New Roman
  • Font Size: 12
  • Spacing: Single
  • Spell and Grammar Checking: Microsoft Word Spell Checker
  • Table of Contents: Included at top of each document
  • History:Modification history will be at the top of each document and updated by developers upon making document changes

• Artifact Size Metric Standards

  • The size of project will be determined by the number of lines of code in the project.

Project Team Organization

Our team consists of the following members Pete Clements, Sean Williams, Anusha Kotha and Joan Baldriche. Team will ensure that each member will equally participate in all aspects of the project.

• Pete Clements will be responsible for maintaining team website and works on the requirements acquisition from the client.
• Anusha Kotha will perform tasks on project scheduling,planning and validating the technical progress of the project.
• Seam Williams will work on system designing and maintaining the face book canvas page.
• Joan Baldriche will be in charge of quality assurance and testing the system.
• All team members will assist others as needed to ensure proper progress of the project.

Team face-to-face meetings are scheduled every Saturday and online meetings are conducted through e-mail. Communication with the client shall occur through e-mail and personal meetings as required.

Deliverables

Software Life Cycle Process

The team follows a rapid prototyping model called evolutionary model. The model is well suited as our system is small interactive system and it helps in easy implementation of modifications at any stage without any dependencies. Additionally, the model allows the flexibility in system design as required by the customer.

Tools and Computing Environment

Client Side

Client can use any computer with a Web Browser to access our application

Server Side

The application will be developed on Facebook platform using PHP and FBML languages. The application server is apache2 and mySQL and it interfaces with Facebook server using Facebook API from Facebook tools kit.

Configuration Management

Each team member will work on different documents and software units. The team proposes the changes if necessary to be carried out in respective code units and documents. The team members are responsible to document those changes by specifying the version number and date and by whom the change is carried out.This minimizes version conflicts and maintains consistency. The project manager places the updated versions of source code units in version baseline directory called subversion repository courtesy of Google. The team members can access the directory through the http://code.google.com/p/neverendingstory/

Quality Assurance

To ensure highest quality assurance of the project, documentation as well as testing will be carried through out the development process. The software units developed by each member will be tested using test cases specified in test plan. The project manager validates by reviewing the corresponding documentation. Then the team performs tests on integrated unit to ensure that it meets the requirements specification.

Risk Management

The major risk involved in the project is failing to deliver the acceptable content within the schedule. Team members will ensure to foresee the risk and abide by the planned schedule. Meeting requirement specification is another issue and team members will overcome this hurdle by reviewing the corresponding documents of the design in each meeting .Unsuccessful design implementation is subdued by constant monitoring and carrying out the modifications after each phase.

Table of Work Packages, Time Estimates, and Assignments

Note: This information will be updated monthly

PERT Chart

Technical Progress Metrics

The technical progress is ensured by keeping track of changed number of requirements in the requirements phase. The actual vs. planned duration with respect to schedule and the type of modifications in the source code is reviewed in each meeting.

Plan for tracking, control, and reporting of progress

Each team member will be responsible to update the log time, the status of documents and the issues weekly. The team will review the website and discuss the logs, technical progress, risks and take corrective measures if necessary. The project manager will be responsible to issue the updated management report weekly.

Template created by G. Walton (GWalton@mail.ucf.edu) on Aug 30, 1999 and last updated Aug 15, 2000

This page last modified by Anusha kotha (anushakotha@gmail.com) on September 25, 2008.