C. Gacek, A. Abd-Allah, B. Clark, and B. Boehm, On the Definition of Software Architecture. Proceedings of the First International Workshop on Architectures for Software Systems In Cooperation with the 17th International Conference on Software Engineering, D. Garlan (ed.), Seattle, WA, USA, 24-25 April 1995. pp. 85-95.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....the software architecture is defined in terms of architectural styles, thus binding the style specific features. Subsequently, as the architecture is further refined towards the life cycle architecture, application specific features are bound. This is exemplified on Table 1 (adapted from [4]) Every time an architectural feature is bound there exists the potential for an architectural mismatch to be introduced. Hence, we refer to architectural mismatches as being: style specific if their presence is brought about by some architectural feature(s) the style(s) imposes; or as ....

C. Gacek, A. Abd-Allah, B. Clark, and B. Boehm, On the Definition of Software Architecture. Proceedings of the First International Workshop on Architectures for Software Systems In Cooperation with the 17th International Conference on Software Engineering, D. Garlan (ed.), Seattle, WA, USA, 24-25 April 1995. pp. 85-95.

....thought completely reusable to subtle differences in domain and or architectural assumptions (about timing, synchronization, data forms, coordinate systems, environment models, etc. Facets were used to simplify the process of selecting reusable components [Prieto Diaz and Freeman 1987] [Gacek 1995], but still underlying assumptions were ignored. Handling, or rather detecting, the differences in underlying architectural assumptions is the focus of this work. The Domain Specific Software Architecture (DSSA) approach was created with the intention of providing an effective megaprogramming ....

....based on the distributed processes, event based, layered, main subroutine, multithreaded, 1. One can find various definitions of software architectures in the literature [Perry and Wolf 1992] Shaw and Garlan 1996] Tracz 1994] The one used throughout this work we introduced in a previous paper [Gacek et al. 1995]. Namely, we consider an architecture to be a set of components, connectors, constraints imposed on the components, connectors, and their composition, and a supporting rationale. 5 pipe and filter, and software bus styles (see section 2.1) I will be extending his set of conceptual features by ....

C. Gacek, A. Abd-Allah, B. Clark, B. Boehm, "On the Definition of Software Architecture," in Proceedings of the First International Workshop on Architectures for Software Systems - In Cooperation with the 17th International Conference on Software Engineering, D. Garlan (ed.), Seattle, Wa., 24-25 April 1995, pp. 85-95.

....[Booch JacobsonRumbaugh 1997] have undergone a similar development. In software development, we make use of models and views (e.g. UML diagrams) to cope with the complexity of software systems. Views enable different perspectives and therefore address different stakeholder concerns independently [Gacek et al. 1995]. Just as in the case of (COTS) package composition, we find that it is the composition of these views which ultimately leads to non trivial side effects. It is when those side effects clash that we are faced with mismatches. When we speak of mismatches, we mean basically everything, from risks, ....

Gacek, C., Abd-Allah, A., Clark, B., and Boehm, B. (1995) "On the Definition of Software Architecture," in Proceedings of the First International Workshop on Architectures for Software Systems - In Cooperation with the 17th International Conference on Software Engineering, D. Garlan (ed.), Seattle, Wa., 24-25, pp. 85-95.

....Modeling Language UML [3] have undergone a similar development. In software development, we make use of models and views (e.g. UML diagrams) to cope with the complexity of software systems. Views enable different perspectives and therefore address different stakeholder concerns independently [4]. Just as in the case of (COTS) package composition, we find that it is the composition of these views which ultimately leads to non trivial side effects. It is when those side effects clash that we are faced with mismatches. When we speak of mismatches we mean basically everything, from risks, to ....

C. Gacek, A. Abd-Allah, B. Clark, and B. Boehm, "On the Definition of Software Architecture," Proceedings of the First International Workshop on Architectures for Software Systems, D. Garlan (ed.), Seattle, WA, pp. 85-95, 1995.

No context found.

C. Gacek, A. Abd-Allah, B. Clark, B. Boehm. "On the Definition of Software Architecture", ICSE 17 Software Architecture Workshop, April 1995

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