M. Shepperd, "Design Measures: An Empirical Analysis," Software Eng. J., Jan. 1990. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
Defining and Validating Measures for Object-Based.. - Briand, Morasca, Basili (1999) (3 citations) (Correct)
....for focusing our research on a smaller set of strategies and concepts. A number of studies have been published on software design measures in recent years. It has been shown that system architecture has an impact on maintainability and fault proneness [26] 24] 38] 30] 39] 16] [40], 41] 43] 1] 17] 2] 44] These studies have attempted to capture the design attributes affecting the ease of maintaining and debugging a software system. Most of the design measures are based on information flow between subroutines or declaration counts. We think that, even though they ....
....system. To define it, we will start from its elementary components: software modules. In the literature, there are two commonly accepted definitions of modules. The first one sees a module as a subroutine, and has been used in most of the design measurement publications [35] 20] 26] 38] [40]. The second definition, which takes an object oriented perspective, sees a module as a collection of type, data, and subroutine definitions, i.e. a provider of computational services [13] 25] In this view, a module is the implementation of an Abstract Data Type (ADT) e.g. a package in Ada, ....
M. Shepperd, "Design Measures: An Empirical Analysis," Software Eng. J., Jan. 1990.
Defining and Validating Measures for Object-Based High-Level .. - Briand, Morasca, al. (1999) (3 citations) (Correct)
....and concepts. 1 Object based systems differ from object oriented systems in that inheritance is not allowed. 3 A number of studies have been published on software design measures in recent years. It has been shown that system architecture has an impact on maintainability and faultproneness [HK84, G86, R87, IS88, R90, BRBD90, S90, SB91, Z91, AE92, BTH93, BBH93, ZEWH95]. These studies have attempted to capture the design attributes affecting the ease of maintaining and debugging a software system. Most of the design measures are based on information flow between subroutines or declaration counts. We think that, even though they provide interesting insights into ....
....design of a software system. To define it, we will start from its elementary components: software modules. In the literature, there are two commonly accepted definitions of modules. The first one sees a module as a subroutine, and has been used in most of the design measurement publications [M77, CY79, HK84, R87, S90]. The second definition, which takes an object oriented perspective, sees a module as a collection of type, data, and subroutine definitions, i.e. a provider of computational services [BO87, GJM92] In this view, a module is the implementation of an Abstract Data Type (ADT) e.g. a package in ....
M. Shepperd, "Design Measures: An Empirical Analysis," Software Engineering Journal, January 1990.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC