gitdelehe / ontouml-lightweight-editor

Automatically exported from code.google.com/p/ontouml-lightweight-editor
0 stars 0 forks source link

OLED without complex event #48

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. I need build a complex event, but I don't have this item in OLED. 
2. Uma compra pública pode ser modelada como um evento complexo, com 
3. várias etapas (empenho, liquidação e pagamento) e cada etapa, com os 
seus: atestes, homologação, notas de empenho, nota de liquidação, ordem  de 
pagamento e nota fiscal. 

What is the expected output? What do you see instead?

<<complex event>> in toolbox (OLED).

What version of the product are you using? On what operating system?
 oled-1.0.04.jar, o qual é de 08/12/2014. 
 Windos 8 

Please provide any additional information below.

  I am a PHD student and I wish UFO.

Original issue reported on code.google.com by mariano....@gmail.com on 13 Dec 2014 at 4:17

GoogleCodeExporter commented 9 years ago
Hi Mariano,

The current version of OntoUML language reflects the ontological distinctions 
from the structural part of UFO i.e. UFO-A. UFO-A deals with types of endurants 
(objects that persist in time) and their relations.The temporal part of UFO is 
named UFO-B and deals with the types of perdurants (process, events, 
situations, and so son).

Isn't that easy to include an event type in a structural conceptual model 
(diagram) which represents a snapshot of reality.Events and objects are 
different by nature, there is a huge discussion about this topic that I am not 
going to elaborate here but all I can say is that this issue needs to be 
further addressed i.e. whether should we represent this type of entity in a 
structural conceptual model and with what semantics or in a different sort of 
behavioural model.

With that being said, we don't have any entity from UFO-B in the current 
version of the OntoUML language. In this sense, OLED cannot help you very much. 

Having that in mind, if you still need to design a model with such 
characteristics, you can use Astah to represent these stereotypes since it is 
very flexible with regard to extending UML. You can use any stereotype you 
want. However, by doing that, you will no longer be able to use OLED to build, 
evalute and implement your ontology since OLED does not support the Event 
stereotype. 

You can actually think about other types of endurants which may be suitable to 
your case, for instance, relators  have a strict correspondence to events, they 
are created by them. So maybe some of these events can be represented as 
relators in OntoUML. But as I said earlier, you need to be careful in both 
cases, choosing another stereotype for it or introducing events in (Onto)UML 
class diagrams. Perhaps you  might need to choose another language to represent 
such entities.

Hope this helps.
Regards,
John

Original comment by johnguer...@gmail.com on 15 Dec 2014 at 2:21