Popular notations for functional requirements specifications frequently ignore developers' needs, target specific development models, or require translation of requirements into tests for verification; the results can give out-of-sync or downright incompatible artifacts.
Devices have emerged that can be used for functional requirements in high speed optical data processing, filtering, nonlinear optical functions such as all-optical switching - and many other applications.
The design of composite components in the aerospace industry often includes structural discontinuities, such as cutouts, for functional requirements like ventilation, tunnel passage, maintenance and repair.
Punching is an efficient and economical process for producing a hole in structures for functional requirements, repair, maintenance, and so forth.
Use cases are the notation of choice for functional requirements documentation, whereas task models are used as a starting point for user interface design.
Use cases that describe possible interactions involving a system and its environment are increasingly being accepted as effective means for functional requirements elicitation and analysis.
To demonstrate the practicability of an approach that unifies these advanced graph-transformation techniques, we define the abstract syntax of behavior trees (BTs), a graphical specification language for functional requirements.
Most requirements specification tools, e.g., Accent, Nu Thena, SES, Rational, are more suited for functional requirements than for non-functional RAMP requirements [1 5].
For functional requirements this does not occur, since there is a need to specify details for the developing system (Palomares et al. 2013).
