34 lines
1.0 KiB
Markdown
34 lines
1.0 KiB
Markdown
|
# Requirements
|
||
|
|
|
||
|
|
## Functional
|
||
|
|
|
||
|
|
### 1. Compliance with language specification
|
||
|
|
|
||
|
|
Functional requirement to comply with the language definition for parsing and execution.
|
||
|
|
|
||
|
|
### 2. Integratable with Unity
|
||
|
|
|
||
|
|
Functional requirement to run in a Unity based execution environment.
|
||
|
|
|
||
|
|
### 3. Unable to access or interfere with systems the program has not been permitted to
|
||
|
|
|
||
|
|
Functional requirement that the system cannot access these systems.
|
||
|
|
|
||
|
|
## Measurable
|
||
|
|
|
||
|
|
### 1. Performant enough to be used in real time applications
|
||
|
|
|
||
|
|
Software must be able to run common programs in a short amount of time.
|
||
|
|
Knowing what common programs ae requires usage data.
|
||
|
|
"Short amount of time" is use dependent, but likely refers to < 1 frame in many cases, so around 5ms is a good idea for an absolute maximum.
|
||
|
|
|
||
|
|
## Qualitative
|
||
|
|
|
||
|
|
### 1. Language should be easy to use for programmers
|
||
|
|
|
||
|
|
Hard to define. Specification can be updated based on feedback from users.
|
||
|
|
|
||
|
|
### 2. Software should be easy to integrate with other projects
|
||
|
|
|
||
|
|
Hard to define. Design can be updated based on user feedback
|