portal provider, domain manager, and tutor. ... esses in the qualification application domain, and .... course booking manager, which is one of the task-specific.
An Open Framework for Integrated Qualification Management Portals Michael Fuchs, Claudio Muscogiuri, Claudia Niederée, Matthias Hemmje FhG – IPSI D-64293 Darmstadt, Germany {fuchs,musco,niederee,hemmje}@ipsi.fhg.de
Abstract Systematic and individual qualification improvement in a professional context is a challenging task, which is based on a complex knowledge supply chain. Human as well as virtual actors contribute to this supply chain and have to be supported by adequate system services. The authors believe that a qualification management portal that integrates support for all qualification-related activities like course production, content provision, teaching, and learning, into an open system enables the flexibility, responsiveness, and community-orientation that is necessary for modern qualification support. The coupling of the involved processes and roles enables synergies and innovative communication opportunities. A flexible, extensible, and standard-compliant framework for such integrated qualification management portals has been developed in the eQualification project. By integrating user-friendly and task-oriented application authoring tools for qualification portal design and evolution into the Web application itself, users are empowered to act as application co-designers.
1. Introduction The information society imposes challenging requirements towards learning behavior but also provides exciting new learning opportunities enabled by using computer- and Web-based technologies for teaching and learning. Learning is no longer linked to special times, places or phases in the lifetime [1]. Learning becomes a permanent qualification process where learners acquire new skills and knowledge according to their preferences and the needs of their personal (working) environments. Successful qualification management (QM) depends on the entire knowledge supply chain including - provision and management of focused, high-quality training material, - qualification goal planning, - skill-aware selection of learning content, and - effective step-by-step learning support. Thus, QM as well as its system support is a challenging task that involves several actors in different roles. Furthermore, QM is complicated by the accelerated innovation cycles in many application domains. For this purpose mediation between qualification needs and goals
on the one side and the available learning content on the other side is crucial. In the eQualification project four complementing mediator roles supporting the qualification process have been identified: qualification consultant, portal provider, domain manager, and tutor. An integrated system approach as it is propagated in the eQualification project enables integration synergies like inter-role communication and intelligent support of mediator roles. The customizable QM framework developed in the eQualification project integrates flexible system support for all phases of the QM process and exploits the resulting synergies for the realization of an improved, customized QM. Flexibility is achieved by combining three types of components: A) Modular, task-specific packages for the support of the different tasks and roles in the QM process like shared workspaces for tutors and learners, e-learning communication and cooperation support, semiautomatic qualification consulting, SCORM1 compliant user tracking [2], workflow support for cooperative WBT2 authoring, etc., B) a set of task-specific authoring tools, for the set up and management of typical business objects and processes in the qualification application domain, and C) a set of generic Web application authoring tools for system set up, customization and evolution. The authoring tools empower special users like the portal provider to take an active part in system customization and evolution as well as in the support of new roles. We believe, that a wide range of evolutionary changes can be supported in a (QM) Web application itself. For this purpose meta-design [3] is applied, i.e., Web applications provide integrated support for participating in their own design process. To achieve this goal, Web application authoring support is necessary, that has to be at the same time powerful and user-friendly; this kind of support empowers special users of the Web application, the power users [4], not only to use the application but also to adapt it to changing requirements. In our approach the combination of task-specific and generic Web
1
SCORM (= Sharable Content Object Reference Model) is a standard for the structuring, description, and handling of learning objects. 2 WBT = Web Based Training
- Tutors mediate between a specific WBT course and an associated group of learners (virtual classroom). They support learners in the knowledge acquisition process. The roles can be further refined. The WBT author for example is just one of a group of different author types involved in the WBT production process (see Figure 1).
application authoring tools aims at providing such metadesign support. The rest of this paper is structured as follows: The key roles involved in the QM process and the synergies achieved by integrating support for all parts of the QM knowledge supply chain into one system are discussed in section 2. Section 3 focuses on our approach to a flexible framework for integrated QM portal implementation and introduces the concepts underlying the authoring tools. The paper concludes with a discussion of related work and plans for future research in sections 4 and 5.
2.2 Integration Synergies Various task-specific system services are necessary to support the variety of roles in the QM process. Separate role-specific tools can be used for this purpose, like authoring tools for the production of the WBTs, a virtual classroom tool for the learning process, etc. Instead of providing separate tools, the eQualification project propagates an integrated, but extensible QM portal, that incorporates system support for the different roles fostering the following integration synergies: - The coexistence of all roles in one context introduces new opportunities for inter-role communication. As an example, WBT quality and focus can be improved by inter-role communication between learners and WBT authors enabling different forms of feedback. - On the semantic level the sharing of a QM core model and a common knowledge infrastructure, especially the central knowledge domain network, contributes to a common domain view for all involved partners. This joint understanding has positive effects on learning, qualification planning, consistent course production, and (inter-role) communication. Furthermore, it fosters the provision of consistent intelligent assistance. - The shared use of a service infrastructure like, e.g., communication components, lowers the boundaries between roles. This facilitates a switch between roles and enables new forms of learning and course creation [5], e.g., by incorporating learners into the course production process [6]. - If all engaged WBT authors rely on the authoring support provided by the integrated system this contributes to the homogeneity and consistency of the course material. This effect is intensified by the use of (uniform) templates in WBT production. The QM process, the involved roles, and the underlying knowledge supply chain vary considerably in different QM contexts like corporate and public universities, schools, etc. So flexibility and extensible multi-role support are important design issues for a QM framework.
Role
System User
Portal Developer Administrator
Course Manager
Domain Manager
G uest
Mediator
T utor
Learner
Portal Provider
Q ualification Consultant
W BT Author
Editor
Topic Autho r
Designer
Figure 1: Roles in the QM process
2. Roles in the Qualification Management Process Human and non-human actors in various roles are involved in the QM process. The two basic user roles learner and WBT author, that form the two end points of the knowledge supply chain, are supplemented by additional roles acting as mediators in the process.
2.1 Mediator Roles In addition to the QM portal provider, the domain manager, and the tutor, the eQualification framework introduces the qualification consultant as an important mediator role in the QM process (see Figure 1). All these roles contribute to the mediation between the qualification needs of learners and the available WBT contents: - QM portal providers act as mediators between the WBTs and the learner community as potential clients. They make the WBTs available, control access and offer community services. - QM domain managers support the portal providers in their mediation task by managing the knowledge domains and organizing the available WBTs, learner skills and qualification goals into these domains. - Qualification consultants support a specific learner in course selection and qualification planning mediating between the available content and the qualification goals and preconditions of the learner. Consulting roles can be performed by humans with system support or fully automatic based on coded rules.
3. An Open Framework for Integrated Qualification Management Portals An open framework for integrated QM portals has been developed in the eQualification project3 based on an extensible component architecture that can be easily 3
Further project information can be found at http://ipsi.fraunhofer.de/delite/Projects/EQualification
2
ally construct their domain by defining domain objects, creating and evolving multiple representation for them, and establishing complex relationships between objects through their representation. Within the context of the eQualification framework this domain construction process is performed on a particular domain that is a complex syntactic and semantic coalescence of objects and relationships between them.
customized to meet the requirements of specific QM portal providers. Flexibility is achieved by supporting three types of components: A) Modular, task-specific packages for the support of the different tasks and roles in the QM process; B) Task-specific authoring tools, for the setup and management of typical business objects and processes in the application domain; C) Generic Web application authoring tools for system set up, customization and evolution. The authoring tools empower special users to take an active part in QM system customization and evolution.
web publishing model FORM MANAGER(Composer)
3.1 User Empowerment
Publishing Tools
Control-Data mapping
Online user data object
control object
constraint data object definition action object definition object definition
Task specific Tools COURSE BOOKING MANAGER
Figure 3: Authoring tool environment The development and evolution of an integrated QM solution requires a coupling of entities from at least two different domains: - the domain of Web application development; - the application domain, which includes QM business objects, relationships and business processes. A systematic approach to their flexible coupling starts with the modeling of the domains. In a second step, a model that systematically specifies the process of mapping between objects of the Web application user interface to business objects or business process subtasks of the QM application domain has to be enabled. The validity of such an approach is confirmed by analyzing UI design best practice [8], which follows the model-based UI development paradigm [9]. According to software engineering best practice, design modeling elements can be stereotyped in three basic kinds of objects [10]. Boundary objects model the interaction between actors and the system. Control objects handle the main tasks and control flows representing the dynamics of a system. Entity objects model the information stored by the system and its associated behavior. Specializing this approach for our conceptual framework, the authoring environment allows power users to (implicitly) define user interface objects, which are a special type of boundary objects, control objects representing specific client and server logic and data objects for the information stored by the system. A key activity in the authoring tools is the definition of mappings between different types of objects (see Figure 2). Figure 3 illustrates the authoring tools conceptual framework. In the framework task-specific authoring tools (task-specific tools) are used for the set up and management of task-specific objects and mappings in the Central Model Repository (CMR) and generic Web application authoring tools (publishing tools) are used for the definition and set up of components for the Web publishing
It is the aim of our approach to provide a framework for adequate task-specific design support which is required for the new kind of co-designers and developers in system customization and evolution. An extended analysis of the designers’ activities and their tools in [7] confirms that design communities graduControl-Control mappi ng
presentation control mapping object definition object definition object definition
FIELD MANAGER MENU MANAGER
3.2 The Authoring Tools Conceptual Framework
user interface object
COURSE CONTENT MANAGER
CONTROL MANAGER
We believe, that a wide range of evolutionary changes can be supported in the Web-based QM system itself by providing adaptation support mechanisms. For this purpose, meta-design [3] for Web applications is required. To achieve this goal, our framework provides powerful Web application authoring support for power users [4], empowering them to adapt the system to changing requirements. For real user empowerment we are interested in system modification that goes beyond user interface customization. Users should be enabled to manipulate system functionalities (in an operational system) to the underlying QM business process. Such modifications are normally reserved to skilled software developers. Since the power users are members of the application domain, we may not assume programming skills. The use of task specific design support [4] instead of general programming languages provides a user-friendly working environment for the development task. It has to be noted here, that we do not expect power users to develop an entire QM solution from scratch on their own. The focus is on small incremental changes and adaptations in an operational system.
UI-Control mapping
Central Model Repository
control object user interface object
Figure 2: Authoring tool objects
3
specific UI logic stored in the CMR The resulting object and mapping definitions are stored in the CMR. Once a course catalogue has been defined using the booking manager as described, a power user probably wants to offer an on-line booking service for such a catalogue; therefore he/she wants presumably to create a Web page like the one shown in Figure 5. In this case the power user will employ the publishing tools for setting up the catalogue information to be published as a list, where each entry in this list is associated with a checkbox implementing the booking logic; in doing this a mapping object is created (see Figure 6). Other objects will be implicitly referenced or created, like a generic_submit object and UI_table_list templates. All the information stored in the CMR is composed for defining the Web page model (part of the Web publishing model, together with the definition of other required components, such as navigation/browsing components). Figure 7 shows how the Web publishing model is applied for implementing the run time behavior. The server side pre-compiler component reads the Web publishing model, compiles the required components and produces a UI description written in an intermediate description language. In the eQualification framework this is an XForms definition compliant language [12], which is user agent independent. In the UI description all the mapping object definitions are resolved to binding
for $course in (/eqf/courses/course[domain_id=1]) return (for $auhor in (/eqf/authors/author[id=$course/author_id]) return (for $domain in (/eqf/domains/domain/id=$course/domain_id) return ($course/id,$course/title,$course/price,$author/name,$domain/name)))
Figure 4: Course booking control object definition
model which is the complete definition of the Web application implementing the integrated QM portal at run time. For maximum client side compatibility a form based approach has been chosen for the framework. Following the model-view-controller approach for flexible user interface design [11], form-based user interfaces are split into form layout specification (view), form dialog control (control), and the underlying form data schema (model) as it is proposed in [12].
Figure 5: A course booking In using the task-specific tools the power users manage domain tasks to be applied on specific domain entities by implicitly creating control, data and mapping object definitions that are stored in the CMR. For instance, the course booking manager, which is one of the task-specific tools in the QM context, enables the portal provider to define properties for the course booking service like prices as well as special constraints or business logic to be applied. A resulting object definition is shown in Figure 4 including the definition for a control object named course_catalogue_booking, which implements the definition for a specific online course catalogue. The publishing tools enable power users to compose the Web publishing model (see Figure 3) by defining, managing, and using - control object templates (e.g. homogenous collection, generic_submit) stored in the CMR, - mappings between object definitions (i.e. control, UI, constraints, action objects) defined using the taskspecific tools, - UI object templates (e.g. UI_checkbox_list, UI_table_list) stored in the CMR, - constraint and action objects definition that complete course_catalogue_booking control object definition
generic_selection_list control object definition
Instance Data
Instance Data Instance Data Submit
Submit User agent specific UI instance
User agent specific UI instance
Client Specific XForms Processor
Submit User agent specific UI instance
XHTML Processor
WAP Processor
d Data Translater/Processor
Pre-Compiler
web puplishing model
XForm compliant UI description
Application Data
Figure 7: Framework run time mechanisms between UI components and application data. The agent-specific processor gets the resulting UI description and generates the user interface instance specific for the user agent, which sent the request.
UI_checkbox_list object
Course Catalogue for Domain IT
