Domain Modeling In FREMA David Millard Yvonne Howard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University of Southampton, UK.

Slides:



Advertisements
Similar presentations
Andrea Maurino Web Service Design Methodology Batini, De Paoli, Maurino, Grega, Comerio WP2-WP3 Roma 24/11/2005.
Advertisements

OMV Ontology Metadata Vocabulary April 10, 2008 Peter Haase.
EPortfolio for Lifelong Learning Angela Smallwood Peter Rees Jones Sandra Kingston Exemplifying the value of the eFramework A.
Chapter 11 Designing the User Interface
Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
A centre of expertise in digital information management UKOLN is supported by: An introduction to … OAIS and reference models for repositories.
Evaluation Mary Rowlatt MDR Partners. Definition of project evaluation Evaluation focuses on whether the project was effective, achieved its objectives,
Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 12, 2001 Capturing.
The Innovation Base Tom Franklin Franklin Consulting Hilary Dexter University of Manchester.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
e-Framework Components and Responsibilities.
2006 Ontopia AS1 Towards an Ontology Design Methodology Initial work Lars Marius Garshol CTO, Ontopia TMRA
The Innovation Base Tom Franklin Franklin Consulting Hilary Dexter University of Manchester.
CLAReT PERSONAS AND SCENARIOS. When? Personas were used in the CLAReT workshops as a role play activity. Participants were required to assume a persona.
FREMA: e-Learning Framework Reference Model for Assessment David Millard Yvonne Howard Learning Technology Group University of Southampton, UK.
Thee-Framework for Education & Research The e-Framework for Education & Research an Overview TEN Competence, Jan 2007 Bill Olivier,
Context Map Hands-On Session April 2007 David Millard Learning Societies Lab University of Southampton Kate Dickens, Ann Jeffery, Julie Watson, Kate Borthwick.
FREMA: e-Learning Framework Reference Model for Assessment Yvonne Howard David Millard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University.
FREMA: e-Learning Framework Reference Model for Assessment David Millard Yvonne Howard IAM, DSSE, LTG University of Southampton, UK.
FREMA : e-Learning Framework Reference Model for Assessment Assessment: Priorities and Challenges for 2006 Hugh Davis Learning Technologies University.
Introduction and Hands-On Session June 2007 David Millard, Yvonne Howard Learning Societies Lab University of Southampton Kate Dickens, Ann Jeffery, Julie.
Cherchez the ‘Learning Object’ Workshop November 2007 David Millard, Gary Wills, (Yvonne Howard) Learning Societies Lab University of Southampton Julie.
FREMA: e-Learning Framework Reference Model for Assessment Design Patterns for Wrapping Similar Legacy Systems with Common Service Interfaces Yvonne Howard.
FREMA Lester Gilbert Dave Millard Yvonne Howard An ELF Reference Model Project In the JISC Distributed e-Learning Programme e-Learning Framework Reference.
FREMA: e-Learning Framework Reference Model for Assessment Lester Gilbert David Millard Yvonne Howard University of Southampton, UK University of Strathclyde,
David Millard Karen Fill Hugh Davis Lester Gilbert Gary Wills Learning Societies Lab, University of Southampton, UK.
FREMA : e-Learning Framework Reference Model for Assessment FREMA Overview David Millard Learning Technologies University of Southampton, UK.
UFCEPM-15-M Object-oriented Design and Programming Jin Sa.
FREMA : e-Learning Framework Reference Model for Assessment Hugh Davis, Yvonne Howard, David Millard,
FREMA : e-Learning Framework Reference Model for Assessment FREMA Workshop Hugh Davis David Millard Yvonne Howard Learning Technologies University of Southampton,
Course Instructor: Aisha Azeem
Chapter 13: Designing the User Interface
Domain Modelling the upper levels of the eframework Yvonne Howard Hilary Dexter David Millard Learning Societies LabDistributed Learning, University of.
MDC Open Information Model West Virginia University CS486 Presentation Feb 18, 2000 Lijian Liu (OIM:
School of something FACULTY OF OTHER School of Computing FACULTY OF ENGINEERING Sharing of Community Practice through Semantics: A Case Study in Academic.
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
Learning Technology Interoperability Standards Niall Sclater, and Lorna M. Campbell,
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Knowledge based Learning Experience Management on the Semantic Web Feng (Barry) TAO, Hugh Davis Learning Society Lab University of Southampton.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
Communications support for the Vodafone EMF community Pre-read for EMF Leader Workshop, 8 April 2008 Dianne Sullivan & Ros Young.
References: [1] [2] [3] Acknowledgments:
JISC e-Framework Innovation Knowlegebase An Overview David Millard (University of Southampton) Tom Franklin (Franklin Consulting)
10/12/ Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews & questionnaires.
The Brain Project – Building Research Background Part of JISC Virtual Research Environments (Phase 3) Programme Based at Coventry University with Leeds.
© DATAMAT S.p.A. – Giuseppe Avellino, Stefano Beco, Barbara Cantalupo, Andrea Cavallini A Semantic Workflow Authoring Tool for Programming Grids.
Linking research & learning technologies through standards 1 Lyle Winton lylejw AT unimelb.edu.au.
CLARIN work packages. Conference Place yyyy-mm-dd
UML-1 8. Capturing Requirements and Use Case Model.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
SKOS. Ontologies Metadata –Resources marked-up with descriptions of their content. No good unless everyone speaks the same language; Terminologies –Provide.
Portable Infrastructure for the Metafor Metadata System Charlotte Pascoe 1, Gerry Devine 2 1 NCAS-BADC, 2 NCAS-CMS University of Reading PIMMS provides.
Domain Modeling In FREMA Yvonne Howard David Millard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University of Southampton, UK.
Issues in Ontology-based Information integration By Zhan Cui, Dean Jones and Paul O’Brien.
1 Class exercise II: Use Case Implementation Deborah McGuinness and Peter Fox CSCI Week 8, October 20, 2008.
WISER: Teaching Information literacy This session will give an overview of the key concepts and models of information literacy as an important transferable.
Approach to building ontologies A high-level view Chris Wroe.
Use Case Model Use case description.
Supporting further and higher education E-learning Framework and Tools Tish Roberts JISC Programme Manager.
Be.wi-ol.de User-friendly ontology design Nikolai Dahlem Universität Oldenburg.
Ontologies for the Semantic Web Prepared By: Tseliso Molukanele Rapelang Rabana Supervisor: Associate Professor Sonia Burman 20 July 2005.
Joint Information Systems Committee 11/03/2016 | slide 0 e-Framework Next Generation - Sharing Learning & Creating Value Joint Information Systems CommitteeSupporting.
How to use C OBI T implementation resources Brian Selby Director of C OBI T Initiatives ISACA.
Metadata Schema Registries: background and context MEG Registry Workshop, Bath, 21 January 2003 Rachel Heery UKOLN, University of Bath Bath, BA2 7AY UKOLN.
© Copyright 2010 Rockwell Collins, Inc. All rights reserved. Practical SysML Applications: A Method to Describe the Problem Space Ray Jorgensen David Lempia.
Model Checking Early Requirements Specifications in Tropos Presented by Chin-Yi Tsai.
Learning Technology Interoperability Standards Lorna M. Campbell and Boon Low CETIS and the University of Strathclyde LMC, SURF Presentation, April 2002.
ServiceNow Implementation Knowledge Management
FREMA: e-Learning Framework Reference Model for Assessment
Presentation transcript:

Domain Modeling In FREMA David Millard Yvonne Howard Hugh Davis Gary Wills Lester Gilbert Learning Societies Lab University of Southampton, UK

What is FREMA? The e-Framework REference Model for Assessment JISC funded Project between Southampton, Strathclyde and Hull Aim to produce a Reference Model of the e- Learning Assessment Domain To aid interoperability and aid in the creation of Assessment Services for the e-Framework

FREMA Definitions What is a Reference Model? –A guide to help developers create web services that work with one another –But there is more than one type of guide A standard data format A best practise example of service design A methodology for creating or describing services A description of what is currently available What is a Reference Model for Assessment? –Assessment is a broad and complex domain –Many different assessment scenarios More than one data model More than one set of cooperating services –An active Community requires an evolving model

Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model 1

The FREMA Use Case Stakeholders and Personas 1

Personifying the actors Will, Web services developer –Scenario: ‘I want to lookup use cases and scenarios to help me design my application. This will help me to define my footprint in the assessment domain. I see there are some web services I could download but some are missing. What standards can I use when writing my own web services to ensure that I can interoperate with the web services I’ve chosen?’ Yvonne, Institutional Resource Manager –Scenario ‘I want an overview of what this domain is all about. I want to know what standards are applicable in the domain to ensure that we comply with quality assurance requirements. I want to examine use cases and scenarios to understand the available footprints. I also want to know who the key players are and what the key projects are.’ Other Actors –Early Adopter –Toolkit developer –Course developer –And there are others... Stakeholders and Personas 1

The Domain Actors These stakeholders are using the Domain Model There are other stakeholders who exist within the domain itself These will be identified as Actors in Scenarios For example, the external examination process –External examiner –Internal examiners –Teachers –Students –Etc… These can also be defined as actors in use cases, and described as personas Stakeholders and Personas 1

Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model 1 Concept Maps 2

Concept Mapping We built concept maps of the domain of Assessment –Series of expert workshops produced drafts –These were taken to the community and opinions fed back –Concept maps revised over time Engaged the community Built into a concept map tool for browsing –All resources will be linked to at least one concept –Users viewing the map can select concepts to see all the related resources –Unlike directories, or search tools, they don’t need to know what they are looking for! Concept Maps 2

FREMA Concept Map (verbs) Concept Maps 2

Concept Mapping But also an important activity in its own right Focused on the key activities in the domain (the functions) Captured the domain knowledge of the experts –The goals in the domain –Important functions –Entities in the domain –Begins to structure the knowledge Built a shared understanding of the domain –Common vocabulary of domain areas Concept Maps 2

Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model 1 Concept Maps 2 FREMA Ontology 3

A Knowledge Base Decided to deliver our domain model as a searchable, flexible, dynamic website Built on a knowledge base –Requires an ontology of resources in the domain with relationships between them –The ontology is the schema that describes what types of resources and relationships are allowed –(Ontology means the study of existence, and an ontology is a particular view of existence) The ontology is different than the concept map –Concept maps shows areas of the domain –Ontology shows what type of thing can be in the domain FREMA Ontology 3

The FREMA Ontology FREMA Ontology 3 what who

Concept Maps FREMA Ontology Semantic Wiki Pages Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model

A Dynamic Website Need to turn our Knowledge Base into a website Can be done dynamically –Resources displayed as web pages –Relationships displayed as hypertext links –Resources are also placed on the concept maps The ontology and the concept maps offer alternative interfaces –Concept maps are more intuitive –Ontology is more structured Semantic Wiki Pages 4

Ontology Example Project: FREMA Organisation: JISC Organisation: University of Southampton Is funded byIs involved in JISC frema FREMA Southampton JISC Uni Soton frema Semantic Wiki Pages 4

Implementing the Website Semantic Wiki Pages 4

Semantic Wiki –a wiki in which all the pages and links are typed Open editing, but with Administrator controls Users can edit –Resources –Relationships between resources –The ontology itself Enables full evolution of the Domain Information and System models Enables Smart Searching and Analysis –Semantic Search –Dynamic Gap Analysis Semantic Wiki Pages 4

Browsing the Wiki Semantic Wiki Pages 4

Dynamic Gap Analysis Semantic Wiki Pages 4

Concept Maps FREMA Ontology Semantic Wiki Pages Use Cases and Interaction Diagrams Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model

FREMA Scenarios Scenarios capture a certain activity (function) within the Domain Can be captured at different levels of formality From narrative descriptions Through to real interacting services Use Cases and Interaction Diagrams 5 formality Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations

Service Usage Model Describes a scenario in which services work together Use Case Diagram Set of Abstract Logical Service Expressions Interaction Diagram Use Cases and Interaction Diagrams 5 FREMA Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations

Use Cases and Narratives Formal as a Use Case Diagram Informal as a Narrative Description Use Cases and Interaction Diagrams 5 FREMA Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations

Service Expression: SRC Logical, abstract description FREMA Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations Use Cases and Interaction Diagrams 5

Service Interaction: Overview FREMA Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations Use Cases and Interaction Diagrams 5

Service Interaction: Diagram FREMA Written Scenarios Use Cases Service Expressions Service Interactions Service Interfaces (WSDL) Service Workflows (BPEL) Service Implementations Use Cases and Interaction Diagrams 5

Concept Maps FREMA Ontology Semantic Wiki Pages Use Cases and Interaction Diagrams Stakeholders and Personas Domain Modelling Domain Context Stakeholders and Role Models Domain Information Model Scenarios (workflows and narratives) Domain System Model Goal and Function Model

Scenario: Technical Developer Will, Technical Developer ‘I want to lookup use cases and scenarios to help me design my application. This will help me to define my footprint in the assessment domain. I see there are some web services I could re-use but some are missing. What standards can I use when writing my own web services to ensure that I can interoperate with the web services I’ve chosen?’

How did things go? Excellent reaction from the Community –Lots of engagement (concept mapping) –Has helped the community to understand their domain –Useful resource for people researching the domain (reading) But limited contribution to the Wiki itself –Reading is as easy as browsing the web –Writing takes more technical skill Perceived as intimidating Overhead of adding your project details Openess vs. Control –Finding a guardian (Assessment SIG?) –Protecting the Wiki Have had some limited problems with spam Future Plans –Currently evaluating the Wiki through our own tools projects –Looking to build more natural authoring tools –Activities to help the community to get over the authoring barrier

Afternoon Workshop Hands-on activity A chance to try out some of the FREMA methodology for Domain modelling –Stakeholder and Persona modelling –Concept Mapping –Ontology Construction –Authoring in a Semantic Wiki We’ll be very pleased to see you!