In this doodle I will share my PeopleSoft Interfaces 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.
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.
Checklist Items | |
1 | Scope of the requirement |
2 | Description of the source and Target systems |
3 | Integration architecture between Source and target Systems |
4 | Business Process Flow Information |
5 | Whether this interface is an existing one in PS 9.0 ? If so whether this logic and Objects will be reused |
6 | Technology to develop this interface (if there is an preference) - AE/SQR/ ETL |
7 | Input File layout details (if inbound) |
8 | Output file layout details (if outbound) |
9 | Whether File will be received from more than one source system? |
10 | Sample Data file |
11 | PeopleSoft Modules that are impacted |
Data Mapping | |
12 | Source system table to PS Tables along with columns details ( if Inbound) |
13 | Source system file to PS Tables along with columns details ( if Outbound) |
14 | PS Tables to target system tables along with columns details ( if Inbound) |
15 | PS Tables to output file layout along with columns details ( if Outbound) |
16 | Default values for the columns (if any) |
17 | Mapping rules for the columns that needs transformation |
18 | Select / Insert / Update conditions (if applicable) |
19 | Required Columns list (Rules should state what has to be done if any required column is missing) |
20 | Fornnating details for the required columns (like Date, DateTime, Amount etc) |
21 | Error/Exception handling strategy |
Business Processing Logic | |
22 | Any Business specific execution logics |
Scheduling | |
23 | Whether this interface will be run as adhoc or scheduled Batch ? |
24 | Whether run control page has to be created ? If so, whether page layout information provided |
25 | Frequency of run |
26 | Time of run |
27 | Schedule Dependencies |
28 | Any custom pages that has to be created for this interface |
29 | Any steup data that has to be configured for this interface |
30 | Expected average volume of data |
31 | Expected time of completion (if any) |
Input/Output File | |
32 | Input file name standards |
33 | Out file name standards |
34 | Input file path |
35 | Output file path |
36 | Error file path |
37 | Log file path |
38 | File Archive Startegy |
Any communications (like mailing error file or success mail etc) | |
39 | Mail note text |
40 | Sender address |
41 | receiver address |
42 | Any attachments |
No comments:
Post a Comment