AI02 Process Description

Definition of specific statements of functional and operational software requirements, and a phased implementation with clear deliverables.

Design Methods: create and modify design specifications for new information system development projects and to verify them against client requirements. When major changes to existing systems are called for, a similar development process is observed as in the case of the development of new systems.
Data Integrity: Maintain procedures to verify data integrity in application programs
Application Testing: Test application software according to the project test plan and established testing standards before it is approved by clients
User Reference and Support Materials: Prepare user reference and support manuals in electronic format.

Number of applications delivered on time, meeting specifications and in line with the IT architecture
Number of applications without integration problems during implementation
Cost of maintenance per application below the set level
Number of production problems, per application, causing visible downtime or service degradation
Number of solutions not consistent with the currently approved IT strategy
Reduced ratio of maintenance efforts relative to new development

implement active directory and Windows 2000 server for email for all ministries in EBC,
working with MBS lead on a review of market tools for debit/POS and payment, and a recommendation for moving forward,
implementing the recommendations of LIO work in 02-03, viz a web based interface for cluster linkage to LIO geo-spatial data, particularly for INB/MIS and ONBIS, based on acceptance of LIO interface as common component (assumes project approval and funding).

Ratio of actual maintenance cost per application versus the application portfolio average
Average time to deliver functionality, based on measures such as function point or modules
Number of change requests related to bugs, critical errors and new functional specifications
Number of production problems or disfunctionality per application and per maintenance change
Number of deviations from standard procedures, such as undocumented applications, unapproved design and testing reduced to meet deadlines
Number of returned modules or level of rework required after acceptance testing
Time lag to analyse and fix problems
Number or percent of application software effectively documented for maintenance

Software testing in a pre-production environment simulating the production environment will be completed within 20 days of ebcCAB approval, 90% of the time

The acquisition and implementation methodology is strongly supported by senior management
Acquisition practices are clear, understood and accepted
There is a formal, accepted, understood and enforced acquisition and implementation methodology
An appropriate set of automated support tools is available, saving time on software selection by focusing on the best of breed
There is separation between development and testing activities
Key requirements are prioritized in view of possible scope reductions, if time, quality or cost cannot be compromised
The approach taken and effort committed are related to the business relevance of the application
The degree and form of documentation required is agreed upon and followed in the implementation
Compliance with corporate IT architecture is monitored, including a formal process for approving deviations