1 Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will: Understand the systems development life cycle. List.

1

Chapter 15

Systems Development

2

Learning Objectives

When you finish this chapter, you will: Understand the systems development

life cycle. List and explain the pros and cons of

prototyping. Understand how software tools facilitate

the monitoring and controlling of systems development.

3

Learning Objectives Recognize the difficulties involved in

systems development. Be able to list the advantages and

disadvantages of different system conversion strategies.

Understand the concept of systems integration.

4

Why Develop an IS?

Three phenomena can trigger IS development An opportunity (proactive) A problem (reactive) A directive

5

The Systems Development Life Cycle (SDLC)

SDLC approach Life of an IS starts with a need Followed by assessment of functions that

system must have to fulfill that need and Ends when benefits of the system no

longer outweigh its maintenance cost At this point a new system begins

6

The Systems Development Life Cycle (SDLC)

Figure 15.1 The systems development life cycle

7

Analysis Phase

Analysis System

analysis phase is a five-step process…

8

5 Steps in System Analysis Step 1: Investigation

Is there a real need and is it feasible?

Step 2: The Technical Feasibility Study Ensures hardware and software exist to build the

system

Step 3: The Economic Feasibility Study Benefits of the system weighed against the cost

Step 4: The Operational Feasibility Study Determines if system will be used as intended

Step 5: Requirements Definition Specific requirements/features of system defined

9

The Design Phase

Figure 15.4 Phases in systems design

10

Phases in Systems Design Logical Design

Translation of user requirements into detailed functions of the system

Physical Design Construction Systems Testing

11

Logical Design: Business Processes

Figure 15.6 A flowchart describing a sales bonus system

12

Logical Design: Business Processes – For Real

H. MeasurePerformance and

Report

Field

F. Execute Account/Territory Plan andManage Partners

Field

E. Create Account andTerritory Plans

Field

D. Identify and ProfilePartners

Field

C. Assign Partners toPortfolios and PAMs/

PTMs

Field

B. Define andRecommend

“Managed” PartnerCriteria

Corporate

A. Define partnerstrategy

Corporate

Annually Quarterly

G. Lead ManagementSystem Onboarding

Field

Periodically as PAMs or partners are added or changed

13


Esc

ala

tio

n A

ge

nt

60Escalate product,program, license

61Can EA resolve? Yes

67Escalate to program

manager

62Respond to CSR withresolution/information

No

MS

Pro

ject

Ma

na

ger

69Receive escalation

via email (Kona)

70Need additional

information?

71Can PM resolve?

72Respond to EA w/

resolution information

74Communicate

infodesk response toEA

73Create and submit

infodesk case

Cu

sto

mer

Tel

esa

les

Yes

Yes

No

E

53Product/Licensingquestion?

No

54Create SR 55

Complaintacknowledged &

resolved?

57Escalate to EA

No

56Enter resolution, SR

is closed

58Receive SR

64Escalate complaint to

Program Manager(MS Contact)

59Complaintresolved?

65Complaintresolved?


is closed

68Escalate complaint to

US ComplaintManagement Team

Yes

Mic

roso

ft U

S C

MT

eam

75Identify solution andcontacts customer


is closed

Yes

No

63Contact customer

Who is the contactfor complaint

management?

Need specificescalation path

identified for flow.

No

No

Yes

Yes

14


15


16


17

Logical Design: Data Flow Diagrams

18

Systems Testing The idea is to try and break the

system Programs to run code Human users try and ‘outsmart’ the

system Stress Testing

Often it is one of the most tempting phases to reduce or cut from project plan

19

Implementation Phase

Implementation (also called delivery) consists of two steps: Training Conversion

Parallel Conversion Phased Conversion Cold Turkey Conversion Pilot Conversion

20

Strategies used to convert from one IS to another

21

System Support Phase

22

Additional Topics

Prototyping, Project Management…

23

Prototyping

Systems developed using an iterative process Purpose is to develop a working model as

quickly as possible, which can be tweaked and revised

Significantly shortens systems development backlog

Can increase risk of incompatibility and other unforeseen mishaps

24

Prototyping

Figure 15.12 In prototyping, refinement of the system continues until users are satisfied.

25

Prototyping

Figure 15.13 When to prototype and when not to prototype

26

Computer-AidedSoftware Engineering

Computer-Aided Software Engineering (CASE tools) System development programs that ease

and speed design and construction of new ISs

Application generators I-CASE tools Rapid Application Development (RAD)

27

Project Management Project Management Tools

Project Evaluation and Review Technique (PERT) PERT chart shows events, required activities,

and relationships Advantage: Communication of

interdependencies among activities Gantt Chart

Represents activities and start and completion times, but not the relationships among activities

Advantage: Simple and linear

28

Dimensions of Project Management

29

Project Management

Project Management Goals Complete the project on time Complete the project within budget Meet requirements Meet expectations

30

Project Management

Project Management Functions Communication Management Schedule Management Quality Management Financial Management Resource Management

31

Systems DevelopmentLed by End Users (SDLU)

JAD: An example of User-led Systems Development Joint Application Development (JAD):

method to be used in SDLU Uses six-step process to take the team

through planning and design

32

Systems DevelopmentLed by End Users (SDLU)

Figure 15.17 The six steps of JAD

33

JAD Critical Success Factors All participants must be committed to JAD

process. Customers and IS people must agree on project’s

scope. Sponsor must be supportive and involved. Team members must be empowered decision

makers. Business objectives must be clearly defined. Business process must be understood. Team members must be able to meet two or

more days per week. Members must be committed to the team.

34

Systems Integration

Takes a look at the information needs of an entire organization (or a major division)

Analysts integrate existing systems so that: Data can flow more easily among

business units. Users can access different types of data

via a single interface.

35

Systems Integration

Siebel

External Sources

SYSTEM

PartnerAccount Mgr

SYSTEM Functionality• Manage partner account/contact

and customer data• Evaluate existing managed

partners• Select new partners to manage• Fiscal year planning with each

partner• Measure and evaluate partners• Enhanced opportunity pipeline

management capabilities

Siebel’s Role• Opportunities

created within Siebel

• Sends opportunity and associated data to SYSTEM

Partner Functionality• Participate in fiscal planning

process• Manage their account and

contact profile including extended attributes like competencies and solutions

• Manage their opportunities (accept, reject, claim, return, update and close)Other Data Sources

• Sales• Product Data•Customer data

Partner UI

Partner UI

Customer System

Daily Synchronization

Manual feedas needed

Configurable Feed

Weekly Feed

36

Two Real World Examples Revisited

1. Susan’s Training Wheels: MAX

2. Current Hitachi Consulting Methodology

37

Phase II: World Class Implementation!

• Planning & Preparation

– Not an easy task… Sample Work Plan

• Functional Ownership

• Integrated Business Process Redesign

• Fast Application Implementation through Prototyping

– Base Design Prototype

– Integration Prototype

– Model Workplace

600 Performance Measurement & Benefits Tracking

MAX Methodology Phase II: Design and Implementation

1000 Detail Design & Integration

800 Process Design and Preparation

900 Base Design Prototype

1100 Model Workplace

120

0 C

uto

ver

PR

OC

ES

SS

YS

TE

M

TRAINING

100 Project Management and Facilitation

200 Change Management & Communication

Ext

en

de

d T

ea

m K

icko

ff

BuildDesignSetup•Config.

•Test Data

Build Test

Scenarios

Unit Test

System

Report, Modification &Interface Gap

Analysis & Design

Organizational Transformation

MockConver-

sion

Integ-rationSetup•Config.•Static Data

Regression Unit Test

•Dynamic Data

IntegrationTestPrep.

Report, Modification &Interface

Development

ConversionTesting & Validation

SuperUser

Training&

Testing

IntegrationTesting

Report, Mod. & InterfaceValidation

Conversion Design & DevelopmentStatic---------------------------------->Dynamic

System Performance Assessment

StressTest/

Perfor. Tuning

RegressionTest

Validate Cutover/ Fallback

Plan

ProcessOptimization

Validate To-Be

Detail Design

Documentationand Process Tool Development

Pilot Testing of To-Be Processes

AddressIntegration

Issues

ReviewCompletedAnalysis

To-Be ProcessStrategy &Approach

BestPracticeReview

High LevelProcess Design

ProcessImplementation

Workplan

Validate To-BeApproach& Design

DetailProcess Design

Install Hardware

& Software

Project Team

ApplicationTraining

Config-uration

Preparation

39

Base Design IntegrationModel

Workplace

Fast Implementation through Prototyping

40

Process Design and Preparation

What• Preparation for the first configuration of the

application & high level process definitionGoal• To establish the road map for subsequent

phaseDeliver• Extended Team Kickoff• Install Hardware & Software• Project Team Application Training• Configuration Preparation• Review Completed Analysis• To-Be Process PAVA• High Level Process Design

800 Process Design and Prep.

Ext

en

de

d T

ea

m K

icko

ff

ReviewCompletedAnalysis

To-Be ProcessStrategy &Approach

BestPracticeReview

High LevelProcess Design

Install Hardware

& Software

Project Team

ApplicationTraining

Config-uration

Preparation

41

Base Design Prototype


Workplace

42

Base Design Prototype

What• Testing discrete transactions,

inquiries, reports within each module

Goal• 90% of the business requirements

configured, detailed processes defined

Deliver• Unit test plan• Conversion, interface plan• Application Gap Analysis• Report development matrix• Process/ long lead matrix• Detailed design

900 Base Design Prototype

BuildDesignSetup•Config.

•Test Data

Build Test

Scenarios

Unit Test

System

Report, Modification &Interface Gap

Analysis & Design

Conversion Design &

Development

ProcessImplementation

Workplan

Validate To-BeApproach& Design

DetailProcess Design

43


Workplace

Integration Prototype

44

Detail Design and Integration

What• Building on Base Design Prototype to

create an Integrated system

Goal• Verify that the processes and system

will support the business across interfaces

Deliver• Regression Unit Test• Report & Interface Development• Super-User Training & Testing• Conversion Testing & Validation• System Performance Assessment• Integration Testing• Report & Interface Validation

1000 Detail Design & Integration

TRAINING

Integ-rationSetup•Config.•Static Data

Regression Unit Test

•Dynamic Data

IntegrationTestPrep.

Report, Modification &Interface

Development

ConversionTesting & Validation

SuperUser

Training&

Testing

IntegrationTesting

Report, Mod. & InterfaceValidation

System PerformanceAssessment

Validate To-Be

Detail Design

Documentationand Process Tool Development

AddressIntegration

Issues

Pilot Testing of To-Be Processes

45

To-Be PAVA

Process Inventories

Detailed Designs

UNIT Test Plans

To-Be Brown Papers/RACI

Integration Test Plans

Training Manuals

User Documentation

Business Case Requirements

Life Cycle of Implementation Documentation

46


Workplace

Model Workplace

47

1100 Model Workplace

TRAINING

MockConver-

sion

StressTest/

Perfor. Tuning

RegressionTest

Validate Cutover/ Fallback

Plan

ProcessOptimization

Pilot Testing ofTo-Be Processes

Model Workplace

What• Full Business Simulation• Stress Testing & TrainingGoal• To fine-tune cutover procedures and verify

potential impacts Deliver• System Performance Assessment• Mock Conversion• End User Training• Stress Test/Performance Tuning• Regression Test• Validate Cutover/Fall Back Plan• Process Optimization• Pilot Testing of To-Be Processes

System PerformanceAssessment

48

Summary

• Planning & Preparation

• Functional Ownership

• Integrated Business Process Redesign

• Fast Application Implementation through Prototyping

– Base Design Prototype

– Integration Prototype

– Model Workplace

49

Critical Success Factors

• Fast Implementation through Prototyping• Drive to Critical Path / Milestones• High Performance Team — Challenged to Succeed

– Committed the BEST PEOPLE– Winning Attitude– Support for Risk Taking– Ownership at ALL LEVELS

• Scope Control• Test Thoroughly• No Looking Back

Phase I: Mobilize Project

Phase II: Analyze Situation

Train Project Team

IdentifyGaps and

Constraints

Prepare Simulation / Design

Environment Review Functional

Requirements

Develop Project Plan / Conduct

Kickoff

Inventory Inputs and Outputs

Inventory Manual Procedures

Inventory Data Conversion

Requirements

Plan Business Process Simulation

Review Technical Infrastructure Requirements

Inventory Interface Requirements

Sample Service Offering: Vanilla ERP Implementation(1 of 3)

Conduct As-Is Interviews Identify

Desired Changes

Dev

elop

Bus

ines

s C

ase

Monitor Budget / Plan / Scope

Execute Communications Plan

• Work plan• Schedule• CARE documentation• etc.

• ??

Phase III: Design Solution

Phase IV: Develop Solution

Design To Be Processes

Define Data Usage

Finalize Roll Out Approach

Develop and Install Technical Infrastructure

Define Training Approach

Configure Software for Simulation

Define Testing Approach

ID Gaps, Enhancements, Workarounds Define Organizational

Approach

Develop Work

Program for Develop Solution

Sample Service Offering: Vanilla ERP Implementation continued (2 of 3)

Use

r S

igno

ff o

n D

esig

n

Ite

rativ

e

Design Interfaces

Design Data Conversion

Define Customware Development Approach

Define Performance Measures

Define Conversion Approach

Con

firm

Bus

ines

s C

ase

Define Rollout Approach

Code and Unit Test Customware

Develop and Document Procedures

Develop Training Materials

Finalize Software Config for Testing

Prepare System Test Plan

Develop Data Cleansing Approach

Collect / Cleanse Data

Test Converted Data

Prepare Development Environment



• Work plan• Schedule• CARE documentation• etc.

• ??

Phase V: Deliver Solution

Phase VI:Support & Improve Solution

Prepare Production Environment

Document Test Conditions & Data

Transfer to Production

Support

Monitor Key Performance

MeasuresPrepare for Testing

Conduct Testing (Unit,

String,System, User)

Document and Sign Off Test Results

Perform Data Conversion

Conduct Training

IdentifyIssues

Design and Test

Improvements

Monitor Production

Sample Service Offering: Vanilla ERP Implementation continued(3 of 3)

App

rove

/ C

utov

er to

new

Sys

tem



1 Chapter 15 Systems Development. 2 Learning Objectives When you finish this chapter, you will: Understand the systems development life cycle. List.

Documents

systems design slide

systems development

real slide

directive slide

system support phase

system step

step process slide

sales bonus system slide