M. Shaw. Abstraction techniques in modern programming languages. IEEE Software., pages 10--26, October 1984.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....(at least, for Ada programmers) and formally defined notation [Fra96] to state non functional issues of software systems. This notation improves software understandability, reusability and maintenance, since more information appears in the software itself. In spite of many claims to this effect [Sha84, Win90, MCN92, Jaz95], we do not know of any approach providing a programming language with the same features as ours. There are many non formalised or partial proposals [Mat84, LG86, Win89, CGN94, Sit94, SY94] the results of which are subsumed in our work. Also, CZ90] present a very interesting framework, close to ....

M. Shaw. "Abstraction Techniques in Modern Programming Languages". IEEE Software, 1(10), 1984.

....Representation The description or specification of a system where some aspects are emphasized, while others are suppressed, is called abstraction. A good abstraction emphasizes details that are significant to the task at hand, while it suppresses those details that are insignificant or immaterial [72]. At the highest abstraction level, only general aspects are given, while at the lower levels more and more details are provided. The design rules are abstracted in a similar fashion: the more abstract level design rules are concerned with the 38 general aspects of a design while the more detailed ....

Shaw, M., "Abstraction Techniques in Modern Programming Languages," IEEE Software, Vol. 3x No. 2x pp. 10-26, August 1984.

....framework for dealing with non functionality. A natural way to facilitate the product oriented approach is to define a notation aimed at stating non functional requirements of software in the software itself. Although many researchers have pointed out the convenience of this notation [2, 11, 16, 18, 21], there seem only to be semi formal (even informal) or limited (with respect to the kind of non functional information managed) proposals in the software community. The lack of such a comprehensive and formally defined language has some negative effects on many software development tasks: ....

M. Shaw. "Abstraction Techniques in Modern Programming Languages". IEEE Software, 1(10), 1984.

....more work has be done for the first one than for the second, especially concerning specification languages and, lately, also architectural languages. This happens in despite of the fact that many researchers have pointed out the convenience of non functional features appearing in those languages [5, 15, 18, 19, 22]. In this paper, we are going to propose a way of putting non functional information of software systems into software architectures. So long as we are not interested in a particular software architectural style or notation, we will use an ad hoc language for describing components and connectors, ....

M. Shaw. "Abstraction Techniques in Modern Programming Languages". IEEE Software, 1(10), 1984.

.... relationship) although free interaction is usually restricted (see [Sit92, Fra94] for different proposals to avoid such restrictions) 4 Comparisons As far as we know, there is no proposal for a language with the constructs proposed here, although many researchers have advocated for it [Jaz95, Sha84, Win90]. There are many non formalised proposals [Mat84, LG86] the results of which are subsumed in our work. Also, Win89] presents a case study to deal with boolean NF attributes in an object oriented framework; no other kind of properties are dealt with in her approach. An interesting proposal appears ....

M. Shaw. "Abstraction Techniques in Modern Programming Languages". IEEE Software, 1(10), 1984.

.... languages provide language constructs for separating the specification portion of a module from its implementation, and enforce the constraint that one module can depend only on the specification part of another and can in no way depend on the details hidden in another module s implementation part [15]. This works well using the splittransaction: Bob and Alice simultaneously modify their specifications; the transactions are then split making the new specifications public; finally, Bob and Alice modify their implementations using the new specifications. If we had used simple nested transactions, ....

Mary Shaw. Abstraction techniques in modern programming languages. IEEE Software, 1(4):10--26, October 1984.

....have introduced: A formally defined notation to state non functional issues of software systems. Although some previous work has been done at the process level (see [MCN92] we do not know of any approach at the product level with the same features as ours (in spite of many claims in this sense [Sha84, Win90, MCN92, Jaz95]) There are many non formalised or partial proposals [Mat84, LG86, Win89, CGN94, SY94] which results are subsumed in our work; also, CZ90, CZ91] present a very interesting framework close to ours, but restricted to non functional properties taking numerical values. Our notation leads to a system ....

M. Shaw. "Abstraction Techniques in Modern Programming Languages". IEEE Software, 1(10), 1984.

....Another possible remedy is to extend current programming languages where feasible to allow some design abstractions like certain popular patterns to be implemented directly in the language. In effect, there is a strong trend towards supporting higher and higher design concepts as languages evolve[Sha84] For example, inheritance is a commonly needed design concept that is now an integral part of many languages. Rumbaugh[Rum87] also designed a language in which abstract associations and constraints among objects were first class entities in the language. In the same way, current programming ....

Mary Shaw. Abstraction Techniques in Modern Programming Languages. IEEE Software, October 1984.

.... languages provide language constructs for separating the specification portion of a module from its implementation, and enforce the constraint that one module can depend only on the specification part of another and can in no way depend on the details hidden in another module s implementation part [38]. This works well using transaction restructuring operations: Bob and Alice can modify their specifications at the same time; the transactions are then split making the new specifications public; finally, Bob and Alice can modify their implementations using the new specifications. If we had used ....

Mary Shaw. Abstraction techniques in modern programming languages. IEEE Software, 1(4):10--26, October 1984.

.... pays conscious attention to the family rather than a sequence of individual programs, the overall cost of development and maintenance of the programs will be reduced (parnas 1979) Abstraction in programming in general, and program families in particular, have been around for some time [31]. IBM s OS 360 can be SYSGEN ed for its entire 360 and 370 family of computers using macro processing. The code for operating system routines contained a number of macro references ( calls ) whose parameters and resulting expansion depended on the specific member of the family. ....

Mary Shaw, "Abstraction Techniques in Modern Programming Languages," IEEE Software, pp. 10-26, October 1984.

No context found.

M. Shaw. Abstraction techniques in modern programming languages. IEEE Software., pages 10--26, October 1984.

No context found.

Shaw M, `Abstraction techniques in modern programming languages', IEEE Software, 1(4):10-26, 1984

No context found.

Shaw M, `Abstraction techniques in modern programming languages', IEEE Software, 1(4):10-26, 1984

No context found.

M. Shaw, `Abstraction techniques in modern programming languages', IEEE Software, 1, 10--26 (1984).

No context found.

Shaw, M. Abstraction techniques in modern programming languages. IEEE Softw. , (Oct. 1984), 10-26.

No context found.

Shaw, M. (1984). Abstraction techniques in Modern Programming langages. IEEE Software. October 1984.

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