Requirements: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
m (→Functional) |
||
Line 21: | Line 21: | ||
=Functional= | =Functional= | ||
{| border="1" cellpadding="2" | |||
! scope="col" width="200px" | Communal Package Holding System | |||
! scope="col" width="200px" | Package Designation System | |||
|- | |||
| align="center" | (holds packages until people come and collect) || align="center"| (goes to individual boxes of specific people) | |||
|- | |||
| | |||
* Has several compartments for package holding | |||
* Ability to contain/handle multiple packages | |||
** to accept package from drone | |||
** to distinguish package owner | |||
** to place in compartment | |||
** to notify owner package is in compartment x & access code | |||
* Report malfunctions/if its full somehow | |||
* Easy access for maintenance | |||
* Be robust – the program should be so simple it (almost) never crashes or hangs. | |||
* Display Address/Apt no. | |||
|| | |||
* Has separate compartment for each residence | |||
* Ability to handle contain/handle packages | |||
** to accept package from drone | |||
** to distinguish package designation | |||
** to put package in appropriate box | |||
* Report malfunctions/ if its full somehow | |||
* Easy access for maintenance | |||
* Be robust – the program should be so simple it (almost) never crashes or hangs. | |||
* Display Address/Apt no. | |||
|} | |||
=Non-Functional= | =Non-Functional= | ||
Requirements here | Requirements here |
Revision as of 21:55, 14 September 2014
Project Trajectory | Project Pages | |
---|---|---|
Home | Problem Definition | |
Planning and Milestones | Background Research | |
Meetings | Requirements |
Functional
Communal Package Holding System | Package Designation System |
---|---|
(holds packages until people come and collect) | (goes to individual boxes of specific people) |
|
|
Non-Functional
Requirements here