TENCompetence WP2: Common Ground Rob Koper Work Packages Kick-Off TENCompetence Project 9-13 January 2006 Heerlen, The Netherlands.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

Bernd Bruegge & Allen Dutoit Object-Oriented Software Engineering: Conquering Complex and Changing Systems 1 Software Engineering September 12, 2001 Capturing.
Presentation 6 – How to conduct training programmes on cleaner production1 Presentation 6 Presentation 6 How to conduct training programmes on cleaner.
Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 16 HCI PROCESS.
Bologna Process in terms of EU aims and objectives
1 Graduates’ Attributes : EMF, EUR-ACE and Federal Educational Standards Alexander I. Chuchalin, Chair of the RAEE Accreditation Board Graduates’ Attributes.
In Europe, When you ask the VET stakeholders : What does Quality Assurance mean for VET system? You can get the following answer: Quality is not an absolute.
WP 3 - Technical design & Implementation of the Integrated system Wouter Jan Smeulers LogicaCMG The Hague Roland Ettema LogicaCMG Maastricht Louis Maessen.
Object-Oriented Analysis and Design
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Personal Competence Management in Learning Networks Prof. dr. Rob Koper Educational Technology Expertise Centre Open University of the Netherlands ICDE-SCOP,
WP5 – Knowledge Resource Sharing and Management Kick-off Meeting – Valkenburg 8-9 December 2005 Dr. Giancarlo Bo Giunti Interactive Labs S.r.l.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
SWE Introduction to Software Engineering
1 COST G9 - Work group 2 meeting Székesfehérvár, Hu Modeling real property transactions Radoš Šumrada Faculty of Civil and Geodetic.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
Requirements Elicitation Chapter 4. Establishing Requirements Two questions –What is the purpose of the system –What is inside and what is outside the.
Software Requirements
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 An Introduction to Software Engineering.
1/19. 2/19 WP6 Presentation Pythagoras Karampiperis, WP6 Leader Demetrios Sampson, CERTH CB Representative Antonis Kokkonos, CERTH WP6 Team Member Advanced.
Iterative development and The Unified process
WP 8: Networks for Lifelong Competence Development Alicia Cheak INSEAD CALT (Centre for Advanced Learning Technologies) TEN Competence Kickoff Meeting.
EVALUATION AND QUALITY ASSURANCE STRATEGY PRESENTED BY DR SHYAM PATIAR.
Slide 1 Requirements Workflow. Slide 2 The Phases/Workflows of the Unified Process Figure 3.1 l Phase is Business context of a step Workflow is Technical.
WAGGGS Policy & Guidelines: Adult Training, Learning and Development
Developing the Personal Competence Manager Evaluation Work: ‘EPIQ Business Demonstrator’ Elena Shoikova, Vladislav Denishev, Radoslav Milanov Technical.
Introduction to Information System Development.
S/W Project Management
Validation Validation is the process of identifying, assessing,
26 TH ACADEMIC COUNCIL ST APRIL 2015 Breakout session Group C “EXPERIENTIAL LEARNING”
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
1 Phases in Software Development Lecture Software Development Lifecycle Let us review the main steps –Problem Definition –Feasibility Study –Analysis.
ITEC224 Database Programming
Team Skill 6: Building the Right System From Use Cases to Implementation (25)
TENCompetence: The European Network for Competence Development Chris Kew CETIS April
Ways for Improvement of Validity of Qualifications PHARE TVET RO2006/ Training and Advice for Further Development of the TVET.
Feasibility Study.
CEN rd Lecture CEN 4021 Software Engineering II Instructor: Masoud Sadjadi Phases of Software.
A COMPETENCY APPROACH TO HUMAN RESOURCE MANAGEMENT
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Testing Workflow In the Unified Process and Agile/Scrum processes.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 4, Requirements Elicitation.
Chapter 7 Applying UML and Patterns Craig Larman
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Methods and Models Choice of methods for Development of IT related products and systems SVINGSVING Conference held in Gothenburg, Sweden, October 2000.
Lecture 7: Requirements Engineering
An Introduction to Software Engineering. Communication Systems.
SmartNets Results Overview SmartNets SmartNets Methods.
Integrating competence development at the individual-, group- and organizational level Luxembourg, February 6, 2006.
Aim (and name)... We will build The European Network for Lifelong Competence Development i.e. Provide a technical and organisational Infrastructure that.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
Rational Unified Process (RUP) Process Meta-model Inception Phase These notes adopted and slightly modified from “RUP Made Easy”, provided by the IBM Academic.
WP2: Domain Model + WP3 TENCC Rob Koper & Hubert Vogten TENCompetence Project Meeting 3-4 July 2006 Kerkrade, The Netherlands.
Quality Assurance Netherlands Universities Dublin descriptors.
Ivar Jacobson, Grady Booch, and James Rumbaugh The Unified Software Development Process Addison Wesley, : James Rumbaugh's OOMD 1992: Ivar Jacobson's.
Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution Structured programming Product SW.
Requirements Analysis
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
UML - Development Process 1 Software Development Process Using UML.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
Testing throughout Lifecycle Ljudmilla Karu. Verification and validation (V&V) Verification is defined as the process of evaluating a system or component.
Bernd Bruegge and Allen Dutoit Requirements Process The requirements process consists of two activities: Requirements Elicitation: Definition of the system.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Introduction to Software Engineering
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Presentation transcript:

TENCompetence WP2: Common Ground Rob Koper Work Packages Kick-Off TENCompetence Project 9-13 January 2006 Heerlen, The Netherlands

Objective of this week Get to know each other Detailed (as possible) planning of activities at all levels: - Project at large - Each partner - Each person Start to do the work... (Common Ground)

Common Ground Joint understanding of: Project Plan Definition of concepts and relations between concepts (Domain Model, i.e. theories) Scenario's and Use Cases Output (technologies, publications) Methodology (Unified Process) Joint understanding of the Technology Requirements

Method Everyone involved in WP2 Identification of Misconceptions, Clarifications, etc. Explanation, Discussion of concepts and record/register them (tencompetence.org) Joint work on Domain Model, Use Cases and non- functional requirements Joint planning of the work Rules for Participants: - Ask experienced participants when in doubt - Study the resources available at tencompetence.org

Some Misconceptions & Clarifications Needed

First of all... The project plan is leading for all activities. This means: That we will perform the tasks as stated in the work package descriptions for the first 18 month to attain the objectives as stated in the plan. The requirements analysis of WP2 has to fit within the overall requirements as already formulated into the project plan. >> So it is NOT an open analysis but restricted by the project plan! The same is true for the technology and licence constraints as defined in the project plan.

All tasks as mentioned in the 18 month work plan should be finished in the first 18 month No: most tasks described in each WP have to be completed in period 1 but there are also tasks that will continue

As stated already in general: requirements must fit in the requirements mentioned in the project plan Furthermore: we do not build the infrastructure solely on the requirements that are specified by the users of the WP4 Pilots (eg Digital Cinema) The Requirements Analysis

TENC-Infrastructure - technical (= the system) - organisational (= methods manuals, workflow, paid services, etc.) Organised Pilots in Project Plan: 1. Digital Cinema (first 18 month) 2. Health Care (after 18 month) 3. Nile Region (after 18 month) 4. Antwerp Lifelong Learning City (after 18 month) Organised Pilots in Project Plan: 1. Digital Cinema (first 18 month) 2. Health Care (after 18 month) 3. Nile Region (after 18 month) 4. Antwerp Lifelong Learning City (after 18 month) 7 Core Requirements (solve problems:) 1. Implement New Pedagogical & Organisational Models for Lifelong Compt Development 2. Support the Discovery of Best Solutions 3. Stimulate Pro-active Sharing of resources 4. Support Competence Assessment 5. Provide Effective & Efficient User Support 6. Provide Decentralized, Self-org. Management 7. Integrate Isolated Models & Tools from four 'worlds': knowledge sharing (WP5); learning activities (WP6); programmes (WP7); learning networks (WP8) 7 Core Requirements (solve problems:) 1. Implement New Pedagogical & Organisational Models for Lifelong Compt Development 2. Support the Discovery of Best Solutions 3. Stimulate Pro-active Sharing of resources 4. Support Competence Assessment 5. Provide Effective & Efficient User Support 6. Provide Decentralized, Self-org. Management 7. Integrate Isolated Models & Tools from four 'worlds': knowledge sharing (WP5); learning activities (WP6); programmes (WP7); learning networks (WP8) Non-functional Requirements: 1. Open Source Only (OSI) 2. Use of Open Standards 3. Service Oriented Architecture 4. Extensible 5. OSS services can be replaced by commercial services Non-functional Requirements: 1. Open Source Only (OSI) 2. Use of Open Standards 3. Service Oriented Architecture 4. Extensible 5. OSS services can be replaced by commercial services Additional Pilots: 1. Small pilots by Partners 2. Pilots by Ass. Partners 3. Pilots by others At any time! Additional Pilots: 1. Small pilots by Partners 2. Pilots by Ass. Partners 3. Pilots by others At any time! Use Cases & Domain Models

The only pilot we perform in month is in the area of Digital Cinema? We will perform the following pilots: 1. Small pilots by Partners 2. Pilots by Ass. Partners 3. Pilots by others General principle is that we should try to gain as much experience from different pilots as possible! However: the system must set the right expectations (and fulfill as much of the 7 requirements as possible)

WP5-8 deliver requirements for the infrastructure Look at the Work Package Descriptions in the project plan: The WPs 5-8 do NOT have tasks to define their own requirements Defining the requirements for WP5-8 is the task of WP2 However: this does not mean that you do not have to perform this task, only in a technical sense: - we want to combine all requirements into one consistent document - we want to discuss and prioritize them in one place See figure next slide -->

Relations between WPs in the three cycles

About WP5-8 ● Each of the four WPs 5-8 is responsible for experiments to validate their own tools/methods/models. This includes the recruitment of their test persons/organizations but may also include (in particular in period 1) the installation of an environment to enable the experiments. In other words these experiments take place outside the overall project validation as carried out in WP4. ● Furthermore, each of the four WPs is responsible for the development of their part of the software in line with the requirements formulated by WP3 ● The output of WP5-8 is one of two things: a. scientific publications and b. technologies that comply to the technical requirement that can be integrated as services within the infra

Moodle (this website) is used as the first infrastructure of TENCompetence No, Moodle is only used to setup the project website ( for internal and external asynchronous communications within the projectwww.tencompetence.org Illustration: we don't need to use the Moodle Wiki when we want to setup a Wiki for the competence monitor of WP8 However: the selection of adequate tools for the integrated system will be done by WP3, based on the requirements formulated in the project plan + WP2. WP8 can select and setup a temporary Wiki for experimentation that is consistent with the technical standards and requirements that have to be defined by WP3 (some of them are already defined in the Proj.Plan)

Communication in the project We use: * Moodle ( as a project website for internal and external communication. * Dspace for external publications of all project outputs (publications + technology sources for archive purposes) * Surf Groepen for synchronous communication This afternoon further introduction!

Use of the (Rational) Unified Process The Unified Process (UP) is used as follows: As a way to structure the project plan (the first 18 month we will do the UP phases Inception and elaboration). Some of the tasks to be performed are derived from the UP: e.g. Domain Model, Use Case Model). We can use it as a process in the development of the integrated system. Some clarifications (next slides)

Clarifications UP We don't use the UP in a strict sense as it can be seen in the different handbooks of UP (or RUP). The tasks that we should perform are already planned in the project plan. The major problems with UP is that: * it is often used too strict: the procedure dominates instead of the product to be developed. * it is not developed for R&D projects but for engineering projects. R&D projects are in principle theory driven: we develop new technologies that solve problems that users are not aware of at this moment. We can still use the UP, but with some adaptations. * it can be used at different levels of abstraction: for theory modelling, business modelling and software modelling.

As a consequence we cannot use most of the standard UP tools that are available in e.g. the Rational Unified Process (RUP), because they are too rigid and engineering driven. What we will need is a multiplatform UML modelling tool (preferably open source) that we can use jointly to change UML models. Possible solution: Magic Draw (see UML tools discussion in WP3 wiki)

Competences vs Competencies See discussion in WP7 forum See Domain Model Competence & slides kick-off (next slides)

Key role for 'competences' The concept of competence can bridge the world of education, training, knowledge management, human resource management & informal learning Many definitions, problem for system development - Competence: Effective performance in a domain at different levels of proficiency - Competency: Undefined (I prefer to avoid the term and use more specific terms when needed, eg, a skill) We will use a stipulative definition and model in TENCompetence to avoid endless discussions about the concept (see next side)

Domain Model Competences

Definition of TENCompetence Competences are bound an occupation, a profession, a market (for an organisation) or any other life or work situation (a defined ecological niche). In words: A competence is defined as the ability of an actor to act effectively and efficiently upon the events in an ecological niche (an occupation, a hobby, a market, a sport, etc.). (short: effective performance in a domain) These competences are divided in 5 primary categories: Cognitive, Functional, Personal, Ethical and Trans-/Meta Competences (they are not orthogonal/can overlap!) Example: “English Writing” is a skill; Being an effective News Reporter is a competence.

Example: The Baker Occupation: Baker Key Ecological Niches: - The bakery shop - The bakery - The office

In The Shop Some key events (tasks, problems, objectives, triggers) in the bakery shop: “Client orders bread” “Client asks which bread contains milk” “Make an order list for the bakery for the next weekend” “Ask feedback from clients; develop ideas for new products” “Take care of tax and environmental regulations” “...”

Competences in the Bakery Shop Remember: competences are arbitrary descriptors and so the 5 categories are also arbitrary groupings: The competent baker has the following competences: Cognitive Competences: - Knowledge of the different types of products - Knowledge of the maintenance requirements of different machines in the shop - Knowledge of hygiene regulations and rules Functional Competences: - Handle orders of clients - Handle payment - Cut bread (and other small product customizations)

Personal Competences: - Friendly for costumers, stress resistant, collegiality - Task centeredness Ethical Competences: - duty to keep up to date in the profession - acknowledging boundaries of own competences - adherence to law & professional rules - sensibility to needs and values of others Trans-/Metacompetences: - Communication - Reflective - Self-development - Flexible & Creative solutions for small problems See also: s.html s.html

Exercise 1 Groups of 2 or 3 persons (different partners), minutes: Select an occupation/hobby you know well in the group. Define some of the sub-ecological niches in the occupation Define some key events in one of the sub-ecological niches Define the competences of an actor to deal with these events in one of the sub-ecological niches effectively and efficiently. Divide the competences in: a. Cognitive competences (knowledge base of occupation) b. Functional competences (handle key events/tasks) c. Personal competences (invoke changes, creativity, etc.) d. Ethical competences (behave according to rules, laws) e. Trans-/metacompetences (competences that are not unique for the occupation, like communication skills) Upload results toforum of this meeting

Exercise 2 (same groups, min.) Define the different types of roles of the members of your learning network (e.g. learner, expert, mentor,...) What user functions do we support in the learning network for the different members, divided in the 4 key services + the common services: Formal and Informal key services: - Knowledge Sharing & Content Management - Learning Activities & Units of Learning - Competence Development Programmes - Learning Network Aspects: social exchange mechanisms, comptence monitor, social aspects in the network, self- organisation aspects in the network

Exercise 3: Same Groups minutes Check whether all the 7 requirements for the TENCompetence infrastructure are met in the previous functions Work out some core scenarios and abstract use cases from these scenario's (for two member roles) Work out some of the non-functional requirements: (open standards are needed; usability requirements (e.g. user interface, accessibility); performance; security; openness and sustainability of the infrastructure for other groups) (When time left:) Work out assessment criteria for the evaluation of the effectiveness, efficiency, attractiveness and accessibility of the infrastructure when tested in the pilots

Learning Networks for Lifelong Learning Each network is defined on a life/workdomain Each network is defines one or more proficiency levels Each network has a competence framework defined for the different proficiency levels (subniche-event-activity tuple) Each network has formal and informal programmes defined to attain the different competences Each programme has an ordered set of one or more learning activities and/or units of learning (a unit of learning contains an ordered set of learning activities) Each learning activity or unit of learning contains learning resources

Learning Network for Bakers Shared formal and Informal learning activities or units of learning Example “Competence Development Programme” (programme to develop competence X) selection in the learning path sequence in the learning path

Layers in the Learning Network Key Concepts: - Learning Network - Competence - Lifelong Learning - Programme - Learning Activity - Unit of Learning - Comp. Assessment - Learning Resource - Self-organisation - Social Exchange - Discovery - Positioning - Navigation - Learning Path Key Concepts: - Learning Network - Competence - Lifelong Learning - Programme - Learning Activity - Unit of Learning - Comp. Assessment - Learning Resource - Self-organisation - Social Exchange - Discovery - Positioning - Navigation - Learning Path