open wells cross-platform mobile applicationdcm.uhcl.edu/capf16g11/midreviewpresentation.pdf ·...

30
OpenWells Cross-Platform Mobile Application Techno Sharks: Rou’a Aldalqamouni Daniel Wang Shreyas Makde Madhavi Potluri 1/30

Upload: trinhduong

Post on 27-Jun-2018

214 views

Category:

Documents


0 download

TRANSCRIPT

OpenWells Cross-Platform Mobile

Application

Techno Sharks:

Rou’a Aldalqamouni

Daniel Wang

Shreyas Makde

Madhavi Potluri1/30

OpenWells Cross-Platform Mobile Application

Mentors:

David Crawshay

Olivier Germain

Instuctor:

Dr.Pradeep Buddharaju

Course:

CSCI 6838 – Capstone Project

2/30

Outline

Introduction

Requirements analysis

System architecture diagram and UI design

Demo

Project time line and task division

3/30

Introduction

Background

Previous work

Cross-platform features

Xamarin forms

Xamarin forms features

Roadblocks

4/30

Background

Here is the world map

from where United

States gets oil from

To manage the daily

workovers by large

numbers of workers

we need some from

of software that can

help us update

information in the

presence and

absence of internet

How Do We Solve This Problem?

5/30

Previous Work

Landmark, Halliburton’s technology solutions provider, created an iOS

application in the year 2014

OpenWells Application is a mobile application used by Halliburton

workers that provide a way to manage daily information of Oil Wells

Operations can be logged upon daily, monthly as well as yearly basis

Landmark’s OpenWells iOS app provides a quick and easy data entry

for Workover operations in a connected or disconnected world.

The app can be downloaded from the App Store: Halliburton's App

Link

Major Limitation: Application is only available on iPad and related iOS

devices

6/30

Cross-platform Features

Our task is to convert this

iOS application into

Xamarin Cross platform

application

We will be using Xamarin

Forms to implement a

cross platform mobile

application

This application is

targeted to run on all

major mobile devices

7/30

Xamarin Forms

Xamarin is a mobile application development tools owned by

Microsoft which primarily uses C# as a code behind language

Subsequently, we can use Xamarin as an extended feature to

Microsoft Visual Studio while creating apps on a Windows

Machine

Furthermore, we can use Xamarin Studio to enjoy similar benefits

on a Mac OS X machine

8/30

Xamarin Forms Features

In order to create a cross platform application, Xamarin provides a

UI toolkit named as Xamarin.Forms

Xamarin.Forms allows you to write user interfaces using XAML, the

eXtensible Application Markup Language

Since Xamarin.Forms is suitable for popular MVVM (Model-View-

ViewModel) application architecture, we can programmatically

create a wide variety of new user interfaces with existing models

Xamarin also support various Web Services via web APIs

9/30

Roadblocks

The most noteworthy roadblock that we encountered while

working with Xamarin is while installing Xamarin on Windows 10

The JDK version which gets installed with Xamarin was

incompatible android SDK which comes along with the installation

package

You have to manually install a lot of APIs within android SDK in

order to get the Android Emulator working

You have manually install Visual Studio Cross Platform features

even after installing Xamarin

We then switched to Xamarin Studio on Mac OS X, where again

we had to manually match the JDK and SDK version, since the

default combination did not work.

10/30

Requirements analysis

Business requirements

Functional/technical requirements

Hardware/software requirements

11/30

Business Requirements

Develop an application that can manage oil well workover tasks and

functions similarly to the Landmark OpenWells iOS application for the

Android platform

User should be able to input daily oil well workover task information

User should be able to enter data in a connected or disconnected

environment

Application should sync with the EDM database

User should be able to view data entered in the past or obtained from

EDM database

User information should be tied to the submitted data

12/30

Functional/Technical Requirements

Develop an application that can manage oil well workover tasks and

functions similarly to the Landmark OpenWells iOS application for the

Android platform

• Application should be developed in Xamarin with cross platform capabilities

for both iOS and Android using the Xamarin.Forms library

User should be able to input daily oil well workover task information

• Application should allow numerical data entry with value limits

• Application should allow textual data entry for both data and comment

fields

• Application should allow user to input information via radio buttons

• Application should allow user to delete entered data

• Application should allow user to attach a media file or document

13/30

Functional/Technical Requirements

User should be able to enter data in a connected or disconnected

environment

• Application should be able to detect if it is in a connected or disconnected

environment

• Application should save and store data locally on device in both connected

and disconnected environments

Application should sync with the EDM database

• Application should send stored data to EDM database if it is in a connected

environment

• Application should receive data from the EDM database if it is in a connected

environment

• Application should allow manual syncing of data to the EDM database with a

“Sync” button

14/30

Functional/Technical Requirements

User should be able to view data entered in the past or obtained from

EDM database

• User should be able to generate a PDF report with details of daily tasks

• User should be able to view past data within the application

• Application should display views of the data filtered by “All”, “Year”, “Month”,

and “Day”

• Application should display Well Bore schematic data obtained from the EDM

database

• Application should display a map of the current area via device GPS

User information should be tied to the submitted data

• User information should be tied to the device settings

• Application should identify the user for a specific device the first time a well is

downloaded

15/30

Hardware/Software Requirements

Hardware:

• Windows computer with Xamarin Open Source installed

• Android device with GPS

• Apple computer capable of viewing OpenWells application source code

• iPad tablet with GPS capable of running the Landmark OpenWellsapplication

Software:

• Xamarin Open Source

• XCode

• Visual Studios (compatible with Xamarin Open Source)

• MS Office

• Notepad++

• Adobe Acrobat

16/30

Design

System architecture diagram

General architecture diagram

UI design

Database Info

17/30

System Architecture Diagram18/30

General Architecture Diagram19/30

UI Design20/30

UI Design21/30

UI Design22/30

Database Info

Landmark Engineer’s Data Model (EDM) is the corporate

database

The OpenWells application is able to sync with the EDM

database

Realm Mobile Database will be used to generate a mobile

database on each android device

The Realm Database will communicate with EDM corporate

database via the AutoSync API

23/30

Demo24/30

Task Division & Project Timeline

Task division

Project timeline

25/30

Task Division

XML data model conversion

• Rou’a Aldalqamouni, Daniel Wang, Shreyas Makde, Madhavi Potluri

XML OpenWells forms conversion

• Madhavi Potluri, Daniel Wang, Shreyas Makde, Rou’a Aldalqamouni

Realm Database Integration

• Madhavi Potluri, Daniel Wang, Shreyas Makde, Rou’a Aldalqamouni

Well-selection page creation

• Daniel Wang

Background page creation

• Daniel Wang

Common pages creation

• Shreyas Makde, Daniel Wang, Rou’a Aldalqamouni, Madhavi Potluri

26/30

Task Division

Map display function/page

• Shreyas Makde

Report generation function/page

• Daniel Wang

Schematic display page

• Shreyas Makde

Web service Function page

• Madhavi Potluri

Integration of complete application

• Rou’a Aldalqamouni, Daniel Wang, Shreyas Makde, Madhavi Potluri

Application installation and testing

• Rou’a Aldalqamouni, Daniel Wang, Shreyas Makde, Madhavi Potluri

2730

Project Timeline28/30

Project Timeline29/30

References30/30