Project Framework Outline

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT
ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS
DCP0085 – Application Development and Support Page 1


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 and
caters for the two alternative approaches in creating an application - either custom-built development or a package solution.

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. The
above diagram illustrates the phases making up the total process and the remainder of the document deals with the individual phases, firstly in summary form
then 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 the
implementation of either a packaged software product or the development of a custom-built application.


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 from
the 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 the
work will be managed. It identifies the requirements to be provided by the application and it also identifies the requirements of the project such as
documentation, specifications and project governance structures.
Prerequisites for this Phase:
● Identification of a business problem or opportunity that can be addressed by an application system


● 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


● Project Execution Plan
● Base Budget
● Suggested Resources
● Business Requirements Document (BRD)
● Traceability Matrix Document (TMD)
1.


Activities Prior to Initiation:
Activity Description Who By

Deliverables


Develop Project Proposal A project proposal form is completed to give an overview of Project Proposal form completed Initiating Officer
Document the problem/opportunity that needs to be addressed.
Project Proposal form approved/rejected by the Business Unit Manager or
initiating Business Unit's management Director or Executive Director
Review Project Proposal The project proposal is reviewed, costed and categorised by The Business Unit decides whether to continue IPPSA and Business Unit staff
IPPSA. A joint review of the proposal and its findings is then with the proposal
held with the initiating Business Unit.


Develop Business Case IPPSA in conjunction with the initiating Business Unit Business case approved/rejected by initiating IPPSA and Business Unit staff
Document completes a business case. Business Unit management
Review business case The Director ISD reviews the business case Business case approved/rejected by Director Director ISD
ISD
IMC Review If a project cost exceeds $50,000 the business case is Business case approved/rejected by the IMC IMC
reviewed by the Information Management Committee (IMC).


Statement of Work This describes the project in a brief outline. Identifies the Statement of Work document no more than 2 Initiating Officer and IPPSA were
stakeholders, a basic timeline and budget. Possible 3rd party pages. needed
stakeholders.
Activities during the Initiation Phase:

Activity Description Deliverables Who By
Initiate Project This establishes the project team, project governance and project Project Sponsor and
● Project team established


management protocols DCP Project Manager
● Project Governance established

● Project management protocols defined
Engagement Review The ERD is used through the life of the project and updated as ● ERD document to form part of the project Project
Document (ERD) needed. It is the repository of project description, stakeholders, library. Manager/Business
brief proposal of solution and brief architectural description, Analysis


account for post support and maintenance costs
Develop Project Plan / The project plan establishes how the project will be executed and ● Project plan completed and approved by Project Manager
Base Budget delivered. It is the key document to clearly communicate to all project steering committee
stakeholders the scope, objectives, reporting and resources. For
more information refer to the project plan template. ● Base Project Plan & Budget 55-70%
● Required Resources
● Project Management $


● Implementation Training $
● Post Imp Support $
● Maintenance & PA Costs 15-20%
“Go” or “No Go” At this point the customer needs to decide if the project is to move ● Sign off on the decision to “Go” or “No Go” Stakeholder and
forward or not. Contractor
Develop Project Execution For larger projects with a large number of tasks a project ● Project execution plan completed and DCP Project Manager
Plan execution plan may be necessary. The project execution plan


approved by project steering committee
Business Requirements The BRD is used to capture the functional and non-functional ● The BRD completed and approved by IPPSA
Document (BRD) requirements of the project. It answers one question. “What does project steering committee and stakeholders
the client want?” This needs to be written in a language for
business users with flow diagrams. The stakeholders need to be
able to read and understand that the contactor understands what
is needed.


Phase Sign Off Single page indicating that the phase has been completed and ● Signed document from stakeholders and DCP Project Manager /
indicating the requirements being locked down. contractors indicating satisfaction of phase Stakeholder
completion
2.
Tasks That Must Be Completed to Complete This Phase:
● Project Plan and Budget Updated


● 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


The purpose of the design phase is to define the application features and operating environment specifications to fulfil the operational, usability, and business
requirements identified in the Initiation Phase. This includes designing the application and establishing non-functional requirements such as security and
accessibility.
Standards and Guidelines Applicable to this Phase:
● Software Development Standards
● Solution Design Document (SDD)

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


● Issue / Change Register
3.
Activities:
Develop Solution Design The application design should be developed and Contactor
Design completed
Document (SDD) documented according to BRD. The document details how


the application will be designed to achieve the requirements
contained in the BRD.
Traceability Matrix The TMD needs to be updated and all requirements in the Updated TMD Contactor
Document (TMD) BRD need to be cross referenced to the SDD
Review SDD The SDD will be reviewed by the Stakeholder and where SDD approved and signed by Stakeholder and IPPSA, project manager,
needed by IPPSA.. contractor and IPPSA were needed Contactor, stakeholders


Develop Technical This document will specify the infrastructure required and Infrastructure design approved by ISD Contactor, IPPSA
Requirements Document the infrastructure design.
(TRD)
Data Migration Plan (If If data needs to be migrated from existing systems a plan Data Migration Plan completed Contactor IPPSA
applicable) will be developed on how this will be performed. It will also
need to take into account data quality issues. Data Migration Plan approved by IPPSA


Develop Business Testing These are script of tests which are to test both the workflow Scripts that will be used for sign off of the Visual Contactor
Scripts and business logic of the application. Proto Type as well as final testing of the
application when it has been developed.
Visual Proto Type (VPT) The visual proto type needs to be a close representation of A clickable proto type of the proposed Contactor
the proposed solution. Interfaces and imagery needs to be application with all required graphics
developed, designed and implemented so the Software
developers have no need to create any of the visual


interfaces of visual outputs
4.
● Project Plan and Budget updated
● Infrastructure Design approved by ISD


● 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


The develop phase involves the production of the software application and the establishment of the environment it will operate in.
Standards and Guidelines Applicable to this Phase:
● Software Development Standards
● Business Requirements Document
● Solution Design Document


● Traceability Matrix Document (Updated)
● Full Business Test Scripts
● User Manual
● Administrators Manual
● Software Development and Standards manual
● Project Status report


5.
Activities:
Wherever possible the development will be broken down into feature sets Contactor
Develop Application
which implement a full set of functionality which are developed and then ● Code developed according to the Coding Standard
Features and Components Guidelines
integrated with the other feature sets.
(Application development)
● Code is reviewed and checked after completion


The software package will be modified to incorporate the custom features Contactor
Develop Custom Features
required. Software coding may be required or otherwise the package will be ● Code developed according to the Coding Standard
(Software package) Guidelines (if applicable)
modified using it’s in -built customisation functionality.
● Code or changes are reviewed and checked after
completion
Undertake Configuration This involves keeping track of all different versions of the code base. The Contactor
Source code version control
and Change Management management and control of the application code during the development
phase is essential to ensure code quality. Object Management


Library management
Perform unit testing This involves the testing of a component or module to verify its correct Testing completed and results recorded Contactor
operation.
Perform system testing When all the components or modules have been completed and individually Contactor
Testing completed and results recorded
tested they will be assembled and tested as a complete system
Perform Integration testing Integration testing involves verifying the operation of the application as it will Contactor, IPPSA
Testing completed and results recorded


be implemented such as testing the interfaces to other systems and
connections to external agencies. This may or may not be required
depending on the design of the application.
Develop Administrators The administrator’s manual needs to be completed. This must detail how an Administrators manual completed Contactor
Manual application administrator would manage the application.
Test results endorsement The project steering committee will endorse the results from all the testing Test results endorsed Project Steering Committe


6.
● Code completed and tested
● Unit testing completed
● System testing completed
● Integration testing completed


● 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 the
Initiation phase i.e. that all the required functionality is present and working correctly.


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)


● Administrators manual completed
● Test Plan
● User Manual
● Updates to requirement due to issues and changes


● Application Support Plan
● Implementation Plan
● Training Plan
● Project Status Report
7.
Activities:


Develop test plan A test plan will be developed outlining the test requirements and resources. It will Test Plan completed Contactor
detail how the system will be tested.
User Acceptance Testing User acceptance testing involves the verification of the correct operation of the System functions as designed Stakeholder
application. This is typically carried out by the Business Unit using the test plan.
Testing results signed off by project steering
committee


Performance and Stress This involves the verification of the operation of the application under load. Testing completed and results recorded Contactor
Testing Performance testing is required if the technology is new or the design is complex, it
has been untested over the WAN, or there is some doubt as to the performance or
impact of the application.
Test Data Migration (If If existing data needs to be migrated to the new system the process to achieve this Data migration tested Contactor, IPPSA and
applicable) will be tested. Stakeholder
Test signed off by IPPSA and Business Unit
Pre Production Testing This is a final test of the application after all other testing is completed. This test System functions as designed Contactor


verifies the correct operation of the system in an environment that is a replica of Testing results signed off by project steering
the production environment. committee
Develop application support A support plan will be developed detailing the support requirements and resources Application support plan completed Contactor, IPPSA
plan
Application support plan approved by IPPSA
Develop Implementation Plan An implementation plan will be developed detailing the implementation Implementation plan completed Contactor, ISD
requirements and resources
Implementation plan approved by ISD


Develop Training Plan A training plan will be developed detailing the training requirements and resources Training Plan completed Contactor, Stakeholder
Develop User Manual The user manual and training material will be developed User Manual completed Contactor, Stakeholder
Training material completed
Steering Committee All test results and documentation will be endorsed by the Project Steering Test results and documentation endorsed Project steering
Endorsement Committee 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


production committee's satisfaction they will decide if they wish to move the application into production. Committee
production.
8.
● User acceptance testing completed


● 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


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)


● Pre production testing completed
● Approval from steering committee to move the application into production
● Implementation Plan
● Application Installation Guide
● User Manual


● Training plan and materials
● Project closure document
9.
Activities:


Conduct Administrator All application administrators must be trained in all administrative tasks Administrator training completed Contractor
training they need to perform to ensure the correct operation of the application
Conduct User training All application/software users must be trained in the correct operation of User training completed Stakeholder
the system to ensure the planned benefits of the system are realised.
Production A final check must be made to ensure all application/software Documentation completed Contractor’s Project Manager
implementation documentation is correct and up to date prior to the production
implementation request. Change request raised IPPSA


A change request will be raised by IPPSA to move the Final production test Business Unit
application/software into production on a date/time agreed by the
Business Unit.
A final test will be conducted on the application/software in the production
environment prior to declaring it 'live'
Post production At a suitable point soon after the application/software has gone live in System functions as designed Contractor’s Project Manager
verification production verification will take place to check that the application is
functioning correctly and there are no major issues for users. These Project steering committee decides if remedial action


results will be reviewed by the steering committee and a decision made if required
any remedial action is required to fix defects.
Project Closure & Post If the post production verification shows the application/software is Project closure document completed Project Manager & DCP
Implementation Review functioning correctly with no issues and all documentation is complete, the Project Manager
project closure document can be completed. This document is presented Steering Committee to formally close the project
to the project steering committee and a formal decision is made to close
the project.


● Administrator training completed
● User training completed
● Application/software moved into production and 'live'
● Post production verification testing completed
● Project closure document completed


● 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 maintenance
services 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 or
functionality e.g. technical or functional enhancements, corrective adjustments or emergency fixes.

● Project formally closed by Steering Committee
● No documents applicable to this phase
10.
Activities:


Post production At suitable time intervals verification should take place to check that the application is System functions as designed Business Unit,
verification functioning correctly and there are no major issues for users. These results should be reviewed Application
by the application administrator(s) and Business Unit management and a decision made if any Business Unit decides if remedial action required Administrator
remedial action is required to fix defects.
Decision to After a period of time the post production verification may reveal that the application is no Decision to upgrade/replace/retire application Business Unit,
upgrade/replace/retire longer providing business benefit or is proving difficult and /or costly to maintain. At this point a Application
application decision may be made by the application administrator(s) and Business Unit management that If upgrade or replace a proposal is submitted Administrator
the application should be retired, upgraded or replaced. If the application is to be upgraded or If retirement a request is made to IPPSA


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

● Proposal submitted to upgrade or replace application (if applicable)


● 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 longer
delivers the business benefit on which its initial justification was based.
● Request made to IPPSA to retire the application or software


● No documents applicable to this phase
11.
Activities:


ISD will coordinate the decommissioning of the application/software from
the Department's infrastructure. All system data, application code and
Application/software
documentation will be archived and stored for future reference. A
● Application/software archived
ISD
decommissioning
date/time for the decommissioning will be organised and agreed to by the ● Application/software removed from infrastructure
application administrator(s).
Terminate licence and All contracts associated with the application for software licensing and ● All software licensing and support contracts IPPSA & Business Unit
support contracts support will be terminated terminated


● All system data, application code and documentation archived and stored
● Application/software removed from the infrastructure


Project Framework Outline

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Project Framework Outline

Caricato da

Copyright:

Formati disponibili

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

Activity Description Who By

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

ATTACHMENTS READ AND KEEP THIS PART ATTACHMENTS

ATTACHMENT READ AND KEEP THIS PART ATTACHMENT

DCP0085 – Application Development and Support Page 1