A software complexity model of object-oriented systems

Graduate School of Business, University of Colorado, Boulder, CO 80309-0419, USA
Decision Support Systems (Impact Factor: 2.31). 03/1995; 13(3):241-262. DOI: 10.1016/0167-9236(93)E0045-F


A model for the emerging area of software complexity measurement of OO systems is required for the integration of measures defined by various researchers and to provide a framework for continued investigation. We present a model, based in the literature of OO systems and software complexity for structured systems. The model defines the software complexity of OO systems at the variable, method, object, and system levels. At each level, measures are identified that account for the cohesion and coupling aspects of the system. Users of OO techniques perceptions of complexity provide support for the levels and measures.

Download full-text


Available from: David Monarchi
  • Source
    • "Ideal degree vectors I, through normalized and obtain the weight vector of relationship between the system functional objective 4) Determination of competing demands While conducting customer satisfaction surveys, customers evaluated for competitive conditions of four companies by numbers 1-5. (Including: 1 means customer demand for a particular product for a very unsatisfactory and 5 means customer demand for a particular product for a very satisfied), then obtained competitor assessment data by sort out the investigation file [17]. By the formula: "
    [Show abstract] [Hide abstract]
    ABSTRACT: The aim of this paper established priority level determines method of manufacturing system functional objective based QFD theory, priority sequence presented and the functional objective priority weights, advised manufacturing system functional objective decisions, provides technology support and application reference for system functional objective decisions.
    Preview · Article · Sep 2015 · International Journal of Multimedia and Ubiquitous Engineering
  • Source
    • "Engineering (CONSEG) 15th - 17th November, 2013 @ Pune, India Copyright (c) 2013 Computer Society of India (CSI) ACM X-XXXXX- XX-X/XX/XX ...$15.00. [9], Li and Henry [12], McCabe [15], Tegarden et al. [18], Lorenz and Kidd [13] and Chidamber and Kemmerer metric [5] suite. CK metrics suite is a set of six metrics such as Weighted method per class (WMC), Depth of inheritance tree (DIT), Number of children (NOC), Coupling between objects (CBO), Response for class (RFC), and Lack of cohesion among methods (LCOM). "
    [Show abstract] [Hide abstract]
    ABSTRACT: Open source tools are coded in different languages and developed in different project management styles. Hence, the quality varies from version to version of any software. Quality can be best measured from the number of faults in the software. This paper presents an approach for fault prediction in case of Apache open source integration framework using Chidamber and Kemerer (CK) Metrics suite. Statistical evaluation (such as liner and logistic regression) and machine learning method (neural network) are used for fault prediction. The six CK Metrics were used in analyzing the framework. This paper emphasizes on performance of CK Metrics values for different versions of the Apache integration framework (AIP). The results achieved highlight the influence of CK Metrics in fault prediction
    Full-text · Conference Paper · Nov 2013
  • Source
    • "Fig. 2. SQUANER Analyzer. and overridden methods and total number of methods [8]; Cyclomatic Complexity Metric (CC) [9]; numbers of hierarchical levels below a class and class-to-leaf depth [10]. The component Pattern detection is responsible for design patterns detection. "
    [Show abstract] [Hide abstract]
    ABSTRACT: Despite the large number of quality models and publicly available quality assessment tools like PMD, Checkstyle, or FindBugs, very few studies have investigated the use of quality models by developers in their daily activities. One reason for this lack of studies is the absence of integrated environments for monitoring the evolution of software quality. We propose SQUANER (Software QUality ANalyzER), a framework for monitoring the evolution of the quality of object-oriented systems. SQUANER connects directly to the SVN of a system, extracts the source code, and perform quality evaluations and faults predictions every time a commit is made by a developer. After quality analysis, a feedback is provided to developers with instructions on how to improve their code.
    Preview · Conference Paper · Oct 2010
Show more