Life Cycle Objectives CSE 403 Project: Developing a GIS application for a mobile client. Developing a GIS application for a mobile client.

Operational Concepts A mobile client application would utilize Microsoft MapPoint web services to determine the places of interest within a certain range of the location of a client. A mobile client application would utilize Microsoft MapPoint web services to determine the places of interest within a certain range of the location of a client. A user should be able to access and retrieve the driving directions to the specified location and the maps of the specified segment of the directions. A user should be able to access and retrieve the driving directions to the specified location and the maps of the specified segment of the directions. A user should be able to update the database of the places of interest A user should be able to update the database of the places of interest

System Requirements Get request from a user, create a session, and invoke the appropriate web services Get request from a user, create a session, and invoke the appropriate web services Retrieve the information from MapPoint and transfer it to the client application Retrieve the information from MapPoint and transfer it to the client application Client app should display the results in a dynamic format so user would be able to call these results again for more options Client app should display the results in a dynamic format so user would be able to call these results again for more options Sample usage: Sample usage: Traveling range and the current location -> List of places of interest with feedback and rating -> Driving directions to the specified location -> Map of an individual segment from the driving directions Coordinates and name of the place + the feedback/rating -> Update the database according to the provided information

System Architecture Front End Server DBClient1Clinet2 MS MapPoint  Application runs on a mobile client such as smart phone or PDA  Front end server provides web services for the application and a sessionID for each client  Database provides a data support for the front end server  Microsoft MapPoint web services acquire the GIS information and convert them into driving directions, maps, etc. to the front end server

Software architecture Create a.Net application using C# and Microsoft SQL server Create a.Net application using C# and Microsoft SQL server Well defined web services of 2 categories: Well defined web services of 2 categories: Utility servicesUtility services Retrieve information from database Retrieve information from database Utilize MS MapPoint web services Utilize MS MapPoint web services Calculate a route according to coordinatesCalculate a route according to coordinates Retrieve a map with starting point and an end pointRetrieve a map with starting point and an end point Retrieve driving directionsRetrieve driving directions Retrieve map for each segment of directionsRetrieve map for each segment of directions Client-server servicesClient-server services Establish a session Establish a session Retrieve information from a client Retrieve information from a client Deliver a map, a list of directions, or a list of locations to the client Deliver a map, a list of directions, or a list of locations to the client

Lifecycle Plan Split the development and design into five categories: Split the development and design into five categories: Mobile client app interfaceMobile client app interface Communications between the mobile client and the front end serverCommunications between the mobile client and the front end server Database for the places of interest and communication of the database with the front end serverDatabase for the places of interest and communication of the database with the front end server Front end server architecture and web servicesFront end server architecture and web services Interface between a front end sever and the Microsoft MapPoint web servicesInterface between a front end sever and the Microsoft MapPoint web services Distribute the requirements between the team members according to strengths and interests Distribute the requirements between the team members according to strengths and interests Produce a pre-release version every week and test all the parts together Produce a pre-release version every week and test all the parts together Update system requirements and architecture according to the feasibility and deadlines Update system requirements and architecture according to the feasibility and deadlines

Feasibility Seems feasible, but a lot of uncertainties and risks Seems feasible, but a lot of uncertainties and risks MapPoint servicesMapPoint services 7 weeks of project time7 weeks of project time TechnicalityTechnicality Group coordination (other projects and classes)Group coordination (other projects and classes) Further discussion with the group has to be made before deciding the feasibility of the system given the architecture and the deadline Further discussion with the group has to be made before deciding the feasibility of the system given the architecture and the deadline