<Ostrich Software>

SUBMITTED CHANGE REQUESTS


WEEK 1

Change Request 1:

Date: Thu, 3 Apr 2008:

user : Clovas Hansen

userEmail: cehansen@calpoly.edu

product : Stage 0.1 release

Changes: Requirement specifying that the Format button must ensure compile and then format has been changed to disable the format button in the case that the file is not yet formatted.

Rationale: This was changed at the last minute before the Stage 0.1 release in order to sidestep a problem where compiling uncompilable code resulted in a crash of BlueJ. This change was authorized by the instructor.

Impacts : This change will allow the Stage 0.1 release to be reached relatively on time.

CCB'S DECISION: ACCEPTED

Change Request 2:

Date: Fri, 4 Apr 2008:

user : Tyler Charlesworth

userEmail: tcharles@calpoly.edu

product : Stage 0.1 release

Changes: Recompilation requested using Java 1.4 compatibility in order to allow the Stage 0.1 release to be tested.

Impacts : This change will allow the Stage 0.1 release to be tested.

CCB'S DECISION: ACCEPTED

WEEK 3

Change Request 3:

Date: Tues, 15 Apr 2008:

user : Clovas Hansen

userEmail: cehansen@calpoly.edu

product : Stage 1 release

Changes: Modify the SRS to reflect the functional requirements added for stage 1.

Rationale: The new requirements need to be in the project SRS in order to satisfy the Functional Traceability Requirements for this project.

Impacts : This allows for requirements traceability to be applied to the new functional requirements within other project documentation.

CCB'S DECISION: ACCEPTED

Change Request 4:

Date: Wed, 16 Apr 2008:

user : Clovas Hansen

userEmail: cehansen@calpoly.edu

product : Stage 1 release

Changes: Change code to recompile after formatting.

Rationale: This is an added function for Stage 1.

Impacts : This change is necessary to have code generated by Clovas Hansen for the Stage 1 release.

CCB'S DECISION: ACCEPTED

Change Request 5:

Date: Wed, 16 Apr 2008:

user : Brian Blonski

userEmail: bblonski@calpoly.edu

product : Stage 1 release

Changes: Add class structure for Undo code.

Rationale: This is an added function for Stage 1.

Impacts : This change is necessary to have code generated by Brian Blonski for the Stage 1 release. While this does not add a visible feature to Stage 1 it is intended to fix a known issue that multiple file formatting would have with the current Undo feature.

CCB'S DECISION: ACCEPTED

Change Request 6:

Date: Wed, 16 Apr 2008:

user : Tyler Charlesworth

userEmail: tcharles@calpoly.edu

product : Stage 1 release

Changes: Change Jalopy code to show help information for preferences.

Rationale: This is an added function for Stage 1.

Impacts : This change is necessary to have code generated by Tyler Charlesworth for the Stage 1 release.

CCB'S DECISION: ACCEPTED

Change Request 7:

Date: Wed, 16 Apr 2008:

user : Aaron Waechter

userEmail: awaechte@calpoly.edu

product : Stage 1 release

Changes: Change Jalopy code to compile before formatting.

Rationale: This is an added function for Stage 1.

Impacts : This change is necessary to have code generated by Aaron Waechter for the Stage 1 release.

CCB'S DECISION: ACCEPTED

Change Request 8:

Date: Wed, 16 Apr 2008:

user : Michael McThrow

userEmail: mmcthrow@calpoly.edu

product : Stage 1 release

Changes: Change Jalopy code to use Brian's Undo class structure to maintain Undo data for use in the Undo command.

Rationale: This is an added function for Stage 1.

Impacts : This change is necessary to have code generated by Michael McThrow for the Stage 1 release. While this does not add a visible feature to Stage 1 it is intended to fix a known issue that multiple file formatting would have with the current Undo feature.

CCB'S DECISION: ACCEPTED

WEEK 4

Change Request 9:

Date: Tue, 22 Apr 2008:

user : Michael McThrow

userEmail: mmcthrow@calpoly.edu

product : Stage 1 release

Changes: Modify the User Manual to reflect the new features added for stage 1.

Rationale: The new functionality needs to be in the project User Manual in order to satisfy the consistency requirements for this project.

Impacts : This change is necessary for the project's documentation to remain consistent for the change to Stage 1.

CCB'S DECISION: ACCEPTED