Deliverable D4.3 Mobile Application Editor Pfennigschmidt, S. (FF) Contributors Burkard, S., Fischer, F. (HTW), Fotouhi Tehrani, P., Fuchs-Kittowski, F., Hellriegel J. (FF), Himberger, S. (HTW), Koukoulas, N. (SPH), Papadakis, N. (SPH), Pfennigschmidt, S., Restel, H., Rösler, M. (FF) Version 1.0 Date 24.02.2017 Distribution RESTRICTED Ref. Ares(2017)1742441 - 31/03/2017
11
Embed
City.Risks D4.3 Mobile-Appproject.cityrisks.eu/wp-content/uploads/2017/08/D4.3.pdf · Mobile App. The mobile app represents one interface for citizens to communicate with the City.Risks
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
This report is a short description accompanying the City.Risks Mobile App(deliverable D4.3). It describes the integration of the app into the overallinfrastructure of the City.Risks system, its functionality and basic implementationstructure.
The following figure represents a general overview of technical architecture ofCity.Risksandshowstheintegrationofthemobileappwithintheoverallsystem.
Fig.1:SystemarchitectureofCity.Risks.
MobileApp. Themobileapp representsone interface for citizens tocommunicatewith the City.Risks infrastructure and access its functionality. It connects to thesystem using the services of the App Backend,which in turn communicate to theCorePlatformand theRiskManagementandResponseService (RMRS) to forwardandreceiveinformation.
Core Platform. The Core Platform is a set of services, including a database, amessagebroker,andsenderand loggingcomponents, thatarecentral toCity.Risksfunctionality.
RiskManagementandResponseService(RMRS).TheRMRSaddsreactiveaswellaspro-activefunctionalitiestotheCity.Risksframework.Thosefunctionalities include,for instance, (semi-)automatic real-time analysis of incoming reports (frommobileappusers,Webapplicationusers,orexternalsources)orcommunityrequests,basedonsemanticalandspatio-temporalanalyticsmethods.
Operation Centre. The Operation Centre represents a set of management andoperational tools for public authorities or private companies operating City.Risks.These tools and interfaces let agents and their supervisors handle incidents incooperation with the decision support provided by RMRS. Other componentssupportsimulationsandstatisticalanalysisofsecurityandriskrelateddata.
The detailed app requirements that have been identified are documented indeliverableD2.4. The general concept of the app has been detailed in deliverableD2.5.
Mobileapp.Themobileappismodularizedalongenduserfunctionalityorservices.For all the functions, necessary to support such a service (or use case) a set ofmodules and interfaces has been developed that implement the service on themobiledeviceandontheserverside.Thegoalwastohavetheservicemodulesasindependentfromeachotheraspossiblewhileallowingbasicmodulestobesharedbyothers.
Inso far, theCity.Risksmobileapprepresentsone incarnationofsuchanappthatincorporatesall services. Themodule approach, however, allows to create variousappsthatcanofferdifferentcombinationsofservicestoitsusers.
The following sections describe technical details of the platforms used to developanddeploycomponentsaswellaslist internalandexternaldependenciesbetweenthedifferentmodules.
I.1 DevelopmentEnvironment
MobileApp. ThemobileApphasbeendevelopedas anativeapp for theAndroidsmartphone platform using Android Studio 2.2.3 and the latest Androiddevelopmenttools.
App backend. The App backend has been implemented as a set of HTTP RESTservicesbasedonnode.js(nodejs.org).
I.2 DeploymentEnvironment
MobileApp.Inordertosupportthetheftdetectionfunctionality,whichisbasedonBluetoothLE technology, themobileapp requiresanAndroidSmartphone runningAndroid 5.0 Lollipop (API Level 21) or higher. For all other functions a minimalversionofAndroid4.4KitKatisrequired.