{ With the growing emphasis on reuse, software development process moves toward component-based software design. In this paper we present an overview of the architecture-based approach to reliability estimation of the software composed of components. First, the common requirements of the architecture-based models are identiied, and the classiication is proposed. Then, the key models in each cla...

Despite recent advancements in software architecture knowledge management and design rationale modeling, industrial practice is behind in adopting these methods. The lack of empirical proofs and the lack of a practical process that can be easily incorporated by practitioners are some of the hindrance for adoptions. In particular, the process to support systematic design reasoning is not availab...

This paper describes the development of a groupware system from the requirements developed through researching the activities of software enginering students who were developing specification reports in groups. The specification is designed for an imaginary, but realistic, client. The groupware was developed to enable these groups to meet more often in non-collocated sessions. A list of require...

The effective documentation of Architectural Knowledge (AK) is one of the key factors in leveraging the paradigm shift toward sharing and reusing AK. However, current documentation approaches have severe shortcomings in capturing the knowledge of large and complex systems and subsequently facilitating its usage. In this paper, we propose to tackle this problem through the enrichment of traditio...

Components of a software system may be related in a wide variety of ways. These relationships need to be represented in software architecture in order develop quality software. In practice, software architecture is immensely challenging, strikingly multifaceted, extravagantly domain based, perpetually changing, rarely cost-effective, and deceptively ambiguous. This paper analyses relations amon...

As the complexity of software systems increases, so does the need for a good mechanism of abstraction. Software architecture design is an abstraction, hiding an immense amount of details about the data structures, algorithms, idiosyncrasies of programming language constructs, etc. that may be used in implementing the system-to-be. Fundamental as it may be to the modeling of the system, the very...

What is Software Architecture? The rules, paradigmen, pattern that help to construct, build and test a serious piece of software. It is the practical experience boiled down to abstract level. Software Architecture builds on System Engineering and the scientific method as established by Galileo Galilei: Measure what you can and make measureable what you can not. The experiment (test) is more imp...

Architects regularly make architectural design decisions but are usually unable to evaluate the economic impact of those decisions. Management, in contrast, is often interested in product-level decisions (such as features and quality) but not in the technical details of how those decisions are made. These differing interests lead to inconsistencies between how managers view value and how archit...

Marry your architecture in haste and you can repent in leisure. —Barry Boehm from a keynote address: And Very Few Lead Bullets Either How can you be sure whether the architecture chosen for your software is the right one? How can you be sure that it won't lead to calamity but instead will pave the way through a smooth development and successful product? It's not an easy question, and a lot ride...

18. NUMBER