D. Soni, R.L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proceedings of the 17th International Conference on Software Engineering, pages 196--207, Seattle, Washington, USA, April 1995. ACM Press. ISBN 0-89791-708-1  Home/Search   Document Details and Download   Summary   Related Articles   Check

....distribution of hardware . Physical distribution of software One important purpose for a software architecture is to offer a set of views of the system and to act as a bridge between different stakeholders. Recently, different view models addressing the aspects above have been described, 1] and [2]. The views of these models highlight properties that address needs related to the stakeholders of a system or system family being under development. In SS2000, the conceptual and static views are covered rather extensively. One of the aspects above, layers of abstraction, highlights a number of ....

Soni D. , Nord R. L., and Hofmeister C., "Software Architecture in Industrial Applications", Proceedings of the 17th International Conference on Software Engineering, April 1995

....are presented for system and software architecture. The electrical and mechanical architecture can be modeled according to the Meta architecture as well but are not included in this chapter. In literature, a few architecture models have been published. Two examples are the Soni model [23] and the 4 1 View Model [24] both applicable to software architecture. The Architecture MetaModel is used as a guideline to specify the system and softwarearchitecture. The 6 View Model of Architecture is used as a template for the System Architecture definition. See also the Detailed ....

....concerns. Architectural modeling also helps to decrease complexity, to ensure completeness of the architecture, to organize its documentation and to improve communication with the various stakeholders. In literature, a few architecture models have been published. Two examples are the Soni model [23] and the 4 1 View Model [24] both applicable to software architecture. The physical level was often not included in the architecture, causing the architecture to miss the link to every day reality of programming resulting in a design that was not reflected in the source code. Typically, ....

D. Soni, R.L. Nord and C. Hofmeister. Software Architecture in Industrial Applications.

.... of the software architecture should be available in order to assess if separation of concerns is applied and eventually classify the components using the scheme in [Brod95] More variables could be considered by changing the level of granularity (e.g. subsystem, module) and the perspective [Soni95]. The type of representation to be adopted for representing architectural information depends on the level of granularity chosen for the components. How data could be collected The data sources to get an architectural description might be: interviews to original developers and maintainers, ....

D. Soni, R. L. Nord, and C. Hofmeister, "Software architecture in industrial applications", Proc. Int. Conf. on Soft. Eng., Seattle, Washington, 1995, pp.196-207.

....viewpoint at the micro architecture level and the context viewpoint and the technical infrastructure viewpoint at the macro architecture level. The micro architecture level viewpoints rougly coincide with viewpoints identified earlier by Kruchten in his 4 1 View Model [7] and by Soni et al. [12]. The viewpoints at the macro architecture level are new. Initially, we used informal notation techniques to express the information in views. However, we noticed that this leads to lack of clarity about the semantics of the views. We next used the Unified Modeling Language (UML) notation [3] to ....

....prescriptions for the building blocks that will be used in the implementation of the system. The micro architecture level viewpoints coincide with the logical and the development viewpoint in Kruchten s 4 1 1 View Model [7] and the conceptual and the code architecture identified by Soni et al. [12]. The macro architecture viewpoints were not identified before and are discussed in this section. A more elaborate treatment can be found in [9] Context View The context viewpoint gives an overview of the system and the systems in its environment with which it communicates. This communication ....

D. Soni, R. L. Nord and C. Hofmeister. Software architecture in industrial applications. In R. Jeffrey and D. Notkin, eds, Proceedings of the 17th International Conference on Software Engineering, pages 196--207, ACM Press, New York, 1995. 6

....perspective or the deployment perspective. A collection of such views is called a view model. A number of authors have introduced view models, which consist of a coherent set of views. The most important of these are the 4 1 view model by Kruchten ( 6] and the four architectures by Soni, et al. [9] and [4] To perform architecture level impact analysis we need those views that capture structural aspects of the system, i.e. the system s decomposition in components, the relationships between these components and the relation of the system to its environ2 ment. This information enables us to ....

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In 4 R. Jeffrey and D. Notkin, editors, Proceedings of the 17th International Conference on Software Engineering, pages 196--207, New York, 1995. ACM Press.

....the needs of specific stakeholders. For example, in lieu of specifying the data flow and the concurrency of a large system on the same diagram, two separate diagrams (views) are used to represent these aspects separately. In this section, we present the work of Kruchten [Kru95] and Soni et al. SNH95] on architecture views. Kruchten proposes modelling architecture using four di#erent views and one use cases view to illustrate and validate the other views. Each view addresses a specific architecture concern for a particular set of stakeholders. In his 4 1 View Model of Architecture, he ....

Dilip Soni, Robert L. Nord, and Christine Hofmeister. Software Architecture in Industrial Applications. In IEEE 17th International Conference on Software Engineering, 1995.

....forward engineering approaches, i.e. they are architectural or configuration integration languages producing system descriptions that can be, for some of them, further processed to generate real software systems. These descriptions usually represent what is called the idealized[5] or conceptual [12] software architecture. From a reverse engineering point of view, it is difficult to recover such kind of information because it is often distant from the actual objects that are retrievable from source code. Code represents the as built[5] architecture, that is the actual software organization. ....

....and connectors, that are incrementally instantiated with the aid of the user. These views are hierarchical so that zoom in and zoom out visualization is allowed. The hierarchical nature of architectural information and the need for multiple levels of representation have also been stated in [12, 13]. The highest abstraction level of our architectural model is the system and the corresponding system view. A system, S = P; I , which can also be distributed, consists of a set P of program components which communicate through a set I of connectors of type inter process connector(IPCs) ....

[Article contains additional citation context not shown here]

D. Soni, R. L. Nord and C. Hofmeister, "Software Architecture in Industrial Applications", in Proceedings of the 17th International Conference on Software Engineering, pp. 196-207, Seattle, 1995.

....within forward engineering approaches. They are architectural or configuration integration languages producing system descriptions that can be, in some cases, further processed to generate real software systems. These descriptions usually represent what is called the idealized [21] or conceptual [43] software architecture. From a reverse engineering point of view, it is difficult to recover such information because it is often distant from the actual objects that are retrievable from source code. Code represents the as built [21] architecture, that is the actual software organization. These ....

....system. These views are hierarchical in that components at one level of the hierarchy may be described by views of components and connectors at the lower level. The hierarchical nature of architectural information and the need for multiple levels of representation have also been stated in [35,43]. The highest abstraction level of our architectural model is the system and the corresponding view is the system view. A system, S = P; I consists of a set P of program components that communicate through a set I of connectors of type Inter Process Connector (IPC) Programs are separately ....

[Article contains additional citation context not shown here]

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proceedings of the International Conference on Software Engineering, pages 196--207, Seattle, 1995.

....explained its growth rate. Currently, we are investigating the evolution of the GCC compiler. 5 BUILD TIME VIEW During our study of open source systems, we found that they exhibit interesting and complex build time properties that aren t explicitly addressed by traditional architecture views [9, 13]. Open source systems are, in general, designed to be as portable as possible. Rather than create a separate source distribution for each platform, the commonalities are abstracted into a single distribution and configuration tools are used to aid in building the system. A build time view records ....

D. Soni, R. L. Nord, and C. Hofmeister. Software Architecture in Industrial Applications. In IEEE 17th International Conference on Software Engineering, 1995.

....the selected viewpoints and provides the rationale for their selection. No fixed set of viewpoints: Various architectural methods prescribe a fixed, or starting set of viewpoints, such as Kruchten s 4 1 view model [19] ISO s Reference Model for Open Distributed Processing [17] Siemens [26]. IEEE P1471 does not require any specific viewpoints; leaving this to individual methodological (or religious ) considerations. Instead, P1471 provides mechanisms for insuring that whatever viewpoints are used in a conforming AD, these are documented and understandable. IEEE P1471 does not take a ....

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proceedings of the 17th International Conference on Software Engineering, Seattle, Washington, 1995.

....4 we discuss why our metrics are indeed metrics for adaptability, in Section 5 we give extended uses for these metrics and Section 6 concludes this paper. 2. DEVELOPMENT OF ADAPTABILITY METRICS Software can have several, sometimes an infinite number of different architectures. For example, [1] talks about four different software architectures: Conceptual architecture, Module architecture, Execution architecture and Code architecture. It is the opinion of the authors that complex software can have several different types, or levels, of architectures thus there could be algorithmic ....

....R 1 : x # R 1 if x is adaptable Relation R 2 : x, y) # R 2 if x is more adaptable than y. The corresponding numerical relation system is given by E 2 = R, P) where R is the set of real numbers and P is the set of relations over R given by P = P 1 , P 2 , where Relation P 1 : x # P 1 if x #[0,1] Relation P 2 : x,y) # P 2 if x y. The mapping M from E 1 to E 2 is given by our formulas in Section 3 and in addition this mapping is a representation (as defined in [3] because for each relation in E 1 there is a relation in E 2 this is true for EAI and AAI but is not true for SAI in ....

D. Soni, R. L. Nord and C. Hofmeister, "Software Architecture in Industrial Applications", Proceedings of the 17 th International Conference on Software Engineering, 1995, Seattle, Washington, pp. 196-207.

....on which this process is based. We adhere to the terminology proposed by Chikofsky and Cross [CC90] To improve software architecture we must first have a described software architecture, which is an explicit description of requirements of the system from a software architecture point of view [SNH95, Kru95] For large software systems a software architecture description is usually not available. Software architecture recovery or reverse architecting [Kri97, Kri99] is the process that extracts such a description from the software. Rearchitecting is the process of changing the software ....

D. Soni, R. Nord, and C. Hofmeister. Software Architecture in Industrial Application. In Proceedings of the International Conference on Software Engineering, pages 196--207, 1995.

....Fortunately, the architect is not entirely in the dark. View models have been introduced to help the architect focus on the important aspects of the software architecture. The most important of these view models are the 4 1 View Model by Kruchten [10] and the four architectures by Soni et al. [18] and [6] A view model constitutes a coherent set of architectural perspectives, or viewpoints, that should be considered when defining a system s software architecture. Each of these viewpoints emphasizes different aspects of the software architecture, such as the run time perspective (the ....

....applying ALMA to business information systems (see for instance [12] and [13] we have identified four viewpoints that provide full insight into the effect of realizing change scenarios. Two of these viewpoints roughly coincide with viewpoints earlier identified by Kruchten [10] and Soni et al. [18]. These viewpoints concern the internals of the system whose modifiability is assessed. The two other viewpoints address the relationships between the system being analyzed and its environment. These latter viewpoints are not explicitly included in existing models; yet, we found them to be ....

[Article contains additional citation context not shown here]

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In R. Jeffrey and D. Notkin, editors, Proceedings of the 17th International Conference on Software Engineering, pages 196--207, New York, 1995. ACM Press.

....kinds of views. Simple systems may not require all of those described in his model while others may require more [30] He suggests 49 additional views, such as safety views and security views, that would be important to speci c classes of systems such as nuclear reactor controllers. Soni et al. [52] discuss categories of architecture: conceptual, module, execution, and code. These categories were de ned after studying the structure of a variety of industrial software systems. They feel that viewing software structure from di erent perspectives is crucial as it will provide a base for formal ....

D. Soni, R.L. Nord, and C. Hofmeister. Software Architecture In Industrial Applications. In Proceedings of the 17th International Conference on Software Engineering, pages 196-207. Association for Computer Machinery, April 1995.

....interconnections along with their interactions. At this level, the exact algorithms and data structures play only a secondary role. At the architectural level the structural properties are important. The constituent components of an architecture depends on the level of abstraction. For example, [17] describe three levels of abstraction. The conceptual architecture which describes the design, the module interconnection architecture which is concerned with functional decomposition and the execution architecture which is concerned with the dynamics. The following is well accepted terminology ....

D. Soni, R. L. Nord, and C. Hofmeister. Software Architecture in Industrial Applications. In Proceedings of the International Conference on Software Engineering, Washington, USA, April 1995.

....transition rules or always statements. 2.4. 6 Software Architecture and Design Patterns Mary Shaw, et al. describe the architecture of a software system in terms of the components used, the interactions among those components, and the patterns that guide the composition of components into systems [5, 35, 32, 34, 33, 78, 79, 81]. An architectural style is defined as a collection of recurring patterns of system organizations. In other words, it is an abstract framework for related applications. Some examples of architectural styles are procedure call, pipe filter, pipeline, realtime, and event based styles. In their ....

Dilip Soni, Robert L. Nord, and Christine Hofmeister. Software Architecture in Industrial Applications. In Proceedings 17th International Conference on Software Enginneering, pages 196--207, Seattle, Washington, USA, April 1995. ACM SIGSOFT.

....the intended, and sought, concrete architecture. 2.1 Architectural design recovery We consider four fundamental views for software architecture namely, structure, behavior, environment, and domain specific (section 1. 3) The notion of views has been discussed extensively in the literature [95, 57, 84, 70] (also see section A.2.3) In a broad sense, views are the result of applying separation of concerns on a design in order to classify the related knowledge about the design into more understandable and manageable forms. The notion of views is widely used in different aspects of the software ....

....tools and methodologies for maintaining or reengineering our valuable software assets. In software development phases, architecture description languages (ADLs) capture the high level design and provide analysis capabilities [81, 39, 60, 21] The notion of different views of an architecture [85, 57, 84], as design decomposition into orthogonal concerns, suggests further clarity and understandability for the design. Direct software development from large pieces of commercial components, known as COTS [90, 38] is another example. A brief review of software engineering discipline and the related ....

[Article contains additional citation context not shown here]

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In IEEE 17th International Conference on Software Engineering, pages 196--207, 1995. 56

....on the system enables us to judge the system s flexibility. The effect of these changes can be assessed using architectural views. A number of authors have introduced view models, the most important of which are the 4 1 view model by Kruchten ( 7] and the four architectures by Soni, et al. [10] and [4] Their views provide different perspectives on a software architecture. e.g. Kruchten s model contains the following views: 1) the logical view: the key abstractions of the system, 2) the process view: the set of the independently executing processes, 3) the physical view: a mapping ....

....experiences with applying SAA to business information systems (see for instance [8] and [9] we have identified four views that provide full insight into the effect of realizing change scenarios. Two of these views roughly coincide with views also identified by Kruchten ( 7] and Soni, et al. [10]) These views concern the internals of the system whose flexibility is assessed. The two other views capture the relationships between the system being analyzed and its environment. These latter views are not present in [7] and [10] yet, we found them to be essential in the analysis of business ....

[Article contains additional citation context not shown here]

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In R. Jeffrey and D. Notkin, editors, Proceedings of the 17th International Conference on Software Engineering, pages 196--207, 1995.

....execution, and code. This separation is based on our study of the software archi Proceedings of the First Working IFIP Conference on Software Architecture. 1999 IFIP. Published by Kluwer Academic Publishers. tectures of large systems, and on our experience designing and reviewing architectures (Soni, 1995). The different views address different engineering concerns, and separation of such concerns helps the architect make sound decisions about design trade offs. The notion of this kind of separation is not unique: most of the work in software architecture to date either recognizes different ....

Soni, D., Nord, R.L., and Hofmeister, C. (1995) Software Architecture in Industrial Applications, in Proceedings of the 17th International Conference on Software Engineering, Seattle, WA.

No context found.

D. Soni, R.L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proceedings of the 17th International Conference on Software Engineering, pages 196--207, Seattle, Washington, USA, April 1995. ACM Press. ISBN 0-89791-708-1

No context found.

D. Soni, R. L. Nord, and C. Hofmeister. Software architecture in industrial applications. In Proc. of the Int. Conf. on Software Engineering, pages 196--207, 1995.

No context found.

Dilip Soni, Robert L. Nord, and Christine Hofmeister. Software architecture in industrial applications. In Proceedings of the 17th International Conference on Software Engineering, pages 196--207, Seattle, Washington, April 1994.

No context found.

Soni,D.,Nord,R.,andHofmeister,C.,"Software Architecture in Industrial Applications", Proc ICSE, pp. 1962.

No context found.

D. Soni, R. L. Nord, and C. Hofmeister. Software Architecture in Industrial Applications. In International Conference of Software Engineering (ICSE'95), pages 196--207, 1995.

No context found.

D. Soni, R. Nord and C. Hofmeister, Software Architecture in Industrial Applications, In Proceedings of the International Conference on Software Engineering, ICSE1995, pp. 196-207, Seattle, Washington. USA.

First 50 documents

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