30.01.2015 Views

u3Zgz

u3Zgz

u3Zgz

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

These materials are the copyright of John Wiley & Sons, Inc. and any<br />

dissemination, distribution, or unauthorized use is strictly prohibited.<br />

Chapter 5: Ten Steps to Take toward PaaS 43<br />

Step 4: Figure Out What<br />

Your Requirements Are<br />

Create a set of requirements with consideration for pop-up<br />

concerns:<br />

✓ What language do you prefer to work with<br />

✓ How much abstraction do you need<br />

✓ Do you want a platform that automates many of the routine<br />

tasks in both development and deployment<br />

✓ What type of middleware is already in use and what middleware<br />

services do you need<br />

✓ How much integration do you need to do with other<br />

public or private environments<br />

Getting the answers to these questions makes your selection<br />

process a lot easier.<br />

Step 5: Put Together<br />

an Evaluation Team<br />

A PaaS environment can have a dramatic change in how your<br />

organization develops software, so you don’t want to make<br />

a decision on your own. A PaaS environment touches many<br />

parts of the business, so put together a team that represents<br />

all the key constituents and stakeholders to include representatives<br />

from development, quality assurance, and operations.<br />

Step 6: Conduct a Pilot Project<br />

Identify a project that’s well-defined and can show the development<br />

and operations team how well PaaS supports the development<br />

of a business project. You may want to try several PaaS<br />

environments so you can experience different approaches.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!