Project Delivery Process D656

D656 - Modify Non-Package Software

DEFINITION

Modify existing applications or build new software tools to meet new functional and technical requirements in a way which is consistent with the overall software design, and avoids adverse impact on other application functions.

SUMMARY

The purpose of this activity is to make modifications and enhancements to existing application software according to specifications developed earlier (see processes D600, D602, D604, D606).  Custom development may also be used to build new facilities such as data interfacing or conversion / validation tools.

This activity consists of steps to analyse existing code, develop new code, supplement existing code with the necessary new code, and test and correct the modules.

PATH PLANNING GUIDANCE

This process is optional - used where custom modifications or additions are required.

DEPENDENCIES

Prerequisites (Finish-Finish):

• Create detailed specifications for non Application Software IT development work (D600)
• Finalise interface design (D602)
• Finalise data conversion routine design (D604)
• Finalise design for functional modifications / additions / custom reports (D606)

Dependent procedures (Finish-Finish):

• Integration testing (see D800)
• Technical testing (D810)

RECEIVABLES

• Specifications (D600, D602, D604, D606)
• Definition of IPs/Topics (DoT)
• Relevant technical IPs
• Existing system software code and documentation
• Site technical and operations documentation
• Vendor technical document
• Site standards and procedures
• Processing Control Specifications

DELIVERABLES

• Working and unit tested modules and documentation
• Source code with documentation
• Object code
• Test results (file dumps, screen prints, control reports, test reports, etc)

TOOLS

• Custom Development Guidelines

DETAILED DESCRIPTION OF TASKS

Worksteps

Custom development work will be sub-divided into separate groups of activities according to the applications or modules being worked upon.  Within each of these there are three main aspects:

• Analyse, code and test modification (each modification)
• Create/review application test plan
• Integration test application

Analyse, code and test modification (each modification)

Modify program code according to physical design specifications to produce software that performs the required functions efficiently and in accordance with overall application design, that is maintainable, that blends with other modules, and that produces acceptable test results.  The approach and documentation will normally be defined by the client organisation’s standard practice for custom development.

The purpose of this activity is to modify (or add to) and unit test the code for an individual program or module of an existing application.  The complexity of each module modification will depend on the detail design specifications and the agreed upon guidelines for development.

Worksteps:

• Analyse existing design and code
• Modify program code
• Test for correct coding, i.e., a clean compile
• Unit test and correct in accordance with unit testing guidelines.

Information sources

• Existing program code and documentation
• Site technical and operations documentation
• Vendor technical documentation
• Documentation of existing systems
• Site standards and procedures
• Management and technical staff
• Unit Test Plan/Script
• Development Procedures
• Development Team Access Privileges
• Documentation Catalogue
• Modifications Specifications
• Physical Data Structures
• System Tables
• Test Data

Create/review application test plan

Develop comprehensive test scripts containing detailed cases to thoroughly test designed application or modifications in addition to testing for any negative effects on unchanged routines.

The purpose of this task is to create or update the integration plan for the application to be tested by adding test cases and scripts to reflect the design and development changes that have occurred over the course of this phase.

Information sources

• Application documentation and test plans
• Site technical and operations documentation
• Vendor technical documentation
• Existing program code and documentation
• Site standards and procedures
• Integration Test Plan/Script (System Design)
• Modification Specifications
• Unit Test Plan/Script
• Unit Test Cases
• Physical Data Structures
• System Tables
• Test Data
• Program Source Code
• System Control Language Instructions

Typical contents of the test plan and script may include:

• Name and ID
• Module reference ID
• Test sequence of events
• Description of script event
• Tester
• Evaluation criteria
• Comments.

Typical test case documentation may contain:

• Test script ID
• Test event description
• Test sequence number from script
• Detailed test condition and input values specified
• Expected results.

Integration Test Application

Confirm that the modifications made to an existing application have had the desired effect.  Note that the integration tests concerning the existing/modified applications may be conducted as a separate programme to the mainstream integration testing of the new package-based system, however, the final results should also be integration tested with the full new system solution.

The purpose of this activity is to test an existing application to which modifications or enhancements have been made.  In addition to determining whether the newly modified application performs added or changed functions correctly, this testing activity should be designed to detect unanticipated changes in application functions unrelated to the current change.

Information sources

• Application documentation and test plans
• Site technical and operations documentation
• Vendor technical documentation
• Existing program code and documentation
• Site standards and procedures
• Applications support staff
• Management and technical staff
• Integration Test Plan/Script
• Development Procedures
• Development Team Access Privileges
• Documentation Catalogue
• Modifications Specifications
• Physical Data Structures
• System Tables
• Test Data
• Program Source Code
• Existing Application Module
• System Control Language Instructions
• Integration Test Plan/Script