2011 © EPAM Systems

www.epam.com

в условиях распределённой команды>

<Разработка и интеграция

hotel chain booking системы

2011 © EPAM Systems

www.epam.com

What is our project about

2011 © EPAM Systems

www.epam.com

New solution

2011 © EPAM Systems

www.epam.com

OTA specification

2011 © EPAM Systems

www.epam.com

The Day platform

Day CQ5 platform

OSGi

(apache Felix)

JCR (JSR-283)(apache Jackrabbit)

2011 © EPAM Systems

www.epam.com

EPAM internal communication model

- Booking Engine

- Tests

(Auto &performance)

- UI

<Kharkov>

- Day CQ

- QA

- UI

<Dnepr>

- Global API

- Content

<Peter>

Teams coordination

<Atlanta>

BA & Consultants

<Minsk>

Business Analysis

<Mexico>

Architect

<NY>

Management

<Toronto>

2011 © EPAM Systems

www.epam.com

Vendors

Area EPAM V1 V2 V3 V4 V5

Design/Solutioning

Functional and Content Requirements (Usecases)

Tech specification and design

Solution Architecture

Build

Content Auth & Publishing

Content Translation

Booking flow engine

Testing

Unit/Assembly tests

Performance

Deployment

Detailed deployment plan

Training and knowledge trans

Stabilization

Project Management

2011 © EPAM Systems

www.epam.com

Avoiding miscommunication

“When you said «hot pussy», I thought you were roasting a cat.”

2011 © EPAM Systems

www.epam.com

Testing

2011 © EPAM Systems

www.epam.com

Production deployment

2011 © EPAM Systems

www.epam.com

What’s next?

2011 © EPAM Systems

www.epam.com

Challenges

New domain area

Developing system from scratch

Requirements

Day CQ platform