Details about Autumn Bug Tracker

1. Requirement
     1.1 INPUT: As start point, there is no element input.
     1.2 OUTPUT: Requirement Doc.
     1.3 OBJECTIVE: Descript the business logic, and confirm the functions of the system.
     1.4 COMMENT: Due to unknow quantity of module, the schedule will be worked out after this phase.

2. UI Prototype
    2.1 INPUT: Requirement Doc.
    2.2 OUTPUT: UI built with C#.
    2.3 OBJECTIVE: Confirm the work flow, and reduce different or confused meanings.
    2.4 COMMENT: The prototype may be different with useable system.

3. Architecture
    3.1 INPUT: Requirement Doc
    3.2 OUTPUT
        a. Hardware Infrastructure: Doc
        b. Software Architecture: Doc
    3.3 OBJECT: Confirm hardware infrastructure and software architecture and their versions.

4. System Design
    4.1 INPUT: UI Prototype and Architecture doc.
    4.2 OUTPUT
        a. Demain Design: Visio Diagram (Class Diagram)
        b. DB Design: SQL Script
        c. Interface Design: Class Diagram (or other diagrams)
        d. Test Case: Doc
    4.3 OBJECTIVE: Confirm entity classes and boundary classes, provide all documents for coding.

5. Coding
    5.1 INPUT: System Design Doc
    5.2 OUTPUT: Useable and testable system, with expected format, such as exe, jar, war, etc.
    5.3 OBJECTIVE: Implement all business logic, according to system design documents.
    5.4 COMMENT: Unit Test should be hold on.

6. Test
    6.1 INPUT: Useable System, Test Case Document
    6.2 OUTPUT: Deployable System
    6.3 OBJECT: Find out defects as possible.
    6.4 COMMENT: Coding and Test may be alternant.

NOTICE:
    1. Schedule should be work out after Requirement Phase.
    2. The following should be Robust:
        a. Interface.
        b. framework.
        c. DB. Modifying fields is permitted, but Table Relationgship should not be modified frequently.