Needs and Requirements

User Needs

1. Users need to be able to easily deploy the system in areas with high feral cat populations to provide continuous monitoring.

2. Users need to be automatically notified by the system of new areas of focus for trapping un-spayed/neutered cats based on new cats coming into the colony, such as individual cats that are not eartipped or have health issues.

3. Users need to be able to access key insights such as population and percent sprayed.

4. Users need to be able to view charts of metrics over time such as the population of cats and percentage neutered in a community.

5. Users need to be able to access information from multiple geographical locations (as specified in User Requirement #4).

6. Users need to be able to export relevant data to appropriate file formats (.xlsx or .csv).

7. Users need to be able to deploy and access the system in a variety of areas, including those with limited access to power and the internet via LTE and battery packs.

8. Users need to be able to view raw camera data from the system such as key images of cats (identified through motion detection) and/or live video feed through all times of day regardless of lighting conditions.

System Requirements

Parentheses reference the user needs these system requirements seek to fulfill

1. System shall be able to detect and recognize feral cats caught on camera. (1)

2. System should be able to identify and track individual feral cats in the same community, similar to facial recognition with humans. (1 and 2)

3. System shall be able to track population of cats over time in a single location. (1)

4. System shall be able to detect ear-tipped cats and track them accordingly. (2)

5. System shall be able to generate charts and other visualizations based on data stored. (3 and 4)

6. System shall be able to monitor and store multiple cat communities separately and simultaneously. (5)

7. System shall be able to export/dump database content to CSV or Excel format for external processing. (6)

8. System should minimize power usage (less than 2.5W on average) to be able to operate on battery backup when mains power is unavailable. (7)

9. System shall use a camera capable of capturing images in a range of outdoor lighting and weather conditions through No-IR style cameras (such as at night and during precipitation). (8)

10. System should track location data in order to draw correlation between sightings. (5)

Non-functional Requirements

1. The system shall maintain data security in storage and transit.

2. The system shall be physically secure and tamper resistant.

3. The system shall have acceptable uptime for customer use (as close to 24/7 as possible).

4. The system shall be remotely maintainable without causing disruption to customers.

Domain Requirements

1. Cameras shall not be directed towards private areas without prior approval from the property owner.

2. Camera shall be installed with approval from the property owner. If installing on public property the township must approve the installation.

3. Website and server shall adhere to TLS and protect privacy according to privacy policy.

4. All sensitive user data stored according to IEEE 1619-2018 (IEEE Standard for Cryptographic Protection of Data on Block-Oriented Storage Devices).