Dear All
I am Mohammed Mamdouh , working with Ramez on the OOQ project, we
are still waiting for your support and comments, as filling for ramez, The
tool will produce xmi file from the code also which is readable by ARGOUML
and possibly Borland Together or Rational rose
your concern will be very appreciated
Best Ragerds
Mohammed
From: "Ramez Gabriel" <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: [tools-dev] Code analysis tool
Date: Sat, 03 Sep 2005 14:22:58 +0000
Dear all
first I have to introduce myself, I am a member of the Egyptian team
working on the
code analysis tool, we contacted Mr.Christof pintaske and Mr.Martin
HollMichel and other
members who were a lot of help to us , we finalized the design and went far
enough in the
implementation, Mr.Martin redirected us to the mailing group to ask for the
developers
opinion about the tool, the first release will be delivered soon as a
prototype will be
available before 20/9/2005 for evaluation we are first asking for your
opinions about the
tool and how it's evaluation will be organized, the first release will be
on testing the
design of the source code from any supported language (mainly JAVA, C++ and
more hopefuly)
the next points will be exactly what this tool will automatically check :
Class size:
The number of attributes in a class.
The number of operations in a class.
The number of public operations in a class.
For inner classes, nesting level of the inner class
Class Inheritance:
The number of interfaces the class implements (UML Abstraction).
The number of children of the class (UML Generalization).
The number of descendants of the class (UML Generalization).
The number of ancestors of the class.
The depth of the class in the inheritance hierarchy.
Class to leaf depth.
The number of inherited operations.
The number of inherited attributes.
Class Coupling:
The number of dependencies where the class is the client.
The number of dependencies where the class is the supplier.
The number of associated classes in the same scope.
The number of associated classes in the same scope branch.
The number of associated classes not in the same scope branch.
The number of times the class is externally used as attribute type.
The number of attributes in the class having an interface or class as
their type.
The number of object instances of the class in the model.
The number of classifier roles where the class is the base.
Package Size:
The number of classes in the package.
The number of interfaces in the package.
Nesting level of the package in the package hierarchy.
Package Coupling:
The number of packages on which classes of this package depend.
The number of elements outside the package having an association with a
class inside
the package.
Interface Metrics:
The number of operations in the interface.
The number of times the interface is used as attribute type.
The number of associations the interface participates in.
The number of classes directly implementing the interface (UML
Abstraction).
The number of classes implementing a descendent of the interface.
The number of ancestors of the interface.
The number of descendants of the interface.
Diagram-specific Metrics:
The number of classes on the diagram.
The number of interfaces on the diagram.
The number of packages on the diagram.
The number of associations on the diagram.
The number of generalizations on the diagram.
The number of abstractions on the diagram.
thanks for your patience and we are sorry for the long mail but we are
waiting for the
comments and support of anyone interested
your concern will be highly appreciated
best regards
Ramez gabriel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
