Enterprise SIG, University of Nottingham

1
ADoM and DELIA

• a family of eAdmissions projects

2
ADoM and DELIA

• Separate but related
• Partners
• Cousin PortisHEad

3
ADoM

• 15 months
• Domain map (new name for reference model)
• Previous RM projects COVARM, eP4LL, FREMA,
  LADIE, PLE, XCRI

4
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

5
The Role of Domain Models (Bill again)
A Domain Model shows howthe needs of its
practitioners can be met by a set of Services
A Domain Model may used to help buildReference
Implementations, Demonstrators and/or
Institutional Service Architectures

• Domain Models form a Bridge between Users Needs
  Services

6
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

7
ADoM the process

• Process modelling workshops and interviews
• Draw up initial map
• Engage community to refine model
• Wiki
• SIG
• Other?
• Produce demonstrators

8
ADoM the outcomes

• Blueprint for shared best practice
• Feed into further work
• Add to e-Framework
• Feedback on Domain Map concept

9
DELIA

• Delivering Enhanced Learner Information for
  Admissions
• 21 months

10
DELIA context

• Schwartz/Wilson reviews
• HE admissions review Delivery Partnership/SPA
• Specifying an ePortfolio/eP4LL/XCRI work
• Scoping studies (Fairness, applicant feedback)

11
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?

12
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)

13
DELIA method

• Capture practice
• Outline technical spec
• Trialling (staff and students)
• Prototyping
• Scenarios and use cases