Abstract. The paper presents a framework for introducing design patterns that facilitate or improve the techniques used during ontology lifecycle. Some distinctions are drawn between kinds of ontology design patterns. Some contentoriented patterns are presented in order to illustrate their utility at different degrees of abstraction, and how they can be specialized or composed. The proposed framework and the initial set of patterns are designed in order to function as a pipeline connecting domain modelling, user requirements, and ontologydriven tasks/queries to be executed. 1

The domestic environment is predicted by market analysts to be the major growth area in computing over the next decade, yet it is a poorly understood domain at the current time of writing. Research is largely confined to the laboratory environment, although it has been recognized that ubiquitous computing will in due course have to resonate with the ‘stable and compelling routines of the home’. This paper seeks to inform ubiquitous computing for the home environment by unpacking the notion of domestic routines as coordinational features of domestic life. We focus in particular on the routine nature of communication and use ethnographic study to explicate a discrete organization of coordination whereby household members routinely manage communications coming into and going out of the home. The coordinate ways in which members routinely organize communication are made visible through sequences of practical action, which articulate domestic routines and key properties of communication. These include ecological habitats, activity centres, and coordinate displays at which technology is at the core. These organizational features combine to form a locally produced system of communication and open up the play of possibilities for design, articulating the distinct needs of particular settings and ‘prime sites ’ for the deployment of ubiquitous computing devices.

Despite vast interest in design patterns, the specification and application of patterns is generally assumed to rely on manual implementation. We describe a precise method of specifying how a design pattern is applied: by phrasing it as an algorithm in a meta-programming language. We present a prototype of a tool that supports the specification of design patterns and their realization in a given program. Our prototype allows automatic application of design patterns without obstructing the source code text from the programmer, whom may edit it at will. We demonstrate pattern specification in meta-programming techniques and a sample outcome of its application. Keywords: Application of design patterns, tool support for design patterns, metaprogramming i Also available at: http://www.math.tau.ac.il/~eden/precise_specification_and_automatic_application_of_d esign_patterns.{ps.Z,rtf.zip} ii Supported in part by the German-Israeli Foundation for Scientific Research and Development (GIF) an...

Abstract. The movement of design out of the workplace and into the home brings with it the need to develop new analytic concepts to consider how ubiquitous computing might relate to and support everyday activities in domestic settings. In this paper we present a number of concepts derived from ethnographic studies of routine activities and technology uses implicated in the production and consumption of communication in the home. These concepts sensitise design to the importance of the ecology of the domestic space and distributed arrangements of collaboration to communication. They draw attention to the places where communication is accomplished and the routines whereby communication is articulated, thereby highlighting ‘prime sites ’ for situating ubiquitous computing in the domestic environment. 1 A New Challenge The domestic environment is currently receiving a great deal of attention as a place for the development of ubiquitous computing. The technical and methodological challenges involved in realising computing systems for the domestic environment are

Testing is an important part of any software development project, and can typically surpass more than half of the development cost. For safety-critical computer based systems, testing is even more important due to stringent reliability and safety requirements. However, most safety-critical computer based systems are real-time systems, and the majority of current testing and debugging techniques have been developed for sequential (non real-time) programs. These techniques are not directly applicable to real-time systems, since they disregard issues of timing and concurrency. This means that existing techniques for reproducible testing and debugging cannot be used. Reproducibility is essential for regression testing and cyclic debugging, where the same test cases are run repeatedly with the intention of verifying modified program code or to track down errors. The current trend of consumer and industrial applications goes from single microcontrollers to sets of distributed micro-controllers, which are even more challenging than handling real-time per-see, since multiple loci of observation and control additionally must be considered. In this thesis we try to remedy these problems by presenting an integrated approach to monitoring, testing, and debugging of distributed real-time systems. For monitoring

An open collaborative effort has been initiated: to design a common framework for algebraic specification and development of software.

A design pattern is a particular prose form of recording design information such that designs which have worked well in the past can be applied again in similar situations in the future. The availability of a collection of design patterns can help both the experienced and the novice designer recognize situations in which design reuse could or should occur. We have found that design patterns: 1) provide an effective "shorthand" for communicating complex concepts effectively between designers, 2) can be used to record and encourage the reuse of "best practices", 3) capture the essential parts of a design in compact form, e.g. for documentation of existing software architectures. Since the patterns community is one that shares information in an open forum and builds on the experiences of others, we chose to submit a joint paper on our industrial experiences with patterns. We focus on the lessons learned in our respective industrial settings as a first step towards answering the questions...

Agent systems must have a strong foundation; one approach that has been successfully applied to other kinds of software is patterns. This paper presents a collection of patterns for agents. 2. MOTIVATION Almost all agent development to date has been "home grown" [4] and done from scratch, independently, by each development team. This has led to the following problems: . Lack of an agreed definition: Agents built by different teams have different capabilities. . Duplication of effort: There has been little reuse of agent architectures, designs, or components. . Inability to satisfy industrial strength requirements: Agents must integrate with existing software and computer infrastructure. They must also address security and scaling concerns. Agents are complex and ambitious software systems that will be entrusted with critical applications. As such, agent based systems must be engineered with valid software engineering principles and not constructed in an ad hoc fashion. Agent system...

Component-based software development has proven effective for systems implementation in well-understood application domains, but is still insufficient for the creation of reusable and changeable software architectures. Design patterns address these shortcomings by capturing the expertise that is necessary for reusable design solutions. However, there is so far no methodical approach to providing these conceptual design building blocks in a tangible and composable form. To address this limitation, we introduce the notion of design components, reified design patterns fit for software composition. In this paper, we define design components and explain their constituents and services. Furthermore, we detail the activities of design composition and illustrate them as a process within a four-dimensional design space. Moreover, we describe a prototype of a design composition environment. A case study helps illustrating our approach.

Workflow systems seek to provide an implementation vehicle for complex, recurring business processes. Notwithstanding this common objective, there are a variety of distinct features offered by commercial workflow management systems. These differences result in significant variations in the ability of distinct tools to represent and implement the plethora of requirements that may arise in contemporary business processes. Many of these requirements recur quite frequently during the requirements analysis activity for workflow systems and abstractions of these requirements serve as a useful means of identifying the key components of workflow languages. Previous work has identified a number of workflow control patterns which characterise the range of control flow constructs that might be encountered when modelling and analysing workflow. In this paper, we describe a series of workflow data patterns that aim to capture the various ways in which data is represented and utilised in workflows. By delineating these patterns in a form that is independent of specific workflow technologies and modelling languages, we are able to provide a comprehensive treatment of the workflow data perspective and we subsequently use these patterns as the basis for a detailed comparison of a number of commercially available workflow management systems and business process modelling languages.