Showing papers on "Database-centric architecture published in 1994"

SAAM: a method for analyzing the properties of software architectures

Abstract: While software architecture has become an increasingly important research topic in recent years, insufficient attention has been paid to methods for evaluation of these architectures. Evaluating architectures is difficult for two main reasons. First, there is no common language used to describe different architectures. Second, there is no clear way of understanding an architecture with respect to an organization's life cycle concerns -software quality concerns such as maintainability portability, modularity, reusability, and so forth. We address these shortcomings by describing three perspectives by which we can understand the description of a software architecture and then proposing a five-step method for analyzing software architectures called SAAM (Software Architecture Analysis Method). We illustrate the method by analyzing three separate user interface architectures with respect to the quality of modifiability. >

Correctness and composition of software architectures

Abstract: The design of a large system typically involves the development of a hierarchy of different but related architectures A criterion for the relative correctness of an architecture is presented, and conditions for architecture composition are defined which ensure that the correctness of a composite architecture follows from the correctness of its parts Both the criterion and the composition requirements reflect special considerations from the domain of software architectureThe main points are illustrated by means of familiar architecture for a compiler A proof of the relative correctness of two different compiler architectures shows how to decompose a proof into generic properties, which are proved once for every pair of architectural styles, and instance-level properties, which must be proved for every architecture

Software architecture: practice, potential, and pitfalls

Abstract: Whatever the long-term impact of software architecture may turn out to be, an appropriate starting point is a concrete appraisal of the current state of the practice in the use of software architecture. It is the purpose of the article to take a step in this direction. It provides concrete examples of what is now possible when architectural principles are applied to industrial problems in systematic ways, considers the potential impact of software architecture over the next few years, and suggests steps that should be taken to bring this about. >

Towards an architecture for distributed multimedia applications support

Abstract: Presents the basic principles of a general architecture for distributed multimedia applications support over ATM-based networks. The architecture is aimed at providing the services, the mechanisms and the interactions required by multimedia applications. The architecture is based on the quality of service and communication management functions associated to the services it provides. >

The many dimensions of scalability

Abstract: The scalability of a computer architecture has more dimensions than are usually recognized. These dimensions include performance economics, physical size, addressing, software independence, communication ability, technology independence, and optionality. All must be considered in the design if an architecture is to be successful over a significant time period. Certain recently-developed system architectures have much better scaling properties than did the previous generations, which are now approaching their fundamental limits. >

Micro-Architecture vs. Macro-Architecture

Abstract: The field of study commonly known as "software architecture" should be split into two subareas: micro-architecture and macro-architecture. Work to date under the name "software architecture" has concentrated largely on macro-architecture. But micro- architecture, a.k.a. software component engineering, is of equal concern.

Application specific parallel architectures

Abstract: This paper deals with the design of parallel architectures dedicated to specific applications and mainly focuses on the relationships between software and hardware tradeoffs, putting the emphasis on parallel architecture for non-numeric applications. The analysis covers both medium and massive parallelism. Medium level parallelism is seen through the analysis of VLIW architectures where code-generation takes an important role for achieving high performance. In particular we show the main design steps of a parallel architecture for Prolog. High level parallelism in non-numeric applications is introduced through the presentation of a dedicated architecture for the solution of NP-complete problems with the Boltzmann Machine model. Also in this case, we present the problems related to the design of the architecture and the interaction between hardware and software components. >

A reference architecture for control of mechanical systems

Abstract: Presents a reference architecture for the control of mechanical systems. The architecture, called the "Joint Architecture", is derived in part from existing real-time control systems and manufacturing systems integration architectures at the National Institute of Standards and Technology. The Joint Architecture is under development and not yet complete. It is a hierarchical control architecture and focuses on the control of systems for manufacturing discrete parts by machining. A definition of "architecture" has been adopted which includes explicit levels of abstraction, termed "tiers of architectural definition", and five elements of architectural definition: (i) statement of scope and purpose, (ii) domain analyses, (iii) architectural specification, (iv) methodology for architectural development, and (v) conformance criteria. This paper gives an overview of the Joint Architecture and describes its two most abstract tiers. >

Systematic Assessment of Computer Systems Architectures

Abstract: Development, selection, and evolution of workstation architectures depend mainly on a comprehensive assessment of the architecture and its parts. Proper assessment of an architecture is a key to its success on the market. This paper presents a systematic method for system assessment which supports the user to make decisions explicit, allowing to find out later why which decisions were taken. The assessment process is reproducible and documented by a graphical representation of the most important aspects underlying architecture assessment: system architecture, assessment criteria, and system workload.