Design Principles of connected Devices

The Internet of things(IoT) is the network of physical objects that contain embedded technology to communicate and sense or interact with internal states or the external environment

Design Principles of connected Devices

•some of the overarching principles that can be applied when designing an Internet of Things system-

•CALM AND AMBIENT TECHNOLOGY-calm technology—systems which don’t vie for attention yet are ready to provide utility or useful information when we decide to give them some attention. With its focus on computing power being embedded everywhere, Iot is often also referred to as ambient computing

•ACCEPTANCE-One of the main issues with introducing any new technology or service that is radically different from the normal is getting people to understand and accept it

•PRIVACY-With more sensors and devices watching us and reporting data to the Internet, the privacy of third parties who cross our sensors’ paths (either by accident or design) is an important consideration. Designers of an Internet of Things service will need to balance these concerns carefully

• DATA RIGHTS-With the number of sensors being deployed, it isn’t always clear whose data is being gathered the term data subjects—those people to whom the data pertains, regardless of whether they owned the sensors used to gather the data or the property where the sensors were sited. There’s no clear understanding of what rights, if any, such “data subjects” will enjoy, but it is an area that deserves more debate and attention

•INTERNET USAGE-When you are thinking of the networked aspect of Internet of Things objects, it might help to draw on experiences and design guidelines from existing network deployments.

•SMALL PIECES, LOOSELY JOINED- Even if you are building all the components of your service, it makes sense not to couple them too tightly together. The Internet flourished not because it is neatly controlled from a central location, but because it isn’t; it is a collection of services and machines following the maxim of small pieces, loosely joined.

•PROTOCOLS OF INTERNET Where possible, you should use the same protocols and conventions that the rest of the Internet uses. In the few cases where the existing protocols don’t work, such as in extremely low-powered sensors, a better solution is to work with your peers to amend existing standards or create new open standards which address the issue within the conventional standards groups.

•COMMON SERVICES- Because the Internet is so welcoming and tolerant of all sorts of devices and services, the endpoints have a massively disparate and diverse range of capabilities. As a result, building services which can be used by all of them is a nearly impossible task. However, a number of design patterns have evolved to mitigate the problem.

•AFFORDABLE- Affordances provide strong clues to the operations of things. Plates are for pushing. Knobs are for turning. Slots are for inserting things into. Balls are for throwing or bouncing. When affordances are taken advantage of, the user knows what to do just by looking: no picture, label, or instruction is required. Complex things may require explanation, but simple things should not. When simple things need pictures, labels, or instructions, the design has failed