Helix: The Architecture of the XMS Distributed File system

Fridrich, M.; Older, William J.

doi:10.1109/ms.1985.230697

Cited by 16 publications

(12 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The architecture encourages a client-server model for the structuring of applications. " FO85] { \We h a ve c hosen a distributed, object-oriented a p p r oach to managing information. " Lin87] { \The easiest way to make the canonical sequential compiler into a concurrent compiler is to pipeline the execution of the compiler phases over a numberofprocessors.…”

Section: Folklore and Common Practicementioning

confidence: 99%

Formulations and formalisms in software architecture

Shaw

Garlan

1995

Computer Science Today

View full text Add to dashboard Cite

Abstract. Software architecture is the level of software design that addresses the overall structure and properties of software systems. It provides a focus for certain aspects of design and development that are not appropriately addressed within the constituent modules. Architectural design depends heavily on accurate speci cations of subsystems and their interactions. These speci cations must cover a wide variety of properties, so the speci cation notations and associated methods must be selected or developed to match t h e properties of interest. Unfortunately, the available formal methods are only a partial match for architectural needs, which e n tail description of structure, packaging, environmental assumptions, representation, and performance as well as functionality. A prerequisite for devising or selecting a formal method is sound understanding of what needs to be formalized. For software architecture, much of this understanding is arising through progressive codi cation, which begins with real-world examples and creates progressively more precise models that eventually support formalization. This paper explores the progressive codi cation of software architecture: the relation between emerging models and the selection, development, and use of formal systems.

show abstract

Section: Folklore and Common Practicementioning

confidence: 99%

Formulations and formalisms in software architecture

Shaw

Garlan

1995

Computer Science Today

View full text Add to dashboard Cite

show abstract

“…The architecture encourages a client-server model for the structuring of applications." [Fridrich85] "* "We have chosen a distributed, object-oriented approach to managing information." [Linton87] "* "The easiest way to make the canonical sequential compiler into a concurrent compiler is to pipeline the execution of the compiler phases over a number of processors.... A more effective way [is to] split the source code into many segments, which are concurrently processed through the various phases of compilation [by multiple compiler processes] before a final, merging pass recombines the object code into a single program."…”

Section: Background and Rationalementioning

confidence: 99%

mentioning

confidence: 99%

Experience With a Course on Architectures for Software Systems. Part 1. Course Description

Garlan¹,

Shaw²,

Okasaki³

et al. 1992

View full text Add to dashboard Cite

As software systems grow in size and complexity their design problem extends beyond algorithms and data structures to issues of system design. This area receives little or no treatment in existing computer science curricula. Although courses about specific systems are usually available, there is no systematic treatment of the organizations used to assemble components into systems. These issues -the software architecture level of software design -are the subject of a new course that we taught for the first time in Spring 1992. In this pair of reports, Part I presents the motivation for the course, the content and structure of the current version, and our plans for improving the next version. Part II consists of teaching materials from the first offering, including assignments and overheads for lectures. Experience With a Course on Architectures for Software Systems Part I: Course Description Abstract: As software systems grow in size and complexity their design problem extends beyond algorithms and data structures to issues of system design. This area receives little or no treatment in existing computer science curricula. Although courses about specific systems are usually available, there is no systematic treatment of the organizations used to assemble components into systems. These issues-the software architectume level of software design-are the subject of a new course that we taught for the first time in Spring 1992. In this pair of reports, Part I presents the motivation for the course, the content and structure of the current version, and our plans for improving the next version. Part II consists of teaching materials from the first offering, including assignments and overheads for lectures. 1 OverviewThe software component of the typical undergraduate curriculum emphasizes algorithms and data structures. Although courses on compilers, operating systems, or databases are usually offered, there is no systematic treatment of the organization of modules into systems, or of the concepts and techniques at an architectural level of software design. Thus, system issues are seriously underrepresented in current undergraduate programs. Further, students now face a large gap between lower-level courses, in which they learn programming techniques, and upper-level project courses, in which they are expected to design more significant systems. Without knowing the alternatives and criteria that distinguish good architectural choices, the already-challenging task of defining an appropriate architecture becomes formidable.We have developed a course that will help to bridge this gap: Architectures for Software Systems. Specifically, the course: "* Teaches how to understand and evaluate designs of existing software systems from an architectural perspective."* Provides the intellectual building blocks for designing new systems in principled ways using well-understood architectural paradigms."* Shows how formal notations and models can be used to characterize and reason about a system design."* Presents concrete exam...

show abstract

“…However, we subscribe to the view that it is premature to build mechanisms for atomic transactions into the low level stable store [1,9,10,15]. The stable store provides a very primitive form of transaction that allows the system to recover from unexpected errors, be they hardware or software.…”

Section: Endmentioning

confidence: 99%

On the integration of object-oriented and process-oriented computation in persistent environments

Morrison

Brown

Carrick

et al. 1988

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Persistent programming is concerned with the construction of large and long lived systems of data [1,2]. Such systems have traditionally required concurrent access for two reasons. The first is that of speed, be it access speed for multiple users or execution speed for parallel activities. The second reason for concurrency is to control the complexity of large systems by decomposing them into parallel activities.This process-oriented approach to system construction has much in common with the object-oriented approach. We will demonstrate, in this paper, the facilities of the language Napier [18] which allows the integration of the two methodologies along with a persistent environment to provide concurrently accessed object-oriented databases.

show abstract

Helix: The Architecture of the XMS Distributed File system

Cited by 16 publications

References 5 publications

Formulations and formalisms in software architecture

Formulations and formalisms in software architecture

Experience With a Course on Architectures for Software Systems. Part 1. Course Description

On the integration of object-oriented and process-oriented computation in persistent environments

Contact Info

Product

Resources

About