<Your Team Name>

SUBMITTED CHANGE REQUESTS

The change manager posts all formal change requests that have been submitted.  Use the format as in the examples below.  Number each new request sequentially.  Until the Change Control Board (CCB) has discussed the request, the "CCB DECISION" field should indicate "PENDING".  Once the CCB has discussed the request, the decision field is updated with the result.


WEEK 1

Change Request 1:

Date: Thu, 15 Apr 1999:

user : Chris Brooks

userEmail: cjbrooks@falcon.csc.calpoly.edu

product : UI Prototype / Chris

adminEmail: aqnguyen@falcon.csc.calpoly.edu

Changes: I changed the prototype to add a help link from the

Welcome page. I guess we need to let the designers know about that?

Rationale: User's need a link to a page of instructions

if they need assistance logging in. Yahoo does this. We should too.

Impacts : Will require another HTML page.

Probably about 2 hours of development time.

CCB'S DECISION: ACCEPTED

This is part of the User Manual that Chris is writing.

Date: Fri, 23 Apr 1999


Change Request 2:

Date: Sun, 18 Apr 1999 21:10:48 -0700 (PDT)

From: edenson@falcon.csc.calpoly.edu

Subject: Change Request

User : Ed Denson

UserEmail : edenson@falcon.csc.calpoly.edu

Product : Software Architecture / John Z.

AdminEmail : jzolezzi@falcon.csc.calpoly.edu

Changes : we need to change all the CTimes to type tm and have both a

start and end time. Rashad and I found a time library. We

just have to #include <time.h>. It is located on the falcon

server. you can man ctime.

Rationale : It is the only Time library we found. And no others have

been proposed.

Impacts : Wide spread, but it is used by most calendar functions and

is needed

CCB'S DECISION: ACCEPTED

All developers must implement the above changes.

Date: Fri, 23 Apr 1999


Change Request 3:

Date: Tue, 20 Apr 1999 21:54:54 -0700 (PDT)

From: jdalbey@falcon.csc.calpoly.edu

Subject: Change Request

User : John Dalbey

UserEmail : jdalbey@falcon.csc.calpoly.edu

Product : Detailed Design Document / John Z.

AdminEmail : jzolezzi@falcon.csc.calpoly.edu

Changes : The buddy list box on the Invite section of AddEvent

doesn't work. I tried it in the prototype. It will

only select a single buddy, or a contiguous block

of buddies. You can't select multiple discrete

buddies. I don't know how to fix this with HTML forms.

I guess this is really a 'Defect" not a change,

but the defect report procedure isn't up yet.

Rationale :

Impacts : Changes to prototype and detailed design.

CCB'S DECISION: NOT APPLICABLE

Reason: This is a Defect, not a Change. This defect will be reported

to the Quality Assurance Lead to be entered in the defect tracking system

when it becomes available.

Date: Fri, 23 Apr 1999


WEEK 2

Change Request 4:

Date: Thu, 6 May 1999 12:38:46 -0700 (PDT)

From: jdalbey@falcon.csc.calpoly.edu

Subject: Change Request

User : John Dalbey

UserEmail : jdalbeyfalcon.csc.calpoly.edu

Product : Requirements Specification / Chris

AdminEmail : cjbrooks@falcon.csc.calpoly.edu

Changes : Any events scheduled for times outside ofthe range being displayed by DayView do not appear. It would be desirable if a small message appeared at the bottom of Day View informing the user of the existence of other events that are outside the time range being displayed. Something like: "3 events not displayed (after 5pm)."

Rationale : Improved usability. Informs the user of events that are not displayed in Day View.

Impacts : Modification to Day View module. Probably less than 2 hrs developer time.

CCB'S DECISION: ACCEPTED

This request will be implemented in the third release.

Date: Fri, 07 May 1999