1 st 5 minutes: Fill out Exercise #13 Write your team answers to #1 & 2 on your flip chart

1st 5 minutes: Fill out Exercise #13

Write your teamanswers to

#1 & 2on your flip chart.

Launch Point for Build Phase

Inception Phase(s)

LaunchPoint

Project Charter

Analysis &Requirements

Summaries& Planning

Youare here

Development Production

Youare here

Client Project Deliveries

Delivery 1 – Project Charter P

Delivery 2 – Interim Stage Report

Final Delivery – What you leave for your client (Delivery #4)

Delivery 3 – ~12-minute presentation to class 4/29 or 5/1

Client Project Deliveries: # 2 #4

Delivery 2 – Interim Stage Report & software & test data

Final Delivery – What you leave for your client

#2 is an

early

draft of

Final

Delivery

Focus Shift: across Client Project Deliveries

Delivery #1 Charter Delivery #2 Interim Status Report : big shift in focus

Delivery #2 Interim Status Report Delivery #4 Final Delivery : NO shift in focus

Delivery 2 is an early version of the Final Delivery, plus a planning section.

note: Delivery 3 is a ~10-minute presentation to class on Apr 29 or May 1

Sample PagesIntroductory

PagesincludingPlanning

Table ofContents

ExecutiveSummary

Status Memo

RevisedPlanning

User Interaction

User Materials *

(to Date)

Table of Contents

Sample Pages

Quick ReferenceGuide(s)

Test Materials *

(to Date)

Test Plan

* The table of contents of the user and developer materials will be graded for completeness. The sample pages and the table of contents must be reviewed by the appropriate clients (end-user, user-sponsor, or tech support staff).

The first report section includes plans for completion.

These 3 sections are an early draft of your final delivery.

Test Specs

Software,Pages,

Test data,Environ-ments

1

2

4

Developers’ Materials *

(to Date)

Table of Contents

3

Overview of Delivery 2

Final PagesIntroductoryPages

Table ofContents

ExecutiveSummary

Status Memo

RevisedPlanning

User Interaction

User Materials *

(Final)

Table of Contents

Final Pages


Test Materials *

(Results)

Test Summary

Test ResultDetails

Software,Pages,


1

2

4


(Final)

Table of Contents

3

Overview of Final Delivery

X

The Build Phase

Looking ahead to Production

Construction as part of methodology Construction Iterations (aka A-D-C-R Loops )Final Construction

Environments for A-D-C-R Loops & Final Construction1st Environment: Developers’ sandbox Staging Environments 2, 3, & 4

Development Production

Production Goals:

1. Keep the system running

2. Help users use it

High Level tasks:

3. Operate the system

4. Support the system

5. Identify defects and enhancements

that leads to development work for errors, quick fixes, and enhancements that are termed “maintenance” or may be considered work on “next release”

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

Why does maintenance cost so much

Cost of Change Curve for Traditional SDLC

Scott Ambler’s Figure 1 in http://www.agilemodeling.com/essays/costOfChange.htm

Maintenance:Changes inProduction

Comparison of Power of Bugs to . . .

Steve McConnell, Rapid Development

How can maintenance costs be reduced

SDLC Perspective

How can maintenancecosts be reduced ?

Fixing defects and making enhancements = Maintenance

Maintenance Issues

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

Inception

The Build Phase


Construction as part of methodology Preliminary Construction Iterations Final Construction


Launch Point for Build Phase

Inception Phase(s)

LaunchPoint

Project Charter

Analysis &Requirements

Summaries

Build Iterations Focus on Creating Functionality q

We provide end-to-end services focused on business issues important to our portfolio clients. Our investments and scale are aligned around those issues and industry sectors where we have unique expertise to deliver complete valuable solutions.

Deloitte’s Build Phase

Strategy

Manage

Plan

Design

Build

Sustain

• Provide executable strategy supporting business and technology objectives. Includes assessments, diagnostics, advice, planning, and strategy articulation.Strategy

• Establish a program’s or project’s scoping, timeline definition, resource allocation, and high leveled requirements gathering in tactical, detailed steps. Plan

• Link business and technology through designing enterprise architecture, technology-enabled business operations, technology infrastructure, IT organizations, Centers of Excellence, and reusable methods and tools.

Design

• Configure, extend, and integrate SAP and Oracle industry solutions. Deliver IT solutions in Finance, HR, Supply Chain, and Customer Management. Custom engineer and integrate software using deep industry and technology platform expertise.

Build

• Deliver application stabilization, maintenance and support, and operations management in areas of deep business expertise.Sustain

• Lead oversight, program, and integration management of large-scale technology design, configuration, implementation, merger integration, and cost reduction efforts.

Manage

Build

Sense Corp has 4 Inception Phases:> Assessing> Conception> Initiation> Planning

MIS 374’s Build Phase is Sense Corp’s 10-step Execution

Phase.

Build Iterations

Construct / create / test – web pagesConstruct / create / test – reports

Construct / create / test – code (copy max & edit) Construct / create / test – On-line help & other help

Construct / create / test – training Construct / create / test – database

Acquire/ arrange / test hardware capacityTest conversion / migration

Test Data for Safari Books, 333k

Matc

h te

st d

ata

to e

ach

fun

ctio

nal p

hase

Data Validation Requirements for Safari Books, 333k

Test Specification for MIS 374 – Can opt for variation on 333k spreadsheet

User Testing is key to success

Construct / create / test – web pagesConstruct / create / test – reports

Construct / create / test – code (copy max & edit) Construct / create / test – On-line help & other help

Construct / create / test – training Construct / create / test – database

Acquire/ arrange / test hardware capacityTest conversion / migration

User Testing in Build Iterations – Client Project Example

User Testing in Build Iterations – Client Project Example

Provide user

materialseach

function

Where do the user testing activities fit on the Gantt Chart

Client Project Team Q’s – Data Focus

1. How good is your test data?

2. How will your users test your work(software, training, on-line help, etc ) ?

3. Who will create your production data to be ready for the go live point ?

Final Construction

1. Integrated Testing, Acceptance Testing2. Final Documents for Stakeholders3. (Final) Training4. Deploy / Migrate / Transition to new system

Release (End Game)

Figure 4 and Section 5 in “The Agile SDLC,” Scott Amblerhttp://www.ambysoft.com/essays/agileLifecycle.html

Goal: Transition the system into production

High Level tasks:

1. Final testing of the system

2. Rework

3. Complete documentation for all stakeholders (system and user docs)

4. Deploy the system

Note: this can take several iterations.

http://www.ambysoft.com/essays/agileLifecycle.html

Sample Pages

Delivery 2 is a user test of your materials

IntroductoryPages

includingPlanning

Table ofContents

ExecutiveSummary

Status Memo

RevisedPlanning

User Interaction

User Materials

(to Date)

Table of Contents

Sample Pages


Test Materials *

(to Date)

Test Plan

* Put as much help material as you can directly into your system.

These 3 sections are an early draft of your final delivery.

Test Specs

Software,Pages,


1

2

4


(to Date)

Table of Contents

3

The Build Phase


Construction as part of methodology Construction Iterations (aka A-D-C-R Loops )Final Construction


4 Software Staging Environments1. Development sandbox – hardware where

individual software modules or objects are constructed, tested, and debugged. (This is where unit testing occurs.)

2. Development integration environment – hardware for integration testing

3. Production staging environment – hardware for system testing & user acceptance testing occurs

4. Production environment – hardware for user interaction

Software Staging Environments for MIS 374

Preliminary Construction occurs in “sandbox”– coding and testing in the A – D – C loops

For 374 you will migrate your code from your sandbox to a host site, unless you are already on the host site.

This is the code – test, code – test area.

Integration testing combines modules and tests again.

This is the 333k experience – test data was used for testing in a McCombs folder.

System testing will test the complete system with broader test data. This is the 374 situation.

User acceptance testing is after system testing in contractual situations & 374.

Finally, the system is deployed (or migrated) and goes live (or control is cut over to the new system.)

Do you need to integrate modules before migration?

Build Phase Reading, p. 3

For 374 you will migrate your code from your sandbox to a host site, unless you are already on the host site.

Complexity is a Growing Problem

Infrastructure built with no roadmapArchitecture policy may not existApplications built/bought to support line-of-business needsPoint-to-point connections made on ad hoc basis

MIS 373 - Copyright Edward Doan 2008 41

Production Staging is needed for large public systems – so all 4 environments must be created.

Graphic overview of layers

Basic organization of code shows separation of layers for .vb files

The code review at the Interim Status Report time (i.e. Delivery 2) will be for file organization as well as looking at code commenting, naming, etc.

Late in the development cycle . .“We’re strapped for time,” says Lou, the nervous one on the team. Looking at the Gantt chart he says “we can’t possibly make the July 1 deadline for testing with live data. We’re already three weeks behind.”

As you have better planning skills than Lou, you say “if we push the testing off, the users will be on vacation.” Lou is upset.

Lou suggests “something’s got to go. Let’s see…maybe we can skip unit testing….and do it at system test time.”

What should the team do? What is realistic?