1 / 39

eLSE (eLearning for Software Engineering)

eLSE (eLearning for Software Engineering). S . Stojanov ECL, University of Plovdiv. Topics. CBT & eLearning Projects‘ overview Objectives of eLSE? Implementation approach eLSE development environment & Tools Conclusion. Computer Based Training. eLearning. Semantic Web.

lisastewart
Télécharger la présentation

eLSE (eLearning for Software Engineering)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. eLSE(eLearning for Software Engineering) S. Stojanov ECL, University of Plovdiv

  2. Topics • CBT & eLearning • Projects‘ overview • Objectives of eLSE? • Implementation approach • eLSE development environment & Tools • Conclusion

  3. Computer Based Training eLearning Semantic Web CBT & eLearning Just-in-time/at-work-place/ customized/on-demand process of learning Time/place/content predeterminated 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

  4. Projects‘ overview DeLC BULCHINO eLPortal eLSE TestPortal eSArchitecture CBRFramework COMMERCE

  5. 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

  6. Approach 3 S-Bahn Tool GlossarySE 2 4 5 LOs Transformation SEnew (.ppt) staticSCORM (basic version) 6 1 7 SE-Editor SEold (.ppt) SE(SCORM)Version n Mod static SCORМ R- Editor + S & N eLSE development environment 8 9

  7. 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

  8. 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

  9. 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

  10. 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

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

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

  13. 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

  14. 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

  15. 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

  16. 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

  17. Ontology Development Organization (Concept) Person (Concept) Event (Concept) TerroristEvent (Sub-concept)

  18. Classes / Logic View

  19. Classes / Properties View

  20. Editing Properties

  21. Editing Individuals

  22. Configuring Forms

  23. Classifying Individuals

  24. 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

  25. Visualization – Example 1

  26. Visualization – Example 2

  27. Visualization – Example 3

  28. Visualization – Example 4

  29. Visualization – Example 5

  30. Visualization – Example 6

  31. Input - Output Formats • Default: Text files • Available backend plugins • OWL / RDF • OWL Databases • RDF • XML / XML Schema • UML (OWL-UML bridge work in progress)

  32. Other Plugins / OWL Wizard

  33. Other Plugins / Prompt

  34. Multi-User Mode • Client-Server setup • Central database • Clients with user interface • Changes are synchronized immediately • Scalable

  35. Protégé Web Browser

  36. 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.

  37. 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, ...)

  38. 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

  39. Possible development environment? • Protégé • eLSE plugin • Sam’s S-Bahn-Tool • Keti’s multilingual dictionary

More Related