Software Build and Test
Building of applications where circumstances are such that no existing or purchased solution is available to meet the needs of the ebc client Ministries.
Development of systems include:
- web development changes to existing systems,
- prioritization of enhancements, fixes and changes to existing systems,
- maintenance of systems,
- IT vendor/contract management
Environmental maintenance includes:
- establishment of build and test environments
![[To top of Page]](../../images/up.gif)
Development of meaningful activities on schedule and within budget with a minimum of ensuing incidents attributable to untested or poor quality software code, or evaluation.
- applications implemented within negotiated timeframes, 90% of the time.
How are we doing ?
- business unit participation in developing and approving requirements
Costs are paid through an annual appropriation to the ebcIT Division through the Ministry of Labour as negotiated during the annual government-wide fiscal budgeting process.
6. Dependencies
- commitment to a systems development methodology such as Rational Unified Process (RUP) is considered best practices
- the Ontario Government maintains technology standards for hardware and software usage. ebc Cluster is expected to operate within this standards.
- pre-production (UAT) testing is conducted using the Peterborough server facilities
- Requirements Management - System requirements allocated to software are controlled to establish a baseline for software engineering and management use.
Software plans, products, and activities are kept consistent with the system requirements allocated to software.
- Software Project Planning - Software estimates are documented for use in planning and tracking the software project. Software project activities and commitments are planned and documented. Affected groups and individuals agree to their commitments related to the software project.
- Software Project Tracking and Oversight - Actual results and performances are tracked against the software plans. Corrective actions are taken and managed to closure when actual results and performance deviate significantly from the software plans. Changes to software commitments are agreed to by the affected groups and individuals.
- Software Subcontract Management - The prime contractor selects qualified software subcontractors. The prime contractor and the software subcontractor agree to their commitments to each other. The prime contractor and the software subcontractor maintain ongoing communications. The prime contractor tracks the software subcontractor's actual results and performance against its commitments.
- Software Quality Assurance - Software quality assurance activities are planned. Adherence of software products and activities to the applicable standards, procedures, and requirements is verified objectively. Affected groups and individuals are informed of software quality assurance activities and results. Noncompliance issues that cannot be resolved within the software project are addressed by senior management.
- Software Configuration Management - Software configuration management activities are planned. Selected software work products are identified, controlled, and available. Changes to identified software work products are controlled. Affected groups and individuals are informed of the status and content of software baselines.
- a "Master Blueprint"is developed for implementation of new application.
- Application Sizing - determining the optimal availability and capacity requirements for the application when in production
8. More Information
- Responsible for Service Management, delivery and accuracy of this Catalogue item: Ray Nakano, Director, Application Systems
- HP - Relationship to Release to Production
Printable Version