Services for Kuali Rice

Our experience with other Rice projects has allowed us to develop the Kuali Rice Proof of Concept (POC), a methodology that effectively prepares institutions to use Kuali Rice. The rSmart Rice POC provides consulting and developer training as well as ongoing developer support and coaching throughout the engagement so that you can successfully develop applications and streamline business processes using Kuali Rice.

The Kuali Rice Proof of Concept includes the following four phases.

Phase 1 – On-site Kuali Rice consulting and hands-on training

Kuali Rice training—5 days, on-site

• Provide hands-on training and set-up of Kuali Rice developer environment
   
• Provide developer training on:
  
  • Kuali Enterprise Workflow
  • Kuali Nervous System
  • Kuali Enterprise Service Bus
  • Kuali Identity Management
     
• Include and provide exercises on:
  
  • Data dictionary
  • Business objects
  • Simple maintenance documents
  • Business rules
  • Formatter
  • Validation and rrror handling
  • Exception handling
  • Transactional documents
  • Java searchable attributes
  • Authentication/authorization (KIM)
  • Java workflow (KEW nodes, roles, permissions, groups, etc)
  • Extended attributes
• Evaluate additional training needs prior to Phase 2

Phase 2—On-site Workflow Prototyping Workshop, part 1

Workflow Prototyping Workshop—5 days, on-site

• Workflow Prototype Workshop – design strategy, set up, development
  • Review requirements for applications (completed prior to visit)
  • Design strategy/coaching
  • Plan application design project
  • Creating technical specifications
  • Architecting the system
  • Setting up version control
  • Setting up Rice project
  • Pair programming to develop initial parts of code
  • Hands-on development
     
• Evaluate additional training needs

Phase 3—On-site Workflow Prototyping Workshop, part 2

Workflow Prototyping Workshop—5 days, on-site

• Workflow Prototyping Workshop—development, review, refactoring
  • Continuing hands-on development
  • Code reviews
  • Merge process for upgrading Rice code
  • Refactoring
  • Enhancements
  • Documentation
     
• Evaluate additional training needs

Phase 4—Off-site developer support, coaching and code review

Developer support, code review and recommendations—6 months, off-site

• Ongoing support of developers as they develop applications
  • Planned weekly/bi-weekly review calls
  • Code review
  • Ad hoc developer support
  • Issue resolution
     
• Coaching
   
• Workflow analysis and recommendation (end of engagement)
  • Joint review of success criteria
  • Deployment recommendations