Re: Code analysis tool (Egyptian team)

Dear sir

I'm sorry if my contribution was not clear , but I couldn't find any specifications for this tool , But in the way I see this tool and I pln to produce is that it will have two main tracks

* online developping consultant that helps the developper to Identify flaws in his design or implementation (I do not mean bugs or errors) I mean best class design and methods used or however it can automatically help the developper) in order to introduce better source with higher flexibility , maintainability and extensiability as required , and also to test formally introduced source code and detecting areas that need testing and enhancements with Hints of how to do so, That's why I needed the source code as a case study , this is the generic consulting

* second track is detecting step by step if the code follows till this instance of time the OpenOffice.org standards.

* The Tools should support analysis for Java,C++ and basic lnguages

* API testing and GUI testing were not in the original plan but they can be added to the tool if time were on our side.

Note : I reviewed the links and I can see I will use alot of help there but still my planned tools will be more generic in a way that any developper should be able to use on his work , and As Mr.martin told me that I can introduce my work as a CWS to the code base. and that's what I hope for after finishing my work.

Plz if U find I need any corrections I will be more than thankful

Thanks in advance

>From: Malte Timmermann <[email protected]>
>Reply-To: [email protected]
>To: [email protected], [email protected]
>Subject: Re: [tools-dev] Code analysis tool (Egyptian team)
>Date: Mon, 27 Jun 2005 12:03:56 +0200
>
>Mohammed,
>
>you already got some answers about contribution an so on from Martin
>Hollmichel.
>
>I am still not able to figure out what exactly you plan to do.
>
>You write about a *module*, but I have the feeling that you don't
>plan to write a tool for doing the analysis, but to do some analysis
>with existing tools or code reviews.
>
>Can you please clarify?
>
>Anyway, there will be no deadline.
>- If it's a tool, it's not part of the product
>- If it's code changes, you can

do them in a CWS, which will IMHO
>not be integrated before OOo 2.0 is out.
>
>Anyway, I love to see that people want to improve OOo
>code/structure, so let me know what you plan to do...
>
>Please find some usefull URL's below.
>
>Regards,
>Malte.
>
>
>qa:
>http://qa.openoffice.org/
>
>Automated GUI Testing
>http://qa.openoffice.org/qatesttool/index.html
>
>Automated API testing
>http://qa.openoffice.org/qadevOOo_doc/index.html
>
>
>
>
>Mohammed Mamdouh wrote:
>>Dear sir
>>
>>we are trying to contact you from a week or more to know if there
>>is a dead line to deliver the tool or is it opened for enhancements
>>, your reply will be highly appreciated
>>
>>Thanks in
advance
>>
>>
>>
>>---------------------------------------------------------------------
>>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]
>