Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

WICSA 2012 presentation - Ontology-based software architecture documentation

No description
by

K.A. de Graaf

on 20 July 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of WICSA 2012 presentation - Ontology-based software architecture documentation

File-based approach is
less efficient and effective

Structuring of AK and
formal description of AK

Qualitative evaluation of
ontology-based approach
is positive
Conclusions
Findings
Introduction
Documentation
I need to find all decisions about one component
I need to find all alternatives and related decisions to this one decision
I need to find all software and Quality attributes affected by this decisions
Different views
Ontology-Based Software Architecture Documentation
Klaas Andries de Graaf
Many thanks!
Questions?
1A: Which settings have an impact on behaviour XX?
1B: Which settings have an impact on behaviour YY?
Ontology-based approach:
File-based approach:
- No structure to find settings
- Settings are not explicit
less time
more time
Less correct
no significant difference
implication
Implication
Experiment - overall results
More time saved (53%)
More correct answers (24%)
Statistically significant for most questions
'Ontology-based' documentation
SADs
SBDs
System reference
UML diagrams
Ontology
Semantic Wiki tool
Documentation
Experiment
File-based documentation
-versus-
Ontology based documentation
7 questions about software project
MS word
File explorer
Magicdraw
Semantic Wiki
Ontology-based approach
Structuring of
knowledge
Formal description of knowledge
Question 1
Time
Correctness
3A: Which decisions have been made around component X?
3B: Which decisions have been made on the configuration of behaviour XX, YY, ZZ, and QQ?
File-based approach:
- Structuring of decisions
not fine-grained enough.
more time
File-based approach:
- Decisions are informally recorded
Less correct
no significant difference
Question 3
Time
Correctness
Ontology-based approach:
File-based approach:
- Structure not consistent for decisions
less time
more time
less time
From which sources do you get software knowledge?
Do you think it is worthwhile to set up a semantic wiki at Océ for searching software knowledge & documentation management?
Yes - 17.5 (67.3%)
No - 2 (7.7%)
I do not know - 6.5 (25%)
Mostly People
Documents

Source code
Sharepoint

Docfinder

CM synergy
Peng Liang
Antony Tang
Hans van Vliet
Different cross-sections required
on Architecture knowledge
Documentation
Documentation
less time
more time
File-based approach
- Some setting are recorded more informal
Ontology-based approach:
More correct
More correct
Ontology-based approach:
See how the ArchiMind tool works at
http://archimind.few.vu.nl/index.php
Efficiency and effectiveness of AK retrieval
Identify costs & benefits of implementing and using the approach.

Understand underlying technology.

How should software documentation be structured according to how users use it?
Full transcript