Re: [tools-dev] Code analysis tool
From: Mohammed Mamdouh [EMAIL PROTECTED] Date: Wed, 07 Sep 2005 21:30:07 + Hi, 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 can you ask that question again? Please do not send private mails. Use this list. -- Pavel Janík With some developers it is not needed to run the code through obfuscator... I have inherited code which only the compiler could understand. -- someone in LKML - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] Code analysis tool
Dear sir we are asking for the developers comments and Ideas on our tool, is it useful, what did we miss..etc, the tool reads the code files idependent from the language it is written in, produces xmi file readable by ARGOUML mainly and we are working on compatibility with other UML tools as BTogether or rational rose, the tool produces a report of flaws in the design these Ramez mentioned and I pasted them again here... these metrics are the first release (design checking) there will be - as planned- automated checklist tool, Style and convention checking tool and also an optimization techniques cheking tool.. 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 interest waiting for the support of everyone interested Best Regards Mohammed Mamdouh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [tools-dev] Code analysis tool
From: Mohammed Mamdouh [EMAIL PROTECTED] Date: Thu, 08 Sep 2005 11:07:20 + Hi, we are asking for the developers comments and Ideas on our tool yes, it could be useful. Now please show us some real results or the tool itself. Do not repeat what you wrote already three times. -- Pavel Janík Q: Or are you waiting for GNU Emacs 21 release with it? A: Unfortunately, I'm not sure I'll live that long. -- One of GNU Emacs's developers in private e-mail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [tools-dev] Code analysis tool
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: dev@tools.openoffice.org To: dev@tools.openoffice.org Subject: [tools-dev] Code analysis tool Date: Sat, 03 Sep 2005 14:22:58 + 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]
[tools-dev] Code analysis tool
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]
Re: [tools-dev] Code analysis tool
Dear sir Thank you for your ineterest and time , I already replied to you but I guess it was lost, I'll reply again , what I'm going to detect takes two levels: sample of our design metrics: 1- depth of inheritance (number of parents). 2- detect and report Intermodule dependency. 3- calculate the Weighted Methods per Class (WMC) 4- detect and report high cyclomatic complexity within methods. (high isn't specific to a number and can be determined by the developer) and other metrics as well , on the code level we have two ways to detect code flaws: 1- code checklist (sun's for Java , GNU for C++ , and a general checklist for any OOP language) 2- code conventions (those of OOo and of checkstyle tool and http://www.cs.columbia.edu/~hgs/etc/coding-style.html) we will support as many as possible and new checks can be plugged in easilly for both checklist and conventions. about the legacy tools we checked for similar tools we found alot that were very helpful for us , we inherited our metrics to be checked from theirs to improve our work and our tool is better mainly for the following reasons : 1- we are not dedicated for a single lnguage as all of these tools are we mainly support checking C++ and java , and smart wizzard can import any OOP language and apply checks on them even those we don't know and never practiced. 2- no tool works on design level for flaw detection , code inspection , code conventions reporting as well , our tool also is planned to generate XMI files readable by designe tools as ARGOUML. 3- our tools is totally free and open source. 4- we will provide a full version dedicated for openoffice.org project to suppor mainly its standards . as soon as a prototype is ready we will post it for comments and testing ( we have now a ready XML parser and processor of some of the design flaws. waiting for your comments your support is highly appreciated From: Christof Pintaske [EMAIL PROTECTED] Reply-To: dev@tools.openoffice.org To: dev@tools.openoffice.org Subject: Re: [tools-dev] Code analysis tool Date: Tue, 19 Jul 2005 10:38:43 +0200 Hi Mohammed, you seem to have a detailed understanding how to implement this tool, however I do not yet understand *what* specificly are the metrics that you want to mesure. Can you provide a list or give an example of what concrete metrics you consider the most important ? Did you check what tools already exist in this area ? Commercial and Open Source ? What metrics do these tools check ? How would your tool be better/different ? The OpenOffice.org coding guide lines are a bit outdated as far as I remember, I'm not sure wether it's useful to focus on them. I recommend to first target a simple prototype that checks only very few metrics (maybe even without any GUI or options) befor aiming at the ultimate flexibility. This helps you to better understand the problem domain and once you have it running it's easier to get feedback about it. I'm not familiar with XMI tech so I cannot comment on how useful that might be. best regards Christof Mohammed Mamdouh wrote: Dear sir you helped us so far so much , but I'll have to ask for more of your time and support , Mr.Christof has discussed ourcontribution and supported us with some notes that really helped us but he seems to be too busy now I couldn't get his opinion of our modification on the vision of the tool , itis planned to support a List of choices to the user of what flaws he wants to detect in his code on three Branches 1- Design generating by parsing the code (Using XMI tech) 2- list of supported checklists for java or C++ or other language can be inserted by a plugin wizard that asks the user for inputs and translate into BNF to detect general flaws of OOP languages. 3- support a third list of code conventions (styling) that user will need to ensure (mainly OpenOffice.org codingGuideLines.SXW) * we will support all of openoffice.org checklist and conventions plus any other respectful checks to add to improve code Quality * we will enable report generation of design or code levels according to lists the user choose with ability to access parts of code reported as incompatibl with the list he choose to detect. * Design can be drawn alone or generated by our tool from the code. If requirements document is required I can provide it ( following tigris readySet project ) what are your comments on the tool in this manner? we are on our design phase now so your concern will be very appretiated - 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] - To unsubscribe, e-mail
Re: [tools-dev] Code analysis tool
Dear sir I want to infrom you that we started working indeed on some phases of our tool .. now we have a UML Designer that generates XMI file where we Developped a parser that reads the XMI file and a processor that detects some of the design flaws , we are Using ARGOUML for designing till now ... but the parser and processor are ours ... we are working on increeasing the number of detectable design flaws... (As Depth of inheritance and High cyclomatic complecity , cyclic dependencies etc..) our plan is to Enhance our design level QA tool then start working on the code level Flaws detection If any comments plz let us know Thanks for your patiance - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
