Berkeley has been developing web services for 8 years but they were unstructured, undocumented, not inventoried, and rarely shared. The university wants to transition to a SOA to enable flexibility, speed up development through reuse, and ensure quality. However, adopting SOA presents challenges around technologies, processes, culture and resources that need to be addressed.

2. From Services to SOA at Berkeley CSG - Sept 25, 2008 THE SOFTWARE GOAL: Quality, Speed, Flexibility. THE TRENDS: Increasingly complex and changing business processes. Increasingly tech savvy business partners. Increase dept/unit development of mission critical systems. Decrease in resources while increase in IT demands. THE CHALLENGE : How to get UC Berkeley from a set of unorganized, unstructured web services to SOA? We need help. We don’t have the right experience or enough of the right resources. Berkeley became Kuali Student Founder July, 2007.

7. KS & Rice Planned Alignment UI Middleware Eclipse Workbench Mapping Frameworks Technology Stack Google Web Toolkit uPortal 3.0 Id Mgmt: KIM Workflow: KEW Rules: BRMS Dictionary, Search: KNS Code Mgmt: Subversion Build: Maven Unit Test: JUnit JPA: Hibernate JAXB JAX-WS DB: Derby Service Eng: CXF/Metro Servlet: Tomcat ESB: ServiceMix Rules Eng: Drools KS & Rice Planned Alignment KS - Jan 1, 2008