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: [email protected]
To: [email protected]
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
