Final report Planning

時間表:

1. Implementation: 13-5-2008
2. User guide and installation guide: 15-5-2008
3. The requirements: 17-5-2008
4. Results and conclusions:19-5-2008
5. Documentation for detailed design:20-5-2008
6. Documentation for problem analysis: 23-5-2008

Final Report是重質多於重量的

Implementation: Discuss on 10-5-2008

1. 記錄自己做過甚麼，可以參考我的工作記錄
   
2. Testing
   1. Black Box testing - Requirements Verification
      
3. Changes to design(Provide reason) - Requirements Verification

Results and conclusions: Discuss on 16-5-2008

1. Summary
   
2. 全方位檢討(驗證)
   1. 由original problem formulation(簡潔陳述) was correct
      1. difficulties encountered
      2. delays/changes in project schedule
   2. 到how well the solution meets the specification
      1. limitations of the proposed system
   3. subsection suggesting further developments to be undertaken

User guide and installation guide: Discuss on 12-5-2008

1. User Guide
   1. 寫自己的function
2. Installation guide
   1. 把Software folder複製到儲存位置(USB記憶體也可以!!)。
   2. 按JAR file。
   3. 完成。

Documentation for detailed design

1. 考慮多個可行方案，然後選擇最好的。
2. 要把設計全部列出，不可以因為Project沒有做到而刪去。
   
3. software/hardware architectural design (system design)
   1. Software architectural design
      1. 可行方案
         1. Client-Server
         2. Database-centric architecture
         3. Structured Systems Analysis and Design Method (SSADM)
      2. 正常情況下我們的程式只會在一部電腦上使用。
         
      3. 員工可以上網看時間表的話程式會在多部電腦上使用(Client: Staff, Server: Software)
   2. hardware architectural design
      1. 可行方案
         1. PC
         2. Pocket PC
      2. 在普通PC上運作，沒有特別的設計
         
4. data design
   1. Project資料會以Object Oriented File儲存: 檔案裡全是Objects。
      
5. user interface design.

The requirements

1. analysed the problem
   1. 找出真正要解決的問題
2. for evidence that you have investigated(調查) commercially available solutions
   1. 參考過市面上的軟體
   2. 決定最終的解決方案
      1. Scope of the proposed system
      2. description of functions provided
      3. data processed by the system
         1. User可以輸入甚麼，例如Task的資料
      4. other non-functional requirements
         1. 免安裝的特性應在此說明。

Documentation for problem analysis

1. approach to problem solving
2. choice of methods
3. tools and techniques
4. the quality of design
   1. data model
      1. class diagram
   2. functional model
      1. use cases
   3. dynamic model
      1. state transition diagram
      2. sequence diagram
   4. data dictionary

Referencess:

1. http://en.wikipedia.org/wiki/Software_architecture
2. http://en.wikipedia.org/wiki/Hardware_architecture