Sawari Hamari

Abhishek Vijayvargia (13111002)Sriram Gopalakrishnan

Group no. 19

Problem

Solution

Name : Search For a TaxiActor : UserTrigger : When user launches application

1) System Displays login screen.2) User provide login details.3) System authenticates user.4) System displays main screen.5) User chooses taxi.

Use Case : Search for a taxi

6) System Displays taxi options.7) User Chooses search for a taxi option..8) System asks user to provide details.9) System displays various matching requests sorted according to relevance.10) User chooses an option.11) System Displays details of that option.12) User can chat with other user ( who is offering ) and join him.

Use Case : Search for a taxi

Use Device Efficiently

Should not continuously query for new messages /request to the server.

Should be updated to get latest notification from other users.

Use server Efficiently Handle only those instances which is sending

request at that time. Send message to multiple users without delay.

Performance Tactics

Resource Demand

Design efficient algorithms Reduce Computational overhead

Resource Management Limit same data entered multiple time. Store less data

Performance Tactics

Reuse resource and result Use asynchronous processing Optimize Repeated Processing Increase Capacity, Put more resources.

Scalability Tactics

Maintain Semantic Coherence Hide Information Restrict Communication paths Maintain Existing Interface

Modifiability Tactics

Use “Cloud”.

But which one to choose ?

Lots of available options Google App Engine Microsoft Azure Amazon EWS

Architectural decisions

Microsoft Windows Azure

Support for Java Free for 30 days-90 days trial. Need to pay even

if we don’t have a single user.

Amazon AWS AWS SDK is available for android for easier use Again not free. Need credit card details.

Architectural decisions

Google App Engine

Support for Java Only pay for resources which is useful. Do load balance automatically. Can check errors in log viewer. Absolutely Free for our need.

Google App engine : Storage : 1GB , Bandwidth : 1 GB

Google Map API- 1000 request/day

Architectural decisions

Robustness Diagram : Searching

LoginScreen Authentication UserData

Searching

MainScreen

TaxiScreen

DisplayResult

Filtering

StoredData ChatScreen

Chatting

Robustness Diagram : Offering

CreateRequestScreen

Searching

StoredDataOffering

Logical View

Process View

Deployment View