共查询到20条相似文献，搜索用时 0 毫秒
1.
Communication software systems have become very large and complex. Recognizing the complexity of such software systems is a key element in their development activities. Software metrics are useful quantitative indicators for assessing and predicting software quality attributes, like complexity. However, most of existing metrics are extracted from source programs at the implementation phase of the software life cycle. They cannot provide early feedback during the specification phase; and subsequently it is difficult and expensive to make changes to the system, if so indicated by the metrics. It is therefore important to be able to measure system complexity at the specification phase. However, most software specifications are written in natural languages from which metrics information is very hard to extract. In this paper, we describe how complexity information can be derived from a formal communication protocol specification written in Estelle so that it is possible to predict the complexity of its implementation and subsequently its development can be better managed. © 1998 John Wiley & Sons, Ltd. 相似文献
2.
3.
RICHARD WEST 《Journal of Software: Evolution and Process》1996,8(5):345-356
The monograph, Improving the Maintainability of Software, has the objective of providing practical guidance on the maintainability of software: maintainability definitions, factors, building and improvement suggestions, and an assessment method. The first part of this review provides an introduction to the monograph and discusses the general software maintainability guidance it provides. The second part provides a more in-depth review of the maintainability assessment method. This monograph is easy to read and understand. The guidance provided appeals to common sense and reflects an understanding of many software maintenance concerns. Although the scope of the monograph is primarily business information systems, the guidance is basically sound for many other types of applications in business, industry, government and military organizations. The defined framework of maintainability factors, features, and measures provides interesting guidance for discovering potential areas of concern. Identifying these areas of concern can be a basis for directing action and resources to the more critical maintenance activities. The maintainability assessment method provided by this monograph is not adequately supported by references or detailed information. Definitely read this monograph for its practical guidance. But be careful when applying the maintainability assessment method and analysing the results. 相似文献
4.
5.
Denis Kozlov Jussi Koskinen Markku Sakkinen Jouni Markkula 《Journal of Software: Evolution and Process》2008,20(1):31-58
The focus of the paper is to reveal the relationships between software maintainability and other internal software quality attributes. The source code characteristics of five Java‐based open‐source software products are analyzed using the software measurement tool SoftCalc. The relationships between maintainability and internal quality attributes are identified based on the Pearson product moment correlation analysis. Our results show negative correlations between maintainability and some well‐known internal software quality attributes, as well as the ones between maintainability and complexity metrics. Particularly, according to our results, the Number of Data Variables Declared and the Decisional Complexity McClure Metric have the strongest correlations with maintainability. The results of our study, that is to say, knowledge about the relationships between internal software quality attributes and maintainability, can be used as a basis for improvement of software maintainability at earlier stages of the software development process. Copyright © 2007 John Wiley & Sons, Ltd. 相似文献
6.
产品线体系结构需要支持多种变化性以满足其内部成员特性，因而是重要又复杂的软件产品线子系统。本文通过分析产品线体系结构的vADL规约，充分考虑产品线体系结构变化性对其复杂性度量的影响，生成产品线体系结构信息流图PLA—IFG，基于PLA—IFG，实现自动化度量产品线体系结构复杂性，提出了支持变化性的产品线体系结构复杂性度量方法。 相似文献
7.
8.
9.
面向对象软件度量学研究 总被引：4，自引：0，他引：4
软件度量学是软件工程的一个新分支，通过度量反馈的信息来控制开发过程，以提高软件质量，是一种行之有效的方法。传统的面向过程的软件将数据和操作分离，强调以算法为核心。近年来发展起来的面向对象软件的主要特性包括抽象性、封装性、继承性和多态性，将数据和操作封装，强调以对象为核心。因此，面向对象软件度量方法也随之发展起来，著名的是C＆K度量方法。文中指出C＆K度量方法的不足，并就面向对象度量学有待解决的问题提出了—些观点。 相似文献
10.
Kurt D. Welker Paul W. Oman Gerald G. Atkinson 《Journal of Software: Evolution and Process》1997,9(3):127-159
When software maintenance results in changing the source code, the change frequently occurs in an undisciplined manner that results in source code that is inherently more difficult to maintain. The long-term effect may be thought of as a downward spiral that culminates in virtually ‘unmaintainable’ code where it is more cost effective to just start again. Too often, software personnel and managers, aware that the code is becoming less maintainable, have been unable to estimate with useful accuracy the degree to which maintainability has diminished. The result is that they either continue to waste time and money maintaining code which is effectively unmaintainable, or they opt to live with what seems to be bad code, not touching it for fear of breaking it. To avoid this state of affairs, software developers need to be able to quanitify both the current level of software maintainability and the impact on it of any given change. This paper discusses the application of software metrics as a tool for quantifying code maintainability and, by extension, for making decisions. The first part of the discussion focuses on deriving a minimal set of easily calculated metrics which, when taken together, can produce a single-valued quantification (or index) of code maintainability. Case studies are then presented which serve to illustrate not only the degree to which software can degrade over time, but how this ‘maintainability index’ (MI) can be used to quantify maintainability and aid decision making. Finally, a methodology for making metric assessments readily available to software personnel is presented so that they can now easily integrate maintainability metrics into maintenance (and development) processes. As a result, the downward spiral of code degradation becomes at least recognizable, hopefully less precipitous, and perhaps avoidable entirely. © 1997 by John Wiley & Sons, Ltd. 相似文献
11.
基于继承图的面向对象软件复杂性度量研究 总被引：2，自引：0，他引：2
面向对象软件开发是一种新的可以减少成本、提高可用性和灵活性的高效的软件系统开发方法。复杂性度量在软件开发中起着非常重要的作用,它可减少整个开发周期的费用,但目前还没有成熟的用于面向对象软件复杂性的度量方法。文章首先通过继承图描述面向对象软件复杂性度量方法,然后讨论了单元重复继承算法,最后给出了具体实例。 相似文献
12.
Software inspections are an intensely people‐centric activity. Even though this is routinely recognized in industry, much of the research focuses on inspection mechanics. During three years of inspection experiments, even though the main purpose of the experiments was to investigate the effectiveness of a particular technique, the inspectors involved provided broad comments on many other aspects of inspections. Their comments were collected and organized into themes. These themes are presented here as a set of maxims that cover all the topics that the inspectors felt were important as they endeavoured to do good inspections. Copyright © 2004 John Wiley & Sons, Ltd. 相似文献
13.
In component‐based development, software systems are built by assembling components already developed and prepared for integration. To estimate the quality of components, complexity, reusability, dependability, and maintainability are the key aspects. The quality of an individual component influences the quality of the overall system. Therefore, there is a strong need to select the best quality component, both from functional and nonfunctional aspects. The present paper produces a critical analysis of metrics for various quality aspects for components and component‐based systems. These aspects include four main quality factors: complexity, dependency, reusability, and maintainability. A systematic study is applied to find as much literature as possible. A total of 49 papers were found suitable after a defined search criteria. The analysis provided in this paper has a different objective as we focused on efficiency and practical ability of the proposed approach in the selected papers. The various key attributes from these two are defined. Each paper is evaluated based on the various key parameters viz. metrics definition, implementation technique, validation, usability, data source, comparative analysis, practicability, and extendibility. The paper critically examines various quality aspects and their metrics for component‐based systems. In some papers, authors have also compared the results with other techniques. For characteristics like complexity and dependency, most of the proposed metrics are analytical. Soft computing and evolutionary approaches are either not being used or much less explored so far for these aspects, which may be the future concern for the researchers. In addition, hybrid approaches like neuro‐fuzzy, neuro‐genetic, etc., may also be examined for evaluation of these aspects. However, to conclude that one particular technique is better than others may not be appropriate. It may be true for one characteristic by considering different set of inputs and dataset but may not be true for the same with different inputs. The intension in the proposed work is to give a score for each metric proposed by the researchers based on the selected parameters, but certainly not to criticize any research contribution by authors. Copyright © 2012 John Wiley & Sons, Ltd. 相似文献
14.
In this paper, we investigate how to incorporate program complexity measures with a software quality model. We collect software complexity metrics and fault counts from each build during the testing phase of a large commercial software system. Though the data are limited in quantity, we are able to predict the number of faults in the next build. The technique we used is called times series analysis and forecasting. The methodology assumes that future predictions are based on the history of past observations. We will show that the combined complexity quality model is an improvement over the simpler quality only model. Finally, we explore how the testing process used in this development may be improved by using these predictions and suggest areas for future research. 相似文献
15.
形式描述是协议工程的基础。本文提出一种支持国际标准形式描述语言Estelle 描述生成的交互式生成方法。协议文本可划分为用有限状态自动机(FSM)描述的协议功能部分和用自然语言描述的动作部分。该方法把FSM 描述自动变换成Estelle 描述,把动作描述由自然语言交互地变换成Estelle 描述后,再组合得到完整的Estelle 描述。 相似文献
16.
17.
18.
19.
讨论在通信协议安全分析中形式描述技术的使用方法。重点研究在协议模型的基础上建立层次化的协议攻击行为模型的方法,对所建模型进行形式化验证和脆弱性分析,根据验证和分析结果提出防护措施,设计安全方案。给出Petri网建模实例,提出形式描述技术在通信协议安全分析中的一些其他应用。 相似文献
20.
Muhammad Anan Hossein Saiedian Jungwoo Ryoo 《Journal of Software: Evolution and Process》2009,21(1):1-18
Architecture‐based metrics can provide valuable information on whether or not one can localize the effects of modification (such as adjusting data flows or control flows) in software and can therefore be used to prevent the changes from adversely affecting other software components. This paper proposes an architecture‐centric metric using entropy for assessing structural dependencies among software components. The proposed metric is based on a mathematical model representing the maintainability snapshot of a system. The introduced architectural‐level metric includes measures for coupling and cohesion. From this model, the relative maintainability of a component, referred to as a maintainability profile, can be developed to identify architectural decisions that are detrimental to the maintainability of a system. Copyright © 2008 John Wiley & Sons, Ltd. 相似文献