CAM - Confluence by hedongchenchen

VIEWS: 13 PAGES: 19

									                                                                                COA Module Preliminary Review

                                                                                             How many                         Page
Location                                  Where found? Website                               test?    Date:      Module       Nos. Section is:
Foundation Functional Test Scripts        https://test.kuali.org/confluence/display          31 tests 10/12/09 -
(Arizona? - Kymber Horn)                                                                              01/19/10
                                          /KFSIMP/Chart+of+Accounts+%28COA%
                                          29
KFS Business Transaction & Fit Analysis   https://confluence.cornell.edu/display/KFSIMPL/C 14 tests    03/27/10               13     Very high
(ML & BA - Module Appendix) ML: Dave      hart+of+Accounts+Maintenance                                                               level in
Hegelein & BA: Shelley Ruth                                                                                                          COA
                                                                                                                                     Module
                                                                                                                                     Appendix




Technical Implementation Plans (TIAs)     https://confluence.cornell.edu/display/KFSIMPL/C ?
TIA=N/A                                   hart+of+Accounts+-+CoA#ChartofAccounts-CoA-
                                          QualityAssurance




Business Readiness Plans (Project         https://confluence.cornell.edu/display/KFSIMPL/P             03/13/10   All         12, 13 Test Plan:
Management) See Draft Functional Area     roject+Management                                                       modules
KFS Business Readiness Plans General                                                                              are
Accounting Sue Hoadley, Dave Hegelein                                                                             effective
                                                                                                                  by CoA
                                                                                   COA Module Preliminary Review
Notes:


https://test.kuali.org/confluence/display/KFSIMP/Chart+of+Accounts+%28COA%29



The COA Module Team will work with the KFS QA Lead to finalize. For more test cases see the Kuali Foundation test site.
Test converted data and makes sure it is accurate; Test system options; Test Cornell COA parameters and how they function in e-docs; Test Charts; Test
Organizations; Test Account Attribute setup values; Test Account setup; Test Sub-Accounts; Test Object Codes; Test Sub-Object Codes; Test Project
Codes
Test User Access in all COA e-docs; Test Workflow in all COA e-docs; Test Sub-Fund Program customization and other approved customizations




To be defined by Module Team and QA Lead; There are Interfaces & Customizations HQ;              TIA = TBD;                       Various TIA
sections: Business Process; Minimum Usability Requirements; Prerequisites; Access/Security*; Workflow*; Parameters*; ID&R, QA; Data
Conversion/Loading*; Environment Management Plan; Interfaces; Customizations; Integration Points; Operations Plan: Batch




Testing Process Overview:
GA testing focus will be proofing new account attributes in the new system to ensure that it follows the table conversions. GA will also focus on
creating new database and queries to proof new account setup, attributes, reclass entries, footnotes and other miscellaneous reconciliations and
schedules. The plan is to duplicate the results from the new query tools using the balances in the test environment throughout FY11.
GA will need to test Kuali object code balances to determine the process to extract asset and liability transactions/balances to revamp reconciliations.
GA will work closely with Reporting and Kuali ID&R team to ensure the charts and mapping issues for the production of the financial statements and
that similar FS details are available for variance analysis.
Describe Acceptance Criteria:
Acceptance criteria in GA is defined as running duplicate processes for queries, databases, reclass entries, footnotes, schedules between the two
systems. This testing will occur during FY11, and FY12 for footnotes.
Testing Roles and Responsibilities:
Generally, each person within GA will be responsible for converting queries, database, reclass entries, footnotes, and schedules. Where needed, the GA
supervisor will provide assistance in development.
Testing Scope: The list of business processes to be tested includes but not limited to: New account setup/attribute review, CR Management System –
daily deposit reconciliation, Reclass entries, Footnotes, Schedules;               Test Plan: A more detailed test plan will be submitted in the future.
GA’s plan is to during FY11 to duplicate processes in both systems to ensure the new processes are retrieving the same data. Major timelines are listed
in the System and Tools section. The focus for “testing” written procedures will not occur until FY13. The plan will be for a functional backup employee
test (follow) the written procedures. GA will provide assistance to Kuali COA to review COA tables.
                                                               Financial Processing General Ledger Module Preliminary Review

                                                                                  How many                            Page             Notes:
Location                   Where found? Website                                   test?         Date:     Module      Nos. Section is:
Foundation Functional      https://test.kuali.org/confluence/display/KFSIMP/Finan ~ 124      10/29/09 -   includes
Test Scripts (Arizona? -   cial+Processing+%28FP%29                                          01/19/10     IDC, etc.
Kymber Horn)

KFS Business Transaction https://confluence.cornell.edu/display/KFSIMPL/KFS+Tr                                                         Test each FP e-doc and ensure the following: • Positive testing:
& Fit Analysis (Module   ansaction+Business+Process+Fit+Analysis                                                                       1.All parameters are working as designed; 2.Only valid roles can
Appendix): Cathy Salino                                                                                                                initiate the documents; 3.Ensure template uploads work
& Sherry Wilson                                                                                                                        4.Workflow is pulling in correct routing 5.Workflow is pulling in
                                                                                                                                       correct routing 6.Validate roles in workflow can change values in
                                                                                                                                       e-docs • Negative testing: 1.Input invalid data and ensure
                                                                                                                                       correct error messages are presented; 2. Import templates with
                                                                                                                                       invalid data; 3. Try to initiate e-docs with invalid roles 4. Try to
                                                                                                                                       change values in the workflow which should not be allowed.
                                                                                                                                       More intense testing for DV e-doc (utilize hands on FIT session
                                                                                                                                       scenarios with CU data)
                                                                                                                                       Test interfaces for CCR/AD Receipt Balance when modification is
                                                                                                                                       complete.
                                                                                                                                       Test all modifications for roles and workflow. For more test
                                                                                                                                       cases see the Kuali Foundation test site.




Technical                  https://confluence.cornell.edu/pages/viewpage.action?                                                       Business Process, Minimal Usability Requirements, Pre-
Implementation Plans:      pageId=118754291                                                                                            requisites; Access/Security; Workflow; Parameters; ID&R;
Dennis Friends                                                                                                                         Quality Assurance; Data Conversion; Environment Management
                                                                                                                                       Plan; Interfaces; Customizations; Integration Points;
                                                                                                                                       Operations Plan; Batch

Business Readiness Plans https://confluence.cornell.edu/display/KFSIMPL/Project              2/12/2010                                 Accounting Operations: Testing Plan • Continue to test in Test
(Project Management); +Management                                                                                                      Drive; • When CU copy of instance available, shift focus to that
See Draft Functional                                                                                                                   instance. • Create local testing groups. • Expand testing groups
Area KFS Business                                                                                                                      across campus Describe Acceptance Criteria Testing Roles and
Readiness Plans: Cathy                                                                                                                 Responsibilites: n/a 7/28/10; Testing Scope: n/a 7/28/10; Test
Salino                                                                                                                                 Plan: n/a 7/28/10
                                                              Purchasing / Accounts Payable Module Preliminary Review                                    4 of 19
                                                                                                                                               Page
Location                   Where found? Website                         How many test? What kind?           Date:        Module                Nos.
Foundation Functional      https://test.kuali.org/confluence/display/KF ~171 tests                          10/12/2009   Purchasing and
Test Scripts (Arizona? -   SIMP/Purchasing+and+Accounts+Payable+%                                                        Accounts Payable
Kymber Horn)               28PURAP%29                                                                                    (PURAP)


Foundation Functional      https://test.kuali.org/confluence/display/KF 26 tests - Vendor                   10/12/2009   Purchasing - Vendor
Test Scripts (Arizona? -   SIMP/Vendor+%28VN%29                                                                          (VN)
Kymber Horn)

KFS Business Transaction https://confluence.cornell.edu/display/KFSI 13+ tests (basic scenarios)            4/22/2010    Purchasing            14, 15,
& Fit Analysis (Module   MPL/Purchasing                                                                                                        19
Appendix)

Technical                  https://confluence.cornell.edu/display/KFSI 1.Minimal Usability Requirements*;   Confluence   Purchasing
Implementation Plans       MPL/PURAP+Technical+Implementation+Pla 2.Access/Security*
                           n                                           3.Issues/Outstanding Questions
                                                                 Purchasing / Accounts Payable Module Preliminary Review                              5 of 19
Business Readiness Plans https://confluence.cornell.edu/display/KFSIMPL/ See Draft Functional Area KFS Business 3/26/2010    Purchasing         8&9
(Project Management) Project+Management                                  Readiness Plans




Foundation Functional      https://test.kuali.org/confluence/display/KFSIMP 34 tests (PDP)                      10/12/2009   Accounts Payable
Test Scripts (Arizona? -   /Pre-Disbursement+Processing+%28PDP%29
Kymber Horn)

KFS Business Transaction https://test.kuali.org/confluence/display/KFSIMP Information from Functional Review    7/8/2010     Accounts Payable
& Fit Analysis (Module   /Pre-Disbursement+Processing+%28PDP%29           Presentation
Appendix)

Technical                  https://confluence.cornell.edu/display/KFSIMPL/ 1.Minimal Usability Requirements*;   Confluence   Accounts Payable
Implementation Plans       PURAP+Technical+Implementation+Plan             2.Access/Security*
                                                                           3.Issues/Outstanding Questions

Business Readiness Plans https://confluence.cornell.edu/display/KFSIMPL/ See Draft Functional Area KFS          3/26/2010    Accounts Payable   12
(Project Management) Project+Management                                  Business Readiness Plans
                                                                  Purchasing / Accounts Payable Module Preliminary Review                                                                  6 of 19

Section is:                       Notes:
                                  https://test.kuali.org/confluence/display/KFSIMP/Test+Scripts+%28Functional%29




Need detailed scenarios??         Issues / Outstanding Questions 1. Vendor Document: Create a role that allows limited persons to initiate a vendor (Business Service Center's - BSC):
Testing Roles and                 Vendor Creator. Limit who can edit a vendor to those above. Would like all edits (right now anyone can add a contact) to go to Vendor Reviewer just
Responsibilites; Testing Scope;   as the Vendor document does. Only people with that role can add an attachment. (new permission specific to this document type?) Limit who can
Test Plan; First meeting is       see those attachments to Vendor Reviewer. Blanket Approval - Add KFS-SYS Purchasing Manager Delete Attachments - Add KFS-SYS Purchasing
scheduled with Tony and           Manager, and Vendor Reviewer Why is there a split node for Vendor reviewer and Workflow initiator; Why are there two levels (parent and doc) for
module leads to begin             Vendor. VEND vs. PVEND; Vendor Contract, can be accessible by all. 2. Requisition Document: All Workflow participants other than ad-hoc can edit
discussing QA for the modules     items and lines. Commodity Reviewers will be determined for select Commodity codes. Other commodity codes will not have commodity reviewers.
on June 7 from 3:00-4:00pm.??     Any time a sensitive commodity is used it should automatically restrict access to the requisition and purchase order. Not wait until purchasing checks
                                  the box as sensitive. MAY NEED BUSINESS CASE - (!)Possible Customization Will need to determine what role will be the Separation of Duties and who
                                  will have the permission in that role. Can we add permission 85 separation of duties reviewer to a role qualified by org? so that the separation of
                                  duties person is in the organization that the initiator is in.If we want payments to human participants to be considered sensitive, we need to look at
                                  the disbursement voucher. When creating a DV there is a drop down menu for payment types, one of which could be human subjects. This could be
                                  the cue for sensitive. Ask Cathy Salino. 3. Purchase Order and Purchase Order Split Document: Pre-route, Purchasing Processor is represents central
                                  or campus Purchasing staff. They can modify Vendor section of Purchase Order. We need to test if any FYI recipient would have the ability to print.
                                  Sys Manager: can delete notes & attachments, add delete note & attach permission to KFS Sys Purchasing Manager role and add up to a Parent Level
                                  (check this). Fix the routing for commodity reviewer so that it does not route to them once as a requisition and once as a PO. Also look at commodity
                                  reviewer permissions, may need to move to another role. 4. Purchase Order Amendment: PO Amendment: Workflow goes to Purchasing Processor.
                                  Purchasing processors do not deal with account number. Need to make a changes so that PO amendments go to Fiscal Officer or their delegate. Or
                                  someone in BSC. Would like: If PO Amendment has a dollar amount amendment then it should go to Contract Manager if over $50K. Should go to FO
                                  first then Purchasing Processor in Business Service Center's - BSC. Research Amending POs and what is routing of dollar amounts and other criteria.
                                  5.Contract Manager Assignment: The contract manager/purchasing agents will have to have the role of purchasing processor. 6.Purchase Order
                                  Document By Status: Purchase Order Close and REQ/PO. Test how Print works and when the initiator gets the Print ability and who should/ get it
                                  and about when people get FYI'd. Looks like there is no way for a the initiator to open (view) closed document. Test PO attachments, Is a pdf version
                                  of the po always created and where is it stored. Is there a batch job that prints printed PO's so they can be put together with their attachment. If
                                  faxing or e-mail can the system send PO plus designated attachment types from the PO. No, designated attachments cannot be sent in connection
                                  with faxed or emailed PO.
                                                               Purchasing / Accounts Payable Module Preliminary Review                                                              7 of 19
Testing Roles and               Testing Process Overview: Testing has been ongoing. High level test cases already exist and will be repeated when we have a CU instance, with CU
Responsibilites; Testing Scope; data. Testing Roles & Responsibilities: Not defined yet. Testing Scope: • Req creation and workflow, including use of ad hoc • PO approval &
Test Plan                       submission to vendor (multiple submission methods) •PO changes •Receiving (note: many criteria available for receiving requirements), and PO
                                amendments resulting from Receiver •Vendor setup and attachments, including testing of internal ad hoc routing for Vendor approval •Payment
                                request, including required approval •Testing of data stored in warehouse to ensure it is adequate to meet reporting needs Test Plan: Testing has
                                been ongoing and high level test cases have been created. We have not, however, documented a formal testing plan.


PDP: includes pcard override




Incomplete sections: High-level
test cases identified?


Incomplete sections: Testing
Roles and Responsibilites;
Testing Scope; Test Plan

Incomplete sections: Testing    KFS batch jobs related to PURAp & PDP; Payments Requests; Vendor Credit Memo; Electronic Invoices; PDP
Process Overview; Testing Roles
and Responsbilites; Testing
Scope
To be completed separately - PDP - mostly batches
                                                                    Capital Asset Module Preliminary Review

                                                                        How many test? What                                   Page
Location                           Where found? Website                 kind?                   Date:        Module           Nos. Sections
Foundation Functional Test         https://test.kuali.org/confluence/di 32 tests                10/12/09     CAM, CAB,
Scripts (Arizona? - Kymber Horn)   splay/KFSIMP/Capital+Assets+%28C
                                   AM+and+CAB%29
KFS Business Transaction & Fit     https://confluence.cornell.edu/disp                          04/22/10     Capital Asset,   14,
Analysis (Module Appendix)         lay/KFSIMPL/Capital+Assets                                                FP, PUR, AP      15,
                                                                                                                              19




Technical Implementation Plans     https://confluence.cornell.edu/disp   1.Minimal Usability    Confluence   CAM                     Testing Roles and
                                   lay/KFSIMPL/Capital+Assets+Techni     Requirements*;                                              Responsibilites; Testing
                                   cal+Implementation+Plan#CapitalA      2.Access/Security*                                          Scope; Test Plan
                                   ssetsTechnicalImplementationPlan-     3.Issues/Outstanding
                                   QA                                    Questions




Business Readiness Plans (Project https://confluence.cornell.edu/disp See Draft Functional      05/06/10     CAM              8, 9   Testing Roles and
Management)                       lay/KFSIMPL/Project+Management Area KFS Business                                                   Responsibilites; Testing
                                                                      Readiness Plans                                                Scope; Test Plan
                                                                        Capital Asset Module Preliminary Review



Notes:



High-Level Test Cases: 1.Capital Asset AP Builder: when the record is created in the builder from the Purchasing
module; 2.Capital Asset GL Builder: when the record is created in the builder from all of the relevant financial e-
docs; 3.Capital Asset Retirement functionality; 4. Maintenance of Capital Assets; 5.Trade-in and selling of assets
and associated G/L entries created, retirement of the original asset; 6.Depreciation of assets, when the asset starts
depreciating, sub objects; 6.Test workflow for different groups; 7.Capital Asset object code and sub object code
set up in COA

Collaborate: Module Team, KITI Team Leads, QA Lead: {The module-specific QA strategy must include unit
testing, technical testing and functional testing that will take place over the life of the implementation effort.}
Current Capital Assets Foundations issues: 1. https://test.kuali.org/jira/brows/KFSMI-5199; Capitalization Offset
entry needs its own parameter for setting up the fund balance object code offset;
2.https://test.kuali.org/jira/brows/KFSMI-5247 CAB is hardcoded to assign Acquisition Type of 'N' to all assets;
3.https://test.kuali.org/jira/brows/KFSMI-5179 Asset Conditions are not reflective of the corresponding
maintenance values that have been established in the system. Quality Assurance will probably have to involve
some sort of plan for testing each eDoc, as well as verifying that all permissions are correct. In addition, verifying
that the Capital Asset Builder and PURAP Purchase Orders are working in sync will be necessary. Verification of
indirect cost calculation; Verification of ability to generate feed for SUNY and successfully send it. Creation of
capital assets through Purchasing / Accounts payable eDocs, which are then used to feed the CAB extract job. Bar
code inventory process will need to be tested.Metrics for run time on batch processes would probably be useful,
especially if batch processing must run while KFS is shut down. Verification of successful routing of each eDoc in
module (where applicable); Verification of business process acceptability.
Testing Plan: Testing Process Overview: Testing of the system has been on-going, but testing of Cornell data will
be needed once the data has been converted. Describe Acceptance Criteria: Capital Assets in information will
need to be converted and balance to financial statements. E-Docs can be properly used and routed. Depreciation
can be calculated correctly. Government reports can be generated. Contingency Plans - We can still use the MAC
system if the current system does not work. We would need to pull the new capital assets information into a
database to calculate depreciation. Testing Roles and Responsibilities: Capital Assets staff in conjunction with KFS
project team. Testing Scope:
A formal testing plan as not been documented but testing will include that acquisition cost, accumulated
depreciation and remaining depreciation reconcile to the current system. Remaining useful lives will be tested.
Once this is completed, testing of the depreciation calculation is necessary. Test Plan: See above
                                               Labor Distribution Module Preliminary Review
                                                      How many test?                       Page
Location Reviewed      Where found? Website           What kind?       Date:      Module   Nos.   Sections
Foundation Functional https://test.kuali.org/conflu ~53 scenarios
Test Scripts (Arizona? - ence/display/KFSIMP/Test+
Kymber Horn)             Scripts+%28Functional%29


KFS Business           https://confluence.cornell.e
Transaction & Fit      du/display/KFSIMPL/Labor+
Analysis (Module       Distribution
Appendix)


Technical            https://confluence.cornell.e
Implementation Plans du/display/KFSIMPL/Labor+
                     Distribution+KFS+Technical
                     +Implementation+Plan#Lab
                     orDistributionKFSTechnicalI
                     mplementationPlan-QA




Business Readiness     https://confluence.cornell.e                    03/05/10
Plans (Project         du/display/KFSIMPL/Project
Management); See       +Management
Draft Functional
Area KFS Business
Readiness Plans
                                                 Labor Distribution Module Preliminary Review

Notes
https://test.kuali.org/confluence/display/KULKFS/Labor+Distribution



Foundation test cases are based on old versions of the application. We may find limited use in these. 1. Data validation from
PeopleSoft Interface to KFS 2. Data validation for Fringe Benefit Calculation, using both endowed and statutory accounts 3.Data
validation for General Ledger Feeds 4.Salary Expense Transfer Routing and Workflow 5.Data validation for LL detail after
Scrubber and Poster Batch jobs 6.Data validation for Benefit Expense totals to GL


Collaborate: Module Team, KITI Team Leads, QA Lead; Testing scope includes: 1.KFS Labor Ledger set-up tables; 2.KFS
Customizations 3.Data conversion programs 4.initial population of PeopleSoft account and object code tables a.PeopleSoft
account distributions b.initial population of KFS Labor ledger balance and detail tables) c.KFS - to - PeopleSoft interfaces
(Accounts, Objects, sub-accounts, sub-objects) 5.End-to-end PeopleSoft payroll process, including job account distribution
updates, earnings detail interface file creation, gross-to-net calculation, reports (NY reimbursement, deduction registers by
vendor, etc) 6.PeopleSoft - to - KFS interfaces (earnings details, encumbrance details, employee benefit charge calculation and
account distribution) 7.KFS Labor Distribution eDocs including Labor Ledger Error Correction Process 8.KFS Labor Distribution
batch processes; Test Plan: Labor Ledger test plan will include the functions listed in the above section. Timing of these tests is
subject to availability of a number of programming tasks for which the schedule is not yet determined. Our goal is for all
PeopleSoft mods, all payroll and KFS Labor Ledger testing and all bug fixes to be complete at least thirty days prior to the
planned go-live date of 7/1/2011. Testing Process Overview: 1.Create test scripts for Kuali processes. 2.Review with the intent
of re-using PeopleSoft 8.9 test scripts. 3.Test each application (PeopleSoft, Kuali, reports) as it is developed 4.Test all
applications as a system as if it were production on July 1, 2011 5.Develop production procedures, error resolution protocols,
and calendars 6.Develop error detection queries for PeopleSoft production 7.Train Payroll Office staff and Production Control to
run Labor Ledger production 8.Train unit level staff 9.Conduct a "dry run" of production 10.Issue weekly status reports (Red,
Green, Yellow) 11. Resolve and/or raise issues to project manager



Testing Process Overview: 1.Create test scripts for Kuali processes. 2.Review with the intent of re-using PeopleSoft 8.9 test
scripts. 3.Test each application (PeopleSoft, Kuali, reports) as it is developed 4.Test all applications as a system as if it were
production on July 1, 2011 4. Develop production procedures, error resolution protocols, and calendars 5.Develop error
detection queries for PeopleSoft production 6.Train Payroll Office staff and Production Control to run Labor Ledger production
7.Train unit level staff 8.Conduct a “dry run” of production 9.Issue weekly status reports (Red, Green, Yellow) 10.Resolve and/or
raise issues to project manager; Describe Acceptance Criteria: The system as a whole must produce the predetermined
results for the primary permutations of employee attributes and earnings types. 1.All standard reports must be available, error-
free at implementation 2.The labor ledger eDocs must work as designed, including the modified employee benefit charge
calculation process. 3.The salary and wage accrual for end-of-the-fiscal-year biweekly payroll must work on July 1, 2011. It must
reverse the entry made in the legacy GL for June 30, 2011. 4.All PeopleSoft Payroll applications must function correctly (produce
checks, reverse checks, compute and withhold taxes and deductions, compute and feed commitment transactions, handle
adjustments, error corrections, associate the proper account numbers, etc. 5.All data conversions and data interfaces must work
correctly; Testing Roles and Responsibilities: All functional testing will be performed by the Payroll Office staff, with support
from OHR-Records, CIT developers and CIT Production Control. In addition, testing will be done by the SET Workgroup. Testing
scope includes: 1.KFS Labor Ledger set-up tables 2.KFS Customizations 3.Data conversion programs 4.initial population of
PeopleSoft account and object code tables a.PeopleSoft account distributions o initial population of KFS Labor ledger balance
and detail tables) b.initial population of KFS Labor ledger balance and detail tables) c.KFS – to – PeopleSoft interfaces (Accounts,
Objects, sub-accounts, sub-objects) 5.End-to-end PeopleSoft payroll process, including job account distribution updates,
earnings detail interface file creation, gross-to-net calculation, reports (NY reimbursement, deduction registers by vendor, etc)
6.PeopleSoft – to – KFS interfaces (earnings details, encumbrance details, employee benefit charge calculation and account
distribution) 7.KFS Labor Distribution eDocs including Labor Ledger Error Correction Process 8.KFS Labor Distribution batch
processes Test Plan: Labor Ledger test plan will include the functions listed in the above section. Timing of these tests is
subject to availability of a number of programming tasks for which the schedule is not yet determined. Our goal is for all
PeopleSoft mods, all payroll and KFS Labor Ledger testing and all bug fixes to be complete at least thirty days prior to the
planned go-live date of 7/1/2011.
                                                 Effort Certification Module Preliminary Review
                                                          How many test?                       Page
Location              Where found? Website                What kind?       Date:      Module   Nos.   Sections
Foundation Functional https://test.kuali.org/confluence/ 19 scenarios      03.16.09
Test Scripts (Arizona? - display/KFSIMP/Test+Scripts+%28
Kymber Horn)             Functional%29;

KFS Business          https://confluence.cornell.edu/di 9                  01.15.09
Transaction & Fit     splay/KFSIMPL/KFS+Transaction+
Analysis (Module      Business+Process+Fit+Analysis
Appendix)




Technical            https://confluence.cornell.edu/di
Implementation Plans splay/KFSIMPL/Effort+Certificatio
                     n+KFS+Technical+Implementation
                     +Plan#EffortCertificationKFSTech
                     nicalImplementationPlan-QA

Business Readiness    https://confluence.cornell.edu/di                    05.06.10
Plans (Project        splay/KFSIMPL/Project+Managem
Management); See      ent
Draft Functional
Area KFS Business
Readiness Plans
                                                    Effort Certification Module Preliminary Review

Notes
https://test.kuali.org/confluence/display/KULKFS/Effort+Reporting?




High-Level test cases: User nbtetrea; 1.Test Creation of Action Lists after Batch Jobs 2. Test replacement of forms in action lists
after a new batch job is run that replaces old 3.Test the logic for the Extract Batch Job 4.Test Completion of Effort Certification
Reports 5.Verify creation of salary expense transfer reports from Effort Certification Process 6.Workflow routing. Testing all the
combinations of possible workflow routing a form could take based on the different approver roles and different times a form
could be adjusted within the approval process. 7.Testing Salary Expense Transfers (SET) in relation to the EC process. Processing
SET during the different EC period status (N, O, C). There were a large number of very specific test cases for this testing area.
8.Testing the recreate process. When can recreates be processed based on EC period status (N, O, C) and approval status of
original EC form. 9.Testing updates made in EC forms. Changing $$s/%%s, hard stops or errors received for business rules that
are broken when changes made to accounts that may be closed, restricted, etc. For more test cases from the Kuali Foundation:
Effort Certification Testing




Collaborate: Module Team, KITI Team Leads, QA Lead; A high level functional test cases have been identified in module appendix
at https://confluence.cornell.edu/x/8KfXBg; Some test cases have been found at foundation website:
https://test.kuali.org/confluence/display/KULKFS/Effort+Reporting




Security/Access Validation Plan: It is planned that only individuals in the route log will be able to view the effort certification
reports along with central staff. Interfaces Plan: Capital Assets feeds CRIS (Comprehensive Rate Information System) from the
general ledger, labor ledger, facilities inventory, capital assets and other sources. This is identified for remediation. Testing
Plan Testing Process Overview: see above Describe Acceptance Criteria: Correct data is included in the reports. Reports are
routed correctly. Project Directors and Financial Administrators understand the process and are able to certify effort (usability).
The reports meet standards established by the federal government. Testing Roles and Responsibilities: n/a Testing Scope: Cost
transfers must be made within 90 days. Reports are approved in a timely manner. Test Plan: High Level testing plans have been
identified but are not documented at this time.
                                                         Contracts and Grants Module Preliminary Review

                                                     How many test? What                                    Page
Location                   Where found? Website kind?                    Date:        Module                Nos.    Sections
Foundation Functional      https://test.kuali.org/co 0 tests              12/22/2009 Contracts & Grants
Test Scripts (Arizona? -   nfluence/display/KFSIMP
Kymber Horn)               /Test+Scripts+%28Functi
                           onal%29
KFS Business               https://confluence.corne                         4/22/2010 Contracts & Grants    14,    *Laran Evans has not been
Transaction & Fit          ll.edu/pages/viewpage.a                                                          15, 19 replaced.
Analysis (Module           ction?pageId=123552368
Appendix)




Technical             https://confluence.corne 1.Minimal Usability       Confluence   Contracts & Grants;           Incomplete sections: Testing
Implementation Plans ll.edu/pages/viewpage.a Requirements*;                           Chart of Accounts;            Roles and Responsibilites;
                      ction?pageId=123552368 2.Access/Security*                       Purchasing; Capital           Testing Scope; Test Plan;
                                               3.Issues/Outstanding                   Assets; Financial             *Laran Evans has not been
                                               Questions                              Processing                    replaced.
Business Readiness    https://confluence.corne                               5/7/2010 Contracts & Grants    9, 10   Incomplete sections: Testing
Plans (Project        ll.edu/display/KFSIMPL/P                                                                      Roles and Responsibilites;
Management); See      roject+Management                                                                             Testing Scope; Test Plan
Draft Functional Area                                                                                               *Laran Evans has not been
KFS Business                                                                                                        replaced.
Readiness Plans
                                                           Contracts and Grants Module Preliminary Review


Notes
Not test cases: https://test.kuali.org/confluence/display/KFSIMP/Contracts+and+Grants



High-level Test Case: Testing Scenarios from Foundation to test previous issues:
https://test.kuali.org/confluence/pages/viewpage.action?pageId=30043; High Level Test Scenarios
1. Validation of the functionality related to customization 2.Validation of workflow routing for initiation of new,
changes and approval of Contracts and Grants accounts and sub accounts 3.Validation of functionality related to
account termination and posting of transactions after termination 4.Validation of functionality related to sufficient
funds checking 5.Testing for changes to Indirect Cost Rates: limitation to access 6.Test transactional routing for Cost
Share accounts 7.Validation for workflow routing for transactions initiated for Contracts and Grants accounts
8.Validation of role that can update Indirect Cost Maintenance eDocs 9.Validation of budget : initiation of new,
changes and approval using Budget Adjustment eDoc 10.Validation of initiation of new, changes and approval of
proposals and awards
11.Validation of batch jobs: a.Data validation for Indirect Cost transactions detail after Scrubber and Poster Batch
jobs; b.Data validation for CFDA upload after the cfda batch job is run; c.Data validation for proposal and award
active indicator after the close job is run
Collaborate: Module Team, KITI Team Leads, QA Lead: {The module-specific QA strategy must include unit testing,
technical testing and functional testing that will take place over the life of the implementation effort.} • High Level
Test Scenarios:1.Validation of the functionality related to customization; 2.Validation of workflow routing for
initiation of new, changes and approval of Contracts and Grants accounts and sub accounts

Testing Plan: Testing Process Overview: SFS will conduct testing of both the C&G module and reporting tools to
ensure that they meet unit needs. Testing Roles and Responsibilities: Janet Strait, as C&G Module Lead is
responsible for overall testing of the C&G Module. Ilene Lambiase will be responsible for overseeing testing of SFS-
specific KFS needs. SFS staff, supplemented with other university participants as appropriate will be utilized as
testers.Testing Scope: Key processes including: 1.C&G account set up 2.Routing of transactions to SFS 3.Preparation
of data for invoicing 4.Reporting on costs and cost sharing for periodic and final reporting 5.Award close out...will all
be tested. Test Plan: N/A {Testing ensures that the system operates in the manner expected, and that any
supporting material such as reports, queries, user manuals, procedural documentation, forms, etc. are accurate and
suitable for the intended purpose. Describe your high level testing plan and significant milestones (developed in
concert with the KFS QA lead) and include link to detailed testing plan and test cases.}
                                      Endowment Module Preliminary Review

                                                How many test? What                  Page
Location                 Where found? Website   kind?               Date:   Module   Nos.
Foundation Functional
Test Scripts (Arizona? -
Kymber Horn)

KFS Business
Transaction & Fit
Analysis (Module
Appendix)




Technical
Implementation Plans




Business Readiness
Plans (Project
Management); See
Draft Functional Area
KFS Business
Readiness Plans
           Endowment Module Preliminary Review


Sections
                                    Endowment Module Preliminary Review


Notes
As of 7/29/10, the Endowment Module hasn't begun.

								
To top