Functional Requirements – Mobile Application
Neat & simple design.
Accessible to internal and external stakeholders.
Ability to include YouTube videos.
Ability to include pictures.
Ability to send push notifications
Ability to complete forms
Ability to link to main website and CGS’ social pages
Ability to link to the CGS’ events web page (Register for events, receive event information etc.)
Ability to show upcoming events by months and years
Ability to display live seismic events which is pulled from a CGS database ∙ Ability to display live mining events which is pulled from a CGS database ∙ Ability to display an interactive map of southern Africa indicating earthquakes scaled according to size and color scale to indicate age
Ability to display interactive geological map (1 in a million map) that will deliver: o integration of geoheritage and geo-tourism information such as hiking trails and geosites from around the country with geological data from the million map of South Africa
o deliver topographic information
o The above information must also be available offline as well.
o Display of viewable and downloadable material (e.g., annual reports, projects, etc.)
Ability to view seismic events GPS coordinates
Ability to view seismic events in a list With its coordinates
Ability to switch between map view and list view
Ability to view the exact location, the magnitude and the distance away from you. ∙ Information must be pulled from the CGS seismic network databases ∙ Ability to filter and search for seismic events using area, magnitude, date. ∙ Ability to subscribe to notifications - Alerts and Push notifications. You should choose which earthquakes you wish to receive notifications for.
Ability to share to social media
Ability to report seismic event on a questionnaire - report if you felt something ∙ Ability to display earthquake statistics
Ability to change the view of the application however the viewer wishes. ∙ Ability to display earthquake safety tips awareness
The successful bidder will be required to perform regular security and vulnerability tests on the application and Host environment.
The source code must be prevented from being viewed by external parties. ∙ The website must be configured not to return detailed error information about the website.
Website users must be prevented from gaining access to script and application files. ∙ The web server application must be properly secured as it provides links to back-end systems such as databases, applications and portals.
User identification and authentication: Users will access the content of this website through a web browser by using an anonymous logon. No account or password will be required, as the purpose of this website is to provide access to the public. E-commerce site subscribers will be required to register as users. Administrators, Editors and Publishers with access to the back-end will need to be registered as users. These will be authenticated through the web server. Password implementation must be established according to the CGS policy.