Work done in week 11

Major work accomplished is the finalization of our project preliminary documentations.

I participated both documentations.

The documents have already been posted on our website. They can be accessed by clicking the "Documentation" link in the navigation bar.

Week 12 Group Meeting

Jobs done in Week 11

One major task accomplished in week 11 is the releasing of our Preliminary Documentations, including:

Allocated web space (ZIM) has been directed to our project web stie.

User Manual (Done by Zhiyun YU (Drake) & Runlai Huang (Henry)), 14pages

Technical Manual (Done by Jeff, Drake and Allen), 44 pages

The user manual covers the full (designed) functionalities and details of the Client model, from registering to retrieving reports.

The technical manual covers more in details of the design, implementations, flow control, UML diagrams, etc. Basically the idea of realizing of Clients and Servers are all there.

Job Allocations

There're no futher major tasks to be done in this session, so the tasks for following weeks would be to review the current preliminary documents.

There're sure much to be revised and refined in our current documents. And we need to be fully familiarized with those concepts, to better doing the coding in next session.

In addition, our web page needs to be updated, to have a better look, with a clear and easy navigation.

Timeline

Timeline for this week is:

To finalize website by the end of week 13.

And in addition, the last day for exam of our group is 21st June. We will continue our project during the session break, and the first meeting in the break is expected to be held by the end of June.

Week 11 Group Meeting

Conclusion of week 10

As we started working on the documentations, at the beginning of this meeting I checked the jobs done by our group members, and it was not satisfying. I believe it was due to the lack of experiences. The best we have done so far is the User Manual, as it includes less stuff than the technical manual. The main contents are finished, only additional feature like Appendix is to be added on.

Job Allocations

And about the technial part, we decided to do it all over again. We discussed about the previous works listed on e-learning, and we think they were good examples. So we decide to divide our technical documentation into eight parts:

SQL/DATABASE

UI

UML Diagram

Flow Control

Code layout

Libraries

Basic Class Description

Test Plans

So the job allocations for this week is that:

Henry takes care of the User Manual, which is almost to be done.

The other two and I will take the Technical Documentation.

Jeff takes the SQL/DATABASE, UI, Flow Control parts.

Allen and I take the rest parts.

Timeline

As the documentations are due this week, all works are to be submitted to me by Friday.

Final revisions will be made and discussed before it is formally submitted.

Work done in week 10

In week 10 the main work done is the finalization of our project proposal. Basically it will be a Client-Server model. Clients and Server send and receive data to generate reports and updates.

In additional, we started the documentation work but it was progressing slowly. I took the Client part in the technical documentation, but it was later to be found that it's more in a style of a User Manual. So I gave Henry the structure of what I wrote as a reference for him to finalize the User Manual, and technical documentation jobs are going to be started all over again.

Week 10 Group Meeting

In the group meeting of week 10 we discussed the details of our whole project. As the preliminary diary is due next week, we need to have all things and details settled down.

Also, the UML diagrams have also been postponed due to the heavy work in designs.

Job allocation for this week is as follows:

Project proposal is to be finalized by this Friday (12/05/11)

After that we need to get started on the User Manual and the Technical Documentaion, each part is taken by 2 people.

The User Manual aims to tell the users what they need to operate the software, and how to use it, while the Technical Documentation aims to give specific details of every aspects of this software.

We hope to release an alpha version of the documentations by next Tuesday.