Project Approach

INTRODUCTION

SCOPE

The scope of this document is to help who? to deliver what? by how?

The extent of the area and subject matter that this document deals with is relevant to the
SMART Objectives in the following areas

Area:

Subject Matter:

Planned Outcome:

PROJECT OBJECTIVE STATEMENT

By April 2022, and within approved budget, we will deliver

A: BEFORE

B: DURING

C: AFTER

APPROACH

SYSTEMS ENGINEERING

CONCEPT OF OPERATIONS

Deliverable: Concept of Operations document

Rationale: The Concept of Operations (CONOPS), is both an analysis and a formal

document that describes how an asset, system, or capability will be employed and
supported. It is developed to bridge the gap between the Business Need Statement and the
Outcome based Requirements Specification Document (RSD) by identifying the capabilities
needed to satisfy the business need and fills the gaps expressed in the business needs
statement, and to assist in identifying and selecting balanced solutions in the Options
Appraisals.

The CONOPS is a communication vehicle to inform all stakeholders of the intended uses
and methods of support of assets, systems, or capabilities. It enables an early assessment
of the fit of a solution in its operational environment and its expected performance in
achieving business goals and tasks. Conversely, the CONOPS is a user-oriented
 Project Approach

framework within which users and acquirers can identify potential solutions that can be
appraised, evaluated, and traded-off.

 Concept of Operations: Citizen centric focus to understand and direct the delivery
of products, processes, and services to achieve the service improvement objectives.
 Requirement Gathering and Analysis − All possible requirements of the system to
be developed are captured in this phase and documented in a requirement
specification document.
 System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.
 Implementation − With inputs from the system design, the system is first developed
in small programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality, which is referred to as Unit Testing.
 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system
is tested for any faults and failures.
 Deployment of Service − Once the functional and non-functional testing is done
(Acceptance Test Pass), the product-service solution is deployed in the NHSS
operational environment
 Post Go-Live Support − Issues and opportunities for service improvement arise in
the operating environment. A range of operational support services are required,
typically classified as:
o Reactive support: e.g. Helpline/Call Centre Support
o Proactive support: e.g. System Upgrade
o Consultative support: e.g. 3rd Party Software Development
o Project Management e.g. Transition to a new or changed capability

REQUIREMENTS

Deliverable: Outcome Focused system requirements specification document

Rationale: Flowing from the CONOPS, the Outcome Focused system requirements may be
understood and optimised to achieve mission success

The CONOPS provides actionable insight to inform the Outcome Focusedi system
requirements specification (SRS).

Deliverable: System architecture and high level design document

Rationale: TBA

SYSTEM DESIGN

Deliverable: Programme Plan and Plans for each project in the dossier of projects

Rationale: TBA
 Project Approach

IMPLEMENTATION

Deliverable: Programme Plan and Plans for each project in the dossier of projects

Rationale: TBA

VALIDATION

Deliverable: The set of Test Procedure and Test Results Documents (UNIT, INTEGRATION,
and SYSTEM Testing)

Rationale: TBA

OPERATIONS

Deliverable: Standard Operating Procedure (SOP) Document

Rationale: TBA

SUPPORT

Deliverable: Service Level Agreement document(s)

Rationale: TBA

APPENDIX
i
Outcome focused specifications describe the outcomes and benefits expected by Health Boards from solution
providers. The approach recognises that Health Boards specialise in understanding and defining the problem to be
solved, and the solution providers specialise in solving the problem. In accordance with innovation-centric public
procurement procedures, all in the ‘innovation partnership’ project collaborate to realise benefits and outcomes of
strategic significance for all.