R. Kazman, L. Bass, G. Abowd, P. Clements. An Architectural Analysis Case Study: Internet Information Systems. Presented to ICSE 17 Workshop on Software Architecture, 1995.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....selected co design architectures, and one side effect which is the test of applicability of SAAM, originally devised for software architectures, on a different field. The SAAM method has been successfully applied to a few important software system domains such as Internet Information Systems (IIS) [2], and User Interface domain [1] This paper is structured as follows: The next three sections briefly describe common HW SW co design approaches namely, UNITY, COSYMA, and CASTLE with respect to their system architectures. In section 5 The SAAM method is described and the notion of task scenarios ....

....software systems (modifiability, scalability, security, etc. were used as the evaluation criteria in the SAAM paper. The method had some shortcomings which in the next attempt to improve the method, they changed the focus from non functional qualities as the base for evaluation, to task scenarios [2]. In order to apply SAAM to the co design domain, the system architecture should be an integrated environment, not individual design tools combined by a tool integration environment such as in MARVEL system [15] 5.1 Overview of the SAAM method The following descriptions of the SAAM method are ....

[Article contains additional citation context not shown here]

R. Kazman, L. Bass, G. Abowd, P. Clements. An Architectural Analysis Case Study: Internet Information Systems. Presented to ICSE 17 Workshop on Software Architecture, 1995.

....for determining how well it satisfies its requirements and quality trade offs that have to be made. Evaluating means measuring an architecture against a set of criteria. The criteria are given by the requirements which, in turn, are an expression of the usage context of a system. Kazman et al. [Kazman et al. 1995] state that Architectures are not inherently good or bad, they are simply more or less fit for a given purpose it is this fitness which architectural analysis helps to reveal. In general, requirements for non functional quality attributes are only loosely defined. Designers tend to talk about ....

....are only loosely defined. Designers tend to talk about properties like modifiability, adaptability, reliability without exactly defining what is implied by these terms. Consequently, it is next to impossible to assess the influence of these attributes on the architecture. As Kazman et al. [Kazman et al. 1995] point out it is important to be precise about these requirements: One difficulty in discussing software qualities is that they do not exist in the abstract, and cannot be completely described in the abstract. They are manifested in software and hardware and they exist within an environment of ....

Rick Kazman, Len Bass, Gregory Abowd, and Paul Clements: "An Architectural Analysis Case Study: Internet Information Systems," Software Architecture Workshop Proceedings ICSE95, Seattle, April 1995.

....has many variations: portability, reusability, adaptability, extensibility; all are special perspectives of a system s ability to support change. There is emerging a consensus on the value of scenario based evaluation to judge an architecture with respect to non runtime quality attributes [Kazman 95] Kruchten 95] 5.1.5 Implementing Based on the Architecture and Assuring Conformance This activity is concerned with ensuring that the developers adhere to the structures and interaction protocols dictated by the architecture. An architectural environment or infrastructure would be beneficial ....

Kazman, F.; Basas, l.; Abowd, G.; & Clements, P. "An Architectural Analysis Case Study: Internet Information Systems." Invited talk, First International Workshop on Architectures for Software Systems. Seattle, WA, April 1995.

.... systems We have performed a full SAAM study of a collection of Internetbased information systems (WAIS, WWW, Harvest) in an attempt to understand how architectural differences have evolved over the past few years and whether they have successfully supported the expected uses of these systems [13]. 3. Key word in context A small architectural case study first presented by Parnas and used in several places as a classic comparison of different architectural style approaches to the same problem. We performed a SAAM evaluation on KWIC to determine if we could reproduce similar results as ....

Kazman, R., Bass, L., Abowd, G., and Clements, P., "An Architectural Analysis Case Study: Internet Information Systems," Proceedings, First International Workshop on Software-Intensive Systems, Seattle, April 1995. (Also available as CMU-CS-TR-95-151, School of Computer Science, Carnegie Mellon University, Pittsburgh).

....to the scenarios considered. This case study appears in the next section. We have also conducted a number of other industrial and academic case studies in scenario based analysis as SAAM was maturing in areas such as user interface development environments [11] internet information systems [13], key word in context (KWIC) systems [3] embedded audio systems, and visual debuggers. 3.1 The WRCS System 3.1.1 System context purpose In this section we will discuss the application of SAAM to a commercially available revision control system, based upon RCS [18] which we will call WRCS. WRCS ....

Kazman, R., Bass, L., Abowd, G., and Clements, P., "An Architectural Analysis Case Study: Internet Information Systems," Proceedings, First International Workshop on Software-Intensive Systems, Seattle, April 1995. (Also available as CMU-CS-TR-95-151, School of Computer Science, Carnegie Mellon University, Pittsburgh).

No context found.

R. Kazman, L. Bass, G. Abowd, P. Clements, "An Architectural Analysis Case Study: Internet Information Systems". Proceedings, First International Workshop on Architectures for Software Systems, Seattle, 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