Bachelor of Software Engineering

1. Bachelor of Software Engineering Final Project Project Title : CyberGIS Project Members W.M.D Jeewantha M.S.R Perera D.S Kulasuriya

2. Contents • Introduction. • Design & Development. • Testing. • Challenges Faced. • Lessons Learned. • Future Works. • Conclusion. • References.

3. Introduction Motivation • Our vision, “make use of existing GIS data providers and expand that technology into new levels, that the society can make more use of it in their domains.” • Our mission, “develop a GIS based solution to a simple map viewer to a complex geographic related analysis and decision support system.”

4. Introduction Problem Definition • GIS (Geographic Information Systems) capture geographically distributed spatial data and temporal data for visualizing, analyzing and decision marking. • Many domains are geographically distributed and greatly beneficial from GIS. examples :– • Road development and maintenance sector. • Transportation and logistics sector. • Police, Security and military sector. • Emergency response and rescue sector.

5. Introduction Problem Definition cont’d… • There are GIS Systems either that required high GIS and mapping knowledge which bit complex (ESRI ArcGIS) or very simple with few functionalities (Google Map). • Very Complex GIS Systems avoid the wide and general use by high costs, requirement of GIS professionals and less usability. • Very simple GIS Systems do the same thing by not providing authorized and secure data access, less customizability and no reporting and analysis features.

6. Introduction Solution Purposed • A Web based system that users of this system can tag their geographically distributed domain entities on a map, customize these entity details and, store and share them only among other required and authorized parties within the domain. • The CyberGIS system with capabilities as mapping entities, manipulating entity data, mobile operative command, reporting and analysis while ensuring customizability, usability, security and performance.

7. Introduction Solution Purposed cont’d… • Web based system. • Mobile application module for operatives command. • GPS tracking via mobile. • Use Google maps as map data provider. • Private data domains. • Customizable domain maps. • Map data store, visualize, manipulate, analysis.

8. Introduction Solution Purposed cont’d…

9. Design & Development Design Challenge(Problem) • Is to simply provide a GIS application that is customizable by the business users according to their business needs. • Arising Challenges : 1. Finding a suitable & reliable GIS Provider from available GIS Providers & integrating it to the CyberGIS in a customizable manner by the end users. 3. Find a methodology to Implementing a customizable Mapping solution that will allow the user to customize according to his own domain by adding his own icons/images etc.

10. General System Architecture

11. CyberGIS GUI Module Architecture

12. CyberGIS Service Module Architecture

13. CyberGIS Mobile Client Operational Flow

14. Functional Specifications • Business Requirements • The major Business Requirements Found for the CyberGIS includes. - Needs of the businesses to provide a customized GIS Based Services to business users that are customizable to suit their own domain. - Needs of the businesses to keep track & streamline their delivery systems in order to provide the best services to the customers. - Needs of the bussines to Monitor their customer locations based on the customer delivery statistics.

15. Functional Specifications • Operations Requirements • The System should be able to operate with optimum performance in internet bandwidth ranging from dialup (52kbps) to ADSL bandwidth (512kbps-3Mbps) & above. • The system should be able to render the content effortlessly to various end user devices as personal computers to handheld smart phone devices.

16. Functional Specifications • System Requirements • The system requirement s on the deployment (vendor) site should consist of a cluster of web servers running Java EE Edition & Tomcat Application Server. • Each server deployed in the cluster should be at least equipped with the following basic hardware configurations. - Memory 4GB. • 500GB HDD. • Ethernet Network Adapters.

17. Objectives of Testing Testing Specification • The primary objective of testing is to assure that the system meets the full requirements, including non-functional requirements and satisfies the use case scenarios and maintain the quality of the product. At the end of the project development cycle, the user should find that the project has met or exceeded all of their expectations as detailed in the requirements. • The secondary objective of testing the system will be to identify and expose all issues and associated risks, communicate all known issues to the project team, and ensure that all issues are addressed in an appropriate matter before release.

18. Testing Specification Testing Methodology • Unit Testing : Test each and every component for it’s desired functionality. • System Testing : Test the overall integrated system and verify that it meets the requirements. • Regression Testing : Test all units to check the integrity after a bug fix. • Performance Testing : Test the system response time with heavy stress and volumes. • Compatibility Testing : Test the browser Compatibilities of the System. • Security Testing : Test the access control strategies and data security.

19. Testing Specification Test Results • Unit Test cases are executed manually for GUI modules and JUnit used for web service module. • Test cases are documented in Test Case Document alone with the Test Results. • 85% of the tests are succeeded and 15% of bugs detected during the testing phase. • According to the bug severity level(exempt minor), 97% immediate bug fixes were done. • Test deliverables after successful completion are defect free software with documents and test result report. • Test documentations - Test plan - Test cases and Test case review - Test Result Report

20. Challenges Faced • Technological limitation can occur due to limited resource allocation. • Less functionality due to the use of third party open source and free softwaredue to licensing issues. • Limited time in the schedule and team member’s other activities. • No proper WYSWYG IDEs JSF developments. • High functionality deprecation of Primeface version updates and less help documentation.

21. Lessons Learned • We need to perform proper technology analysis and available help documentation before choosing any 3rd party APIs libraries. • Choosing efficient and user friendly development IDEs prior to select the development language. • Proper time estimation model for planning project activities including research time for new technologies.

22. Future Works 1. CyberGIS GUI Module • Marker Proximity Ruler and Alerter :- "Ruler" feature CyberGIS main console users will be able to measure the distance to each marker (including mobile markers) from a specified central origin point. "Alerter" feature CyberGIS main console users will be able to view the details of markers, within a specified proximity circle. • Automatic Real Time Operative Tracking :- Operative tracking will be fully automated and updated locations will be refreshed on the CyberGIS main console map in a specified time intervals. • Hardware Sensor Based Real Time Telemetry :- Gather various data required by domain users through hardware sensors, attached to CyberGIS Mobile component. So the CyberGIS GUI module will include a dashboard component in order to support this feature.

23. Future Works 2. CyberGIS Mobile Component • Porting the J2ME client software to newly available high end mobile phone operating systems like: Android & iPhone. • Location Data acquisition via connected hardware sensors or via a mobile operator cell information to send to CyberGIS GUI Module live monitoring services.

24. Future Works 3. CyberGIS Service Module • Code optimization to reduce the resources usage by the application during the execution. • More code level validations can be implemented to provide additional security to the system. • SSL Support for secure data communication.

25. Conclusion • we would like to believe the CyberGIS is a concept rather than a system that will grow into higher levels that will help potential geographically distributed domain to store, track and coordinate their distributed entities and facts. Also this concept will assist decision making and planning by providing reporting and analysis capabilities

26. References Google Maps API http://code.google.com/apis/maps/index.html ESRI ArcGIS http://www.esri.com/software/arcgis/index.html PrimeFaces http://www.primefaces.org Wikipedia http://www.wikipedia.org

27. Thank You !.