TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Keith Shillington <[log in to unmask]>
Reply To:
Keith Shillington <[log in to unmask]>
Tue, 18 Nov 1997 16:04:08 -0800
text/plain (40 lines)
Try this:

  Maintainability := ( Readability
                       + Commentary
                       + Standard_Conformance
                       - Complexity
                       - Missing_Error_Handling
                       + Embedded_Testing_Information )
                      / Semicolon_Line_Count;

To the extent that you can quantify the other measures, maintainability is
merely a direct function of them.  If a software module is readable, well
commented, conforms to standards, lacks excess complexity, handles
anticipated, expected, and unexpected errors well, expresses testability;
it should be easy to maintain.

At 09:39 PM 11/18/97 +0000, Angel Fern\andez Guerra wrote:
>Hi ada activists,
>We are currently performing a code walkthrought (ada source code of
>course). In the checklist we have an entry for maintainability along
>with others like readability, conformance with coding standard, data
>flow errors, testability, etc.
>We found some problems to decide whether a compilation unit passes or
>fails on the maintainability topic. One option could be to evaluate the
>complexity of the code using Mccabe, Haltstead, or/and Harrison figures.
>In this way the problem is the establishment of the valid range for
>these figures.
>If someone can enlighten me or provide any useful information, thanks a
>Angel Fernández Guerra.
Keith Shillington - [log in to unmask]
Manager, Ada Customer Support