Requirements

As part of the requirement acquisition process, various functional, non-functional, and environmental requirements were developed through discussions with General Dynamics Mission Systems. The following contains a brief overview of these requirements. For a full list of requirements, see the documents page.

Functional Requirements

The following high-level functional requirements are as follows:

• Control of Channel Assignment
• Management of User Accounts
• View Channels Available to Users
• Mix Audio Streams in 3D
• Mute/Unmute channels
• Save/Load Channel Configurations
• Log errors, access, and activity

In addition, the following deliverables are to be provided to General Dynamics:

• A demonstration report of the solution
• All necessary source code
• Design documentation
• Design review material

Performance (Non-Functional) Requirements

The following high-level non-functional requirements are as follows:

• HTTPS Connection Overhead
• Authentication Response Time
• Concurrent User Support
• Concurrent Audio Streams
• Minimized Packet Loss
• Low Latency Transmission
• 3D Audio Processing Latency
• Mute/Unmute Response Time
• Volume Adjustment Latency
• Log Retrieval

Environmental Requirements

The following high-level environmental requirements are as follows:

• HTTPS access
• Use of U.S. Sourced Software
• Zero Trust Architecture
• AWS GovCloud Access
• NIST Compliance
• User-Friendly UI
• Responsive Web Design
• Cross-Platform Compatibility
• $100 AWS Budget
• $2500 Speaker Budget