| CreationDate
|
17 September 2010 +
|
| HasClearProblemDescription
|
The problem description is ok; however, I … The problem description is ok; however, I would like to comment that the problem example (with the figure) is not clear enough. I mean it is not clear the meaning of the first hierarchy and of the second; I assume 'classify' means to run a reasoner, but I think this should be explained in the pattern. k this should be explained in the pattern.
|
| HasProblems
|
Apart from the problems already pointed ou … Apart from the problems already pointed out by Catherine and Boris, I would like to mention that the solution has also inconvenience that should be included in the description. For example, sometimes to state explicitly the hierarchy is better than provide axioms to implicitly define it (e.g. Naïve developers can include errors in the axioms). elopers can include errors in the axioms).
|
| HasReusability
|
I see here a problem with respect to the restrictions that should be included by developers. This could be a place of problems in the modelling, because of the difficulties of thinking about restrictions that allow to classify classes.
|
| HasReviewScore
|
1 -needsminorrevision +
|
| HasReviewSummary
|
The pattern provides a solution to represent multi-inheritance.
|
| HasReviewerConfidence
|
High
|
| HasUnderstandability
|
In general the pattern is well explained.
|
| LastModifiedDate
|
17 September 2010 +
|
| Modification dateThis property is a special property in this wiki.
|
17 September 2010 10:19:46 +
|
| ReviewAboutSubmissionThis property is a special property in this wiki.
|
Normalization +
|
| ReviewAboutVersion
|
10,115 +
|
| SubmittedBy
|
MariCarmenSuarezFigueroa +
|
| Categories |
QCReview +
|
