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)
- (See below)
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.2.1. Set up development environment
- 1.3.2.2. Core Framework
- 1.3.2.3. Communications API
- 1.3.2.3.1. Bluetooth Low Energy Implementation
- 1.3.2.3.2. USB Implementation
ID | Name | Description | |
|---|---|---|---|
2.1 | BLE Communications Interface | The FN VictoR SDK shall provide developers with a common cross-platform interface that facilitates communications with an FN VictoR device over a Bluetooth Low Energy (BLE) connection. | |
2.2 | BLE Scan | The BLE Communications Interface shall support scanning and identification of nearby FN VictoR device radios. | |
2.3 | BLE Scanned Devices | The BLE Communications Interface shall provide the ability to query for a list of scanned FN VictoR devices. | |
2.4 | BLE Connection | The BLE Communications Interface shall provide the ability to connect to any FN VictoR device in its scanned devices list. | |
2.5 | BLE Connected Devices | The BLE Communications Interface shall provide the ability to query for a list of connected FN VictoR devices. | |
2.6 | BLE Disconnection | The BLE Communications Interface shall provide the ability to disconnect from any FN VictoR device in its connected devices list. | |
2.7 | BLE Reconnection | The BLE Communications Interface shall attempt to reconnect to any FN VictoR device in its connected devices list if the connection to that device is lost. | |
2.8 | Read BLE GATT Characteristic | The BLE Communications Interface shall provide the ability to read from GATT Characteristics of the Device Information, Device Configuration, | |
2.9 | Write BLE GATT Characteristic | The BLE Communications Interface shall provide the ability to write to GATT Characteristics of the Device Information, Device Configuration, | |
2.10 | Subscribe to BLE GATT Characteristic Notify | The BLE Communications Interface shall provide the ability to subscribe to notifications from supported GATT Characteristics of the Device Information, Device Configuration, | |
2.13 | USB Communications Interface | The FN VictoR SDK shall provide developers with a common cross-platform interface that facilitates communications with an FN VictoR device over a Universal Serial Bus (USB) connection. | |
2.14 | USB Connected Devices | The USB Communications Interface shall provide the ability to query for a list of connected FN VictoR devices. | |
2.15 | Read USB Characteristic Equivalent | The USB Communications Interface shall provide the ability to read from the USB-equivalent characteristic data structures of the Device Information, Device Configuration, | |
2.16 | Write USB Characteristic Equivalent | The USB Communications Interface shall provide the ability to write to the USB-equivalent characteristic data structures of the Device Information, Device Configuration, | |
2.17 | Single Device Support | The FN VictoR SDK shall support either BLE or USB communications to a single device, depending on which communications mode the device is currently configured to use. |
3. Platform / OS
- 1.3.2.5. Common Logging API
- 1.3.2.6. Platform/ Operating System API
- 1.3.2.6.1. Windows Support Implementation
- 1.3.2.6.2. Android OS Support Implementation
ID | Name | Description | |
|---|---|---|---|
3.1 | Windows BLE | The FN VictoR SDK shall support BLE communications to an FN VictoR device for Windows OS application development. | |
3.2 | Windows USB | The FN VictoR SDK shall support USB communications to an FN VictoR device for Windows OS application development. | |
3.3 | Android BLE | The FN VictoR SDK shall support BLE communications to an FN VictoR device for Android OS application development. | |
3.4 | Android USB | The FN VictoR SDK shall support USB communications to an FN VictoR device for Android OS application development. | |
3.5 | Windows Version Target | The FN VictoR SDK shall support development for applications targeting Windows 10. | |
3.6 | Android Version Target | The FN VictoR SDK shall support development for applications targeting Android 10. |
4. Device Information Service
...
- 1.3.3.1. Create Unity project
- 1.3.3.2. Implement Unity interface to Core Library
- 1.3.3.3. Create base prefabs & gameobjects
- 1.3.3.4. Create single example scene
- 1.3.3.5. Generate .unitypackage
...
ID | Name | Description | |
|---|---|---|---|
8.1 | Logging System | The FN VictoR SDK shall provide developers with a multi-platform Logging System that aides in the development, debugging, and monitoring of interactions between their applications and the SDK, and interactions between the SDK and the FN VictoR device. | |
8.2 | Logging Levels | The Logging System shall provide DEBUG, INFO, WARN, ERROR, and | |
8.3 | DEBUG Log Level | The DEBUG Log Level shall provide information about SDK and/or FN VictoR device behavior that may be useful to diagnose or debug issues. | |
8.4 | INFO Log Level | The INFO Log Level shall provide information about SDK and/or FN VictoR device events that would be considered useful knowledge for general purposes. | |
8.5 | WARN Log Level | The WARN Log Level shall provide information about SDK and/or FN VictoR device events that may be an indication of a problem with SDK or device interaction. | |
8.6 | ERROR Log Level | The ERROR Log Level shall provide information about SDK and/or FN VictoR device errors that indicate a definite but potentially recoverable problem with SDK or device interaction. | |
8.7 | FATAL Log Level | The FATAL Log Level shall provide information about SDK and/or FN VictoR device errors that indicate a critical problem with SDK or device interaction that results in application termination. | |
8.8 | Logging Targets | The Logging System shall support logging to the standard output and standard error streams, or to a file. |
9. Documentation
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.18 |
|
|
4. Device Information Service
ID | Name | Description | |||
|---|---|---|---|---|---|
| |||||
|
|
| |||
|
|
| |||
|
|
| |||
5. Device Configuration Service
| Warning |
|---|
Not supported by firmware. |
1.3.2.4.1. Set device name1.3.2.4.3. Set computer vision model (none, VictoR, LTS, SmartProtectoR)1.3.2.4.4. Set computer vision application1.3.2.4.8. Enable/Disable physical buttons
ID | Name | Description | |||
|---|---|---|---|---|---|
| |||||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
6. Object Transfer Service
ID | Name | Description | |||
|---|---|---|---|---|---|
| |||||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
|
|
| |||
...
Test Documentation
| View file | ||
|---|---|---|
|
...
...
Meeting Information
...
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