Assumptions

Certain assumptions have been made while designing the badge tracking system. If any of these assumptions prove not to be true, certain design changes will be in order, and capabilities and/or specifications will need to be added or modified.

• Sensor Controller
  1. Communications are available both directions between Routers and Badges and between Routers and the Controller, and are handled by the Zigbee system. Badges are able to pull status updates from the Controller through the Routers.
  2. "Reader" block in block diagram is completely handled by the Zigbee system.
  3. The system utilizes a standard local area network, assumed to be already present at the school.

• Data Controller
  1. The Data Controller components (including databases) will be served from a single server.
  2. The server housing the Data controller components will be properly secured (including encryption if necessary).
  3. This server will be administered by someone with Linux/MySQL experience.
  4. The Data Controller components will not be directly accessible by any clients.
  5. The Data Controller module assumes that all staff and students have, and are wearing, badges and that anyone entering the area will be given and will wear a guest badge.

• Interface Controller
  1. The interface controller provides various types of interfaces to each type of user, and it assumes that users log into the system from within the local area network (or through VPN software).
  2. The interface controller is only responsible for passing on data and commands. It does not address data error.

• User Assumptions
  1. The user will be able to wear or hold the badges close to themselves at all times while inside the facility.
  2. The user understands that they need to keep the badges near them, or they have an assistant that will make sure the badge is always with this person.
  3. The customer will contact us, the developer, for all upgrading, redesigning, or maintenance issues that involve recompiling the source code.