Corporate Systems and Educational Purposes JISC-CETIS 2010 #cetis10scs Jim Everett Reorganisation and Review Aspirations Remove unnecessary steps Stamp out repetition, duplication and variation Single source data Simplify access to data Squaring the Circle? Review of Course and Class Approval and Review General agreement that current arrangements are not tenable Process modelling Information flow not data structures Decision points not timings or criteria Highlight areas of ambiguity/complexity Propose some innovations Generalised model addressing the “common variations” BPMN diagram Predicated on a data management solution System’s architecture and technologies overview Presentation Layer User Interface Components, Presentation Logic SharePoint UI, ASP.NET, jQuery, AJAX Service Layer Orchestration, Service Interfaces, Message Types Windows Workflow Foundation, Web Services Business Layer Domain Model, Business Entities, Business Workflows Domain-Driven-Design, Windows Workflow Foundation, .NET Data Access Layer O/R Mapping, Service Agents NHibernate, SharePoint Object Model / Web Services Access Components Data Stores SQL Server, SharePoint Lists, Document Libraries Interoperability Problems The data structures are not the problem! There is a place to hold all the data (more or less) The problems/bottlenecks/issues centre on Putting the information into the process On time Complete Compliant with requirements Getting access to the information When needed In a reusable form Not buried in a mass of irrelevant data Corporate v. Education? Academic Entrepreneurs v Academic Innovators Problem is too much entrepreneurialism Impose discipline on entrepreneurs Problem is NOT too much innovation Good policies, but not embraced Training and resources, accessed by a few Harness corporate processes to provide information to quality monitoring Standards and Specifications Entirely driven by demands of external agencies HESA, UCAS, Hot Courses Diploma Supplements, Teachers' Profiles Generally poor fit with internal data requirements Often need to tailor data making whole automated extraction problematic No desire to pro-actively adopt external data models, especially for internal applications Reflections Jim Everett Development and Innovation Unit Information Services Directorate jim.everett@strath.ac.uk @jeestirling PiP: Principles in Patterns Project http://www.principlesinpatterns.ac.uk