A Work System Front End for Object-Oriented Analysis and Design

This paper proposes that basic ideas from the work system theory (WST) and the work system method (WSM) might serve as a front end to object-oriented analysis and design (OOAD), thereby providing a path from business-oriented descriptions to formal, technical specifications. After describing the background motivation and summarizing work system concepts, the paper uses a hiring system example to show how two tools from WSM can be used as a front end for OOAD, in effect, a step before creating use case diagrams and other types of Unified Modeling Language (UML) artifacts. Potential benefits of this approach stem from a business-oriented question, how can we improve this work system\u27s performance, rather than an IT-oriented question, how can we create a technical artifact that will be used

A Work System Front End for Object-Oriented Analysis and Des

This paper proposes that basic ideas from the work system theory (WST) and the work system method (WSM) might become a front end to object-oriented analysis and design (OOAD). After describing the background motivation and summarizing work system concepts, it uses a hiring system example to show how two tools from WSM can be used as a front end for OOAD, in effect, a step before creating use case diagrams. Potential benefits of this approach stem from a business-oriented question, how can we improve this work system\u27s performance, rather than an IT-oriented question, how can we create an IT artifact that will be used

Next generation software environments : principles, problems, and research directions

The past decade has seen a burgeoning of research and development in software environments. Conferences have been devoted to the topic of practical environments, journal papers produced, and commercial systems sold. Given all the activity, one might expect a great deal of consensus on issues, approaches, and techniques. This is not the case, however. Indeed, the term "environment" is still used in a variety of conflicting ways. Nevertheless substantial progress has been made and we are at least nearing consensus on many critical issues.The purpose of this paper is to characterize environments, describe several important principles that have emerged in the last decade or so, note current open problems, and describe some approaches to these problems, with particular emphasis on the activities of one large-scale research program, the Arcadia project. Consideration is also given to two related topics: empirical evaluation and technology transition. That is, how can environments and their constituents be evaluated, and how can new developments be moved effectively into the production sector

User interface development and software environments : the Chiron-1 system

User interface development systems for software environments have to cope with the broad, extensible and dynamic character of such environments, must support internal and external integration, and should enable various software development strategies. The Chiron-1 system adapts and extends key ideas from current research in user interface development systems to address the particular demands of software environments. Important Chiron-1 concepts are: separation of concerns, dynamism, and open architecture. We discuss the requirements on such user interface development systems, present the Chiron-1 architecture and a scenario of its usage, detail the concepts it embodies, and report on its design and prototype implementation

IMPLEMENTATION OF A LOCALIZATION-ORIENTED HRI FOR WALKING ROBOTS IN THE ROBOCUP ENVIRONMENT

This paper presents the design and implementation of a human–robot interface capable of evaluating robot localization performance and maintaining full control of robot behaviors in the RoboCup domain. The system consists of legged robots, behavior modules, an overhead visual tracking system, and a graphic user interface. A human–robot communication framework is designed for executing cooperative and competitive processing tasks between users and robots by using object oriented and modularized software architecture, operability, and functionality. Some experimental results are presented to show the performance of the proposed system based on simulated and real-time information. </jats:p

Should I Bug You? Identifying Domain Experts in Software Projects Using Code Complexity Metrics

In any sufficiently complex software system there are experts, having a deeper understanding of parts of the system than others. However, it is not always clear who these experts are and which particular parts of the system they can provide help with. We propose a framework to elicit the expertise of developers and recommend experts by analyzing complexity measures over time. Furthermore, teams can detect those parts of the software for which currently no, or only few experts exist and take preventive actions to keep the collective code knowledge and ownership high. We employed the developed approach at a medium-sized company. The results were evaluated with a survey, comparing the perceived and the computed expertise of developers. We show that aggregated code metrics can be used to identify experts for different software components. The identified experts were rated as acceptable candidates by developers in over 90% of all cases