國立虎尾科技大學 |

Measuring Software Complexity Differences with the Analytical Hierarchy Process.

紀錄類型:	書目-語言資料,手稿 : Monograph/item
正題名/作者:	Measuring Software Complexity Differences with the Analytical Hierarchy Process./
作者:	Guilbault, Noah.
面頁冊數:	1 online resource (160 pages)
附註:	Source: Dissertation Abstracts International, Volume: 79-05(E), Section: A.
Contained By:	Dissertation Abstracts International79-05A(E).
標題:	Management. -
電子資源:	click for full text (PQDT)
ISBN:	9780355590890

Measuring Software Complexity Differences with the Analytical Hierarchy Process.
Guilbault, Noah.

Measuring Software Complexity Differences with the Analytical Hierarchy Process. - 1 online resource (160 pages)

Source: Dissertation Abstracts International, Volume: 79-05(E), Section: A.

Thesis (D.Engr.)

Includes bibliographical references

Software systems can become overly complex throughout the software development process, leading to increased error rates and failures. This praxis improves on the measurement of complexity, the first step in resolving this problem. Most software development technologies allow for incorporation of ever more interactive, error-prone, and interwoven designs that can introduce problems and increase the complexity of a software baseline. Because software typically holds latent defects, increasing the complexity of the software source code creates new adverse risks that undermine the usability, understandability, and reliability of software products. Despite following best practices during the software engineering process, the introduction of change to the software baseline can unnecessarily increase the complexity of software source code.

Electronic reproduction.
Ann Arbor, Mich. :
ProQuest,
2018

Mode of access: World Wide Web

ISBN: 9780355590890Subjects--Topical Terms:

558618
Management.
Index Terms--Genre/Form:

554714
Electronic books.

Measuring Software Complexity Differences with the Analytical Hierarchy Process.
LDR:04872ntm a2200385Ki 4500 001 910119
005 20180511093035.5
006 m o u
007 cr mn||||a|a||
008 190606s2018 xx obm 000 0 eng d
020 $a 9780355590890
035 $a (MiAaPQ)AAI10690017
035 $a (MiAaPQ)gwu:13915
035 $a AAI10690017
040 $a MiAaPQ $b eng $c MiAaPQ
099 $a TUL $f hyy $c available through World Wide Web
100 1 $a Guilbault, Noah. $3 1181206
245 1 0 $a Measuring Software Complexity Differences with the Analytical Hierarchy Process.
264 0 $c 2018
300 $a 1 online resource (160 pages)
336 $a text $b txt $2 rdacontent
337 $a computer $b c $2 rdamedia
338 $a online resource $b cr $2 rdacarrier
500 $a Source: Dissertation Abstracts International, Volume: 79-05(E), Section: A.
500 $a Advisers: Alan K. Gideon; Gina Guillaume-Joseph.
502 $a Thesis (D.Engr.) $c The George Washington University $d 2018.
504 $a Includes bibliographical references
520 $a Software systems can become overly complex throughout the software development process, leading to increased error rates and failures. This praxis improves on the measurement of complexity, the first step in resolving this problem. Most software development technologies allow for incorporation of ever more interactive, error-prone, and interwoven designs that can introduce problems and increase the complexity of a software baseline. Because software typically holds latent defects, increasing the complexity of the software source code creates new adverse risks that undermine the usability, understandability, and reliability of software products. Despite following best practices during the software engineering process, the introduction of change to the software baseline can unnecessarily increase the complexity of software source code.
520 $a Software metrics are critical to fault prediction models that seek to improve the quality of software products by predicting the location of bugs in the source code. Measuring software complexity assists software developers by providing insights into projects by identifying areas of source code baseline that have potential issues with reliability, readability, understandability, and implementation. However, producing a set of software measurement data is not sufficient for making a reliable decision. Interpretation of the results of complexity measurements can be problematic because an accurate understanding of the numerical values that characterize specific software attributes such as coupling, reliability, and overriding can be difficult.
520 $a This praxis develops a technique for identifying the parts of a software baseline that experience the most complex changes between successive versions. This objective is vii accomplished using a software complexity measurement technique that combines multiple aspects of the source code to quantify the variations in complexity of a software baseline between succeeding revisions. Building on prior successful efforts, this praxis develops a model for locating the portions of a software baseline that have undergone the most complex changes. The analytical hierarchy process (AHP) is used to combine the complexity metrics of number of metrics (NOM), number of children (NOC), coupling between objects (CBO), level of cohesion metrics (LCOM), weighted method complexity (WMC), and number of methods overridden (NMO) to determine the most complexly changed files for four open-sourced projects from the Apache Commons family of projects including IO, Net, Compression, and Discovery.
520 $a This praxis observed that the AHP process can be reliably applied to the set of six metrics used for the projects evaluated and produced AHP consistency ratings within the AHP process recommended ranges. Aggregate complexity values were successfully calculated for each source code file within the projects, and the most complexly modified files were identified. Several threats to the validity of the findings of this empirical study prompt the suggestion that the conclusions of this praxis should be treated as indications toward a pragmatic remedy to the problem of software complexity measurement between software versions rather than a final conclusive technique. To improve the reliability and the generalizability of this study, similar empirical studies should be conducted, using relatively large commercial systems developed in other programming languages such as C++, as well as selected from different domains.
533 $a Electronic reproduction. $b Ann Arbor, Mich. : $c ProQuest, $d 2018
538 $a Mode of access: World Wide Web
650 4 $a Management. $3 558618
650 4 $a Computer science. $3 573171
655 7 $a Electronic books. $2 local $3 554714
690 $a 0454
690 $a 0984
710 2 $a ProQuest Information and Learning Co. $3 1178819
710 2 $a The George Washington University. $b Engineering Management. $3 1179162
773 0 $t Dissertation Abstracts International $g 79-05A(E).
856 4 0 $u http://pqdd.sinica.edu.tw/twdaoapp/servlet/advanced?query=10690017 $z click for full text (PQDT)