Presentation of D25 The knowledgebased content management application design methodology ICONS Metho

1
Presentation of D25The knowledge-based content
management application design methodology(ICONS
Methodology)

• Michal Smialek, Sebastian Lisek
• Infovide S.A.

2
Current state-of-the-art andour motivation

• Most of the current methodologies define only the
  environment for building a KM system do not
  describe how to build it all operate on a high
  level of abstraction
• Most of the methodologies are descriptive they
  do not supply us with detailed instructions for
  activities
• We want our methodology to provide a prescription
  on how to reach a goal which is building a system
  based on the ICONS framework
• We want to use a comprehensive and uniform
  notation and method of description

3
Process areas in the ICONS methodology
Knowledge Management Methodologies
ICONS Methodology
4
Presentation outline

• Notation
• Knowledge Life Cycle Methodology
• lifecycle model and a short example of activities
• Knowledge Management Methodology
• lifecycle model and a short example of activities
• Software Life Cycle Methodology
• lifecycle model, artefacts, artefact description
  example, activities example
• Final reamarks

5
Process notation

• Notation based on UML
• Class diagrams contain classes stereotyped as
  ltltrolegtgt and ltltartefactgtgt
• Activity diagrams graphical representation of
  the workflow

6
Knowledge Life Cycle Methodology
7
Knowledge Life Cycle Model

• Lifecycle based on Knowledge Components
• Incremental updating of the Knowledge Repository

8
Example Activities in Knowledge Production

• Knowledge Producer creates Knowledge Components
  based on the Tacit Knowledge and on Information
  Packages prepared by the Information Gatherer

9
Knowledge Management Methodology
10
Knowledge Management Lifecycle Model

• All the changes to the KLC Process are made based
  on KLCP Change Sets
• The KLCP get improved incrementally in several
  iterations

11
Example Activities in KLC Assessment (some)

• KLCP Participant and KLCP Reviewer produce change
  requests and change guidelines based on their
  evaluation of the process

12
Knowledge Life Cycle Methodology
13
Software Life Cycle Model

• Software lifecycle based on Use Cases
• The system is gradually built during several
  iterations

14
Artefacts in the lifecycle

• Our methodology defines all the necessary
  artefacts as they are distributed along the
  process

15
Artefacts - structure
1..
1..
Use Case
Use-Case Model
Knowledge Management Software System
Study()
Create()
available interfaces
1..
1..
used interfaces
Java Interface
1..
1..
Logical Architecture
Component

• We define relationships between artifacts

Create()
Configure()
Test()
Configure for Workflow()
Integrate()
Configurable Component
Developed Component
Implementable Component
16
Artefacts KMSS Components

• All the Configurable Components have their
  definition in the ICONS framework (see the
  Architecture Specification).
• The methodology provides guidelines on activities
  for these components.

Configurable Component
Concept Glossary
Datalog Inference
Content Repository
Knowledge Schema
Content Categorization
17
Artefacts description example

• Concept Glossary
• Notation
• XTM (XML Topic Maps)
• Outline
• Activities and best practices
• Determine the knowledge domain
• Create the glossary schema

!
Concept Glossary
18
Role example - Knowledge Requirements Designer

• Specifies the boundaries the knowledge available
  through the KMSS
• The associated artefacts describe knowledge with
  different notations

19
Example activities in the Knowledge System
Design (Construction)
1 Study( )
Use Case Model
2 Study( )
Use Case Storyboard
Architect
4 Create Rough( )
3 Create( )
Logical Architecture
Use Case Realization
20
Methodology for the Structural Funds Portal

• Methodology followed by the project team
• Every team member has assigned a role
• Individual components and other artefacts
  prepared according to guidelines
• Iterative process followed

21
Whats new about it?

• The methodology joins general software
  development methodologies with general and
  specific knowledge management methodologies
• Coherent and practical approach to the overall
  Knowledge Management Process - not a YAKM (Yet
  Another Knowledge-Lifecycle Methodology)
• New disciplines, roles, artefacts discovered (and
  described in detail)
• Bridge between the theory (ICONS reaserach
  results) and practice (how to build such a
  system) - the methodology enables systematic and
  repeatable construction of systems based on the
  ICONS framework
• Process participants receive a ready description
  of activities and products the process is not
  ad-hoc

22
T8.5 User oriented assessment of the SF Portal

• Method designed for measurement of user
  satisfaction of the SF Portal based on Gartner
  Methodology
• Main steps
• Defining peoples (roles) responsible for
  conducting the survey and types of portal users -
  done
• Indicators definition, benchmarking - done
• Definition of questionnaire
• Launching the survey
• Analysis of responses

23
Thank you
24
Artefacts - structure
1..
1..
Use Case
Use-Case Model
Knowledge Management Software System

• The KMSS is composed of Components that form the
  Logical Architecture
• Components belong to three classes

Study()
Create()
available interfaces
1..
1..
used interfaces
Java Interface
1..
1..
Logical Architecture
Component
Create()
Configure()
Test()
Configure for Workflow()
Integrate()
Configurable Component
Developed Component
Implementable Component
25
Roles

• All the roles communicate in order to produce
  appropriate artefacts. Roles use certain
  artefacts to produce artefacts they are
  responsible for.
• Roles in Functionality and Knowledge Design
  Domain Expert, Profile Designer, Workflow
  Designer, Knowledge Requirements Designer,
  Functionality Designer
• Roles in Knowledge System Design Knowledge
  Structure Designer, Content Structure Designer,
  Architect, Component Designer
• More

26
Functionality Designer

• Specifies functional frames for the KMSS
• The Use Case Model is the basis for the
  construction process
• Scenarios written in simple grammars

27
Iterative lifecycle model

• Projects consist of iterations that result in
  system builds. Each iteration ends with iteration
  assessment.
• Two types of iterations inception and
  construction. Projects has a single inception
  iteration and several construction iterations.
• The goal of inception iteration is to define the
  system boundary. System boundary is defined by
  means of a use-case and domain model.
• The goal of construction iteration is to produce
  a build design, construct, test and verify a set
  of use-cases assigned to iteration.