Re: Code analysis tool

Christof Pintaske <[email protected]>
Newsgroups gmane.comp.openoffice.devel.tools
Organization StarOffice / Sun Microsystems, Inc.
Message-ID <[email protected]>
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]
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.