PeopleSoft Functional Requirements Questionaire

 

Whether you are modifying a page, an app engine, PeopleCode, SQR, or component interface, you need to gather pertinent information before beginning any modification. This will help you determine the functional requirements.

The following is a list of questions that can be used by developers or system analysts to help find all the necessary information for a modification so that a full and complete functional document can be written up. The purpose is to expose underlying functionality or to make sure the requestor has thought of all the needed requirements.

Purpose
• What is this modification or process trying to perform?
• Why should this modification be done?
• Importance
• How valuable is this process?
• Are there workarounds?
• Define the benefit to the organization for completing this modification.
• Flows
• What is the flow of the process? Show each step in the process.
• Do not forget to include reports and background processes.
• Mark the steps that are not being changed in bold (standard PS processes).
• Show decision and alternate routes of the flow.
• Pages
• Describe each page—not only the update pages, but any inquiry pages as well.
• Determine the process for each page (Add, Update, or Inquire).
• What is the criterion for starting each page?
• Show all required fields in bold.
• Show which fields are hidden or grayed.
• Define the process by which field’s gray/hide or ungray/unhide.
• Show which fields have prompt values and what the prompt criterion is.
• Order is assumed from top to bottom, left to right—if not, note the order.
• Note any field changes based on user input— for example, if a field fills in, the prompts change in x and y fields.
• Note any validations required or controls needed in each field.
• Note field change criteria and save criteria.
• Define whether this page belongs with a group or other pages.
• If the page has scroll areas, what is the sort order?
• Define the menu where the page should be placed.
• Define the action and response of all button fields.
• Reports
• What are the selection criteria for each report?
• What is the sort order for the report?
• What is the expected output for the report?
• Define the header, footer, and main body sections of the report. Give examples, if possible.
• Are any subtotals or totals needed? For which fields? On what change criteria?
• Define the menu where the page should be placed.
• Programs
• What are the selection criteria for running the program?
• Is there any expected output?
• How is error handling resolved?
• Is this program automatically run? From what page or process?
• Can any of these programs be put into one job stream versus running separately?
• Define the menu where the page should be placed.