No description available.

Program comprehension, i.e. to understand from its source code what a computer programdoes, is crucial for change and maintenance in software development. In this thesis, it is lookedfor innovative documentation techniques and tools that support program comprehension, butthat are also conform to agile values and principles – commonly, documentation is consideredcritical due to the agile value “working software over comprehensive documentation.”1 First,a research framework is developed that embodies detailed requisites for such techniques andtools. Apart from its internal use for examining techniques and tools subsequently obtainedfrom a literature search, this framework is intended to be likewise employed by software practitioners.Eventually, the findings of a series of survey studies conducted in an industrial softwareorganization for the primary purpose of evaluating the obtained techniques and tools are analyzed.Three innovative techniques that meet all requisites are revealed. These are regarded bypractitioners independently from the support of program comprehension as helpful for a changeimpact analysis conducted by non-developers. Therefore, a requisite deduced from the highestpriority in agile software development – customer satisfaction – is met. It says that a techniqueor tool has to directly induce a benefit for non-developer stakeholders besides the benefits forthem which are indirectly induced by the support of program comprehension, e.g. a potentiallyimproved source code quality. Further, the technique most beneficial for developers as well asfor non-developers among the three techniques is identified, which bases on design rationales– textual information related to the source code that states the reasons why a part of the programhas been implemented in a certain way. Secondarily, the studies revealed that the researchframework is difficult to understand for practitioners due to its unstructured form. / Program: Magisterutbildning i informatik

Thesis (M.S.)--University of Texas at El Paso, 2008. / Title from title screen. Vita. CD-ROM. Includes bibliographical references. Also available online.

Thesis (M.S.)--Mississippi State University. Department of Computer Science and Engineering. / Title from title screen. Includes bibliographical references.

Since humans first put pen to paper, people have critically assessed written work; thus, the assessment of documents per se is not new. Only recently, however, has the issue of formalized document quality assessment become feasible. Enabled by the rapid progress in computing technology, the prospect of an automated, formalized system of quality assessment, based on the presence of certain attributes deemed essential to the quality of a document, is feasible. The existing Objectives/Principles/Attributes Framework, previously applied to code assessment, is modified to allow application to documentation quality assessment. An automated procedure for the assessment of software documentation quality assessment and the development of a prototype documentation analyzer are described. A major shortcoming of the many quality metrics that are proposed in computer science is their lack of empirical validation. In pursuit of such necessary validation for the measures proposed within this thesis, a study is performed to determine the agreement of the measures rendered by Docalyze with those of human evaluators. This thesis demonstrates the applicability of a quality assessment framework to the documentation component of a software product. Further, the validity of a subset of the proposed metrics is demonstrated. / Master of Science

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / In the documentation of software architecture, it must be considered two relevant points: i) the architecture is composed by several visions, and ii) each vision identifies a set of components and interactions which allows a better understanding between developers and system programmers. The documentation of the components, when treating reusability, must present a set of information concerning its functionality and applicability in order to adapt them in applications of same domain. When we think of interaction among components, the information concerning the communication messages must be well identified so that the process of working may be clearly understood. This work shows the creation of a catalog of documentation patterns for the architecture of image processing and analysis systems approaching on the concept of design patterns and architecture visions of UML which will be used as the base for designing the Patterns. Through its use, the developers will be more sure of which is necessary to document and safer when reusing components previously tested and documented. It is also shown in this work the development of templates environment of the Patterns in the tool MoinMoinWiki aiming at creating a scenery for collaborative work and also a repository of information on documentation of systems architecture and frameworks within image domain. / Na documentação da arquitetura de software deve ser considerado dois pontos relevantes: i) a arquitetura é composta por várias visões, e ii) cada visão identifica um conjunto de componentes e interações, permitindo melhor compreensão entre desenvolvedores e projetistas do sistema. A documentação dos componentes, quando se tratando de reusabilidade, deve apresentar um conjunto de informações referente a sua funcionalidade e aplicabilidade a fim de adaptá-los em aplicações de mesmo domínio. Quando pensando em interação entre componentes, as informações relacionadas às mensagens de comunicação devem ser bem identificadas, para que o processo de funcionamento seja claramente entendido. Este trabalho apresenta a criação de um catálogo de Padrões de Documentação da Arquitetura de sistemas e frameworks para processamento e análise de imagens, abordando o conceito de design patterns e visões arquiteturais da UML, as quais servirão de base para elaboração dos padrões. Através do uso desses, os desenvolvedores sentirão mais clareza do que é necessário documentar e mais seguros em reusar componentes previamente testados e documentados. Apresenta-se também neste trabalho, o desenvolvimento de um ambiente de templates dos Padrões na ferramenta MoinMoinWiki, com o objetivo de criar um cenário para o trabalho colaborativo, e também um repositório de informações sobre a documentação da arquitetura de sistemas e frameworks no domínio de imagens.

Software developers, maintainers, and testers rely on documentation to understandthe code they are working with. However, software documentation is perceivedas a waste of effort because it is usually outdated. How documentation evolvesthrough a set of releases may show whether there is any relationship between timeand quality. The results could help future developers and managers to improvethe quality of their documentation and decrease the time developers use to analyzecode. Previous studies showed that documentation used to be scarce and low inquality, thus, this research has investigated different variables to check if the qualityof the documentation changes over time. Therefore, we have created a tool thatwould extract and calculate the quality of the comments in code blocks, classes,and methods. The results have agreed with the previous studies. The quality of thedocumentation is affected to some extent through the releases, with a tendency todecrease.

No description available.

International Telemetering Conference Proceedings / October 17-20, 1988 / Riviera Hotel, Las Vegas, Nevada / Software development is becoming less an art form and more an engineering discipline. Methods of software development which leave as little as possible to chance are constantly being sought and documented. However, the gap between what is written and what is actually applied is usually quite wide. The only way this gap can be narrowed is through practical application of these very detailed and complex methods. Since it is unlikely that the complexity of these methods will be reduced, automation must be employed wherever possible in the software development process. This paper addresses the successful development of software for the Navy's Realtime Telemetry Processing System III (RTPS III) using practical application of existing methodology in conjunction with a Computer Aided Software Engineering (CASE) tool. Based on this experience, the conclusion presents implications affecting software development the 1990s.

Broadly, agile software development is an approach where code is frequently built, tested and shipped, leading to short release cycles. Extreme version is the DevOps approach where the development, testing and deployment pipelines are merged and software is continuously tested and updated. In this context our work focuses on identifying spots where the participants should be more aware of the performance and offers approaches and tools to improve their awareness with the ultimate goal of producing better software in shorter time. In general, the awareness is raised by testing, documenting, and monitoring the performance in all phases of the development cycle. In this thesis we (1) show a framework for writing performance tests for individual components (e.g. libraries). The tests capture and codify assumptions about the performance into runnable artifacts that simplify repeatability and automation. For evaluation of the performance tests we (2) propose new methods, which can automatically detect performance regressions. These methods are designed with inherent variation of performance data in mind and are able to filter it out in order to detect true regressions. Then we (3) reuse the performance tests to provide the developers with accurate and up-to-date performance API documentation that steer them...