About This Journal

This journal will be used to keep a record of my decisions and progress as I work on my Third Year Project.

Since I’ve spent the last few weeks working, I’m going to write a couple of catch-up entries and then start writing weekly entries next Monday 19th October.

Progress Updates

For a variety of personal reasons work on the project slowed down a lot in the past few weeks. I’m happy to say work has now resumed =)

My Initial Report is in, and while it is missing risk analysis and ethical considerations, it is done. Here’s an excerpt:

Project Tasks

1.   Research
Several areas of the project still need to be researched before development can begin.

a.   Device Emulation (sensors and control unit)
b.   Data Persistence (weak references etc)
c.   Pin Signalling (alerts from devices etc)
d.   Threading
e.   User Interfaces (Micro Framework WPF)
f.    Heuristics and Data Mining Algorithms (Self Setting Alarms)
g.   Networking (Sensor Communications and Alerts)
h.   GSM Communications (Mobile Alerts)

2.   Prototyping
As research is progressing prototype programs will be created to test out individual features
and assess the viability of particular approaches to problems.

3.   Emulation
An emulation environment will be created to test the prototypes being developed in
combination with one another (sensors and control unit, for example).

4.   Design Final Program
Once research is complete and prototypes have been created, the design of the full program
can begin.

5.   Construct Final Program
Once the design of the final program has been finalised it will be implanted and tested in the
emulation environment and physical hardware.

Project Deliverables

1.   Initial Report – Due by 29th October 2009, 4PM
This document describes initial research and development activities from the early weeks of the
project, and outlines project goals and deliverables.

2.   Interim Report – Due by 21st January 2010, 4PM
A more detailed report on the progress of the project, the Interim Report describes
activities and research undertaken since the submission of the Initial Report and outlines
any problems encountered and adjustments made to compensate.

3.   Final Report – Due by 6th May 2010, 4PM
The final report is a complete submission describing the entire project development,
including some details from the Initial and Interim Reports.

4.   Documentation
A collection of separate documentation (user manuals etc) for the final product – included with
the Final Report appendices.

5.   Project Presentation
This is the presentation given to supervisors and staff at the end of the project.

Time Allocation

Research: 28/09 – 13/11 (35d)
Prototyping: 12/11 – 18/12 (27d)
Emulation: 10/11 – 18/12 (29d)
Interim Report: 16/12 – 19/01 (25d)

Design Final Program: 01/02 – 19/02 (19d) (Visio can’t do maths, apparently)
Construct Final Program: 17/02 – 02/04 (32d)
Final Report: 05/04 – 03/05 (21d)
Presentation: 24/05 – 04/06 (10d)

Note that according to this research should already be complete and prototyping should have begun. As it is at the moment research and prototyping will probably be interleaved as I evidently have a lot to learn around Windows Presentation Foundation (the Micro Framework GUI libraries). The ‘business classes’ which do all the heavy lifting of the actual functionality should be a lot easier. I hope =)

Weeks 1 & 2 – Mockup Mania

After much consideration, time, effort and a little bit of investment, I’ve completed a set of UI mockups for my system.

An impromptu equipment list for the physical device:

• GHI Electronics Embedded Master Development System (#GHI-00108) – USD 299.95 / GBP 182.91
• ZG2101 WiFi Expansion (#GHI-00126) – USD 99.95 / GBP 60.95
• Telit GE864-PY GSM Module – Unknown, Specialist Suppliers
• USB Pen – GBP 6.31 for 2GB from Novatech UK (User Data Storage and Firmware Backup?)
• SD Card (?) – GBP 8.72 for 4GB

Total – £258.89 not including GSM Modules/Sensors – wow.

Without further ado:

Catch Up: Summer Break

Over summer I spent my time doing preliminary research into the feature sets, design philosophies and user interfaces of modern home security systems.

I wanted to get concrete and complete examples of systems in use, so I started out by looking into ADT. From Wikipedia:

ADT Security Services, originally American District Telegraph now also known as ADT Fire and Security or simply ADT, is a division of Tyco International and a worldwide supplier of electronic security systems, fire alarm systems, communication systems, and integrated building management systems.

ADT in the UK

ADT first entered the UK in the late 1950s with the establishment of Electric Protection Services Limited based in London and introduced central monitoring in the mid-60s at the request of several leading banks, despite not opening a central monitoring station of their own. The 1970s and 80s brought steady growth.

In the mid 1990s, ADT Inc was acquired by Tyco International at the same time Tyco also bought up the UK firm Thorn Security. In 1997, ADT Fire and Security plc was formed from the merger of three of the UK’s largest security firms: ADT, Thorn Security and Modern Security Systems.

Today, ADT is the UK’s leading security company, helping to protect over 250,000 UK family homes and 160,000 businesses across the country.

From there I went to ADT’s UK website and began looking at how the company markets its systems to customers. The website seeks to create the impression of an easy to use, yet flexible system which provides peace of mind to the home or business owner.

I wanted to see beyond the marketing spin, so I began looking around for user manuals and engineer documentation. I found a website – www.tech-man.com – and downloaded a couple of manuals for a (2006?) system produced by a company named North Building Technologies Ltd. As far as I can remember, I chose that manufacturer because I was researching a system I had seen that day, but an eBay Auction seems to indicate that the system is related to/sold by ADT.

A search around their site seemed to indicate that the manuals I found were for a Honeywell Security Galaxy alarm/access control system. Honeywell is a major congomerate, producing a variety of products for consumers, business and government. I found a marketing brochure for the entire line of security products from Honeywell which had a suprising amount of technical detail.

The impression I got from reading these documents was that (at least in the case of the Galaxy line) the system was cumbersome to use. The users’ manual was definately not written to be easy to understand. For example:

Notice how the language uses terminology which is somewhat non-obvious to the user. The product itself doesn’t communicate meaning to the user in a partiularly easy to understand way either. The user must mentally organise rooms into groups and then activate or deactivate groups of sensors. From the manual:

To me this is a good example of how NOT to design a system. Meanings should be obvious, terms shouldn’t have to be explained. The user doesn’t care how the system works. They just want it to do its job and protect them with minimal work and hassle on their part.

The user should not need a sheet of indexes as long as their arm to correctly manage even a large scale installation – even being able to properly name the groups would be a start. If you need a manual like this to explain how to use the most obvious features of an alarm system, you need to fire some designers (thanks Ars!).

I think it was around this point that I decided my product would be easy to use above all else. I wanted to make the alarm that Apple would make. Sort of.

I spent most of the rest of summer break reading these two books:

I picked up a lot of great pointers from both books which began to give me an idea of what goals would and wouldn’t be reasonable to aim for in the time I have available. I’ll talk more about this later on. For now it’s enough to say I was about ready to return to University and kick things off. The books should prove themselves very useful over the coming weeks and months as I cut my teeth on the world of Micro Framework development.