Requirements: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{| border="1" cellpadding="5" cellspacing="0" align="right" width="40%" | {| border="1" cellpadding="5" cellspacing="0" align="right" width="40%" | ||
|+ '''Quick Links''' | |+ '''Quick Links''' | ||
|- | |- | ||
! | ! style="background: #ffdead;" | Project Trajectory | ||
! colspan=" | ! colspan="3" style="background: #ffdead;" | Project Pages | ||
|- | |- | ||
| [[PRE_Groep1| Home]] | | [[PRE_Groep1| Home]] | ||
| [[Problem Definition]] | | [[Problem Definition]] | ||
| [[Sliding Doors]] | | [[Sliding Doors]] | ||
| | |||
|- | |- | ||
| [[Planning|Planning and Milestones]] | | [[Planning|Planning and Milestones]] | ||
| [[Background Research]] | | [[Background Research]] | ||
| [[Chimney]] | | [[Chimney]] | ||
| | |||
|- | |- | ||
| [[Meetings]] | | [[Meetings]] | ||
| [[Requirements]] | | [[Requirements]] | ||
| [[Chimney to Cubby]] | | [[Chimney to Cubby]] | ||
| | |||
|- | |||
| [[Design Methodology| Design Method(s)]] | |||
| [[Brainstorm]] | |||
| [[Cubby to Person]] | |||
| | |||
|- | |- | ||
|style="border-bottom: 3px solid grey;" | [[Personal Logs]] | |style="border-bottom: 3px solid grey;" | [[Personal Logs]] | ||
|style="border-bottom: 3px solid grey;" | [[Concepts Chosen]] | |||
|style="border-bottom: 3px solid grey;" | Software | |||
|style="border-bottom: 3px solid grey;" | | |style="border-bottom: 3px solid grey;" | | ||
|} | |} | ||
=Functional Requirements= | =Functional Requirements= | ||
Revision as of 08:21, 24 September 2014
| Project Trajectory | Project Pages | ||
|---|---|---|---|
| Home | Problem Definition | Sliding Doors | |
| Planning and Milestones | Background Research | Chimney | |
| Meetings | Requirements | Chimney to Cubby | |
| Design Method(s) | Brainstorm | Cubby to Person | |
| Personal Logs | Concepts Chosen | Software | |
Functional Requirements
- Accept/Retrieve package from drone &/or delivery man
- Have holding space for package(s)
- Display address or apartment (somehow)
- Be robust - withstand damage, break ins etc.
- Report status (full, empty, malfunction)
Process Requirements
there must be a guide on how to install the system
there must be a short manual on how to use the system, that can be hung next to the system.
help must be available all days between 9.00 and 18.00
External Requirements
Drones must be capable of moving to an exact location in x, y and z direction.
Product Requirements
- The user must be able to use the system immediately without any problem by following indicated steps.
- The system must be able to receive and handle a package within a minute, so a possible other drone waiting to deliver does not have to wait too long. This waiting costs fuel and time that could be used in other deliveries.
- The system should at all times only open the locker with the package for which the right code has been presented.
- The system should be able to open more than one locker if a shipment includes more than one package.
- The system should open the right locker(s) within ten seconds after verifying the code.
- The system is allowed to be broken twice a year. It should then be repaired within 24 hours of the malfunctioning being reported.
- The user should feel their package is safe in the system.
- The user should feel safe when using the system.
- The system should be resistant to violent break-ins.
Additional Considerations &/or Constraints
5lb payload (package); dimensions - ?
sUAS (amazon drone) will have a maximum weight of less than 55 pounds;
Amazon prime air