Related Links

Ministry of Agriculture & Lands

System Development Life Cycle (SDLC) Standards

System Development Life Cycle (SDLC) Standards

This document is intended as a guideline for all Application Managers, Project Managers, Project Leaders, Business Analysts, Database Designers and Developers involved in planning, delivering and maintaining applications for the Ministry. For more details refer to the Systems Development Life Cycle Overview (SDLC) document. 

The Ministry Project Manager is responsible for the overall co-ordination of the Quality Assurance of all application deliverables. The Information Management Branch, Business Analyst is responsible for ensuring the application deliverables are quality assured from a technical perspective.

The SDLC Phases for new application development are supported by the Project Management Methodology. The phases also apply to other types of development projects like Warehousing and Application Maintenance as shown below. The only difference being in the amount of effort required for each phase.

Planning
Definition
 Analysis Design Build Implement
Project Management
Warehousing
Maintenance

Note: A listing of all available standards for the Ministry is detailed in the Alpha List of Existing Standards.

Resource
Abbreviation
Business Experts BE
IMB Business Analysts BA
IMB Technical Experts ITE
GEOBC Technical Experts GTE
Application Architects AA
Data Architects DA
Business Data Administrator BDA
IMB Project Manager PM
Development Team DT

Phase
(Click Phase
Name for Purpose)
Deliverable
 Contributes to Deliverable Quality Assures Deliverable Applicable Standard
Business Architecture
Phase 1:
Business Planning		 Conceptual Requirements BE, BA, ITE BE, BA, ITE, as appropriate Conceptual Requirements Standard
Transformation Plan BE, BA, ITE BE, BA, ITE, as appropriate Transformation Plan Standard
Phase 2:
Application Planning		 Software Needs Assessment BE, BA, ITE BE, BA, ITE, as appropriate Software Needs Assessment Standard
Gap Analysis - TBD BE, BA, ITE BE, BA, ITE, as appropriate Not applicable
Business Case BE, BA, ITE BE, BA, ITE, as appropriate Business Case Standard
SDLC
Phase 1:
Project Planning		 Not Applicable Quality Assurance is not actually a deliverable but a guide that must be followed for all deliverables As appropriate Quality Assurance
SDLC Rightsizing Matrix
(329k pdf)		 BE, BA, ITE BE, BA, ITE, as appropriate Not Applicable
Project Charter BE, BA, ITE BE, BA, ITE, as appropriate Project Charter Standards Template
(word doc)
SDLC Checklist
(word doc)		 BA Not Applicable Not Applicable
RFP Template - Contact your BA BE, BA, ITE BE, BA, ITE, as appropriate  
Phase 2:
Definition		 Project Plan
(word doc)		 PM, BE, BA

PM, BE, BA, ITE, as appropriate Project Plan Standard
Phase 3:
Analysis		 Software Requirements Specification(word doc) BE, DT, ITE BE, BDA, AA Software Requirements Specification Standard
Data Conversion Analysis BE, DT BE, BA, ITE, as appropriate

Not Applicable
Phase 4:
Design		 Software Design Description(word doc) BE, BA, DT, ITE BE, AA, DA, BA Software Design Description Standard
Logical Model
 
Physical Model		 BE, BA, DT, ITE DA Data Architecture Standards
Data Conversion Design BE, BA, DT, ITE DA Not Applicable
Phase 5:
Build		 Web Mapping Application Development Standards BE, BA, GTE, DT GTE GEOBC Web Mapping Application Development Standards
Application Code BE, DT, BA AA Java Standards Guidelines
Application Reports BE, DT BE, AA Oracle Reports Standards

Tested Application DT BE, BA Vendor Test Plan
Data Conversion Application DT BE, AA Not Applicable
Phase 6:
Implementation		 User Procedures BE BE, BA Not Applicable
On-Line Help Text BE BE Not Applicable
User Acceptance Test BE, DT, BA BE, BA User Acceptance Plan
User Training Plan BE BE Not Applicable
Implementation Plan BE, BA BA, ITE Not Applicable
Application Delivery and Migration DT, AA, BA AA, ITE Application Delivery Standards

 

PHASE AND PURPOSE

 

Business Architecture

Phase 1: BUSINESS PLANNING

  • Required to identify the current business processes used and the future business processes which may result in changes or the implementation of a new systems project.
  • Produces a Conceptual Requirements document to identify the AS IS and TO BE business models.
  • May also result in a Transformation Plan for a large area which identifies the projects to be tackled over time.

Phase 2: APPLICATION PLANNING

  • Required to identify the high level business requirements which may result in changes or the implementation of a new systems project.
  • Produces a Software Needs Assessment document to identify the high level business requirements which may be used in the production of a Gap Assessment to determine appropriate solution (COTS, Custom Built, Software as a service, etc.)
  • Produces a Business Case document to evaluate the possible solutions and recommend the most feasible based on cost benefit analysis.

 

SDLC

Phase 1: PROJECT PLANNING

  • Required to determine the feasibility of whether the project should proceed or not.
  • Produces a high level overview document of the project which relates to the project requirements and scope.
  • To include requirements for data replication to the warehouse.

Phase 2: DEFINITION

  • Defines what, when, who, and how the project will be carried out.
  • This phase expands on the high-level project outline and provides a specific and detailed project definition
  • This phase assumes that an RFP has been prepared and distributed, a contract project development team chosen and a Project Manager appointed.

Phase 3: ANALYSIS

  • Required to understand and document the user's needs for the system.
  • Documents in detail the scope, business objectives and requirements of the system.
  • Emphasizes what the system is to do.
  • Includes analysis of what data needs to be replicated to the data warehouse.

Phase 4: DESIGN

  • Describes how the proposed system is to be built.
  • The design is specific to the technical requirements the system will be required to operate in and the tools used in building the system.
  • Impacts the build and implementation phases of the SDLC.
  • Describes movement of data between operational databases and the data warehouse.

Phase 5: BUILD

  • Deals with the development, unit testing and integration testing of the system modules, screens and reports and data replication to the data warehouse if required.
  • Carried out in parallel with the development of user procedures and user documentation from the implementation phase.

Phase 6: IMPLEMENTATION

  • Prepare for and carry out the implementation of the developed system through user acceptance testing to full production and warehouse population.