1 Congifurable, Incremental and Re- structurable Contributive Learning Environments Dr Kinshuk Information Systems Department Massey University, Private.

Slides:



Advertisements
Similar presentations
FUNCTION FITTING Student’s name: Ruba Eyal Salman Supervisor:
Advertisements

The Cost of Authoring with a Knowledge Layer Judy Kay and Lichao Li School of Information Technologies The University of Sydney, Australia.
Unit Testing in the OO Context(Chapter 19-Roger P)
Bridgette Parsons Megan Tarter Eva Millan, Tomasz Loboda, Jose Luis Perez-de-la-Cruz Bayesian Networks for Student Model Engineering.
Chapter 2 Software Processes (1/2) Yonsei University 2 nd Semester, 2014 Woo-Cheol Kim.
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
1 Adaptive Learning Systems Associate Professor Kinshuk Information Systems Department Massey University, Private Bag Palmerston North, New Zealand.
Alternate Software Development Methodologies
OASIS Reference Model for Service Oriented Architecture 1.0
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Page 1 Building Reliable Component-based Systems Chapter 3 - Architecting Component-Based Systems Chapter 3 Architecting Component-Based Systems.
CS 501: Software Engineering Fall 2000 Lecture 16 System Architecture III Distributed Objects.
UML CASE Tool. ABSTRACT Domain analysis enables identifying families of applications and capturing their terminology in order to assist and guide system.
1 Software Testing and Quality Assurance Lecture 30 – Testing Systems.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Cognitive Science Overview Design Activity Cognitive Apprenticeship Theory Cognitive Flexibility Theory.
Course Instructor: Aisha Azeem
1 An introduction to design patterns Based on material produced by John Vlissides and Douglas C. Schmidt.
Domain-Specific Software Engineering Alex Adamec.
31 st October, 2012 CSE-435 Tashwin Kaur Khurana.
Enterprise Systems & Architectures. Enterprise systems are mainly composed of information systems. Business process management mainly deals with information.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.1.
Made with Protégé: An Intelligent Medical Training System Olga Medvedeva, Eugene Tseytlin, and Rebecca Crowley Center for Pathology Informatics, University.
Beyond DHTML So far we have seen and used: CGI programs (using Perl ) and SSI on server side Java Script, VB Script, CSS and DOM on client side. For some.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 4 - System modelling Dr Richard Clayton.
S/W Project Management Software Process Models. Objectives To understand  Software process and process models, including the main characteristics of.
Human Teacher in Intelligent Tutoring System: A Forgotten Entity! Kinshuk, Alexei Tretiakov, Hong Hong, Ashok Patel Dr Kinshuk Information Systems Dept,
Jaeki Song ISQS6337 JAVA Lecture 16 Other Issues in Java.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
An Introduction to Software Architecture
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
101 User Interface Patterns and its applications Tonya Groover Department of Computer Science.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Algoval: Evaluation Server Past, Present and Future Simon Lucas Computer Science Dept Essex University 25 January, 2002.
Design engineering Vilnius The goal of design engineering is to produce a model that exhibits: firmness – a program should not have bugs that inhibit.
Patterns and Reuse. Patterns Reuse of Analysis and Design.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
1 Granular Approach to Adaptivity in Problem-based Learning Environment Sally He, Kinshuk, Hong Hong Massey University Palmerston North, New Zealand Ashok.
Precedence Health Care The MAS – SE Gap: Bridging the Divide Michael Georgeff Precedence Health Care & Monash University Autonomous Agents and Multiagent.
Tutoring & Help System CSE-435 Nicolas Frantzen CSE-435 Nicolas Frantzen.
On-line Knowledge Management Search Engine Lei Zhang, Bhavani Sridharan and Kinshuk Information Systems Dept, Massey University Palmerston North, New Zealand.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
CS 501: Software Engineering Fall 1999 Lecture 12 System Architecture III Distributed Objects.
Software Prototyping Rapid software development to validate requirements.
Design and Implementation of a Rationale-Based Analysis Tool (RAT) Diploma thesis from Timo Wolf Design and Realization of a Tool for Linking Source Code.
Domain-Expert Repository Management for Adaptive Hypermedia Learning System By Norazah Yusof & Paridah Samsuri Members of SPAtH Group Faculty of Comp.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Chapter 24 객체지향 응용프로그램 테스팅 Testing Object-Oriented Applications 임현승 강원대학교 Revised from the slides by Roger S. Pressman and Bruce R. Maxim for the book.
1 Lecture 15: Chapter 19 Testing Object-Oriented Applications Slide Set to accompany Software Engineering: A Practitioner’s Approach, 7/e by Roger S. Pressman.
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Object Design More Design Patterns Object Constraint Language Object Design Specifying Interfaces Review Exam 2 CEN 4010 Class 18 – 11/03.
Elaboration: Iteration 2. Elaboration: Iteration 2 Basics Iteration 1 ends with : All the software has been tested: The idea in the UP is to do early,
Distribution and components
Architecture Components
Chapter 24 Testing Object-Oriented Applications
Software Architecture
Software Test Automation and Tools
Chapter 19 Testing Object-Oriented Applications
An Introduction to Software Architecture
CS310 Software Engineering Lecturer Dr.Doaa Sami
CS 8532: Advanced Software Engineering
Chapter 19 Testing Object-Oriented Applications
Logical Architecture & UML Package Diagrams
Presentation transcript:

1 Congifurable, Incremental and Re- structurable Contributive Learning Environments Dr Kinshuk Information Systems Department Massey University, Private Bag Palmerston North, New Zealand Tel: Ext 2090 Fax: URL:

2 Reusability Benefits are widely known However, early promises of time and cost savings hae not materialised In software reuse, only trivial pieces of code can be used in another context without much effort

3 CIRCLE Architecture Only way to increase usability and in the process automatically increase the reusability, is to allow: implementing teacher to contribute through: configuring the learning space Incrementally adding and re-structuring scope and functionality of IES components Early adoption: HyperITS

4 HyperITS No pre-defined sequence of operations Concepts linked in an interrelationship network Inconsistency results in graded feedback leading the learner gradually to the point of start Mis-conceptions and missing conceptions are identified.

5 HyperITS Emphasis on cognitive skills development Uses cognitive apprenticeship approach to provide cognitive skills: Observation Imitation Dynamic feedback by learning Interpretation of data Static feedback from testing

6 HyperITS Granular design Domain concepts are acquired in the context of their inter-relaed concepts Interfaces are brought up to give: Another perspective on the data set Fine grained interface to give details of a coarse grained presentation Fine grained basic application to revise steps at a more advanced level

7 HyperITS Process modelling Overcoming the shortcomings of overlay model Understanding learner’s mental processes Allows finding optimal and sub-optimal paths in learning process

8 HyperITS Architecture

9 Knowledge representation

10 Knowledge repres. framework

11 Domain Layer Static domain content provided by the designing teacher: Concepts, the smallest learning units Relationships among concepts Priorities associated with the relationships Custom operator definitions Constraints on backward chaining, if desired

12 Teacher Model Layer Consists of the pedagogy base reflecting various tutoring strategies and scaffolding provided by the implementing teacher Optional problem bank created by the implementing teacher to situate the concepts in a particular context The teacher can also provide additional diverse contexts

13 Contextual Layer Contains the current goals and structural information of current tasks: system’s solution to current problem; system’s problem solving approach; immediate goals. This information is dynamically updated along with the learner’s progress in problem solving.

14 Initialization functionality  Domain representation initialiser initialises the system according to the current learning goal for all types of problems.  Random problem generator randomly selects concepts to treat as independents and creates their instances by randomly generating values within specified boundaries.

15 Initialization functionality  Prediction boundary initialiser initialises the boundaries for the overlay model (how far student’s solution can go from expert solution). These boundaries are used later to evaluate a learner’s action.

16 If independent variable introduced  Contextual dependency finder identifies the dependent concepts that can be derived within in the current state of the problem space.  Dependency activator (client side) activates the instances of the contextually dependent concepts and invokes the dependency calculator at server to update their current status in the expert solution.

17 If independent variable introduced  Dependency calculator (server side) provides values for the dependent concepts based on domain layer and pedagogy base to update the expert solution. This functionality allows a learner to adopt a different route to the solution than the one currently adopted by the system.

18 Setting validation bounds for dependent variables  Prediction boundary updater updates the prediction boundaries used in comparing a learner’s solution with the expert solution. The updater fine-tunes the system’s initial prediction boundaries to match the route to solution adopted by a learner.

19 Validation of learner’s input to dependent variables  Discrepancy evaluator evaluates the validity of a learner’s attempt by matching it with the expert solution within the prediction boundaries.

20 Validation of learner’s input to dependent variables  Dynamic feedback generator provides context-based feedback to the learner. The messages are generated dynamically to improve semantics and to prevent monotony. Granular approach is used in identifying the source of error and for providing feedback.

21 Validation of learner’s input to dependent variables  Dynamic feedback generator i. Basic misconceptions, where the learner fails to derive a variable due to misconceptions about the critical concepts. In such cases, graded scaffolding is used: a.ask the learner to try again; b.suggests the relationship to be used; c.provides the calculation data; d.shows the full calculation, and allows the learner to proceed.

22 Validation of learner’s input to dependent variables  Dynamic feedback generator ii. Missing conceptions, when learner unsuccessfully tries to derive a variable that requires derivation of intermediate variables  the error arising from missing knowledge about intermediate relationships. System suggests learner to derive the intermediate concept first.

23 Validation of learner’s input to dependent variables  Dynamic feedback generator iii. If learner unsuccessfully tries to derive some complex concepts, system advises the learner to use a finer grain interface. The finer grain interface deconstructs the complex concept into components to capture the misconceptions at a fine grain level.

24 Evaluating learner’s process of deriving solution  Local optimiser identifies the possible relationships and determines the best relationship to use based on the priorities specified in the domain layer. It allows the system to identify any sub- optimal approach adopted by the learner.

25 Finally.. Adequate technologies are rapidly emerging that can be harnessed for deploying the CIRCLE Architecture. For example: Distributed Component Object Model (DCOM) for Microsoft development tools or Remote Method Invocation (RMI) for Java