ions Implementation-level: pages, links, presentation styles Reuse Plug-in components; Reusable presentation styles Architecture Two-tiers, based on file system Static binding of content to pages Usability High graphical control through manual authoring High coherence through use of presentation styles Low customization, no adaptivity, no proactivity 236 . P. Fraternali ACM Computing Surveys, Vol. 31, No. 3, September 1999 metaphor (e.g., in Director, objects' synchronization is defined by editing the score for the cast members of a stage; see Figure 6). ---The type of database connectivity, which may range from support of an internal database, of an external database via gateway software (typically ODBC or JDBC), or of an external database through DBMS API. ---The type of Web connectivity, which may be achieved by means of a plug-in application extending a Web browser, or by exporting the hypermedia application into a network language. Web connectivity may affect database c...

We propose a simple and complete method to determine the needed rights for roles in a system. We make use of the concept of use cases, commonly used to determine requirements in object-oriented system development. We extend use cases with rights specifications and we determine all of a role's rights from the collection of all use cases for the system. This method is in strict accordance with the least privilege principle. Keywords : Authorization models, Object-oriented analysis, Object-oriented authorization, RoIe-BasedAccess -Control, Use cases. 1.

practitioners and their customers who are familiar with the effects of large deviations between planned time for delivery and the actual one. Time is often estimated based on the size of the software to build and it is therefore interesting to investigate how well experienced software developers predict change.

In this paper we present a novel scenario-driven role engineering process for RBAC roles. The scenario concept is of central significance for the presented approach. Due to the strong human factor in role engineering scenarios are a good means to drive the process. We use scenarios to derive permissions and to define tasks. Our approach considers changeability issues and enables the straightforward incorporation of changes into a#ected models. Finally we discuss the experiences we gained by applying the scenario-driven role engineering process in three case studies.

: The evolution from mainframe to personal computer and network technology is characterized by a paradigm shift from algorithms to interactive models of computation. The first three sections develop a conceptual framework for interactive computation, showing that models of interaction have observably richer behavior than Turing machines that more completely express the behavior of embedded systems like airline reservation and banking systems. Sections 4 through 9 examine specific software architectures for programming in the large, including object-based design, multiple interface models, and technologies for interoperability, design patterns, coordination, and agent-oriented programming. Sections 10 and 11 present case studies for virtual reality and data information systems, demonstrating the naturalness of interactive models as a basis for computer graphics applications and more generally for empirical computer science. Interactive Software Technology 2/24 Interactive Software T...

Patterns have shown to be an effective means of capturing and communicating software design experience. However, there is more to patterns than software design patterns: We believe that patterns work for software development on several levels. In this paper we explore what we have come to understand as crucial aspects of the pattern concept, relate patterns to the different models built during software design, discuss pattern forms and how we think that patterns can form larger wholes like pattern handbooks. 1 Introduction Design patterns have become a hotly discussed topic in software development. We and many other researchers have been using and experimenting with patterns over the last years. We have applied patterns and observed their usage within software development. We have used and seen several definitions of patterns, and we have experimented with pattern forms. The emerging literature shows a flourishing and fruitful diversity of pattern definitions, forms and applications. ...

Abstract not found

Data modelling reveals the internal structure of an information system, abstracting away from details of the physical representation. We show that entity-relationship modelling, a well-tried example of a data-modelling technique, can be applied to both interactive and non-interactive information artefacts in the domain of HCI. By extending the conventional ER notation slightly (to give ERMIA, Entity-Relationship Modelling for Information Artefacts) it can be used to describe differences between different representations of the same information, differences between user's conceptual models of the same device, and the structure and update requirements of distributed information in a worksystem. It also yields symbolic-level estimates of Card et al.'s (1994) index of `cost-of-knowledge' in an informa- tion structure, plus a novel index, the `cost-of-update'; these symbolic estimates offer a useful complement to the highly detailed analyses of time costs obtainable from GOMS-like...

Traceability defined as the ability to trace dependent items within a model and the ability to trace correspondent items in other models is advocated as a desirable property of a software development process. Potential benefits of good traceability are clearer documentation, more focussed development, increased ease of system understanding, and more precise impact analysis of proposed changes. An industry-scale project applying the analysis and design method Objectory has been examined and documented with a number of traceability examples generated from the perspective of a maintainer attempting to understand the system. Four representative examples and a categorization of traceability are presented in this paper in order to provide a concrete empirical basis for the application of traceability to systems development.

The basic motivation for software inspections is to detect and remove defects before they propagate to subsequent development phases where their detection and removal becomes more expensive. To attain this potential, the examination of the artefact under inspection must be as thorough and detailed as possible. This implies the need for systematic reading techniques that tell inspection participants what to look for and, more importantly, how to scrutinise a software document. Recent research efforts investigated the benefits of scenario-based reading techniques for defect detection in functional requirements and functional code documents. A major finding has been that these techniques help inspection teams find more defects than existing state-of-the-practice approaches, such as, ad-hoc or checklist-based reading (CBR). In this paper we describe and experimentally compare one scenariobased reading technique, namely perspective-based reading (PBR), for defect detection in objec...