Comparison Study and Review on Object-Oriented Metrics

The best elucidations to software development problems are regularly touted as object-oriented processes. The popularity of object-oriented design metrics is essential in software engineering for measuring the software complexity, estimating size, quality and project efforts. There are various approaches through which we can find the software cost estimation and predicates on various kinds of deliverable items. Object-oriented metrics assures to reduce cost and the maintenance effort by serving as early predictors to estimate software faults. Such an early quantification augments the quality of the final software. This paper reviews object-oriented metrics. A comparison table is maintained via which we can analyze the difference between all the object-oriented metrics effectively

Evaluating the GO Programming Language with Design Patterns

GO is a new object-oriented programming language developed at Google by Rob Pike, Ken Thompson, and others. GO has the potential to become a major programming language. GO deserves an evaluation. Design patterns document reoccurring problems and their solutions. The problems presented are programming language independent. Their solutions, however, are dependent on features programming languages provide. In this thesis we use design patterns to evaluate GO. We discuss GO features that help or hinder implementing design patterns, and present a pattern catalogue of all 23 Gang-of-Four design patterns with GO specific solutions. Furthermore, we present GoHotDraw, a GO port of the pattern dense drawing application framework JHotDraw. We discuss design and implementation differences between the two frameworks with regards to GO

進化型組込みソフトウェアにおける継続的なメンテナンス性向上手法に関する研究

近年，技術革新スピードが加速し，市場のニーズは短期間で変化し，技術の陳腐化，急速な製品価値低下が起きている．このような変化に対応し，継続的に開発を行うソフトウェアを“進化型組込みソフトウェア”と定義する．従来の計画的な開発手法や適応的な開発手法を進化型組込みソフトウェアに適用しても，開発が進むにつれ，メンテナンス性が低下することで，全体的なリファクタリングが必要になる．そこで，本研究では，進化型組込みソフトウェアにおいて，メンテナンス性を継続的に向上させる手法を提案する．本手法は，進化型組込みソフトウェアを開発する上で必要となる3つの定義した要件に対応する拡張性可視化手法，拡張性強化手法，拡張性評価手法で構成される．さらに，提案手法を実際の製品ソースコードに対し，継続的に適用することで，対象ソフトウェアのメンテナンス性が向上することを確認した．電気通信大学201