IS480 Team wiki: 2009T1 Optimus
by Team Optimus
Contents
- 1 Project Overview
- 2 Project Schedule
- 3 The Terrapins
- 4 Weekly Progress Summary
- 4.1 Week 1 (20 April to 26 April)
- 4.2 Week 2 (27 April to 03 May)
- 4.3 Week 3 (04 May to 10 May)
- 4.4 Week 4 (11 May to 17 May)
- 4.5 Week 5 (18 May to 24 May)
- 4.6 Week 6 (25 May to 31 May)
- 4.7 Week 7 (01 June to 07 June)
- 4.8 Week 8 (08 June to 14 June)
- 4.9 Week 9 (15 June to 21 June)
- 4.10 Week 10 (22 June to 28 June)
- 4.11 Week 11 (29 June to 05 July)
- 4.12 Week 12 (06 July to 12 July)
- 4.13 Week 13 (13 July to 19 July)
- 4.14 Week 14 (20 July to 26 July)
- 4.15 Week 15 (27 July to 02 August)
- 4.16 Week 16 (03 August to 09 August)
- 4.17 Week 17 (10 August to 16 August)
- 4.18 Week 18 (17 August to 23 August)
- 4.19 Week 19 (24 August to 30 August)
- 4.20 Week 20 (31 August to 06 September)
Project Overview
Software Engineering is a compulsory core module that every responsible School of Information Systems student must undertake. This course equips students with techniques, methodology and hands-on experiences to better manage software projects – from requirements gathering, project planning, project tracking, software application developing and user acceptance testing.
Every successful delivery of the Software Engineering course to the students depends on the hard work and dedication put in by the instructors to ensure students’ get the best learning experience when they graduate from this course.
However, more initiatives are introduced to the course every term, making the next term better than the one before. The instructors are usually bogged down by manual administrative tasks that impede their productivity, hence compromise instructors from providing other additional value-added teaching materials to the students.
Project Description
Our project is aimed to relieve instructors from their heavy administrative manual tasks that are required from the Software Engineering course. A web-based system will be developed to give instructors access to various features that will allow them to get their administrative job done as efficiently and effectively as possible.
In addition, our project would also include various tools necessary for the Software Engineering course such as Bug Tracking, Sub versioning Tools.
Motivation
The opportunity to be involved in such a project is indeed attractive. Our team believes that by helping to develop, test and deploy such a solution, we can gain considerable experience – both in terms of software project management skills and engagement of our clients.
Additionally, on a personal level, our skill sets are tailored towards a project such as this one, as will be elaborated later on in this proposal. Having identified significant continuity in this project, we are determined to deliver this solution effectively.
Objectives
At the end of our project, we aimed to alleviate the teaching staffs of the Software Engineering course from their manual administrative tasks with our web-based application solution. This enables them to focus their efforts towards delivering value-added teaching initiatives to future Software Engineering students.
Features of Project Terrapin
- Timetabling of Student Schedules Module
- Student Projects/Assignments Preparation Module for Instructors
- Student Group Project Reporting Module
- Group Project Student Allocation Module
- Peer Evaluation Management Module
- Create/Upload Code bases to Code Checking System Module
- Tools for Software Engineering; Bug Tracker, Subversioning
- Project Collaboration Tools; WiKi, Discussion Boards
- SEE FULL FEATURE LIST [1]
Project Schedule
Timeline
Project Milestone
The Terrapins
Team Members
- Irwan SUNJAYA
- Jayson ANG
- Jeremy GAN
- Richard YAU
- ZHOU Zhe
- SEE ROLES & RESPONSIBILITIES [8]
Supervisor
- Professor Benjamin GAN [9]
Client
Weekly Progress Summary
Week 1 (20 April to 26 April)
What was done / discussed
- Went through specifications and came up with a list of questions to be clarified with sponsors
- Defined roles and responsibilities, as well as assigned primary and secondary ICs
Download Minutes for full details;
- (Internal) Meeting Minutes - 20 April 2009: [12]
- (Client) Meeting Minutes - 23 April 2009: [13]
- (Supervisor) Meeting Minutes - 23 April 2009: [14]
Week 2 (27 April to 03 May)
Week 3 (04 May to 10 May)
Week 4 (11 May to 17 May)
- (Internal) Meeting Minutes - 13 May 2009: [19]
- (Supervisor) Meeting Minutes - 14 May 2009: [20]
- (Client) Meeting Minutes - 14 May 2009: [21]
Week 5 (18 May to 24 May)
- (Client-Supervisor) Meeting Minutes - 21 May 2009: [22]
Week 6 (25 May to 31 May)
Week 7 (01 June to 07 June)
Week 8 (08 June to 14 June)
- (Client) Meeting Minutes - 10 June 2009: [27]
Week 9 (15 June to 21 June)
Week 10 (22 June to 28 June)
- (Client) Meeting Minutes - 26 June 2009: [30]
Week 11 (29 June to 05 July)
- (Client) Meeting Minutes - 30 June 2009: [31]
Week 12 (06 July to 12 July)
- (Supervisor) Meeting Minutes - 09 July 2009: [32]
Week 13 (13 July to 19 July)
Week 14 (20 July to 26 July)
Week 15 (27 July to 02 August)
Week 16 (03 August to 09 August)
Week 17 (10 August to 16 August)
- (Supervisor) Meeting Minutes - 13 August 2009: [37]
Week 18 (17 August to 23 August)
- (Supervisor) Meeting Minutes - 20 August 2009: [38]
Week 19 (24 August to 30 August)
- (Supervisor) Meeting Minutes - 20 August 2009: [39]