CSE 403, Winter 2010

Project

Turn in a project phase

Specifications:	Overall Project Spec Phase 1: Software Requirements Specification (SRS) and UI Prototype (due Fri Jan 22, 11:59pm; UI prototype due Mon Jan 25 at start of lecture) Phase 2: Software Design Specification (SDS) (due Fri Feb 5, 11:59pm) UPDATE: As an alternative, if you want to turn in one (1) UML state diagram in place of one of your sequence diagrams, this is okay. The state diagram should follow proper state diagram syntax as described in Fowler, Chapter 10. Your diagram should include: a starting pseudo-state; at least 3-4 other meaningful states, properly labeled; transitions between those states as appropriate, properly labeled; and a final state, properly labeled, as appropriate. Phase 3: Zero Feature Release (ZFR) (due Mon Feb 8, 11:59pm) CLARIFICATION: Part of completing your ZFR is creating your database or other data source. Therefore, your ZFR product must in some way connect to this source of data, fetch at least one piece of data from it, and display the data in some way on the screen or web page. If your data source is plain files, your product should open and display some content from at least one file. Phase 4: Testing Procedure Specification (TPS) (due Fri Feb 26, 11:59pm) Phase 5: Initial Code Implementation (Beta) (due Mon Mar 1, 11:59pm) Phase 6: Feature-Complete Implementation (V1) (TENTATIVE; subject to change) (due Sat Mar 13, 11:59pm) Phase 7: Testing Resources (TEST) (TENTATIVE; subject to change) (due Sat Mar 13, 11:59pm) Phase 8: Updated Specs (SRS2/SDS2) (TENTATIVE; subject to change) (due Sun Mar 14, 11:59pm)

Specifications:

Overall Project Spec
Phase 1: Software Requirements Specification (SRS) and UI Prototype
(due Fri Jan 22, 11:59pm; UI prototype due Mon Jan 25 at start of lecture)
Phase 2: Software Design Specification (SDS)
(due Fri Feb 5, 11:59pm)
- UPDATE: As an alternative, if you want to turn in one (1) UML state diagram in place of one of your sequence diagrams, this is okay. The state diagram should follow proper state diagram syntax as described in Fowler, Chapter 10. Your diagram should include: a starting pseudo-state; at least 3-4 other meaningful states, properly labeled; transitions between those states as appropriate, properly labeled; and a final state, properly labeled, as appropriate.
Phase 3: Zero Feature Release (ZFR)
(due Mon Feb 8, 11:59pm)
- CLARIFICATION: Part of completing your ZFR is creating your database or other data source. Therefore, your ZFR product must in some way connect to this source of data, fetch at least one piece of data from it, and display the data in some way on the screen or web page. If your data source is plain files, your product should open and display some content from at least one file.
Phase 4: Testing Procedure Specification (TPS)
(due Fri Feb 26, 11:59pm)
Phase 5: Initial Code Implementation (Beta)
(due Mon Mar 1, 11:59pm)
Phase 6: Feature-Complete Implementation (V1) (TENTATIVE; subject to change)
(due Sat Mar 13, 11:59pm)
Phase 7: Testing Resources (TEST) (TENTATIVE; subject to change)
(due Sat Mar 13, 11:59pm)
Phase 8: Updated Specs (SRS2/SDS2) (TENTATIVE; subject to change)
(due Sun Mar 14, 11:59pm)

CSE 403: Software Engineering, Winter 2010

Project

Turn in a project phase