7 research outputs found

    Collaborative Decision Making Tools : A Comparative Study Based on Functionalities

    Get PDF
    International audienceThis paper is on collaborative decision making issues. The study is on collaborative decision making tools. To do that, a state of the art of these tools supporting collaborative work in general and especially the tools supporting collaborative decision making process GDSS (Group Decision Support System) has been realized. A comparative study of these systems is made in order to highlight their strengths and their weaknesses. That aims to be a kind of tools selection guide, useful for mediated decision makers, in particular the facilitator

    Evolution style Mining in software architecture

    No full text
    International audienceSequential pattern extraction techniques are applied to the evolution styles of an evolving software architecture in order to plan and predict future evolution paths for the architecture. We present in this paper, a formalism to express the evolution styles in a more practical way. Then, we analyze these collected styles from the formalism introduced by the techniques of sequential patterns extraction to discover the sequential patterns of software architecture evolution. Finaly, from the analysis results, we develop a learning base and prediction rules to predict future evolution paths

    Approche système pour la conception d'une méthodologie pour l'élicitation collaborative des exigences

    No full text
    La présente thèse porte sur la collaboration dans la conception d'un système dans un cadre Ingénierie Système (IS) et plus spécifiquement, nous nous sommes intéressés à la phase de définition des besoins du système ou processus d'Ingénierie des Exigences, qui est la toute première phase dans l'Ingénierie Système. L'Ingénierie des Exigences est un processus assez complexe au cours duquel les exigences qu'un système doit satisfaire sont définies à partir de besoins provenant des différentes parties prenantes concernées de près ou de loin par la réalisation du système. Nous faisons la distinction entre le besoin qui est la perception qu'un utilisateur final a du système et l'exigence qui est la vision en termes techniques qu'un concepteur ou un développeur a du système. Le processus d'élicitation des besoins et de leur transformation en exigences techniques est un travail assez critique et demande l'implication de toutes les parties prenantes. Sur la base de ce constat, nous avons adopté une approche collaborative pour traiter la complexité de ce processus. Ainsi, nous définissons la problématique suite à une étude bibliographique sur l'Ingénierie des Exigences en vue de définir les frontières et le cadre de nos travaux. Etant donné la nature du problème, nous avons distingué deux domaines de définition de nos travaux : l'Ingénierie des Exigences à travers l'Elicitation des Exigences et la Collaboration. Nous avons ainsi adopté une démarche dans laquelle nous faisons la distinction entre les problèmes d'Ingénierie et ceux de la collaboration. Nous proposons alors une méthodologie pour l'Elicitation Collaborative des exigences. Nous séparons le domaine de l'Ingénierie du domaine de la collaboration en définissant deux types de processus : les processus d'Ingénierie des exigences et les processus de collaboration. Les processus de collaboration sont définis à l'aide de l'Ingénierie de la Collaboration en s'appuyant sur les tâches d'Ingénierie identifiées aux travers de processus d'Ingénierie fournis par des normes, en l'occurrence la norme EIA-632. Nous avons également réalisé des expérimentations de notre méthodologie avec des étudiants en utilisant l'outil ThinkTank de GroupSystems et un prototype de spécification collaborative des exigences appelé SPECJ que nous avons développé.This thesis treats the collaboration issues of design teams in the context of System Engineering (SE). Systems are more and more complex; their design requires the involvement of various skills, i.e., several stakeholders. This also involves team work between different stakeholders. Since this needs to be done correctly, it is necessary to define the methods required. In order to accomplish this, we were interested in collaboration that we considered more elaborated than simply group work. Indeed, collaboration is intended to be a group work that is better organized and structured, with clearly defined rules. To understand this problem more clearly, we were particularly interested in the process of identifying the needs of the system also called Requirements Engineering (RE), which is the first phase of the Engineering System. RE is a very complex process during which system requirements have to be defined based on needs from different stakeholders concerned in one way or another by the realization of the system. We make a distinction between the need that is the perception of a final user of the system, and the requirement that is the vision, in technical terms, that a designer or a developer has of the system. Indeed, requirement is the technical expression of a need and it will be recorded in the specifications book in order to be transferred to the system realization team. The process of needs collection and the transformation of these needs into technical requirements is critical and requires involvement of all stakeholders. As a result of this, we decided to adopt a collaborative approach to deal with the complexity of this process. Thus, in order to define the boundaries and scope of our research work, we made a literature review on RE. We have more focused on the phase of Requirements Elicitation, the first phase of RE, because it requires the committed participation of all stakeholders. Given the nature of the problem, we have distinguished two domains in which our research work is located: RE through Requirements Elicitation and Collaboration...TOULOUSE3-BU Sciences (315552104) / SudocSudocFranceF

    Modelling and Planning Evolution Styles in Software Architecture

    No full text
    International audienceThe purpose of this study is to find the right model to plan and predict future evolution paths of an evolving software architecture based on past evolution data. Thus, in this paper, a model to represent the software architecture evolution process is defined. In order to collect evolution data, a simple formalism allowing to easily express software architecture evolution data is introduced. The sequential pattern extraction technique is applied to the collected evolution styles of an evolving software architecture in order to predict and plan the future evolution paths. A learning and prediction model is defined to generate the software architecture possible future evolution paths. A method for evaluating the generated paths is presented. In addition, we explain and validate our approach through a study on two examples of evolution of component-oriented software architecture

    A Recommender System Based on Multi-Criteria Aggregation

    Get PDF
    Recommender systems aim to support decision-makers by providing decision advice. We review briefly tools of Multi-Criteria Decision Analysis MCDA, including aggregation operators, that could be the basis for a recommender system. Then we develop a multi-criteria recommender system, STROMa SysTem of RecOmmendation Multi-criteria, to support decisions by aggregating measures of performance contained in a performance matrix. The system makes inferences about preferences using a partial order on criteria input by the decision-maker. To determine a total ordering of the alternatives, STROMa uses a multi-criteria aggregation operator, the Choquet integral of a fuzzy measure. Thus, recommendations are calculated using partial preferences provided by the decision maker and updated by the system. An integrated web platform is under development

    Effects of pre-operative isolation on postoperative pulmonary complications after elective surgery: an international prospective cohort study

    No full text
    corecore