M.D. McIlroy. Mass produced software components. In P.Naur and B. Randel, editors, NATO Conference on Software Engineering. NATO Science Commitee, Oktober 1968.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....ground up, software applications are expected to utilize functionalities provided by existing service components. Commercial off theshelf (COTS) software applications and other information services are the building blocks that provide pieces of functionalities. This vision of software composition [15] is echoed in the megaprogramming framework [5, 25] which builds on software components called megamodules [18] that capture the functionality of autonomous services provided by large organizational units. Autonomous services are linked together according to composition specifications [19, 23] to ....

M. D. McIlroy, "Mass Produced Software Components", Software Engineering, NATO Science Committee, January 1969, pp. 138-150.

....thus provide for a high level of reusability and dynamic adaptability. This can also enable formal modelling with the support of UML. We further discuss issues that arise in order to obtain CAOTS. 2. SUPPORT FOR CAOTS Although a clear distinction between a component and an aspect was provided in [12, 16], programming languages and tools deployed to enforce AOSD have yet to provide a mechanism (abstraction level) with which CAOTS can be achieved. We believe that a means to group (modularize) as well as to define the behavior of an aspect, will be a step in this direction for the following ....

....of tangled code. Most of them mentioned in this context are AspectJ [2] implemented by those people who actuated the term aspect oriented programming [11] HyperJ [14] which is an offspring of subject oriented programming (SOP, 10] DemeterJ [6] whose foundation came from adaptive programming [12] and composition filters [1] More recent proposals include for example logical meta programming [16] or different mixin mechanisms like destructive mixins [15] or per object mixins [13] Although there are already some comparisons between different approaches like AspectJ and HyperJ (cf. e.g. ....

[Article contains additional citation context not shown here]

M. D. McIlroy. Mass-produced software components. In P. Maur and B. Randell, editors, Engineering Concepts and Techniques, Proceedings of 1968 North Atlantic Treaty Organisation (NATO) Conference on Software Engineering Garmisch-Partenkirchen, pages 138 -- 150. NATO Science Commitee, Jan 1976.

.... Reuse aims at increasing the productivity and quality in large scale software development [130] The productivity of software development can be increased because for the development of a new system not all software needs to be developed from scratch but existing artifacts can be used (as is) [103]. The quality of software can be increased because proven technology can be reused [73] Software reuse is not limited to source code fragments, but may include documentation, specification, design structures and so on [61, 92] In this thesis we concentrate on reuse of source code fragments ....

....a collaborative development activity because different parts of a system are developed by different people at different institutes. In 1968 McIlroy was the first to recognize this and to distinguish manufacturers which are producers of reusable components and system builders that use them [103]. He suggested mass produced software components by a software component sub industry consisting of software manufacturers dedicated primarily to the development of reusable software components. This distinction of manufacturers and system builders yields two complete development cycles: ....

D. McIlroy. Mass-produced software components. In P. Naur and B. Randell, editors, Software Engineering, NATO Science Committe report, pages 138--155, 1968.

....message, the protocol transits to the Sending state and the server broadcasts the message to every connected client (clients#, with newMessage(Message) 2. 2 Life cycle of a component The life cycle of a component has five main phases: Design, implementation, assembly, deployment, and run time [10,2]. Component specifications are defined during the design phase. The specifications expressed as protocols are integrated in the component implementation, during the implementation phase. We call the protocol specifying the behavior of a given component, at the design level, a design level ....

McIlroy, M., Mass produced software components, in: Proceedings of the NATO Conference on Software Engineering (1968), pp. 138--155.

....normalize variability in industrial software systems. The method is exemplified by applying it to the software product line of the aforementioned company. 1 Introduction The notion of constructing software systems by composing software components and a family of software products is not recent [23][25] Combining both concepts has resulted in approaches towards software design that share the ability to delay design decisions to a later phase in the development process [19] 20] The recent emerge of software product lines provides an example of delayed design decisions. The core idea of ....

M. D. McIlroy. Mass Produced Software Components. Report on a conference of the NATO Science Committee, 1968, 138-150.

....from pre existing software building blocks. What differs is the types of building blocks envisioned for each paradigm. Information hiding and data abstraction. Composing software from reusable artifacts has been a goal of software researchers for over three decades. For example, Doug McIlroy [15] motivated the need for software integrated circuits (ICs) and mass produced software ICs, as well as examines the types of variability needed in software ICs and the types of ICs that can be standardized usefully. McIlroy envisioned an IC to be a standard catalogue of routines, classified by ....

M. D. McIlroy, "Mass Produced Software Components," in Proceedings of the NATO Software Engineering Conference, Oct. 1968.

....be recognized by an industry that measures productivity in terms of positive lines of code per day. 2.2 Are Components the Solution Although object is not yet a four letter word, component seems to be the current buzz. But components, like objects, have also been around since the sixties [14]. Szyperski defines a software component as a unit of independent deployment, a unit of third party composition, that] has no persistent state [19] Clearly this definition can fit many di#erent kinds of software entity. Whether we call it a component or a library or a framework or an ....

M. Douglas McIlroy. Mass produced software components. In P. Naur and B. Randell, editors, Software Engineering, pages 138--150. NATO Science Committee, January 1969.

....surprising that people developed the vision that the future of software engineering lies in the use of reusable components: new applications would be built by selecting from a set of existing components and then clicking or gluing them together. McIlroy was one of the first to advocate this idea [16], and many have followed since. We have indeed seen some successes in this area, for instance the use of ActiveX controls (components) and Visual Basic (glue) to quickly build interactive applications for PCs. But we have also seen many failures, especially when applied within companies to create ....

M. D. McIlroy, Mass produced software components, Proc. Nato Software Eng. Conf., Garmisch, Germany (1968) 138-155.

....Contracts for . 102 Introduction Modern software development often requires collaboration between independently operating groups of developers. These developers publish components and extensions that others combine to form a working system. McIlroy [39] first proposed the idea of software components in 1969. In a marketplace with reusable components, software manufacturers would produce software components with well specified interfaces. Developers would assemble systems from these off the shelf components, possibly adapting some with wrapper ....

McIlroy, M. D. Mass produced software components. In Naur, P. and B. Randell, editors, Report on a Conference of the NATO Science Committee, pages 138--150, 1968.

....describes our thesis a prescription for language designers who wish to support black box reuse and two novel language constructs that illustrate the thesis. Section 1.3 provides an overview of the rest of the dissertation. 1. 1 Reuse without Source Code At the 1968 NATO conference, McIlroy [59] described component reuse in its ideal form, a world where programmers construct software using off the shelf components that are supplied by a software components industry. This off the shelf approach should also work within a development team, where each part of the team supplies components to ....

....Figure 5.2 : Unit structure of DrScheme with linking i i i i i i i H H H Z Z Z Z Z Z Z Z Q Q Q Q Q Q Q c c c c b b b b j j j j # # # # H H H H Figure 5. 3 : Local unit structure in DrScheme 102 Chapter 6 Related Work on Software Components McIlroy [59] first crystallized the idea of software components produced by a softwarecomponents industry. More recently, Weide et al. 83] and Szyperski [79, 80] substantiate the need to base reusable components on compiled code rather than source code. Szyperski [79] further points out that reuse of ....

McIlroy, M. D. Mass produced software components. In Naur, P. and B. Randell, editors, Report on a Conference of the NATO Science Committee, pages 138--150, 1968.

....employ very different configurations. The component interfaces, consequently, need to be prepared for being bound to various interfaces and may need to be able to cope with smaller mismatches. Example. Philips Consumer Electronics presents an excellent example of this approach. As discussed in [9], Philips has adopted an approach where a set of components can be used to derive a variety of different products, including analog televisions, digital televisions, video recorders and digital set top boxes. A number of teams around the world develop components that adhere to the defined ....

....for the specific context in which these are used. Due to the size of the overall system, the hierarchical domain engineering unit model is typically employed. 6 Related Work Software reuse is a long standing ambition of the software engineering community, dating back to the late 1960s [9] and 1970s [11] The increasing popularity of the object oriented paradigm during the 1980s lead to the definition of object oriented frameworks. As part of this work, for instance, the REBOOT project defined reuse maturity levels [7] Also, Roberts and Johnson [12] discuss a number of maturity ....

M. D. McIlroy, `Mass Produced Software Components,' in `Software Engineering,' Report on A Conference Sponsored by the NATO Science Committee, P. Naur, B. Randell (eds.), Garmisch, Germany, 7th to 11th October, 1968.

....di#erent potential specialisations of the variability. Moreover aspects may be used to implement the dependencies between di#erent flexible elements. 1 Introduction The intention of software reuse is rather old. Already at the NATO science conference on software engineering D. McIlroy stated [12]: Software engineers should take a look at the hardware industry and establish a software component subindustry. The produced software components should be tailored to specific needs but be reusable in many software systems. One way to reuse code which comes McIlroy s vision very close is ....

M. D. McIlroy. Mass-produced software components. In P. Maur and B. Randell, editors, Engineering Concepts and Techniques, Proceedings of

....the current practice of object oriented programming, although how this can be done is much less obvious. One recent proposal for such an improvement is the idea of componentoriented programming [41] While various forms of components have been proposed in the past starting in the late 1960s [27] this latest incarnation focuses on the distributed extensibility of software. A software system is extensible in a distributed fashion if extensions can be (a) developed by anyone and (b) integrated at any time. In contrast to the standard notion of extensibility, this rules out a central ....

M. Douglas McIlroy. Mass-produced software components. In Proceedings of the NATO Software Engineering Conference, pages 138--155, Brussels, Belgium, October 1968.

....kinds of valuable learning experiences. The question was how the experience of past students could be passed on to future students. This led us to investigate how software reuse could be implemented in this student environment. Software reuse was introduced in the literature in 1968 by McIlroy [19]. The initial focus was on reusing code components and much has been written about how components may be identified, indexed and retrieved. A good summary is given by Krueger [15] The definition of components has been extended to include any artifact of the software development process including ....

McIlroy, M. D., "Mass produced software components". In Software Engineering; Report on a Conference by the NATO Science Committee (Garmisch, Germany,Oct). Naur, P., and Randell, B., Eds. NATO Scientific Affairs Division, Brussels, Belgium , 1968 pp. 138150.

....programming is and certainly none on how to do component oriented programming. The number of approaches and technologies that have been proposed for component oriented programming in the past provide ample evidence of this. With the publication of Douglas McIlroy s classic paper [13] in 1968, software components became a silver bullet for software engineering [2] and reappeared regularly through the decades. Components in this classic sense are primarily concerned with reuse, either in the form of buying needed components cheaper than their development cost, or in the ....

M. D. McIlroy. Mass-Produced Software Components. In Proceedings of the NATO Software Engineering Conference, pages 138--155, Brussels, Belgium, Oct. 1968.

....programming is and certainly none on how to do component oriented programming. The number of approaches and technologies that have been proposed for component oriented programming in the past provide ample evidence of this. With the publication of Douglas McIlroy s classic paper [13] in 1968, software components became a silver bullet for software engineering [2] and reappeared regularly through the decades. Components in this classic sense are primarily concerned with reuse, either in the form of buying needed components cheaper than their development cost, or in the ....

M. D. McIlroy. Mass-Produced Software Components. In Proceedings of the NATO Software Engineering Conference, pages 138--155, Brussels, Belgium, Oct. 1968.

....and how the various advancements fit together in a coherent way. We conclude with adoption guidelines and a discussion of the work that lies ahead. 1. Introduction For quite some time now there has been an explicit recognition of the need for building software based on reusable components [1]. In spite of the amount of work to date focusing on software technology to achieve high levels of reuse, most notably object oriented approaches, software reuse has remained an elusive goal. Quite simply, the great majority of software practitioners today still develop applications according to ....

McIlroy, D. Mass produced software components. NATO Conf. On Software Engineering. (1968) pp-138-155.

....vs. Objects Luigia Petre Turku Centre for Computer Science (TUCS) FIN 20520 Turku, Finland lpetre abo.fi Component based software engineering [5, 6] means constructing new systems from already existing, service providing components. Object based software engineering [2, 3] means constructing a new system in terms of interacting, distinct units of information and services called objects. Both components and objects have encapsulation ....

M. C. McIlroy. Mass Produced Software Components. In Proc. of NATO Conference on Software Engineering, Garmisch, Germany, 1968.

....Products must be developed to realize the benefits of the product line. A promising approach is to use component based development to realize the products. It has long been recognized that it is beneficial to develop large software programs by dividing the programs into several smaller components [McIlroy 1969], that together perform the task at hand. In product lines an attractive approach is to componentify the features as components and instantiating the products by integrating the components that implement the wanted features. There is however several problems that prohibit this in practice. ....

McIlroy, M.D., Mass produced software components. In Software Engineering: Concepts and Technologies, Buxton, J.M., Naur, P., Randell, B. (eds). Petrocelli/Charter Publishers Inc. (1976): New York NY; 8898.

....contracts between the components. Our mixin mechanism is realized with aspects according to the Aspect Oriented Programming (AOP) principles. 1 Introduction The idea to build software from components has been proposed by D. McIlroy on the NATO conference at Garmisch Partenkirchen in 1968 [8]. Software should be manufactured like machines, i.e. it should be built from separate components which are provided by third party vendors. These components may be also reused in a large number of systems [23] In this paper we introduce an abstract component architecture model (Component ....

McIlroy, M. D.:Mass-produced software components. In Software Engineering Concepts and Techniques, Proceedings of

....may be a flexible mechanism for creating different but consistent views on a complex system. Ideas for concrete tool support based on the Object Constraint Language (OCL) are sketched. 1 Introduction Building software from pre fabricated components has been discussed since a long time (e.g. McIlroy68, Cox90] as the ultimate breakthrough towards industrial production of software. It took until the end of the 90s that a number of technologies have appeared, mainly based on object oriented principles, which make the component based construction of complex software practically viable. A good ....

M. D. McIlroy, Mass produced software components, Proc. Nato Software Eng. Conf., Garmisch, Germany (1968) 138-155.

....words and phrases: domain analysis, software architecture, software reuse, configuration space, version space, refinement, software component, software process, glue code. 1. Introduction The research on software construction from component parts began shortly after it s suggestion by McIlroy [16] at the 1968 NATO conference founding Software Engineering. In the 1970 s Software Engineering (SE) research primarily focused on the difficulties of developing systems in the traditional way of new development within large groups. Some early work within Software Engineering [9] attempted to ....

McIlroy, D., Mass Produced Software Components, in Software Engineering, Naur, P., and Randell, B., eds., NATO Science Committee Report, pp. 138-155, Germany, 1968.

....hierarchies is so difficult that none of the existing contract monitoring tools correctly assign blame for these failures. In this paper, we show how to overcome these problems in the context of Java. Our work is based on the notion of behavioral subtyping. 1. INTRODUCTION In 1969, McIlroy [19] proposed the idea of reusable software components. In a marketplace with reusable components, software manufacturers would produce software components with well specified interfaces. Programmers would assemble systems from these off the shelf components, possibly adapting some with wrapper code ....

McIlroy, M. D. Mass produced software components. In Naur, P. and B. Randell, editors, Report on a Conference of the NATO Science Committee, pages 138--150, 1968.

....domain at a later time. The ultimate goals of software reuse are to improve the quality of software produced, reduce costs of software development, and increase the productivity of software developers. The importance of reusing software components in software development has long been recognized [McIlroy 68a] The current low level of software reuse stems from the difficulties of obtaining appropriate components for populating a reuse library. In this paper, we describe an approach to acquire reusable software components and present the framework for this approach. We then detail the steps taken to ....

M.D. McIlroy, "Mass-Produced Software Components," in Software Engineering Concepts and Techniques, Proc. NATO Conf., Software Engineering, pp. 88 - 98, 1968.

....for unit lang. 97 Chapter 8 Related Research Man invented language to satisfy his deep need to complain. Lily Tomlin Components are typically de ned as separately compilable, externally connected, independently deployable and multiply instantiable units of black box reuse [54] McIlroy [41] introduced the concept of a factory of software components in 1968. Components are gaining prominence with the growing popularity of protocols such as COM, CORBA and JavaBeans, all of which provide some form of component based reuse. Proponents of this technology envision each component being ....

McIlroy, M. D. Mass produced software components. In Naur, P. and B. Randell, editors, Report on a Conference of the NATO Science Committee, pages 138-150, October 1968.

....competitive and dynamic field of software development implies the need to continuously increase the efficiency of the construction and evolution of software products. For a long time reuse of software artifacts in general and of standard components in particular have been promising approaches [McI76][Sch94] to achieve this goal through the consequent and efficient exploitation of the commonalities among produced software artifacts. However, there are inherent problems with both techniques. Firstly, software artifacts have to be made sufficiently abstract to be reusable, i.e. to be applicable ....

McIlroy, M.D.: Mass-produced software components, Software Engineering: Report on a Conference by the NATO Science Committee, (Naur, P.; Randell, B., eds.). NATO Scientific Affairs Division, Brussels, 1976

....of the user application to the interfaces of the components. 2.2 Component Technologies Researchers have been investigating the use of components and component based systems for a number of years. McIlroy first introduced the idea of components as a solution to the software crisis in 1968 [13]. Although the idea of components has been around for some time, only in the last few years has component technology become mature enough to be e#ectively used. Today, several component models, component frameworks, middleware, design tools, and composition tools are available, which allow for ....

D. McIlroy. Mass-produced software components. In Proceedings of the 1st International Conference on Software Engineering, Garmisch Pattenkirchen, Germany, pages 88--98, 1968.

No context found.

M.D. McIlroy. Mass produced software components. In P.Naur and B. Randel, editors, NATO Conference on Software Engineering. NATO Science Commitee, Oktober 1968.

No context found.

M.D. McIlroy. Mass produced software components. In P.Naur and B. Randel, editors, NATO Conference on Software Engineering. NATO Science Commitee, Oktober 1968.

No context found.

M.D. McIlroy. Mass produced software components. In P.Naur and B. Randel, editors, NATO Conference on Software Engineering. NATO Science Commitee, Oktober 1968.

No context found.

M. D. McIlroy. Mass-Produced Software Components. In J. M. Buxton, P. Naur, and B. Randell, editors, Software Engineering Concepts and Techniques (1968.

No context found.

McIlroy, M. D. (1969), Mass produced software components, in P. Naur & B. Randell, eds, `Proceedings of NATO Software Engineering Conference', Vol. 1, NATO Science Committee, pp. 138--150. Presented at the NATO conference on software engineering, Garmisch, Germany, 7-11 October, 1968.

No context found.

M.D. McIlroy. Mass produced software components. Report on the NATO Software Engineering Conference, pages 79--87, 1968.

No context found.

M. D. McIlroy, "Mass Produced Software Components", Software Engineering, NATO Science Committee, January 1969, pp. 138-150.

No context found.

McIlroy, M. (1969), `Mass produced software components ', Software Engineering Concepts and Techniques pp. 88--98.

No context found.

M. D. McIlroy, Mass produced software components, in: P. Naur, B. Randell (Eds.), Software Engineering: Report on a Conference Sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October, 1968.

No context found.

M. D. McIlroy, Mass produced software components, in: P. Naur, B. Randell (Eds.), Software Engineering: Report on a Conference Sponsored by the NATO Science Committee, Garmisch, Germany, 7th to 11th October, 1968.

No context found.

M. D. McIlroy, "Mass Produced Software Components," in Software Engineering, P. Naur and B. Randell, Eds. Garmisch, Germany: NATO Scientific Affairs Division, 1968, pp. 138-155.

No context found.

McIlroy, M. D. (1969). Mass Produced Software Components. In Software Engineering: Concepts and Techniques. Edited by P. Naur, B. Randell, and J. N. Buxton, Mason/Charter Publishers, NY, pp. 138-150.

No context found.

McIlroy. Mass produced software components. In P. Naur and B. Randell, editors, Report on a Conference of the NATO Science Committee, pages 138--150, October 1968.

No context found.

M.D. McIlroy. Mass Produced Software Components. In P. Naur and B. Randell, editors, 1968 NATO Conference on Software Engineering, pages 138--155. NATO Science Committee, 1969.

No context found.

M. D. McIlroy. Mass produced software components. In 1968.

No context found.

McIlroy, M. D.: Mass Produced Software Components. In: Naur, P., Randell, B. (eds): Software Engineering: Report on a Conference by the NATO Science Committee. NATO Scientific A#airs Division, Brussels (1968) 138--150

No context found.

McIlroy, M., D., `Mass-Produced Software Components', NATO Science Committee, Garmisch, Germany, 7~11 October 1968

No context found.

M. D. McIlroy, "Mass Produced Software Components", Software Engineering, NATO Science Committee, January 1969, pp. 138-150.

No context found.

M. D. McIlroy. Mass produced software components. In Software Engineering, Report on a conference sponsored by the NATO Science Committee, 1969.

No context found.

M. D. McIlroy. Mass produced software components. In Software Engineering, Report on a conference sponsored by the NATO Science Committee, 1969.

No context found.

M.D. McIlroy, "Mass Produced Software Components, " Software Engineering, P. Naur and B. Randell, eds., NATO Scientific Affairs Division, Garmisch, Germany, 1968, pp. 138--155.

No context found.

M.D. McIlroy, "Mass Produced Software Components," Software Engineering, P. Naur and B. Randell (Ed.), NATO Science Committee, Jan 1969, pp. 138-150.

No context found.

McIlroy, D. (1968). Mass produced software components. In Naur, P., B. Randell (Eds.), Software Engineering, pp. 138-155.

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