Embed Size (px)
Citation preview
WP 3 - Technical design & Implementation of the
Integrated system
Wouter Jan Smeulers LogicaCMG The Hague
Roland Ettema LogicaCMG Maastricht
Louis Maessen
LogicaCMG Maastricht
Agenda
I. LogicaCMG’s vision on competence development (Wouter Jan Smeulers)
II. Work package 3 Technical design & Implementation of the Integrated system (Louis Maessen)
• Objectives • Overall approach
III. WP3 in more detail (Roland Ettema)IV. Organisation (Louis Maessen)
• Global time plan• Risks and measures• Preparation of the technical kick-off
January 2006
Wouter Jan SmeulersPrincipal Consultant LogicaCMG©
20
05
Logic
aC
MG
(e)
Learn
ing
L o g i c a C M G NL(e) L e a r n i n g C o m p e t e n c e
C e n t r e
(e) C o m p e t e n c e
D e v e l o p m e n t . . .
t h e s k y I s t
h e l i m i t ?
L O G I C A C M G ( e ) E D U C A T I O NL O G I C A C M G ( e ) E D U C A T I O N
To boldly go …To boldly go …
establish the most appropriate
technical and organizational infrastructure,
for lifelong competence development
The development of Who has the map?The development of Who has the map?a good idea … a good idea …
An infrastructure,for
lifelong competence development …
An infrastructure,for
lifelong competence development …
We needed a roadmap… in 3D We needed a roadmap… in 3D
To develop a system bordered by functionalities…To develop a system bordered by functionalities…
LEARNING CONTENTLEARNING CONTENT
LEARNING INFRASTRUCTURELEARNING INFRASTRUCTURE
LEARNING MANAGEMENTLEARNING MANAGEMENT
Prerequisite 1: Coherent subsystems for competence developmentPrerequisite 1: Coherent subsystems for competence development
To develop a system agreed upon by all perspectives…To develop a system agreed upon by all perspectives…
ORGANISATIONORGANISATION
PEDAGOGYPEDAGOGY
TECHNOLOGYTECHNOLOGY
Prerequisite 2: Involve predominant stakeholdersPrerequisite 2: Involve predominant stakeholders
To develop a system using time structures…To develop a system using time structures…
Instructional Systems Design: ADDIE
Dynamic Systems Development Method
Prerequisite 3: A structured process approach!Prerequisite 3: A structured process approach!
Integrated into a frameworkIntegrated into a framework
EvaluationEvaluation
ImplementationImplementation
DevelopmentDevelopment
Design
AnalysesAnalyses
ProcessesProcesses
PerspectivesPerspectives
(Sub)System(Sub)System
PedagogicalPedagogical OrganizationalOrganizational TechnicalTechnical
ManagementManagement
EnvironmentEnvironment
ContentContent
ProcessesProcesses
PerspectivesPerspectives
(Sub)System(Sub)System
TenCompetence (a wide HR perspective)TenCompetence (a wide HR perspective)
Competency (certificates) reuse and exchange Competency (certificates) reuse and exchange
Competency CertificationCompetency Certification
Competency AssessmentCompetency Assessment
Competency development Competency development
Formalknowledge & learning
resources
Formalknowledge & learning
resources
Informalknowledge & learning
resources
Informalknowledge & learning
resources
Individual competence development Organizational competence development
(Human Resource Development)
(Competence Management)
(Knowledge Management)
2 – Overview of resources2 – Overview of resources
3 - Business Models3 - Business Models
5 - Support on using the infrastructure5 - Support on using the infrastructure 5 - Support on using the infrastructure5 - Support on using the infrastructure
6 – (Decentralized) management of
learning networks
6 – (Decentralized) management of
learning networks
1 - pedagogy1 - pedagogy
7 - Integrate Learning & Working
7 - Integrate Learning & Working
4 - assess competencies4 - assess competencies
Agenda
• LogicaCMG’s vision on competence development (Wouter Jan Smeulers)
• Work package 3 Technical design & Implementation of the Integrated system (Louis Maessen)– Objectives – Overall approach
• WP3 in more detail (Roland Ettema)• Organisation (Louis Maessen)
– Global time plan– Risks and measures– Preparation of the technical kick-off January
2006
WP3 Objectives first 18 months
1) To develop an architecture that supports the agile integration of heterogeneous tools and applications
2) Design and implement the first version of the common services layer as integral part of the architecture
3) Select, design and implement adaptations of existing components that are currently state of the art and form the building blocks of the architecture
4) Design and implement a first version of the integrative layer tying all common services together and thereby delivering the first version of the integrated TENCompetence System
5) Set up and maintain the infrastructure for the running pilots
WP3 Technical design & Implementation of the Integrated system
Global overall approach
(technical)Architecture
model
Technical design
WP2 Requirements &Analysis of the
Integrated system
Construction of the Integrated system
WP 5,6,7,8
Technology standards & architectures
Technical validation
WP4 Pilots with & validation of the
integrated system
WP2
Agenda
• LogicaCMG’s vision on competence development (Wouter Jan Smeulers)
• Work package 3 Technical design & Implementation of the Integrated system (Louis Maessen)– Objectives – Overall approach
• WP3 in more detail (Roland Ettema)• Organisation (Louis Maessen)
– Global time plan– Risks and measures– Preparation of the technical kick-off January
2006
Integration RTD
Management
Aspect RTD
Validation
WP 1 Consortium Management
WP 5 Knowledge Resource
Sharing & Management
WP 6 Learning Activities
& Units of Learning
WP 7 Competence
Development Programmes
WP 8 Networks for Lifelong
Competence Development
WP 9 Networks for Lifelong
Competence Development
WP 10 Networks for Lifelong
Competence Development
WP 2 Requirements &
analysis of integr. systems
WP 3 Technical Design &
Implementation of
integrated systems
WP 4 Pilots with and Validation
of the integrated systems
Interfacing
Interfacing
WP 2 Requirements &
analysis of integr. systems
WP 4
Pilots with and Validation
of the integrated systems
WP 3 Technical Design & Impl.
of integrated systems
Tools
Standards& Guidelines
Development Environment
Technical TENCompetence Environment
WP
2 Services
Existin
g S
ervices
Co
mm
on
Services
Portlet Container
Web Container
Deliverables
Technical TENCompetence
Environment
Process Container
1 n + 12
Presentation Layer
Business Process Integration
Inte
grat
ive
Laye
r
Service Layer
Application Layer
Technology Layer
1. Technical Architecture
Steps:• Design the software architecture and hardware infrastructure.• Select IT standards (XML, UDDI, SOAP, …).• Select out-of-the-box software (portal, application server, …).• Set up development environment.• Implement the software architecture and hardware infrastructure.
Goal:
To develop a first cut of an architecture that supports the agile integration of heterogenous tools and applications.
Technical TENCompetence Environment
Portlet Container
Web Container
Deliverables
Technical TENCompetence
Environment
Process Container
Questionnaire
Goal:
Provide information to the architecture design and the component selection process.
Some possible items for the questionnaire:• Used programming language(s).• Available technical documentation.• Overview of external interfaces.• Can the component be used as open source.• List of used third party components.• Supported operating system(s) and hardware platform(s).• …
Architectural Constraints
Integrate Existing Common Service Components
Steps:• Inventory the requested common services.• Prioritise the services.• Search components with corresponding functionality.• Assess the implementation impact per component.• Implement components.
Goals:1. Select existing state of the art components.2. Integrate selected components in the TENCompetence
infrastructure.
Technical TENCompetence Environment
Co
mm
on
Services
Portlet Container
Web Container
Deliverables
Technical TENCompetence
Environment
Process Container
1 n + 12
Common Services
Common Services
Common Services
3. Construct Components
Steps:• Design and implement adaptations of existing
“TENComponents” that are currently state of the art and corresponding WP2
• Set up and maintain the infrastructure for the running pilots.
Goal:Deliver the first version of the integrated
TENCompetence System.
Technical TENCompetence Environment
Portlet Container
Web Container
Deliverables
Technical TENCompetence
Environment
Process Container
Common Services
Common Services
Common Services
WP
2 Services
Learn
ing
Services
Co
mm
on
Services1 n + 12
Learning Services
Learning Services
Learning Services
Agenda
• LogicaCMG’s vision on competence development (Wouter Jan Smeulers)
• Work package 3 Technical design & Implementation of the Integrated system (Louis Maessen)– Objectives – Overall approach
• WP3 in more detail (Roland Ettema)• Organisation (Louis Maessen)
– Global time plan– Risks and measures– Preparation of the technical kick-off January
2006
Global time plan
Participants WP3
• Open Universiteit (Netherlands) [5]
• Software De Base S.A. (Spain) [12]
• LogicaCMG (Netherlands) [15]• Fundacio Barcelona media
Universitat Pompeu Fabra (Spain) [6]
• Giunti Interactive Labs (Italy) [5]
• Centre for research and technology Hellas (Greece) [4]
• Universitaet Hannover (Germany) [4]
• Insead (France) [4]• University of Bolton (United
Kingdom) [15]• Universiteit van Amsterdam
(Netherlands) [1]• Stichting Surf (Netherlands) [1]
• 72 person months (4 FTE average)
Main risks at WP-level - 1• Risk:
– There is more functionality (or ambitious functionality) specified then could be developed with the available development capacity of WP3
• Measure: – Use cases (or parts of use cases) will be prioritized (WP2,
5,6,7,8)• A must, an important functionality, nice-to-have, cosmetic
– Realize as much as possible functionality, starting with the functionality with the highest priority, within the available timeframe and development capacity
– Remaining use cases (or parts of the use cases) will be realized in the next development cycle
Main risks at WP-level - 2• Risk:
– Quality level of functional requirements (output WP 2,5,6,7,8) has strong impact on the quality of technical design and the further construction of the integrated system
• Measure: – Use RUP standard for documents and tailor
the standard to the project needs– Perform quality review
• Accuracy, understandability, testability– Start drafting technical design when relevant
findings are solved
Main risks at WP-level - 3
• Risk: – Changes in requirements during setting up
the technical design or construction of the integrated system frustrates development process
• Measure:– Use change management procedure – Prioritize changes (a must, an important functionality,
nice-to-have, cosmetic) by submitter• Determine impact (technical impact, effort, time plan) by
WP3 • Project management authorization for change
Preparation technical kick-off
• Presentation / demonstration about contributed application / tools
• Share common knowledge • Availability of participants of WP3
and their skills• Preference for WP3 activities:
– Technical design and / or– Construction of the integrated system
and / or– Technical validation
Summary
• LogicaCMG’s vision on competence development (Wouter Jan Smeulers)
• Work package 3 Technical design & Implementation of the Integrated system (Louis Maessen)– Objectives – Overall approach
• WP3 in more detail (Roland Ettema)• Organisation (Louis Maessen)
– Global time plan– Risks and measures– Preparation of the technical kick-off January
2006QUESTIONS?
WP 3 - Technical design & Implementation of the
Integrated system
CONCLUSIONS
Conclusions - 1
• Use tailored version of RUP for communication between work packages
• Open source inventory of architectural components (ASAP)– Setup WIKI environment including forms
• name component, • function description, • capabilities like integration abilities and legal
issues
Conclusions - 2
• Architectural visionaries (January meeting)– First version ‘Architecture’ (delivery 1)
• Existing components• Extended initiatives
– Second version • “Berlin draw up” (delivery 2)
– Units of learning – Learning activities
• Extend with ELF
– Gap analysis (delivery 1 – delivery 2) • Involved are WP2 and WP4• Digital Cinema Pilot
Conclusion - 3
• Design a ‘ to build’: UML Component Diagram– Setup development environment – Prioritizing
• Integration level • MOSCOW
– Deliverable: reasonable to build architecture & project plan
