eLSE(eLearning for Software Engineering)
S. StojanovECL, University of Plovdiv
Topics
CBT & eLearning Projects‘ overview Objectives of eLSE? Implementation approach eLSE development environment & Tools Conclusion
Computer Based Training
eLearning
Semantic Web
Time/place/content predeterminated learning
Just-in-time/at-work-place/ customized/on-demand process of learning
Ontology-based annotation of learning materials, common-shared-meaning, machine-processable metadata
“Through the Internet, education will become learner- and goal-oriented rather than faculty-centered”
Lesser, Klein, MIT
CBT & eLearning
Projects‘ overview
eLSE
COMMERCE
eLPortal
CBRFrameworkeSArchitecture
BULCHINO TestPortal
DeLC
Main objectives
System infrastructure for eLearning and distance learning in software engineering
Methodology for creation of e-content in SE – best practices (CM University – Development Guide …)
SCORM-compliant e-content Integration of eLSE in DeLC infrastructure Multilingual
LOs Transformation
SE-Editor
S-Bahn Tool
Glossary SE
R-Editor
SEnew (.ppt)
SEold
(.ppt)
static SCORM(basic version)
SE (SCORM) Version n
Mod static SCORМ
+ S & N
1
2
4 5
6
3
7
8
9
Approach
eLSE development environment
Implementation steps
Restructuring – the basic learning elements of the lecture course are extracted and restructured in suitable learning objects
Generation of local objects – local copies of learning objects can be generated through the S-Bahn-Tool
Usage of Glossary – for generation of local copies we can use a dictionary
1
2
3
Implementation steps
LOs Transformation (Tools) – learning objects are transformed in SCORM format (static)
Generation of basic (static) SCORM version – the basic SCORM version is build from the existing learning objects (creating of manifest files)
SE-Editor – the static SCORM version can be edited by help of SE-Editor
4
5
6
Implementation steps
Modification of static SCORM – the static SCORM version can be further updated (additional learning objects can be integrated, existing objects can be deleted, …)
Creation of dynamic SCORM version – to the static SCORM version sequencing and navigation information can be added
Generation of the next SCORM versions – next versions can be generated from the first e-content version
7
8
9
First version
Supports the eLearning-orieted CBT in SE Start point – existing JCSE content (.ppt) Manual restructuring of the existing JCSE content
(.ppt) S & N - manual generation & inclusion Partly eLSE development environment Tools:
Transformation Tools Reload-Editor (Reload – UK company in the field of
eLearning) S-Bahn-Tool
Second version
Supports eLearning in SE Start point – LOs & SCORM-compliant content 3-layered architecture:
eLSE editors Transformators SCORM generators
Full eLSE development environment: Domain (SE) – oriented intelligent editors Protege-based (plug-ins) Reload-based generators Education Patterns & Frameworks
Ontologies
Formal models of a domain Shared (internet, between groups) Common modeling constructs
Classes Properties Logic / Meaning Individuals
Can be used to define domain-specific modeling languages
Web Ontology Language (OWL)
W3C Standard Based on RDF(S) Ontologies are shared on the web Explicit support for linking ontologies Built-in reasoning support based on Description
Logics Rule-based extension SWRL
Protégé
Open-Source ontology editing tool Developed at Stanford Medical Informatics with
help from community Evolves since the 1980s In routine use around the world Traditional domain: Biomedicine General-purpose tool and platform
Protégé and OWL
Core System (since 1990s)
• Generic metamodel (OKBC)• Configurable• Open platform with “Plugins”
OWL Plugin (since 2003)
• OWL Full metamodel• Optimized user interface• Built-in reasoning access • Several thousand users
OWL Plugin Background
OWL Plugin started in 2003 Major sources of Funding: NLM, NCI Goals (Achievements):
Comprehensive support for OWL DL & Full Editing and visualizing OWL/RDF ontologies Integration of DL reasoners (classification) Open platform for Semantic Web community
Ontology Development
Organization (Concept)
Person(Concept)
Event (Concept)
TerroristEvent(Sub-concept)
Classes / Logic View
Classes / Properties View
Editing Properties
Editing Individuals
Configuring Forms
Classifying Individuals
An Open-Source Platform
Available for free Transparent behavior / semantics Flexible “Plugin” mechanism
New user interface components New file formats New reasoners ... (your application here)
80+ plugins publicly available
Visualization – Example 1
Visualization – Example 2
Visualization – Example 3
Visualization – Example 4
Visualization – Example 5
Visualization – Example 6
Input - Output Formats
Default: Text files Available backend plugins
OWL / RDF OWL Databases RDF XML / XML Schema UML (OWL-UML bridge work in progress)
Other Plugins / OWL Wizard
Other Plugins / Prompt
Multi-User Mode
Client-Server setup Central database Clients with user interface
Changes are synchronized immediately Scalable
Protégé Web Browser
Protégé - summary
An open-source ontology tool platform De-facto standard OWL editor Comprehensive OWL / RDF support Configurable visual editors Built-in reasoning capabilities Many plugins for visualization etc.
Conclusion - tasks for the next year:
Partly implementation of the first version – only selected topics: Restructuring of selected topics – building LOs Topics as net structures of LOs Confirmation of the LOs – eventually the same
approach as preparation of topics (reviews) Selection of SCORM transformation tool - (LNR-
Toolkit, Theses, ...)
Conclusion - tasks for the next year:
Concept for the second version: SE ontologies – LOs as concepts:
Upper ontology Mid-level ontology Domain-ontology
DB structure – keeping of the LOs Interfaces between ontologies and DB Using and adapting of Protégé – approproate plug-ins
Possible development environment?
Protégé eLSE plugin Sam’s S-Bahn-Tool Keti’s multilingual dictionary