Transcript Selected Topics of Software Engineering - Distributed

BTW@MDH
DSD Course – Design Presentation
School of Innovation, Design and Engineering
Malardalen University
Nov 20th , 2008
2016-04-02
1
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
2016-04-02
2
Team Members
Name
Main Responsibility
Mostafa
Pordel
Project Manager
Anand
TA
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
2016-04-02
3
Introduction – Project Status
 Project members roles, time schedule
 Project cost estimate
Current Planned Cost
2920$
Current Actual Cost
3500$
Planned Project Cost
70000$
Forecasted Project Cost
56000$
2016-04-02
Current hours worked = 286
Result = Within budget
Man-hr cost = 20$
4
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
2016-04-02
5
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
2016-04-02
6
Requirements – Use Cases
2016-04-02
Use Case
Element
Desc
Use Case ID
….
Use Case
Name
….
Use Case
Description
….
Requirement
Reference
….
Primary Actor
….
Precondition
….
Basic Flow
….
Alternate flow
….
7
Requirements – Use Cases (cntd)
2016-04-02
8
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
2016-04-02
I
1
Manage managers
Sys
9
Design – Graphical User Interface (cntd)
2016-04-02
10
GUI – Profile page
Design – High Level Architecture
Presentation Layer
Use Generic Type
for Advices
Business Layer
With this model
Challenges
Google Maps API
Data services
DB
2016-04-02
PHP limitations
Google Dependency
Server side limitations
Benefits
Layering and OOP Benefits
Local design
Rich Google APIs
Fast PHP Development
12
Design – Class Diagram
2016-04-02
13
Design – Sequence Diagram
 Search advice
Maps
Login
Traveller
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
2016-04-02
14
Design – Sequence Diagram
 Administrator
Administrator
Maps
Google API
Advice
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 map
9 : show the update map
2016-04-02
15
Design – Database
2016-04-02
16
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
2016-04-02
17
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
2016-04-02
18
Thank you
&
Any Question?