11. Individual SOA projects

In this section we would like to collect some detailed information about individual SOA projects or initiatives that you have undertaken in the last 18 months. The

section allows for up to 2 projects. However, if there are more you would like to share, there is a freeform text box at the end of the section.

Project #1

11.1, 2, 3 Name, URL and lifecycle stage of project

11.4, 5 What are the goals of the project (technology goals and business goals)

UBC

• Goals Develop a RESTful API for our SIS
  • Student demographics
  • Enrolment
  • Course Catalog
    

Michigan
Cornell

• Goals Spark mobile innovation on campus by providing an environment where student, staff, and research developers can collaborate and find the tools and data they need to create mobile applications.
• Comments Enterprise mobile apps, which have mostly been focused on student functionality are now being developed using the Kuali Mobility Enterprise framework. Web services that are developed for mobile applications are planned to be published to the community and will be encouraged to be reused.
  

Georgetown

• Goals
  • Business: Replace existing applications with a modern HCM/Payroll/Benefits solution with improvements in reporting, business process management, auditability. Implement an integrated solution that also includes Finance and Grants in future phases.
  • Technology: End of life legacy mainframe applications. Implement a cost effective cloud based solution. Real-time integration of HR system with identity management system (using web services). Standardize other integrations (using web services whenever possible) and take advantage of vendor-delivered integrations with business partners.
    

11.6 What business domains does this project address?

Project #1

11.1, 2, 3 Name, URL and lifecycle stage of project

11.4, 5 What are the goals of the project (technology goals and business goals)

UBC

• Goals Develop a RESTful API for our SIS
  • Student demographics
  • Enrolment
  • Course Catalog
    

Michigan
Cornell

• Goals Spark mobile innovation on campus by providing an environment where student, staff, and research developers can collaborate and find the tools and data they need to create mobile applications.
• Comments Enterprise mobile apps, which have mostly been focused on student functionality are now being developed using the Kuali Mobility Enterprise framework. Web services that are developed for mobile applications are planned to be published to the community and will be encouraged to be reused.
  

Georgetown

• Goals
  • Business: Replace existing applications with a modern HCM/Payroll/Benefits solution with improvements in reporting, business process management, auditability. Implement an integrated solution that also includes Finance and Grants in future phases.
  • Technology: End of life legacy mainframe applications. Implement a cost effective cloud based solution. Real-time integration of HR system with identity management system (using web services). Standardize other integrations (using web services whenever possible) and take advantage of vendor-delivered integrations with business partners.
    

11.6 What business domains does this project address?