Mary Shaw. Heterogeneous Design Idioms for Software Architecture. Proc. Sixth International Workshop on Software Specification and Design, IEEE, October 1991, pp.158-165.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... have proposed generic knowledge for requirements engineering e.g. clichs in the Requirements Apprentice [Reubenstein91] and generalised application frames in the ITHACA project [Fugini90] In software engineering, libraries of abstractions have been described at the level of design architectures [Shaw91] and reusable functions, although these have limited success in practice [Pietro Diaz91] Harandi91] Similar abstract classes have also been proposed in Artificial Intelligence, Greuber92] Chandrasekaran92] Knowledge engineering methods, notably KADS [Wilenga93] have also espoused the use ....

: Shaw M., "Heterogeneous design idioms for software architecture", 6th International Workshop on Software Engineering and Design, IEEE Computer Society Press, 158-165, 1991.

....as it stands describes the problem domain. It therefore models requirements specification and current system description. One future direction is to examine how solutions (designs) may be linked to specifications (problem description) Other workers have studied abstract classes of design problems [6, 18] and proposed classes of solutions. Extension of our current work in analogical matching envisages matching abstract domain models to software solutions belonging to the same problem class. The domain theory represents an alternative view of the Subject, Usage and Development worlds espoused in ....

Shaw M., (1991), Heterogeneous design idioms for software architecture. Proceedings 6th International Workshop on Software Specification and Design, Como Italy, IEEE Computer Society Press, 158.

.... : 6 6 Recognition Queries Reusable Styles (Idealized and As Built) Architectural Representation Recognition Engine Source Code Figure 1: Architectural Recovery Engine Figure 2: Bird s Eye Overview 2. 1 Architectural Styles The research community has provided detailed examples [6, 7, 8, 2] of idealized architectures abstractions that can guide architectural discovery. We have attempted to recognize instances of these abstractions in source code. 2.1.1 Entity and Relation Representation To support recognition, we have developed a dictionary of entity and relation terminology ....

M. Shaw. Heterogeneous design idioms for software architecture. In Proceedings of the 6th International Workshop on Software Specification and Design, 1991.

....[68] are still weak on groupware functionality. Structuring and planning of cooperative work is related to reengineering [10] and complexity metrics. That is, how to identify clusters of software with high internal cohesion and few interdependencies. See also recent work on software architectures [63]. We can also mention general project management [53] not considered in this paper) This involves planning of projects and their resources, e.g. using PERT diagrams. Such planning can partly be formulated as constraint based reasoning [33] For transaction planning, both COO and the Extended ....

Mary Shaw. Heterogeneous design idioms for software architectures. In Proceedings of the 6th International Workshop of Software Specification and Design, Como, Italy, pp. 1-8. IEEE-CS Press, Los Alamitos, CA (1990).

....off. The idea of using software for control is not new; scheduling algorithms and real time operating systems are an established area. However, the control character of the task is rarely obvious from the system architecture. For example, the architecture of one commercial process control system [Shaw 91, Garlan and Shaw 93] is primarily a layered architecture in which the control elements at the control loop level appear as objects; here the separation Mary Shaw Beyond Objects: A Software Design Paradigm Based on Process Control 10 between task and control is not obvious. The Chimera framework ....

Mary Shaw. Heterogeneous Design Idioms for Software Architecture. Proc. Sixth International Workshop on Software Specification and Design, IEEE, October 1991, pp.158-165.

....refer to common, or idiomatic, patterns used to organize the overall system. These are often widely used among software engineers in high level descriptions of system designs. A number of the more pervasive patterns have been identified in descriptions of architectural idioms [GKN88, GS93b, Sha89, Sha91] and material based on these patterns is beginning to appear in courses on architectural design of software [GSO 92] Among the more common architectural patterns are: Pipes and filters Graph of incremental stream transformers. Examples: Unix pipes, signal processing. Client server Shared ....

Mary Shaw. Heterogeneous design idioms for software architecture. In Proceedings of the Sixth International Workshop on Software Specification and Design, IEEE Computer Society, Software Engineering Notes, pages 158--165, Como, Italy, October 25-26 1991.

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