Parnas, D. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, March 1979, 128-138. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Extracting The Essence Of Flexibility In System Design - Saleh, Hastings, Newman (2001) (1 citation) (Correct)
....above, between two concepts that are potentially to be confused with one another: That of flexibility versus universality of a design. A software for instance that can be used in a variety of situations without change or modification, is considered universal not flexible. Flexible software [23] is one that can be easily changed extended, contracted, or else in order to be used in a variety of ways. Similarly, spacecraft that carry multiple instruments and performs multiple missions simultaneously are NOT considered flexible according to the definition of flexibility provided above. ....
D. Parnas. "Designing software for Ease of Extension and Contraction". IEEE Transactions on Software Engineering, Volume SE-5, Number 2, March 1979. pp. 128-138.
To Reuse or To Be Reused: Techniques for Component Composition.. - de Jonge (2003) (Correct)
....granularity . These are the central themes of this thesis and will be discussed in more detail in the next sections. A component is an abstraction consisting of an abstraction specification or interface that is externally visible, and an abstraction realization or implementation that is hidden [92, 11, 116, 36]. Observe that this is a much broader definition than the one given in [132] where components are defined as binary units. Abstractions are hard to define for generally reusable artifacts because we do not have many universal abstractions available that go beyond the abstraction level of ....
....of composite systems all integration mechanisms can be combined. To make component based software development successful, it should not be difficult to construct composite software systems from a wide range of components with different integration techniques. To that end, component interfaces [11, 116, 14] and standardized exchange formats are essential. Component interfaces serve to make software components interchangeable (plug compatible) by hiding their implementations. Standardized exchange formats are inevitable to easily integrate different types of components (such as executable programs or ....
D. L. Parnas. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, SE-5(2):128--38, March 1979.
Generating Indexed Formal Software Documents - Wang Self-citation (Parnas) (Correct)
....E X Tool Design 29 The program uses relation is used to illustrate the detailed design of TLT in terms of the uses relation between the access programs. Program A uses Program B if there exist situations in which the correct functioning of Program A depends on the correct behavior of Program B [11]. The program uses relation of TLT is shown as a matrix in Figure 4.2. Each program of TLT is identified by an integer (i.e. the program id) Table 4.1 provides the mapping between the program ids and the program names. x in the matrix indicates that the program located in the corresponding row ....
Parnas, D.L., "Designing Software for Ease of Extension and Contraction," IEEE Transactions on Software Engineering, vol. SE-5, no. 2, pp. 128--138, March 1979.
Service-based Processes - Design For Business (Correct)
No context found.
Parnas, D. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, March 1979, 128-138.
Architectures for Service-oriented Processes - Martin Henkel Jelena (Correct)
No context found.
Parnas, D.: Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, (March 1979). 128-138
On the Notion of Functional Aspects in Aspect-Oriented Refactoring - Apel, Liu (2006) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE TSE, SE-5(2), 1979.
Aspectual Mixin Layers: Aspects and Features in Concert - Apel, Leich, Saake (2006) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE TSE, SE-5(2), 1979.
Mixin-Based Aspect Inheritance - Apel, Leich, Saake (2005) (Correct)
No context found.
Parnas, D.L.: Designing Software for Ease of Extension and Contraction. IEEE Transactions on Software Engineering SE-5 (1979)
Using Mixins to Build a Flexible Lightweight Middleware for.. - Apel, Böhm (2004) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE Transaction on Software Engineering, SE-5(2), 1979.
Towards the Development of Ubiquitous Middleware Product Lines - Apel, Böhm (2005) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE Transaction on Software Engineering, SE-5(2), 1979.
Combining Feature-Oriented and Aspect-Oriented.. - Apel, Leich.. (2005) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE Transactions on Software Engineering (TSE), SE-5(2), 1979.
FeatureC++: Feature-Oriented and Aspect-Oriented.. - Apel, Leich.. (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE Transactions On Software Engineering, SE-5(2), 1979.
Aspectual Mixin Layers - Sven Apel Thomas (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE TSE, SE-5(2), 1979.
FeatureC : On the Symbiosis of Feature-Oriented and.. - Apel, Leich.. (2005) (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE TSE, SE-5(2), 1979.
Configurable Binding: How to Exploit Mixins and Design.. - Apel, Sichting, Böhm (Correct)
No context found.
D. L. Parnas. Designing Software for Ease of Extension and Contraction. IEEE Transactions On Software Engineering, SE-5(2), March 1979.
Families of Formal Requirements in Telephone Switching - Bredereke (2000) (1 citation) (Correct)
No context found.
David Lorge Parnas. Designing software for ease of extension and contraction. IEEE Trans. Softw. Eng. SE-5(2), 128--138 (March 1979).
On Feature Orientation and on Requirements Encapsulation Using.. - Bredereke (2004) (Correct)
No context found.
David Lorge Parnas. Designing software for ease of extension and contraction. IEEE Trans. Softw. Eng. SE-5(2), 128--138 (March 1979). Reprinted in [48].
Unknown - (Correct)
No context found.
D. L. Parnas. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, SE-5(2):128--138, March 1979.
Component Design of Retargetable Program Analysis Tools .. - Hayes, Griswold.. (2000) (Correct)
No context found.
D. L. Parnas. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, 5(2):128--138, March 1979.
A Comparison of Jiazzi and AspectJ for Feature-wise.. - Xin, McDirmid, Eide, Hsieh (2004) (Correct)
No context found.
D. L. Parnas. Designing software for ease of extension and contraction. In Software fundamentals: collected papers by David L. Parnas, pages 269--290. Addison-Wesley Longman Publishing Co., Inc., 2001.
Software Economics - Barry Boehm And (Correct)
No context found.
. D.C. Parnas, Designing Software for Ease of Extension and Contraction, IEEE-TSE, March 1979, pp.128-137.
Unknown - (Correct)
No context found.
David L. Parnas. Designing software for ease of extension and contraction. IEEE Transactions on Sofware Engineering, SE-5, 2, 1979.
A Comparison of Jiazzi and AspectJ for Feature-wise.. - Xin, McDirmid, Eide, Hsieh (Correct)
No context found.
D. L. Parnas. Designing software for ease of extension and contraction. In Software fundamentals: collected papers by David L. Parnas, pages 269--290. Addison-Wesley Longman Publishing Co., Inc., 2001.
Programming Language Requirements for the Next Millennium - William Griswold Richard (1996) (Correct)
No context found.
D. L. Parnas. Designing software for ease of extension and contraction. IEEE Transactions on Software Engineering, 5(2):128--138, March 1979.
On the Separation of Concerns in Program Families - Colyer, Rashid, Blair (2004) (8 citations) (Correct)
No context found.
D. L. Parnas, "Designing Software for Ease of Extension and Contraction," IEEE Transactions on Software Engineering, vol. 5, pp. 128-38, 1978.
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