TPF Development Process Flow

Major Project* Process Steps

• Project Inception • Research and Design Solution• Construction• Testing• Production/Implementation• Project Closedown• Maintenance/Clean up

* Projects include both new development, problem resolution, and maintenance/PUT upgrades

Detail - Project Inception

• Project assignment• Project Database containing

– Name– Description– Components to be modified/recompiled (programs, macros, headers, pilots,

alters, etc.)– Requirements – Load dates and contents of each– Testing results at each test level– Project estimate (schedule, manpower, etc)

• Project plan - ?• Approval processes

– Approvers– Acceptance at team transitions– Reviewer approval– Rejection processing

• Built throughout the project• Subprojects

Detail - Research & Design Solution

• Develop requirements• Research tools

– Xref– Scan– Component history– APAR data

• Develop High level design• Develop Detail design• Obtain Approvals as required

Detail - Construction

• Checkout from SCM to HFS• Toolkit

– Edit/modify/merge– Compile/assemble– Create test loads

• Check in to SCM from HFS• Synchronize with project data as

required

Detail - Testing

• Define levels of testing– Unit, system, package, integration, QA, etc.– Customizable

• Target test environments• Process for moving components into each

level of testing– Control/Promotion process– Build method (User build, module copy, built by test

group, etc)

• Creation and manage test scripts

Detail - Production/Implementation• Release management• Promotion process

– User driven, change team driven, coverage driven, etc

– Load creation– Load staging– Link to TPF system

• Pass load data to TPF (version, revision, SCM location of source, etc)

• Pass success data from TPF (accepted, fallback (member/packet), etc)

• Update project data base

Detail - Project Closedown

• Copy staging to production• Update production source (SCM, work

libraries)• Document post project review

– Schedule variance– Manpower variance– Problem logs following implementation for x

period of time

• User workspace clean up• Project data base archival