BTW@MDH DSD Course

1
BTW_at_MDHDSD Course Design PresentationSchoo
l 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
3
2012-05-03
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

• 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
• Dont be overbearing

6
2012-05-03
7
Requirements Use Cases
7
2012-05-03
8
Requirements Use Cases (cntd)
9
Project Requirement Priorities
9
2012-05-03
10
Design Graphical User Interface (cntd)
11
GUI Profile page
12
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
12
2012-05-03
13
Design Class Diagram
13
2012-05-03
14
Design Sequence Diagram

• Search advice

14
2012-05-03
15
Design Sequence Diagram

• Administrator

15
2012-05-03
16
Design Database
16
2012-05-03
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, 345
  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?