Making intelligent systems team players: Case studies and design issues. Volume 1: Human-computer interaction design

Initial results are reported from a multi-year, interdisciplinary effort to provide guidance and assistance for designers of intelligent systems and their user interfaces. The objective is to achieve more effective human-computer interaction (HCI) for systems with real time fault management capabilities. Intelligent fault management systems within the NASA were evaluated for insight into the design of systems with complex HCI. Preliminary results include: (1) a description of real time fault management in aerospace domains; (2) recommendations and examples for improving intelligent systems design and user interface design; (3) identification of issues requiring further research; and (4) recommendations for a development methodology integrating HCI design into intelligent system design

Considering the User in the Wireless World

The near future promises significant advances in communication capabilities, but one of the keys to success is the capability understanding of the people with regards to its value and usage. In considering the role of the user in the wireless world of the future, the Human Perspective Working Group (WG1) of the Wireless World Research Forum has gathered input and developed positions in four important areas: methods, processes, and best practices for user-centered research and design; reference frameworks for modeling user needs within the context of wireless systems; user scenario creation and analysis; and user interaction technologies. This article provides an overview of WG1's work in these areas that are critical to ensuring that the future wireless world meets and exceeds the expectations of people in the coming decades

Model-driven Enterprise Systems Configuration

Enterprise Systems potentially lead to significant efficiency gains but require a well-conducted configuration process. A promising idea to manage and simplify the configuration process is based on the premise of using reference models for this task. Our paper continues along this idea and delivers a two-fold contribution: first, we present a generic process for the task of model-driven Enterprise Systems configuration including the steps of (a) Specification of configurable reference models, (b) Configuration of configurable reference models, (c) Transformation of configured reference models to regular build time models, (d) Deployment of the generated build time models, (e) Controlling of implementation models to provide input to the configuration, and (f) Consolidation of implementation models to provide input to reference model specification. We discuss inputs and outputs as well as the involvement of different roles and validation mechanisms. Second, we present an instantiation case of this generic process for Enterprise Systems configuration based on Configurable EPCs

Investigating and learning lessons from early experiences of implementing ePrescribing systems into NHS hospitals:a questionnaire study

Background: ePrescribing systems have significant potential to improve the safety and efficiency of healthcare, but they need to be carefully selected and implemented to maximise benefits. Implementations in English hospitals are in the early stages and there is a lack of standards guiding the procurement, functional specifications, and expected benefits. We sought to provide an updated overview of the current picture in relation to implementation of ePrescribing systems, explore existing strategies, and identify early lessons learned.Methods: a descriptive questionnaire-based study, which included closed and free text questions and involved both quantitative and qualitative analysis of the data generated.Results: we obtained responses from 85 of 108 NHS staff (78.7% response rate). At least 6% (n = 10) of the 168 English NHS Trusts have already implemented ePrescribing systems, 2% (n = 4) have no plans of implementing, and 34% (n = 55) are planning to implement with intended rapid implementation timelines driven by high expectations surrounding improved safety and efficiency of care. The majority are unclear as to which system to choose, but integration with existing systems and sophisticated decision support functionality are important decisive factors. Participants highlighted the need for increased guidance in relation to implementation strategy, system choice and standards, as well as the need for top-level management support to adequately resource the project. Although some early benefits were reported by hospitals that had already implemented, the hoped for benefits relating to improved efficiency and cost-savings remain elusive due to a lack of system maturity.Conclusions: whilst few have begun implementation, there is considerable interest in ePrescribing systems with ambitious timelines amongst those hospitals that are planning implementations. In order to ensure maximum chances of realising benefits, there is a need for increased guidance in relation to implementation strategy, system choice and standards, as well as increased financial resources to fund local activitie

Assessing cloud development platforms - What Platform as a Service offers and what not

Cloud computing has rapidly become a computing paradigm of great interest to the research and practitioner community. In addition to the provisioning of cloud-based software services, a plethora of solutions for the development of these services in the cloud have emerged. Cloud-based development platforms, also known as Platform-as-a-Service (PaaS) include a broad spectrum of elaborated application-level services. Architects and developers willing to exploit the advantages of this new technology for the software development process are confronted with a complex decision problem. Which PaaS characteristics are of specific importance for cloud-based development? What are major limitations negatively influencing the development process? In order to address these questions, we carried out a comprehensive case study. Nineteen developer groups comprising three master student developers each were asked to develop a cloud-based talent management software service. Each group was presented the same set of requirements, and randomly assigned one out of three pre-selected PaaS products. The groups were asked to record every development step during the four month project in a developer diary and also write a comprehensive project report. Within the developer diary as well as the final report particular topics had to be addressed, e.g. the time needed for the development of each requirement, helpful characteristics of the platform which supported efficient development of particular features, but also hindering characteristics or missing functionalities. The collected data was analyzed and a set of key characteristics for PaaS solutions was identified. Twelve functional and non-functional characteristics of PaaS solutions which were perceived as either helpful or hindering during the development project were extracted. For example, reusable platform objects were perceived as an important functional characteristic positively influencing the development process in the cloud. In contrast, limited DBMS functionalities were identified as a hindering characteristic by the developers. Our research is of specific relevance for practitioners dealing with development in the cloud; we provide guidelines for PaaS vendors and help architects and developers in the selection process for an appropriate PaaS solution