Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007
Team 2B Determind
- Thomas Hunter
- Cheol-Woo Jung
- Justin Smith
- Nate Wilson
Milestone 3: Design the Location Based Services System
Our project for Spring of '05 is to design a Location Based Service. For Milestone 3 we had to design our entire system as it will be at the completion of M6. This includes the design for the PDA port, Air Graffiti service, and our own system. For our own system we decided to implement a safety service. With this service you can alert others of events or emergencies that are occuring in a certain area. This service is simply an extension of the air graffiti service, as far as the coding end is concerned. We will now discuss the different parts of our M3.
For scenarios we just took everyday situations and told how our system could improve them. We gave them titles and tried to make them somewhat funny and enjoyable to read, while still running through all the pieces of our system. The scenarios were made to be real life situations that most people encounter and how they would use our LBS in that situation. An example Scenario is below:
Lindsay has a meeting with her video game design group and goes to the CRC to meet them. She doesn’t find them so she logs into the system as a new user. She sets her name to Lindsay, inputs an icon, and sets a password. She sets her location to the CRC and states that she is on her PDA. She searches the people in the CRC to find her friends but they are not listed. Lindsay thinks that they may have said COC, so she resets her location to the COC. She searches the people there and finds her friends. She then logs off and goes to the COC for her meeting.
Here we simply tried to account for problems that could arise while using our system. These plans were to be implemented within our SUnit tests.
Responsibilities and Timelines
We decided to try and meet every Monday and Wednesday at 3, because it is about the only time all of us are free. We will meet at other times as seen necessary. We tried to adhere to this schedule as much as possible and get everything done on time (although something usually messes this plan up.) For responsibilities we decided to keep pretty much the same responsibilities throughout so that we don't get mixed up code and work will go faster because people already understand their part of the code. The responsibilities broke down like this:
Tom: backend and "clean up"
Justin: Design, paperwork, and assisting the other 3 members
We implemented a simple interaction on client side. The GUI interacts with the ClientDataStore to get its informations and updates. The Client sends messages across the network to alert or receive updates. The UML we implemented is shown below.
Common Classes UML
This Milestone is very important to the rest of the project. It helped us establish goals and made sure that our group was on the same page. UML should be paid very close attention because a lot of the system is built off of what the UML shows. Scenarios are also a good way to guage what a user will want to do with the system. Extendability is a must! The system is much easier to build and add on to when classes are easily extendable.
Link to this Page
- Cases last edited on 30 July 2011 at 2:33 am by r59h132.res.gatech.edu