|
A Financial System of, by, and for Higher Education |
|
Archived Updates |
|
Kuali Update April 18th—May 2rd, 2005 |
|
Highlights - April 18th—May 23rd, 2005 Functional Council Meeting April 27th-29th - The Functional Council, AP/Purchasing Representatives and the Technical Council met in Indianapolis at the end of April. Day 1- each schools AP & Purchasing representatives reviewed the AP/Purchasing Module (EPIC) and identified and ranked enhancements;
Day 2- Functional Council met with the Technical Council (developers), completed design critique session 2, answered developer questions.
Day 3 - Functional Council assigned Lead SMEs for each module, reviewed Kuali Enhancement Requests prepared for General Ledger, Chart of Accounts and Transaction Processing and assigned Functional Council members to write up the AP/Purchasing enhancement requests; defined the duties/responsibilities of the Lead SME. · Functional Council Meeting Summary · Second Design Critique Session
Business Rules: · Brian McGough answered the workflow questions raised in Arthur's document ( page 12 - item 5). Module updates: AP/Purchasing - Several of the Arizona AP/Purchasing SMEs went to Indianapolis to review the AP/Purchasing module and identified enhancments. They are in the process of reviewing the AP/Purchasing enhancement requests. AP/Purchasing Kuali Enhancement Requests Endowments - MSU, IU Foundation and Arizona will be demoing the systems they use to manage endowments via NetMeetings. MSU will be demoing their system May 2nd - details will be provided as they become available. ERA/CnG (Electronic Research Administration/Contracts & Grants) - Oregon State University has joined Kuali to work only on this module. They are contributing 3 developers; consequently work has begun. The Arizona Subject Matter Expert (SME) subcommittee lead by Sherry Esham and Lori Schultz are having their first meeting to prepare comments on the Enhancement Requests for this module. ERA/CnG Kuali Enhancement Requests General Ledger and Financial Transactions - have been combined into one subcommittee and this group will be meeting shortly to kick off these modules. Chart of Accounts, Workflow and Decision Support System/Basic Reporting - Some preliminary work has begun on these modules and we will be meeting with the SME subcommittees in the next few weeks to kick off these modules. Accounts Receivable, Budget, Capital Assets and Labor Ledger modules have not yet begun. Testing: There will be two types of testing - usability and functionality. Usability testing works on the look, feel and navability using screen mock ups. The results of the usability testing will be incorporated into a standards document to be applied across all screens/documents. When the users go to Indiana they will be video taped as they move through screens. They will be asked questions as they progress - "why did you push that button - what did you think was going to happen, etc." The UXG team will compile the results which will be provided to the developers for incorporation in the production Kuali screens and used to create a standards document to be used across all Kuali screens/documents. Each school has been asked to identify two "real" users. These users will be doing some usability testing over netmeetings, will travel to Indiana for a couple of sessions where they will be video taped. Plans are in the work for the IU Usability Experience team to travel to each school to do some additional testing with 10-16 users. Margo Santucci (College of Ag) and Lisa Laatsch (ARL) have been volunteered as the "real users" who will be representing Arizona. Functionality testing will test whether or not the application is working correctly. A person has been hired for the Kuali Project to write up functional specifications document on each of the FIS eDocs and the approved enhancements. The functional specifications document will be reviewed and approved by the Subject Matter Experts and their subcommittees. Once finalized the functional documents will be given to the developers. The developer will work with the Lead SME of each module for clarification as necessary. The Lead SME will also be responsible for the first functional testing. Followed by the SMEs from each school, then the SME subcommittee and other campus users will complete the testing. |
