Search

The article presents rules to make software that is impactful and usable by using software engineering best practices. It mentions that modern integrated development environments will frequently generate documentation strings automatically as researchers write code, that takes the burden of the need to remember to write comments. It states that people more probably to use it as part of their research if they can quickly start playing with the tool.

Not only system assurance drives a need for semantically richer relationships across various artifacts, work products, and items of information than are implied in the terms “trace and traceability” as used in current standards and textbooks. This paper deals with the task of working out artifacts in software and system development, their representation, and the analysis and documentation of the relationships between their logical contents—herein referred to as tracing and traceability; this is a richer meaning of traceability than in standards like IEEE STD 830. Among others, key tasks in system development are as follows: capturing, analyzing, and documenting system-level requirements, the step to functional system specifications, the step to architectures given by the decomposition of systems into subsystems with their connections and behavioral interactions. Each of these steps produces artifacts for documenting the development, as a basis for a specification and a design rationale, for documentation, for verification, and impact analysis of change requests. Crucial questions are how to represent and formalize the content of these artifacts and how to relate their content to support, in particular, system assurance. When designing multi-functional systems, key artifacts are system-level requirements, functional specifications, and architectures in terms of their subsystem specifications. Links and traces between these artifacts are introduced to relate their contents. Traceability has the goal to relate artifacts. It is required for instance in standards for functional system safety such as the ISO 26262. An approach to specifying semantic relationships is shown, such that the activity of creating and using (navigating through) these relationships can be supported with automation. [ABSTRACT FROM AUTHOR]

Although digital technology has advanced the visualization of treatment planning and rehabilitation in prosthodontics, the field of maxillofacial prosthetics is in vital need of an accessible document for exchange of interactive three-dimensional (3D) model visualization without requiring installation of any additional software. This article introduces a 3D data documentation method for effective interactive digital visualization in maxillofacial prosthetics using a portable documentation format (PDF). [ABSTRACT FROM AUTHOR]

Do you need to master embedded indexing before your clients ask for it? And what are the pros, cons and practicalities of doing so? Lucie Haskins, who teaches and practices embedded indexing, offers an authoritative overview. [ABSTRACT FROM AUTHOR]

The business capabilities of modern enterprises crucially rely on the enterprises' information systems and underlying IT infrastructure. Hence, optimization of the business-IT alignment is a key objective of Enterprise Architecture Management (EAM). To achieve this objective, EAM creates, maintains and analyzes a model of the current state of the Enterprise Architecture. This model covers different concepts reflecting both the business and the IT perspective and has to be constantly maintained in response to ongoing transformations of the enterprise. In practice, EA models grow large and are difficult to maintain, since many stakeholders from various backgrounds have to contribute architecture-relevant information. EAM literature and two practitioner surveys conducted by the authors indicate that EA model maintenance, in particular the manual documentation activities, poses one of the biggest challenges to EAM in practice. Current research approaches target the automation of the EA documentation based on specific data sources. These approaches, as our systematic literature review showed, do not consider enterprise specificity of the documentation context or the variability of the data sources from organization to organization. The approach presented in this article specifically accounts for these factors and presents a situational method for EA documentation. It builds on four process-supported documentation techniques which can be selected, composed and applied to design an organization-specific documentation process. The techniques build on a meta-model for EA documentation, which is implemented in an EA-repository prototype that supports the configuration and execution of the documentation techniques. We applied our documentation method assembly process at a German insurance company and report the findings from this case study in particular regarding practical applicability and usability of our approach. [ABSTRACT FROM AUTHOR]

System modelling using Unified Modelling Language (UML) is the task that should be solved for software development. The more complex software becomes the higher requirements are stated to demonstrate the system to be developed, especially in its dynamic aspect, which in UML is offered by a sequence diagram. To solve this task, the main attention is devoted to the graphical presentation of the system, where diagram layout plays the central role in information perception. The UML sequence diagram due to its specific structure is selected for a deeper analysis on the elements' layout. The authors research represents the abilities of modern UML modelling tools to offer automatic layout of the UML sequence diagram and analyse them according to criteria required for the diagram perception. [ABSTRACT FROM AUTHOR]

Background: Endoscopic documentation software can generate research data on large numbers of subjects automatically. There are increasing numbers of published studies based on endoscopic databases such as the Clinical Outcomes Research Initiative. However, no study has yet validated such data. We compared colonoscopic findings reported by an endoscopic documentation software (Provation) against manually collected medical records data from two similar patient cohorts in the same endoscopy unit.Methods: In November 2011, our unit switched from dictation-based text documentation to the Provation system. As a quality control initiative, we collected data on 9614 patients who had undergone colonoscopies from January 2010 to November 2011, using manual electronic chart review. We compared these data against those generated by Provation on 7091 similar patients who underwent colonoscopy from November 2011 to March 2013.Results: Age, sex and procedural indication distribution were similar between the Manual and Provation cohorts, as were the large (≥1 cm) polyp (7.6 vs. 8.1%; p = 0.25) and advanced neoplasia (8.3 vs. 8.2%; p = 0.80) prevalences. However, there were significant differences in the polyp (46.9 vs. 49.8%) and adenoma prevalences (31.3 vs. 26.8%; p < 0.001). Furthermore, the Manual cohort had a higher prevalence of diverticulosis and hemorrhoids, and a lower colonoscopy completion rate. Stratification by indication resulted in additional discrepancies between the two cohorts for screening and surveillance patients. There were also differences in the anatomic (right vs. left colon) distribution of large polyps.Conclusions: There were significant discrepancies between data from Provation and manually collected medical records data. Although the two cohorts were enrolled during slightly different time periods, they came from the same endoscopy unit, had the same endoscopists and indications, and demonstrated similar demographics, making it unlikely for there to be true differences between the cohorts independent of documentation method. Thus, caution is advised when using endoscopic data for research. [ABSTRACT FROM AUTHOR]

The absence of standard library software is one of the main hinderance in the effective automation of libraries of Higher Education Institutions (HEIs) of Pakistan. A review of the literature does not provide the actual requirements of the libraries in Pakistan related to library software and highlights the absence of library software selection criteria. This paper explores the opinion of the experts about the current status of library software, problems faced by the libraries and needs relevant to library software in order to suggest a sustainable solution for the automation of the libraries of HEIs of Pakistan. This study was conducted using qualitative approach and three focus groups were conducted in Lahore, Islamabad and Karachi. The participants of all three focus groups comprised librarians from HEIs, Library and Information Science (LIS) experts with experience in designing and implementing library software, LIS educators with experience of teaching library automation and computer science professionals having experience with library software. A purposive sampling was made in this regard. A discussion guide was prepared on the basis of literature review and expert opinions. Data were analyzed qualitatively. The analysis of focus groups revealed that there was a shortage of library software and the libraries of HEIs were still in the process of automation. Few libraries were using standard software but most of the libraries had implemented cataloguing module only. The non-availability of standard library software, regional languages, lack of awareness, lack of funds and lack of vision in the top management of HEIs were the common problems causing hinderance in the effective automation of the libraries. The experts suggested formulation of a consortium under the umbrella of HEC that takes the resposibility of development and distribution of the software. [ABSTRACT FROM AUTHOR]

With the pervasiveness of mobile applications (apps), many Chinese libraries have begun to use apps to provide mobile services to users. Although many mobile library (m-library) apps have a high-downloaded rate in the App store, the rate of users continuing to use them remains extremely low, and the acceptance-discontinuance anomaly phenomenon (i.e., users discontinue using a m-library app after initially accepting it) is a common occurrence in China. This study develops an integrated model designed to explain and predict users' continued usage of m-library apps based on the expectation confirmation model of information system continuance (ECM-ISC) and the theory of information system success, It incorporates habit, as a moderating variable of continuance intention and behaviour, into the model. Empirical data was collected from 396 users who had prior experience with m-library apps and was tested against the proposed research model using structural equation modelling. The results demonstrated that user perceived usefulness, expectation confirmation and satisfaction are important parts of the formation of m-library apps continuance usage. Furthermore, the three components of the information system success model, system quality, information quality and service quality, also have significant impacts on user confirmation and ultimately affect continuance usage. And the negative influence of habit on continuance intention and behaviour has been supported. The study will be useful for Chinese libraries to better understand users' continuance usage behaviour and service demands, and in turn to optimize the function of apps and improve the quality of mobile services. [ABSTRACT FROM AUTHOR]

Clinical research and routine care documentation have traditionally been performed in a dual-source approach, where data is collected redundantly and maintained in separated systems. The generic x4T single-source process removes redundant steps and is adoptable to specific types of studies. In support of the various processes, we have designed and implemented an architecture called x4T based on CDISC ODM. The software has been deployed in three different use cases containing up to 3976 subjects until now and allows real-time access to live data from routine care documentation systems. [ABSTRACT FROM AUTHOR]

Companies often develop a set of software variants that share some features and differ in others to meet specific requirements. To exploit the existing software variants as a Software Product Line (SPL), a Feature Model of this SPL must be built as a first step. To do so, it is necessary to define and document the optional and mandatory features that compose the variants. In our previous work, we mined a set of feature implementations as identified sets of source code elements. In this paper, we propose a complementary approach, which aims to document the mined feature implementations by giving them names and descriptions, based on the source code elements that form feature implementations and the use-case diagrams that specify software variants. The novelty of our approach is its use of commonality and variability across software variants, at feature implementation and use-case levels, to run Information Retrieval methods in an efficient way. Experiments on several real case studies (Mobile media and ArgoUML-SPL) validate our approach and show promising results. [ABSTRACT FROM AUTHOR]

Developer documentation helps developers learn frameworks and libraries, yet developing and maintaining accurate documentation requires considerable effort and resources. Contributors who work on developer documentation often need to manually track all changes in the code, determine which changes are significant enough to document, and then, adapt the documentation. We propose AdDoc, a technique that automatically discovers documentation patterns, i.e., coherent sets of code elements that are documented together, and that reports violations of these patterns as the code and the documentation evolves. We evaluated our approach in a retrospective analysis of four Java open source projects and found that at least 50 percent of all the changes in the documentation were related to existing documentation patterns. Our technique allows contributors to quickly adapt existing documentation, so that they can focus their documentation effort on the new features. [ABSTRACT FROM PUBLISHER]

This article considers why users of popular software packages choose to find answers to their task problems on user forums rather than in official documentation. The author concludes that traditional documentation is developed around an antiquated notion of "task," which leads to restrictive ways of thinking about problems that users encounter and the solutions that might be appropriate. The author argues, instead, that tasks and problems arise from networked rhetorical situations and networked contexts for rhetorical action. The influence of networks requires a redefinition of rhetorical situation and context, from which we derive a networked picture of tasks and problems as emergent and uncertain phenomenon, best addressed in the uncertain and sometimes-chaotic setting of user forums. Forum threads are studied using discourse analytic techniques to determine what they can reveal about qualities making tasks and problems uncertain. [ABSTRACT FROM AUTHOR]

The Ewha Music Database (EMDB) and its system are being developed to store and share music information of East Asia through the project "Establishing a Music Education Database of Modern East Asian Music," funded by the National Research Foundation Korea. In order to tackle problems that have arisen due to a lack of a proper establishment of primary sources in East Asian music, the EMDB offers a user-friendly web-based content management system to register and search for information on East Asian music. It will become one of the new and powerful research tools to provide much needed materials efficiently and effectively and form the foundation of a unified primary sources repository for modern music of East Asia. [ABSTRACT FROM AUTHOR]

The documentation of cultural heritage is an essential part of appropriate care of historical monuments, representing a part of our history. At present, it represents the current issue, for which considerable funds are being spent, as well as for the documentation of immovable historical monuments in a form of castle ruins, among the others. Non-contact surveying technologies - terrestrial laser scanning and digital photogrammetry belong to the most commonly used technologies, by which suitable documentation can be obtained, however their use may be very costly. In recent years, various types of software products and web services based on the SfM (or MVS) method and developed as open-source software, or as a freely available and free service, relying on the basic principles of photogrammetry and computer vision, have started to get into the spotlight. By using the services and software, acquired digital images of a given object can be processed into a point cloud, serving directly as a final output or as a basis for further processing. The aim of this paper, based on images of various objects of the Slanec castle ruins obtained by the DSLR Pentax K5, is to assess the suitability of different types of open-source and free software and free web services and their reliability in terms of surface reconstruction and photo-texture quality for the purposes of castle ruins documentation. [ABSTRACT FROM AUTHOR]

The article provides guidelines related to the use of multicolour flow cytometry in the diagnosis of haematological neoplasms. The guidelines include checking the proper instrumentation of cytometry including optimization of Photomultiplier tube (PMT) voltages to maximise signal-noise ratio and choosing lasers with good stability, data files having sample-specific labeling and identification, and documentation of cytometer optimization.

Software architects make architectural decisions such as choosing architecture patterns or frameworks. Capturing architectural decisions reduces evolution costs for software systems. Existing approaches overlook the challenge of capturing tacit knowledge about architectural decisions. Previously, we proposed the REGAIN approach to capture tacit knowledge about architectural decisions. REGAIN is based on the Repertory Grid technique, a powerful knowledge acquisition approach from knowledge engineering. However, REGAIN lacked industrial validation. Therefore, in this paper, we initially present a study to ensure that REGAIN meets the needs of industrial architects. We interviewed 16 architects who indicated REGAIN advantages such as systematic decision-making support. Also, architects indicated improvement opportunities, in particular tool support and the possibility to prioritize concerns that are used to evaluate decision alternatives. Therefore, we conducted an additional study to evaluate two approaches for prioritizing concerns: pairwise-comparisons and the hundred-dollar approach. We conducted an experiment with 30 graduate students to compare the two prioritization approaches. Based on the results of the experiment, we added the hundred-dollar approach to REGAIN. Moreover, based on the study with architects and the experiment with students, we implemented open source tool support for REGAIN, which architects can use to capture architectural decisions. [ABSTRACT FROM AUTHOR]

In the US Air Force there exist several systems for which design documentation does not exist. Chief reasons for this lack of system documentation include software having been developed several decades ago, natural evolution of software, and software existing mostly in its binary versions. However, the systems are still being used and the US Air Force would like to know the actual designs for the systems so that they may be reengineered for future requirements. Any knowledge of such systems lies mostly with its users and managers. A project was commissioned to recover designs for such systems based on knowledge of systems obtained from stakeholders by interviewing them. In this paper we describe our application of the NFR Approach, where NFR stands for Nonfunctional Requirements, to recover software design of a middleware system used by theAir Force called the Phoenix system. In our project we interviewed stakeholders of the Phoenix system, applied theNFR Approach to recover design artifacts, and validated the artifacts with the design engineers of the Phoenix system. Our study indicated that there was a high correlation between the recovered design and the actual design of the Phoenix system. [ABSTRACT FROM AUTHOR]

Abstract: Invariant assertions play an important role in the analysis and documentation of while loops of imperative programs. Invariant functions and invariant relations are alternative analysis tools that are distinct from invariant assertions but are related to them. In this paper we discuss these three concepts and analyze their relationships. The study of invariant functions and invariant relations is interesting not only because it provides alternative means to analyze loops, but also because it gives us insights into the structure of invariant assertions, hence it may help us enhance techniques for generating invariant assertions. [Copyright &y& Elsevier]

Since 2009, the so-called “Aschebücher" have been digitized after their restoration and made accessible in the document management system (DMS) of the Duchess Anna Amalia Library. Parts of the library's collections were damaged to such an extent by the 2004 fire that they are difficult to identify. An internet-based interactive module enables the research community to assist in their identification. The article provides details on the technical adaptations of the DMS and the project organization. Since April 2012, numerous suggestions made facilitated the identification of a wide range of titles. [ABSTRACT FROM AUTHOR]

A complete and detailed (full) Design Rationale Documentation (DRD) could support many software development activities, such as an impact analysis or a major redesign. However, this is typically too onerous for systematic industrial use as it is not cost effective to write, maintain, or read. The key idea investigated in this article is that DRD should be developed only to the extent required to support activities particularly difficult to execute or in need of significant improvement in a particular context. The aim of this article is to empirically investigate the customization of the DRD by documenting only the information items that will probably be required for executing an activity. This customization strategy relies on the hypothesis that the value of a specific DRD information item depends on its category (e.g., assumptions, related requirements, etc.) and on the activity it is meant to support. We investigate this hypothesis through two controlled experiments involving a total of 75 master students as experimental subjects. Results show that the value of a DRD information item significantly depends on its category and, within a given category, on the activity it supports. Furthermore, on average among activities, documenting only the information items that have been required at least half of the time (i.e., the information that will probably be required in the future) leads to a customized DRD containing about half the information items of a full documentation. We expect that such a significant reduction in DRD information should mitigate the effects of some inhibitors that currently prevent practitioners from documenting design decision rationale. [ABSTRACT FROM AUTHOR]

Modeling is a fundamental activity within the requirements engineering process and concerns the construction of abstract descriptions of requirements that are amenable to interpretation and validation. The choice of a modeling technique is critical whenever it is necessary to discuss the interpretation and validation of requirements. This is particularly true in the case of functional requirements and stakeholders with divergent goals and different backgrounds and experience. This paper presents the results of a family of experiments conducted with students and professionals to investigate whether the comprehension of functional requirements is influenced by the use of dynamic models that are represented by means of the UML sequence diagrams. The family contains five experiments performed in different locations and with 112 participants of different abilities and levels of experience with UML. The results show that sequence diagrams improve the comprehension of the modeled functional requirements in the case of high ability and more experienced participants. [ABSTRACT FROM PUBLISHER]

This paper reviews research on how new forms of transportation and information and communication technology (ICT) facilitate changes in daily individual activity patterns and, as a result, the social ecologies of urban environments. Prior attempts to map and describe the space–time social ecologies of place are based on activity diaries for representative samples of urban residents. Geo-referencing information and location technologies embedded within ICT are seen as increasingly central to transformations in urban social ecologies, affording new forms of human activity behavior. Incorporation of geo-enabled ICT provides a research agenda for geographical information science (GIS) to develop concepts and tools for documenting and mapping indicators of the ongoing reorganization in the space–time social ecologies of cities and regions for purposes of exploratory research, diagnostic use, and policy evaluation. [ABSTRACT FROM AUTHOR]

This paper describes an approach to obtain worstcase execution times and worst-case stack usage using a method supported by the Rapita Verification Suite (RVS) from Rapita Systems Ltd for a DO-178B level A Flight Control System software application. The approach has been applied in a Research and Development project in Embraer. The paper outlines the technical approach, and the results achieved so far using two successful testing strategies. [ABSTRACT FROM AUTHOR]

Application Programming Interfaces (API) are exposed to developers in order to reuse software libraries. API directives are natural-language statements in API documentation that make developers aware of constraints and guidelines related to the usage of an API. This paper presents the design and the results of an empirical study on the directives of API documentation of object-oriented libraries. Its main contribution is to propose and extensively discuss a taxonomy of 23 kinds of API directives. [ABSTRACT FROM AUTHOR]

The documentary language thesaurus, as standard terms, have been an important development for document management using software applications such as TemaTres, which is a controlled vocabulary server. This free application, for use on the web, provides continuous access to the sets of documents on specific topics for study, research and decision making. It presents the installation, functionality and interface that shows the application structure and ways of exploiting TemaTres for visual representation and management o fcontrolled vocabularies. [ABSTRACT FROM AUTHOR]

Objective: The aim of this study is to assess the level of acceptance by the dental practitioners to implement a software application that allows a presumptive diagnosis of the systemic diseases based on the oral manifestations. Methods: First we developed a questionnaire to assess the degree of acceptance for the implementation of a dental patient's management information system. The initial questionnaire was applied to a number of 54 dentists from several cities. The questionnaire contains 6 questions evolving from simple to complex. The final evaluation was made after the presentation of the dental patients management software application, and respondents were asked to complete an evaluation questionnaire regarding the application submitted and its applicability in the dental office. Results: We compared the scores average from the final questionnaire, for the groups formed after evaluating the first questionnaire results. Conclusions: Most of the respondents found this computer based decision support system to be easy to use, scientifically well documented and enables accurate and quality documentation of patient data. [ABSTRACT FROM AUTHOR]

The GYRO documentation system offers a simple and efficient method for a friction ridge examiner to document the analysis and comparison stages of the ACE-V process. GYRO uses a colorcoding system to convey the analyst's degree of confidence in the existence of a feature and the degree of variation to which that feature may appear in a corresponding exemplar print. We also explore the benefits and utility of the PiAnoS software, which bears some similarity to GYRO, but with added tool . [ABSTRACT FROM AUTHOR]

The article offers news briefs related to Computerised Documentation Service/Integrated Set of Information Systems (CDS/ISI) in Great Britain. Jean-Claude Dauphin announces that the release of Java-ISI (J-ISIS) can be downloaded. Marshall Breeding also announces his interests in gathering information regarding the many libraries that uses ISIS-related products. Richard Price of Oxford University has set up a web site for the academic world.

Commissioning an indexer can be a daunting task for new editors. What information do indexers need to know about a job? What needs to be supplied to get an indexing quote? What does the indexer do, and in what format can you expect the finished index? Then, once the indexing is underway, how do you deal with late changes to the text without causing undue angst? Finally, what specific areas of the finished index need to be checked? This article explains what is involved. [ABSTRACT FROM AUTHOR]

A review is presented of Rili-BÄK for documentation of the diagnostic processes from NEXUS AG.

Aims and objectives. This paper aims to report the development stages of an audit instrument to assess standardised nursing language. Because research-based instruments were not available, the instrument Quality of documentation of nursing Diagnoses, Interventions and Outcomes (Q-DIO) was developed. Background. Standardised nursing language such as nursing diagnoses, interventions and outcomes are being implemented worldwide and will be crucial for the electronic health record. The literature showed a lack of audit instruments to assess the quality of standardised nursing language in nursing documentation. Design. A qualitative design was used for instrument development. Methods. Criteria were first derived from a theoretical framework and literature reviews. Second, the criteria were operationalised into items and eight experts assessed face and content validity of the Q-DIO. Results. Criteria were developed and operationalised into 29 items. For each item, a three or five point scale was applied. The experts supported content validity and showed 88·25% agreement for the scores assigned to the 29 items of the Q-DIO. Conclusions. The Q-DIO provides a literature-based audit instrument for nursing documentation. The strength of Q-DIO is its ability to measure the quality of nursing diagnoses and related interventions and nursing-sensitive patient outcomes. Further testing of Q-DIO is recommended. Relevance to clinical practice. Based on the results of this study, the Q-DIO provides an audit instrument to be used in clinical practice. Its criteria can set the stage for the electronic nursing documentation in electronic health records. [ABSTRACT FROM AUTHOR]

This review reflects on the response made within the English regions to the national strategy adopted for museums development in the Renaissance in the Regions programme. It considers the national data collection expectations and the actuality of the reporting/evaluation of the programme's management in different regions. A survey of the available regional documentation suggests a lack of consistency in available information and approach, and that review of the programme is welcome in order to establish baseline information for performance measurement. [ABSTRACT FROM AUTHOR]

The article focuses on the nonprofessional social network tools, professionally based adaptation and the rationale behind the use of these tools. Best examples of these nonprofessional social network tools are MySpace and Facebook. These nonprofessional social networking services that are used for professional purposes have been found to be appropriate for an office-based application. Kathleen Hale, the FDLP's Facebook pioneer, sees the use of Facebook as an effective tool in providing the Commonwealth of Pennsylvania's 56 FDLP libraries an outlet for FDLP-related communications.

Traceability links provide support for software engineers in understanding relations and dependencies among software artefacts created during the software development process. The authors focus on re-establishing traceability links between existing source code and documentation to support software maintenance. They present a novel approach that addresses this issue by creating formal ontological representations for both documentation and source code artefacts. Their approach recovers traceability links at the semantic level, utilising structural and semantic information found in various software artefacts. These linked ontologies are supported by ontology reasoners to allow the inference of implicit relations among these software artefacts. [ABSTRACT FROM AUTHOR]

Author Cocitation Analysis (ACA) and Web Colink Analysis (WCA) are examined as sister techniques in the related fields of bibliometrics and webometrics. Comparisons are made between the two techniques based on their data retrieval, mapping, and interpretation procedures, using mathematics as the subject in focus. An ACA is carried out and interpreted for a group of participants (authors) involved in an Isaac Newton Institute (2000) workshop—Singularity Theory and Its Applications to Wave Propagation Theory and Dynamical Systems—and compared/contrasted with a WCA for a list of international mathematics research institute home pages on the Web. Although the practice of ACA may be used to inform a WCA, the two techniques do not share many elements in common. The most important departure between ACA and WCA exists at the interpretive stage when ACA maps become meaningful in light of citation theory, and WCA maps require interpretation based on hyperlink theory. Much of the research concerning link theory and motivations for linking is still new; therefore further studies based on colinking are needed, mainly map-based studies, to understand what makes a Web colink structure meaningful. [ABSTRACT FROM AUTHOR]

Code without documentation is generally useless. Moreover, all safety standards require that documentation to be consistent with the actual code. AdDoc automates the generation of documentation from the source code and therefore helps ensuring that the documentation is always up to date. [ABSTRACT FROM AUTHOR]

Jan Rayment recounts her experiences of using a new book on Adobe InDesign CC to begin exploring its applications for the professional indexer [ABSTRACT FROM AUTHOR]