Thursday 31 January 2008

Tutorial 2 - Task 1

Identify the main stakeholders for this project

  • users
  • trainers
  • IT support
  • facilities management
  • client management
  • catering services

Fourth Board Meeting on 31 Jan 2008

Meeting time: 20 00 hrs to 22 00 hrs
Attendance: Full

Business consultants met with individual stakeholders on Tuesday, 29 Feb 2008, with their proposed usage scenarios. These scenarios have been reviewed and approved by the stakeholders.

User Interface is still in development phase and is scheduled to be completed on Sunday, 3 Feb 2008.

Lead programmer and database lead had their first discussion on the data model and description.

Tuesday 29 January 2008

Third Board Meeting on 28 Jan 2008

Meeting time: 19 00 hrs to 22 00 hrs

Presented our proposed use case scenarios to individual stakeholders and received feedback from them.


Made changes to the use cases according to the stakeholders and will have our deliverables reviewed tentatively by tomorrow, 29 Jan 2008.

User Interface is still in development with constructive internal feedbacks.

Saturday 26 January 2008

Second Board Meeting on 26 Jan 2008

Meeting time: 10 00 hrs to 17 00 hrs

We finalized our Software Project Plan based on the RSPA template and started on the Software Requirement Specification.

We came up with use cases for each of the following actors:
  • Administrator
  • Ticketing Officer
  • Registered User
  • Normal User
We also started designing the User Interface (UI) using Microsoft Visual Basic.Net

Thursday 24 January 2008

First Board Meeting on 24 Jan 2008

Meeting time: 20 00 hrs to 22 00 hrs

We've decided on the RSPA template based on the following comparison. We will still go through the other templates and look out for their good points to integrate into our documentations.

Templates Comparison
  • DSDM.com
    • Too many documents to maintain, making it messy
    • Not neatly organized
  • Rspa.com
    • No table of content
    • Guidelines too brief
    • Suitable for small scale projects
  • UPEDU
    • Less documents to maintain
    • Suitable for large projects and easy to maintainability
    • Contains revision history, allowing control of change management
    • Template well explained

Work Discussion

  • Discussion on Software Development plan
  • Task allocation usage scenario
    • Administrator: Morris
    • Ticketing Office: Selamat
    • Registered user: Rahim & Shani
    • Normal user: Natalie