Ver Mensaje Individual
  #4  
Antiguo 21-01-2007
Avatar de Lepe
[Lepe] Lepe is offline
Miembro Premium
 
Registrado: may 2003
Posts: 7.424
Reputación: 29
Lepe Va por buen camino
icarus analyzer, aunque de pago es muy bueno analizando software.

Con ESSModel (open source) se puede documentar, principalmente las clases (algo así como los diagramas de BDS2006), relaciones entre ellas, en htm con hiperenlaces.

Tengo apuntado que DelphiCodeToDoc crea 400 páginas web con las variables tipos y demás, muy completo y solo especificando el .dpr

pro-analyzer (demo) incluye unos 10 tipos de informes:

A report of unusual conditions detected during processing. Items detected include: variables that were not set, variables that were not used, value params reset & invalid real compares.

A list of data elements used by the system in alphabetical order, with their scope, type and definition location.
A list of any duplicate identifiers used, in alphabetical order, with their scope, type and definition location.

A list of the files used by the system and summary of their contents in alphabetical order.
A cross reference of all global identifiers, indicating their usage by subprogram, with their scope, type and references.

A list, in report form, of the subprogram comment blocks that were generated for insertion as headers into the source code.

A system cross reference of all identifiers, indicating their usage by subprogram, with their scope, type and references.

A list of the subprograms used by the system in alphabetical order with their file location.
Source code listing with syntax highlighting.

A traditional cross reference by subprogram, an alphabetical list of identifiers, with their scope, type and references.

A logic map of the program's structure at the subprogram call level. The map may optionally include externals, and brief descriptions of the subprograms. Occurrences of ordinary, mutual and indirect recursion are detected, if present in the program.

A diagram of the object hierarchy for the objects encountered in the program.
A survey of the subprograms used in the system. The 'path' count indicates the number of independent paths in the code, a commonly used measure of program complexity. The various line counts give an indication of subprogram size and quality.

Saludos
__________________
Si usted entendió mi comentario, contácteme y gustosamente,
se lo volveré a explicar hasta que no lo entienda, Gracias.
Responder Con Cita