UCT Student System Documentation

ACA04 - UCT Student SystemsDevelopment Request

Note:

  • This is a development request for UCT Student Administrative Systemssuch as:
    PeopleSoft (PS), Residential Management System (RMS), Syllabus plus, Image Now etc.
  • For all other development requests see the SAP06 form.

Instructions:

  • Send the completed, signed development request form to the Chair of SCCC (Student Computing Co-ordinating Committee), for approval via:

Student Systems Support

Room 5.15

Student Admin Building

Middle Campus

UCT
Rondebosch, 7701

  • Email a copy (Microsoft Word format, as this document needs to be edited during the approval and development process)to:

1. Submission Details

A. Request Number(SSS to assign)
B. Development Request Description (short description, limit 50 characters)
C. Submission Date
D. Proposed By (Name)
E. Section & Department
F. Priority / High / Medium / Low
G. Implementation Deadline
H. Super User/Tester(Requester to assign. This is the person with whom the Business Analyst and the Trainer will liaise to clarify requirements and test the functionality)
I.User Procedure Documenter(SSS to assign)
J. Trainer(SSS to assign)
K. User support(SSS to assign)
L. Departmental Evaluation: Name / Signature / Date
M. HOD Approval: Name / Signature / Date
______

2. Tracking Details

A. Date Received by SSS Office
B. Date Referred toSystems Division for Evaluation
C. Date Submitted to SCCC

Complexity Rating

/

SCCC Decision

High
Medium to High
Medium
Low to Medium
Low / Approved for functional analysis
Rejected
Additional Info Required
Hold Status
D. Related CR Number (if approved for analysis, assigned by Systems Division):
E. Date Completed / Signature / Date
______

3. Development Request

A. Full description(include all relevant details. No technical descriptions are needed, but all functional requirements must be specified, including where relevant: business rules, input options, report output/layout).Be as thorough as possible, as the SCCC needs to understand your request, and a business analyst may need to create a technical development document based on this description, or establish whether or not a delivered function can support your need).
B. Conditions/remarks
C. Authorisations (UCT Job roles to receive access)
D. Proposed position on menu

4. Business Motivation

A. Reasons/motivation(why is this needed, how is the work done now, what are the consequences of not making this change?)
B. Impact on other related processes (provide brief description)
C. Business Process Owner (Name)

5. Systems Division Evaluation

(Refer to Functional Specification for further details)

A. Module/Function affected/developed
B. Custom objects to be created:
C. Upgrade implication
D. Comments:

20April 2017 Page 1 of 3 ACA04

CONFIDENTIAL – FOR INTERNAL USE ONLY