The supporting software, libraries, and virtual layer that sit between the app and the operating system to make the program run.
Table of Contents
FUNCTIONAL ANALYSIS
Further Refined Use Case Model
UC-1: Function Feature
IF Describing via EARS Function Requirements Format:
- Ubiquitous (Always Active): The shall (e.g., The mobile phone shall have a mass of less than 150 grams
- State-Driven (Active During a State): While , the shall (e.g., While the vehicle is in reverse, the system shall display the rear camera feed)
- Event-Driven (Triggered by an Event): When , the shall (e.g., When the user presses the power button, the device shall turn on)
- Optional Features: Where , the shall (e.g., Where the navigation package is installed, the system shall display the map)
- Unwanted Behavior: If , then the shall (e.g., If the password is entered incorrectly three times, then the system shall lock the account)
NOTES
References
| Reference |
Description |
| EventTarget |
Represents how webpages communicate events and provides mechanism for the webpage to register for them. |
| Location |
Provides a webpage with basic information of their network location. |
| Navigator |
Attaches a bunch of different APIs that require detection as they may not be available in different web browsers. |