Travel ERP

Design Approach
June - 2013

2009. Cox and Kings

Contents
Introduction
State of Union for WP1
Design Approach
Design Steps
Design & Construction Deliverables
Risk and Dependencies
Action Items

Introduction
Cox and Kings (C&K) wishes to develop a complete homegrown
Travel ERP solution, which flexible, rich in functionality and will
provide them an edge over competitors, in addition to the
ownership of the IPR. NIIT Technologies (NTL) has been engaged
with C&K for the Requirement Gathering , Design and
Construction for this program.
Currently the Requirement Analysis phase is in progress and we
will soon move the next phase i.e. Design, Construction and
Release
An iterative based approach is been agreed between C&K and
NTL, whereby the entire Travel ERP project is been divided into 8
different Work Pack.
This document provides high level understanding of the design
approach for Work Pack 1. This approach will be further refined

State of the Union for WP1

Use case status
26 - Signed of
19 - Work in progress
8 - Pending

Business Architecture
System/Product wide Process Model - Pending

Technical Architecture

Architecture Work in progress

Stack Work in progress
Framework API - Pending
Best practices - Pending

Information Architecture
System/Product wide Data mapping Work in progress

Approach

Design Prerequisites
Architecture
Signed-off Use Case
Signed-off NFR
Technology Stack
Business Process
Model
Information Model

u
itect
h
c
r
A
re
&
w or
e
m
Fra k

Architectures
(Logical,
Deployment, Process,
Data)
API Contracts
Framework
Principles
Guidelines
Best Practices

Design
Design
SDD Template
Collaboration Diagram
Object Model
Data Model
Screen UI
API Calls (WF, Rules)
Data Mapping
Packaging Structure
Test Plans

Construction
& Testing

IDE & Tools

Coding
Dev Environment
CI Builds
JUnit, Selenium,
Manual

Activities
Architecture/Design

Construction

Testing

KT & Screen UI
Collaboration Diagrams
Object Model, Data Design
Business Logic, Validation
Review, Approval, & Sign off

Architecture Finalization NFR,

Context Diagram, Security,

Template, I18N, Error, Workflow,
Scheduling, Logging, Audit, Reviews,
Approval

Framework API Contracts - Workflow,

Rules, Logging, Scheduling, Reviews

Framework Services
Dev Environment- SVN, CI
Builds, JUnit Reports, Quality
checks

Construction - Coding, Reviews, Demos, Defect fixes, CI, JUnit

System Test Plans, System and Regression Test Cases: Review Approval &
Sign off
Selenium/ Manual Tests

Deliverables
The deliverable of Design phase is the System Design Document.
This document will be jointly reviewed by C&K and NTL and sign
off will be provided by C&K. The sign off will form entry criteria
for Construction phase.
Design

System Context Diagram

Architecture
Collaboration Diagram
Object Model
Data Model
Screen UI
API Calls (WF, Rules)
Data Mapping
Error Handling

Construction
Code, Resources
Unit Test Plans, Results

SIT
Test Plan
Test Cases
Test Results

Risks and Dependencies

Framework API coming late in the cycles will impact
design
Design will depend on API contracts of Common areas
Requirement changes in base feature set for
framework will delay design
Achieving Performance NFRs without load & stress
testing is a risk
Design prerequisites
Architecture
Signed-of Use Case
Signed-of NFR
Technology Stack
Business Process Model
Information Model

Action Items

Item

Owner

KT of Use Cases

Solution Architect

Screen UI

UI Designer

Technical Architecture

Technical Architect

Data Architecture

Data Architect

Framework API
Contracts

Technical Architect

Design

Technical Architect

Dev Environment

Technical Architect

Test Plans

Test Manager

Thank You

2009. Cox and Kings