Giter VIP home page Giter VIP logo

wearables-final-group-project's People

Contributors

awmusic12635 avatar jrgabler avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar

Forkers

jrgabler

wearables-final-group-project's Issues

Choose Beacon ID System (p2)

You should use your Gimbal beacons, either as iBeacons or Eddystone Beacons. You should have 6 beacons for your group. You need to decide on an identification system (e.g. same UUID but different Major/Minor numbers). The identification system should take into account the same type of machine (e.g. X-Ray) as well as recognize each individual machine of that type (e.g. X-Ray machine 1, X-Ray machine 2 etc.) That is, it needs to be capable of handling multiple devices of each multiple types. Here are the devices you need to track:

  1. X-Ray machine (2 of them)
  2. EKG machine (3 of them)
  3. MRI machine (1 of them)

Checkout Feedback

a. When trying to check out a device:
i. If authorized to do so, provide a visual, tactile and audio feedback and “check” out the device so that it appears checked out by that person in the admin console.
ii. If not authorized or if the device is not available for checkout, provide a different visual, tactile and audio feedback than when they are authorized. In addition, provide the information to the admin console so it can display invalid attempts (differentiate between unauthorized and unavailable).

Documentation Part 1

  1. A diagram of your system showing how all of the pieces communicate and what technologies you are using for each part.
  2. A description of your system describing why you did what you did and why you chose the various pieces.
  3. A user manual for the end user to be able to set up and use your system.
  4. All code, database structures, etc.

Documentation Updated (p2)

  1. An updated diagram of your system showing how all of the pieces communicate and what technologies you are using for each part.
  2. A description of your beacon-type choice describing why you chose that option.
  3. A description of your identification system including why you designed it that way.
  4. A description your mapping system including why you designed it that way.
  5. An updated user manual for the end user to be able to set up and use your system.
  6. Updated admin console showing the new information.
  7. All code, database structures, etc.

Admin Console base functions

a. Allows the easy addition of addition/editing/removal of RFID tag/card values with the associated person using a Photon and an RFID reader. How you accomplish this is up to you.
b. Allow the assigning of devices to groups of people who can check them out.
c. Assign people to the groups that can sign out the various devices. A person can be a member of multiple groups.
d. Add/remove/update devices that can be checked out.
e. Ability to show who has what device and where it is located (location will be part of Part 2 of the project).
f. Ability to show bad attempts to check out a device (not available for checkout or not authorized)
g. Ability to add other “admins” with username and password (should be hashed).
A super admin that can perform item g – the only user that is able to do item g

Building / Location Map (p2)

Next, you will need to come up with a “map” of buildings and rooms. For the purposes of this assignment, you only need to come up with 2 buildings of 3 rooms each, but your mapping scheme should account for more buildings and rooms in each building.

Next you will need to assign each “device” to a building and room where they will start out.

Beacon Tracking (p2)

Once it is checked out, you will need to track its location in the various buildings/rooms. You will do this by writing NodeJS code that will scan for the beacons and report to the admin system any beacons that come within immediate or near ranges as being in that room and mark it as such. If the beacon is no longer within those ranges, report that and remove it from that building/room.

You will need to update your admin console to display who has what machine and where it is as well as where it is if it is not checked out. You will also need to note if it is “between” buildings/rooms (i.e. not being recognized as being immediate/near in any room).

Extend checkout with locations (p2)

You will then need to add to your Part 1 code, the ability to check out these devices from those locations according to the access rules you came up with for Part 1 (e.g. are they allowed to check it out, is it actually in that room, etc.). More than one type of a machine may be in a room at one time.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.