Innovative e-commerce ideas are characterized by commercial products yet unknown to the market, enabled by information technology such as the Internet and technologies on top of it. How to develop such products is hardly known. We propose a interdisciplinary approach, e -value , to explore an innovative e-commerce idea with the aim to understand such an idea thoroughly and to evaluate it for potential profitability. Our methodology exploits a requirements engineering's way of working, but employs concepts and terminology from business science, marketing and axiology. It shows how to model business requirements and improve business-IT alignment, in sophisticated multi-actor value constellations that are common in electronic commerce. In addition to the e -value approach methodology, we also present the action research-based development of our methodology, by using one of the longitudinal projects we carried out in the field of online news article provisioning.

Global communication networks and advances in information technology enable the design of information systems facilitating effective formulation and efficient resolution of negotiation problems. Increasingly, these systems guide negotiators in clarifying the relevant issues, provide media for offer formulation and exchange, and help in achieving an agreement. In practice, the task of analysing, modelling, designing and implementing electronic negotiation media demands a systematic, traceable and reproducible approach. An engineering approach to media specification and construction has these characteristics. In this paper, we provide a rationale for the engineering approach that allows pragmatic adoption of economic and social sciences perspectives on negotiated decisions for the purpose of supporting and undertaking electronic negotiations. Similarities and differences of different theories that underlie on-going studies of electronic negotiations are identified. This provides a basis for integration of different theories and approaches for the specific purpose of the design of effective electronic negotiations. Drawing on diverse streams of literature in different fields such as economics, management, computer, and behavioural sciences, we present an example of an integration of three significant streams of theoretical and applied research involving negotiations, traditional auctions and on-line auctions.

ill most likely lead to key abstractions with bloated interfaces. Such interfaces are difficult to understand and hard to maintain. Unanticipated changes cannot be handled gracefully and will trigger lots of recompilation. Changes to a client-specific part of the class interface are likely to affect clients in other subsystems or applications as well. A simple solution might be to extend the Customer class by adding new Borrower and Investor subclasses which capture the borrower-specific and investor-specific aspects respectively. From an object identity point of view, subclassing implies that two objects of different subclasses are not identical. Thus, a customer acting both as investor and as borrower is represented by two different objects with distinct identities. Identity can only be simulated by an additional mechanism. If two objects are meant to be identical, their inherited attributes must constantly be checked for consistency. However, we will inevitably run into problems in

Relationships between objects are almost as important to designs as objects themselves. Most programming languages do not support relationships well, so programmers must implement relationships in terms of more primitive constructs. This paper presents ve basic patterns which describe how objects can be used to model relationships within programs. By using these patterns, programs and designs can be made smaller, more exible, and easier to understand and maintain.

A pattern language to deal with Business Resource Management is presented. It covers a great number of applications in business systems, including patterns for resource rental, trading and maintenance, and was designed based on practical experience in information systems development. Existing recurring patterns were applied to form patterns in our language, which were instantiated to this specific domain. The idea has been to make the language as complete as possible in order to be useful for the analysis of a wide variety of applications in this domain. Fifteen patterns are presented together with a diagram showing the precedence for checking the convenience of their utilization. Object models using UML notation are used both to present each pattern structure and a sample instantiation. The pattern language application to practical cases has shown that analysis is easily conducted, as it is a guideline for the work to be done.

Often a project is faced with non-object-oriented languages or with object systems that are not powerful enough for the project’s purposes. But nevertheless we want to apply advanced object-oriented techniques in these languages. Therefore, build or use an object system as a language extension in the target language, and then implement the design on top of this OBJECT SYSTEM LAYER.

Since the publication of the Design Patterns book, a large number of object-oriented design patterns have been identified and codified. As part of the pattern form, objectoriented design patterns must indicate their relationships with other patterns, but these relationships are typically described very briefly, and different collections of patterns describe different relationships in different ways. In this paper we describe and classify the common relationships between object oriented design patterns. Practitioners can use these relationships to help them identity those patterns which may be applicable to a particular problem, and pattern writers can use these relationships to help them integrate new patterns into the body of the patterns literature. 1.

Jackson's Problem Frames provide a means of analysing and decomposing problems. They emphasise the world outside the computer helping the developer to focus on the problem domain instead of drifting into inventing solutions. The intention is to delay consideration of the solution space until a good understanding of the problem is gained.

Abstract: Specification and rapid prototyping of graph manipulation software by means of PROgrammed Graph REwriting Systems (PROGRES) is a paradigm, which attracts more and more interest in various fields of computer science. Nowadays produced specifications for process modeling tools, database query languages, etc. have a typical size of about 100 to 300 printed pages. They suffer severely from the lack of any module concept. This paper introduces a module concept for the graph rewriting (transformation) language PROGRES, which is closely related to the package concept of the standardized OO modeling language UML. It supports a variety of software

This position paper argues for the concurrent, iterative development of requirements and architectures during the development of software systems. It presents the "Twin Peaks" model -- a partial and simplified version of the spiral model -- that illustrates the distinct, yet intertwined activities of requirements engineering and architectural design. The paper suggests that the use of various kinds of patterns -- of requirements, architectures, and designs -- may provide a way to increase software development productivity and stakeholder satisfaction in this setting.