Changes between Version 31 and Version 32 of BluePrint/CAPMobileApp


Ignore:
Timestamp:
01/31/16 14:43:51 (6 years ago)
Author:
Lutz Frommberger
Comment:

updated requirements

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/CAPMobileApp

    v31 v32  
    7676<http://en.wikipedia.org/wiki/Requirements_analysis requirements>
    7777<Identify different types of requirements:>
     78
    7879=== Functional ===
    79  * Simple interface
     80 * Simple interface. Must adhere to the web application interface. At best, it is auto-generated (or semi-auto-generated) from the web templates.
    8081 * step by step input
    8182 * must work without internet connectivity
    82  * alerts are a buffered and automatically sent as soon as the internet connection comes up again
    83  * satisfies a subset of CAP
     83 * drawing a polygon on the map must be easy, seamless and exact. Map should be centered around the current position. Adequate initital zoom level.
     84 * summary at the end to show all the information again, must be explicitly confirmed by the user.
     85 * Login only necessary at initial use. (to be discussed)
     86
     87
     88==== Optional ===
     89 * alerts are a buffered and automatically sent as soon as the internet connection comes up again ''(Currently I do not think this is mandatory for the usecase. If the issuer can not create the alert due to lacking internet connectivity, he/she should take steps to make the alert go out other than waiting for internet connectivity. Fallback to SMS would be an option (either automatically parsed by the server or just to somebody else).
     90
     91
    8492=== Non-functional ===
    8593http://en.wikipedia.org/wiki/Non-functional_requirements
    8694=== Interoperability ===
    8795=== Standards ===
    88  * Results are sent out in CAP
     96 * Native communication with the Sahana data types. Compliance to CAP
     97
    8998=== System Constraints ===
    9099