Sample of Requirement

DT Business Requirements Form
CR 51013
1 Requirement Identification
Requirement
Name
Adding new fields to existing Aperture interface .
Requirement ID
CR 51013
Submitted Date
August 14, 2008
Requested By
Maggie Thomson
Required By
Date
September Maintenance Release
Business
Analyst
Ami Desai
Approval
Status
Pending
2 Requirement Summary
Description of
business
requirement
We currently have an interface with Aperture system. As part of this CR we will

send additional information to Aperture by modifying current interface. Aperture
interface receives peoplesoft data via ODS. We will need to modify the query
in ODS to add following 5 additional fields.
Gap between
current and
Desired (if
change request)
Need following 5 additional fields.
Business
Objectives /
Benefits ROI
Will help locate employees location under different division.
1.
2.
3.
4.
5.
Direct Supervisor first name

Direct Supervisor last name
Supervisor's Employee ID
Division
Sub Division
Business
Impacts if
change / issue
fix not
implemented
Updated new query for ODS team which includes new fields.
Add the following 5 field to Aperture interface data file at the end of the current file.
Field Name
Supervisor ID
Supervisor First Name
Supervisor Last Name
Division
Sub Division
Source Table/field
ps_job
ps_personal_data.first_name (pull data based on supervisorID)
ps_personal_data.last_name (pull data based on supervisorID)
ps_sy_dept_tree.SY_DT_DIVISION_DEC
ps_sy_dept_tree.SY_DT_SUB_DIV_DEC
3 Classification
To check a checkbox, right click on the box. Select Properties. In the Properties dialog box use
the radio buttons to change the default value of the box.
CR51013 Sympeople-ODS-Aperture
Last updated: 7/26/2016
Page 1 of 3

Request Type
CR 51013
Enhancement
Maintenance (Issue fix)
(New or enhanced functionality)

Severity/Priority
Severity of Impact:
Critical
(Business will not function without this

change)
Priority:
High
Medium
Low
High
(Business needs this functionality but a workaround is available/possible)

Nice to Have
(Business can operate without this

functionality but is desired)
Classification
Alert/Notification
Configuration
Customization
Data Change/Script
SOx Controls
New Report
Privileges/Access Control
Patch / Fix
Performance
Other (please specify):
Identify component to be changed

<text>
4 Assumptions/Risks/Dependencies
Changes and testing needs to be coordinated thru ODS team during each cycle of testing
and during production migration.
5 Reference Artifacts
n/a
6 Business Requirement Approvals

The IT representative submitting this requirement form for release is responsible for requesting and
managing the business approval of the requirement, and for updating this section with the link to
the actual approval doc. The process for submitting the approval is described below.
Important: Failure to complete one of the following recommended actions to document linkage
between the business requirements form and business requirement approval may result in a failed
SOX audit.
1. The business representative of the change request submits the business requirements
approval. Ideally, this person is the Business Stakeholder or Business Owner/Approver
(BOA). The business approval should be submitted to the IT representative as an e-mail
containing the business representatives e-mail signature.
2. The IT rep/request submitter posts the approval to the project repository for the release
AND/OR attaches it to a CR in Remedy. This person verifies that the reference to the
Remedy CR attachment AND/OR the actual URL to the doc in the project repository is
added to this BR from in the below section.
Page 2 of 3
CR 51013
If posting to Remedy, refer to Remedy CR.
If posting to repository, do one of the following:
Add name and URL of repository, then list Stage and Package name in text. After
update, post doc to repository.
Post doc to repository, obtain specific doc URL, update local document to contain
URL, then re-post doc to project repository
Name
Maggie
Thomson
Role
Sr. CAD/CAFM
Specialist
Date Approved
Approval link/reference
<dd-monyyyy>
Refer to approval attached in Remedy

CR 51013
7 Change History
Updated by
Version
Date
Reason for change, summary of change
Page 3 of 3

Sample of Requirement

Uploaded by

Copyright:

Available Formats

Sample of Requirement

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sample of Requirement

Uploaded by

Copyright:

Available Formats

DT Business Requirements Form

Adding new fields to existing Aperture interface .

August 14, 2008

September Maintenance Release

We currently have an interface with Aperture system. As part of this CR we will

Need following 5 additional fields.

Will help locate employees location under different division.

Direct Supervisor first name

DT Business Requirements Form

Maintenance (Issue fix)

(New or enhanced functionality)

(Business will not function without this

(Business needs this functionality but a workaround is available/possible)

(Business can operate without this

Other (please specify):

Identify component to be changed

6 Business Requirement Approvals

DT Business Requirements Form

If posting to Remedy, refer to Remedy CR.

If posting to repository, do one of the following:

Refer to approval attached in Remedy

Reason for change, summary of change

You might also like