A Framework For Dynamic Updating In Component-based Software Systems

Setiap sistem perisian (software) perlu dikemas kini setiap masa bagi pelbagai alasan seperti penetapan pepijat (fixing bugs) Every software system needs to be updated over time for different reasons such as fixing bugs, upgrading its components, or adapting the system in response to its environment's changes

Proceedings of Monterey Workshop 2001 Engineering Automation for Sofware Intensive System Integration

The 2001 Monterey Workshop on Engineering Automation for Software Intensive System Integration was sponsored by the Office of Naval Research, Air Force Office of Scientific Research, Army Research Office and the Defense Advance Research Projects Agency. It is our pleasure to thank the workshop advisory and sponsors for their vision of a principled engineering solution for software and for their many-year tireless effort in supporting a series of workshops to bring everyone together.This workshop is the 8 in a series of International workshops. The workshop was held in Monterey Beach Hotel, Monterey, California during June 18-22, 2001. The general theme of the workshop has been to present and discuss research works that aims at increasing the practical impact of formal methods for software and systems engineering. The particular focus of this workshop was "Engineering Automation for Software Intensive System Integration". Previous workshops have been focused on issues including, "Real-time & Concurrent Systems", "Software Merging and Slicing", "Software Evolution", "Software Architecture", "Requirements Targeting Software" and "Modeling Software System Structures in a fastly moving scenario".Office of Naval ResearchAir Force Office of Scientific Research Army Research OfficeDefense Advanced Research Projects AgencyApproved for public release, distribution unlimite

Quality prediction for component-based software development: techniques and a generic environment.

Cai Xia.Thesis (M.Phil.)--Chinese University of Hong Kong, 2002.Includes bibliographical references (leaves 105-110).Abstracts in English and Chinese.Chapter 1 --- Introduction --- p.1Chapter 1.1 --- Component-Based Software Development and Quality Assurance Issues --- p.1Chapter 1.2 --- Our Main Contributions --- p.5Chapter 1.3 --- Outline of This Thesis --- p.6Chapter 2 --- Technical Background and Related Work --- p.8Chapter 2.1 --- Development Framework for Component-based Software --- p.8Chapter 2.1.1 --- Common Object Request Broker Architecture (CORBA) --- p.9Chapter 2.1.2 --- Component Object Model (COM) and Distributed COM (DCOM) --- p.12Chapter 2.1.3 --- Sun Microsystems's JavaBeans and Enterprise JavaBeans --- p.14Chapter 2.1.4 --- Comparison among Different Frameworks --- p.17Chapter 2.2 --- Quality Assurance for Component-Based Systems --- p.199Chapter 2.2.1 --- Traditional Quality Assurance Issues --- p.199Chapter 2.2.2 --- The Life Cycle of Component-based Software Systems --- p.255Chapter 2.2.3 --- Differences between components and objects --- p.266Chapter 2.2.4 --- Quality Characteristics of Components --- p.27Chapter 2.3 --- Quality Prediction Techniques --- p.32Chapter 2.3.1 --- ARMOR: A Software Risk Analysis Tool --- p.333Chapter 3 --- A Quality Assurance Model for CBSD --- p.35Chapter 3.1 --- Component Requirement Analysis --- p.38Chapter 3.2 --- Component Development --- p.39Chapter 3.3 --- Component Certification --- p.40Chapter 3.4 --- Component Customization --- p.42Chapter 3.5 --- System Architecture Design --- p.43Chapter 3.6 --- System Integration --- p.44Chapter 3.7 --- System Testing --- p.45Chapter 3.8 --- System Maintenance --- p.46Chapter 4 --- A Generic Quality Assessment Environment: ComPARE --- p.48Chapter 4.1 --- Objective --- p.50Chapter 4.2 --- Metrics Used in ComPARE --- p.53Chapter 4.2.1 --- Metamata Metrics --- p.55Chapter 4.2.2 --- JProbe Metrics --- p.57Chapter 4.2.3 --- Application of Metamata and Jprobe Metrics --- p.58Chapter 4.3 --- Models Definition --- p.61Chapter 4.3.1 --- Summation Model --- p.61Chapter 4.3.2 --- Product Model --- p.62Chapter 4.3.3 --- Classification Tree Model --- p.62Chapter 4.3.4 --- Case-Based Reasoning Model --- p.64Chapter 4.3.5 --- Bayesian Network Model --- p.65Chapter 4.4 --- Operations in ComPARE --- p.66Chapter 4.5 --- ComPARE Prototype --- p.68Chapter 5 --- Experiments and Discussions --- p.70Chapter 5.1 --- Data Description --- p.71Chapter 5.2 --- Experiment Procedures --- p.73Chapter 5.3 --- Modeling Methodology --- p.75Chapter 5.3.1 --- Classification Tree Modeling --- p.75Chapter 5.3.2 --- Bayesian Belief Network Modeling --- p.80Chapter 5.4 --- Experiment Results --- p.83Chapter 5.3.1 --- Classification Tree Results Using CART --- p.83Chapter 5.3.2 --- BBN Results Using Hugin --- p.86Chapter 5.5 --- Comparison and Discussion --- p.90Chapter 6 --- Conclusion --- p.92Chapter A --- Classification Tree Report of CART --- p.95Chapter B --- Publication List --- p.104Bibliography --- p.10

The Data Distribution Service – The Communication Middleware Fabric for Scalable and Extensible Systems-of-Systems

During the past several decades techniques and technologies have emerged to design and implement distributed systems effectively. A remaining challenge, however, to devising techniques and technologies that will help design and implement SoSs. SoSs present some unique challenges when compared to traditional systems since their scale, heterogeneity, extensibility, and evolvability requirement

Spider: An overview of an object-oriented distributed computing system

The Spider Project is an object-oriented distributed system which provides a testbed for researchers in the Department of Computer Science, CSUSB, to conduct research on distributed systems

Model Transformation Languages with Modular Information Hiding

Model transformations, together with models, form the principal artifacts in model-driven software development. Industrial practitioners report that transformations on larger models quickly get sufficiently large and complex themselves. To alleviate entailed maintenance efforts, this thesis presents a modularity concept with explicit interfaces, complemented by software visualization and clustering techniques. All three approaches are tailored to the specific needs of the transformation domain