IoT: Design and Prototype
Design
The customer needed a new security system with a distance sensor, a light that lighted up on detection,
a button to start and stop the alarm, and a light that informed the owner. Some designs must be created
to satisfy these standards.
We produced several solutions to meet the client's needs using only the pieces that were accessible. Of
course, some requirements, such as notifying the owner, might be better served by a software solution,
but the buzzer and LED should suffice as a start. We also looked at various alternatives outside of the
client's specifications to see whether they were more effective, finally settling on the client's preferred
motion sensor because it was already accessible to us and was less noticeable.
We then used a requirements diagram to outline how the alarm system would match the client's
criteria; this was also done using several types of sensors to demonstrate that the logic would be
consistent across all of them. The plan was not only to notify the owner, but also to log the information
in a database and transmit and continue to notify the owner until a manual override was detected.
A flowchart was also created to depict the stages that the security system will go through to remain safe
without being unduly complicated or bloated. This was also verified across several types of sensors to
ensure that the logic remained consistent; if the reasoning remained consistent, modifications to the
sensor down the road are more practical. It would simply be more difficult to deploy if the entire system
were based on a single sensor.
, An early iteration of the security system had an M2M interface that enabled the brightness of the LED to
be adjusted from a web browser; this could easily be adapted into the mobile realm as well. Using the
existing Node-Red dashboard also allows the user to remotely activate the alert, which would be useful
for testing.
A block chart was created to clearly explain how each component will flow and interact with one
another. Because of the small number of pieces, executing instructions via these components should not
be too difficult to program or implement.
Design
The customer needed a new security system with a distance sensor, a light that lighted up on detection,
a button to start and stop the alarm, and a light that informed the owner. Some designs must be created
to satisfy these standards.
We produced several solutions to meet the client's needs using only the pieces that were accessible. Of
course, some requirements, such as notifying the owner, might be better served by a software solution,
but the buzzer and LED should suffice as a start. We also looked at various alternatives outside of the
client's specifications to see whether they were more effective, finally settling on the client's preferred
motion sensor because it was already accessible to us and was less noticeable.
We then used a requirements diagram to outline how the alarm system would match the client's
criteria; this was also done using several types of sensors to demonstrate that the logic would be
consistent across all of them. The plan was not only to notify the owner, but also to log the information
in a database and transmit and continue to notify the owner until a manual override was detected.
A flowchart was also created to depict the stages that the security system will go through to remain safe
without being unduly complicated or bloated. This was also verified across several types of sensors to
ensure that the logic remained consistent; if the reasoning remained consistent, modifications to the
sensor down the road are more practical. It would simply be more difficult to deploy if the entire system
were based on a single sensor.
, An early iteration of the security system had an M2M interface that enabled the brightness of the LED to
be adjusted from a web browser; this could easily be adapted into the mobile realm as well. Using the
existing Node-Red dashboard also allows the user to remotely activate the alert, which would be useful
for testing.
A block chart was created to clearly explain how each component will flow and interact with one
another. Because of the small number of pieces, executing instructions via these components should not
be too difficult to program or implement.
