A Middleware Framework for Constraint-Based Deployment and Autonomic Management of Distributed Applications

We propose a middleware framework for deployment and subsequent autonomic management of component-based distributed applications. An initial deployment goal is specified using a declarative constraint language, expressing constraints over aspects such as component-host mappings and component interconnection topology. A constraint solver is used to find a configuration that satisfies the goal, and the configuration is deployed automatically. The deployed application is instrumented to allow subsequent autonomic management. If, during execution, the manager detects that the original goal is no longer being met, the satisfy/deploy process can be repeated automatically in order to generate a revised deployment that does meet the goal.Comment: Submitted to Middleware 0

St. Mary’s Episcopal Church: Architectural History and Preservation Possibilities

This thesis focuses on the architectural and historical significance of St. Mary’s Episcopal Church in Portsmouth, Rhode Island. It comprises two major sections: a historical narrative and a research narrative. Thus, it is meant to illuminate the history of St. Mary’s and to guide future research. The historical narrative contains information regarding the context into which the church was built, the founding of the parish, the construction of the church building, and selected significant changes. The research narrative contains a list of archives consulted, suggestions of uses for the information obtained, and a description of the necessary steps to list St. Mary’s in the National Register of Historic Places

Consideration in the Design of Art Scholarly Databases

published or submitted for publicatio

A Framework for Constraint-Based Deployment and Autonomic Management of Distributed Applications

We propose a framework for deployment and subsequent autonomic management of component-based distributed applications. An initial deployment goal is specified using a declarative constraint language, expressing constraints over aspects such as component-host mappings and component interconnection topology. A constraint solver is used to find a configuration that satisfies the goal, and the configuration is deployed automatically. The deployed application is instrumented to allow subsequent autonomic management. If, during execution, the manager detects that the original goal is no longer being met, the satisfy/deploy process can be repeated automatically in order to generate a revised deployment that does meet the goal.Comment: Submitted to ICAC-0

On site challenges for the construction of 16-storey condominium: as observed by a young civil engineering technologist

The difference between an engineer and an engineering technologist is that, an engineer would mainly focus and produce structural designs based on engineering calculations, while the job of an engineering technologist is to execute the design in the real working environment by adopting flexible and critical technical ideas on-site. The challenges can be divided into two categories, namely design challenges faced by an engineer and the construction challenges faced by an engineering technologist. Thus, the job scope of an engineering technologist is relatively wider when compared to that of an engineer, as the engineering technologist would be dealing with the consultant, contractors and suppliers on site, while handling the in situ construction challenges. This requires basic understanding of engineering principles and technology, critical thinking and problem-solving skills, modern tools competency in software applications, designs and construction calculations, as well as communication and leadership skills all rolled into one. I have recorded my experience as a junior civil engineering technologist engaged in the construction works of a 16-storey condominium at Langkawi, Kedah. Included in the descriptions are in situ technical problems encountered, potentially unsafe working conditions, foundations, scheduling and housekeeping on site, among others. I hope that the information shared in this entry would make a good introduction and induction for juniors entering the work site, where my personal undertakings could serve as a guide and reminder for them

A Flexible and Secure Deployment Framework for Distributed Applications

This paper describes an implemented system which is designed to support the deployment of applications offering distributed services, comprising a number of distributed components. This is achieved by creating high level placement and topology descriptions which drive tools that deploy applications consisting of components running on multiple hosts. The system addresses issues of heterogeneity by providing abstractions over host-specific attributes yielding a homogeneous run-time environment into which components may be deployed. The run-time environments provide secure binding mechanisms that permit deployed components to bind to stored data and services on the hosts on which they are running.Comment: 2nd International Working Conference on Component Deployment (CD 2004), Edinburgh, Scotlan