C redocumentor CERO
The maintenance of a system constitutes 60 to 80% of the total effort placed by the developers. The process of maintenance continues throughout the lifetime of the software as it undergoes numerous modifications. However, with all these improvements, the documentation is often forgotten or not updat...
Saved in:
| Main Authors: | , , , |
|---|---|
| Format: | text |
| Language: | English |
| Published: |
Animo Repository
1999
|
| Subjects: | |
| Online Access: | https://animorepository.dlsu.edu.ph/etd_bachelors/14200 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | De La Salle University |
| Language: | English |
| Summary: | The maintenance of a system constitutes 60 to 80% of the total effort placed by the developers. The process of maintenance continues throughout the lifetime of the software as it undergoes numerous modifications. However, with all these improvements, the documentation is often forgotten or not updated. This makes later maintenance more difficult.
C Redocumentor (CERO) aims to solve this problem. Given a C source code that can be compiled in Turbo C, CERO can generate and display a number of design tools such as structure chart, input-process-output chart, and module specification. These tools give the current design of the program and bridge the gap between documentation and code. Certain metrics and heuristics are also included in order to evaluate the code and give suggestions on how to make it more efficient or portable. CERO also features a pretty printer, which accepts a source code and modifies its appearance to visibly show its structure and make it more readable. In addition, a print option allows the user to print all the design tools, the outputs of the pretty printer, and the evaluation of the source code. |
|---|