scispace - formally typeset
Search or ask a question
Author

A. S. Peterson

Bio: A. S. Peterson is an academic researcher. The author has contributed to research in topics: Domain analysis & Domain (software engineering). The author has an hindex of 6, co-authored 7 publications receiving 4384 citations.

Papers
More filters
ReportDOI
01 Nov 1990
TL;DR: This report will establish methods for performing a domain analysis and describe the products of the domain analysis process to illustrate the application of domain analysis to a representative class of software systems.
Abstract: : Successful Software reuse requires the systematic discovery and exploitation of commonality across related software systems. By examining related software systems and the underlying theory of the class of systems they represent, domain analysis can provide a generic description of the requirements of that class of systems and a set of approaches for their implementation. This report will establish methods for performing a domain analysis and describe the products of the domain analysis process. To illustrate the application of domain analysis to a representative class of software systems, this report will provide a domain analysis of window management system software.

4,420 citations

ReportDOI
01 Jun 1992
TL;DR: An analysis of the army movement control domain performed by the Software Engineering Institute (SEI) and a team of movement control experts from the Army is documents.
Abstract: : This report documents an analysis of the army movement control domain performed by the Software Engineering Institute (SEI) and a team of movement control experts from the Army. This report includes common terminology and requirements extracted from Army doctrine, experts in the field, and movement control systems. The report also describes the potential for prototyping of systems using domain analysis products and the tool support needed.

42 citations

01 Jun 1992
TL;DR: In this article, an analysis of the army movement control domain performed by the Software Engineering Institute (SEI) and a team of movement control experts from the Army is described. And the potential for prototyping of systems using domain analysis products and the tool support needed.
Abstract: : This report documents an analysis of the army movement control domain performed by the Software Engineering Institute (SEI) and a team of movement control experts from the Army. This report includes common terminology and requirements extracted from Army doctrine, experts in the field, and movement control systems. The report also describes the potential for prototyping of systems using domain analysis products and the tool support needed. Common Army terminology and requirements, Domain analysis, Tool support. Movement control,

34 citations

ReportDOI
01 May 1994
TL;DR: A process for mapping domain information in Feature-Oriented Domain Analysis (FODA) into a generic design for a domain, which includes supporting code components that conform to the Object Connection Architecture (OCA), a model for structuring software systems.
Abstract: : In contrast to the number of reports on domain analysis, little work has been done in describing the utilization of domain analysis results in the development of generic designs for building applications in a domain. This report describes a process for mapping domain information in Feature-Oriented Domain Analysis (FODA) into a generic design for a domain. The design includes supporting code components that conform to the Object Connection Architecture (OCA), a model for structuring software systems. A process for the use of the design in implementing applications is included. The processes and products described herein augment the final phase of domain analysis (or engineering) described in the original FODA report. This report also documents the continuing work of applying FODA to the movement control domain. The design and Ada code examples for the domain used in the document are from prototype software, created in part to test the processes presented

27 citations

ReportDOI
01 Jun 1990
TL;DR: A bibliography of references on a comparatively new discipline called domain analysis is presented to provide an historical perspective on the field as well as a necessary background for further work in the discipline.
Abstract: : This document presents a bibliography of references on a comparatively new discipline called domain analysis. This discipline defines a process to identify and represent the relevant information in a domain (a set of systems which share common capabilities). The information is derived from: (1). the study of existing systems and their development histories (2). knowledge captured from domain experts (3). underlying theory (4). emerging technology Domain analysis has received considerable attention since the early 1980s. This interest stems from the fact that the application of domain analysis is now believed to be part of the foundation upon which a successful and systematic program of software reuse can be built. This foundation is achieved by capturing and preserving the information to be reused in future developments in the form of application-specific tools and reusable software models, architectures, and components. This bibliography has been compiled as a part of the work on the Domain Analysis Project at the Software Engineering Institute. The bibliography's purpose is to provide an historical perspective on the field as well as a necessary background for further work in the discipline. Bibliography, Domain analysis, Software reuse.

12 citations


Cited by
More filters
Journal ArticleDOI
01 Apr 1988-Nature
TL;DR: In this paper, a sedimentological core and petrographic characterisation of samples from eleven boreholes from the Lower Carboniferous of Bowland Basin (Northwest England) is presented.
Abstract: Deposits of clastic carbonate-dominated (calciclastic) sedimentary slope systems in the rock record have been identified mostly as linearly-consistent carbonate apron deposits, even though most ancient clastic carbonate slope deposits fit the submarine fan systems better. Calciclastic submarine fans are consequently rarely described and are poorly understood. Subsequently, very little is known especially in mud-dominated calciclastic submarine fan systems. Presented in this study are a sedimentological core and petrographic characterisation of samples from eleven boreholes from the Lower Carboniferous of Bowland Basin (Northwest England) that reveals a >250 m thick calciturbidite complex deposited in a calciclastic submarine fan setting. Seven facies are recognised from core and thin section characterisation and are grouped into three carbonate turbidite sequences. They include: 1) Calciturbidites, comprising mostly of highto low-density, wavy-laminated bioclast-rich facies; 2) low-density densite mudstones which are characterised by planar laminated and unlaminated muddominated facies; and 3) Calcidebrites which are muddy or hyper-concentrated debrisflow deposits occurring as poorly-sorted, chaotic, mud-supported floatstones. These

9,929 citations

ReportDOI
01 Nov 1990
TL;DR: This report will establish methods for performing a domain analysis and describe the products of the domain analysis process to illustrate the application of domain analysis to a representative class of software systems.
Abstract: : Successful Software reuse requires the systematic discovery and exploitation of commonality across related software systems. By examining related software systems and the underlying theory of the class of systems they represent, domain analysis can provide a generic description of the requirements of that class of systems and a set of approaches for their implementation. This report will establish methods for performing a domain analysis and describe the products of the domain analysis process. To illustrate the application of domain analysis to a representative class of software systems, this report will provide a domain analysis of window management system software.

4,420 citations

Journal ArticleDOI
TL;DR: In this article, the authors identify patterns in the decision, analysis, design, and implementation phases of DSL development and discuss domain analysis tools and language development systems that may help to speed up DSL development.
Abstract: Domain-specific languages (DSLs) are languages tailored to a specific application domain. They offer substantial gains in expressiveness and ease of use compared with general-purpose programming languages in their domain of application. DSL development is hard, requiring both domain knowledge and language development expertise. Few people have both. Not surprisingly, the decision to develop a DSL is often postponed indefinitely, if considered at all, and most DSLs never get beyond the application library stage.Although many articles have been written on the development of particular DSLs, there is very limited literature on DSL development methodologies and many questions remain regarding when and how to develop a DSL. To aid the DSL developer, we identify patterns in the decision, analysis, design, and implementation phases of DSL development. Our patterns improve and extend earlier work on DSL design patterns. We also discuss domain analysis tools and language development systems that may help to speed up DSL development. Finally, we present a number of open problems.

1,778 citations

Journal ArticleDOI
TL;DR: The literature available on the topic of domain-specific languages as used for the construction and maintenance of software systems is surveyed, and a selection of 75 key publications in the area is listed.
Abstract: We survey the literature available on the topic of domain-specific languages as used for the construction and maintenance of software systems. We list a selection of 75 key publications in the area, and provide a summary for each of the papers. Moreover, we discuss terminology, risks and benefits, example domain-specific languages, design methodologies, and implementation techniques.

1,538 citations

Book ChapterDOI
26 Sep 2005
TL;DR: This work integrates prior results to connect feature models, grammars, and propositional formulas, which allows arbitrary propositional constraints to be defined among features and enables off-the-shelf satisfiability solvers to debug feature models.
Abstract: Feature models are used to specify members of a product-line. Despite years of progress, contemporary tools often provide limited support for feature constraints and offer little or no support for debugging feature models. We integrate prior results to connect feature models, grammars, and propositional formulas. This connection allows arbitrary propositional constraints to be defined among features and enables off-the-shelf satisfiability solvers to debug feature models. We also show how our ideas can generalize recent results on the staged configuration of feature models.

1,231 citations