10 citations found. Retrieving documents...
M. Shaw. Toward Higher Level Abstractions for Software Systems. In Proceedings Tercer Simposio Internacional del Conocimiento y su Ingerieria, 1988.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Thoughts on Software Engineering Knowledge, and how to.. - Bagert, Barbacci.. (2002)   (Correct)

....SEEK. In addition to these, a number of issues were identified that received either a scant or a scattered treatment in either or both of SWEBOK and SEEK: Software Architecture. Software architecture has become one of the central topics in software engineering. In early publications, such as [Shaw, 1988], software architecture was by and large synonymous with global design. This is also the view reflected in SWEBOK and SEEK, with their emphasis on (design and architectural) patterns. In a broader view, architecture involves making tradeo#s between quality concerns of di#erent stakeholders. As ....

M. Shaw. Toward Higher Level Abstractions for Software Systems. In Proceedings Tercer Simposio Internacional del Conocimiento y su Ingerieria, 1988.


Augmenting Design Patterns With Design Rationale - Vadhavkar (1996)   (4 citations)  (Correct)

....by domain experts [39] However it should be noted that building of reusable software components is 14 only a small part of the whole reuse effort. It is being realized that effective software reuse requires more than building easy to browse, well cataloged, convenient software components [31] and [17] There are several issues in making a component based approachtosoftware design work in practice. First, a reusable componentmust have a formal (but still human comprehensible) specification to say what it does. No software designer can be expected to use a component without a complete ....

....to provide the software designer with clear requirements and design alternatives that can help in solving the problem and make the reuse effort worthwhile. There is a growing consensus, that simply providing 52 a library of reusable software artifacts is insufficient for supporting software reuse [31] and [17] Tomake reuse worthwhile, the library of components should be used within well defined and well understood domains. To date, little research has been focused on the developmentoftechniques for discovering workable patterns that can be captured, formalized, indexed and quantitatively ....

M Shaw. Towards higher level of abstractions for software systems. Data and Knowledge Engineering, 5:119--128, May1990.


Design Rationale and Design Patterns in Reusable Software.. - Peņa-Mora, Vadhavkar (1996)   (1 citation)  (Correct)

.... support for software design has focused on issues concerned with the synthesis and development of reusable software components (Smith, 1990) It is now being realized that, effective software reuse requires more than building an easy to browse, well cataloged, convenient software components (Shaw, 1990) and (Lubars, 1991) Methodologies combining catalogs of standardized software components and corresponding retrieval tools with models that capture and retrieve relevant design rationale need to be formalised. The goal of reuse research should be to establish a software engineering discipline ....

Shaw, M :1990. Towards Higher-Level Abstractions for Software Systems, Data and Knowledge Engineering, 5, pp 119-128.


Architecture-driven Reuse of Code in KASE - Bhansali (1993)   (Correct)

.... (e.g. Barstow, 1979; Smith, 1990) It is now being realized that in order to support the synthesis of large, complex systems, we also need to focus on design problems that go beyond the level of algorithms and data structures (Bhansali Nii, 1992b; Graves, 1991; Lubars, 1991; Mettala, 1990; Shaw, 1990) . This has been called the architectural level of design. In the KASE (Knowledge Assisted Software Engineering) project we have developed an approach for providing automated support to a software designer in designing software systems at the architectural level. In brief, our approach can be ....

Shaw, M. (1990). Toward higher-level abstractions for software systems. Data & Knowledge Engineering , 5, 119-128.


The Interaction Between Static Typing and Frameworks - Gail Murphy And (1993)   (1 citation)  (Correct)

....Frameworks [Deu89, JF88, NGT92] are one of several approaches to reducing the cost of building complex applications by exploiting commonalities between related applications. Several properties distinguish frameworks from the other approaches. First, in contrast to software architectures [Sha90] which primarily focus on the common aspects of the specification of the members of a family, frameworks capture key aspects of the design and implementation of the members. Second, in contrast to application generators, which define a special purpose language for specifying the details of the ....

....When a framework is reused in this manner, both the design and implementation are reused. A framework thus provide reuse at a finer granularity than the transformation based approach and may be reused in multiple different ways. Software Architecture: Research into software architecture [Sha90] focuses on developing more formal descriptions of the structure of a software system. This involves the use of existing formal notations [AG92] and the development of new notations and languages for describing the components and interactions between components of a software system [AAG93] In ....

Mary Shaw. Toward higher-level abstractions for software systems. Data & Knowledge Engineering, 5:119--128, 1990.


A Formal Approach to Software Architecture - Allen (1997)   (107 citations)  (Correct)

....connectors in WRIGHT, we have contributed to an improved understanding of a connector as a pattern of interaction. Connectors have been a key, but informal, element of the concept of software architecture almost from the moment software architecture was introduced as a term (see, for example [Sha88] WRIGHT is the first notation to provide mechanisms Chapter 10. Conclusion 199 for the explicit characterization of the semantics of a connector and to define the meaning of that characterization in system composition. ffl Style as Predicate Over Sets of Configurations: We have provided an ....

Mary Shaw. Toward higher-level abstractions for software systems. In Proc. Tercer Simposio Internacional del Conocimiento y su Ingerieria, pages 55--61, October 1988.


Design Theory and Software Design - McPhee (1997)   (Correct)

....with uncertain or incomplete requirements are more likely to use less formal techniques. Today, close to thirty years after the NATO conference, the demand for timely delivery of reliable, complex, high quality software systems still strains the ability of the computing community to provide them [188] [200] Why is this so Has nothing happened during those thirty years The answer, of course, is that a great deal of progress has been made in the industry s ability to deliver complicated software systems. Systems developed today are many orders of magnitude more complex than their counterparts ....

Shaw, M., "Toward higher-level abstractions for software systems," Data and Knowledge Engineering, vol. 5, 119-128, 1990.


The Coming-of-Age of Software Architecture Research - Shaw (2001)   (8 citations)  Self-citation (Shaw)   (Correct)

....the informal knowledge about common software structures, or architectural styles, that can be used in a variety of problem domains. This work cataloged existing systems to identify common architectural styles such as pipe filter, repository, implicit invocation, and cooperating processes [3] 5] 48][54]. These complementary lines of research led to models for explaining the architectural styles and to two widely cited papers in 1992 and 1993 that established the structure of the field [21] 51] 3.2 Concept formulation The basic models were elaborated and explored: through architecture ....

Mary Shaw. Toward Higher-Level Abstractions for Software Systems. Proc. Tercer Simposio Internacional del Conocimiento y su Ingerieria, October


A Formal Approach to Software Architecture - Allen (1997)   (107 citations)  Self-citation (Shaw)   (Correct)

....connectors in WRIGHT, we have contributed to an improved understanding of a connector as a pattern of interaction. Connectors have been a key, but informal, element of the concept of software architecture almost from the moment software architecture was introduced as a term (see, for example [Sha88] WRIGHT is the first notation to provide mechanisms Chapter 10. Conclusion 199 for the explicit characterization of the semantics of a connector and to define the meaning of that characterization in system composition. Style as Predicate Over Sets of Configurations: We have provided an ....

Mary Shaw. Toward higher-level abstractions for software systems. In Proc. Tercer Simposio Internacional del Conocimiento y su Ingerieria, pages 55--61, October 1988.


Abstractions for Software Architecture and Tools to.. - Shaw, DeLine, Klein, .. (1995)   (235 citations)  Self-citation (Shaw)   (Correct)

No context found.

Mary Shaw. Toward Higher-Level Abstractions for Software Systems. Proc. Tercer Simposio Internacional del Conocimiento y su Ingerieria, Oct 1988.

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