CT071-3.5-3-DDAC - Designing Developing Cloud Applications v1

DDAC Individual Assignment Page 1 of 7

Level 3 Asia Pacific University Of Technology And Innovation 2014

CT071-3.5-3-DDAC - DESIGNING & DEVELOPING CLOUD APPLICATIONS

INDIVIDUAL ASSIGNMENT

Intake :

Lecturer :

Date Assigned : Week 4

Date Due : Week 16

LEARNING OUTCOMES

At the end of this assignment, you should be able to:

1. Demonstrate the understanding of cloud computing in its various forms and how Microsoft Azure fits in the cloud computing space.

2. Analyze why organizations want to run applications on the cloud. 3. Explore the Azure SDK and DevFabric development environment. 4. Write and deploy an ASP.NET Web application (Web Role) to Azure. 5. To architecturally design efficient applications for the Microsoft Azure Platform

BUSINESS NEEDS

Based in Luton, England, easyJet is the largest airline in the United Kingdom and the fourth-

largest carrier in Europe. It operates 685 routes and sells 61 million tickets annually. Building

on its reputation for providing great service at low cost, the airline wanted to improve the

customer experience without adding staff or IT infrastructure.

Offering new features, including the ability for customers to choose their own seats, was a top

priority. However, easyJet faced several challenges in implementing a new solution. The airline

outsourced its IT infrastructure, and operated with a lean team of IT professionals. It needed a

delivery platform that would be affordable, easy to manage, and highly scalable.

Were really good at handling the kind of scale that involves huge sales and seasonal peaks,

says Bert Craven, Enterprise Architect Manager at easyJet. But its more difficult to manage

unpredictable factors like weather conditions and external industrial action. When those things

occur, the parts of our infrastructure designed to give real-time information come under real

pressure.



Initially, the airline looked at deploying a seat allocation solution on the same on-premises

platform that it used for its reservation system. However, it discarded the idea when it realized

that building a new; high-availability infrastructure across two data centers would be too costly

and time-consuming, with too many uncertainties about scalability and workload.

Not only that, but the Common Use Terminal Equipment (CUTE) infrastructure designed and

developed SITA is very difficult to scale to the fluctuating needs of the travel industry. We

have to tell airports months in advance how many desks we need to handle passenger load,

Craven says. Its a real capacity-planning challenge.

easyJet wanted to explore new, low-risk options for expanding online services. Its all about

making travel easier and more affordable for our customers, while being able to deliver features

quickly, says Heath Roylance, Senior Project Manager at easyJet. We need to be really agile

and adaptable.

The vision was to have easyJet agents roaming around check-in areas with mobile devices.

While passengers could still drop bags at traditional fixed locations, they could also look for

agents wearing bright orange easyJet shirts who would check them in if they hadnt already

checked in on the Internet, print their boarding passes, check and tag their bags, and move them

right to security without having to wait in a single line. Agents could even book a rental car for

passengers or provide other services from the handheld device.

The following provides a list of the most significant goals and requirements:

Provisioning: You must be able to provision the application for the new tenant.

Maintainability: You must be able to upgrade the application and perform other maintenance

tasks while multiple tenants are using it.

Monitoring: You must be able to monitor the application at all times to identify any problems

and to troubleshoot them. This includes monitoring how each tenant is using the application.

Availability: Individual tenants want the application to be constantly available, perhaps with

guarantees defined in an SLA. Again, the activities of other tenants should not affect the

availability of the application.

Scalability: The application scales to meet the demand of individual tenants. The presence and

actions of other tenants should not affect the performance of the application.

Customizability: The ability to customize the application for an individual tenant in various

ways such as adding or removing features, changing colors and logos, or even adding their own

code or script.



CLIENT VISION

easyJet, a leading low-fare airline in Europe, wanted to offer new features without costly

investment in on-premises infrastructure.

REQUIREMENTS

You are required to design and develop a single tenant web solution that allows individual

tenants to view the application as though it was their own on Microsoft Azure for the following

reasons:

1. It was vital that the solution could support extreme fluctuations in activity as there is a significant spike in demand for bookings and reservation during holiday seasons.

2. To be able to scale the solution to meet the needs bookings during peak seasons. 3. To accelerate setup and deployment of solution. 4. Managed solutions to keep costs down. 5. Assurance & reliability through Failover Management 6. Segment Web site Tenants by Host Headers with or without SSL communication

DELIVERABLES & FULLFILLMENT

1. Design & Develop a single tenant web application with the solution to include the existing reservation system to run at on-premises and the seating allocation service to

runs on Microsoft Azure.

2. Consume Azure Storage & SQL Database 3. Consist of 5 - 10 interlinked pages 4. Provide quality content 5. Application deployed to have secure access 6. Customers experience a seamless reservation process with the hybrid cloud booking

solution, including finding flights, choosing seats, and purchasing tickets.

DOCUMENT ATION

The documentation should include the following:

Format: - Type face: Times New Roman/ Arial. Bold face, italic & lines can be used for

emphasizing and to enhance readability.

- Font size: 12(except tittles and headings). - Margins: 1 from the left, right, top & bottom of the edges of the A4 paper. - Spacing: maximum 1.5 lines between texts of a paragraph. - Alignment: justify. - Headers and footers can be used all pages must be numbered accordingly. - Standard cover page as available in learning management system



Recommended Content

- Acknowledgement

- Table of Contents The table of contents should have the topic title and reference page

number attached to each topic.

- Introduction This section introduces your project including the background

information, and objectives, scopes, requirement specifications and a

summary of the major functions or contents of your solution.

- Project Plan This section defines the tasks to be completed, and project schedule.

- Design Cloud Design Patterns Architectural Diagrams Design considerations Modelling

- Implementation Discuss the steps on how you implemented the system.

- Test Plan & Testing Discussion

- Conclusions

- References

- Appendices



SUBMISSION

The completed solution to be published in Microsoft Azure Project documentation (softcopy) in the form of a CD-ROM. The project documentation (hardcopy)

PERFORMANCE CRITERIA

Please refer Appendix 1

PLAGIARISM

Verbatim reproduction of material from external sources (web pages, books, papers, etc.) is not

acceptable. If you are paraphrasing external content (or even your own prior work) or were

otherwise influenced by them while completing your assignments, projects or exams, you must

clearly acknowledge them. When in doubt, add a citation.

ASSESSMENT CRITERIA

The individual efforts will be assessed based on the following criteria.

No Criteria Mark Allocated Score

Documentation

1. Introduction 5

2. Project Plan 10

3. Design & Solution Architecture 10

4. Implementation & Deployment Guide 10

5. Conclusion 5

Implementation

6. Publishing An Application To Azure 10

7. Application Scaling 10

8. Testing Cloud Applications 10

9. Database Hosting On SQL Azure 15

10. Investigate & Analyze Application (Plan, collect,

and interpret diagnostics and instrumentation

data)

15

Total: 100



Grading:

Grade Range

A+ >=80%

A 75-79%

B+ 70-74%

B 65-69%

C+ 60-64%

C 55-59%

C- 50-54%

D 40-49%

F+ 30-39%

F- 20-29%

F 0-19%



APPENDIX 1

Marking

Band Band Description

Ch

ara

cte

ris

tic

s o

f S

tud

en

t A

ch

iev

em

en

t b

y M

ark

ing

B

an

d

80-100 %

Exceptional problem solving with supporting analysis and application development skills

with extraordinary originality and adoption of new tools, platforms, methods & technologies.

Work may be considered for further expansion.

Create Microsoft Azure AD directory tenant as part of your Microsoft Account-based Azure

subscription, create new directory users & register an application to enable Web sign onto

application

75-79 % Outstanding problem solving and application development skills.

70-74 % Excellent knowledge base that supports analysis, evaluation, problem-solving and application

development of discipline with considerable originality

65-69 % Good knowledge base that supports analysis, evaluation, problem-solving and application

development.

60-64 % Satisfactory knowledge base that supports some analysis, evaluation and problem-solving and

application development.

55-59 % Basic knowledge base with some omissions at the level of technology. Restricted ability to

discuss and/or or solve problems.

50-54 % Limited knowledge base. Limited understanding of discipline. Difficulty with problem

solving and application development.

40-49 % Little evidence of knowledge base. Little evidence of understanding of discipline. Significant

difficulty with problem solving and application development.

30-39 % Inadequate knowledge base. Inadequate understanding of discipline. Major difficulty with

problem solving and application development.

20-29 % No evidence of knowledge base; no evidence of understanding of discipline. Total inability of

problem solving and application development.

0-19 %

Awarded for: (i) non-submission; (ii) dishonesty; (iii) in situations where the student fails to

address the assignment brief (e.g.: answers the wrong question) and/or related learning

outcomes

Documents

CT071-3.5-3-DDAC - Designing Developing Cloud Applications v1