1. BTW@MDH DSD Course – Project Status Presentation 2 School of Innovation, Design and Engineering Malardalen University Dec 18 th, 2008 12016-01-22

2. Contents Introduction Project Status Presentation Team Members Project Status Activity Diagram Tasks Completed Current Tasks Testing Aspect Statistics Time Financial Communication Project Experiences Score Approach Demo 22016-01-22

3. 3 Project Status – Activity Diagram Project Status : On Track

4. Project Status – Tasks Completed Add registration functionality Databases changes Add advice and search map Remote development Creation of advice Search route from point A to B Search place Change marker to advice Filter advices Add advice template 42016-01-22

5. Project Status – Current Tasks Management functionalities Convert prototype implementation to real implementation Integration Documentation Score Project and DSD reports

6. Project Status – Testing Aspect Requirement Test Cases System Test Cases

7. Statistics – Time Typically 20-30 hours spent by group members in the project. WeekW45W46W47W48W49W50W51Total Hour Spent 139.5146150116130131In Progre 813

8. Statistics – Financial Project Cost at the End of Week: W#50 Current Planned Cost 21000 $ Current Actual Cost 16260$ Planned Project Cost 38500$ Forecasted Project Cost 29810$

9. Statistics – Communication Posted mails – 180 Meetings (MoMs) – 10 Weekly Reports – 5

10. Project Experiences 102016-01-22 Learning Integration of logic and Google API More learning on AJAX for Google API interaction Challenge Deal with downtime of server in real scenario Team Member leaving the project Missed Members task. Integration of Different Member Code Experience Team work and integration Linux based remote development Need to be positive and motivated

11. Score Approach 112016-01-22 Customer driven product Customer seek information as well as provide Customer acts as administrator Our design help us to acheive the above Market driven product Scalability – Our design does not hard code advices. Maintainability – Zero maintenance as most are user maintained. Requirement analysis Ambiguity – Our approach of website with subjective polling Attitude & opinion – Interview of various customers to draw conclusion. Requirement prioritization – Doc sign off with customer. Changing requirements – Design is the answer.

12. Score Approach 122016-01-22 Problem solving approach Well defined project researcher role Always looked for alternatives  Example : Problem : Development environment setup  Alternatives : Local and remote development  Inspiration : To work in all conditions  Result : Successful local and remote development Industrial problem – Legacy systems No documents and no experienced architect of the system Our approach : Well defined documents  Someone want to install our development environment?  Want to know why we used PHP?  How to interact with Google API?  Requirements in our words

13. 132016-01-22

14. Merry Christmas & Happy New year To All Thank you & Any Questions?