Transcript Domain Modeling In FREMA CAA Presentation

Domain Modeling In FREMA
Yvonne Howard
David Millard
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
• 2004 - 2006
• Aim to produce a Reference Model of the eLearning Assessment Domain
• To aid interoperability and aid in the creation of
Assessment Services for the e-Framework
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 practice 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
FREMA
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
Goal and Function
Model
Domain System
Model
Scenarios
(workflows and narratives)
1
Stakeholders
and Personas
The FREMA Use Case
1
Stakeholders
and Personas
•
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 . . .
1
Stakeholders
and Personas
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
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
Goal and Function
Model
2
Concept Maps
Domain System
Model
Scenarios
(workflows and narratives)
2
Concept Maps
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!
2
Concept Maps
FREMA
Concept
Map
(verbs)
2
Concept Maps
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
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
3
Goal and Function
Model
FREMA Ontology
2
Concept Maps
Domain System
Model
Scenarios
(workflows and narratives)
3
FREMA Ontology
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 from the concept maps
– Concept maps shows areas of the domain
– Ontology shows what type of thing can be in the domain
3
FREMA Ontology
The FREMA Ontology
who
what
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
3
Goal and Function
Model
FREMA Ontology
2
Concept Maps
Domain System
Model
Scenarios
(workflows and narratives)
4
Semantic Wiki Pages
4
Semantic Wiki Pages
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
4
Semantic Wiki Pages
Ontology Example
Organisation:
University of
Southampton
Organisation:
JISC
Is funded by
JISC
Project:
FREMA
FREMA
Is involved in
Uni Soton
Southampton
JISC
frema
frema
4
Semantic Wiki Pages
Implementing the Website
4
Semantic Wiki Pages
•
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
4
Semantic Wiki Pages
Browsing the Wiki
4
Semantic Wiki Pages
Dynamic Gap Analysis
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
3
Goal and Function
Model
FREMA Ontology
2
Concept Maps
Domain System
Model
Scenarios
(workflows and narratives)
5
Use Cases and
Interaction Diagrams
4
Semantic Wiki Pages
Use Cases and
Interaction Diagrams
Scenarios
• Scenarios capture a certain
activity (function) within the
Domain
Service Implementations
Service
Interfaces
(WSDL)
• Can be captured at different
levels of formality
• Through to real interacting
services
FREMA
• From narrative descriptions
Service
Workflows
(BPEL)
Service
Service
Expressions Interactions
Use Cases
Written Scenarios
formality
5
Use Cases and
Interaction Diagrams
Service Usage Model
•
Describes a scenario
in which services
work together
•
•
Use Case Diagram
Set of Abstract
Logical Service
Expressions
Interaction Diagram
•
Service Implementations
FREMA
5
Service
Interfaces
(WSDL)
Service
Workflows
(BPEL)
Service
Expressions
Service
Interactions
Use Cases
Written Scenarios
Use Cases and
Interaction Diagrams
Use Cases and Narratives
• Formal as a Use Case
Diagram
• Informal as a Narrative
Description
Service Implementations
FREMA
5
Service
Interfaces
(WSDL)
Service
Workflows
(BPEL)
Service
Expressions
Service
Interactions
Use Cases
Written Scenarios
Use Cases and
Interaction Diagrams
Service Expression: SRC
• Logical,
abstract
description
Service Implementations
FREMA
5
Service
Interfaces
(WSDL)
Service
Workflows
(BPEL)
Service
Expressions
Service
Interactions
Use Cases
Written Scenarios
Use Cases and
Interaction Diagrams
Service Interaction: Overview
Service Implementations
FREMA
5
Service
Interfaces
(WSDL)
Service
Workflows
(BPEL)
Service
Expressions
Service
Interactions
Use Cases
Written Scenarios
Use Cases and
Interaction Diagrams
Service Interaction: Diagram
Service Implementations
FREMA
5
Service
Interfaces
(WSDL)
Service
Workflows
(BPEL)
Service
Expressions
Service
Interactions
Use Cases
Written Scenarios
Domain Modelling
Domain Context
Domain Information
Model
Stakeholders and
Role Models
1
Stakeholders
and Personas
3
Goal and Function
Model
FREMA Ontology
2
Concept Maps
Domain System
Model
Scenarios
(workflows and narratives)
5
Use Cases and
Interaction Diagrams
4
Semantic Wiki Pages
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?’
Thank you…
http://www.frema.ecs.soton.ac.uk/