Natural Resource Ministries System Development Life Cycle
We are currently working to update and restructure the NRM SDLC Site. Please contact us if you have any questions.
IIT Standards Enquiries: IIT.Standards@gov.bc.ca
The System Development Life Cycle (SDLC) is the process for conducting system and application development and maintenance in the natural resource ministries (NRM).
It guides information management and information technology vendors, staff, and clients in the creation and maintenance of information management systems.
SDLC Standards
SDLC standards are defined as “compliance expectations” for a defined activity - typically supported by processes, procedures, guidelines, templates and forms. Complying with a defined activity ensures stakeholders operate in a predictable and repeatable manner and that they generate a consistent and correct quality product (output) without negative impacts. The processes, procedures, guidelines, templates, and forms are provided to assist stakeholders navigating the SDLC but are not necessarily prescribed or mandatory.
Each section below outlines a category of activities or tasks that are performed during the SDLC. These apply to all types of projects and/or products at any stage of their lifecycle - with a focus on outcomes as opposed to tools or methodologies. Each activity/task will outline a standard for compliance and provide an overview with any required support documentation (guidelines, templates, etc.).
The categories have been listed in logical order; however, you may need to visit or re-visit certain categories in the order that makes the most sense for the approach taken.
If you are involved in a system/application development/maintenance initiative or product with the NRM, you should familiarise yourself with all the categories below.
SDLC Categories
Planning
Activities that need to be completed prior to a project beginning.
Initiation
Plan and define the scope, approach, budget and work plan.
Privacy
Establish specific privacy policies and procedures.
Security
Ensure plans and processes are in place to manage the risks for applications and information.
Application Transition to Operations
Identify transition requirements and confirm delivery of application.
Requirements
Document business needs to design appropriate solution.
Design
Document how the solution will satisfy the business requirements.
Build
Implement the solution into a delivery environment.
Test
Migrate delivered components into test environment, execute user acceptance test plan.
Deployment and Implementation
Migrate built and tested components into a production environment.
Operations and Sustainability
Product stabilization, post implementation review, achieving project material, and releasing team members from the project.
