Cloud Computing is a term applied to large, hosted datacenters, usually geographically distributed, which offer various computational services on a “utility” basis. Clouds are most often serving Developers or Businesses, or Large Enterprises as a new way to host applications. These applications are usually delivered to client PC’s or PC-like smart phones. We consider the case where the clients are highly mobile, very interactive, and very functional, such as in a car. The car is in and of itself a rich, three screen client (Phone-like, Television-like, Computer-like) which can host complicated application scenarios, with some logic in the car, and other logic “in the Cloud”. Additionally, the car can represent a collection of next generation sensors eventing up to the cloud. We explored the resultant needed capabilities of such a cloud, and concluded that a very rich Platform-as-a-Service (PaaS) Cloud Computing platform, far beyond the capabilities of today’s PaaS system, would be required to support such a large collection of mobile devices. We have generated an architecture for this platform from collecting requirements from several Connected Car applications, and are now modeling the results simulating millions of cars on the road per country. The PaaS system emerged with different mechanisms to other PaaS systems in existence.

This paper addresses some controversial issues relating to two main questions. Firstly, we discuss 'man-in-the loop' issues in SAACS. Some people advocate this must always be so that man's decisions can override autonomic components. In this case, the system has two subsystems - man and machine. Can we, however, have a fully autonomic machine - with no man in sight; even for short periods of time? What kinds of systems require man to always be in the loop? What is the optimum balance in self-to-human control? How do we determine the optimum? How far can we go in describing self-behaviour? How does a SAACS system handle unexpected behaviour? Secondly, what are the challenges/obstacles in testing SAACS in the context of self/human dilemma? Are there any lesson to be learned from other programmes e.g. Star-wars, aviation and space explorations? What role human factors and behavioural models play whilst in interacting with SAACS?.

Middleware Networks: Concept, Design and Deployment of Internet Infrastructure describes a framework for developing IP Service Platforms and emerging managed IP networks with a reference architecture from the AT&T Labs GeoPlex project. The main goal is to present basic principles that both the telecommunications industry and the Internet community can see as providing benefits for service-related network issues. As this is an emerging technology, the solutions presented are timely and significant. Middleware Networks: Concept, Design and Deployment of Internet Infrastructure illustrates the principles of middleware networks, including Application Program Interfaces (APIs), reference architecture, and a model implementation. Part I begins with fundamentals of transport, and quickly transitions to modern transport and technology. Part II elucidates essential requirements and unifying design principles for the Internet. These fundamental principles establish the basis for consistent behavior in view of the explosive growth underway in large-scale heterogeneous networks. Part III demonstrates and explains the resulting architecture and implementation. Particular emphasis is placed upon the control of resources and behavior. Reference is made to open APIs and sample deployments. Middleware Networks: Concept, Design and Deployment of Internet Infrastructure is intended for a technical audience consisting of students, researchers, network professionals, software developers, system architects and technically-oriented managers involved in the definition and deployment of modern Internet platforms or services. Although the book assumes a basic technical competency, as it does not provide remedial essentials, any practitioner will find this useful, particularly those requiring an overview of the newest software architectures in the field.

For a number of years, the network, software, and telecommunication industries have been working on a number of key technical issues dealing with the infrastructure support for hybrid services. From the end users' perspectives, hybrid services utilize various networks while hiding the underlying network technologies such as the wireless networks, phone system, and data networks. To this end, however, the data networks lack necessary power to support next-generation hybrid services. It is now generally understood that there is great value in creating a three-level network model with the middle level supporting a service platform that would contribute certain common services. Such a data network would provide the common services at its edges close to its points of presence (POPs) while maintaining control over all network components belonging to a specific network provider. It would interoperate with other networks to offer a uniform view and management of all hybrid services. This article describes the nature of the enhanced emerging networks and outlines the structure of a service platform that would support its functions.

Constellation is a Web-based design framework for developing distributed applications which allows a single user or group of users to concurrently access and manipulate different aspects of a distributed application from a simple Mosaic-like front-end tool. Users can edit and build programs and documents, manage source code, debug and instrument running distributed programs, read manual pages and other documents, browse through source code and much, much more from a simple yet powerful front-end tool. Constellation is designed to work in a heterogeneous networked environment. It works with different host types and different OS environments, and supports different communication protocols. It is designed to work with hybrid client/server applications that consist of new as well as legacy code. Constellation is easily extensible to support new protocols, hosts, servers, services and back-end tools.

The parallel computational model with data flow sequencing is introduced. Description of the basic principles and features of mpDF, a massively parallel architecture, based on the dataflow operational model and RISC organizational principles is presented. The analytical performance model is developed to evaluate proposed architectural solution for distributed/parallel computing based on data flow sequencing of instructions. Algorithmic performance model is extended to include characterization of the parallel programs in terms of the average parallelism. Model is solved for number of different workloads. The values of the basic architectural characteristics are analyzed showing that architecture is well balanced providing consistent performance made for wide rage of parallel applications.<<ETX>>

An integration framework project to define and implement a set of design framework toolkits for development of an environment supporting concurrent interdisciplinary engineering tasks is described. A graphic user interface for tools and frameworks, tool and design information management support, and distributed/parallel processing support are discussed. The core of the framework support facilities which have been implemented and utilized in functional design environments is discussed. A general integration methodology is discussed

A description is given of the issues encountered in generating an integrated design environment (IDE) based on the DEMETER workbench (DWB) and PIE (a parallel programming and instrumentation environment for UNIX machines). Some of the reasons for using a general integration methodology are explained. DEMETER, which supports complexity reduction, CAD tools management and manipulation, and distributed/parallel problem-solving, is presented. DWB is described. It is shown how the IDE can be built using the DWB and the basic concepts developed in PIE.<<ETX>>

The synthesis tools provided by the MICON system are described. They are M1, which utilizes a knowledge-based approach to represent and apply design knowledge, and the knowledge acquisition tool CGEN, which allows hardware designers to deposit their expertise into M1 without writing any code. The authors explore the development of an automated design environment for M1/CGEN, where computer design knowledge in M1 and CGEN is replaced by operational knowledge creating a generalized system for integrating and sequencing a suite of design tools.<<ETX>>