共查询到18条相似文献,搜索用时 187 毫秒
1.
功能点分析(FPA)本身只能度量系统静态的方面,不能考虑到对象的交互性和对象的行为。基于FPA,结合面向对象系统的特点,提出了一种面向对象方法的功能点,完成了从FPA方法到面向对象方法概念上的映射和度量规则上的映射,并给出了该方法具体的度量过程,为Web应用的度量奠定了坚实的理论基础。 相似文献
2.
基于Web应用的全面功能点的改进 总被引:1,自引:0,他引:1
全面功能点(FFP)是一种应用广泛且使用方便的软件功能规模度量(FSM)方法,但其方法本身只能度量系统静态的方面,不能考虑到对象的交互性和对象的行为。根据COSMIC-FFP的度量元素和Web应用的结构,对COSMIC-FFP软件模型进行了改进,列出了针对Web应用的度量规则,并给出了实例说明了这些规则的使用。 相似文献
3.
4.
针对功能点分析(FPA)方法因缺少精确化定义而导致度量结果与实际之间有一定偏差的问题,基于B方法对FPA的度量规则进行形式化定义,即为功能点计算提供一个明确的定义。实例应用表明,把B方法应用到软件度量中,能够提高软件项目管理的效率,为软件功能规模的自动化度量奠定基础。 相似文献
5.
基于过程的软件规模度量方法的研究 总被引:1,自引:1,他引:0
功能点分析是一种广泛使用的度量软件功能大小的方法,它不依赖于实现语言,度量出来的结果也可以在不同的开发过程之间进行比较。代码行度量需要对系统的内部有准确的了解。它是对软件产品(特别是编码)规模最直接的描述。本文综合了这两种规模度量方法的优点,针对一个多层MIS系统的迭代开发过程建立了一个规模度量模型,并将其应用到实际当中,使得项目开发者能够在过程中有效的把握进度制定合理的项目计划。 相似文献
6.
在软件工程监理的早期,单凭监理人员的经验对系统进行准确有效的估算几乎是不可能的.功能点分析法(FunctionPoint Analvsis)是一种广泛使用的度量软件功能大小的方法,它不依赖于某种实现语言,度量出来的结果也可以在不同的开发过程之间进行比较.文章对基于FPA的软件工程监理方法进行了研究,并对其做了应用分析.监理人员使用该方法能在项目的早期估算出软件系统的规模及成本,为监理方案的制定提供依据. 相似文献
7.
8.
9.
规模度量是软件项目管理的关键,其度量的准确性直接关系到软件项目的成败。针对传统FPA方法中复杂度等级划分不连续性的问题,提出一种改进的复杂度权值计算方法。该方法利用模糊理论分析功能要素的复杂度,首先以DET和RET作为输入变量,以复杂度权值作为输出变量,建立模糊推理系统;然后根据FPA中复杂度和功能点数量的转换关系,设置模糊推理规则,并利用该规则确定复杂度权值。研究结果表明,这种模糊推理的方法可以消除不同复杂度等级之间的断层,从而使软件功能点的估算结果更加准确。 相似文献
10.
针对软件开发的规模度量模型和方法的研究,提出了基于用例与功能点相结合的软件规模度量方法,并对度量过程进行了应用分析。通过验证,采用用例功能点方法进行软件规模度量的结果与实际规模相比误差小,其估算结果优于一般的规模估算方法。 相似文献
11.
A functional size measurement method for object-oriented conceptual schemas: design and evaluation issues 总被引:1,自引:0,他引:1
Functional Size Measurement (FSM) methods are intended to measure the size of software by quantifying the functional user requirements of the software. The capability to accurately quantify the size of software in an early stage of the development lifecycle is critical to software project managers for evaluating risks, developing project estimates and having early project indicators. In this paper, we present OO-Method Function Points (OOmFP), which is a new FSM method for object-oriented systems that is based on measuring conceptual schemas. OOmFP is presented following the steps of a process model for software measurement. Using this process model, we present the design of the measurement method, its application in a case study, and the analysis of different evaluation types that can be carried out to validate the method and to verify its application and results. 相似文献
12.
Juan J.CUADRADO-GALLEGO Alain ABRAN Pablo RODRíGUEZ-SORIA Miguel A.LARA 《浙江大学学报:C卷英文版》2014,15(3):161-173
The use of functional size measurement (FSM) methods in software development organizations is growing during the years. Also, object oriented (OO) techniques have become quite a standard to design the software and, in particular, Use Cases is one of the most used techniques to specify functional requirements. Main FSM methods do not include specific rules to measure the software functionality from its Use Cases analysis. To deal with this issue some other methods like Kramer's functional measurement method have been developed. Therefore, one of the main issues for those organizations willing to use OO functional measurement method in order to facilitate the use cases count procedure is how to convert their portfolio functional size from the previously adopted FSM method towards the new method. The objective of this research is to find a statistical relationship for converting the software functional size units measured by the International Function Point Users Group (IFPUG) function point analysis (FPA) method into Kramer-Smith's use cases points (UCP) method and vice versa. Methodologies for a correct data gathering are proposed and results obtained are analyzed to draw the linear and non-linear equations for this correlation. Finally, a conversion factor and corresponding conversion intervals are given to establish the statistical relationship. 相似文献
13.
14.
15.
《Information and Software Technology》2013,55(10):1796-1809
BackgroundThe measurement of Function Points is based on Base Functional Components. The process of identifying and weighting Base Functional Components is hardly automatable, due to the informality of both the Function Point method and the requirements documents being measured. So, Function Point measurement generally requires a lengthy and costly process.ObjectivesWe investigate whether it is possible to take into account only subsets of Base Functional Components so as to obtain functional size measures that simplify Function Points with the same effort estimation accuracy as the original Function Points measure. Simplifying the definition of Function Points would imply a reduction of measurement costs and may help spread the adoption of this type of measurement practices. Specifically, we empirically investigate the following issues: whether available data provide evidence that simplified software functionality measures can be defined in a way that is consistent with Function Point Analysis; whether simplified functional size measures by themselves can be used without any appreciable loss in software development effort prediction accuracy; whether simplified functional size measures can be used as software development effort predictors in models that also use other software requirements measures.MethodWe analyze the relationships between Function Points and their Base Functional Components. We also analyze the relationships between Base Functional Components and development effort. Finally, we built effort prediction models that contain both the simplified functional measures and additional requirements measures.ResultsSignificant statistical models correlate Function Points with Base Functional Components. Basic Functional Components can be used to build models of effort that are equivalent, in terms of accuracy, to those based on Function Points. Finally, simplified Function Points measures can be used as software development effort predictors in models that also use other requirements measures.ConclusionThe definition and measurement processes of Function Points can be dramatically simplified by taking into account a subset of the Base Functional Components used in the original definition of the measure, thus allowing for substantial savings in measurement effort, without sacrificing the accuracy of software development effort estimates. 相似文献
16.
17.
18.
现代安全关键系统的功能实现越来越依赖于软件,这导致软件的安全性对系统安全至关重要,而软件的复杂性使得采用传统安全性分析方法很难捕获组件交互过程带来的危险。为保证安全关键系统的安全性,提出一种基于系统理论过程分析(STPA)的软件安全性验证方法。在安全控制结构基础上,通过构建带有软件过程模型变量的过程模型,细化分析危险行为发生的系统上下文信息,并以此生成软件安全性需求。然后通过设计起落架控制系统软件,采用模型检验技术对软件进行安全性验证。结果表明,所提方法能够在系统级层面有效识别出软件中潜在的危险控制路径,并可以减少对人工分析的依赖。 相似文献