project framework outline

8/8/2019 Project Framework Outline

1/56

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS






DCP0085 Application Development and Support Page 1




DCP0085 Appli ca tion Development and Support Page 7











2/56








ATTACHMENT 5 Methodology and Development Life Cycle

Figure 1 - Methodology and Development Life Cycle Attachment 8 for exploded version

Overview

This process covers the complete life-cycle of an application from the initial identification of the business need to the eventual retirement of an application andcaters for the two alternative approaches in creating an application - either custom-built development or a package solution.
















3/56








This document follows a top-down approach by providing the reader with an overall view of the process and the facility drill down for specific detail. Theabove diagram illustrates the phases making up the total process and the remainder of the document deals with the individual phases, firstly in summary formthen in greater detail.

Initiation Phase

The Initiation phase is the point at which a person in the Department identifies that there is a business need or opportunity that may be solved by theimplementation of either a packaged software product or the development of a custom-built application.
















4/56








This is commenced with a Statement of Work which will then form the foundation of the Engagement Review Process. The Statement of Work is created fromthe Project Proposal and Business Case.

The initiation phase starts after the request has been approved and the funding identified. The purpose of this phase is to establish the plan against which thework will be managed. It identifies the requirements to be provided by the application and it also identifies the requirements of the project such asdocumentation, specifications and project governance structures.

Prerequisites for this Phase:

Identification of a business problem or opportunity that can be addressed by an application system
















5/56








Business Case approved by ISD Director or Information Management Committee

Project funds identified and available

Documents Applicable to this Phase:

Project Proposal

Business Case

Project Plan
















6/56








Project Execution Plan

Base Budget

Suggested Resources

Business Requirements Document (BRD)

Traceability Matrix Document (TMD)

1.
















7/56








Activities Prior to Initiation:

Activity DescriptionDeliverables

Who By
















8/56








Develop Project ProposalDocument

A project proposal form is completed to give an overview ofthe problem/opportunity that needs to be addressed.

Project Proposal form completed

Project Proposal form approved/rejected by theinitiating Business Unit's management

Initiating Officer

Business Unit Manager orDirector or Executive Director

Review Project Proposal The project proposal is reviewed, costed and categorised byIPPSA. A joint review of the proposal and its findings is thenheld with the initiating Business Unit.

The Business Unit decides whether to continuewith the proposal

IPPSA and Business Unit staff
















9/56








Develop Business CaseDocument

IPPSA in conjunction with the initiating Business Unitcompletes a business case.

Business case approved/rejected by initiatingBusiness Unit management

IPPSA and Business Unit staff

Review business case The Director ISD reviews the business case Business case approved/rejected by DirectorISD

Director ISD

IMC Review If a project cost exceeds $50,000 the business case isreviewed by the Information Management Committee (IMC).

Business case approved/rejected by the IMC IMC
















10/56








Statement of Work This describes the project in a brief outline. Identifies thestakeholders, a basic timeline and budget. Possible 3 rd partystakeholders.

Statement of Work document no more than 2pages.

Initiating Officer and IPPSA wereneeded

Activities during the Initiation Phase:

Activity Description Deliverables Who By

Initiate Project This establishes the project team, project governance and project Project team established

Project Sponsor and
















11/56








management protocols

Project Governance established

Project management protocols defined

DCP Project Manager

Engagement ReviewDocument (ERD)

The ERD is used through the life of the project and updated asneeded. It is the repository of project description, stakeholders,brief proposal of solution and brief architectural description,

ERD document to form part of the projectlibrary.

ProjectManager/BusinessAnalysis
















12/56








account for post support and maintenance costs

Develop Project Plan /Base Budget

The project plan establishes how the project will be executed anddelivered. It is the key document to clearly communicate to allstakeholders the scope, objectives, reporting and resources. For

more information refer to the project plan template.

Project plan completed and approved byproject steering committee

Base Project Plan & Budget 55-70%

Required Resources

Project Management $

Project Manager
















13/56








Implementation Training $

Post Imp Support $

Maintenance & PA Costs 15-20%

Go orNo Go At this point the customer needs to decide if the project is to move

forward or not.

Sign off on the decision to Go orNo Go Stakeholder and

ContractorDevelop Project ExecutionPlan

For larger projects with a large number of tasks a projectexecution plan may be necessary. The project execution plan

Project execution plan completed and DCP Project Manager
















14/56








approved by project steering committee

Business RequirementsDocument (BRD)

The BRD is used to capture the functional and non-functionalrequirements of the project. It answers one question. What doesthe client want? This needs to be written in a language forbusiness users with flow diagrams. The stakeholders need to beable to read and understand that the contactor understands whatis needed.

The BRD completed and approved byproject steering committee and stakeholders

IPPSA
















15/56








Phase Sign Off Single page indicating that the phase has been completed andindicating the requirements being locked down.

Signed document from stakeholders andcontractors indicating satisfaction of phasecompletion

DCP Project Manager /Stakeholder

2.

Tasks That Must Be Completed to Complete This Phase:

Project Plan and Budget Updated
















16/56








Project Execution plan approved by Steering Committee (if applicable)

Traceability Matrix Document commenced

BRD completed and signed by both contractor and stakeholders

ERD updated with skills and resources

Design Phase
















17/56








The purpose of the design phase is to define the application features and operating environment specifications to fulfil the operational, usability, and businessrequirements identified in the Initiation Phase. This includes designing the application and establishing non-functional requirements such as security andaccessibility.

Standards and Guidelines Applicable to this Phase:

Software Development StandardsDocuments Applicable to this Phase:

Solution Design Document (SDD)
















18/56








1. Architectural Requirements Document

2. Functional Requirements Document

3. Technical Requirements Documen

Business Test Script These are tests which will show that the business logic of the application works as designed.

Infrastructure Design document

Project Status report
















19/56








Issue / Change Register

3.

Activities:


Develop Solution DesignDocument (SDD)

The application design should be developed anddocumented according to BRD. The document details how

Design completedContactor
















20/56








the application will be designed to achieve the requirementscontained in the BRD.

Traceability MatrixDocument (TMD)

The TMD needs to be updated and all requirements in theBRD need to be cross referenced to the SDD

Updated TMD Contactor

Review SDD The SDD will be reviewed by the Stakeholder and whereneeded by IPPSA..

SDD approved and signed by Stakeholder andcontractor and IPPSA were needed

IPPSA, project manager,Contactor, stakeholders
















21/56








Develop TechnicalRequirements Document(TRD)

This document will specify the infrastructure required andthe infrastructure design.

Infrastructure design approved by ISD Contactor, IPPSA

Data Migration Plan (Ifapplicable)

If data needs to be migrated from existing systems a planwill be developed on how this will be performed. It will alsoneed to take into account data quality issues.

Data Migration Plan completed

Data Migration Plan approved by IPPSA

Contactor IPPSA
















22/56








Develop Business TestingScripts

These are script of tests which are to test both the workflowand business logic of the application.

Scripts that will be used for sign off of the VisualProto Type as well as final testing of theapplication when it has been developed.

Contactor

Visual Proto Type (VPT) The visual proto type needs to be a close representation of

the proposed solution. Interfaces and imagery needs to bedeveloped, designed and implemented so the Softwaredevelopers have no need to create any of the visual

A clickable proto type of the proposed

application with all required graphics

Contactor
















23/56








interfaces of visual outputs

4.


Project Plan and Budget updated Infrastructure Design approved by ISD
















24/56








Data Migration Plan completed and approved by IPPSA

Sign off on SDD

Sign off on VPT

Full Written Business Test Scripts

Approval from Steering Committee to progress to the next phase

Develop Phase
















25/56


26/56








Traceability Matrix Document (Updated)

Full Business Test Scripts

User Manual

Administrators Manual

Software Development and Standards manual

Project Status report
















27/56


28/56








Develop Custom Features(Software package)

The software package will be modified to incorporate the custom featuresrequired. Software coding may be required or otherwise the package will bemodified using its in -built customisation functionality.

Code developed according to the Coding StandardGuidelines (if applicable)

Code or changes are reviewed and checked aftercompletion

Contactor

Undertake Configurationand Change Management

This involves keeping track of all different versions of the code base. Themanagement and control of the application code during the developmentphase is essential to ensure code quality.

Source code version control

Object Management

Contactor
















29/56








Library management

Perform unit testing This involves the testing of a component or module to verify its correctoperation.

Testing completed and results recorded Contactor

Perform system testing When all the components or modules have been completed and individually

tested they will be assembled and tested as a complete systemTesting completed and results recorded

Contactor

Perform Integration testing Integration testing involves verifying the operation of the application as it willTesting completed and results recorded

Contactor, IPPSA
















30/56


31/56


32/56








Administrators manual completed

Test results endorsed by steering committee


Test Phase

The test phase ensures that the developed software application or software package meets the functional and non-functional requirements as defined in theInitiation phase i.e. that all the required functionality is present and working correctly.
















33/56








This will be as per DCP Test Strategy Document.


Code completed, commented and tested

Unit testing completed

System testing completed

Integration testing completed (if applicable)
















34/56


35/56








Application Support Plan

Implementation Plan

Training Plan

Project Status Report

7.

Activities:
















36/56









Develop test plan A test plan will be developed outlining the test requirements and resources. It willdetail how the system will be tested.

Test Plan completed Contactor

User Acceptance Testing User acceptance testing involves the verification of the correct operation of theapplication. This is typically carried out by the Business Unit using the test plan.

System functions as designed

Testing results signed off by project steeringcommittee

Stakeholder
















37/56








Performance and StressTesting

This involves the verification of the operation of the application under load.Performance testing is required if the technology is new or the design is complex, ithas been untested over the WAN, or there is some doubt as to the performance orimpact of the application.

Testing completed and results recorded Contactor

Test Data Migration (If

applicable)

If existing data needs to be migrated to the new system the process to achieve this

will be tested.

Data migration tested

Test signed off by IPPSA and Business Unit

Contactor, IPPSA and

Stakeholder

Pre Production Testing This is a final test of the application after all other testing is completed. This test System functions as designed Contactor
















38/56








verifies the correct operation of the system in an environment that is a replica ofthe production environment.

Testing results signed off by project steeringcommittee

Develop application supportplan

A support plan will be developed detailing the support requirements and resources Application support plan completed

Application support plan approved by IPPSA

Contactor, IPPSA

Develop Implementation Plan An implementation plan will be developed detailing the implementationrequirements and resources

Implementation plan completed

Implementation plan approved by ISD

Contactor, ISD
















39/56








Develop Training Plan A t raining plan will be developed detailing the training requirements and resources Training P lan completed Contactor, Stakeholder

Develop User Manual The user manual and training material will be developed User Manual completed

Training material completed

Contactor, Stakeholder

Steering Committee

Endorsement

All test results and documentation will be endorsed by the Project Steering

Committee

Test resul ts and documentation endorsed Project steer ing

Committee

Approval to move to If all testing and documentation has been completed to the project steering Steering Committee to approve/reject move to Project Steering
















40/56








product ion committee 's satisfact ion they will decide i f they wish to move the applicat ion in toproduction.

production. Committee

8.

Tasks That Must Be Completed to Complete This Phase: User acceptance testing completed
















41/56








Performance and stress testing completed (if required)

Pre production testing completed

Data migration testing completed (if required)

Application support plan, implementation plan and training plan completed

User manual and training material completed

Approval from steering committee to move the application into production
















42/56









Implement Phase

The implement phase involves activities necessary to make the tested application available for business use.


User Acceptance Testing completed Performance and stress testing completed (if required)
















43/56








Pre production testing completed

Approval from steering committee to move the application into production


Implementation Plan

Application Installation Guide

User Manual
















44/56








Administrators Manual

Training plan and materials

Project closure document

9.

Activities:

















45/56








Conduct Administratortraining

All application administrators must be trained in all administrative tasksthey need to perform to ensure the correct operation of the application

Administrator training completed Contractor

Conduct User training All application/software users must be trained in the correct operation ofthe system to ensure the planned benefits of the system are realised.

User training completed Stakeholder

Production

implementation

A final check must be made to ensure all application/software

documentation is correct and up to date prior to the productionimplementation request.

Documentation completed

Change request raised

Contractors Project Manager

IPPSA
















46/56








A change request will be raised by IPPSA to move theapplication/software into production on a date/time agreed by theBusiness Unit.

A final test will be conducted on the application/software in the productionenvironment prior to declaring it 'live'

Final production test Business Unit

Post productionverification

At a suitable point soon after the application/software has gone live inproduction verification will take place to check that the application isfunctioning correctly and there are no major issues for users. These


Project steering committee decides if remedial action

Contractors Project Manager
















47/56








results will be reviewed by the steering committee and a decision made ifany remedial action is required to fix defects.

required

Project Closure & PostImplementation Review

If the post production verification shows the application/software isfunctioning correctly with no issues and all documentation is complete, theproject closure document can be completed. This document is presentedto the project steering committee and a formal decision is made to closethe project.

Project closure document completed

Steering Committee to formally close the project

Project Manager & DCPProject Manager
















48/56









Administrator training completed

User training completed

Application/software moved into production and 'live'

Post production verification testing completed

Project closure document completed
















49/56








Project formally closed by Steering Committee

Maintain Phase

Once the application is operational it moves to the maintain phase to ensure the ongoing support and operational availability of the system. The maintenanceservices are delivered based on the support plan and any established service level agreements.

From the maintain phase additional requirements or modifications may be identified which improve the software's stability, performance, operation orfunctionality e.g. technical or functional enhancements, corrective adjustments or emergency fixes.

















50/56








Project formally closed by Steering Committee


No documents applicable to this phase

10.

Activities:Activity Description Deliverables Who By
















51/56








Post productionverification

At suitable time intervals verification should take place to check that the application isfunctioning correctly and there are no major issues for users. These results should be reviewedby the application administrator(s) and Business Unit management and a decision made if anyremedial action is required to fix defects.


Business Unit decides if remedial action required

Business Unit,ApplicationAdministrator

Decision toupgrade/replace/retire

application

After a period of time the post production verification may reveal that the application is nolonger providing business benefit or is proving difficult and /or costly to maintain. At this point a

decision may be made by the application administrator(s) and Business Unit management thatthe application should be retired, upgraded or replaced. If the application is to be upgraded or

Decision to upgrade/replace/retire application

If upgrade or replace a proposal is submittedIf retirement a request is made to IPPSA

Business Unit,Application

Administrator
















52/56








replaced a proposal will be submitted as specified in the Investigation phase. If the applicationis to be retired a request will be made to ISD.

Tasks That Must Be Completed to Complete This Phase: Proposal submitted to upgrade or replace application (if applicable)
















53/56








Proposal submitted to retire application (if applicable)

Retire Phase

The retire phase is the final phase in the life cycle when the application has reached its 'end of life'. An application is retired when the system no longerdelivers the business benefit on which its initial justification was based.


Request made to IPPSA to retire the application or software
















54/56


55/56








Application/softwaredecommissioning

ISD will coordinate the decommissioning of the application/software fromthe Department's infrastructure. All system data, application code anddocumentation will be archived and stored for future reference. Adate/time for the decommissioning will be organised and agreed to by theapplication administrator(s).

Application/software archived

Application/software removed from infrastructure

ISD

Terminate licence and

support contracts

All contracts associated with the application for software licensing and

support will be terminated All software licensing and support contracts

terminated IPPSA & Business Unit
















56/56









All system data, application code and documentation archived and stored

Application/software removed from the infrastructure













