RMS Functional Requirements - Hanford Site

[Pages:20]RMS Functional Requirements

Initiative: REQUIREMENTS MGMT PROGRAM Revision: 00

Date: 05/13/2021 Author: Suzanne Johnson Author: Todd Griffin

1. Functional Requirements Document Overview

Purpose:

This functional requirements document provides the top-level requirements needed for a solution provided to meet the initiative named in the above table. The document provides voice of functional requirements as well as internal requirements. The document is meant to provide a foundation for the initiative and provides priority of requirements where appropriate.

Terminology and Abbreviations:

Terminology & Abbreviations 508 Compliance

Agile

CIO COTS CPCCo DOE DMZ HISI HLMI HMIS IDEA IT PjM PdM RPM RMP RMS RTM

Description/Definition

508 Compliance is shorthand for a law that requires federal government websites to be safe and accessible for people with disabilities. This law covers a range of issues related to assisting people with different kinds of disabilities In software development, agile practices involve discovering requirements and developing solutions through the collaborative effort of self-organizing and crossfunctional teams and their customer/end user. Chief Information Officer Commercial off the shelf Central Plateau Cleanup Company Department of Energy Demilitarized Zone Hanford Information Systems Inventory Hanford Laboratory Management and Integration Hanford Mission Integration Solutions Individuals with Disabilities Act Information Technology Project Manager Product Manager Requirements Program Manager Requirement Management Program Requirement Management System Requirements Traceability Matrix

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

1

SaaS SECB SME SQA UI/UX WRPS

Software as A Service Software Engineering Change Board Subject Matter Expert Software Quality Assurance User Interface/User Experience Washington River Protection Solutions

2. Stakeholders

Customer Stakeholders of the solution:

? (Bullet list of all customers (companies) who will be utilizing the solution) ? U.S. Department of Energy (DOE) ? Hanford Mission Integration Solutions (HMIS) ? Central Plateau Cleanup Company (CPCCO) ? Hanford Laboratory Management and Integration (HLMI) ? Washington River Protection Solutions (WRPS)

Business Stakeholders of the solution

? (Bullet list of internal stakeholders who will provide input to this document. For instance, project management, dev, 508 compliance, UI/UX, SQA)

? Product Management (PdM) ? Project Management (PjM) ? Requirements Program Manager (RPM) ? Cyber Security ? 508 Compliance ? Procurement ? Contracts ? Software Quality Assurance (SQA) ? Enterprise Application Team ? Network Support Team ? Database Support Team ? UI/UX Team ? IT GAB

3. Scope of the solution

(Provide a brief description of the vision for the solution. For initiatives with a business case, section 1.2 could be utilized here. Goal is to refresh the reader on the objective for the solution)

The vision of the project is to implement a site-wide Hanford Requirements Management Program that establishes and maintains a complete requirements dataset that provides bidirectional traceability to implementing provisions, and from those documented implementing provisions back to applicable

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

2

requirement sources. These requirements sources include, but are not limited to, direct contractual provisions; applicable Contract Requirements Documents (CRDs); applicable DOE directives; applicable federal, state, and local regulatory requirements; permit provisions; applicable DOE Standards; applicable Hanford Site standards; adopted industry standards; adopted guidance; enduring commitments from enforcement actions or corrective actions; and demonstrating that applicable requirements are adequately implemented within the Contractor's documented programs, plans, procedures, and/or work instructions.

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

3

4. Functional Requirements

The below table provides an overview of the high-level requirements and represent voice of customer. Priority A means must have, Priority B means nice to have, Priority C means if time allows or low effort required.

ID 4.1 ? 4.8 4.9 4.9.1

4.9.2

4.9.3

Requirement (Top level description of requirement) HMIS Customer Requirements Usability Requirement

Ease of adding / updating requirements

Rationale (Description of need for requirement)

Ease of usability for Stakeholders and Administrators Ensure requirements are captured and kept current

Ease of accepting requirements

Requirements to be assigned to requirement area owners

Actionable Impact Analysis

Ability to determine impact to project documents when requirements change

Priority Risk (A,B,C) (H,M,L)

Mitigation Strategy

Not applicable to vendor.

A

L Select COTS RMS that

provides the ability to

ensure requirements are

easily captures and the

ability to modify

requirements to keep

them current.

A

L Establish structure and

workflow in COTS RMS

that allows for the

identification of

requirements to assigned

owners.

A

H Establish structure to

provide reporting

functionality on the flow-

down of requirements to

project implementing

documents.

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

4

ID 4.9.4

4.9.5

4.9.6 4.9.7 4.9.8 4.9.9 4.10

Requirement

Rationale

Priority Risk

Mitigation Strategy

Ease of linking

Ensure users can easily create

A

L Establish structure and

requirements to

traceability between their

workflow to allow users to

implementing

assigned requirements to

create traceability

documents, including implementing documents.

between requirements

drag and drop linking. Rules can be assigned to

implementing documents.

ensure linking is performed in

Include this as part of the

the correct direction.

training for users with edit

capability.

Requirement reuse

Ability to capture the same

A

L Establish structure and

requirement in more than one

workflow in COTS RMS to

module or project.

allow for same

requirement to be

captured in more than one

module or object/artifact.

Baselines

Ability to take a "snapshot" at

A

L Establish as part of the

a point in time for a particular

workflow process since all

module or project.

COTS RMS provide

baseline functionality.

Suspect Links

Ability to display an indicator

A

L Establish as part of the

that an item may no longer

workflow process since all

correct of complete, because a

COTS RMS provide suspect

change was made to an item

link functionality.

upstream or downstream.

Ease of linking

Ability to create traceability

A

L Establish as part of the

between multiple

between different projects

workflow process since all

projects

with the database structure.

COTS RMS provide this

functionality.

Document generation Ability to generate documents

C

L Establish as part of the

including attachments and any associated

workflow process since all

attachments.

COTS RMS provide this

functionality.

Import / Export

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

5

ID 4.10.1 4.10.2 4.10.3 4.10.4 4.10.5

4.10.6

4.10.7 4.11 4.11.1 4.11.2 4.11.3 4.11.4

Requirement

Rationale

Priority Risk

Mitigation Strategy

Export to Excel

Ability to export data to Excel.

A

L Common functionality of

COTS RMS.

Import from Excel

Ability to import data from

A

L Common functionality of

Excel into the application.

COTS RMS.

Import from Excel ? Ability to import data from

B

L Common functionality of

including traceability Excel and re-establish

COTS RMS.

traceability.

Export to Word

Ability to export data to Word. A

L Common functionality of

COTS RMS.

Import to Word

Ability to import data from

A

L Common functionality of

Word including the ability to

COTS RMS.

parse data into a hierarchy

format based on the paragraph

header level during import.

Templates for

Ability to establish pre-defined

B

L Common functionality of

document generation templates for document

COTS RMS.

generation as part of the

export.

Assign hierarchy level Automatically assign hierarchy

A

L Common functionality of

level based on paragraph

COTS RMS.

header level during import.

Access Rights

Individual Access

Ability to assign access right to

A

L Common functionality of

Rights

an individual (i.e., read,

COTS RMS.

modify, create, and delete).

Group Access Rights Ability to assign access right to

A

L Common functionality of

a group (i.e., read, modify,

COTS RMS.

create, and delete).

Read-only Access

Ability to assign only read-only

A

L Common functionality of

Rights

access to an individual.

COTS RMS.

Edit Capability Access Ability to assign edit capability

A

L Common functionality of

Rights

to select individuals or groups.

COTS RMS.

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

6

ID 4.11.5

4.12 4.12.1.

4.12.2.

4.12.3.

4.12.4.

4.13 4.13.1.

Requirement Shareable Edit

Collaboration Reviews, Comments, and Input to Requirements

Approve or Reject Changes with Comments Compare Function

Track Decision

Reporting Impact Analysis

Rationale

Priority Risk

Mitigation Strategy

Ability to have multiple users

A

L Common functionality of

working in the same module or

COTS RMS.

project at the same time, but

not the same object.

Ability to establish workflows

A

for reviews, comments, and

input to requirements,

including the ability for

software to communicate (i.e.,

email, dashboard) to user(s)

when actions are required.

Ability for stakeholders to

A

approve or reject changes and

document comments on these

decisions.

Ability for users to see what

A

changed through version

control.

All decisions are tracked for

A

the life of the project.

L Establish as part of the workflow process since all COTS RMS provide this functionality.

L Establish as part of the workflow process since all COTS RMS provide this functionality.

L Establish as part of the workflow process since all COTS RMS provide this functionality.

L Establish as part of the workflow process since all COTS RMS provide this functionality.

Ability to provide reports to

A

requirements owners on

documents potentially

impacted when requirements

change.

H High Risk - Establish structure and workflow to provide requirement flowdown reports to determine potential impacts when requirements change.

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

7

ID 4.13.2. 4.13.3.

4.13.4.

4.13.5. 4.13.6. 4.13.7. 4.14

Requirement Gap Analysis

Gap Analysis

Bi-directional Traceability

Reportable Requirements Charts and Graphs Textual Reports Licensing

Rationale

Priority Risk

Mitigation Strategy

Ability to provide reports for

A

M Medium Risk - Establish

requirements that have not

structure and workflow to

been assigned to a

provide reports to identify

requirement owner (orphan

and track orphan

requirements).

requirements.

Ability to provide reports for

A

M Medium Risk - Establish

requirements that have not

structure and workflow to

demonstrated implementation.

provide requirement flow-

down reports to

determine which

requirements have not

demonstrated

implementation.

Ability to have bi-directional

A

L Establish as part of the

traceability from source

workflow process since all

requirements to implementing

COTS RMS provide this

documents and from

functionality.

implementing documents to

source requirements. This

includes multiple levels of

traceability.

Ability to provide notification

B

H High Risk - Establish as

when reportable requirements

part of the workflow

are coming due.

process and potential

schedule metrics on user

dashboards.

Ability to establish charts and

C

L Common functionality of

graph to represent work to go

COTS RMS.

or completed progress.

Ability to develop and export

C

L Common functionality of

textual reports.

COTS RMS.

Originating Template: Functional Requirements Template Rev 00

Functional Requirements Initiative Requirements Management Program

8

 ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download