Booch, G. (1987), "Software Components with Ada", Benjamin/Cummings.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....based on the L4 kemel and Pebble [ 10] 1.2 DBMS Componentisation Work on evolving the architecture the DBMS architecture has followed a very similar path to that of the OS but has to some extent lagged behind. For example some research has been carded out on adapting lightweight DBMS (LWDB) [4, 27, 16]. Often, these systems omit features found in traditional DBMS, and include more specialised features which maximise performance. Such systems are very limited to particular applications and most were custom built and remained monolithic. Research has also considered extensible systems to tailor ....

Booch G., Software Components with Ada, Benjamin/Cummings, 1987

.... Integration# and# Test # applied# to# different# abstraction# levels# of# the# system architecture.# Structured# Analysis# # Real Time #according# to# [9]# served# as# specification# method. # The design# guidelines# followed# Grady# Booch s# ideas# about# an# object based # design# [10].# The programming#language# Ada#83 #appeared#to#be#the#best#choice#for#safety critical#real time#systems#at that#time. System#Architecture Different#products#implemented#on#this#platform#result#in#the#anticipated#substation#automation#system (e.g.# a# communication#gateway,#a#controller,#a#bus# ....

.... Controller Main CPU I O Device Bus Master I O Device Remote I O Device I O Device Remote I O Device Remote I O Interbay#Bus Process#Bus Figure#1:#Architecture#of#the#Substation#Automation#System Basic#Software#Architecture As#a#consequence#of#the#guidelines#adopted#from#[10],#a#software#architecture#arose#which#decomposed the#system#into#components#called# subsystems .#Figure#2#visualizes#this#architecture#where#the#threeletter abbreviations# identify# the# different# subsystems.# Since# their# meaning# is# not# relevant# to# the discussion,# we# omit# their# ....

G. Booch, Software components with Ada: Addison-Wesley, 1987.

....systems and the failure modes of their development. The goal was to determine the size and scope of reusable software components which are appropriate for large systems development by programmers and semi automatic agents [11] V ry small software components (such as sorts and list management [4]) are helpful in the e construction of large software systems, but do not significantly reduce the development time of a very large system. packages are not a sufficient mechanism for decomposition or reusability. The reason for this is that there are some abstractions that are simply too ....

Booch, G., Software Components with Ada, Benjamin/Cumminings Publishers, 1987.

....time necessary to install the component in the application. and whether the cost of learning should be included. Favaro classified the Booch components according to their relative complexity. The following categories are listed in order of increasing complexity. The quoted definitions are from [Booch 87] monolithic Denotes that the structure is always treated as a single unit and that its individual parts cannot be manipulated. Monolithic components do not permit structural sharing; stack, string, queue, deque, ring, map, set, and bag components are monolithic. polylithic Denotes that the ....

Booch, G. Software components with Ada. Menlo Park, CA: Benjamin / Cummings, 1987.

....constant, only the code for the selected direction is kept. This illustrates that switch values in view types can select optional features of generics. Weide [73] notes that options in reusable procedures are essential to avoid a combinatoric set of versions. For example, the Booch component set [9] contains over 500 components; Batory [5] has identified these as combinations of fewer design decisions. The linked list library has 28 procedures; one view cluster allows specialization of any of them. VIEWAS requires minimal input; it presents sensible choices, so the user does not need to ....

G. Booch, Software Components with Ada, Benjamin-Cummings, 1987.

....to study this subject. Until recent years, with the evolution (or some may prefer revolution) of the Objected Oriented Paradigm, research issues on Software Reuse have been paid extra attention by the software community. For example, Cox s Objective C for Software IC[11] Booch s Ada components[6], Freeman s classification of software reusability[4] Prieto Diaz s facet scheme for software reusability classification[12] Chen s interface design for reusable software components and C reusable components [1,3] to name a few. Some of these research results have led to practical and ....

Grady Booch, "Software Components with Ada", Benjamin/Cummings, California, 1987.

....that omits one or more features of a heavyweight DBMS and specializes the implementations of its features to maximize performance. Examples of LWDBs include main memory DBMSs (e.g. Smallbase [Hey95] persistent stores (e.g. Texas [Sin92] and primitive code libraries (e.g. Booch Components [Boo87], Code Farms C Data Object Library [Cod95] Each of these examples strips features from a general purpose DBMS (e.g. Smallbase removes the databases larger than main memory feature, Texas removes client server architectures, and the Booch Components further strip checkpoints and recovery) and ....

Grady Booch. Software Components with Ada, Benjamin/Cummings, Menlo Park, California, 1987.

....the set. 3. Provide a system call that will iterate over all the elements in a set and call a function passed by the process for each element. This solves the problem directly. See Gamma et al. 1995, pp. 260ff) for a discussion of internal and external iterators (alternatives 2 and 3 above) See Booch (1987, PP. 158 161) for a discussion of active and passive iterators (alternatives 2 and 3 above) in Ada. Implementing threads (operating systems) Threads can be added to an existing operating system in several ways. 1. Threads can be implemented at the user level with no help from the operating ....

Booch, G. Software Components with Ada. Benjamin/Cummings, Redwood City CA, 1987.

....a primitive algorithm or data structure; it is uncommon to find library modules which correspond to complex program subsystems. Examples of function and class libraries include the standard C library [Ker90] X window system [Sch90] NIHCL [Gor90] GNU libg [Lea88] the Booch Components [Boo87, Boo90], and the C Standard Template Library [Pla95] Experience has shown that large software systems do not benefit much from function or class libraries. Because the goal of such libraries is to provide only a general purpose set of basic abstractions, the programmer is responsible for selecting, ....

....contemporary libraries are not scalable, which means that it will be progressively more difficult for such libraries to represent the systems found in their respective problem domains. We uncovered the library scalability problem during our study of libg [Lea88] and the Booch C Components [Boo87], two popular data structure libraries. These libraries contain numerous modules which implement different data structures; often, the only difference between two modules is the algorithm used to implement a single data structure feature. Therefore, even though these libraries offer many data ....

[Article contains additional citation context not shown here]

Grady Booch. Software components with Ada, Benjamin / Cummings, Menlo Park, CA, 1987.

....of look and feel independent services, is similar to our approach, i.e. to provide an extensible, adaptable collection of building blocks and rules for composing them into flexible, evolving library interfaces systems. From these studies and our own experiments using Booch component [Booc 87] implementations and Stepanov and Musser s generic components, we derived a schema for such architectures, allowing us to isolate and deal with a number of orthogonal architectural issues. Such a schema is built on and is complementary to the 3C schema for dealing with single component issues. ....

Booch, G. [1987] Software Components with Ada. Benjamin/Cummings Publishing Co.

....RESOLVE as a Component Description Language The idea of having explicit and precise descriptions for software components is hardly new. Booch, for example, states in his discussion on a stack abstract data type , that we would like to express these (behavioral) characteristics more formally [1]. He goes on to say, current abstract data type techniques are not sufficiently powerful (for this) A central goal of RESOLVE is to address this deficiency by providing means for formally and easily describing the behavior of reusable software components, among others. Consider the example ....

G. Booch, Software Components with Ada, Benjamin/Cummings, 1987.

....G en erateur d Applications, R eutilisation, Evaluation Partielle A Framework of Application Generator Design 3 1 Introduction Our framework for the development of application generators is structured into two levels. The first level is based on well established ideas of generic components [14, 4], which have desirable characteristics for reuse and structured design. This level of the framework consists of the definition of an abstract machine, where operations of the abstract machine can be viewed as generic components. Abstract machines are a well understood concept from programming ....

G. Booch. Software Components with Ada. Benjamin Cummings, 1987.

....Initially, with a partial understanding of the system requirements, a programmer invents data storage structures to address a perceived need. These data structures are then either implemented by hand (a tedious process) or taken from a component library (e.g. STL [Ste95] or the Booch components [Boo87]) It is quite rare, however, that the projected requirements are accurately reflected in the first design (and even if they are they may change in time) Altering a data structure is often costly; interfaces to different data structures can vary widely, and thus may require extensive source code ....

G. Booch, Software Components with Ada, Benjamin/Cummings, 1987.

....block level SVCs. The chemical factory information system is written in Ada 83, which does not support a class construct. Instead, a class can be represented by an Ada package, which exports a private or limited private type, named Object, which is sometimes made public for convenience [7]. The Object type is typically an Ada record type, where each component represents a class attribute. Instances of the class are then instances of the Object type. The source code level SVC for the LANToBroadcast block is given by: LANToBroadcast Block Source Code Level SVC (informal) 1) For ....

Grady Booch, "Software Components with Ada", Benjamin/Cummings Pub. Co., Redwood City, California, 1987.

....existed in one form or another for a number of years. The idea of constructing modular software has long been recognized as advantageous within the software community, even dating back to the early days of FORTRAN programming with subroutines and libraries serving as components. Work by Booch [1] and Meyer [4] in the 1980 s was generally regarded as seminal in the advancement of ideas regarding the fundamental nature of components, particularly with regard to low level structural properties of the components. More recent work by Weide, et al. 5,6,7] extended these ideas along various ....

....is not component based. Figure 1 CBSE in the Curriculum Thus, our initial case study and curriculum emphasis is on how to construct modular software in a relatively straightforward architecture (standard C programming) This view of components is much like the classical view found in [1, 4, 5, 6, 7]. Once this is complete, we then look at issues relative to binary software components. Binary components are compiled software artifacts which are typically integrated into the application at runtime; such components represent the common, commercial use of the term component. Understanding ....

Booch, G., Software Components with Ada, Benjamin-Cummings, 1987.

....existed in one form or another for a number of years. The idea of constructing modular software has long been recognized as advantageous within the software community, even dating back to the early days of FORTRAN programming with subroutines and libraries serving as components. Work by Booch [2] and Meyer [5] in the 1980 s was generally regarded as seminal in the advancement of ideas regarding the fundamental nature of components, particularly with regard to low level structural properties of the components. More recent work [1,7,8,10,12] extended these ideas along various dimensions, ....

Booch, G., Software Components with Ada , Benjamin-Cummings, 1987.

....that do not support local certifiability remain incredibly difficult and costly even if you can make those systems work as they should in the current release. 4. Related Work There are many recent books and papers promoting (partial) disciplines for component built software, e.g. Liskov 86, Booch 87, Meyer 88, Musser 89, Weide 91, Batory 92, Meyer 92] There are papers on certification of various component properties (e.g. Knight 91] and questions about the very feasibility of dependable large systems [Neumann 93] But there is surprisingly little work that pinpoints local certifiability ....

....collector is inappropriate due to its unpredictable effects on system performance. How can you be sure that the storage management techniques used in the individual components do not interact to introduce a storage leak that will eventually crash the system For example, the Booch Ada components [Booch 87] are subject to this problem, and simply adopting a functional style of programming would not fix it [Hollingsworth 91] The program verification literature of the late 1970 s addresses sound and relatively complete modular proof of correctness systems [Cook 78] which are defined for very ....

Booch, G. Software Components with Ada. Benjamin/Cummings, Menlo Park, CA, 1987.

No context found.

Booch, G. (1987), "Software Components with Ada", Benjamin/Cummings.

No context found.

Booch, G. (1987), Software Components with Ada, Benjamin/Cummings.

No context found.

Booch, G., Software Components with Ada, Benjamin/Cummings, Menlo Park, CA, 1987.

No context found.

Booch, G., Software Components with Ada, Benjamin/Cummings, 1987.

No context found.

G. Booch, Software Components with Ada, Benjamin/Cummings, 1987.

No context found.

Booch, Grady. Software Components with Ada, Benjamin/Cummings, 1987.

No context found.

G. Booch, Software Components with Ada, Benjamin/Cummings, 1987.

No context found.

Booch, G., Software Components with Ada. Second ed. 1987. Benjamin Cummings.

First 50 documents  Next 50

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC