This is the delivery checklist for the FN SDK Final Acceptance Test meeting held July 612, 2022.
This list was created from the FN SDK Statement of work milestones as well as the derived software requirements.
...
1.3.2. VictoR Core Library (680 hrs)
1.3.4. Quality Assurance
...
1.4. Delivery (90 hrs)
- 1.4.1. Package source code & files for delivery
- 1.4.2. Meetings, Documents, Knowledge Transfer
- 1.4.3. Final acceptance meeting
...
1.3.5. Documentation (128 hrs)
- 1.3.5.1. Generate code documentation
- 1.3.5.2. Create getting started guide
- 1.3.5.3. Create technical documentation on the SDK
ID | Name | Description | |
---|
9.1 | Code Documentation | The FN VictoR SDK shall come with a fully documented API for developers | |
9.2 | Technical Documentation | Unity shall provide FN with technical documentation on the design of the FN VictoR SDK that details design choices, outlines the software architecture, and illustrates intended use cases. | |
9.3 | Getting Started Guide | Unity shall provide FN with a getting started guide that explains how to set up a Windows or Android development project and integrate it with the FN VictoR SDK. | |
...
Features Removed from Statement of Work/Not Supported
...
ID | Name | Description | |
---|
2.11
| Subscribe to BLE GATT Characteristic Indicate
| The BLE Communications Interface shall provide the ability to subscribe to indications from supported GATT Characteristics of the Device Information, Device Configuration, and Object Transfer GATT Services within an FN VictoR device.
Note |
---|
Out of scope for this phase. |
| |
2.12
| Acknowledge BLE GATT Characteristic Indicate
| The BLE Communications Interface shall provide the ability to acknowledge received indications from supported GATT Characteristics of the Device Information, Device Configuration, and Object Transfer GATT Services within an FN VictoR device.
Note |
---|
Out of scope for this phase. |
| |
2.18 | Multi-device Support
| The FN VictoR SDK may support simultaneous BLE and/or USB communications with multiple FN VictoR devices.
Note |
---|
Simultaneous device connections implemented but not tested because of lack of devices. |
| |
4. Device Information Service
ID | Name | Description | |
---|
Warning |
---|
Holster Draw not supported by firmware. |
|
4.12
| Read Last Holster Draw Timestamp
| The Device Information Service shall provide the ability to read the last holster draw timestamp from an FN VictoR device.
| |
4.13
| Read Last Holster Draw Total Draw Time
| The Device Information Service shall provide the ability to read the last holster draw total draw time from an FN VictoR device.
| |
4.14
| Notify Last Holster Draw Information
| The Device Information Service shall provide the ability to receive last holster draw information notifications (timestamp and total draw time fields) from an FN VictoR device.
| |
5. Device Configuration Service
Warning |
---|
Not supported by firmware. |
-
1.3.2.4.1. Set device name -
1.3.2.4.3. Set computer vision model (none, VictoR, LTS, SmartProtectoR) -
1.3.2.4.4. Set computer vision application -
1.3.2.4.8. Enable/Disable physical buttons
ID | Name | Description | |
---|
Warning |
---|
Trigger detection removed from the Statement of Work. |
|
5.26
| Read Trigger Threshold Value Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to get the trigger threshold value trigger detection parameter from an FN VictoR device as a value between 0 and Tmax.
| |
5.27
| Write Trigger Threshold Value Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to set the trigger threshold value trigger detection parameter of an FN VictoR device to a value between 0 and Tmax.
| |
5.28
| Read Maximum Trigger Threshold Value Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to get the maximum trigger threshold value (Tmax) trigger detection parameter from an FN VictoR device as a value between 0 and 65535.
| |
5.29
| Write Maximum Trigger Threshold Value Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to set the maximum trigger threshold value (Tmax) trigger detection parameter of an FN VictoR device to a value between 0 and 65535.
| |
5.30
| Read Trigger Impact Window Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to get the trigger impact window trigger detection parameter from an FN VictoR device as a value between 1 and 99 milliseconds.
| |
5.31
| Write Trigger Impact Window Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to set the trigger impact window trigger detection parameter of an FN VictoR device to a value between 1 and 99 milliseconds.
| |
5.32
| Read Post-Trigger Impact Window Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to get the post-trigger impact window trigger detection parameter from an FN VictoR device as a value between 0 and 65535 milliseconds.
| |
5.33
| Write Post-Trigger Impact Window Trigger Detection Parameter
| The Device Configuration Service shall provide the ability to set the post-trigger impact window trigger detection parameter of an FN VictoR device to a value between 0 and 65535 milliseconds.
| |
6. Object Transfer Service
ID | Name | Description | |
---|
Warning |
---|
Object Transfer Service removed from Statement of Work. |
|
6.1
| Object Transfer Service
| The FN VictoR SDK shall provide developers with a multi-platform, BLE protocol Object Transfer Service that allows for reading and writing of binary objects including video, images, and vision system model files to and from an FN Victor device over a common interface.
| |
6.2
| Write Command PDU
| The Object Transfer Service shall provide the ability to write Object Transfer Command PDUs to an FN VictoR device
| |
6.3
| Read Response PDU
| The Object Transfer Service shall provide the ability to read Object Transfer Response PDUs from an FN VictoR device.
| |
6.4
| Notify Response PDU
| The Object Transfer Service shall provide the ability to receive notifications of incoming Object Transfer Response PDUs from an FN VictoR device.
| |
6.5
| File Read Command Class
| The Object Transfer Service shall support the File Read Command Class of object transfer commands.
| |
6.6
| Write File Command
| The Object Transfer service shall provide the ability to write the Read File Object Transfer Command to an FN VictoR device with a specified byte offset, number of bytes to read, and file name to read from the device.
| |
6.7
| Read File Command Data
| The Object Transfer service shall provide the ability to read the Read File Object Transfer Command Data from an FN VictoR device which contains the requested file contents in binary format.
| |
6.8
| Notify File Command Data
| The Object Transfer service shall provide the ability to receive Read File Object Transfer Command Data notifications from an FN VictoR device which contains the requested file contents in binary format.
| |
...
Test Documentation
View file |
---|
name | QA_Test_Documentation.zip |
---|
|
...
...
Meeting Information
...
LINK TO MEETING VIDEO HERE
Topic: Rescheduled FN SDK Delivery
Start Time: Jul 12, 2022 08:19 AM
Meeting Recording:
https://unity3d.zoom.us/rec/share/VhO1BKgxBFidTJllP_zG6Q9_tOQr3LQQi-t1E9R_ZmnFz2rdOBbD_-D_M0vWP648.ZqT0ALE6j_g0pGg3