Target release | Release name or number |
---|
Epic | Link to related Jira epic or feature |
---|
Document status | |
---|
Document owner | Joe Pearson |
---|
Designer | Lead designer |
---|
Developers | Lead developer |
---|
QA | Lead tester |
---|
|
Goal
- Create the components needed for an Edge Device (Scenario Two) to be placed and easily connected to an Edge Node (Scenario One A), configured with a Configurator (Scenario One B) to define the device purpose and attributes, and to begin to send data northbound to be collected and analyzed (Scenario Ten) on an Edge Gateway (Scenario One C).
Background and strategic fit
For the end user, this should be a simple process with minimal wiring, configuration, and no development expertise. For the device manufacturer and system integrator, they should be able to easily add the code and configuration needed to use their desired hardware and software solutions. All standards, specifications, and examples should be readily available, and licenses will allow any IP to be used in creating and deploying solutions based on the reference architecture.
Assumptions
- Edge Device will have a QR code or similar technique that will allow a person to scan the device upon placement, associate the device with a plant or plot, specify the purpose of the device, and begin to immediately collect data.
Requirements
# | Title | User Story | Importance | Notes |
---|
1 | Short identifier for the story | Describe the user and what they are trying to achieve | Must Have | - Additional considerations or noteworthy references (links, issues)
|
2 |
|
|
|
|
User interaction and design
Include any mockups, diagrams or visual designs relating to these requirements.
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|
(e.g. How we make users more aware of this feature?) | Communicate the decision reached |
Not Doing
- List the features discussed which are out of scope or might be revisited in a later release.