Construction, Installation, and Maintenance

Final Delivery – the Go Live / Cut Over PointProcess Overview -- SDLCProcess Overview – Staging environments

Maintenance

Cutover Strategies (the final installation step) Pilot Immediate Phased (geographically or by function) Parallel

Client Project Team Q’s

1. Who are your internal & external users?

2. To whom will you turn over your system at the Go Live point?

3. Who are the developers who will replace you at the Go Live point?

Write your Client Project team name and the answers to these 3 questions

on a flip chart page on the wall.

Due Date RemindersThis week

E-mail David Carter to arrange a code and interface review to be held M 4/27 – F 5/1

Email us today if you want to take Exam 2 if not, both classes next week are Work Days

Delivery 2 due this Friday, 4/24 at 4pmMust give Delivery 2 to client at the regular weekly meeting.

1. Design and perform system test.2. Install components on Production system.3. Conduct user review/acceptance test.

System Test and Installation Overview

Fig. 9.1, p. 484

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System test and installation

User Review

Cutover /Deploy : Put system in production

P

D

C

A

Install / migrate / deploy

Install -- Defined as: transfer tested software to

production environment

aka – Migrate tested software to production environment (from a “sandbox” or from a staging environment); aka Publish; aka Ship – term from Authoria, last class

aka – Deploy tested software so available to users (perhaps change where a url points)

System Testing and User Acceptance Testing Occur in the Last Software Staging Environment

Go Live

Host all software in Austin &

Waltham

Authoria Environments

70 software

engineers

develop

new features

Manual testing of

new features& features

that are noteasily tested

with automation

Automatedregression

testing of entiresystem monthly

Authoria Process

On-going software development: Engineers deliver new features in monthly sprints (aka iterations)

Ship every4 months

Automated regression testing of entire system monthly (800 tests)

Sandbox: On-going software development: Engineers deliver new features in monthly sprints (aka iterations)

Manual testing of new features on-going with new development

as part of “test-driven development.”

Why not release monthly since testing entire revised system monthly?

Industry Perspective of Maintenance – high cost

Forrester Research

– In 2004, 73% of I.T. budgets were spent on maintenance and 27% on new investments

– In 2005, survey respondents expect to spend 76% on maintenance, leaving just 24% for new investments

73 % on maintenance

76 % on maintenance

Maintenance Definition: work performed on an

existing system so the system will continue to meet its objectives

4 types of maintenance:1. System compatibility maintenance (to interface

with a new or enhanced system component)

2. System efficiency and reliability maintenance

3. Emergency needs and error repair

4. User enhancements

p. 499

Maintenance – 2 questions

1. Why does maintenance cost so much ?

2. How can the cost of maintenance be reduced ?

Maintenance Issues & Solutions

Two Approaches to Reducing Maintenance (p. 499-503)

Approaches

Stages

P A D C Eliminate Unnecessary Changes

Get it

the first

right time

Thorough Testing

Reduce Effort of Changes

Design for easy changes

Implement for easy Changes

Cost of errors increases over time.

Error found inrequirements

least expensive

Marcus Merrell of Authoria estimated that a memory leak error found in system testing would have cost $250,000 if found after release.

Finding the leak in system testing cost about $10,000.

Software Testing:Testing Across the Entire Software Development Lifecycle, 2007, by Gerald D. Everett & Raymond McLeod,

Test early, test effectivelyHelp the users review your early development work by

providing a Word template with your questions and specific information about what to test.

Simple Word

doc for review

Date

Review DateUser Acceptance Review FormSystem

Review Prepared by

Acceptance CriteriaApproved by Date

1.

10.

2.

3.

4.

5.

6.

7.

8.

9.

Acceptance Acknowledgement: The undersigned representatives agree that this project, identified above, has been completed in a satisfactory manner.

Information Systems Management User Management

Authorized Signature Date Authorized Signature Date

Title Title

Figure 9.4 User Acceptance Review Form

Go Live & Maintenance Q’s for CP

1. Who are your users ?

2. To whom will you turn over your system at the Go Live point?

3. Who are the developers who will replace you at the Go Live point?

4. What user materials are important?

5. Where should your operations steps go in your support materials?

6. What will the operations be at the Go Live point?

Reuse Opportunities for Del. 2 & 4

Project Charter ItemUser

MaterialsDeveloperMaterials

Web flow diagram

Code & I/O Standards

ERD

System Overview Diagram

DFDs, Context Diagram

User Wish List from Day 1

Activity (Check all that apply)

I. People_____A. Hiring of New Personnel _____B. Training _____C. Formation of Installation Team

II. Procedures

_____A. User Manuals _____B. Technical Manuals _____C. Printing/Distribution of Paper Forms _____D. User Acceptance Review _____E. Removal of Out-of-Date Documentation

III. Data/Information

_____A. Control Procedures for File Conversion _____B. Review of Current Files _____C. Freeze Date and File Conversion _____ D. Update of Converted Files _____E. User Acceptance_____F. Archiving of Old Files

IV. Software_____A. Application Program Library _____B. Backup Program Library _____C. User Acceptance Review _____D. Removal/Archiving of Old Software

V. Hardware

_____A. Electrical Outlets, Cables, etc._____B. Supplies _____C. Device Installation

_____Server_____Network_____Printer(s)

_____D. System Security _____Power Backup _____Off-Site Storage _____Access Restriction_____E.Acceptance Review

_____F. Removal of Old Hardware

Installation Plan Checklist Fig. 9.3 (p. 488)

Existing system

Pilot system

Immediate cutoverPhased cutover

Parallel cutover

Existing system New system

Existing system

New system

Existing system New system

Time

Time

Time

Fig. 9.5, p. 491

a. Pilot System strategyb.Immediatecutover

c.Phasedcutoverd.Parallel cutover

Cutover Strategies

Installation Strategies

Strategy Risk Cost

Pilot Installation

Medium Medium

Direct Cutover High Low

Phased Installation

Medium Medium

ParallelInstallation

Low High

What is the cutover strategy for your client project team?