This document discusses the design and prototype 1 of a home automation system called Home-Mess. It introduces prototyping and its benefits, including allowing users to visualize possibilities and identify failures. The objectives are defined as identifying user requirements, developing a supportive design solution, and designing a low-fidelity prototype. User requirements and a two-level prototyping approach are described. The presentation concludes by outlining next steps of evaluation, data analysis, user testing, and new designs.

1. Home-Mess System Presentation II: Design & Prototype 1 Arundhati, Ihab, Ibrahim, Fareed, Zain

2. IntroductionPrototyping provides us with tangible models which help users visualize possibilities and identify failures.Explore the development from an idea to a prototype Construct part of the development lifecycle used to provide valuable insight into the look-and-feel, and the general workflow of an application. Prototypingis the keynode of iterativedevelopment

3. ObjectivesDefining the ProblemIdentifying user requirementsDevelopment of a supportive design solutionDesigning of a low-fidelity prototype.Creating a working model of the system so that conceptual ideas can be 'road tested', alternatives explored and user feedback gathered at an early stage.

4. User Requirements

5. User Requirements- cont.

6. Design Stage

7. Our ApproachJ. Nielsen distinguishestwolevels of prototypingaccording to the level of interaction.Man-Machine InterfaceFunctionalitiesLevels of prototyping

8. Horizontal prototypeIt isthe 'surface interface'. Functionalitiesare not working, but itallows to achieve a perception test.Allowsto check the local behaviour of the interface Identifies the critical points whereusabilityproblems are likely to appear.

9. Vertical prototypeIt implements a consistent set of functionalities in order to allow the user to achieve a typical scenario of use. Some of thisfunctionalitiescouldbesimulated.This second stage of the prototyping phase consists in a series of user tests duringwhich the critical points raisedpreviously are evaluated.

10. StructureMain/Home ScreenMenuInt. MsgsSettingsPhone MsgsEventsSurv CamCustomTasks

11. Prototyping Stage

12. Planning

13. Prototype creation

14. Prototype creation

17. DemoIhab, Arundhati

18. ConclusionPrototypes start off as empty shellsUsability problems detected It will be used to to evaluatethe usabilityof the wholesystem.

19. What’s Next?Evaluation:Data Analysis: What is new, what could we improve?

20. User Testing: What new problems present themselves?