Common Management Systems
Development Request
Development Overview
(Document naming standard: Refer to last page of this document)
Document Title:
Author:
File Reference:
Date
By
Action/Change Reference
IT Project or
ASR Ticket
Date Req.
Completion
Estimate
Created document
This section will track all modification requests so the user can refer back to the ASR Tickets listed.
ASR #
ASR Title
Requested By
Phone Nbr
Mod Applies To
HR
SA
FIN
Module:
Mod Type
Bolt-On
Interface
Report
Self-Service
Other: please list type
Note: Bolt-on = New process not delivered in PeopleSoft requiring a Project to accompany
Note: Report = SQR, Query & NVision
**** If you are not sure what Mod Type you are requesting fill in what you can in the Other section ****
Rev
Date
Review Action
Reviewed By
Phone Nbr
Functional Document Approval
Technical Design Approval
COMR Approval
Page 1
6/30/2016
Common Management Systems
Development Request
Functional Requirements
(Please ensure you fill out the following sections: Objective/s, Business Justification, Regulatory
Requirements/Business rules, Processing Alternatives and Recommendations. The request type will dictate which
sections of the Detailed Requirements section will be completed – eg the Reports section for reports, etc)
Objective/s
Business Justification
Regulatory Requirements/Business Rules
Detailed Functional Requirements
(Provide a detailed description of what is needed. Use the various sections below to provide additional detail
depending on the request type. Provide mock screen shots where necessary)
Please use the table below to provide a brief description of each requirement and its priority.
You can expand on the requirements in the reports, interface or new development requirements sections below.
Requirement
#
Description
Priority
(1 = high,
3 = low)
1
2
Reports Section
1.
Does an existing report exist that meets the needs or can be used as a guide?
2.
Report Title:
3.
Selection Criteria:
4.
Report Frequency:
5.
Dependencies, i.e. processes that need to be run first?
6.
How is report used, i.e. reviewed and filed, Used to create another report?
7.
Approximate size of report? (number of records or pages)
8.
Fields Required on report output
Field Name
Table Name or Navigation
of Fields
Format
Option
Page 2
Field Title (What
you want to call it)
Comments/Notes
6/30/2016
Common Management Systems
Development Request
Interface Section
1.
Does an existing interface exist that meets the needs or can be used as a guide?
2.
Interface Name(s):
3.
Selection Criteria:
4.
Interface run Frequency:
5.
Dependencies, i.e. processes that need to be run first?
6.
How is this interface used, i.e. uploaded into PeopleSoft or extracted out of PeopleSoft for another system?
7.
Approximate size of interface? (number of records)
8.
Fields Required on interface output
Field Name
9.
Table Name or Navigation
of Fields
Format
Option
Field Title (What
you want to call it)
Comments/Notes
Fields used for interface going into PeopleSoft
Field Name
Table To be Inserted Into
Format
Option
Description
New Development (Built-On Section & Self-Service Section)
(Provide detailed information on the new bolt-on or Self-Service process being requested.)
1.
Are there existing PeopleSoft or Baseline pages for this request (What are the pages and what changes are
needed)?
2.
Are new PeopleSoft pages needed? Please describe what new pages should contain and the look.
3.
Is Workflow needed? If yes, please describe the new Workflow process.
Page 3
6/30/2016
Common Management Systems
Development Request
“Other” Section
Security Requirements
1.
Who is authorized to run or view report?
2.
Is Confidential Data required? Why? What level is it?
Refer to http://www.calstate.edu/icsuam/sections/8000/Section8000.pdf#page=50 for details on what data
are classified as confidential and the classification levels.
3.
Are there any audit requirements? Please provide detail.
Processing Alternatives
Recommendations
Business Test Conditions
Condition
Steps
Test Data
Page 4
Expected Results
Success?
6/30/2016
Common Management Systems
Development Request
Technical Design
Technical Description
(Provide a brief description of the Technical solution for this request)
Technical Specifications:
Object Changes:
Provide all information on any changed or additions made via application designer (This includes all tables, pages,
components, menus, peoplecode, workflow). Provide screen shots where applicable. Below is an example only:
Object Name:
Object Type:
son_runctl_hr769
Component
Detailed Description of Object:
This component contains the page son_runctl_hr769. This is a new component, created to provide the end-user the
ability to run the requested report. There is no peoplecode added to this component.
Program Flow:
(Provide information on the process developed. i.e. if an SQR was created provide details of the program,
specifically any part of the program you might view complex that would benefit the reader having ability to read
about it here.)
Report Detail:
Report Information
Report Name:
Report Type:
Run Location:
Sonhr769.sqr
SQR
CSU Custom Rpts/Interfaces > Sonoma>Rpts A-M> EE Mass Terms
Report Layout:
Field Description
Field Name
Position
Length
Page 5
Data Type
Format
Comments
6/30/2016
Common Management Systems
Development Request
Interface Detail:
Interface Information
Program Name:
Report Type:
File Length
File Description
Owner of Source Data/Contact
Owner of Target Data/Contact
Transfer Mechanism (FTP, E-MAIL, Media)
Transfer Frequency
File Attributes (ASCII, Binary)
Volume of Data (estimate # of records)
Detail File Layout:
Field Description
Field Name
Position
Length
Data Type
Default Field Value
Format
Additional Pertinent Technical Information:
Development Test Scenario:
Condition
Steps
Test Data
Page 6
Expected Results
Verified
6/30/2016
Common Management Systems
Development Request
Naming Convention
The following is the naming convention for all development requests. You will find three
naming documents under the folder \\ssu-5\cms\Core Team\Templates. These documents will hold
each of our requests so we can have a unique number associated with this development request.
This will allow us to easily refer back to the document when changes are needed. Below is
information for each Functional Area (Human Resources, Student Administration & Finance) on
the naming convention and name of the tracking document.
Developers: The below naming conventions will be used from this point forward to name our
SQR, Crystal, Queries & nVisions. For Example: A document that is called
SON_BB001_Enrollment Request Worksheet the SQR would be called sonbb001. DO NOT use
naming convention of SMA any longer.
Human Resources:
Open the document \\ssu-5\cms\Core Team\Templates\Human Resources Naming Document.xls. Within this
excel document you will find various worksheet tabs. Locate the tab that represents your work
request area and take the next available number. For example if you were requesting work to be
done in Base Benefits, you would look under BB – Base Benefits tab and log in the next number.
You would then save this document as SON_BB001_Enrollment Request Worksheet.
Areas under Human Resources
AW – Admin Workforce
BB – Base Benefits
LC – Labor Cost
RW – Recruit Workforce
TF – Temp Faculty
TL – Time Labor
HR – HR General
Page 7
6/30/2016
Common Management Systems
Development Request
Student Administration:
Open the document \\ssu-5\cms\Core Team\Templates\Student Administration Naming Document.xls. Within
this excel document you will find various worksheet tabs. Locate the tab that represents your
work request area and take the next available number. For example if you were requesting work
to be done in Financial Aid. You would look under the FA – Financial Aid tab and log in the
next number.
You would then save this document as SON_FA001_Student Loan Report
Areas under Student Administration
AA – Academic Advising
AD – Admissions
FA – Financial Aid
IR – Institutional Reporting
SF – Student Financials
SR – Student Records
CC – Campus Community
SA – SA General
Page 8
6/30/2016
Common Management Systems
Development Request
Finance:
Open the document \\ssu-5\cms\Core Team\Templates\Finance Naming Document.xls. Within this excel
document you will find various worksheet tabs. Locate the tab that represents your work request
area and take the next available number. For example if you were requesting work to be done in
General Ledger. You would look under the GL – General Ledger tab and log in the next number.
You would then save this document as SON_GL001_General Ledger Accounts
Areas under Finance
AP – Accounts Payable
PO – Purchase Orders
GL – General Ledger
AR – Accounts Receivable
FN – Finance General
Page 9
6/30/2016