Done well, separation of concerns can provide many soft-ware engineering benefits, including reduced complexity, im-proved reusability, and simpler evolution. The choice of boundaries for separate concerns depends on both require-ments on the system and on
N Degrees of Separation: Multi-Dimensional Separation of Concerns Peri Tarr Harold Ossher William Harrison IBM Watson Research Center P.O. Box 704 Yorktown Heights, NY 10598 (914) 784-7278{tarr,ossher,harrisn}@watson.ibm.com ABSTRACT Done well, separation of concerns ware engineering benefits, including can provide many reduced complexity, softim-
Stanley M. Sutton, Jr.* EC Cubed, Inc. 15 River Road, Suite 310 Wilton, CT 06897 (203) 761-3971 ssutton@eccubed.com
proved reusability, boundaries
and simpler concerns
evolution. depends
The choice of on both require-
for separate
ments on the system and on the kind(s) of decompositionand composition a given formalism supports. The predominant methodologies and formalisms available, however, support only orthogonal separations of concerns, along sdngle dimen-
sions of composition and decomposition. These characteristics lead to a number of well-known and difficult problems. This paper plementing for modeling and imsoftware artifacts, one that permits separation of overlapping concerns along multiple dimensions of composi-
the formalisms used to develop software artifacts. Reduced complexity and improved comprehensibility require decomposition mechanisms to carve software into meaningful and manageable pieces. They also require composition mechanisms to put pieces together usefully. Reuse requires the development of large-scale reusable components, low coupling, and powerful, non-invasive adaptation and customization capabilities. Ease of evolution depends on low coupling and also requires tracec&lity across the software lifecycle, mechanisms for min-
describes a new paradigm
imizing the impact of changes, and substitutability. Despite much good research in the software engineering domain, many of the problems that complicate software engineering still remain. Software comprehensibility tends to degrade over time (if, indeed, it is present at all). Many common maintenance and evolution activities result in high-impact, invasive modifications. Artifacts are of limited reusability, or are reusable only with difficulty. Traceability across the various software artifacts is limited, which further complicates evolution. These somewhat diverse problems are due, in large part, to limitations and unfulfilled requirements related to separation of concerns[19]. Our ability to achieve the goals of software engineering depends fundamentally on our ability to keep separate all concerns of importance in software systems. All modern software formalisms support separation of concerns to some extent, through mechanisms for decomposition and composition. However, existing formalisms at all lifecycle phases provide only small, restricted sets of decomposition and composition mechanisms, and these typically support only a single,“dominant” dimension of separation at a time. We call this“tyranny of the dominant decomposition.” We believe that achieving the primary goals of software engineering requires
support for simuktaneous separation of overlapping concerns in multiple dimensions. We will illustrate how limitations on current mechanisms prevent this and thereby lead directly to the failure to achieve these goals. We propose a model of software artifacts, decomposition, and composition to overcome
tion and decomposition. This approach addresses numerous problems throughout the software lifecycle in achieving wellengineered, evolvable, flexible software artifacts and traceability across artifacts.
Keywords Hypermodules; hyperslices; software decomposition and composition; multi-dimensional separation of concerns
1
INTRODUCTION
The primary goals of software engineering are to improve software quality, to reduce the costs of software production, and to facilitate maintenance and evolution. In pursuit of these goals, software engineers constantly seek development technologies and methodologies that reduce software complexity, improve comprehensibility, promote reuse, and facilitate evolution. These properties, in turn, induce several specific requirements on +Stanley Sutton performed this work while at the University
of Massachusetts at Amherst. He was supported there in part by the Air Force Materiel Command, Rome Laboratory, and the Advanced Research Projects Agency under Contract F30602-94 c-0137.
Copyright ACM 1999 I-581 13-074-0/99/05...$5.00
107































on Multi-dimensional Sep... 暂无评价 6页 免费 N degrees of separation ... Refinements and Multi-Dimensional Separation of Concerns Abstract 1 Step-wise...
N degrees of separation ... 暂无评价 13页 免费 Refinements and Multi-Di...We discuss the multi-dimensional separation of concerns in HW design in ...
N degrees of separation ... 暂无评价 13页 免费 Refinements and Multi-Di...Multi-dimensional Separation of Concerns examples of concerns (in our ...
N degrees of separation ... 暂无评价 13页 免费 Refinements and Multi-Di... Workshop on Multi-Dimensional Separation of Concerns in Software Engineering ...
Six Degrees Of Separation英文歌词及中文翻译_其它_计划/解决方案_应用文书。Six Degrees Of Separation英文歌词及中文翻译今日推荐 ...
on Multi-dimensional Sep... 暂无评价 6页 免费 N degrees of separation ...nite case concerns the structure of the traceless conformal Killing tensor. ...
Six Degrees of Separation_英语学习_外语学习_教育专区。Six degrees of separation You've read the books, you've watched the shows What's the best way...
John Guare (b 1938) Six Degrees of Separation (1993)_建筑/土木_工程科技_专业资料。John Guare (b 1938) Six Degrees of Separation (1993)...
Sutton, Jr., “N Degrees of Separation: Multi-Dimensional Separation of Concerns”, ICSE 1999. [8] M. VanHilst and D. Notkin, “Using role ...
Sutton, Jr., “N Degrees of Separation: Multi-Dimensional Separation of Concerns”, ICSE 1999. [34] P Tarr and H. Ossher. Hyper/J User and ...
热门文档