Information and Technology Services
PeopleSoft Upgrade Project
Software Development Review Checklist – DRAFT
Comments or questions?
This document is intended for use as an information guideline to developers and reviewers of software. It
is not required that this document be retained after its use.
Software Development Review Checklist
General Items
N/A



 Description
 A complete and accurate functional
description of the work unit is included
and references the Detailed Design as
appropriate.
 A complete and accurate technical
description for the work unit has been
included at the appropriate level of
detail.
 Program code has a sufficient amount
of comments describing the functional
requirements being met, the processing
logic, etc. (see Program Comments
Standards)
Comments/Notes
On-line Components
N/A  Description
RECORDS

 New/modified records begin with M_.

 Editing and validation rules have been
properly developed.

 New and modified records are properly
normalized and fit the overall
PeopleSoft data model.

 Field names are appropriate with all
necessary translate values and
descriptions.

 Screen print of new/modified record
included.

 PeopleCode is appropriate for the
functionality required within this work
unit and follows M-Pathways
PeopleSoft coding standards for Online
Comments/Notes
Document1
2/6/2016 4:37 PM
1
Software Development Review Checklist
Information and Technology Services
Software Development Review Checklist
Comments or questions?
N/A

Description
Programs.
TRANSLATE TABLE (XLAT) VALUES

 Appropriate changes to XLAT tables
completed and documented.
PAGES

 Appropriate pages have been
modified/created.

 Records associated with page
modified/created and documented

 New and modified pages follow the MPathways and PeopleSoft GUI
standards.

 Screen print of new/modified page
included.
MENUS

 Affected Menus modified/developed
appropriately.
QUERIES

 Query SQL is appropriate for required
functionality and efficiently developed.
BUSINESS PROCESS DESIGNER

 All appropriate Activities developed
and documented for the business
process.

 PeopleTools printout and screen print
of the Activity from PeopleTools
included
WORKFLOW

 A workflow model has been developed
that meets the functional requirements
of the business process flow

 All roles and rules for all activities,
events and routings have been
developed.

 Code changes follow the M-Pathways
PeopleSoft coding standards for Online
Programs.

 Developed other modifications
(identified in design) from the delivered
Comments/Notes
Document1
2/6/2016 4:37 PM
2
Software Development Review Checklist
Information and Technology Services
Software Development Review Checklist
Comments or questions?
N/A



Description
workflow.
 All Roles are generic so that
organizational changes can be handled
without further modifications
 Rules are developed so that they can be
stored in the Workflow Administrator
Tool
Comments/Notes
Batch Components
N/A





 Description
 All program Inputs and Outputs have
been documented
 New called modules have been
developed when extensive additional
functionality is being added to existing
batch processing.
 Code changes follow the M-Pathways
PeopleSoft coding guidelines for Batch
Programs.
 All SQL follow the M-Pathways
PeopleSoft coding and performance
standards for SQL.
 Error processing situations (i.e.
Commit/Restart processing) were
developed with clear resolutions.
Comments/Notes
Report Components
N/A




 Description
 Report layouts have been included and
follow all reporting standards.
 Identified code changes follow the MM-Pathways PeopleSoft coding
guidelines for Report Programs.
 Report Processing logic appropriate for
functionality required
 All identified SQL follow the MPathways PeopleSoft coding and
performance standards for SQL.
Comments/Notes
Document1
2/6/2016 4:37 PM
3
Software Development Review Checklist
Information and Technology Services
Software Development Review Checklist
Comments or questions?
N/A

 Description
 Error processing situations have been
developed with clear resolutions.
Comments/Notes
Unit Test Plan
N/A






 Description
 Unit Test Plan follows M-Pathways
template for Deliverable #69
 Test Approach defined
 Detailed testing cycles completed and
documented.
 Detailed test conditions completed and
documented
 Detailed test data documented and is
appropriately cross referenced to test
cycles/conditions
 Detailed expected results documented
and are appropriately cross referenced
to test cycles/conditions
Comments/Notes
General Functional Items
N/A


 Description
 The program meets the identified
functional requirements.
 On-line programs only: The on-line
page(s) looks and functions according
to user specifications.
Comments/Notes
Document1
2/6/2016 4:37 PM
4
Software Development Review Checklist