While I was preparing the
table below, Todd and Leo started a dialogue on the summit-org
list on the same topic, so I've included their exchange after the
Table.
I
hope to be able to do little more research and
propose a reasonable synthesis lifecycle. I
probably won't make it into any of the live
panel sessions, but we can discuss it on this
list.
Terry
This
table is the result of my review of the
presentations from the first four track
panels. I collected all references to
Lifecycle (or in one case, simply 'cycle').
I didn't review the 'mid-term' presentations
from this week (22 Feb), and because I was
pressed for time, I didn't look at any of
the session chairs' intro charts
My
purpose was to illustrate that there are
many perspectives on Lifecycle.
I think it's clear that we don't have a
clear consensus on the meaning of Lifecycle
expressed in the Summit title.
Terry
|
| Day |
Track |
Presenter |
Lifecycle
Label |
Phases |
NOTES |
| 24 Jan |
B |
Schneider |
No |
|
|
|
|
Polzer |
Ontology Life Cycle
Phase Dimensions |
(1)The need for, and
scope of, an ontology have been developed
(2)Some portion of the formal representation of the
ontology has been developed
(3)All of the planned formal representation is complete
(4)The ontology is populated with instance data
(5)Reasoners have used the ontology to achieve real-world
results
(6)The ontology is in operational use
(7)The ontology is evolving based on feedback from
operational use |
|
|
|
Balboni |
Black Box Testing
Paradigm |
(1)Unit Test
(2)Integration
(3)Functional
(4)System
(5)Acceptance
(5)BETA |
|
|
|
Katsumi |
Lifecycle
to support the development of expressive Ontologies |
Design
Requirements
Verification
Tuning
Application |
|
| 31 Jan |
A |
Poveda |
No |
|
|
|
|
Tartir |
No |
|
|
|
|
Duque-Ramos |
No |
|
|
| 7 Feb |
C |
Smith |
No |
|
|
|
|
Partridge
|
No |
|
|
|
|
Levenchuk (1) |
Life Cycle Data Pyramid
|
Data
Model 201
Base Templates ~ 2000
Base Data ~ 200 thousands items
Specialized Data Standard: ~ millions
Specialized Data Non-standard (Proprietary): ~ tens of
millions
Project Data ~ billions |
|
|
|
Levenchuk (2) |
ISO 15926 Equipment
Life-Cycle |
Stage 1 –
Standardization and Supplier's Catalog
Stage 2 – Typical Design
Stage 3 – Particular Plant Design
Stage 4 – Plant Procurement
Stage 5 – Plant Operations |
|
|
|
Levenchuk (3) |
Mapping Methodology:
Place in the Life Cycle |
Process Design
Plant Design and Detailed Engineering
Procurement and Construction
Operations and Maintenance |
|
|
|
Bennett |
No |
|
|
| 14 Feb |
D |
Denny |
Ontology
Development Phases |
Exploration
Phase
Management Phase -
Design Phase
Build Phase
Validation Phase
Integration & Use Phase
Maintenance Phase |
Each
Phase described in one or more pages. |
|
|
Gruninger |
No |
|
|
|
|
Holm |
No |
|
|
|
|
Matthews |
Ontology and
Architecture Evaluation Cycle |
•Before check-in,
locally
– Validation: Automated, syntax and inherent checks
• Within the hour, from source control (CruiseControl)
– Validation
• Nightly build and index
– Validation
– Search Quality: Automated, black box, TREC methodology
– Unit tests: Automated, glass box, semantic, regression
and functional
• Fortnightly push to production
– Validation, search quality, unit tests
• Monthly QA cycle |
|
-------- Original Message --------
Todd,
You are right that we have not in general explicitly referred to the ontology lifecycle. But comments in the chat sessions continue to raise this issue, along with some bullets in previous presentations. The short answer is intrinsic, extrinsic, and in-between aspects of evaluation are required at every step of the lifecycle, but they will be different based on the stage of the lifecycle. E.g., if we assume that the ontology lifecycle is similar to but extends the typical software/system lifecycle, then we have at least the usual way-stations or processes of the latter lifecycle, i.e., approximately:
- Rationale (goals, objectives, at least initial, but subject to refinement)
- Analysis (generally requirements, but also what potential resources meet the requirements, and so it loops into Design, Implementation, etc.)
- Design (also Architecture: see below)
- Implementation (potentially complex)
- Deployment (potentially complex, since may involve many applications, some of which call each other)
- Maintenance (potentially complex)
There may be many cycles in the above, i.e., within each major process, but also loops between one process and others. The graph structure may vary (topology if you wish), depending on the implicit meta-model, i.e., linear/waterfall, spiral, etc.
Each of these processes have "testing" near the end of its process instance, which we can think of as a validation/verification of the results of the process, which can therefore lead to a refinement/correction. This is standard for software engineering/system. Initial Design may have Architecture as a sub-process, which itself repeats, loops.
Of course the complexity of the above is also affected by the size of the effort.
Also, Track C is looking at process improvement, so the above is probably most rooted in that track (I'll talk a bit about this and ontology architecture in the next Track C session, as I'm sure others will).
Thanks,
Leo
>-----Original Message-----
>From: ontology-summit-org-bounces@xxxxxxxxxxxxxxxx [mailto:ontology-
>summit-org-bounces@xxxxxxxxxxxxxxxx] On Behalf Of TSchneider
>Sent: Saturday, February 23, 2013 1:21 PM
>To: ontology-summit-org@xxxxxxxxxxxxxxxx
>Subject: [ontology-summit-org] OntologySummit2013: Ontology Lifecycle -
>Explicit Description?
>
>Though this year's summit subject is about the 'ontology lifecycle'
>I don't recall any explicit description thereof.
>
>If I missed it, could someone send me a link to where is was described
>among the sessions?
>
>Thank you.
>
>Todd
>
>___________________________________________________________
>______
>To Post: mailto:ontology-summit-org@xxxxxxxxxxxxxxxx
>Msg Archives: http://interop.cim3.net/forum/ontology-summit-org/
>Community Files: http://interop.cim3.net/file/work/ontology-summit-
>org/OntologySummit2013/
>Community Wiki: http://ontolog.cim3.net/cgi-
>bin/wiki.pl?OntologySummit2013
_________________________________________________________________
To Post: mailto:ontology-summit-org@xxxxxxxxxxxxxxxx
Msg Archives: http://interop.cim3.net/forum/ontology-summit-org/
Community Files: http://interop.cim3.net/file/work/ontology-summit-org/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
|
_________________________________________________________________
Msg Archives: http://ontolog.cim3.net/forum/ontology-summit/
Subscribe/Config: http://ontolog.cim3.net/mailman/listinfo/ontology-summit/
Unsubscribe: mailto:ontology-summit-leave@xxxxxxxxxxxxxxxx
Community Files: http://ontolog.cim3.net/file/work/OntologySummit2013/
Community Wiki: http://ontolog.cim3.net/cgi-bin/wiki.pl?OntologySummit2013
Community Portal: http://ontolog.cim3.net/wiki/ (01)
|