Monitoring an Ada software development

Basili, Victor R.; Chang, Shih; Gannon, John D.; Katz, Elizabeth E.; Panlilio-Yap, Nikki; Ramsey, Connie Loggia; Zelkowitz, Marvin V.; Bailey, John; Kruesi, Elizabeth; Sheppard, Sylvia B.

doi:10.1145/998401.998402

Cited by 3 publications

(4 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this experiment, the Ada design was shown to be different to a significant degree from the FORTRAN design. This result differs from that reported in Reference 46 for another monitored Ada development project in a different environment.…”

Section: Discussioncontrasting

confidence: 99%

Measuring Software Design

Munson¹

2005

Software Specification and Design

View full text Add to dashboard Cite

The goals of the SEL are (1) to understand the software development process in the GSFC environment: (2) to measure the effect of various methodologies, tools, and models on this process; and (3) to identify and then to apply successful development practices. ABSTRACTAn extensive series of studies of software design measures conducted by the Software Engineering Laboratory is described. Included are the objectives and results of the studies, the method used to perform the studies, and the problems encountered. The document should be useful to researchers planning similar studies as well as to managers and designers concerned with applying quantitative design measures.

show abstract

Section: Discussioncontrasting

confidence: 99%

Measuring Software Design

Munson¹

2005

Software Specification and Design

View full text Add to dashboard Cite

show abstract

“…Basili et al [1] monitored the changes made during the development of an Ada project, which involved the redesign and reimplementation of a portion of a satellite ground control system, and observed that requirements, design, and code changes accounted for 7%, 32%, and 61% of the changes. In addition, 57% of the changes were fault corrections, and 23% were improvements for clarity, maintainability and readability.…”

Section: Related Workmentioning

confidence: 99%

“…These four questions capture the goal of the study. 1. What is the frequency distribution of the pre-release source code changes in the case under study?…”

Section: Introductionmentioning

confidence: 99%

A Case Study of Source Code Evolution

Ghazarian

2009

2009 13th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Obtaining an accurate characterization of pre-release changes, especially those related to fault corrections, can give indications for the quality of the software development process and its product. The resulting indications can then be leveraged to identify areas for quality improvement within software development organizations. Towards this objective, we studied the evolution of the source code modules in an industrial enterprise resource planning software system spanning a time period of two years from the initial creation of the source code modules to the release of the software product. In this paper, we describe our case study process, and present the frequency distributions of pre-release changes and faults along with lessons learned from the case study. Overall, we found that (a) only 22% of pre-release changes contribute new functionality to the system under development; the remaining majority of the prerelease changes are either fault corrections or code cleanups (b) over 72% of pre-release faults are propagated from upper-stream requirements and design activities (c) fault classes that are the target of most fault detection tools have a low frequency.

show abstract

“…Of the several experimental Ado codings that have been carried out, the effort reported by Basili etai [ 1] seems to be typical. The study was aimed at investigating the "problems with training programmers in Ado and its as~ciated design and programming methods and ... [with] redeveloping current systems in Ada."…”

Section: Some Problems Concerning Ada Educationmentioning

confidence: 99%

The impact of Ada on software project organization

Goerner

1985

Proceedings of the Second Annual Washington Ada Symposium on Ada Ada in the Mainstream: Applications and Education - WADAS '85

View full text Add to dashboard Cite

The impact of Ado adoption on software productivity, quality, and cost is discussed. Six fundamental problems revolving around the topic of Ado training are identified and their consequences presented. The conclusion is drawn that the supply of truly Ado-competent software engineers will continue to be small despite training efforts currently planned. Oiven this situation, it is deduced that an essential change in software project organization is required to prevent the serious degradation of software productivity, quality, and cost during the first decade or more of the Ado era. A software project organization strategy, called the AdaTeam, which capitalizes on the personnel available and which integrates training and quality assurance is presented.

show abstract

Monitoring an Ada software development

Cited by 3 publications

References 2 publications

Measuring Software Design

Measuring Software Design

A Case Study of Source Code Evolution

The impact of Ada on software project organization

Contact Info

Product

Resources

About