SDLC PresentationJanuary 2011

Page 2

Agenda

• Introduction

• End to end review of SDLC process

• Detail review of Prototype design stage

• Review prototype design stage deliverables list

• Additional SDLC documentation

Page 3

Introduction

• Key features of SDLC

– UTi SDLC process is collection of Agile, Iterative, prototyping methodologies and best practices from HCL, Infosys.

– Uses Continuous Integration and Testing(Automated) methodologies that helps in identifying integration issues early.

– Uses Time boxing(Sprints) for early realization of high value features

– Helps with faster realization of prioritized requirements

– Uses parallel cross functional teams concept to achieve Time to Market goal for meeting the FF System Development timelines.

Page 4

Introduction

• Items still need to be done as part of SDLC

– MDM(CIM tool) implementation approach for SDLC

– Need to expand on QA activities and engagement process with UST Global.

– Expand on Continuous Integration, Configuration management, Change management processes.

Page 5

Introduction

• Key Success factors– Team work with cross functional teams

– Identifying issues early

– Pro-activeness

– Technical skills

– Working on right things; meeting deliverable expectations

– Stable technology platform, environments

– Continuous improvements

Page 6

SDLC (Level 1)

Page 7

Stage 1 – Foundation work

Page 8

Stage 2 – Prototype team assignment

Page 9

Stage 3 – Prototype Design

Page 10

Stage 4 – SOW Sign off

Page 11

Stage 5 – Development, QA

Page 12

Stage 6 – Validation of Code

Page 13

Stage 7 – Integration testing

Page 14

Stage 8 – Quarterly UAT

Page 15

Prototype design Stage

Objectives

Primary Objective within prototype stage is to elaborate requirements, produce detailed design artifacts that include outputs from tools like TIBCO Business Studio, Business works, Blaze etc. There will be some code skeletons produced as needed.

Ready for offshore to code quickly.

“Proof of concepts” are identified and conducted to reduce any architectural risks if necessary.

Page 16

Prototype Stage 3 - Planning

Page 17

Prototype Stage 3 - Execution

Page 18

Sample representation of multiple tracks/streams

Page 19

Prototype Team Methodology

• Prototype Teams will run with Agile like concepts• Team determines how much time is needed – Sprint 2 to 4

weeks long• Sprint planning at the start of each sprint – Stage 3

planning• Daily stand ups – 15 minutes to see where we are at• Daily task updates – primary way to track progress• Sprint Reviews – Progress report and demo to

stakeholders• Sprint Retrospectives – Team reviews opportunities to

improve• All Stories and Tasks are tracked in RTC, daily report

Page 20

Prototype Deliverables

• SOW• Prototype Specification

– Data Models – Logical, Physical and sample data– Functional Model– ARIS Model– iRISE Model– Business Studio Diagram/Link– Function Work Steps

• Functional Data Elements• Service Requirements• Routing/Entitlements• Notifications/Escalations

– Non-Functional Requirements

Page 21

Additional Deliverables to Development

• Reference Architecture / Theory of Operations• Solution Architecture• Glossary• Rules Catalogue• Requirement Traceability Matrix• Definition of Terms – EA Principles doc• Global Style Sheet• Global Error Message• Global Navigation• Common Services Reference• User Interface Requirements & Guidelines

Page 22

SDLC documentation

Find SharePoint link SDLC in Home Page – http://myuti.teams.go2uti.com/FreightForwarding/default.aspx

• SDLC Process• Prototype Specification, SOW template• Deliverables from SDLC Stages and templates• RACI• Roles and responsibilities(Product Owner, PM, Track

Lead, BA, EA, Dev, QA, EIM, etc..)• Product backlog Management process• Sprint Planning, Retrospective, review documentation• FAQ