About Arabeyes Quality Software Standard

[Tarik FDIL <tfdil at sagma dot ma>]

Salam,

With Lassad, I'm going back to Siragi-OCR project. Since we aim to do good 
job, we've some questions about quality software in arabeyes projects.

UMHO, producing quality software need at least some tools and practices in 
"planning", "designing",  "coding" and "quality measuring"

 **Planning**, I think the "Todos"  tool in arabeyes.org is a good tool for 
planning and monitoring projects and parts of projects. Without planning 
projects we can't know how much of project is done and what's the remainnig 
work.  

**Designing**, coding is a good think but designing software before coding it 
is better. Without sound design, we can't produce bug-free, evolving and 
maintainble software. Since design is essentially producing documents, 
Arabeyes CVS is a good tool to store and track design documents. Every design 
language could be used. I personnaly like UML... But is there  free software 
tools to produce UML diagrams ? Anyway we can always use OO to produce basic 
diagrams.

**Coding** we should write code following a coding standard. Is there an 
arabeyes coding standard ? 

**quality measuring**  bugs.arabeyes.org/ is a sound tool to track bugs. But, 
to be meaningful, bugs measurements should be counted per lines of code (or 
function points). Is there an arabeyes standard  to count LOC (Line Of Code) 
in C, C++ or other languages used by arabeyes developers ?

Best regards 
Tarik