Khan, Tahmina Zaman · BRAC University Institutional Repository (BRAC University) · 2010
This thesis report is submitted in partial fulfillment of the requirements for the degree of Bachelor of Science in Computer Science and Engineering, 2006.
Cited by 0Open access
Brigit van Loggem · 2014
This paper describes a desk study in which a user manual dating from 1925, describing how to operate a table loom, was verified for conformance to an ISO standard that lists requirements for software user documentation and was last revised in 2008. A remarkably high degree of conformance was established. It is discussed whether this is coincidental, or more fundamentally related to the way in which the documentation of software tools is regarded as quantitatively rather than qualitatively different from the documentation of physical tools. The paper concludes by making a case for academic research resulting in guidelines for software documentation that take into account the specific nature of software, and the specific problems that users encounter when working with software.
Cited by 12
Preeti Rastogi, M. Eng, Preeti Rastogi et al. · 2008
ii Precise mathematical documentation plays a crucial role in safety critical, mission critical, and finance critical software where the cost of failure is very high either in terms of money or human life. Good documentation is an important component of software and is absolutely necessary for maintenance. Tabular notation advocated by Parnas et al. has been found to be more readable and easy to understand when compared to conventional mathematical representations. Tables can sometimes be complex and difficult to comprehend. In such cases “specialization ” can simplify them. Some tables can be simplified without loss of generality. For others specialization may be used. Specialization is a technique that reduces the domain for which the expression is valid. For tabular expressions, specialization may allow the removal of rows and/or columns when the domain of predicate (condition) sub-expressions is outside the domain under consideration. User defined constraints narrow the domain under consideration. Specialization
Cited by 0
D'Amico, T E, Michel, H · CERN Document Server (European Organization for Nuclear Research) · 1979
Cited by 0Open access
Johannes Sametinger · 1997
Cited by 6
American Society of Civil Engineers eBooks · 2000
Cited by 14
d'Amico, E, Michel, H · CERN Document Server (European Organization for Nuclear Research) · 1979
Cited by 0
Inpatient Quality Indicators · 2002
The value of information on health care quality has never been so widely recognized; yet many organizations lack the resources and/or expertise to build a quality information program from the ground up. Recognizing this, the AHRQ Quality Indicators were developed specifically to meet the short-term needs for information on health care quality using standardized, user-friendly methods and existing sources of data. This module of the AHRQ Quality Indicators was designed to capitalize on the availability of administrative data on inpatient stays to produce information for Inpatient Quality Indicators (IQIs). These measures include: volume of certain intensive, high-technology, or highly complex procedures for which evidence suggests that institutions performing more of these procedures may have better outcomes; mortality for inpatient procedures and for inpatient conditions; and utilization indicators which examine procedures whose use varies significantly across hospitals and for which questions have been raised about overuse, underuse, or misuse. This document is the software documentation for the Inpatient Quality Indicators software Version 4.1, which is provided on the AHRQ Web site. The software was developed in SAS, for use on a personal computer. AHRQ's goal, by making this tool publicly available, is to assist users in producing information on health care quality more cost effectively. Details on the development of the Inpatient Quality Indicators can be found in Guide to Inpatient Quality
Cited by 0
P. A. Comella · NASA STI Repository (National Aeronautics and Space Administration) · 1973
A tutorial in the documentation of computer software is presented. It presents a methodology for achieving an adequate level of documentation as a natural outgrowth of the total programming effort commencing with the initial problem statement and definition and terminating with the final verification of code. It discusses the content of adequate documentation, the necessity for such documentation and the problems impeding achievement of adequate documentation.
Cited by 1Open access
Karen Paffendorf, Diane L. Souvaine · 1998
This paper describes automating the documentation of a software control structure. The code is preprocessed to take the form of directed graphs. The following tools are used for drawing the directed graphs: DaVinci, Graphlet, Graphviz, and VCG. The tools are described and compared. 1 INTRODUCTION: During the early 1990's I worked for International Business Machines (IBM) on a hierarchical database, Information Management System (IMS), which was initially developed in the late 1960's. One of my responsibilities was to maintain the logger. The logger maintained copies of the information needed for database recovery in case of various assortments of hardware failure. Jack Howe implemented a system which reused blocks of code in different error scenarios for the logger. Rather than pay the time and space penalty of subroutines or the space penalty of macros, he and Ron Peterson developed a system for transferring control between the blocks of code. He documented this http://www.cs.rutg...
Cited by 0
Kim H. Pries, Jon M. Quigley · 2011
Cited by 3
Pieter van der Spek, Steven Klusener, Piërre van de Laar · Embedded systems · 2010
Cited by 2
Diane L. Souvaine, Paendorf, Karen · View · 1998
This paper describes automating the documentation of a software control structure. The code is preprocessed to take the form of directed graphs. The following tools are used for drawing the directed graphs: DaVinci, Graphlet, Graphviz, and VCG. The tools are described and compared.
Cited by 1Open access
Robert L. Glass · 1989
When technical writers speak of software documentation, they usually speak of user manuals. Certainly there is reason for them to. User manuals produced by software people (and I am proud to count myself as a software person!) have often been so bad that a whole industry has sprung up to publish books containing information needed to supplement traditional developer-written user manuals. Technical writers have played a key role in that industry.
Cited by 13
Sandesh Lamichhane, Hunter Brogna, Aiden Hamade et al. · 2025
Cited by 1Open access
Joseph Petito · Journal of Technical Writing and Communication · 1974
In the Spring 1973 of the Journal, Mr. Petito presented two closely related lectures in note form on the development of manuals, as given at an AMA seminar. The present paper develops computer software documentation with reference to types of documentation, documentation library, and documentation standards.
Cited by 1
1984
Cited by 0
Martina Černá · Digital Repository (National Repository of Grey Literature) · 2010
This bachelor thesis is focused on software development documentation. At the beginning, main sorts of software documentation are listed and described. The main point of this bachelor thesis is a description and comparsion of how software development documentation is defined in standards issued by International Organization for Standardization and International Electrotechnical commision and in CMMI for Development. The final part contains a set of the most important general rules for creating software documentation.
Cited by 0
De Bruin, Jonathan, Ferdinands, Gerbrich, Harkema, Albert et al. · Zenodo (CERN European Organization for Nuclear Research) · 2020
This document contains detailed information for version 0.15 of the ASReview software. For more information, see https://github.com/asreview/asreview.
Cited by 0Open access
Jassim, Mostafa, Messadi, Ines · Digitale Bibliothek Braunschweig (Verbundzentrale Göttingen (VZG)) · 2023
Cited by 0Open access