Abstract not found

Abstract not found

Abstract. The increasing proliferation of computational devices has introduced the need for applications to run on multiple platforms in different physical environments. Providing a user interface specially crafted for each context of use is extremely costly and may result in inconsistent behavior. User interfaces must now be capable of adapting to multiple sources of variation. This paper presents a unifying framework that structures the development process of plastic user interfaces. A plastic user interface is capable of adapting to variations of the context of use while preserving usability. The reference framework has guided the design of ARTStudio, a model-based tool that supports the plastic development of user interfaces. The framework as well as ARTStudio are illustrated with a common running example: a home heating control system. 1

As software strives to provide more fine-grained support for a wider range of people and activities, the need for designers and developers to understand human behavior has grown. Usability or user research professionals collect and work to comprehend data from diverse sources, seeking to translate this understanding into an ability to anticipate user responses to designs. Even more challenging, they will be more eKective if they can communicate their understanding to other team members who help in the design, development, and testing process. Personas is an interaction design technique that has demonstrated considerable potential for achieving these goals in software product development. Personas are fictional characters, based on actual data, that depict target user populations. The Persona method builds on previous research eKorts, notably in marketing, and was popularized by Alan Cooper in his 1999 book, The Inmates are Running the Asylum. 1 Personas consist of fully fleshed out fictional characters, as might be

The design of commercial products that are intended to serve millions of people has been a challenge for collaborative approaches. The creation and use of fictional users, concrete representations commonly referred to as ‘personas’, is a relatively new interaction design technique. It is not without problems and can be used inappropriately, but based on experience and analysis it has extraordinary potential. Not only can it be a powerful tool for true participation in design, it also forces designers to consider social and political aspects of design that otherwise often go unexamined.

Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their richness and informality. In some instances, for example when a project’s budget or schedule time is reduced at short notice, practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification. Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves focused attention. We describe our experiences during a goal-driven requirements analysis effort for an electronic commerce application. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability, inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks. We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality systems during goal and scenario analysis Keywords: Goal-based requirements engineering; Requirements specification; Use cases

In this paper, we describe an approach to allocation of function that makes use of scenarios as its basic unit of analysis. Our use of scenarios is driven by a desire to ensure that allocation decisions are sensitive to the context in which the system will be used and by insights from economic utility theory. We use the scenarios to focus the attention of decision makers on the relative financial costs of developing automated support for the activities of the scenario, the relative impact of functions on the performance of the operator's primary role and on the relative demands placed on an operator within the scenario. By focussing on relative demands and relative costs, our method seeks to allocate the operator's limited resources to the most important and most productive tasks within the work system, and to direct the effort of the design organisation to the development of automated support for those functions that deliver the greatest benefit for the effective operation of the inte...

Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their richness and informality. In some instances, for example when a projects budget or schedule time is reduced on short notice, practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification. Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves focused attention.#We describe our experiences during a goal-driven requirements analysis effort for an electronic commerce application. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability, inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks. We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality systems during goal and scenario analysis# Keywords Scenario management, use cases, requirements engineering, goals, requirements traceability, electronic commerce. I.#

Abstract: Complex and chronic illnesses, such as Cancer demand the use of specialist treatment protocols, administered and monitored by a co-ordinated team of professionals. Home based care of chronic illnesses (e.g. cancer patients) by a team of professionals is often a necessity, due to the protracted length of the illness. Hospital based treatment is limited, often demand based for short periods of time. As it is not possible for the health care team to be physically present by the patient at all times, or at any time physically together, whilst the patient is undergoing treatment, a principal aim of the current project is to overcome this problem, through DITIS 1, (∆ΙΤΗΣ, in Greek). DITIS is a system that supports Virtual Medical Teams dealing with the home-healthcare of cancer patients in Cyprus. It aims to support the creation, management and co-ordination of virtual medical teams, for the continuos treatment of the patient at home, and if need for periodic visits to places of specialist treatment and back home. 1.

Abstract not found