K-Team Minutes

SQAP Review Meeting

3rd August 1999

11:00 AM - 2:00 PM

Attendees: Joanna Araminta, Victor Leung, Joel Brakey, Michael Hart, Dean Cortinovis, Long Tang
Apologies: None
Secretary: Joanna Araminta

This Meeting

  1. Be consistent with the team name, it should be K-Team.

  2. Section 1.1 - OK

  3. Section 1.2
    • Change Mac OS 7.6.1 to Mac OS 8
    • Change UNIX (Solaris) to Solaris 7
    • Might not need to mention vi, as everyone is using different text editor. The most important thing is that the final product looks like as set out in the template.
    • Change javac to Java Development Kit 1.2
    • Add MS Project 98 - for project planning.
    • Add Hotline 1.5 - for backups.

  4. Section 1.3 - Fine, however get rid of "(Project Manager)" next to Jo.

  5. Section 2
    • Addition to reference documents:
      • Jo's networking book
      • Mahjong Mueseum website
    • Addition to documents produced - user manuals for both the client and server programs.

  6. Section 3 - Jo to check on consistency and spell check:

  7. Section 3.1.1:
    • Get rid of "Allocate a meeting secretary ........" and dump this into Chairperson
    • Add "Ensure that each team member submit a progress report after each submission"
    • Make sure that tasks are followed.
    • Re-order the list

  8. Section 3.1.2:
    • Delete "this will involve......" (dot point 3)

  9. Section 3.1.3:
    • Delete "Assisting the Project Manager ....."
    • Change dot point 2 -> Ensure that minutes of every meeting are put into the repository within the time frame mention in Section 5, after the meeting takes place.

  10. Section 3.1.4:
    • Delete dot point 3 and 5 -> change it to "Maintain minutes from each client meeting"
    • Add "Organise a 'requirements and acceptance testing' meeting with Client"
    • Add "Pass on requests for resources from team member"

  11. Section 3.1.5:
    • Add "Maintain READMEs"
    • Remove "Makefile in dot point 1
    • Remove "Maintain project's documentation"
    • Remove "Handle the duties of..........."

  12. Section 3.1.6:
    • Dot point 2 -> elaborate on technical details (i.e Java netwroking, swing .....etc)
    • tutorials: JavaDoc, Networking, Swing, etc..
    • Long - AI researcher

  13. Section 3.1.7:
    • Section 3.1.7.1:
      • Reword "before each suubmission" -> "before submission"
      • Add "Ensure that the team has been following all the processes described in the SQAP"
    • Section 3.1.7.2:
      • Get rid of "Act as an internal reviewer"
      • Add "Ensure that documents conform to all standards layout in the SQAP"
      • Add"Ensure each section of a document is completed"

  14. Section 3.1.8:
    • Get rid "in the doc/...." -> dot point 2

  15. Section 3.1.9:
    • Change dot pint 1 to "Perform weekly backups and archive these"
    • Add: "Ensure that external auditors have access to backup log messages in the repository"

  16. Section 3.1.10:
    • Add "Maintain RMMM Plan"
    • Add "Enforce the mitigation steps described in the RMMM Plan, if such risks occur"

  17. Section 3.1.11:
    • Internal reviewers -> all team members

  18. Section 3.1.12:
    • Add "Maintain the meeting's agenda, and distribute it to the other team member, via e-mail, 24 hours prior to the meeting"
    • Remove "Assist the secretary ....."
    • Reword last dot point -> "Ensure all agenda items are covered"
    • Change "Ensure that minutes ....." -> "Elect a meeting secretary"

  19. Section 3.1.13:
    • Remove "Distribute agenda ......"
    • Add "Write up the agenda of the meeting on the board before the meeting starts"

  20. Section 3.1.14 - OK

  21. Section 3.2:
    • Make sure that each events are numbered
    • elaborate on the different GANTT charts produced, eg SADD chart, TP chart ... etc

  22. Section 4:
    • Need reader's background for every document
    • Section 4.1.2 - Reword!
    • Section 4.2 - Need process for SADD
    • Section 4.4:
      • Need to describe user interactions in game manual.
      • Divide to Client and Server manual.
    • Section 4.5:
      • Remove dnbook/
      • Remove "Any relevant......."

  23. Section 5:
    • Section 5.1 - need rewording badly
    • Section 5.2 - add "UNIX newlines should be used"
    • Section 5.3 - OK but need coding procedure -> when a compiler tells you to do something, for the program to compile, add comments about it in the code for traceability and design decision.
    • Section 5.4 - OK, might need a bit rewording

Next Meeting

    Date: 10 August 1999

    Time: 1 p.m.

    Venue: SEECS basement

Client Minutes      General Minutes       Review Minutes      Supervisor Minutes