Secure House System IT09/2A

Members:

1. Melvin
2. Lionel
3. Jenn Yueh
4. Hong Wee

Introduction

There are commercial softwares in the market which allows users to design security systems for buildings. However most of these softwares are designed for building security design professionals and hence they are expensive and sophisticated in its usage although it provides a lot of features.

Our project targets the amateur users market segment to be our market niche. The intended software is designed to be practical and easy to use. It is also priced to be affordable to these users. As a result, only the basic security design funtionalities are incorporated into the software. We do however incorporated some functions which other software does not have.

Local fire protection requirements is not found in other available software. We have incorporated the basic local fire protection requirements which we think would be relevant to a amateur user. For example, the fire protection requirements are limited to small residential buildings (as opposed to multi-storey highrise buildings whose security system would usually be done by professionals) and small industrial buildngs such as a small warehouse which may be owned by the amateur user. The inclusion of the small industrial building would illustrate the sprinkler fire protection system.

Issues encountered

Our team faces some obstacles in the course of the project. The main obstacles is that none of the team members works full-time as programmers. Hence we are slower in our progress as we spent much time researching on how to do certain functions or features.

The other obstacles we encountered is that one particular team member has a heavy work commitment with many work deadlines to meet. Further he need to do travelling.

Project diary

Week 1: 08-May-2009 to 14-May-2009

1. Selected project.
2. Got into project group.
3. Attended first lecture.
4. First meeting with supervisor Mr Ee.
5. Election of project manager.
6. Research on project.

Week 2: 15-May-2009 to 21-May-2009

1. Did research on project.
2. Decided on scope of project.
3. Preparing Project Proposal document.

Week 3: 22-May-2009 to 28-May-2009

1. Preparing Project Proposal document.
2. Submitted Project Proposal.

Week 4: 29-May-2009 to 04-Jun-2009

1. Preparing Requirement Specifications document.

Week 5: 05-Jun-2009 to 11-Jun-2009

1. Submitted Requirement Specifications document.
2. Preparing for exam.

Week 6: 12-Jun-2009 to 18-Jun-2009

1. Preparing for exam.
2. Exam. 3. Preparing Design document.

Week 7: 19-Jun-2009 to 25-Jun-2009

1. Preparing Design document.

Week 8: 26-Jun-2009 to 02-Jul-2009

1. Submitted Design document.
2. Discussion and research on coding of software.

Week 9: 03-Jul-2009 to 09-Jul-2009

1. Started software coding.
2. Coding of blank floor plan template.
3. Coding of drawing of floor plan funtionality.

Week 10: 10-Jul-2009 to 16-Jul-2009

1. Coding of placing of security device functionality.
2. Coding of ability to load saved floor plan fucntionality.

Week 11: 17-Jul-2009 to 23-Jul-2009

1. Discussion of feedback received from assessor.
2. Reviewed Project Proposal and Requirement Specification document.
3. Finalise on amendments required.

Week 12: 24-Jul-2009 to 30-Jul-2009

1. Continued coding and started testing on the codes coded.
2. Research and coding of camera coverage area.

Week 13: 31-Jul-2009 to 06-Aug-2009

1. Encountered problem with coding of camera coverage area.
2. Discussion on issue encountered. Decided to use a different programming language.

Week 14: 07-Aug-2009 to 13-Aug-2009

08-Aug-2009:
Meeting with Mr Ee. The team reported to Mr Ee that progress is behind schedule due to the issue encountered. Had started re-coding using another language instead.

09-Aug-2009 onwards:
Working on the codes.

Week 15: 14-Aug-2009 to 20-Aug-2009

Working on the codes. Bugs were encountered and tried to fix them.

Week 16: 21-Aug-2009 to 27-Aug-2009

Working on the codes. Bugs were encountered and tried to fix them.

Week 17: 28-Aug-2009 to 03-Sep-2009

29-Aug-2009:
Meeting with Mr Ee. The team showed Mr Ee what had been done. However there are still bugs to be fixed

Week 18: 04-Sep-2009 to 10-Sep-2009

1. De-bugging.
2. Start preparing Technical Manual.
3. Start preparing User Guide Manual.

Week 19: 11-Sep-2009 to 17-Sep-2009

14-Sep-2009:
Meeting with Mr Ee. The team reported to Mr Ee that the bugs have not been resolved. Mr Ee highlighted that the time is now very short. The team should expedite the progress. Mr Ee suggests to meet again on 22-Sep-09. Hopefully the bugs are resolved.

Mr Ee highlighted the rest of the work that need to be done.

15-Sep-2009 onwards:
1. Working on the bugs.
2. Preparing Technical Manual.
3. Preparing User Guide Manual.
4. Start recording demo video.

Week 20: 18-Sep-2009 to 24-Sep-2009

22-Sep-2009:
Meeting with Mr Ee. Two team members were not able to attend the meeting due to fixing bugs. Reported to Mr Ee that there are still a couple of bugs to be fixed. Need a day or two more.

Mr. Ee advises on how to do the packaging of the software and reminded the team what are the deliverables required.

23-Sep-2009:
The team meets up discuss on the packaging of the software and work is distributed. The team is also being updated on the progress of the bug fix.

25-Sep-2009:
The team meets up to finalise on the project to be presented on the next day 26-Sep-2009.