E W Dijkstra, "The Structure of THE Multiprogramming System," Communications of the ACM 11(5) (May 1968).  Home/Search   Document Not in Database   Summary   Related Articles   Check

....which uses an annotation language to capture semantic information about the abstractions present in software libraries. 1 Introduction Layering has long been used to simplify the design of software systems. Layering helps decompose systems into manageable pieces, and creates reusable modules [6]. Developers of large scientific software systems have come to depend more and more on layering, since such systems tend to represent a broad spectrum of specialized programming domains. For example, the POOMA framework consists of five layers [16] with the higher layers representing abstractions ....

E. W. Dijkstra. The structure of the THE multiprogramming system. Communications of the ACM, 9:27--37, 1976.

....This research was supported in part by a Cisco Distinguished Graduate Fellowship. to reduce the probability of failure, but we found little guidance on how to represent and propagate errors through autonomous layers of software. This surprised us, given that layering is a well established concept [11, 45], that errors have been identified as an obstacle to user interaction [12, 24] and that many languages provide specialized error constructs such as exceptions [32, 23, 27] Naturally, error propagation is well understood when all the components of a system are available for inspection and ....

E. W. Dijkstra. The structure of the THE multiprogramming system. In Proceedings of the ACM Symposium on Operating System Principles (SOSP), Gatlinburg, Tennessee, October 1967.

....wosch ivs.cs.uni magdeburg.de Abstract If there are areas of computer science that were left behind by the market, operating systems is certainly one of them. The products currently available in the area, namely Microsoft WINDOWS and UNIX, owe their designs to projects such as THE [1] and MULTICS [4] which are at least 30 years old. In the meanwhile, several new hacks have been proposed, but very few systems brought about revolutionary designs. The partitioning of the problem domain in abstractions like process and file is so old that some people regard it as a canonical ....

Edsger Wybe Dijkstra. The Structure of the THE-Multiprogramming System. Communications of the ACM, 11(5):341--346, May 1968.

....management as well. 4. An Aspect Oriented Framework for Operating Systems In [14, 15] AOP is viewed as a general framework for separating the concerns in the system. Dijkstra introduced the layered approach for the design and implementation of operating systems such as the THE operating system [6] and the MULTICS system [18] The layered approach, consisted of layers and components, has showed all the advantages of the modular design. Our observation suggests that an aspect oriented software architecture (AOSA) that uses aspect oriented frameworks could support designers and programmers in ....

Dijkstra, Edsger W., The structure of THE multiprogramming System, Communications of ACM, pp.341-346, May 1968.

....of concerns. A key factor in this inability is inadequate techniques for organizing concerns and defining their composition. Ideally, each concern is encapsulated as a single, self contained software module. Several mechanisms for defining modules are in common practice. These include layering[1], stepwise refinement[2] and information hiding[8] These mechanisms underlie much of the progress in software engineering, and they are fundamental to the notion of objectoriented programming. An important insight is that standard practice allows only some concerns to be separated. The ....

E. W. Dijkstra, The Structure of the THE-Multiprogramming System, Communications of the ACM, 11(5): 341-346, May 1968.

....as follows (Garlan and Perry 1995) The structure of the components of a program system, their interrelationships, and the principles and guidelines governing their design and evolution over time. The roots of software architecture may be found in early studies of software structure (see Dijkstra 1968), which were given further impetus by work related to information hiding, structures and program families (Parnas 1974; Parnas 1976; Parnas 1972) The advantage of evolving the latter in a given domain is primarily that of the economics of the reuse of common assets of design, source code, test ....

Dijkstra, E. W. (1968). The Structure of the THE Multiprogramming System. Communications of the ACM, 11 (5), pp. 341-346.

....wosch ivs.cs.uni magdeburg.de Abstract If there are areas of computer science that were left behind by the market, operating systems is certainly one of them. The products currently available in the area, namely Microsoft Windows and Unix, owe their designs to projects such as The [Dijkstra, 1968] and Multics [Organick, 1972] which are at least 30 years old. In the meanwhile, several new hacks have been proposed, but very few systems brought about revolutionary designs. The partitioning of the problem domain in abstractions like process and file is so old that some people regard it as a ....

Dijkstra, E. W. (1968). The Structure of the THE-Multiprogramming System. Communications of the ACM, 11(5):341346.

....Mike Mislove and Steve Brooks for inviting us to present our results at MFPS. O Hearn and Pym were partially supported by the EPSRC. Yang was supported by NSF grant INT 9813854. 1 the pivotal notion of resource sharing that occurs when different computations reference the same resource [5, 4, 6]. Examples of shared resources include storage, files, external devices and processor time. Our approach in this paper will be to take resource as a primitive in our proposed semantics. The basic idea is to use a possible worlds formalism, where the worlds are thought of as resources, or ....

E. Dijkstra. The structure of the THE-multiprogramming system. In Communications of the ACM, pages 341--346. ACM, 1968.

....Some examples of explicit formulae illustrate the results. Keywords: Dining Philosophers Problem, Markov field, reversible measure, partition function. 1 1 INTRODUCTION. Many different ways of modelling resource sharing situations have been proposed. Dijkstra s Dining Philosophers Problem [2] is one of the first systematic attempts in the area. It describes a situation where the users (philosophers) are the vertices of a graph the edges of which (chopsticks) represent resources. When one of the users starts working, he needs all available resources (adjacent edges) and therefore none ....

E. W. Dijkstra. The structure of the multiprogramming system. Comm. ACM, 11:341--346, 1968.

....L2. File access layer based on a schema and multiindexed files. L1. System services for management of external storage. Mandatory Security Boundary L0. Operating system and hardware. These layers provide guidelines for defining abstract machines in the sense of Edsger Dijkstra [Dijk 66,71] but do not provide the granularity needed for the decomposition of a large software system into modules that lend themselves to independent development, reuse, and replacement. 1.5. Concepts On reflection, it appears that the architectural approach proposed here, as a conceptualization of ....

E.W. Dijkstra: "The Structure of the the Multi-programming System"; CACM, Vol.9 No.3, pp.143--346, May.1966.

....to shared information or to access distributed information. The interaction between the synchronization primitives is defined at the action level. All interactions are constructed from suitable combinations of these primitives. Examples of unstructured synchronization primitives are semaphores [Dij65, Dij68], message passing primitives [Hoa78, Per87] and write once shared variables [Sha89, FT89] of logic programming languages. Interactions among programs in these languages are realized indirectly through the executions of suitable synchronization primitives. The synchronization primitives are at a ....

E. W. Dijkstra. The Structure of the THE Multiprogramming System. Communication of the ACM, 11(5):341--346, 1968.

No context found.

E.W. Dijkstra, "The Structure of the THE Multiprogramming System," Comm. ACM, vol. 11, no. 5, pp.341-346, 1968b.

No context found.

E W Dijkstra, "The Structure of THE Multiprogramming System," Communications of the ACM 11(5) (May 1968).

No context found.

E. Dijkstra. The structure of the - multiprogramming system. Communications of the ACM, 11(5):341--346, May 1968.

No context found.

Dijkstra, E.: The structure of THE multiprogramming system. Communications of the ACM 11 (1968) 341--346

No context found.

Dijkstra, E.: The structure of THE multiprogramming system. Communications of the ACM 11 (1968) 341--346

No context found.

E.W. Dijkstra. The structure of THE-multiprogramming system. Communications of the ACM, 11(5), 1968.

No context found.

E. W. Dijkstra. The Structure of the THE Multiprogramming System. Communications of the ACM, 11(5):341--346, May 1968.

No context found.

E.W. Dijkstra. The structure of the THE multiprogramming system. Communications of the ACM, 11(5), May 1968.

No context found.

E.W. Dijkstra. The structure of the THE multiprogramming system. Communications of the ACM, 11(5), May 1968.

No context found.

Dijkstra, E.: The structure of THE multiprogramming system. Communications of the ACM 11 (1968) 341--346

No context found.

Edsger W. Dijkstra. The structure of the THE multiprogramming system. Communications of the ACM, 9:27--37, 1976.

No context found.

E. W. Dijkstra. The Structure of the THE Multiprogramming System. Communication of the ACM, 11(5):341--346, 1968.

No context found.

E. W. Dijkstra, `The structure of the THE multiprogramming system', Communications of the ACM, 11 (5), 341--346 (1968).

No context found.

Edsger W. Dijkstra. The structure of the THE-multiprogramming system. Communications of the ACM, 11(5):341--346, May 1968.

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