Project Plan

Team 2

Jonathan Knez

Table of Contents

Personnel

(L) Refers to team leader.

 

Name

Roles

Email Address

Jeremy Barton

Configuration Manager (L)

Implementer / Programmer

Tester

Jeremy.S.Barton@rose-hulman.edu

JP Gonzalez

Requirements Analyst

User Interface / Front-End

gonzaljp@rose-hulman.edu

Stephen Gregory

Designer (L)

Requirements Analyst

Stephen.A.Gregory@rose-hulman.edu

Jonathan Knez

Project Manager (L)

Group webpage webmaster (L)

User Interface / Front-End (L)

User documentation specialist

Jonathan.G.Knez@rose-hulman.edu

Eric Lewandowski

Implementer / Programmer (L)

Requirements Analyst (L)

Designer

Eric.D.Lewandowski@rose-hulman.edu

Joseph Richey

Tester (L)

Designer

Implementer / Programmer

Joseph.E.Richey@rose-hulman.edu

Todd Windler

User documentation specialist (L)

User Interface / Front-End

Todd.R.Windler@rose-hulman.edu

Group email

Group email

cs414-group2@cs.rose-hulman.edu

 

Work Packages

  • The table cell should be green for on schedule, yellow for possibly going off schedule, red for off schedule, blue for completed, pink for waiting to begin.
  • Work package tables must be updated weekly, and the updated tables should be part of the project manager's weekly report. 

Work Package ID

Resource Names

Role

Task

Start

Finish

% Work Completed

1

Todd

Minute Taker @

1st Client Meeting

Client Meeting Summary

12/12/2002

12/14/2002

100%

2

Jonathan

Group webpage webmaster

Project Web Page

  • Keep up-to-date

12/12/2002

?

99%

3

Jonathan

Project Manager

Project Plan

12/16/2002

?

99%

4

Steve

Eric

JP

Requirements Analysis Team

Feasibility Report

  • Discuss, and make a rough draft
  • Write it

01/06/2003

01/09/2003

100%

5

Jeremy

Configuration Manager

Configuration Management Plan

  • Write it

01/06/2003

01/13/2003

100%

6

Jonathan Todd

JP

User Interface / Front-End Team

Webpage User-Interface Prototype

  • RHAP webpage
  • Perform Searches
  • Display Search Results

01/06/2003

02/03/2003

100%

7

Jonathan

JP

User Interface / Front-End Team

Use Cases

  • Discuss, and make a rough draft
  • Write it
  • Review with Don Baggert or Mark Ardis

01/20/2003

02/03/2003

100%

8

Steve

Eric

JP

Requirements Analysis Team

Requirements Specification

  • Discuss, and make a rough draft
  • Write it
  • Review with Don Baggert or Mark Ardis

01/06/2003

01/31/2003

100%

9

Steve

Eric

Joseph

Design Team

Design Document

01/20/2003

02/08/2003

100%

10

Jeremy

Joseph

Test Team

Test Plan

03/24/2003

04/07/2003

0%

11

JP

Jonathan

Steve

Joey

Eric

Jeremy

Todd

Presentation

Create Presentation

  • Decide who will be the speakers
  • Create an outline
  • Create basic slides
  • Improve slides so they are more eye pleasing

 

02/03/2003

02/12/2003

100%

12

Eric

Joey

Jeremy

Back-end

Set up a web server

  • Be able to receive parameters from prototype web page
  • Generate Query to be executed on Database
  • Execute Query
  • Format Results
  • Submit formatted results to webpage prototype

 

03/24/2003

04/07/2003

20%

13

Jonathan

Todd

JP

Front-end

Setup up a functioning front end

  • Use the prototype as the template.
  • Log in using script.
  • Receive and display the results obtained from back-end

03/24/2003

04/07/2003

0%

14

Jonathan

User Documentation

Write documentation that will help the client use the system. This will need to be in HTML format and be linked to from the Archives web page

04/07/2003

?

0%

15

Stephen

Technical Documentation

Write the software manual that describes how the software works. This manual would be used for code maintenance.

04/07/2003

?

0%

16

All

Test Reports

Use the test plan to generate reports of software performance

04/07/2003

?

0%

17

All

End of project document

?

?

?

0%

18

All

Project presentation #2

Create Presentation

  • Eric, Todd, Jeremy, and Joey will be speaking
  • Create an outline
  • Create basic slides
  • Improve slides so they are more eye pleasing

 

?

?

0%

19

All

Inspection Reports

Code review reports

?

?

0%

Project Schedule Update

  • The table below must be updated weekly.
  • Week Starting - Monday's date for the week

 

Week Starting

On/Off Schedule

Reason Off Schedule

Corrective Actions To Take

12/09/2002

ON

-.-

-.-

12/16/2002

ON

-.-

-.-

01/06/2003

ON

-.-

-.-

01/13/2003

ON

-.-.

-.-

01/23/2003

ON

-.-

-.-

01/27/2003

ON

-.-

-.-

02/03/2003

ON

-.-.

-.-

02/10/2003

ON

-.-

-.-

3/17/2003

ON

-.-

-.-

To Do List

Items

Modify current search script to handle more than one parameter

Include Frames on team webpage

Set up a web server

To-do list is now listed separately on the webpage and updated there

Revision History

Date

Name

Revision

12/15/2002 

JP

Initial Version

12/21/2002

JP

Create Work Packages

01/09/2003

JP

 Modified Team Roles

01/19/2003

 JP

Added items to “Thing To Do List”

Re-did Work Packages

01/31/2003

JP

Re-assigned Team Leaders, Modified Dead Lines, Updated Project Schedule, Update To Do List

02/16/2003

JP

Update Project Schedule. Update To Do List. Created new work package.

03/17/2003

Jonathan

Modified JP’s and Jonathan’s roles.

Recorded that we are on track.

03/27/2003

Jonathan

Added items 14-19. Moved the to-do list to the web page for faster access.