1 / 14

Contents

BTW@MDH DSD Course – Project Status Presentation 2 School of Innovation, Design and Engineering Malardalen University Dec 18 th , 2008. Contents. Introduction Project Status Presentation Team Members Project Status Activity Diagram Tasks Completed Current Tasks Testing Aspect

cerwin
Télécharger la présentation

Contents

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. BTW@MDHDSD Course – Project Status Presentation 2School of Innovation, Design and Engineering Malardalen UniversityDec 18th, 2008

  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

  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

  5. Project Status – Current Tasks Management functionalities Convert prototype implementationto 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.

  8. Statistics – Financial Project Cost at the End of Week: W#50

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

  10. Project Experiences • 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 • 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. 2020-01-02 11

  12. Score Approach • 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 2020-01-02 12

  13. Demo

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

More Related