Difference between revisions of "Submissions:OOPMetrics"

(Review has been created. Annotation 'assigned' has been removed.)
(Mostly updated according to the reviews.)
Line 2: Line 2:
 
{{Graphical representation header}}
 
{{Graphical representation header}}
 
{{Graphical representation
 
{{Graphical representation
−
|ImageName=OOPMetrics.png
+
|ImageName=OOPMetricsDiagram.png
 
}}
 
}}
 
{{Content OP Proposal Template
 
{{Content OP Proposal Template
Line 8: Line 8:
 
|Name=OOPMetrics
 
|Name=OOPMetrics
 
|Intent=To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system.
 
|Intent=To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system.
−
|Domain=Software Metrics
+
|Domain=Software Engineering
 
|CompetencyQuestion=What are the software metrics for a particular project/package/class/method?
 
|CompetencyQuestion=What are the software metrics for a particular project/package/class/method?
 
Knowing the software metrics, is there a design-flaw in the software system?
 
Knowing the software metrics, is there a design-flaw in the software system?
−
|ContentODPDescription=This is an ontology pattern that represents software metrics for OOP.
+
|ContentODPDescription=This is an ontology pattern that represents software metrics for OOP. The unit test in the ontology pattern shows an example of how an ontology that uses this pattern can be queried to satisfy the scenario.
 
|ReusableOWLBuildingBlock=http://www.cs.ubbcluj.ro/~ivpop/ontologies/oopmetrics.owl
 
|ReusableOWLBuildingBlock=http://www.cs.ubbcluj.ro/~ivpop/ontologies/oopmetrics.owl
 
|Consequences=Software anti-patterns (design-flaws) can be detected based on software metrics by using this ontology pattern.
 
|Consequences=Software anti-patterns (design-flaws) can be detected based on software metrics by using this ontology pattern.
−
|Scenario=Find if a class is a God Class based on it's metrics
+
|Scenario=Find if a class (or which class) is a God Class based on it's metrics
 
}}
 
}}
 
{{Element list header}}
 
{{Element list header}}
Line 52: Line 52:
 
{{Has Element Template
 
{{Has Element Template
 
|HasElement=OOPProject
 
|HasElement=OOPProject
 +
}}
 +
{{Takes in account review
 +
|TakesInAccountReview=MariaPoveda about OOPMetrics
 +
}}
 +
{{Takes in account review
 +
|TakesInAccountReview=RinkeHoekstra about OOPMetrics
 
}}
 
}}
 
{{Additional information header}}
 
{{Additional information header}}
 
Note from the author to the evaluators:
 
Note from the author to the evaluators:
 
the title of the related article is: "An Ontology Pattern for Software Metrics", submission 21.
 
the title of the related article is: "An Ontology Pattern for Software Metrics", submission 21.
 +
 +
 +
 +
 +
 +
 +
 +
[[Category:Review assigned]]
 
{{Scenarios about me}}
 
{{Scenarios about me}}
 
{{Reviews about me}}
 
{{Reviews about me}}
Line 63: Line 77:
 
|Event=WOP:2012
 
|Event=WOP:2012
 
}}
 
}}
−
 
−
 
−
[[Category:Review assigned]]
 

Revision as of 19:36, 28 August 2012

Warning.gif

Warning!

This is an old revision. Go to current revision

Certified.png
This pattern has been certified.

Related submission, with evaluation history, can be found here

Working.gif Last modified date is: 2012-08-28

Graphical representation

Diagram

OOPMetricsDiagram.png

General description

Name: OOPMetrics
Submitted by: IonelVirgilPop
Also Known As:
Intent: To represent software metrics especially for the purpose of detecting design-flaws in software systems based on these metrics. This is useful for re-engineering the software system.
Domains:

Software Engineering

Competency Questions:
  • What are the software metrics for a particular project/package/class/method?

Knowing the software metrics

Solution description: This is an ontology pattern that represents software metrics for OOP. The unit test in the ontology pattern shows an example of how an ontology that uses this pattern can be queried to satisfy the scenario.
Reusable OWL Building Block: 1 (754)
Consequences: Software anti-patterns (design-flaws) can be detected based on software metrics by using this ontology pattern.
Scenarios: Find if a class (or which class) is a God Class based on it's metrics
Known Uses:
Web References:
Other References:
Examples (OWL files):
Extracted From:
Reengineered From:
Has Components:
Specialization Of:
Related CPs:



Elements

The OOPMetrics Content OP locally defines the following ontology elements:

ObjectProperty hasClass (owl:ObjectProperty) Refers to an OOPClass from an OOPPackage.


Se refera la o OOPClass dintr-un OOPPackage.

ArrowRight.gif hasClass page
ObjectProperty hasMethod (owl:ObjectProperty) Refers to an OOPMethod from an OOPClass.


Se refera la o OOPMethod dintr-o OOPClass.

ArrowRight.gif hasMethod page
ObjectProperty hasMetric (owl:ObjectProperty) Refers to a software metric that an OOPProject/OOPPackage/OOPClass/OOPMethod has.


Se refera la o metrica soft pe care o are un/o OOPProject/OOPPackage/OOPClass/ OOPMethod.

ArrowRight.gif hasMetric page
ObjectProperty hasPackage (owl:ObjectProperty) Refers to an OOPPackage from an OOPProject.


Se refera la un OOPPackage dintr-un OOPProject.

ArrowRight.gif hasPackage page
DatatypeProperty hasFloatValue (owl:DatatypeProperty) The real value of the software metric.


Valoarea reala pentru metrica soft.

ArrowRight.gif hasFloatValue page
DatatypeProperty hasIntegerValue (owl:DatatypeProperty) The integer value of the software metric.


Valoarea intreaga pentru metrica soft.

ArrowRight.gif hasIntegerValue page
DatatypeProperty hasName (owl:DatatypeProperty) This represents the name (more precisely the acronym) of the category of software metric. Such as: "WMC" for "Weighted Methods Count", TCC for "Tight Class Cohesion", etc.


Aceasta reprezinta numele (mai precis acronimul) pentru categoria de metrica soft. Cum ar fi: "WMC" pentru "Weighted Methods Count", TCC pentru "Tight Class Cohesion", etc.

ArrowRight.gif hasName page
Class OOPClass (owl:Class) This represents the "class" concept from object-oriented programming.


Aceasta reprezinta conceptul "clasa" din programarea orientata obiect.

ArrowRight.gif OOPClass page
Class OOPMethod (owl:Class) This represents the "method" concept from object-oriented programming.


Aceasta reprezinta conceptul "metoda" din programarea orientata obiect.

ArrowRight.gif OOPMethod page
Class OOPMetric (owl:Class) This represents a software metric specific to object-oriented programming.


Aceasta reprezinta o metrica soft specifica programarii orientate obiect.

ArrowRight.gif OOPMetric page
Class OOPPackage (owl:Class) This represents the "package" concept from object-oriented programming.


Aceasta reprezinta conceptul "pachet" din programarea orientata obiect.

ArrowRight.gif OOPPackage page
Class OOPProject (owl:Class) This represents a software project.


Aceasta reprezinta un proiect soft.

ArrowRight.gif OOPProject page


Additional information

Note from the author to the evaluators: the title of the related article is: "An Ontology Pattern for Software Metrics", submission 21.

Scenarios

Scenarios about OOPMetrics

No scenario is added to this Content OP.

Reviews

Reviews about OOPMetrics
There is no review about this proposal.
Some subquery has no valid condition.

This revision (revision ID 11185) takes in account the reviews: OOPMetrics (MariaPoveda about OOPMetrics, RinkeHoekstra about OOPMetrics)

Other info at evaluation tab


Modeling issues

Modeling issues about OOPMetrics
There is no Modeling issue related to this proposal.
Some subquery has no valid condition.


References

Add a reference


Timer.png Submission to event

WOP:2012

Retrieved from "http://ontologydesignpatterns.org/index.php?title=Submissions:OOPMetrics&oldid=11185"
The page [[Bootstrap:Footer]] was not found.