FCR ARB PRESENTATION · PDF file · 2015-10-14FCR ARB PRESENTATION Team 5: Tour...

FCR ARB PRESENTATION

Team 5: Tour Conductor App

1

Team Strengths

Operational Technical

• Members are very friendly and

collaborate well together.

• Eager to learn new ideas/skills to

help the project.

• Put in effort to meet frequently to

work on project.

• Members open to each others’

opinions.

• Great sense of responsibility in

each member.

• Variety of technical backgrounds

• All M.S. Computer Science students

with experience in programming.

• Some members with industry

experience.

2

Team Weaknesses


• Occasional miscommunication

about meeting times or

meeting goals.

• Client is in different

geographical location and

time zone.

• Few documentation about

project development so far.

• Team is only working on

project for one semester.

• Some inexperience with

technologies to be used in

project.

• Unfamiliarity with class tools

such as WinBook and Unified

Code Counter.

• Unspecified technical

requirements within project

deadline.

• Version control

3

Operational Mitigation & Technical Solutions


• Utilize document

collaboration tools in

addition to chat messaging

tools.

• Work on collaborative

documentation in each

meeting.

• Plan and schedule weekly

project goals and

requirement completions.

• Ask for best practices from

experienced Android app

developer (ex. Classmate,

Professor)

• Make requirements

finalization and alignment a

priority in client meetings.

• Put code under version

control to boost collaboration

efforts.

4

OPERATIONAL CONCEPT

DESCRIPTION

5

System Purpose

Current Situation: There is no mobile application on the market that allow users or tourists to find specific and convenient routes that cover certain areas based on the user’s Location.

Goals:

- Make it convenient for users to tour around any area

- Help users find specific location in a certain area

- Help the Cities(or other areas) to promote any touring route

6

Business Vision

Allow tour creators to construct tours of areas on a

website, and allow tour takers to explore pre-created

tours, that cover areas close to their specific locations,

on their mobiles, with access to sufficient information

about all stops in a certain tour.

7

Program Model

Assumptions: People desire information of an area before they tour around the area

Stakeholders (Who?) Initiatives

(What?)

Value Propositions

(Why?)

Beneficiaries

(For Whom?)

- Tour creator

- Tour taker

- Developers

- Maintainers

- Client

- Design and

develop the new

system

- Market the system

- Create proper

training for admin

to create tours

- Make user manual

documentary

- Make it convenient

for users to tour

around any area

- Help users find

specific location in

a certain area

- Help the Cities(or

other areas) to

promote any

touring route

- Tour creator

- Tour taker

Cost Benefits

- Development costs

- Maintenance costs

- Web hosting, domain name, and services(e.g

google APIs)

- Increase number of tour creators

- Increase number of tour takers

- Increase Number of tourists at significant

locations

8

Benefit Chain Diagram9

System Boundary and Environment10

System Objectives

Operational Capability Goals:

- OC-1: Tour Creator Sign-up: Tour Creators are capable of creating accounts on Tour Conductor’s Website.

- OC-2: Tour Creation: Tour Creators are capable of creating tours of specific areas that they wish to promote.

- OC-3: Client Tour Allowance: Client is capable of allowing, as well as dismissing, tours created by Tour Creators.

- OC-4: Location-Based Touring: Tour Takers are capable of accessing and taking all tours of areas near their location.

- OC-5: Tag-based Location Search: Tour Takers are capable of searching tours of nearby areas according to specific tags

describing the desired areas

11

System Objectives

Organization Goals:

OG-1: Make it convenient for users to tour around any area

OG-2: Help users find specific location in a certain area

OG-3: Help the Cities(or other areas) to promote any touring

route

12

Constraints

CO-1: Android as an Operating System: The

mobile application must work on Android

CO-2: Local Host as Web Server: School and client

are not providing web server.

13

WIN-WIN CONDITIONS

14

Capability Requirements

ID Requirement Win

Condition(s)

Priority

CR 1 As a tour taker, I can choose from a list of

near-by tours and select a desired tour.

WC_3689 10

CR 2 As a tour creator, I can upload the url of the

pic, and other descriptive information about

the stops in my tours.

WC_3683 10

CR 3 As a tour taker, I can click on a stop on the

map that's visible, so that, I can view all the

uploaded information about that stop.

WC_3688 10

CR 4 As an owner, I can authorize tour creator, so

that, they can access the website and upload

tour content

WC_3684 5

CR 5 As a tour creator, I can edit and delete any

tours that I created before.

WC_3690 5

CR 6 As a owner, I can delete any uploaded tour

if it seems to be an irrelevant upload.

WC_3685 3

15

Project Requirements

ID Requirement Win Condition(s)

PR 1 A PHP server is used which can connect to the

database and retrieve information requested by the

android.

WC_3689

PR 2 HTML 5, CSS and Bootstrap will be used to develop

the website.

WC_3683

PR 3 Google Maps API will be used to show markers on

each stop in a tour which will contain details about that

stop.

WC_3688

PR 4 Google Maps API will be used to show markers on

each stop in a tour which will contain details about that

stop.

WC_3689

PR 5 Tour creator has to contact the owner to request

authorization.

WC_3684

16

ARCHITECTURE

17

System Context18

Artifact and Information19

Use-case Diagram20

DB Schema21

Architecture22

PROTOTYPE

23

Risks we mitigated via our first prototype

Get acquainted with android.

Get acquainted with Google Map APIs.

Integrated Google Map APIs to our application.

Displaying the data obtained form the server

24

What we have achieved through this prototype

Create database schema and tables and populate the tables with valid data.

Have the server receive a request and search the database based on search string.

Run asynchronous tasks to retrieve JSON data from the server and decode the JSON data.

Display the information of a particular location retrieved from the database when its marker is pressed.

25

Work flow on the Android application

Tour

taker

enters

a

search

string

Server

retrieves

all tours

based on

search

string

Applicatio

n displays

all the

tours sent

by the

server

Applicatio

n displays

a map with

all the

stops in

that tour

User clicks

on a tour Application

shows the

content

associated

with that

stop

Tour

taker

navigat

es using

the

map

26

Work Flow on the website

Tour

creator

logs in

Create

or edit

tour

Login

successf

ul

Enter

tour

name

Enter

number

of

stops

Server

verifies if

tour name

is unique Enter

details

for each

stop

Create

tour on

databa

se

27

GUI Prototype for website28

GUI Prototype for website29

LIFE CYCLE PLAN

30

Life Cycle Plan

Controlling and monitoring the team in each phase

and iteration of the project’s life cycle

Assumptions:

The duration of the project is 12 weeks in fall 2015.

The development team consist of 7 members listed

before will work on the project during the fall semester.

The project is expected to be worked later on by

another team to continue.

31

Foundation Phase

Duration: 10/11/15-10/20/15

Concept: Assess Project Status, Plan and Manage

Project, Manage Project Quality, Prototyping,

Develop Software Architecture.

Deliverables: Development Commitment Package

Milestone: Development Commitment Review

Strategy: One Incremental Commitment Cycle, Risk

assessment analysis.

32

Foundation Phase33

Responsibilities

Name Role

Ankush H Prasad System Architect , Project Manager,

Prototyper/Builder

Ajay Kumar G C Project Manager, Life Cycle Planner

Prototyper/Builder.

Aadithya B K Requirements Engineer, Prototyper/Builder.

Andrew Han IIV & V, Quality Focal Point, Prototyper/Builder.

Joseph Mouawad Operations Concept Engineer, Prototyper/Builder.

Manas Yadav Feasibility Analyst, Prototyper/Builder.

Rohith Ravindra Life Cycle Planner, Prototyper/Builder.

34

Project Scale Factors

Scale Driver Value Rationale

PREC High (2.48) The team has a thorough understanding of the app objectives. There is scope for

concurrent development.

FLEX High

(2.03)

There is a basic need for software conformance with pre-established requirements

and a considerable need for conformance with external interfaces.

RESL Low

(5.65)

The team needs to identify and to resolve the riskiest module. There is some

uncertainty regarding the architecture.

TEAM High

(2.19)

Each member has experience in working with a team and also there is consistency in

stakeholder’s objectives.

PMAT Low

(6.24)

Since this is the first time, most of the team members are working in such an

environment the process maturity level is low.

35

Estimation36

Estimation

8.92 PM is the estimate.

12Hrs/week/person * 7person * 4weeks = 336

Hrs/PM

( 152Hrs/PM * 8.92PM ) / 336 Hrs/PM = 4.035

PM

As stated above the team has 12 weeks and the

estimate comes up to about 16 weeks. The project

lacks around 4 weeks of time to complete the

agreed requirements.

37

FEASIBILITY EVIDENCE

DESCRIPTION

38

NDI/NCS Candidates

NDI/NCS Usage

Google Maps, Apple Maps, Bing Maps Creating and displaying Map for tours

MySQL, Mongodb Database Management System

Amazon web server, Go daddy Virtual

Private server, Local Server.

Web server to host the database and

website

CSS Framework CSS API to develop the user interface of

the web end.

Android Studio, Eclipse Developing the Android Application.

39

NDI/NCS Comparison: Maps API

Google Maps Apple Maps Bing Maps

The Most Widely used

Maps Software by Google

Not as Widely used as

Google Maps, nevertheless

has many users due to iOS

Mapping software by

Microsoft, default app for

Windows Phone

Highly Accurate and error

free mapping

Has been as being highly

inaccurate.

Accurate mapping on web

end.

Easy to find tutorials on the

web for implementation

Not nearly as easy to find

tutorials as Google maps

Not as easy to find tutorials

for Bing Maps

Cost: Free upto 10,000

calls a day after that

$0.50 per 1000 calls

No limit. Cost: Free up to 10000

calls per day

200$ for 25,000

calls/daily

per month.

40

NDI/NCS Comparison: DBMS

MySQL Mongodb

The Worlds most popular database

management system

Database Mangement System by

MongoDB using dynamic schemas

Has support for complex multi row

transactions

No support for complex multi row

transactions.

Very mature and resilient technology Not nearly as mature as MySQL

Syntax is generally simple Syntax is not as simple as MySQL

41

NDI/NCS Comparison: Server

Local Server86 Amazon Web Service Godaddy VPN

Server hosted on local

machine

Cloud Server that can be

purchased from Amazon

Cloud server that can be

purchased from Godaddy

Performance Limited to

Local hardware and

bandwidth

1 Core CPU with 1 GB

memory

1 Core CPU with 1 GB

memory

No recurring cost for

hosting server

$75 upfront and $0.0086

per hour

1 year cost

$24.99 per month.

42

NDI/NCS Comparison: Android Dev

Android Studio Eclipse

Integrated Development Environment

owned by Google

Integrated development Environment for

Java development

Specially designed for Android

development and has many features like

built in APK generator, Android code

completion

No Special features to aid android

programming

43

NDI/NCS Evaluation Criteria

Evaluation Criteria Weight

Cost 30

Maturity 20

Ease of implementation 20

Functionality 15

Interoperability 15

Total 100

44

NDI Analysis: Google Maps

Criteria Weight Score

Cost 30 27

Maturity 20 20

Ease of Implementation 20 20

Functionality 15 15

Interoperability 15 15

Total 100 97

45

NDI Analysis: Apple Maps


Cost 30 30

Maturity 20 10


Functionality 15 15


Total 100 80

46

NDI Analysis: Bing Maps


Cost 30 23

Maturity 20 17


Functionality 15 15


Total 100 82

47

NDI Analysis: Amazon Web Services


Cost 30 15

Maturity 20 20


Functionality 15 15


Total 100 80

48

NDI Analysis: Godaddy Server


Cost 30 10

Maturity 20 20


Functionality 15 15


Total 100 75

49

NDI Analysis: Local Server


Cost 30 30

Maturity 20 20


Functionality 15 15


Total 100 95

50

NDI/NCS analysis result

NDI Usage

Google Maps Mapping Software

MySQL DBMS

Local Server Server

Android Studio Android App Development

Bootstrap.js CSS Framework

51

Cost Analysis

Personnel Cost

Hardware and Software Cost

52

Personnel Cost

Activities Time Spent(Hours)

Valuations and Foundations Phase: Time

Invested

Team meetings: [3hr/week * 6 weeks *

7people]

126

WinWin Sessions: [3 sessions *

1hr/session/person * 7 people/session

21

Total 147

53

Hardware and Software Cost

Type Cost Rationale

Software- Web Hosting* 200$/year The website for the tour

creation and the database

of the tours need to be

hosted on a server.

Software- Maps API calls 0.50$ per 1000 calls After 10000 calls per day

the average cost of using

the mapping software is

such

* Costs may scale according to the scale of the application

54

Benefits Analysis

Current activities & resources used %

Reduce

Time Saved

(Hours/year)

Time trying to locate tour spots in a location (20

minutes/person/location)

90 110/person

/location

Non Monetary Benefits:

1. People can get quality information about locations and places

2. Increase familiarity of people to different locations

and therefore promote number of visitors

3. Promote tourism

4. Tourist spots and tour creating organizations get a platform to

advertise the attraction and landmarks they have.

55

Major Risks

Risk Description Risk Mitigation

Tour Takers may not be able to view all

the relevant tours that are near them

Develop a mechanism for users to search

tours based on current location and tour

keywords and tags.

The NDI’s and COTS may change. Use the latest versions of API’s so that they

may not get obsolete fast. Moreover,

Keep up to date with the latest trends.

If the project grows to very large scale

then the cost of keeping the project alive

may become very high (API call costs, and

Server Costs)

Give functionality to enable a sustainable

business model that results in profit. This

may include getting income from

advertisements or app pricing depending

on the future needs of the owner.

The Layout of the web and mobile app

may not be preferred by the stakeholders

Get feedback from potential users about

the layout and design details

56

Capability Evidence

Capability Requirement Product Satisfaction

CR-1: Be able to set up mapping API and

place markers

Software/Technology Used: Android

Studio

Feasibility Evidence: Created Prototype

with basic mapping capability

Referred use case diagram:

CR-2: Get Data from the server to the

android application and showing the

content on a marker

Software/Technology Used: Local Server,

MySQL, PHP, Android Studio, JSON

Feasibility Evidence: Implemented new

features in Prototype version 2

Referred Use Case Diagram:

57

LOS Feasibility Evidence

Level of Service Win Condition Rationale

LOS-1: The system shall behave correctly

on mobile

There are currently applications on the

market that can easily render maps with

different markers and details.

LOS-2: The system shall have low to nil

downtime

The web hosting services such as Amazon

and Godaddy have very reliable systems

that are running millions of applications

for various vendors.

58

QUALITY MANAGEMENT

PLAN

62

Quality Management Strategy

All artifacts source controlled using Git

Peer review of the code before committing it to Git

Helps in identifying issues before hand and preventing

sloppy code

Weekly reviews with client

Communicating progress with the client to make sure

progress is on track and agreement with the clients

requirement

IIV&V & Project Manager maintain Git issue tracker

63

Defect Identification

Defect identification will be done through weekly

meetings with peer and clients.

IIV&V performed by the quality focal point

engineer

66

Traceability Matrix67

OCD Win-Win Agreement

OC-1 WC_3752

OC-2 WC_3683

OC-3 WC_3685

WC_3684

OC-4 WC_3689

OC-5 WC_3753

FCR ARB PRESENTATION · PDF file · 2015-10-14FCR ARB PRESENTATION Team 5: Tour...

Documents

Transcript of FCR ARB PRESENTATION · PDF file · 2015-10-14FCR ARB PRESENTATION Team 5: Tour...