Information systems of the future will have to better match their operational organizational environment. Unfortunately, development methodologies have traditionally been inspired by programming concepts, not organizational ones, leading to a semantic gap between the system and its environment. To reduce as much as possible this gap, this paper proposes a development methodology named Tropos which is founded on concepts used to model early requirements. Our proposal adopts the i* organizational modeling framework [21], which offers the notions of actor, goal and (actor) dependency, and uses these as a foundation to model early and late requirements, architectural and detailed design. The paper outlines Tropos phases through an e-business example, and sketches a formal language which underlies the methodology and is intended to support formal analysis. The methodology seems to complement well proposals for agent-oriented programming platforms.

. We describe a software development methodology called Tropos for agent-oriented software systems. The methodology adopts the i* modeling framework [29], which offers the notions of actor, goal and (actor) dependency, and uses these as a foundation to model early and late requirements, architectural and detailed design. The paper outlines the methodology, and shows how the concepts of Tropos can be accommodated within UML. In addition, we also adopt recent proposals for extensions of UML to support design specifications for agent software. Finally the paper compares Tropos to other research on agent-oriented software development. 1

Abstract This paper discusses platform independent Web application modeling and development in the context of model-driven engineering. A specific metamodel (and associated notation) is introduced and motivated for the modeling of dynamic Web specific concerns. Web applications are represented via three independent but related models (business, hypertext and presentation). A kind of action language (based on OCL and Java) is used all over these models to write methods and actions, specify constraints and express conditions. The concepts described in the paper have been implemented in the Netsilon tool and operational modeldriven Web information systems have been successfully deployed by translation from abstract models to platform specific models.

Abstract. The UWE methodology provides a systematic approach for the development of Web applications. UWE is based on a conservative extension of the UML and comprises the separate modeling of the conceptual, navigational and presentational aspects of Web applications. We present the CASE tool ArgoUWE to support the design phase of the UWE development process. It is implemented as a plugin module of the open source ArgoUML modeling tool. ArgoUWE fully integrates the UWE metamodel and provides an XMI extension. The construction process of Web applications is supported by incorporating the semi-automatic UWE development steps as well as the OCL well-formedness rules of the UWE metamodel that allow the designer to check the consistency of the UWE models during editing. ArgoUWE is part of the OpenUWE tool environment for model-driven generation of Web applications.

Abstract. SAs provide a high-level model of large, complex systems using suitable abstractions of the system components and their interactions. SA dynamic descriptions can be usefully employed in testing and analysis. We describe here an approach for SA-based conformance testing: architectural tests are selected from a Labelled Transition System (LTS) representing the SA behavior and are then refined into concrete tests to be executed on the implemented system. To identify the test sequences, we derive abstract views of the LTS, called the ALTSs, to focus on relevant classes of architectural behaviors and hide away uninteresting interactions. The SA description of a Collaborative Writing system is used as an example of application. We also briefly discuss the relation of our approach with some recent research in exploiting the standard UML notation as an Architectural Description Language, and in conformance testing of reactive systems. 1

Development of dynamic Web sites is often performed by teams consisting of graphic designers and software developers. Communication between these different team members has to be supported with a simple modeling approach that considers their different academical backgrounds.

The Unified Modeling Language (UML) community has started to define so-called profiles in order to better suit the needs of specific domains or settings. Product lines represent a special breed of systems---they are extensible semi-finished pieces of software. Completing the semi-finished software leads to various software pieces, typically specific applications, which share the same core. Though product lines have been developed for a wide range of domains, they apply common construction principles. The intention of the UML-F profile is the definition of a UML subset, enriched with a few UML-compliant extensions, which allows the annotation of such artifacts. The paper presents aspects of the profile with a focus on patterns and exemplifies its usage.

We propose a software development methodology which is founded on concepts used to model early requirements. Our proposal adopts the i* modeling framework [21], which offers the notions of actor, goal and (actor) dependency, and uses these as a foundation to model early and late requirements, architectural and detailed design. The paper outlines the methodology, named Tropos, through an example, and sketches a formal language which underlies the methodology and is intended to support formal analysis. The methodology seems to complement well proposals for agent-oriented programming platforms.

Most web applications are data-intensive, i.e. they heavily rely on dynamic contents usually stored in databases. Website design and maintenance can greatly benefit from conceptual descriptions of both data and hypermedia aspects, i.e. those design dimensions which distinguish this application class: the data upon which the content is based, the way dynamic contents are composed together to form pages, and how pages are linked together in order to move across the application content. The paper proposes Webile, a visual Domain-Specific Language based on UML, which enables a model-driven approach to high-level specification of web applications. In contrast with other approaches, Webile exploits the UML metamodel architecture by serialising the specifications in the XMI interchange format. This representation provides interoperability amongst different operative platforms and enables a XSL transformation-based automatic generation of the applications being designed. 1

One aspect of the development of Web-enabled systems that has received increasing attention is information modeling, particularly with respect to aspects such as navigation and content models. These models have however typically focused on modeling at a relatively low-level and have failed to address higher-level aspects, such as architectural and business process modeling. We have proposed WebML+, a set of formal extensions to an existing modeling language (WebML), which is able to form a bridge between higher level business models and lower level detailed designs. In this paper we provide guidelines for supporting the derivation of a WebML+ model from/to these different models, thereby providing a concrete link between them. We illustrate these guidelines with a detailed example. 1