Requirements For TSRS - ITSD-11737

Jira Request	ITSD-11737
Jira Epic
Application(s)	Application Enhancement Request
Business Process(es)	Training Request Site
Requester	Kimberly Ruelas
IT Business Analyst	@a user
Document Owner	@a user
Document Status	APPROVED

Document Purpose

The purpose of this document is to document the high-level business requirements for Service Requests and Projects. High-level business requirements for Projects are obtained from the Business Case Evaluation or the Project Request.

Requirement Elicitation Sessions and Reviews Conducted:

The following requirement elicitation sessions and reviews were conducted with the customers on the following days:

06/06/22, Kimberly Ruelas, SME, Shelly Smith-Cortez, SME, Jennifer Weitz, Sr Training and Development Specialist

Introduction

Request Description

We need to add a new Type of Request. Please add a check box under the "Type of Request" section for "Training Scheduling". Once the check box is selected, the new text box to pop up should include the following: Training Title, Brief Description, Training type (Classroom, field/yard, PowerPoint, Online), Who is required for training (type in box), Location (NACY, Other, SACY, SRWTP), SME, Trainer (able to type in box or select check box that states "Supervisors") , Deliverables (Sign-in sheet, PowerPoint, Handouts, Video, other (with written in box), additional information box, and attachment section.

Business Requirement Instructions

Business requirements are needs or wants or an organization which allows the business to achieve its end objectives, vision, and goals. They give the extent of a business need or a problem that should be addressed by a particular project. Business requirements are intended to be guide and they are not intended to be specified at a level that they could be implemented by a developer. Each requirement should be assigned a unique requirement key as this key is used for traceability from this document through to the implementation of the requirement.

Requirement Key: IT-9999-BR-9999 (IT-9999 = Jira Epic or Issue # of your project/task, BR = Business Requirement, 9999 = Unique # assigned by Requirement Yogi). Requirement Yogi will automatically assign the next consecutive number.

Requirement Type:

Executive, Stakeholder, Product

The source column indicates the source of the requirement and can be any of the following:

Specific Person or Persons
Group, Division or Department
Documentation (Forms, etc.)
Meeting
Application

The priority column ranks the relative importance of the requirement to the Stakeholders:

1 – highest priority; absolutely essential product feature OR Must have
2 – medium priority; individual features are not essential, but together they affect the viability of the system OR Should have
3 – lowest priority; nice-to-have feature; one or more of these features could be omitted without affecting the system viability OR Nice-to-have
Not implementing

Status Legend

NEW	New requirement, details have not been worked out
WIP	Requirement details are being worked out.
PO REVIEW	PO is reviewing the requirement or implementation options.
IN REVIEW	Requirements are in review by the project team.

REVIEWED	Requirements have been reviewed by the project team and are ready for approval
SYSTEM TEST	Requirements are in system test.
UAT	Requirements are being tested by the customer.
CANCELLED	The business decided they did not need the requirement (keep on matrix as they may change their mind).

APPROVED	The requirement has been approved by the customer and can be implemented.
DEPLOYED	A solution that meets the requirements have been deployed into production.

Business Requirements

The following matrix describes the high-level business requirements:

Key

Requirement Description

Type

Source

Priority

Status

Links

ITSD-11737-BR-001

Create new "Type of Request" for Training Scheduling in the Training Request application.

Stakeholder

Kimberly Ruelas

Shelly Cortez

Must have

APPROVED

ITSD-11737

Training Request System

Functional Requirements

This section specifies the functional requirements (FR). These should also be the basis for UAT testing.

Key	Functional Requirement Description	Status	Source	Category	Priority	Refines Business Requirement
ITSD-11737-FR-001	The create training request form must have a selectable option called "Training Scheduling (Only)"	APPROVED	Kimberly Ruelas Shelly Cortez	Data	Must Have	ITSD-11737-BR-001
ITSD-11737-FR-002	The training scheduling option must display a sub-form indicating the form is used for training scheduling only.	APPROVED	Kimberly Ruelas Shelly Cortez	Data	Must Have	ITSD-11737-BR-001
ITSD-11737-FR-003	The training scheduling sub-form must display the following data fields: Training topic - required Brief description - required Training type (include other) - required Number of classes - not required Number of students - not required Training location - required Subject matter expert - required Trainer - not required Deliverables (sign in sheet, invite, other) - required Additional information - not required Attachments - not required	APPROVED	Kimberly Ruelas Shelly Cortez	Data	Must Have	ITSD-11737-BR-001
ITSD-11737-FR-004	The submit training request button must notify the training office a new training scheduling request has been entered.	APPROVED	Kimberly Ruelas Shelly Cortez	Data	Must Have	ITSD-11737-BR-001

Questions

Below is a list of questions to be addressed as a result of this requirements document:

Question	Outcome