Requirements Specification
Document Outline

1. Introduction

The system will be used to keep accurate logs of the time that the counselors spend with the patients. The system will read the number from the counselor's chip and record their number and the time that it was scanned. It will then record the next time it is scanned and put the ending time stamp in the log. The log will be sent at a predetermined time to a database.

1.1. Problem Statement

The problem being solved is the inaccurate recording of counselor – patient sessions. The system needs to be able to accurately keep track of the time that each counselor spends with their patients and store this information in a reliable way.

1.2. System Personnel

  1. System End Users – Counselors, Patients

  2. Project Managers – Doug Karl, Trevor Boardman, Joe Kadrich

  3. System Analysts – Trevor Boardman, Joe Kadrich

  4. System Developers – Trevor Boardman, Joe Kadrich

  5. Key Advisors – Doug Karl, Jim Skon

1.4. Impact Analysis

The system will increase timekeeping efficiency by making it easier for the counselors to keep track of their session times.

The negative impact associated with this system is the initial training the counselors will have to go through. While the training may not be intense, it might take awhile for them to get used to using the new system on a regular basis. There is also a bit of a cost up front to get the system components.

1.5. Related Systems

1.5.1. Related System

One related system would be the chapel scanners.

2. Functional Requirements

2.1. User Interface Overview

The user interfaces with the system in 2 main ways. The first is by using their ID cards to clock in and out of sessions. The second is by accessing the information from the database.

2.2. System-Specific Requirements

The system must have rfid cards that are assigned to both clients and counselors.

The system must have one RFID scanner.

The rfid scanners must be able to connect to a laptop running Ubuntu and send rfid card information directly to the database via ssh in a script.

The laptop will have a script installed onto it that processes the rfid information.

The script must be able to insert time stamps for each scan and send them with SSH to the database.

The database must be accessible by the Live Wellness Center.

The database must contain fields for time stamps, client information, counselor information and the session lengths.

The system must contain a website for the managers of LWC to access session information.

3. Non-Functional Requirements

3.1. System-Related Non-Functional Requirements

Non-functional system requirements include some or all of the following:

  1. a. operational environment

    i. hardware platform

    i. RFID cards and reader

    ii. Laptop

    ii. software platform

    i. Ubuntu

    b. general characteristics

    i. reliability

    i. The information is reliably logged.

    ii. The software gracefully handles most crashes.

3.2. Process-Related Non-Functional Requirements

  1. development time

  2. development cost

    1. No development cost

    2. If raspberry pi is desired, it runs around $80

  3. installation

    1. developer access to installed environment

  4. standards conformance

    1. HIPAA Compliance

3.3. Personnel-Related Non-Functional Requirements

  1. for users:

    1. training

      1. For consistent use of the system.

The system must have rfid cards that are assigned to both clients and counselors. – 90%

The system must have one RFID scanner. – 100%

The rfid scanners must be able to connect to a laptop running Ubuntu and send rfid card information directly to the database via ssh in a script. – 100%

The laptop will have a script installed onto it that processes the rfid information. – 100%

The script must be able to insert time stamps for each scan and send them with SSH to the database. – 100%

The database must be accessible by the Live Wellness Center. – 100%

The database must contain fields for time stamps, client information, counselor information and the session lengths. – 100%

The system must contain a website for the managers of LWC to access session information. – 100%

3. Non-Functional Requirements

3.1. System-Related Non-Functional Requirements

Non-functional system requirements include some or all of the following:

a. operational environment

i. hardware platform

i. RFID cards and readers – 100%

ii. Laptop – 100%

ii. software platform

i. Ubuntu

b. general characteristics

i. reliability

i. The information is reliably logged. – 100%

ii. The software gracefully handles most crashes. – 60%

Topic revision: r7 - 2016-04-29 - TrevorMBoardman
 
This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback