Support for collaborative component-based software engineering

Collaborative system composition during design has been poorly supported by traditional CASE tools (which have usually concentrated on supporting individual projects) and almost exclusively focused on static composition. Little support for maintaining large distributed collections of heterogeneous software components across a number of projects has been developed. The CoDEEDS project addresses the collaborative determination, elaboration, and evolution of design spaces that describe both static and dynamic compositions of software components from sources such as component libraries, software service directories, and reuse repositories. The GENESIS project has focussed, in the development of OSCAR, on the creation and maintenance of large software artefact repositories. The most recent extensions are explicitly addressing the provision of cross-project global views of large software collections and historical views of individual artefacts within a collection. The long-term benefits of such support can only be realised if OSCAR and CoDEEDS are widely adopted and steps to facilitate this are described. This book continues to provide a forum, which a recent book, Software Evolution with UML and XML, started, where expert insights are presented on the subject. In that book, initial efforts were made to link together three current phenomena: software evolution, UML, and XML. In this book, focus will be on the practical side of linking them, that is, how UML and XML and their related methods/tools can assist software evolution in practice. Considering that nowadays software starts evolving before it is delivered, an apparent feature for software evolution is that it happens over all stages and over all aspects. Therefore, all possible techniques should be explored. This book explores techniques based on UML/XML and a combination of them with other techniques (i.e., over all techniques from theory to tools). Software evolution happens at all stages. Chapters in this book describe that software evolution issues present at stages of software architecturing, modeling/specifying, assessing, coding, validating, design recovering, program understanding, and reusing. Software evolution happens in all aspects. Chapters in this book illustrate that software evolution issues are involved in Web application, embedded system, software repository, component-based development, object model, development environment, software metrics, UML use case diagram, system model, Legacy system, safety critical system, user interface, software reuse, evolution management, and variability modeling. Software evolution needs to be facilitated with all possible techniques. Chapters in this book demonstrate techniques, such as formal methods, program transformation, empirical study, tool development, standardisation, visualisation, to control system changes to meet organisational and business objectives in a cost-effective way. On the journey of the grand challenge posed by software evolution, the journey that we have to make, the contributory authors of this book have already made further advances

Resolving Architectural Mismatches of COTS Through Architectural Reconciliation

The integration of COTS components into a system under development entails architectural mismatches. These have been tackled, so far, at the component level, through component adaptation techniques, but they also must be tackled at an architectural level of abstraction. In this paper we propose an approach for resolving architectural mismatches, with the aid of architectural reconciliation. The approach consists of designing and subsequently reconciling two architectural models, one that is forward-engineered from the requirements and another that is reverse-engineered from the COTS-based implementation. The final reconciled model is optimally adapted both to the requirements and to the actual COTS-based implementation. The contribution of this paper lies in the application of architectural reconciliation in the context of COTS-based software development. Architectural modeling is based upon the UML 2.0 standard, while the reconciliation is performed by transforming the two models, with the help of architectural design decisions.

The role of 1st tier suppliers in automobile product modularisation: the search for a coherent strategy

Modularization is a growing concept in auto industry. Architectural decisions had been many time studied from the car maker's point of view. This article addresses the question of supplier's strategy in the modular business. A prior publication (Fourcade Midler 2004) showed that supplier's involvement could take various forms, from light coordination to heavy investment in deep module redesign. This article will investigate how these different modular involvement profile could fit in general 1st Tier supplier's strategy. It is based both on a general study of automotive suppliers industrial field and an interactive research that we have been pursuing in conjunction with one 1st Tier supplier since 2001.

Chester Township Community Questionnaire Summary Report

The Center for Community Planning and Development at CSU’s Maxine Goodman Levin College of Urban Affairs was engaged by Chester Township to assist with conducting a Community Questionnaire. CSU’s role was to work with the Township in developing the questionnaire; and then receiving and analyzing the responses. The questionnaire was mailed to all resident addresses in the Township in May of 2020; responses were received and analyzed during June, July and August. To keep the cost low, the questionnaire was not designed to be a statistically calibrated survey, but rather a questionnaire which would enable the community to get a sense of residents’ interests and desires with regard to the Township’s future. Of 4,724 questionnaires mailed, 1,654 were returned and deemed valid, a 35% response rate. This is a very solid response rate indicative of residents’ high level of interest in participating in Township affairs and expressing their opinion. Questionnaires included both quantitative (multiple choice) questions and open-ended questions. All responses were analyzed by CSU and summarized in this report

The role of 1st tier suppliers in automobile product modularisation: the search for a coherent strategy

Modularization is a growing concept in auto industry. Architectural decisions had been many time studied from the car maker's point of view. This article addresses the question of supplier's strategy in the modular business. A prior publication (Fourcade Midler 2004) showed that supplier's involvement could take various forms, from light coordination to heavy investment in deep module redesign. This article will investigate how these different modular involvement profile could fit in general 1st Tier supplier's strategy. It is based both on a general study of automotive suppliers industrial field and an interactive research that we have been pursuing in conjunction with one 1st Tier supplier since 2001

A physiologically based approach to consciousness

The nature of a scientific theory of consciousness is defined by comparison with scientific theories in the physical sciences. The differences between physical, algorithmic and functional complexity are highlighted, and the architecture of a functionally complex electronic system created to relate system operations to device operations is compared with a scientific theory. It is argued that there are two qualitatively different types of functional architecture, and that electronic systems have the instruction architecture based on exchange of unambiguous information between functional components, and biological brains have been constrained by natural selection pressures into the recommendation architecture based on exchange of ambiguous information. The mechanisms by which a recommendation architecture could heuristically define its own functionality are described, and compared with memory in biological brains. Dream sleep is interpreted as the mechanism for minimizing information exchange between functional components in a heuristically defined functional system. The functional role of consciousness of self is discussed, and the route by which the experience of that function described at the psychological level can be related to physiology through a functional architecture is outlined

Evaluating Trustworthiness of Software Component

Makalah ini membahas tentang konsep keterpercayaan komponen perangkat lunak yang merupakan salah satu pertimbangan utama bagi pengembang perangkat lunak dalam mengimplementasikan metode pengembangan perangkat lunak berbasis komponen. Pada bagian awal makalah, penulis menjelaskan mengenai konsep penggunaan ulang perangkat lunak dan kaitannya dengan keterpercayaan komponen perangkat lunak. Selanjutnya, bagian inti makalah membahas secara detail mengenai metode pengujian komponen perangkat lunak dan 4 (empat) metode yang dapat digunakan untuk mengevaluasi tingkat keterpercayaan dari komponen perangkat lunak. Di akhir makalah, penulis memberi gambaran mengenai proses seleksi komponen perangkat lunak pada domain industri