【作者】 贺青春；

【导师】 叶柏龙； 张伟明；

【作者基本信息】 湖南大学 ， 软件工程， 2008， 硕士

【摘要】 解决软件危机需要技术措施,更需要管理措施,而软件规模估计是整个软件项目管理的基础,所以规模估计对解决软件起着重要的作用。目前,软件业界比较流行的软件规模估计方法有代码行法、功能点分析法和预测对象点法,它们各自有着各自的优点和缺点,但是没有一种方法能得出令人满意的估计结果。在面向对象的软件开发方法和UML十分流行的时代,面向对象软件的规模估计方法相对更加落后。本文在深入分析了面向对象软件的开发过程之后,根据软件规模度量和估计的关系,找到了一种在需求分析之初就能较为准确地估计出软件规模的方法——基于用例的对象点法(简称用例对象点法)。并且这种方法可以和CASE工具Microsoft Visio 2003有机结合起来,通过Java技术和XML技术的运用,使用例对象点法工具化成为可能。根据软件度量准则和面向对象软件度量的惯例,找出用例对象点法的度量元素,结合税库行横向联网项目实例,论证了每一个度量元素对规模的最后度量结果的影响。综合考虑了每个度量元素的影响之后,设计出用例对象点法的估算公式和估计步骤,并且从理论和实践两方面论证了用例对象点法的准确性和精确性。在大规模的软件开发过程中,要用手工完成用例对象点法的软件规模估计过程是很困难的,因此作者在设计好用例对象点法的估算公式和估计步骤之后,开发出它的辅助工具。本工具以项目用例图作为输入,使用者只须输入每一对最底层用例和Actor之间的误差之后,即可直接算出整个用例对象点数。为了论证用例对象点法具有一定的先进性,作者将亲自开发的几个项目(岳阳县电信局话费查询系统、华容县电信局计费系统、长沙市商业银行稽核监控系统、税库行横向联网系统)进行了规模估计方面的比较,得出了用例对象点法比功能点法更加具有可操作性和准确性的结论。更多还原

【Abstract】 Solving the crisis of software need more management mesure than technology mesure.But software project management bases on estimating of the software size .So the size estimating is important to solving the crisis of software.Now the size estimating methods such as coding lines, function points analysis and prognosticate object points are popular in software industry, they have their respective advantages and shortages, but no one can make a satisfying result of size estimating.In the time of OO(object-oriented) developing method and UML very popular,OO software size estimating is very undeveloped.This article according to the relation of size measurement and size estimating finds a size estimating method of OO software in the begin phase of requirement analysis after researching the process of OO software developing.And this method names Object Points Method Based on Use Cases,can be combined with the case tool--Microsoft Visio 2003,then make it possible to develop an aid-tool for this method by utilizing the technology of Java and UML.According to the guide line of software measurement and the tradition of OO software measurement, the article finds the measurement elements, combines with the TIPS project, shows software size impacting of every element, then designs the estimating formula and steps of Object Points Method Based on Use Cases and testifies it from theory and practice.In the process of developing large size software it is difficult to estimate software size manually by using Object Points Method Based on Use Cases, so the writer develops an aid-tool. Input use cases diagram and the errors of every pair of bottom use case and actor, the tool can make out object points automatically.To prove that this method is advanced, the writer contrasts this method with other software size estimating methods, draws a conclusion that the Object Points Method Based on Use Cases has more maneuverability and veracity than other Methods.更多还原