Programming-in-the-Large Versus Programming-in-the-Small

DeRemer, Franklin L.; Kron, Hans H.

doi:10.1007/978-3-642-66319-2_8

Cited by 49 publications

(63 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In 1976, De Remer and Kron [10] published their seminal paper on "programming in the large" versus "programming in the small". This paper gave us the means of talking about systems at two levels, the level of job control language (JCL) and the level of sequential programs that were controlled by the JCL.…”

Section: Software Architecturementioning

confidence: 99%

An Introduction and History of Software Architectures, Components, and Reuse

Barroca¹,

Hall²,

Hall³

2000

Software Architectures

View full text Add to dashboard Cite

SummarySoftware components and architectures are gaining considerable support as the way to develop object-oriented systems and business applications. Current developments in component-based software reuse is taking place in the context of some thirty years of history. It is as well to rehearse that history, as we do in this chapter, and draw lessons from it, lest we repeat the errors of the past.This chapter fills in the background to the rest of the book. Concepts and ideas assumed in the other chapters will be explained and set in a context which will aid the reading and understanding of those chapters. The specialist reader already conversant with the field may wish to skip this chapter, though it is hoped that even for such a reader the orientation adopted here will be informative and helpful.

show abstract

Section: Software Architecturementioning

confidence: 99%

An Introduction and History of Software Architectures, Components, and Reuse

Barroca¹,

Hall²,

Hall³

2000

Software Architectures

View full text Add to dashboard Cite

show abstract

“…Descriptions of the constituent software components and their interconnection patterns provide a clear and concise level at which to specify and design systems, and can be used directly by construction tools to generate the system itself. This approach has been variously referred to as "programming-in-the-large" [3], component-based system building using module interconnection languages [9,20], and "configuration programming" [15,18]. Furthermore, evolution of the system can be achieved by making extensions or changes to the system configuration by the addition or replacement of components [16].…”

Section: Learning From Software Configurationmentioning

confidence: 99%

“…Messages are sent out via exitports and received from entryports. The type definitions for messages and ports are imported from definition modules by the use clause bed alarm patient bed [5] bed [4] bed [3] bed [2] bed [1] a l a r m [ 5 ] a l a r m [ 4 ] a l a r m [ 3 ] a l a r m [ 2 ] a l a r m [ 1 ] nurse group module patient; group module nurse (maxbed:integer=5); …”

Section: Component Types : -Provision Of Context-independent Componenmentioning

confidence: 99%

“…bed [3] bed [4] bed [5] bed [1] a l a r m [ 2 ] a l a r m [ 3 ] a l a r m [ 4 ] a l a r m [ 5 ] system ward; create bed1:patient; nurse: nurse; link bed1.alarm to nurse.alarm [1]; nurse.bed [1] to bed1.bed; end .…”

Section: Constructing Systems In Conic: -Component Instantiation and mentioning

confidence: 99%

“…This would complicate the provision of support for dynamic configuration and the user/management view of the system, both of which are discussed below. change ward; create bed2:patient; link bed2.alarm to nurse.alarm [2]; nurse.bed [2] to bed2.bed; end bed [3] a l a r m [ 5 ] a l a r m [ 4 ] a l a r m [ 3 ] a l a r m [ 1 ] bed alarm bed alarm nurse bed2 bed1 bed [4] bed [5] bed [1] bed [2] a l a r m [ 2 ] In addition to programming initial configurations, the Conic toolkit permits dynamic configuration: changes to running systems. For example, extending the above system to include an additional patient unit can be performed by submitting the configuration change of the system 'ward' (figure 5) to a configuration manager.…”

Section: Figure 4 Initial Patient Monitoring Systemmentioning

confidence: 99%

See 2 more Smart Citations

A configurable framework for method and tool integration

Kramer

Finkelsteiin

1991

Software Development Environments and CASE Technology

View full text Add to dashboard Cite

There is an urgent need to provide a sound generic framework for method and tool integration, where many differing notations are used, software development is distributed and management support for the software development process is provided. This paper argues that there is much to be learnt from proven practical techniques for software construction, particularly those that support distributed software integration, heterogeneity and software management. Configuration Programming is one such approach which advocates the use of a separate, declarative configuration language for the description of system structure. It has been used in the Conic Environment for the development of distributable software, and is being extended for the configuration of heterogeneous components programmed in different programming languages. A number of software tools exist for the development, construction and management of Conic systems. This paper shows how an analogous set of the principles, practice and tools from configuration programming can be combined with recent work on ViewPoints 1 to provide a configurable framework for method and tool integration.

show abstract

Synchronous/Reactive Programming of Concurrent System Software

Montague

McDowell

1997

Softw: Pract. Exper.

View full text Add to dashboard Cite

SUMMARYSynchronous languages are intended for programming reactive systems. Reactive systems, which include real-time systems and key operating system components, interact continually with their environment. This paper considers the applicability of imperative synchronous/reactive languages to the development of general system software, that is, to the implementation of operating system kernels, file systems, databases,networks, server architectures, device drivers, etc. The languages Esterel and Reactive C (RC) receive special attention as Esterel is the oldest and most developed such language and RC is specifically designed for compatibility with C systems programming. An alternative soft-instruction software architecture is described, which is well suited to real-world system programming.

show abstract

Programming-in-the-Large Versus Programming-in-the-Small

Cited by 49 publications

References 4 publications

An Introduction and History of Software Architectures, Components, and Reuse

An Introduction and History of Software Architectures, Components, and Reuse

A configurable framework for method and tool integration

Synchronous/Reactive Programming of Concurrent System Software

Contact Info

Product

Resources

About