FOT MSc Project Proposal

MSc Project Proposal Title ………Cloud Computing and HRMS ………. Author ……………..Nasreen Iqbal………………….……….. Programme ………MSc Software Engineering...

Year ………………….2014/15……………………………

FOT FACULTY OF TECHNOLOGY

Project Identifier: DMU-Faculty Of Technology Version: 1.0 Contact: [email protected] Date: 18 September 2014 ---------------------------------------------------------------------------------------------------------------------------------------------------------------

MSc. Project Plan Project Information Student Name

Nasreen Iqbal

Project Title

Cloud Computing and HRMS System End Date

Start Date Lead Institution

De Montfort University, Leicester

Project Supervisor

Francois Siewe

Contact email

[email protected]

Program Name

IMAT 5314 MSc

Document Information Author(s)

Nasreen Iqbal

Project Role(s)

Researcher

Date

17-09-2014

Filename

Project Proposal

Access

Document History Version

Date

Comments

1.0

17-09-2014

Project Proposal

1.1

23-10-2014

Revised

1.2

18-11-2014

Final Version

---------------------------------------------------------------------------------------------------------------------------------------------Page 1 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


Table of Contents 1.

PROJECT O VERVIEW & BACKGROUND ............................................................................................................................... 4 1.1.

Project Summary .............................................................................................................................................. 4

1.1.1.

Why Important ............................................................................................................................................ 4

1.1.2.

Methodology: .............................................................................................................................................. 4

1.1.3.

Operationialsed the concept ....................................................................................................................... 8

2.

Aim & Objective ..................................................................................................................................................... 5

2.1.

INFRASTRUCTURE AND ROAD MAP: ............................................................................................................................ 6

2.1.1.

SOFTWARE ....................................................................................................................................................... 6

2.1.2.

HARDWARE ...................................................................................................................................................... 6

2.1.3.

Category of Services: ................................................................................................................................... 6

2.1.3.1.

Cloud Environment.................................................................................................................................. 6

2.1.3.2.

Cloud Deployment Models...................................................................................................................... 7

2.1.3.3.

Software Services .................................................................................................................................... 7

2.1.3.4.

Details Methodology: ............................................................................................................................. 7

2.2.

Academic Objectives......................................................................................................................................... 7

2.3.

PRODUCT OBJECTIVES ............................................................................................................................................. 7

2.4.

Learning Objectives .......................................................................................................................................... 8

2.5.

HYPOTHESIS: ......................................................................................................................................................... 9

3.

ANTICIPATED O UTPUTS AND O UTCOMES / D ELIVERABLE .................................................................................................... 9

4.

C ONSTRAINTS .............................................................................................................................................................. 10

5.

ASSUMPTIONS ............................................................................................................................................................. 10

6.

RISK A NALYSIS / RISK MIGHT JEOPARDIZE THE SUCCESS OF THE PROJECT ............................................................................. 10 6.1.

RISK ASSESSMENT & RISK REGISTER .............................................................................................................. 13

6.2.

Intellectual Property Rights............................................................................................................................ 14

7.

PROJECT RESOURCES .................................................................................................................................................... 15 7.1.

Project Partner................................................................................................................................................ 15

7.2.

Project Team Roles ......................................................................................................................................... 15

8.

DETAILED PROJECT PLANNING ....................................................................................................................................... 15

8.1.

E VOLUTION P LANS ................................................................................................................................................... 15

8.1.1.

PLANNING FACE ................................................................................................................................................. 16

8.1.2.

DESIGNING F ACE ................................................................................................................................................ 17

8.1.3.

TESTING FACE: ................................................................................................................................................... 18

8.1.4.

DEPLOYMENT FACE: ............................................................................................................................................ 19

8.1.4.1

GOOGLE A PPS E NGINE APPLICATION PROGRAMMING I NTERFACE ............................................................................ 19

8.1.4.1

APPLICATION S ANDBOXING .................................................................................................................................. 19

8.1.4.1

GAE APPLICATION SERVICES ................................................................................................................................ 20

8.1.4.1

L IMITATIONS AND R ESTRICTIONS .......................................................................................................................... 20


Project Identifier: DMU-Faculty Of Technology Version: 1.0 Contact: [email protected] Date: 18 September 2014 --------------------------------------------------------------------------------------------------------------------------------------------------------------STEP 5: M ANAGE THE M IGRATION : ......................................................................................................................................... 21 8.1.9. 9.

M AINTENANCE F ACE: .......................................................................................................................................... 21

QUALITY ASSURANCE .................................................................................................................................................... 21

10.

SCHEDULE OF ACTIVITIES .......................................................................................................................................... 23

11.

C ONFIRMATION OF E THICAL R EVIEW .......................................................................................................................... 23

12.

PROJECT RECOMMENDATION AND INFORMATION FORM ............................................................................................... 23



1.

PROJECT OVERVIEW & BACKGROUND

1.1. Project Summary The Cloud computing is delivering hosted services through the Internet, included information provided to the computer or other devices. Cloud computing E-Business HRMS based computation provide, software, data access and resources for the storage, without user required to know about the location and other detailed computing infrastructure for the application. Fundamentally, the cloud is an enabling technology allowing companies to shift their focus away from systems and applications management towards increasing business value added areas such as business process and enterprise performance management. The following are the benefits and focus areas: 

Reliability



Personalization



User interface



Security



Reduce implementation cost



Integration



Enhanced reporting



Streamline business process

The study found drastic benefits while choosing migration E-Business system. One of the major reason is cost saving and resource. Moreover, the new generation of cloud business application being developed, a single application can be used by many companies/clients with data segregation and security. Earlier, many companies were uncertain to move their data on the cloud, subject to security and availability. This ambiguity improved and currently many critical businesses legislatives are consenting cloud as cloud computing help users to save a significant amount of cost that is related to infrastructure investment, management, and maintenance. 1.1.1.

Why Important

This project entitled “E-Business Human Resource Management System” is part of larger Oracle Applications and has been designed towards improving the Management of Employee system, which is the backbone of any small/large company structure, consist of Employee detailed history and their succession cycle with the company. In this research, we would implement private cloud computing application that intended to reduce the Hardware / Software maintenance, support, measured cost saving and quickly deployment and development results with the conviction of anywhere anytime. 1.1.2.

Methodology:

The research will focus on the quantitative research methodology to prove the hypothesis, consequently significant results will be derived from the data analysis fetch from the technical literature of existing services, followed by the theorem of „experimental before and after‟ study design pattern with the controlled environment where observation established before & after intervention. Throughout, focused on the „why’, ---------------------------------------------------------------------------------------------------------------------------------------------Page 4 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


„how’ and „what’ theorem, would measure total changes (y=y‟-y‟‟) to assess the impact of an intervention using before and after data collection, intent to receive absolute outcomes, based on dependent variables applied on hypothesis without qualifying independent and extraneous variables separately.

The following

below represents selected project design style: Result

Target Population

Post Test

Selection

Pre-test

Intervention X

Dependent Variable Y’

Before-and-after design is calculated as follows: [Change in dependent variable] = [Status of the dependent variable at the „after‟ observation] – [Status of the dependent variable at the „before‟ observation]

= Y‟=Y‟-Y‟‟ Based on Above selected project design style, we will analysis the future of cloud computing and migration work on Saas (Software as a service) which will demonstrate the Software delivery method. In this migration the Business will migrate with its entire HRMS module along with the database with measured security issues to the chosen resource. The process will structure through the entire life cycle of system development, including testing, implementation and maintenance. The business user will approach to the software and its functions remotely using cloud computing vision environment, fully secured and password protected, each user will be provided credential with their access rights, including administration activates to control the application functionalities and application maintenance. 2.

Aim & Objective

Successfully migrate the E-Business HRMS instances to private cloud to gain the enormous cost saving benefit of cloud computing. My main research objective is to elimination of traditional computing model with the remotely accessible cloud based system. Moreover, I possibly extend my research paper to Cloud based E-Business legacy Apps accessible to various mobile devices, which will provide weightage to my research. Currently, many companies moved and started services for their clients, but still legacy application and their data security are under controversy and has no clear indication. The research also will focus on the facts: 

Applications Infrastructure for Cloud



Cost estimation



Data security & Privacy



Migration and relevant assurances



Mobile devices and Apps access



Law & Services



The main objective of the research paper is Hosted and Migrate latest Oracle E-Business instance on cloud machine, where companies can implement and use any module HCM on Oracle EBS instance, and could access from any device any time. The precise indicative review is given below: 2.1. INFRASTRUCTURE AND ROAD MAP: 2.1.1. SOFTWARE 

Oracle E business (12.1.3) on IBM-Unix. (Multi-Business group)



Separate EBS instance for each country (Legislation specific)

2.1.2. HARDWARE 

P6 IBM virtualization server, which can host up to 250 virtual servers. o

Database Server that logs and archives the data coming in from offshore into a database, an off-site tape drive is used to take daily backups of the database.

o

An application server that hosts a number of data reporting and monitoring applications. The end users access these applications using Mobile devices/ remote desktops over the internet.

Cloud Infrastructure Company Site

Application Server

Database Server Tap Driver For Data Backup

Firewal l

Users

2.1.3.

Category of Services:

2.1.3.1. Cloud Environment o

Infrastructure as a Service (IaaS): provides virtual machines and other abstracted hardware and operating systems.

o

Platform as a Service (PaaS): allows customers to develop new applications using APIs, implemented and operated remotely.

o

Software as a Service (SaaS): is software offered by a third party provider, available on demand, usually through a Web browser, operating in a remote manner.



2.1.3.2. Cloud Deployment Models o

Community cloud: Infrastructure is shared by several organizations and supports a specific community

2.1.3.3. Software Services o

Complete hardware and O/S. (Client company needs only desktop/tablet and net connection)

o

Implementation of any E-Business Module.

o

Migration of data and setup of any existing implemented module

o

Support services for E-Business

o

Free hardware and O/S upgrade

2.1.3.4. Details Methodology: o

Each VM can host Oracle EBS instances for Production, Test and Development environment. Application and data clustering in enabled on VM to provide, 24 X 7, availability against disaster and for online patching to eliminate downtime. It would emphasis to one VM for one country, under this company can implement and run HCM modules needed, each company will use separate business group. All data and setup will under this business group to provide crystal clear segregation of data and setup.

o

The major and critical point of the research paper is about application Security/Access including new application user registration and their roles which will be handled by Cloud Company.

o

Robust Hardware can up to 250 virtual machines.

2.2. Academic Objectives Research, study the process, methods and business of cloud computing. 2.3. PRODUCT OBJECTIVES The objective of this project is to research, gather requirement of cloud computing for an E-Business system that migrate the Modules to the cloud computing for the cost saving and outsourcing. The system is part of a large E-Business Application and will be responsible for maintaining information about employees, 

Admin Module: Administrator controls the entire application. The administrator can add, delete, edit and view all employee details and admin can create Employees‟ Payslip. The administrator also manages the data related to organizations and businesses. Administrator generates reports based on various criteria.



Employee SSHR: herein, employee can view/update their own personal information, view pays lip and can apply for vacation and expense claims





I-Recruitment: Used for Recruitment of employees, Store and manage applicant data, shortlist applicants for a vacancy, creation of vacancy requisition. Connect to other Recruitment agencies‟ database. Publish vacancies on the web.



Success Planning: Used to plan successors for Positions and employees in the company.



HR Module: HR controls, work structures, personnel, Assignment, salary admin and Absence Management.



Payroll Management: Payments to employees, standard recurring, overtime, absence deductions, loan deductions and bank details with transfer to banks..



Employee Module: Employees must have valid login information to access the application. Each employee can view the details of Vacancy, Payslip, schedules and Training



Security Module: Each client should able to create access control to their users.



Export tools: Rapid is exporting of client data by clients.

2.4. Learning Objectives The learning objective is to implement the cloud computing in the organization and access them through Mobile devices, data security and privacy for legacy applications, and relevant upcoming challenges during the process. 2.5. Operationialsed the concept OBJECTIVE

MAJOR

INDICATORS

VARIABLES

CONCEPT

MEASUREMENT

Hosted and Migrate

Hosted

Cloud computing

Total Virtual machine

latest

and

machine

availability using IaaS

Oracle

Business

E-

instance

UNIT OF

In MB / GB

Migrate

on cloud machine, where

companies

can implement and use HCM

any on

module

Software Srvices

Network

availability on Demand

Access

Number of PaaS API‟s

In counting

Oracle

APS‟s

EBS instance, and could access from

Oracle E-Business Model

any device any time.

Oracle E business

Version

(12.1.3) on IBM-Unix IBM-Unix / Linux EBS instance for each

Signs reading /

country Legislation

Servey

specific



Migration of data and

Per MB

setup Wireless communications

Average

Packet type

protocol

communications protocols packets

Migration to gain

Cost

Expenditure per year

the enormous cost

-

saving benefit of

Service provider

Total annual

1 if > 100

Expenditure

000 $

Fees

-

Hardware

Maintenance

-

Software

cloud computing. -

2 if > $ 2500 000

2.6. Hypothesis: Research Objective

Hypothesis

Hosted and Migrate latest

1.

Oracle E-Business instance on cloud machine, where companies

can

computing to access applications remotely. 2.

implement

and use any module HCM on

The elimination of traditional computer system and establish Cloud

Service provider reliability and virtual machine availability using IaaS.

3.

Oracle EBS instance, and

Provide a common platform as Saas for different companies geographically.

could access from any device

4.

API‟s usibilites, availability and their access

any

the

5.

Network reliability and availability with the data security

enormous cost saving benefit

6.

Availability of required Hardware for latest Unix version

of cloud computing.

7.

Legismatic findings in the target country / globally

8.

Successful Data Migration and recorded efficiency

9.

Application availability remotely, anywhere, anytime

time,

to

gain

10. Analysis of costing savings and benefits

3.

ANTICIPATED OUTPUTS AND OUTCOMES / DELIVERABLE

The following below outcomes will typically achieve from the real and relevant strategy plan with focus primarily on addressing priorities. Output / Outcome Type (e.g.

Report,

publication,

Brief Description software,



knowledge built) Successfully

hosting

of

E-Business

instance on private clouds

Clients/Users should be able access an operational live instance using internet from anywhere using PC/Tablet and mobile

Removal, Hardware and Network and

Existing Hardware and Network can be decommissioned that

associated support

will achieve cost saving and reduction.

Technical application)

stack

Software

upgrade

by

(Database, the

cloud

and

O/S

Oracle Software and Hardware upgrade

company on reasonable cost. Database

administration

administration of cloud company on

Database and operating system support can be controlled by cloud computing services.

reasonable cost. 4.

CONSTRAINTS

The following are the constraints: 

User and management assurance of reliability of cloud computing and its Legal challenges.



Data recovery possible after the system crash



Security constraints required user partially authentication, moreover use of secure Socket Layer (SSL) are recommended.

 5.

Latest Windows access issues, recommended windows and patches may apply.

ASSUMPTIONS

Assuming that, the cloud hosting company will take outsourcing of hardware, software, maintenance along with administration of databases. 6.

RISK ANALYSIS / RISK MIGHT JEOPARDIZE THE SUCCESS OF THE PROJECT

Risk management is defined in the ISO 31000 international standard as “the effect of uncertainty on objectives”; therefore externalizing IT resources via the cloud changes the risk profile for the workload and organizational. The categorized table will be maintained for the duration of the project, listed the risk probability in percentage % and its impact (Negligible, critical and marginal) that obtained by the current risk factors. To prioritize applications for migration to cloud computing, it is necessary to first identify and understand the business and technical factors for the migration. The report presented below risk may jeopardize the success of my project, assessing their likelihood and impact. However, I will do my all the best to mitigate the project, will follow step by procedure, included provider and supervisor assistance, even though if any interruption I will move my hypothesis to the project proposal. ---------------------------------------------------------------------------------------------------------------------------------------------Page 10 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


Risk

Proba

identification

bility

Security may

9%

Impact

Critical

be inadequate

Assessment (i.e. Combine

Risk monitoring, mitigation and

probability and impact)

management

Risk of Data loss, data

Having own information, on own

hacking and information

hardware and between our own four

leakage.

walls, provides a level of comfort that may lose in the cloud, we must adapt traditional security models to suit cloud computing needs and consider

end-to-end

security,

including our own internal policies for

access

control

and

user

provisioning Data Security

9%

Critical

Moving your data and code

The technology to make cloud

to a third party provider

computing

creates some security risks

securing cloud workloads often

safe

is

available,

requires new concepts and skills that may take time to acquire

Loss

of

8%

Marginal

For

software-as-a-service

Too Early

(SaaS) and some platform-

control.

as-a-service

(PaaS),

the

entire control of hardware, software, security policies, etc., is placed in the hands of a third party provider Availability

7%

Marginal

Issues may arise from a

and reliability

combination

of

performance, configuration

cloud

applications

of

Too Early

server

errors, network design, and application

architecture,

possibly in combination, which can initially make them difficult to resolve



A

disaster

8%

Marginal

This can be a business

An effective backup and restore

may

occur

"disaster"

as

process, with the backup copy held

from

which

bankruptcies or contract

in a different location from the data,

solution

cancellations on the part of

or on your own rather than the cloud

cloud suppliers.

supplier‟s system, can change the

the

cannot

such

impact of a disaster from fetal to

recover

merely serious The concern is that once a

Emerging standards will increase

provider

cloud

one

the portability and interoperability

lock-in

provider is adopted, it will

of systems across cloud service

not be easy to switch to

providers,

using an equivalent cloud

eliminate this current barrier to

service

cloud adoption.

Cloud service

9%

Critical

service

of

of

a

different

and

will

reduce

or

provider.

These factors are built into

Do short-term and long-term return-

may not meet

most

(return-on-

on-investment (ROI) work. The key

its

investment) models, and

factors to consider when assessing

affect the headline figures

cloud return-on-investment (ROI)

for investment, revenue,

risk probability include utilization,

cost, and time to return.

speed, scale, and quality

Dependence on an external

Organizing departments and CEO

cloud supplier can increase

involvement in the critical issues.

the

of

Even department law and regulation

noncompliance. Even if we

fully documented, implemented and

contractual

have contracts that provide

legalized.

and

the necessary assurances

The solution

7%

Marginal

financial

objectives

The solution may comply its

7%

Marginal

not with legal,

moral

on

obligations

ROI

probability

location

and

confidentiality. the

Research on the reliability and

dependencies

system are well-understood

dependency, develop bonds with the

and

and planned, and others are

service provider and ensure with

Reliability of

not yet comprehended.

their services and adapted reliability.

System

6%

Marginal

Some

elements

of

services



Mobile

and

6%

Marginal

The

critical

information

privacy issue

tablets access

The

authorized

devices

may

and

registered

access

these

applications having authenticated

issue

credential. Services may not available

The best way to address is having a

may not work

on time, several issues in

clear executive vision and direction

in the context

accessing

for business transformation, which

of

provider.

The solution

the

7%

Marginal

user

from

the

includes top-level executive support,

enterprise’s

a clear roadmap for procurement or

organization

implementation of cloud services

and culture

and applications that use them, and coordination of stakeholders and competing

strategies

to

get

agreement for storage, computing, network and applications. 3%

System quality

Low

The system quality of an external service can be assessed using the

may

be

same factors as for the system

inadequate,

quality of our own solution. Look at

so that it does

the track records of suppliers very

not

carefully, Harding and his co-

meet

users’ needs Management

authors advice. 5%

Low

Risk

6.1.

New experience in this

The development plan must review

developing,

periodically

Management

with

the

complete

will focus on security on

research on security and cost saving

cost saving.

table.

RISK ASSESSMENT & RISK REGISTER

The risk register focus on the specific high priority expected risk which required well plan system and resolution. Risk Record Risk

R01

Risk Title

ID Owner

The solution may be difficult to develop due to the difficulty of integrating the cloud services involved

XYZ

Date Raised

Status

Critical



Risk Description Technical risk takes place when the application of software engineering techniques, theories and principles will fail to generate the right software product. In the Cloud computing application development many external, unfamiliar interfaces and software involved with the different platform from the various organizations and the E-Business Software has to work together in order to establish the communication between cloud computing and application access system. Impact Description: The security influence a lot on the image of the software provider because the stakeholder / organization's expectation into more capabilities, quality standards, security and cost saving. Even a tiny defect in the application might cause unreliability. There is a risk that it will not be possible to integrate [multiple] cloud services with the existing system and with each other. Recommended Risk mitigation: The service integration risk can be assessed by considering interface conversion cost, ability to change the existing system, and available skills. Significant skills are required to assemble and customize multiple cloud services from different providers in a flexible, adaptable way, while maintaining security, backup, and governance mechanisms. Portability / Impact Values Portability

Impact Cost

Duration

Quantity

Pre mitigation

Less costly

4 to 6 months

1

Post Mitigation

Costly

Unexpected time

More than expected

Incident Action History Date

Incident / Action

Actor

N/A

Service

Outcome / Comments N/A

Provider 6.2. Intellectual Property Rights This project will research and concern with the copyrights of the organization and service provider that may initiate the various challenges. This research will also highlight the applicable international legal laws and their terms. ---------------------------------------------------------------------------------------------------------------------------------------------Page 14 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


7.

PROJECT RESOURCES

7.1. Project Partner The one of the following below service providers are available for student trial for 30 days, during a specific time period the research will complete its deployment and tests. In case of time concern, we may purchase 12 month space from the best suitable providers. 

Google apps



Organization

7.2. Project Team Roles Team Member

Role

Contact Details

Name

Days per week to be spent on the project

Google Apps

Service provider

5

Organization

Detail provider and stakeholders

5

Francois Siewe

Project Supervise

Nasreen Ahmad

Lead

[email protected]

for

implementation,

Planning, testing

and

P13194231@myemail.

5

dmu.ac.uk

maintenance 8.

DETAILED PROJECT PLANNING

This precise project planning includes scheduling diagrams using Gantt (Appendix A) where activities and links represent task dependencies as follows: Define Activity Identify Activity 8.1. E VOLUTION P LANS The precise evolution plan will carry forward with the „Agile software development methodology’ permits incremental change over time through collaboration, is an umbrella term for a number of different software development models including, „Crystal Clear and Dynamic Systems Development Method‟ (DSDM). However, the overall project is broken down into a series of short development cycles approx. Two-three weeks each called iterative in terms of development models. I selected Agile with a traditional waterfall methodology to manage the project faces individually during implementation activity. As in the figure below, the each iteration involves the development team carrying out essentially the same activities as under the waterfall model (planning, design, coding, testing and deployment), but under Agile working practices: ---------------------------------------------------------------------------------------------------------------------------------------------Page 15 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved




These activities are focused on the current iteration rather than the overall project, though there may be some general planning activities, as we shall discuss later in this paper.



Although there will be some upfront planning in each iteration, the design, coding and testing activities are effectively performed simultaneously.



Using waterfall sequence, based on contract for each face that may complete before the next phase.

Planning

Designing

Coding

Testing

Deployment

3 to 24 Months

Iteration 2

Iteration 1

Design

Design P L A n

Code

Iteration 3

D E P L O y

P L A n

Code

Test

Test

2 to 4 week

2 to 4 week

Design D E P L O y

P L A n

Code

D E P L O y

Test 2 to 4 week

The Agile Model 8.1.1. PLANNING F ACE Step 1: Assess Applications and Workloads: Assessment and Development Planning: in this step we determine what data and application must move to the cloud. The readiness assessment spans the following areas: 

Business Considerations:



Application Lifecycle Considerations:



Application Architecture Considerations



Data Considerations



Technology Considerations



Security Considerations



Integration Considerations

Develop Strategic Plan: plan for deployment, for application selection and for after deployment. Lastly, post plans for usage of the application. Identification of Strategic Goals and Objectives: Provided Complete details for service provider outcome and application implementation stages with the test trial, find out the solutions for project constraints and assumptions. ---------------------------------------------------------------------------------------------------------------------------------------------Page 16 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


Action Plans to Implement Strategic Plan: Finalize deadline, Objective, responsibility and deadline for completion, operating budget completion. Step 2, Build a Business Case: This step follows the development business case for migrating applications to cloud computing with cloud computing strategy and specific information that describes the current state and demonstrates the advantages of cloud computing to not only reduce costs but to deliver meaningful business value. 

Cost Analysis: In order for meaningful comparisons to be made, we must have specific baseline costs for the current environment. The overall cost of application migration to cloud computing must include the following elements:



o

On-going cloud service costs

o

Service management

o

License management.

o

Application re-designs

o

Application deployment and testing

o

Application maintenance and administration

o

Application integration

o

The cost of developing cloud skills

o

Human resources and talent management implications

Service Levels: the required service levels should be agreed with the cloud service provider and explicitly documented in the cloud service agreement. For each application being migrated to cloud computing, consider the following application characteristics: o

Application availability

o

Application performance

o

Application Security

o

Privacy

o

Regulatory compliance: government and industry regulations may require additional measures, such as restricting the migrated applications and data to reside in a specific geographic region



Business Impact: the additional business factors must be weighed in order to develop a complete business analysis, and should be monitored on an ongoing basis: o

Revenue impact

o

Customer acquisition or engagement impact

o

User satisfaction

o

Time to market improvements

o

Cost of handling peak loads

8.1.2. DESIGNING FACE Step 3: Develop a Technical Approach: ---------------------------------------------------------------------------------------------------------------------------------------------Page 17 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved


As discussed above, there are two potential target service models for the migration of an existing application – Infrastructure as a Service (IaaS) and Platform as a Service (PaaS). 1.

PaaS -Migration: A PaaS solution provides the elements of the particular software stack required by applications such as the operating system, an application server and a database, so that the customer only has to be concerned with the specific application components and data.

2.

IaaS-Infrastructure as a Service: Infrastructure service can be thought of as pools of basic resources, such as compute power and storage, which are delivered as a service over the internet.

3.

IaaS -Migration: The entire software stack has to be migrated, the application code, plus any supporting code it requires – including the underlying operating system. To achieve this, we shall package the complete software stack as one or more virtual machine (VM) images, which can then be copied into the cloud service and executed there. 

Common Technical Considerations: In both the PaaS and IaaS cases, the following technical considerations must be taken into account: o

Skills

o

Security

o

Integration

o

Monitoring and Management

o

Scalability

o

Availability and Backup

Step 4: Address Security & Privacy Requirements Security and privacy are two main issues that concern cloud service customers the most, in my term security involves multiple concerns. It includes such aspects as: 

Data security



Trust in the Cloud services



Authorized login services to access system



System and application level security



Risk analysis

8.1.3. TESTING FACE: Iteration: we may plan several iterations for the successful results Design: Planning and assessment of testing and schedule test plans Code: Create Testing code, included Unit Testing, System Testing, Acceptance Testing life cycle, formal test. Test: 

Features to test: 

Requirements specification

o Specific requirement ---------------------------------------------------------------------------------------------------------------------------------------------Page 18 of 27 Document title: Project Proposal Copyright © 2014, De Montfort University, All rights are reserved




o

Non functional requirement

o

Functional requirement



Classes



Program files



Interfaces



Functions



Data flow



Application access from cloud to devices

Features not to test: 

Hardware component



The cloud provider API‟s.



VM Machine

8.1.4. DEPLOYMENT FACE: Deployment of apps will proceed through Google Apps Engine (PaaS). This service offering, the operating system, system software, development framework and virtual machines are integrated into a single unit and will provide to the end user as a single service product. The application deployment architecture based on the below:

App Engine Physical Deployment Diagram

8.1.4.1

GOOGLE APPS ENGINE APPLICATION PROGRAMMING INTERFACE

The GAE provide an integrated software development kit (SDK) for Go programming language, this will provide the web application access point for the users.

8.1.4.1

APPLICATION SANDBOXING

GAE platform run in a sandboxed environment, which provides limited access to the underlying operating system. This allows my application to be executed securely in isolation without interfering with other applications, and independent of hardware, operating system and the physical location of the server.


Project Identifier: DMU-Faculty Of Technology Version: 1.0 Contact: [email protected] Date: 18 September 2014 --------------------------------------------------------------------------------------------------------------------------------------------------------------8.1.4.1 GAE APPLICATION SERVICES

GAE provides services to enable sandbox applications to communicate with „outside world‟ via HTTP requests, with the flawless the following features, which include: 

URL Fetch: for accessing resources on the Internet e.g. web services.



Mail: for applications to send emails.



Memcache: for storing arbitrary data that doesn‟t require persistence.



Image Manipulation: which enables GAE applications to manipulate images (cropping, resizing, rotating and flipping JPEG and PNG images)?



Crown: allows configuration of regularly scheduled tasks that operate at defined times or regular intervals.

GAE Service Infrastructure

The GAE also employs a novel proprietary way to store application data through its Data store concept, as entities with a set of properties in a schema-less structure in distributed Datastores, which are scaled according to need.

8.1.4.1

LIMITATIONS AND RESTRICTIONS

Due to security concerns and fair use associated with any Cloud Computing system, GAE has employed restrictions and limitations on applications deployed on the platform, some of them being: 

Read-only access to the Google File System (GFS) and only virtual storage is accessible.



Code can only be executed through HTTP requests.



In the case of Python applications, only those developed in pure Python are supported.





Only a subset of Java classes is supported on the environment.



SSH/HTTPS is only available through *.appspot.com domains and not via Google Apps Domains.

STEP 5: MANAGE THE MIGRATION: Executing a migration is a complex and delicate activity, which should have a formal project plan and a skilled project manager. In my migration plan, include track tasks, durations, resources, costs, and risks. My deployment plan will follow several iterations that will make sure that the deployment has completed with all the achieved success faces. 

Deploy the Cloud Environment. Provide, install and test the necessary storage, compute, network and security resources that constitute the cloud environment in which the migrated application will run.



Install and Configure the Applications. The applications and supporting middleware should install and configured on the cloud servers. It is studied that the cloud service providers frequently do this through automated deployment of templates.



Harden the Production Environment. Install additional utilities for business continuity and security. Note that some of these services may be provided by the cloud service provider, in which case they do not need to be installed, but they should still be tested.



Execute a Simulated Migration. An experimental run of the migration project plans to uncover unintended results or unnoticed issues during the planning phase. The simulation migration date should be sufficiently distant from the desired final cutover date to have time to rectify problems. I will involve the cloud service provider in the migration date selection.



Cutover to Production Cloud. Assuming a successful simulation migration, or one that only encountered minor issues with a clear fix establish a formal cutover schedule. If the simulation migration ran into serious issues, then it needs to be repeated after correcting the causes.

8.1.9. MAINTENANCE FACE: Check against anticipated outcomes and outputs in the original project plan. The degree to which we have the outputs: Successful deployment E-Business application to the Cloud Computing and finally Authentic Application Access for the users. 9.

QUALITY ASSURANCE

Output / Outcome

Fully searchable and openly accessible digitized collection

Name When will QA be

Who will carry out

carried out?

the QA work?

Receipt/loading

of

Project leader

remote apps sources

What QA methods / measures will be used?

Checking resources comply with naming standard, with reference to project worksheet, amending if necessary.



Project leader

Ensuring Application is addressing to a standard that is legible and usable. Making decisions on inclusion of data, forms and report which are not legible/reusable.

Project leader

Adding correct and relevant metadata, with reference to the terms provided by academic project supervisors.

Project leader

Checking data is accessible and usable to the visually impaired, with reference to agreed Cloud apps standards.

Immediately

Project Supervisor

following upload

Checking sites visual presentation (of items as a whole) and as part, with reference to the Cloud computation application slandered.

Project leader

Reducing that data is correct by carrying out specific searches and referencing against initial lists.

Project leader

Carrying out specific searches to ensure items integrated into the whole collection correctly, amending/resolving any issues wherever possible.

1

months

after

Project leader

release

Gain feedback from Organization Group on their members use.

Incorporate

any

amendments/suggestions/improvements if possible. Pre-deployment

Project Supervisor

Assessment

of

proposed

materials

against

agreed

academic requirements, with reference to handbooks and discussion. Post-deployment

Project leader

Check proposed materials with academics to ensure they still

comply

with

expected

Cloud

Computing

requirements, removing, changing if necessary. Creation Authenticate

Project Supervisor

Usability testing

Project leader

Check with academic members of the team, whether suits

access

control for the users

Once

Cloud

Apps

created

their teaching purposes, check against handbook to ensure meet module criteria, amend as far as possible, as



appropriate. Project Supervisor

Check the functionality of Cloud Computation in general logging and resolving any technical issues.

Project leader

Refer to Steering Group for feedback and incorporate any suggestions where possible

Once Computing

Cloud

Project leader

HRMS

Get feedback User, regarding use in teaching, using the module feedback form (benchmarking against previous

Apps released

iterations

of

the

module)

and

verbal

discussion.

Incorporate any changes/improvements if possible, include in the final project evaluation. Project leader

Regularly check site for comments by external users, responding as appropriate, and collate Cloud Computing remotely usage stats

Project Supervisor

Can/or resources being repurposed? Check web/Jorum, for repurposed items.

10. SCHEDULE OF ACTIVITIES Enclosed Appendices A 11. CONFIRMATION OF ETHICAL REVIEW Enclosed Appendices B 12. PROJECT RECOMMENDATION AND INFORMATION FORM Enclosed Appendices C



APPENDICES A: Gantt chart Task Name

Duration

Start

Finish

Cloud Computation

236 days

Sun, 11/30/14

Thu, 10/30/15

Planning Face

44 days

Sun, 11/30/14

Wed, 1/28/15

Gather Information & Create Requirement specification

5 days

Sun, 11/30/14

Thu, 12/4/14

Analysis and Development Plan

7 days

Fri, 12/5/14

Mon 12/15/14

Develop Strategic Plan

5 days

Tue, 12/16/14

Mon 12/22/14

Identification of Strategic Goals and Objectives

5 days

Tue, 12/23/14

Mon 12/29/14

Action Plans to Implement Strategic Plan

5 days

Tue, 12/30/14

Mon 1/5/15

Create Progress Report

6 days

Tue, 1/6/15

Tue, 1/13/15

Build a Business Case

7 days

Wed, 1/14/15

Thu, 1/22/15

PMP Meeting

1 day

Fri, 1/23/15

Fri, 1/23/15

Cost Analysis

6 days

Mon 1/26/15

Mon 2/2/15

Service Levels

7 days

Tue, 2/3/15

Wed, 2/11/15

Business Impact

8 days

Thu, 2/12/15

Mon, 2/23/15

Perform Detailed Design

6 days

Tue, 2/24/15

Tue, 3/3/15


7 days

Wed, 3/4/15

Thu, 3/12/15

39 days

Fri, 3/13/15

Tue, 5/5/15

Develop a Technical Approach

12 days

Fri, 3/13/15

Mon 3/30/15

Common Technical Considerations

12 days

Tue, 3/31/15

Wed, 4/15/15

Address Security & Privacy Requirements

7 days

Thu, 4/16/15

Thu, 4/23/15


7 days

Fri, 4/24/15

Mon 5/4/15

Designing Face



PMP Meeting

1 day

Tue, 5/5/15

Tue, 5/5/15

33 days

Wed, 5/6/15

Fri, 6/19/15

Develop, Test Requirement

5 days

Wed, 5/6/15

Tue, 5/12/15

Formal Testing

7 days

Wed, 5/13/15

Thu, 5/21/15

Application Testing

7 days

Fri, 5/22/15

Mon 6/1/15

System Testing

7 days

Tue, 6/2/15

Wed, 6/10/15


7 days

Thu, 6/11/15

Fri, 6/19/15

56 days

Mon 6/22/15

Mon 9/7/15

Deploy the Cloud Environment

12 days

Mon 6/22/15

Tue, 7/7/15

Install and Configure the Applications

10 days

Wed, 7/8/15

Tue, 7/21/15

Harden the Production Environment

8 days

Wed, 7/22/15

Fri, 7/31/15

Execute a Simulated Migration

10 days

Mon 8/3/15

Fri, 8/14/15

Cutover to Production Cloud

8 days

Mon 8/17/15

Wed, 8/26/15


7 days

Thu, 8/27/15

Fri, 9/4/15

PMP Meeting

1 day

Mon 9/7/15

Mon 9/7/15

19 days

Tue, 9/8/15

Fri, 10/2/15

Final checks and verification

3 days

Tue, 9/8/15

Thu, 9/10/15

Documentation & User Manual

3 days

Fri, 9/11/15

Tue, 9/15/15

Perform Adaptive Maintenance

3 days

Wed, 9/16/15

Fri, 9/18/15

Perform Preventative Maintenance

3 days

Mon 9/21/15

Wed, 9/23/15


7 days

Thu, 9/24/15

Fri, 10/2/15

20 days

Mon 10/5/15

Fri, 10/30/15

Testing

Deployment Face

Maintenance

Create Research Final Report


