MOKA Interest Group April 2001, the 25th

1
MOKA Interest Group April 2001, the 25th
2
Agenda

• SNECMA  Hydro 2000  project overview
• Knowledge acquisition cycle
• Knowledge acquisition results
• MOKA Formal Model
• main benefits and concerns
• Work load split
• Questions

3
 Hydro 2000  project overview
4
Knowledge acquisition cycle
Knowledge structuring
I N T E R V I E W S
Expert 1
Knowledge Engineer
Coordinator
Expert N
MOKA views
No
StructureProduct and process views
VALIDATION of the structure ?
Yes
Knowledge formalizing
Informal Model
Knowledge Book - Electronic - Paper
5
MOKA Informal Model Product view ( Fuel pump 
high pressure)
Structural Entities
6
MOKA Informal Model Process view ( Fuel pump )
7
Our experience

• Knowledge acquisition requires different steps
  to
• establish the structure (product, process,
  function, )
• insure the consistency of all collected
  informations

• Knowledge acquisition requires different skills
• Knowledge architect structure knowledge
• coordinator animate the debates and define the
  best practices
• expert provide the state of art in his field

• Generation of two formats of knowledge book
• an electronic version (HTML format)
• Visibility and access on all identified links,
• Possibility to open each MOKA forms.
• a paper version (Word format)
• Group all informal model within an unique
  document,
• Easy to edit the whole knowledge acquisition.

8
MOKA Formal Model
Formal model
Code Framework
Informal model Knowledge Book
Automatic
Specifications
Request for Complement
Rules
Integrate
Constraints
9
MOKA Formal Model
Formal model
Informal model
Link
10
MOKA Formal Model
11
MOKA benefits and concerns

• Benefits
• ICARE forms have proven to be an efficient way to
  structure the Knowledge by the different actors
• Better application architecture than with rapid
  application development technics
• make easier the re-use of existing and validated
  components for new conceptions
• Knowledge book can be used to train new employees
• Sharing of knowledge between experts
• Knowledge accessible from application

• Concerns
• Difficult to fix the level of detail of the forms
  (mandatory fields, description, etc..)
• Need a better tool to navigate between the ICARE
  forms (use of Rational Rose for this project)
• Hard to recover a very precise information among
  several MOKA forms ( within many files)
• MML versus UML
• Bi-directional link between formal model and code
  (CASE TOOL APPROACH)

12
Work load split
13
Questions

• Thank you
• Questions