130 likes | 282 Views
ADoM and DELIA. a family of eAdmissions projects. ADoM and DELIA. Separate but related Partners: Cousin PortisHEad. ADoM. 15 months Domain map (new name for reference model) Previous RM projects: COVARM, eP4LL, FREMA, LADIE, PLE, XCRI. Domain model…. (pace Bill Olivier).
E N D
ADoM and DELIA a family of eAdmissions projects Enterprise SIG, University of Nottingham 20 April 2007
ADoM and DELIA • Separate but related • Partners: • Cousin PortisHEad Enterprise SIG meeting, University of Nottingham 20 April 2007
ADoM • 15 months • Domain map (new name for reference model) • Previous RM projects: COVARM, eP4LL, FREMA, LADIE, PLE, XCRI Enterprise SIG meeting, University of Nottingham 20 April 2007
Domain model…. (pace Bill Olivier) • Reusable domain knowledge • Basis for practitioners to: • Agree problem areas • Collaborate with developers • Ensure coherence across ‘family’ of applications • Save redoing the same work (differently) each time Enterprise SIG meeting, University of Nottingham 20 April 2007
User Needs Reference Implementations, Demonstrators,Institutional SOAs Design Domain Model Services The Role of Domain Models(Bill again) Domain Models form a Bridge between Users’ Needs & Services A Domain Model shows howthe needs of its practitionerscan be met by a set of Services A Domain Model may used to help buildReference Implementations, Demonstrators and/or Institutional Service Architectures Enterprise SIG meeting, University of Nottingham 20 April 2007
Domain Models & Engagement(a bit more Bill) • How are needs to be identified? • not just for an Institution, • but across a Sector? • Need to work with • Users and Practitioners • Domain Experts and broader Stakeholders • To Map and Model their Domain, so as to: • Reflect on current Practices and Processes • Identify Problem Areas & New Opportunities • Set out what is common across multiple applications, as a basis for identifying services Enterprise SIG meeting, University of Nottingham 20 April 2007
ADoM: the process • Process modelling: workshops and interviews • Draw up initial map • Engage community to refine model • Wiki • SIG • Other? • Produce demonstrators Enterprise SIG meeting, University of Nottingham 20 April 2007
ADoM: the outcomes • Blueprint for shared best practice • Feed into further work • Add to e-Framework • Feedback on Domain Map concept Enterprise SIG meeting, University of Nottingham 20 April 2007
DELIA • Delivering Enhanced Learner Information for Admissions • 21 months Enterprise SIG meeting, University of Nottingham 20 April 2007
DELIA: context • Schwartz/Wilson reviews • HE admissions review: Delivery Partnership/SPA • Specifying an ePortfolio/eP4LL/XCRI work • Scoping studies (Fairness, applicant feedback) Enterprise SIG meeting, University of Nottingham 20 April 2007
Course Entry Profiles • 100% mandatory from Sept 2008 • What scope for a common framework/structure? • Link to structured personal statements/ePortfolio evidence • How will admissions staff use enhanced data? Enterprise SIG meeting, University of Nottingham 20 April 2007
DELIA: the recipe • Explore pre-admissions practices (not just tests!) • Structured course entry profiles: development and use (improve self-matching and assessment of aptitude and potential) • Define business processes for handling enhanced data • Requirements engineering through prototyping • With ADoM, demonstrate potential of electronic admissions • Propose UCAS security model for ePortfolio-based admissions (with PortisHEad) Enterprise SIG meeting, University of Nottingham 20 April 2007
DELIA: method • Capture practice • Outline technical spec • Trialling (staff and students) • Prototyping • Scenarios and use cases Enterprise SIG meeting, University of Nottingham 20 April 2007