PROSET — A Language for Prototyping with Sets

We discuss the prototyping language PROSET(Prototyping with Sets) as a language for experimental and evolutionary prototyping, focusing its attention on algorithm design. Some of PROSET’s features include generative communication, flexible exception handling and the integration of persistence. A discussion of some issues pertaining to the compiler and the programming environment conclude the pape

Adaptive development and maintenance of user-centric software systems

A software system cannot be developed without considering the various facets of its environment. Stakeholders – including the users that play a central role – have their needs, expectations, and perceptions of a system. Organisational and technical aspects of the environment are constantly changing. The ability to adapt a software system and its requirements to its environment throughout its full lifecycle is of paramount importance in a constantly changing environment. The continuous involvement of users is as important as the constant evaluation of the system and the observation of evolving environments. We present a methodology for adaptive software systems development and maintenance. We draw upon a diverse range of accepted methods including participatory design, software architecture, and evolutionary design. Our focus is on user-centred software systems

Approach Tolerance in the Assemblies of Evolutionary Hybrid Prototypes

A new answer is proposed to replace the traditional “one shot” prototype (manufactured in one piece with one process): the hybrid rapid prototype. It is used to highly reduce time, cost and increase reactivity during the development times of new products. The part is decomposed in several components which can quickly be changed and can be manufactured with a process the most adapted. The main objective of the presented method is to propose an available technological assembly between the different components of the part in the respect of technological and topological function, and initial tolerance. Using a graph of representation, fuzzy logic and a tolerance point of view, some entities are associated with a CIA (Assembly Identity Card) in accordance with evolutionary and manufacturing analysis. This work will be illustrated by an industrial tooling for plastic injection.Mechanical Engineerin

Contingent Information Systems Development

Situated approaches based on project contingencies are becoming more and more an important research topic for information systems development organizations. The Information Services Organization, which was investigated, has recognized that it should tune its systems development approaches to the specific situation. A model has been developed, dealing with the matching between prevailing contingency factors and the preconditions of already existing situated approaches. Furthermore, a generic process model for systems development, including the information systems operations stage, is proposed. This model makes it possible to derive from it specific systems development strategies. A number of basic development strategies, specific for the Information Services Organization, are described. Preconditions, specific for this organization, are added to the standard situated approaches

Low-fi skin vision: A case study in rapid prototyping a sensory substitution system

We describe the design process we have used to develop a minimal, twenty vibration motor Tactile Vision Sensory Substitution (TVSS) system which enables blind-folded subjects to successfully track and bat a rolling ball and thereby experience 'skin vision'. We have employed a low-fi rapid prototyping approach to build this system and argue that this methodology is particularly effective for building embedded interactive systems. We support this argument in two ways. First, by drawing on theoretical insights from robotics, a discipline that also has to deal with the challenge of building complex embedded systems that interact with their environments; second, by using the development of our TVSS as a case study: describing the series of prototypes that led to our successful design and highlighting what we learnt at each stage

The importance of incorporating technological advancements into the artificial eye process: a perspective commentary

Application of technology into healthcare has typically been targeted to high demand illnesses and treatments. However, with an increasing need to meet patient’s expectations combined with increased accessibility and reduced costs, smaller healthcare fields are starting to investigate its function and usability. Services have historically been led by skills and expertise, and recent developments are being seen by ocularists in the field of prosthetic eyes who acknowledge the potential benefit from technological advancement. Utilising the technologies recently investigated in maxillofacial prosthesis can start the evolutionary process where products are continually re-designed and re-developed to achieve excellent patient outcome and satisfaction levels

Historical roots of Agile methods: where did “Agile thinking” come from?

The appearance of Agile methods has been the most noticeable change to software process thinking in the last fifteen years [16], but in fact many of the “Agile ideas” have been around since 70’s or even before. Many studies and reviews have been conducted about Agile methods which ascribe their emergence as a reaction against traditional methods. In this paper, we argue that although Agile methods are new as a whole, they have strong roots in the history of software engineering. In addition to the iterative and incremental approaches that have been in use since 1957 [21], people who criticised the traditional methods suggested alternative approaches which were actually Agile ideas such as the response to change, customer involvement, and working software over documentation. The authors of this paper believe that education about the history of Agile thinking will help to develop better understanding as well as promoting the use of Agile methods. We therefore present and discuss the reasons behind the development and introduction of Agile methods, as a reaction to traditional methods, as a result of people's experience, and in particular focusing on reusing ideas from histor