Loading...
Please wait, while we are loading the content...
Similar Documents
Software Architecture: Practice, Potential, and Pitfalls Panel Introduction
| Content Provider | Semantic Scholar |
|---|---|
| Author | Garlan, David Perry, Dewayne E. |
| Copyright Year | 1994 |
| Abstract | 1 What is software architecture? A critical aspect of the design for any large software system is its gross structure – that is, its high-level organization of computational elements and interactions between those elements [3, 6]. Broadly speaking, we refer to this as the software architectural level of design. Recently software architecture has begun to emerge as an important field of study for software engineering practitioners and researchers. This emergence is evidenced by a large body of recent work in areas such as module interface languages, domain specific architectures, architectural description languages , formal underpinnings for architectural design, and architectural design environments. What do we mean by the term " software architecture " ? If we look at the current uses of the term " architecture " , we find that it is used in different ways, often making it difficult to understand what aspect is being addressed. Among the various meanings are (a) the architecture of a particular artifact, as in " the blueprints describe this building, " (b) an architectural style, as in " that church is an example of Gothic architecture, " and (c) the general study of architecture , as in " he has an advanced degree in architecture. " To clarify the meaning of the term " architecture " with respect to software systems, it is helpful to observe that the recent emergence of interest in software architecture has been prompted by two distinct trends. The first is the recognition that over the years designers have begun to develop a shared repertoire of methods, techniques, patterns and idioms for structuring complex software systems. For example, the box and line diagrams and explanatory prose that typically accompany a high-level system description often refer to such patterns as a " pipeline " , a " blackboard-oriented design " , or a " client-server system ". Although these terms rarely have precise definitions, they permit designers to describe complex systems using abstractions that make the overall system intelligible. Moreover, they provide significant semantic content that inform others about the kinds of properties that the system will have: the expected paths of evolution, its overall computational paradigm, and its relationship to similar systems. The second trend is the recent interest in exploiting specific domains to provide reusable frameworks for product families. This is based on the idea that common aspects of a collection of related systems can be extracted … |
| File Format | PDF HTM / HTML |
| Alternate Webpage(s) | http://www.ece.utexas.edu/~perry/work/papers/icse16.ps.gz |
| Alternate Webpage(s) | http://www-2.cs.cmu.edu/afs/cs/project/able/ftp/saintro-icse16/saintro-icse16.pdf |
| Alternate Webpage(s) | http://www.cs.cmu.edu/afs/cs/project/able/ftp/saintro-icse16/saintro-icse16.pdf |
| Alternate Webpage(s) | http://www.cs.cmu.edu/afs/cs/project/compose/ftp/pdf/saintro-icse16.pdf |
| Language | English |
| Access Restriction | Open |
| Content Type | Text |
