Monday, October 29, 2012

PeopleSoft Reports Requirements Gathering Checklist


In this doodle I will share my PeopleSoft reports requirements gathering checklist. Many times after my requirement gathering meetings I used to think I have missed  at least one important information that has to be captured. I have to get in touch with stake holders again to gather the missing information's  Considering this happening more frequently I started creating my checklist of questions that I need to discuss in my requirements meeting.

This checklist helps me to save time and complete requirements gathering more efficiently. This checklist will undergo changes based on my future experiences and also based on my readers valuable comments.

Based on your requirement and design you can pick the right questions that is more appropriate to complete your specifications document.


General
1 Scope of the Report requirement
2 Integrating System Information (if any)
3 Is this Existing Report ?
4 Whether this report is PS delivered or New report ?
5 Technology to Develop the report (nVision, Crystal, XML Pubisher,PSQuery)
6 Sample Report File
Report Format
7 Layout for the report
8 Header Details of the report
9 Footer Detals of the report
10 Font specification (if any)
11 Expected Print Layout (if any)
12 Report output extension (.csv,.pdf etc)
13 Whether Page Numbering is required
Source Data
14 Whether data is fetched any system other than PeopleSoft ?
15 Whether data is from multiple modules of PeopleSoft?
16 Whether source database is transaction or Staging/archival database?
17 Whether Source data is dependent on any batch jobs?
18 PS records that contains data for reports
19 PS Tree / Ledger details
20 If external system is involved - Table Info from third party system
Security
21 Data Security ( PS Row Level Security)
22 Query Tree Node to which PeopleSoft records has to be attached (if any)
23 Criticality of the report
Business Logic
24 Whether report includes Summarize of data ?
25 Whether report has multiple sections ?
26 Business processing logic that has to be implemented in the report
27 Whether users has to be provided with option to enter input parameters
28 Any values that has to be hardcoded in the reports.
29 If no data is there to fetch for the input value whether any default message has to be displayed to the user ?
30 Data Display format for each column
Run Considerations
31 Whether this Report will be run as adhoc or scheduled Batch ?
32 Whether run control page has to be created ? If so, whether page layout information provided
33 Whether Scheduled report output has to be delivered in Mail or PS Pagelet or any File Server
34 Frequency of run
35 Time of run
36 Expected average volume of data
37 Expected time of completion (Max Run Time)
38 Expected number of parallel runs by end users

No comments:

Post a Comment