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]
