A cellphone for mommie

Well, one would have thought that the market researchers and mobile phone manufacturers would have developed such a cellphone by now. Most of the low-end cell phones today offer a lot of the baby proof features, however I think they have failed to test certain highly important scenarios. For all the mobile phone manufacturers out there, I present these in my latest post.

Test Scenarios:

1. Throw the cellphone in a bucket(upto 60L capacity) and pull it out after 20 seconds.
2. Put the cellphone in the microwave for 20 seconds. Check the device responses at following settings for 20 seconds: 900,780,560  and Grill.
3. Throw the cellphone in a bowl of hot rasam/soup or some porridge.
4. Put the cellphone is the refridgerator and remove after 30 minutes.
5. Slam the cellphone on the floor. Pick up the pieces, re-assemble and test from step 1.
6.The litmus test however is to put the cellphone in a washing machine full of clothes and on a full cycle. 1
    hour 45 minutes later if the device is still working in pre-wash condition, you have the winner.
7.No touch screen,please I couldn't bear the massacre.

Now let us move over to the software. Why? Oh!dear, I'm sure you would have noticed that a 10 month old can successfully unlock your cellphone and send messages to all the contacts whose names start with an 'A'. In my case it is 'Adaddy'. If not, well then I have the smarter kid.

Now since I am a software engineer and I understand the importance of clear requirements, here goes:

Assumption: You are using a basic model cellphone that does not have a touch screen, wifi, bluetooth or any other data exchange feature like push mail etc supported by the network provider.

1. A key/setting to disable send message.
2.A key/setting to disable delete message.
3.A key/setting to disable make call.
4.A key/setting to disable accept call.
5.A key/setting to disable reject call.
6. Allow manual override of such setting with a key/pattern.

Mommies/Daddies reading this post are most welcome to add their requirements information and test scenarios. Please do not suggest behavioral correction techniques, they won't work.