Contents

19
BTW@MDH DSD Course – Design Presentation School of Innovation, Design and Engineering Malardalen University Nov 20 th , 2008 1 22-05-16

description

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 - PowerPoint PPT Presentation

Transcript of Contents

Page 1: Contents

BTW@MDH

DSD Course – Design Presentation

School of Innovation, Design and Engineering Malardalen University

Nov 20th , 2008

123-04-22

Page 2: Contents

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

223-04-22

Page 3: Contents

Team Members

323-04-22

Name Main Responsibility

Mostafa Pordel

Project Manager

AnandT A

Document Manager

Beaulah Vineela P

Project Tester

Mikael Forsgren

Project Researcher

Abhishek Palod

Development Manager

Riasat Abbas

BTW Designer

Nicholas Cockran

Customer Manager

Finally We Work as a Team

Page 4: Contents

423-04-22

Introduction – Project Status

Project members roles, time schedule

Current Planned Cost 2920$

Current Actual Cost 3500$

Planned Project Cost 70000$

Forecasted Project Cost 56000$

Current hours worked = 286Result = Within budget

Man-hr cost = 20$

Project cost estimate

Page 5: Contents

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 researchPaper surveyWeb based survey Informal/formal interviews

523-04-22

Page 6: Contents

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 Don’t be overbearing

623-04-22

Page 7: Contents

723-04-22

Requirements – Use Cases

Use Case Element

Desc

Use Case ID ….Use Case Name

….

Use Case Description

….

Requirement Reference

….

Primary Actor ….Precondition ….Basic Flow ….Alternate flow ….

Page 8: Contents

823-04-22

Requirements – Use Cases (cntd)

Page 9: Contents

923-04-22

Project Requirement – Priorities

Identity Status Priority Description Source

User

USR-1 I 1 Find route from point A to point B Ctm

USR-2 I 1 Seek advice on the map to travel Ctm

USR-3 I 1 Register and login Ctm

USR-4 I 1 Update personal profile Ctm

USR-5 I 1 Save their filter settings to save time Ctm

USR-6 I 1 Filter advice Ctm

USR-7 I 1 Add advices profile based on their experience Ctm

USR-8 I 2 Add new advice template Ctm

USR-9 I 2 Add comments in web log of a location in map Ctm

USR10 I 2 Refute or approve previous comments Ctm

Manager of BTW

BTWM-1 I 1 Manage conflicts Ctm

BTWM-2 I 1 Manage comments Ctm

BTWM-3 I 2 Set effects of dynamic features Ctm

System administrator

SADM I 1 Manage managers Sys

Page 10: Contents

Design – Graphical User Interface (cntd)

1023-04-22

Page 11: Contents

GUI – Profile page

Page 12: Contents

1223-04-22

Design – High Level Architecture

Presentation Layer Presentation Layer

Business Layer Business Layer

Data servicesData servicesGoogle Maps APIGoogle Maps API

With this model

ChallengesPHP limitationsGoogle DependencyServer side limitations

BenefitsLayering and OOP BenefitsLocal designRich Google APIsFast PHP DevelopmentDBDB

Use Generic Type for Advices

Use Generic Type for Advices

Page 13: Contents

1323-04-22

Design – Class Diagram

Page 14: Contents

1423-04-22

Design – Sequence Diagram

Search adviceTraveller Login Maps Google API BTW Engine DB

1 : Login()

2 : Access Main Page

3 : Search route and filter advice()

4 : select the route()

5 : show the map

6 : Fetch advice()

7 : Fetch the advice()

8 : List of advice

9 : Add the flags()

10 : return maps

Page 15: Contents

1523-04-22

Design – Sequence Diagram

AdministratorAdministrator Maps Advice Google API DB

1 : Search the conflicts()

2 : search conflicts()

3 : search()

4 : search conflicting route()

5 : List of conflicts

6 : Visualize of conflicts()

7 : Add the flags()

8 : Show the map9 : show the update map

Page 16: Contents

1623-04-22

Design – Database

Page 17: Contents

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

1723-04-22

Page 18: Contents

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

1823-04-22

Page 19: Contents

Thank you&

Any Question?