NRM SDLC - Design

Design is the effort required to clearly document how the solution is going to look and act to satisfy the business requirements.

  • Whiteboard sessions are scheduled at various stages of the project to ensure that the direction being taken is following Natural Resource Sector IM/IT standards.

    The purpose of a whiteboard session is to bring together the necessary business and technical resources to determine the best approach and best practices to:

    • Address a business need using information technology;
    • Address a technology issue relating to an application or service provided by the Information Management Branch (IMB); or
    • Achieve decisions that will allow the work to go forward.

    There are different types of whiteboards carried out at different times within a project as identified in Usage Within the SDLC.

    • Feasibility Whiteboard – is used to define the business problem and identify potential system solutions that may be viable within the Ministry standard deployments.
    • Technical Whiteboard – is used to confirm the design solution identified by the vendor will fit within the Ministry standard deployment patterns and confirms the technology and servers to be used.
    • Warehouse Whiteboard – is used to get agreement from both DataBC and the operational resources on what and how data will be replicated to the data warehouse.


    Standard booking procedures are available at:


    A whiteboard checklist is available to assist in asking the right questions and documenting the results of the whiteboard sessions:

    Deliverable Requisite

    A whiteboard session is mandatory for all project complexity levels.

    It is expected NRS Projects continue using Whiteboards and Technical Advisory Group (TAG) and Architecture Review Board (ARB) is not intended to replace either Whiteboards or TAGs. If at a Whiteboard or TAG, a solution is recommended that does not conform to NRS architecture, the project must proceed with an ARB Submission and receive exemption before advancing with that solution.


    There is no sample currently available.

The Request for Change (RFC) identifies the components being included in an application release that will impact one of the Natural Resource Sector technical environments.

An RFC should be initiated as early as possible via the JIRA tool.  RFCs are reviewed every Thursday, and must be submitted at least three (3) business days in advance.  RFCs must be updated and resubmitted for each target environment (Integration, Test, and Production).  An emergency RFC may be handled outside of this policy on an exception basis.
Deployment constraints:
  • Integration environment – Daily
  • Test environment – Monthly (third Wednesday of each month)
  • Production environment – Monthly (third Tuesday of each month)

Standards / Guidelines

  • The standard is to complete the RFC form in JIRA and submit the form to the Release Manager for review and approval.


  • The template is only available as a JIRA form.

Deliverable Requisite

The Deliverable is mandatory for all projects.


  • Samples are not available at this time

Quality assurance is a way of preventing mistakes or defects and avoiding problems when delivering solutions or services. It must address both the management and the product of the project, and should be planned into the project and product, and define and set the appropriate standards and identify how these standards are to be met.

Quality should focus on:

  • Fitness for use
  • Fitness for purpose
  • Conformance to requirements
  • Customer satisfaction

For additional information:

For a project, specialized workstations, hardware or software may be required.  These must be ordered using the NRS Business Service Desk request forms.

Standards / Guidelines

The standard is to submit your request using the form linked below.


The NRS Business Service Desk website (BC Government Access Only) contains the forms required for each of these requests.

Use the “Workstation Requests” form for workstation requests, use the “Hardware & Software Requests” for any non-workstation IT hardware requests or workstation software requests. 

Complete the forms with as much detail as possible (for example needs, source (website), vendor, model number, quantity, etc.).  If there are any questions, someone will follow up with you to clarify your request.

Deliverable Requisite

Workstation Hardware Request forms are optional for all project complexities unless there is a need for equipment.


There are no samples available