1,721,024 research outputs found

    A 360-degree process improvement approach based on multiple models

    No full text
    Several models and methodologies have been defi ned in order to support organisational process improvement. The implementation and institutionalisation of these approaches allow organisations to improve, mature, acquire and institutionalise best practices and management systems from multiple approaches. However, there are two issues, which have to be kept in mind. On one hand, it is possible to fi nd several similarities amongst improvement, management and governance approaches. Experts and practitioners can thereby save, improve and optimize the organisational efforts using the best parts of existing models as building blocks; they can thus be prepared to deconstruct models, aiming for their designs to meet multiple needs. On the other hand, nonetheless, there are other factors which may infl uence, for example, compliance, or those aspects related to structural differences such as terminology, size, process, element structure, content, granularity, and complexity, which make diffi cult to work in multi-model environments. This being the case, the people involved need a map or guideline telling them how to carry out the harmonisation of models and standards that have to be implemented inside their organisations. In the quest to help support the work of harmonization of multiple models, this paper presents a framework that defi nes elements needed for the harmonization of multiple reference models to occur, as well as its application to three case studies. The results obtained show that the framework proposed has allowed the harmonization of several models

    An Architecture to infer Business Rules from Event Condition Action Rules implemented in the Persistence Layer

    Full text link
    The business rules that govern the behaviour of a business process can be hardcoded in different ways in a software application. The modernization or improvement of these applications to a process-oriented perspective implies typically the modification of the business rules. Frequently, legacy systems are not well-documented, and almost always, the documentation they have is not updated. As a consequence many times is necessary the analysis of source code and databases structures to be transformed into a business language more understandable by the business experts involved in the modernization process. Database triggers are one of the artefacts in which business rules are hardcoded. We focus on this kind of artefacts, having in mind to avoid the manual analysis of the triggers by a database expert, and bringing it closer to business experts. To get this aim we need to discover business rules that are hardcoded in triggers, and translate it into vocabularies that are commonly used by business experts. In this paper we propose an ADM-based architecture to discover business rules and rewrite then into a language that can be understood by the business experts.Ministerio de Ciencia y Tecnología TIN2009-13714Ministerio de Ciencia y Tecnología TIN2010-20057-C03-02Ministerio de Ciencia y Tecnología TIN2010-21744-C02-

    Evolución de la Ingeniería del Software y la formación de profesionales

    Full text link
    La industria del software ya tiene casi setenta años y en este período ha realizado grandes avances, ya que disponemos de lenguajes de programación más sofisticados, procesos de desarrollo más maduros, y las aplicaciones que se construyen en la actualidad son más complejas. De hecho, el software forma parte de nuestras vidas, está en todos los aparatos que manejamos, medios de transporte, sistemas de telecomunicaciones, equipos médicos, sistemas de administración pública y financieros, en el arte, en el ocio y en el entretenimiento. En definitiva, como decía Bjarne Stroustrup: “Our civilization runs on software”. Ahora bien, hay que tener en cuenta como señala Grady Booch que: “el desarrollo de software ha sido, es y probablemente será fundamentalmente difícil”. En efecto, cada vez se construyen sistemas más complejos desde el punto de vista tecnológico. A lo que hay que añadir también, muchas veces, problemas en el gobierno de las tecnologías y sistemas informáticos, defectos producidos por primar la puesta en marcha de los sistemas de forma oportuna -sacrificando su calidad-, y la falta de formación de los responsables del desarrollo de software. A continuación, resumiremos la evolución de la Ingeniería del Software desde su nacimiento hasta la actualidad; que según Barry Boehm, ha seguido un proceso de tesis, antítesis y síntesis que explicaría las diferentes propuestas y contrapropuestas que se han sucedido a lo largo de estas décadas; señalando las nuevas demandas que se han producido en la formación de los profesionales.Facultad de Informátic

    Methods for measurement-based COTS assessments and selection

    Full text link
    During recent years, new software engineering paradigms like component-based software engineering and COTS-based development have emerged. Both paradigms are concerned with reuse and customisation of existing components. The use of COTS software has become more and more important in state-of-the-art and state-of-the-practice software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, COTS software introduces risks such as unknown quality properties of the COTS software in use that can inject harmful side effects into the final product. In this paper, we present a brief comparison of well-known COTS evaluation methods. Our work is focused on identifying the main goals and features of the methods in order to extend their uses on evaluating COTS products as well as COTS development processes.Eje: Ingeniería de Software y Base de DatosRed de Universidades con Carreras en Informática (RedUNCI

    Stability for component integration assessment

    Full text link
    Component-Based Software Development is focused on assembling previously existing components (COTS and other non-developmental items) into larger systems, and migrating existing systems toward component approaches. Ideally, most of the application developer’s time is spent integrating components. We present an approach that can be used in the process of establishing component integration’s quality as an important field to resolving CBS quality problems – problems ranging from CBS quality definition, measurement, analysis, and improvement to tools, methods and processes. In this paper, we introduce an important property we called system’s stability as part of a cycle for assessing and improving component-based systems. This property is the basis for determining the impact of incorporating COTS components into a stable system.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

    Methods for measurement-based COTS assessments and selection

    Full text link
    During recent years, new software engineering paradigms like component-based software engineering and COTS-based development have emerged. Both paradigms are concerned with reuse and customisation of existing components. The use of COTS software has become more and more important in state-of-the-art and state-of-the-practice software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, COTS software introduces risks such as unknown quality properties of the COTS software in use that can inject harmful side effects into the final product. In this paper, we present a brief comparison of well-known COTS evaluation methods. Our work is focused on identifying the main goals and features of the methods in order to extend their uses on evaluating COTS products as well as COTS development processes.Eje: Ingeniería de Software y Base de DatosRed de Universidades con Carreras en Informática (RedUNCI

    Setting a process to effectively measure COTS functional suitability

    Full text link
    In attempting to build a COTS integrated system, selection of candidates typically pays attention to specify search criteria and goals to be met. Yet they often overlook some elements in the process such as fact-based decisions and teamwork, which might drive the process helping increase the probability of success. In this paper, we identify some features that we have found useful in our research, and which we believe need further discussion before integrating a process for COTS components measurement.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

    Issues for assessing component-based systems

    Full text link
    The use of component-based software has become more and more important in state-of-the-art and state-of-the-practice of software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, component-based software introduces risks such as unknown quality properties of the components in use that can inject harmful side effects into the final product. This paper proposes a multidimensional classification scheme for assessing component-based systems. The classification scheme provides insight into what quality characteristics, managerial features, or assessment methods and techniques might be used for evaluating different component artefacts.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

    Setting a process to effectively measure COTS functional suitability

    Full text link
    In attempting to build a COTS integrated system, selection of candidates typically pays attention to specify search criteria and goals to be met. Yet they often overlook some elements in the process such as fact-based decisions and teamwork, which might drive the process helping increase the probability of success. In this paper, we identify some features that we have found useful in our research, and which we believe need further discussion before integrating a process for COTS components measurement.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI
    corecore