Features and Requirements

Functional Requirements

• API must take in preset audio input options it is expecting
• API must connect to, activate, and record audio from microphone
• API must connect to speech-to-text database (either internal or external)
• API must translate recorded audio into text
• API must compare translated audio input to input options and record if it is included in the list, and which one if it is
• API must return comparison results
• API must be compatible with any suitable AAC device

Non-Functional Requirements

• API should respond quickly to inputs so users don’t feel lag
• API should be flexible enough to support new AAC devices in the future
• API should be able to handle multiple developer requests at once
• API should be able to process concurrent audio inputs
• API should give feedback so users know their action was received
• API should have flexibility for future use-cases
• API should keep data secure