Changes between Version 31 and Version 32 of BluePrint/CAPMobileApp

Timestamp:

01/31/16 14:43:51 (9 years ago)

Author:

Lutz Frommberger

Comment:

updated requirements

BluePrint/CAPMobileApp

@@ -76 +76 @@
 <http://en.wikipedia.org/wiki/Requirements_analysis requirements>
 <Identify different types of requirements:>
+
 === Functional ===
- * Simple interface
+ * Simple interface. Must adhere to the web application interface. At best, it is auto-generated (or semi-auto-generated) from the web templates.
  * step by step input
  * must work without internet connectivity
- * alerts are a buffered and automatically sent as soon as the internet connection comes up again
- * satisfies a subset of CAP
+ * drawing a polygon on the map must be easy, seamless and exact. Map should be centered around the current position. Adequate initital zoom level.
+ * summary at the end to show all the information again, must be explicitly confirmed by the user.
+ * Login only necessary at initial use. (to be discussed)
+
+
+==== Optional ===
+ * 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).
+
+
 === Non-functional ===
 http://en.wikipedia.org/wiki/Non-functional_requirements
 === Interoperability ===
 === Standards ===
- * Results are sent out in CAP
+ * Native communication with the Sahana data types. Compliance to CAP
+
 === System Constraints ===