Groups

You can work in groups of two on the project. Work will need to be evenly shared. The proposals (this phase) should be projects that each person is interested in pursuing.

Phase 2: Project Proposal (3% of Project)

The main goal of this phase of the project is to identify a few projects that interest you.

Foreshadowing

Over the coming weeks we will cover a few new topics that you may want to use in your project (but you are not limited to just the topics covered in class):

• Use of additional hardware from the Maker Kit
  • Temperature sensors and Temperature Sensor Sealed
  • Photo sensor
  • PIR sensor
• Using HTML and JavaScript to create mobile phone apps (via Cordova)
• Integration with services that can send Notifications & Texts to phones
• Integration with services that can be used to collect and analyze data

Partial Project Requirements

Projects are intended to be a proof-of-concept. They should demonstrate that a concept is feasible, but they don’t necessarily have to be an accurate depiction of all aspects of the project. For example, an IoT based system to control home appliances could use a small DC motor or hobby servo or LEDs rather than actually controlling a real appliance.

The project will have several requirements. The ones that are most relevant now are:

• It should use multiple elements of an IoT stack
  • There should be one or more embedded devices
  • There should be sensors and feedback
  • There should be some graphical user interface for some features
  • There should be some networking
    • Moreover, there should be a valid reason for networking (i.e., some substantial benefit of networking. Some thing that could be done that wouldn’t be possible without the network)

There may be bonus credit or recognition for noteworthy ideas. There are many different aspects of an IoT product that may be noteworthy:

• It may be particularly fun or novel
• It may have significant societal benefit (improving the quality of life, assisting with disasters or humanitarian efforts, etc.)
• It may be particularly marketable…. (full rights to the product will be transferred to Professor Siever (just kidding about that last part)).

Bonus credit may also be given for exploring new technologies or tools not covered in class. Here are just a few examples that may merit bonus credit:

• Platforms other than the Photon
  • ESP8266 based platforms (carried by AdaFruit, SparkFun, Amazon)
  • Other Arduino-variants, etc.
• Use of other transports (Bluetooth, LoRa, Zigbee, Cellular, etc.).
• Other approaches to network infrastructure, like Things Board, cloud platforms from Google, IBM, Microsoft, Amazon, AdaFruit.io, etc.)
• Other hardware inputs/outputs not covered in class (browsing AdaFruit and SparkFun may be helpful)
• Wearables

Phase 1 Deliverables

There are two aspects of the “deliverables” for this phase of the project:

1. Safety agreement (in SafetyAgreement.md). Just like during studios, you need to agree that you will follow general safety guidelines when developing your projects. Each team member should read the rules and enter their full name where provided.

2. Two Potential Project Proposals

   • The repo for this project contains two files: project1.md and project2.md. Complete the questions in each to describe two different projects.
   • Pick projects that you would be willing to work on.
   • The projects should be distinct. They should cover different topic/problems.
   • Assume that one will be selected for you. The numbers (project1 and project2) don’t indicate priority or preference.

Repositories

Before configuring a repository, decide if you will be working in a group or not. If you will be working in a group, decide who will create the GitHub group and who will join it.

Follow the same basic process used in studios and previous assignments to create/join a group, download the resulting repository (with GitHub Desktop), and import it using the Particle Desktop IDE.

The GitHub Link is: https://classroom.github.com/g/yjcpOT3q

Submission & Checkout

You must commit work to GitHub by 11:59pm (CST) Sunday, Oct. 27th.