1 / 19

Contents

BTW@MDH DSD Course – Design Presentation School of Innovation, Design and Engineering Malardalen University Nov 20 th , 2008. Contents. Introduction Team Members Project Status Requirements Customer Interaction Use Case Requirement Prioritization Design Graphical User Interface

juan
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 – Design PresentationSchool of Innovation, Design and Engineering Malardalen UniversityNov 20th , 2008

  2. Contents • Introduction • Team Members • Project Status • Requirements • Customer Interaction • Use Case • Requirement Prioritization • Design • Graphical User Interface • High Level Architecture • Class Diagram • Sequence Diagram • Database • Implementation • Activities

  3. Team Members Finally We Work as a Team 2014-08-16 3

  4. Introduction – Project Status • Project members roles, time schedule • Project cost estimate Current hours worked = 286 Result = Within budget Man-hr cost = 20$

  5. Requirements – Customer Interaction • What does the customer want? • No project can be properly developed for an audience without knowing what the audience wants. • Need to do field research • Paper survey • Web based survey • Informal/formal interviews

  6. Requirements – Customer Interaction 2014-08-16 • There are a number of things that need to be considered when developing a customer survey • Simplicity • Brevity • How to maximise the information gathered • Web survey • Targeted emails • High quality appearance • Paper survey • Present yourself • Be willing to answer questions • Don’t be overbearing 6

  7. Requirements – Use Cases 2014-08-16 7

  8. Requirements – Use Cases (cntd)

  9. Project Requirement – Priorities 2014-08-16 9

  10. Design – Graphical User Interface (cntd)

  11. GUI – Profile page

  12. Presentation Layer Business Layer Google MapsAPI Data services Design – High Level Architecture • With this model • Challenges • PHP limitations • Google Dependency • Server side limitations • Benefits • Layering and OOP Benefits • Local design • Rich Google APIs • Fast PHP Development Use Generic Type for Advices DB 2014-08-16 12

  13. Design – Class Diagram 2014-08-16 13

  14. Search advice Design – Sequence Diagram 2014-08-16 14

  15. Administrator Design – Sequence Diagram 2014-08-16 15

  16. Design – Database 2014-08-16 16

  17. Miscelenious • We Use • JavaScript to • To interact with Google Maps • To interact with customer in client side with HTML help (UIL) • PHP • To implement our business layer (BOL) • To fetch data from database (DAL) • Google Maps API allows us • To create a map inside an html container • To create custom markers on the map that we can use to display our custom advices • To draw an area on the map to warn the user of problematic areas • To create a route between two points • To create custom route directions regarding the time consumption of each step

  18. Activities & Future Plan • Currently on time • High level of communication • Google group activities till 9th Nov, 2008, 3:45 am • 89 messages • 61 topics • 38 documents exchanged (including draft versions) • DSD web site • 6 internal documents • 6 important meetings (MoM) • Steering group , Ivana mostly • Internal evolution • Emerged with 2 design possibilities of advices • Future plan • Just follow project plan

  19. Thank you& Any Question?

More Related