TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

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

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

Print Reply
"(No Name Available)" <[log in to unmask]>
Thu, 20 Nov 1997 00:23:09 -0500
text/plain (93 lines)
I view Maintainability as covering more than the sum of the other
qualities listed.  Consider how amenable the design is to changes
in requirements which might reasonably be expected for the problem
domain.

Larry Kilgallen

[log in to unmask] (Keith Shillington) wrote:

>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
>>lot.
>>
>>Angel Fern.ndez Guerra.
>>
>>
>Keith Shillington - [log in to unmask]
>Manager, Ada Customer Support
>
>
>----------------------- Headers --------------------------------
>Return-Path: <[log in to unmask]>
>Received: from  relay30.mail.aol.com (relay30.mail.aol.com
>[172.31.109.30]) by air03.mail.aol.com (v36.0) with SMTP; Tue, 18 Nov 1997
>19:52:28 -0500
>Received: from vms.dc.lsoft.com (vms.dc.lsoft.com [206.241.12.2])
>         by relay30.mail.aol.com (8.8.5/8.8.5/AOL-4.0.0)
>         with ESMTP id TAA28826;
>         Tue, 18 Nov 1997 19:13:03 -0500 (EST)
>Received: from PEAR.EASE.LSOFT.COM (206.241.12.19) by vms.dc.lsoft.com
>(LSMTP for OpenVMS v1.1a) with SMTP id <[log in to unmask]>; Tue,
>18 Nov 1997 20:08:10 -0400
>Received: from ACM.ORG by ACM.ORG (LISTSERV-TCP/IP release 1.8c) with
>spool id
>          530690 for [log in to unmask]; Tue, 18 Nov 1997 19:10:46 -0500
>Received: from gw.alsys.com (gw.alsys.com [136.175.17.2]) by mail.acm.org
>          (8.8.5/8.7.5) with SMTP id TAA18432 for <[log in to unmask]>; Tue,
18
>          Nov 1997 19:10:44 -0500
>Received: from rasht.sd.aonix.com (mailhub.alsys.com) by gw.alsys.com
>          (4.1/SMI-4.1.1) id AA23492; Tue, 18 Nov 97 16:06:38 PST
>Received: from puumba.telesoft by rasht.sd.aonix.com (4.1/TS-1.2c) id
>AA04281;
>          Tue, 18 Nov 97 16:05:56 PST
>Received: from godiva by puumba.telesoft (SMI-8.6/SMI-SVR4) id QAA26120;
Tue,
>          18 Nov 1997 16:05:55 -0800
>X-Sender: keith@puumba
>X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32)
>Mime-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>Message-ID:  <3.0.3.32.19971118160408.00988760@puumba>
>Date:         Tue, 18 Nov 1997 16:04:08 -0800
>Reply-To: Keith Shillington <[log in to unmask]>
>Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
>From: Keith Shillington <[log in to unmask]>
>Subject:      Re: Ada Maintainability
>X-To:         Angel Fernandez Guerra <[log in to unmask]>
>To: [log in to unmask]
>In-Reply-To:  <[log in to unmask]>
>

ATOM RSS1 RSS2