[from Deborah McPherson]:
> With a checklist to follow, untrained customers will be better
> prepared and able to state what their needs are and organize their
> resources to provide ontology engineers, programmers, and formal
> specification writers with what THEY need to get the data to flow in
> potentially customized, atypical manners. (01)
[from Pat Hayes]:
> For the record, our KE mavens (I am not one of them) tell me that one
of
> most efficient such analysis techniques involves collaborative
> construction of a concept map, which is one reason we have developed
> so much software around this apparently trivial notion. (02)
Pat and Deborah, (03)
My group's experience in uncovering project requirements is the same as
Pat's KE mavens - simple concept maps are a fine, collaborative way to
get at underlying concepts. User training is easy, development fast, and
the results are easy to read and understand. They create a basis for
jumping off into any degree of formalism appropriate for the next steps
of the project. (04)
Deborah wishes users to think through a checklist in advance of the
first collaboraton meeting. This has benefits, but perhaps also a hidden
booby trap. A checklist can guide thinking along pre-determined lines
(i.e., the concepts underlying the checklist). This can be at odds with
the need for collaborative exchange. In other words, the
ontologist/analyst group's culture may inadvertantly color the user
group' cultural assumptions. This, however, can be mitigated. (05)
Regards,
--------------------------------------------------------
Jeffrey Schiffel
The Boeing Company - IDS Wichita
System of Systems Engineering
-------------------------------------------------------- (06)
---------------------------------------------------------------------
IHMC (850)434 8903 or (650)494 3973 home
40 South Alcaniz St. (850)202 4416 office
Pensacola (850)202 4440 fax
FL 32502 (850)291 0667 cell
phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes (07)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config:
http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/ Community Wiki:
http://ontolog.cim3.net/wiki/ To Post:
mailto:ontolog-forum@xxxxxxxxxxxxxxxx (08)
_________________________________________________________________
Message Archives: http://ontolog.cim3.net/forum/ontolog-forum/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontolog-forum/
Unsubscribe: mailto:ontolog-forum-leave@xxxxxxxxxxxxxxxx
Shared Files: http://ontolog.cim3.net/file/
Community Wiki: http://ontolog.cim3.net/wiki/
To Post: mailto:ontolog-forum@xxxxxxxxxxxxxxxx (09)