1. Geographic Presentation Eric Zmyslowski-Manager Manan Shah-Programmer Shankar Ramachandran-Architect Jing Chen-Quality Assurance Steve Abraham-Technical Writer

2. Role and Approach Responsible for the dynamic behavior of the Map which includes synchronization between events on the GUI and those on the Map,graphical representation of query results Used the OMT approach: Analysis,Design, Implementation. Problem: It took us several weeks to find the role of ‘GP’. This was primarily due to poor communication between teams.

3. Analysis We modelled the dynamic behavior of three objects to characterize the map behavior:Clickable Icon-Buildings, Non-Clickable Icon-Road Segments and Parking Lots, Map Status. Problems: Inexperience with OMT approach. Poor Communication between GP & QP led to a poor Analysis Document.

4. On the Road to Design Lengthy discussions among team members led to the integration of GP and QP (responsible for the GUI) into a common module called Controller. This addressed the synchronization issue in a novel way, and eventually led to an easier implementation. Problems:No formal syntax for pseudo-code, led to inconsistency in Design Document.

5. Implementation A good Software Engineering practice: Transition from Design to Implementation should be very smooth. The above practice was well carried out in our case. Problems: Insufficient time for testing. Lack of experience with Java.

6. Summary Separation of modules is important in the analysis stage to identify specific roles, considering the magnitude of the project. Analysis to Design resulted in merging of functionality of modules. This happens during Software Engineering. Good group coordination results in effective implementations. All project members need to have a complete understanding of the Requirements before proceeding to Design.

7. Summary (Contd.) Roles among team members overlapped. Group presentations before each deliverable would prove helpful and promote more understanding among team members. Change in role of team and direction through course of project: internal and external. Deviation Requirements Gathering Analysis to Design Design to Implementation