Construction

Client Project – questions & tips for project completion

Construction as part of methodology Phased SDLC, Preliminary Construction, Fig. 7.2, p.425 Agile methodsPhased SDLC, Final Construction, Fig. 8.1, p. 452Phased SDLC, System Test & Installation, Fig. 9.1, p. 484

Environments for A-D-C Loops & Last Two Phases1st Environment: Developers’ sandbox Fig. 7.6 , p. 429 – 431 Environments 2, 3, & 4: Figures 8.2 & 9.2, p. 454 & 486 Install (aka Deploy, Migrate, Publish)

Terms reviewed

Post Project Charter Process Questions

1. Does it make sense to continue client meetings with your entire team ?

2. Does it make sense to have pairs or individuals meet at different times ?

3. What are the expectations of your IT supervisors (aka professors) ?

4. What are effective ways to reduce scope creep at this point ?

Client Project Tip 3Client Project Tip 3: : Check major deadlines link for “Summary of Deadlines” on top of Schedule page on web.

Date Responsibility

Fri. Nov. 13 Last day to arrange Delivery 2 code & I/O review with TA

Mon. Nov. 16 Last day to request option to take Exam 2

W. Nov. 18 Code complete date (nothing to turn in)

W. Nov.18 – W Nov. 25 Meet with TA for Delivery 2 code & I/O review

Fri. Nov. 20 @ 2 p. m. Interim Status Report (Delivery 2) -- hard and soft copies

Wed. Dec. 2 Team Presentations in class (Delivery 3)

Thurs.Dec.10 @ 2 p. m. Final Delivery (hard and soft copies) and peer evaluation

The Preliminary Construction Phase (Chapter 7)

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System test and installation

User Review

Cut Over: Put system in production

P

D

C

AUser

Review

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

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

Construct / create / test – training Construct / create / test – test data

Test hardware capacityTest conversion / migration

Client Project Team Q’s1. 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 ?

4. What is best for what users ?a) User manuals or on-line help only ?b) QRGs for more than 1 type user ?c) Developer manuals or only QRGs?

So the code – test iteration is a partnership.

. . .

Code

Test

Listen

Code

Test

Listen

Code

Test

Listen

Design

Code

Test

Listen

Design

Design

Design

Test data and scripts are written for every new feature and added to the test process.

The test process grows as the code grows.

Problem 1: For large systems continuous iterative testing will take too long.

Preliminary Activities

Sprint Zero:

Problem 2: Agile Methods Ignore the Reality of Contracts

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System testand installation

User Review

Cut Over: Put system in production

P

D

C

A

Two solutions to problems with contracting & large-scale testing

1. Have set dates & meaningful deliveries for user reviews, including a final review.

2. Plan a final integration test and construction phase with adequate time for completion.

Credera’s Time-Boxed Development Process

1st Iteration

took 2 weeks,

then followed with 6 1-week iterations

The 7 deliveries were to the client’s staging environment for testing, not directly to the public.

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System testand installation

User Review

Cut Over: Put system in production

P

D

C

A

1 and 2. Construct and test production-ready database and programs.3. Obtain additional hardware.4. Prepare the facility.5. Test hardware components.6. Complete documentation.7. Train participants and users.

The Final Construction Phase

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System test and installation

User Review

Cut Over: Put system in production

P

DC

AFinal StageGate

Hardware & Software Components Variations

Before final construction a Windows environment on PCs is often the best ROI for development

“Porting from Windows to Linux or another operating system and SQLserver to the mainframe DB2 is common for Final Construction and Production Systems. We do this all the time.” Chip Morgan, Sungard

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System testand installation

User Review

Cut Over: Put system in production

P

D

C

A

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

System Test and Installation Overview

Preliminary investigation

Analysis

Design

Preliminary construction

Finalconstruction

System test and installation

User Review

Cut Over: Put system in production

P

D

C

A

Construction, Installation, and Maintenance

Client Project – questions & tips for project completion

Construction as part of methodology Phased SDLC, Preliminary Construction, Fig. 7.2, p.425 Agile methodsPhased SDLC, Final Construction, Fig. 8.1, p. 452Phased SDLC, System Test & Installation, Fig. 9.1, p. 484

Environments for A-D-C Loops & Last Two Phases1st Environment: Developers’ sandbox Fig. 7.6 , p. 429 – 431 Environments 2, 3, & 4: Figures 8.2 & 9.2, p. 454 & 486 Install (aka Deploy, Migrate, Publish)

Software Staging Environment # 11. Development sandbox – hardware where

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

Custom Development

PurchasedSoftware

Open SourceSolution

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

Fig. 7.6, p. 430

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?

Fig. 7.6, p. 430

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 ProblemComplexity 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 19

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

USAA has a 5th Staging environment

Test complete system

Test system with interfaces

with other systems.

From Fundamentals of Software Integration, by Kay Hammer and Tina Timmerman, 2007

Environments & why layers of code are so important

Graphic overview of Graphic overview of layerslayers

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.

Implementation, Construction & Installation - terms & timing

Users (& Operations staff) take over

Unit test

Integrated test

Systems test of all components, incl. volume testing

User acceptance test

p. 424

Checklist of Implementation Activities

1. Perform preliminary construction• Prepare the physical facilities• Install the hardware• Install software tools and code the software or obtain application software• Build test files• Prepare training materials and documentation

2. Perform preliminary testing• Create a test environment• Test components• Test system

3. Perform final construction• Revise software in developer’s environment• Build production files• Document procedures• Hire and train personnel

4. Perform final testing• Test subsystems• Test system

5. Perform system installation• Transfer tested software to production environment• Transfer production files to production environment

6. Obtain management approval of completion7. Cutover to new system

Fig. 7.4,

p. 427

Installation Activities Span Multiple Phases

Plan and prepare the physical facilities

Preliminary Construction Phases (Iterative)

Final Construction

Phase

System Test and Installation Phase

Plan, obtain, and install the hardware

Obtain software tools and code the software or obtain application software

Build the test files and production data base

Prepare training materials and documentation

Figure 7.5, p. 428