SRS

EOS DIJITLALCHEMY SOFTWARE REQUIREMENTS SPECIFICATION(SRS) for LWTC

Version 1, Mar 25th, 2018
Copyright (C) 2018 Empire of Slop https://empireofslop.tumblr.com/

Everyone is permitted to copy and distribute verbatim copies of this Software
Requirements Specification document, but changing it is not allowed. A copy of this
open source software SRS document can be found online at
https://github.com/dijitlalchemy/LWTC/wiki/SRS. This SRS Document is protected under the
LWTC EOSDA License. A copy of this license can be found online at
https://github.com/dijitlalchemy/LWTC/.

Software Requirements Specification for:

    LoGun Weapon Tracking Cloud(LWTC) v1.0
    Copyright (c) 2018 Gary Wetter
    All rights reserved.

Prepared by: Gary Wetter

Table of Contents

1. Introduction
2. Overall description
3. Specific requirements
4. Prioritization and Release Plan

Revision History

This is a working document, it will change periodically.
1. Initial Release: April 4th, 2018 by Gary Wetter.

1. Introduction

1.1 Purpose

The purpose of this document is to present a detailed description of the requirements for
the open-source software LoGun Weapon Tracking Cloud(LWTC) v1.0. This document is primarily
intended for users of the software and also potential developers and manufacturers and
as reference for developing the first version of the system for the development team..

It will explain the purpose and features of the software, the interfaces of the software,
what the software will do and the constraints under which it must operate, It will also explain
the required hardware, system constraints, interface and interactions with other external
applications, tools, hardware, and systems. It will illustrate the purpose and complete
declaration for the development of the entire system.

1.2 Scope

The LoGun Weapon Tracking Cloud(LWTC), is an OEM/AM weapon tracking system that allows
guns to be tracked by law enforcement, with the aim of preventing potential shootings
in safe zones.

Current Weapon Owners must register their weapon, and have an RFID chip attached to
their weapon and activated upon registration. New Weapons will come chipped and
registered upon purchase.

All registered first responders will receive an alert when a weapon enters a designated
safe zone tier. This alert will notify them who the owner is, what weapon they are carrying
and how close they are to the red-zone. They will also receive another alert if the
owner leaves the safe zone.

Tracking will be limited to certain members of law enforcement, and at certain times,
only with certain court ordered approvals, in regards to search and seizure rights. While the
weapon is within confines private property, that being the owners home, the RFID signal will not be
recorded. The locality of the weapon will not be traced while in the confines of public spaces,
like hunting grounds, shooting ranges, etc. However, Owners will receive an alert
when their weapon has left their vicinity, and the system will ask them what they would like to do
about the situation, like report theft, or approve the movement, etc.

Should the chip fail, for any reason, these dead signals will initiate an alert to the owner,
law enforcement and designated LoGun registration centers. The owner will have sufficient time
to answer the alert. If the owners fails to do so, law enforcement will be sent a second notice
to inquire with the owner to ensure they follow through with resolving the matter.

Only authorized LoGun Registration Centers will be allowed to perform routine maintenance,
to assure the chip is assigned to the right weapon, check for tampering, check for chip life,
this can be done at a yearly frequency. LRC's will only be allowed to attach aftermarket chips
and perform routine maintenance. Weapons retailers, will only be allowed to register the owner
in the LWTC upon completion of standard weapons purchasing. Weapons manufactures will only
be allowed to register a weapon to a chip prior to production shipping. Intermediate weapons
tracking is available during shipping from manufactures to retailers.

As we can see, the systems software(LWTC) is only one part of this project. It also
includes RFID chip technology, software systems integration, so the internet and other
technologies, like localization, GPS will be required.

In the United States, this system will cover both 2A & 4A rights without violating or
diminishing those rights.

This new technology will help save lives, create jobs, raise the cost of weapons, help
improve the response time of first responders, provide a new level of security
intelligence from theft of products to the safety of human lives.

1.3 Definitions, acronyms, and abbreviations

User Someone who interacts with the system
Admin/Administrator System administrator who is given specific permission for managing and
controlling the system
Weapon Owner Someone who has a weapon with an OEM/AM RFID chip in place.
Stakeholder Any person who has interaction with the system who is not a developer.
...

2. Overall description

This section will give an overview of the whole system. The system will be explained in
its context to show how the system interacts with other systems and introduce the basic
functionality of it. It will also describe what type of stakeholders that will use the
system and what functionality is available for each type. At last, the constraints and
assumptions for the system will be presented.

2.1 Product perspective

This system will consist of many parts: one monolithic information software system with
integration into pre-existing software systems, hardware, and eventual features like
mobility.

The system will be used to track, alert and view information while being able to manage
the information and the system as a whole.

2.2 Product functions

With the core software system, based on certain criteria, certain users will be able to
receive alerts, some users will be allowed to receive alerts and conduct weapon tracking,
some users will be able to maintain weapon and RFID registration, and other users will be
allowed to administer and maintain the core system itself.

There will be a quality assurance feature, where certain users are able to provide
oversight of the information system. These are checks-and-balances that will assure the users
are not abusing the system, its data, or information generated by the system - we do
understand that once the information in presented to a user, it would be impossible to
trace that information to a piece of paper or word-of-mouth, but the last known user who
had system access and viewed or received an alert will be a pinch-point during a quality
assurance inquiry.

2.3 User characteristics

There are many types of users that interact with the system: users of the alerts and tracking,
weapon owners, LoGun registration centers, administrators and monitors.
All of these types of users has different use of the system so each of them has their
own requirements.

Some users, may overlap in their use of the system. For example Law Enforcement, will be
registered and monitored, so we can differentiate them from a common person, however
Law Enforcement will also have to register as a common person, so we can see which
weapons they are carrying off-duty, and also tag them as on off-duty officer.

There are other overlaps, which will be handled in similar fashion and we will note them
as we go...

2.4 Constraints

The core system is constrained by the system interface to RFID/GPS navigation
systems within the RFID chips. Since there are multiple systems and multiple RFID
manufacturers, the interface will most likely not be the same for every one of them.
Also, there may be a difference between what navigation features each of them provide.

More research will have to be done into choosing a suitable RFID chip - for now we will
create an arbitrary RFID chip for the development of the system.

2.5 Dependencies and Assumptions

One assumption about the product is that it will always be used on technologies that
have enough performance. If the chosen desktop computer,
does not have enough hardware resources available for the application,
for example the users might have allocated them with other applications. There may be
scenarios where the application does not work as intended or even at all.

2.6 Apportioning of Requirements

In the case that the project is delayed, there will be some requirements that could be
transferred to the next version of the system build. We will decide those details
in section 4, after specifying all of the requirements in section 3.

3. Specific requirements

This section contains all of the functional and quality requirements of the system. It
gives a detailed description of the system and all its features.

4. Prioritization and Release Plan

...