Las TIC en la administración de la cadena de suministro y su incidencia en el desempeño operacional

Las tecnologías de la información han empezado a ser un factor importante a tener en cuenta en cada uno de los procesos que se llevan a cabo en la cadena de suministro. Su implementación y correcto uso otorgan a las empresas ventajas que favorecen el desempeño operacional a lo largo de la cadena. El desarrollo y aplicación de software han contribuido a la integración de los diferentes miembros de la cadena, de tal forma que desde los proveedores hasta el cliente final, perciben beneficios en las variables de desempeño operacional y nivel de satisfacción respectivamente. Por otra parte es importante considerar que su implementación no siempre presenta resultados positivos, por el contrario dicho proceso de implementación puede verse afectado seriamente por barreras que impiden maximizar los beneficios que otorgan las TIC.

Model-Driven requirements engineering process aided by ontologies and natural controlled languages

Researches in Requirements Engineering have been growing in the latest few years. Researchers are concerned with a set of open issues such as: communication between several user profiles involved in software engineering; scope definition; volatility and traceability issues. To cope with these issues a set of works are concentrated in (i) defining processes to collect client s specifications in order to solve scope issues; (ii) defining models to represent requirements to address communication and traceability issues; and (iii) working on mechanisms and processes to be applied to requirements modeling in order to facilitate requirements evolution and maintenance, addressing volatility and traceability issues. We propose an iterative Model-Driven process to solve these issues, based on a double layered CIM to communicate requirements related knowledge to a wider amount of stakeholders. We also present a tool to help requirements engineer through the RE process. Finally we present a case study to illustrate the process and tool s benefits and usage

Enterprise systems modeling: The ERP5 development process

The design and implementation of an ERP system involves capturing the information necessary for implementing the system's structure and behavior that support enterprise management. This process should start on the enterprise modeling level and finish at the coding level, going down through different abstraction layers. For the case of Free/Open Source ERP, the lack of proper modeling methods and tools jeopardizes the advantages of source code availability. Moreover, the distributed, decentralized decision-making, and source-code driven development culture of open source communities, generally doesn't rely on methods for modeling the higher abstraction levels necessary for an ERP solution. The aim of this paper is to present a model driven development process for the open source ERP ERP5. The proposed process covers the different abstraction levels involved, taking into account well established standards and common practices, as well as new approaches, by supplying Enterprise, Requirements, Analysis, Design, and Implementation workflows. Copyright 2008 ACM.

Proposta de modelo conceitual de QFD integrado com AHP, modelo de Kano e análise SWOT no desenvolvimento de produto

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior (CAPES)

Economic development capitalizing on brand agriculture : turning development strategy on its head

This paper explores the possibilities of two unique Japanese concepts - the One Village One Product Movement (OVOP) and Michino Eki (or Roadside Stations) - as potential tools for bridging the gap between cities and rural areas through community-driven development. From the viewpoint of spatial economics and endogenous growth theory, this paper considers both OVOP and Michino Eki as rural development strategies of a broader nature based on "brand agriculture." Here, brand agriculture represents a general strategy for community-based rural development that identifies, cultivates and fully utilizes local resources for the development of products or services unique to a certain "village." Selected examples of OVOP and Michino Eki from Japan and developing countries are introduced.

Model-Driven Methodology for Rapid Deployment of Smart Spaces based on Resource-Oriented Architectures

Advances in electronics nowadays facilitate the design of smart spaces based on physical mash-ups of sensor and actuator devices. At the same time, software paradigms such as Internet of Things (IoT) and Web of Things (WoT) are motivating the creation of technology to support the development and deployment of web-enabled embedded sensor and actuator devices with two major objectives: (i) to integrate sensing and actuating functionalities into everyday objects, and (ii) to easily allow a diversity of devices to plug into the Internet. Currently, developers who are applying this Internet-oriented approach need to have solid understanding about specific platforms and web technologies. In order to alleviate this development process, this research proposes a Resource-Oriented and Ontology-Driven Development (ROOD) methodology based on the Model Driven Architecture (MDA). This methodology aims at enabling the development of smart spaces through a set of modeling tools and semantic technologies that support the definition of the smart space and the automatic generation of code at hardware level. ROOD feasibility is demonstrated by building an adaptive health monitoring service for a Smart Gym.

A Development Methodology to Facilitate the Integration of Smart Spaces into the Web of Things

How to create or integrate large Smart Spaces (considered as mash-ups of sensors and actuators) into the paradigm of ?Web of Things? has been the motivation of many recent works. A cutting-edge approach deals with developing and deploying web-enabled embedded devices with two major objectives: 1) to integrate sensor and actuator technologies into everyday objects, and 2) to allow a diversity of devices to plug to Internet. Currently, developers who want to use this Internet-oriented approach need have solid understanding about sensorial platforms and semantic technologies. In this paper we propose a Resource-Oriented and Ontology-Driven Development (ROOD) methodology, based on Model Driven Architecture (MDA), to facilitate to any developer the development and deployment of Smart Spaces. Early evaluations of the ROOD methodology have been successfully accomplished through a partial deployment of a Smart Hotel.

Introducing usability in a conceptual modeling-based software development process.

Usability plays an important role to satisfy users? needs. There are many recommendations in the HCI literature on how to improve software usability. Our research focuses on such recommendations that affect the system architecture rather than just the interface. However, improving software usability in aspects that affect architecture increases the analyst?s workload and development complexity. This paper proposes a solution based on model-driven development. We propose representing functional usability mechanisms abstractly by means of conceptual primitives. The analyst will use these primitives to incorporate functional usability features at the early stages of the development process. Following the model-driven development paradigm, these features are then automatically transformed into subsequent steps of development, a practice that is hidden from the analyst.

Criação de valor para o cliente: um estudo exploratório sobre programas de Key Account Management (KAM)

Nas últimas décadas, a maturidade de alguns mercados, a globalização e o crescente poder de barganha dos clientes aumentam ainda mais a necessidade das empresas em manterem e desenvolverem de forma eficaz seus clientes mais importantes. Neste contexto, ganham relevância os programas de Key Account Management (KAM), iniciativas corporativas que tratam de forma especial os clientes mais importantes do fornecedor. Para obter o desempenho financeiro superior, o programa de KAM precisa criar valor para o cliente para posterior apropriação de valor pelo fornecedor. Contudo, a maioria dos estudos enfatiza a apropriação de valor pelo fornecedor, porém poucas pesquisas investigam a criação de valor para o cliente em programas de KAM. Além disso, a maioria das pesquisas em marketing de relacionamento ainda foca muito nos impactos positivos do relacionamento. Dessa forma, é importante analisar empiricamente como é a implementação da criação de valor para o cliente em programas de KAM, identificando as principais dimensões e os fatores críticos. O objetivo do presente estudo é analisar o processo de criação de valor para o cliente em programas de Key Account Management (KAM) e propor um modelo de criação de valor para o cliente segundo a perspectiva da empresa fornecedora. As análises e o modelo são elaborados a partir de um processo de investigação abdutiva, ou seja, a combinação entre a fundamentação teórica sobre o conceito de valor e programas de KAM e a análise de conteúdo de 22 entrevistas em profundidade com especialistas em programas de KAM, profissionais de marketing/vendas que trabalham por pelo menos cinco anos com programas de KAM em grandes empresas no Brasil. O modelo proposto explica de forma integrada e sistemática como é a criação de valor para o cliente em programas de KAM segundo cinco dimensões (Desenvolvimento de relacionamentos; Entendimento dos direcionadores de valor; Desenvolvimento da proposta de valor; Comunicação da proposta de valor; e mensuração de valor), quatro moderadores (Orientação relacional do cliente; Formalização do programa de KAM para o cliente; Abordagem do fornecedor: \"orientada ao cliente\" vs. \"orientar o cliente\"; e Fit estratégico entre o fornecedor e o cliente) e três riscos (Não entrega do valor básico para o cliente; Rotatividade do Key Account Manager; e Sentimento de injustiça do cliente). Contribui-se com a teoria sobre o tema, ao incluir uma dimensão específica no modelo para desenvolvimento de relacionamentos do nível da díade (organização-organização) e indivíduo (funcionário-funcionário), e ao abordar não somente aspectos positivos do relacionamento, mas também os aspectos negativos (ou riscos da criação de valor para o cliente). Contribui-se também para a prática, ao prover uma visão mais ampla, sistemática e integradora dos diversos elementos da criação de valor para o cliente aos executivos das empresas que possuem programas de KAM, e ao recomendar práticas organizacionais que servem como guias para a tomada de decisão dos gestores de programas de KAM. Ademais, como a parte empírica do estudo é baseada no contexto brasileiro, amplia-se o conhecimento sobre KAM no Brasil. Por fim, apresentam-se as limitações do estudo com a agenda de pesquisas futuras

MDWEnet: a practical approach to achieving interoperability of model-driven web engineering methods

Current model-driven Web Engineering approaches (such as OO-H, UWE or WebML) provide a set of methods and supporting tools for a systematic design and development of Web applications. Each method addresses different concerns using separate models (content, navigation, presentation, business logic, etc.), and provide model compilers that produce most of the logic and Web pages of the application from these models. However, these proposals also have some limitations, especially for exchanging models or representing further modeling concerns, such as architectural styles, technology independence, or distribution. A possible solution to these issues is provided by making model-driven Web Engineering proposals interoperate, being able to complement each other, and to exchange models between the different tools. MDWEnet is a recent initiative started by a small group of researchers working on model-driven Web Engineering (MDWE). Its goal is to improve current practices and tools for the model-driven development of Web applications for better interoperability. The proposal is based on the strengths of current model-driven Web Engineering methods, and the existing experience and knowledge in the field. This paper presents the background, motivation, scope, and objectives of MDWEnet. Furthermore, it reports on the MDWEnet results and achievements so far, and its future plan of actions.

Empirical study on the maintainability of Web applications: Model-driven Engineering vs Code-centric

Model-driven Engineering (MDE) approaches are often acknowledged to improve the maintainability of the resulting applications. However, there is a scarcity of empirical evidence that backs their claimed benefits and limitations with respect to code-centric approaches. The purpose of this paper is to compare the performance and satisfaction of junior software maintainers while executing maintainability tasks on Web applications with two different development approaches, one being OOH4RIA, a model-driven approach, and the other being a code-centric approach based on Visual Studio .NET and the Agile Unified Process. We have conducted a quasi-experiment with 27 graduated students from the University of Alicante. They were randomly divided into two groups, and each group was assigned to a different Web application on which they performed a set of maintainability tasks. The results show that maintaining Web applications with OOH4RIA clearly improves the performance of subjects. It also tips the satisfaction balance in favor of OOH4RIA, although not significantly. Model-driven development methods seem to improve both the developers’ objective performance and subjective opinions on ease of use of the method. This notwithstanding, further experimentation is needed to be able to generalize the results to different populations, methods, languages and tools, different domains and different application sizes.

MDD vs. traditional software development: a practitioner’s subjective perspective

Context: Today’s project managers have a myriad of methods to choose from for the development of software applications. However, they lack empirical data about the character of these methods in terms of usefulness, ease of use or compatibility, all of these being relevant variables to assess the developer’s intention to use them. Objective: To compare three methods, each following a different paradigm (Model-Driven, Model-Based and Code-Centric) with respect to their adoption potential by junior software developers engaged in the development of the business layer of a Web 2.0 application. Method: We have conducted a quasi-experiment with 26 graduate students of the University of Alicante. The application developed was a Social Network, which was organized around a fixed set of modules. Three of them, similar in complexity, were used for the experiment. Subjects were asked to use a different method for each module, and then to answer a questionnaire that gathered their perceptions during such use. Results: The results show that the Model-Driven method is regarded as the most useful, although it is also considered the least compatible with previous developers’ experiences. They also show that junior software developers feel comfortable with the use of models, and that they are likely to use them if the models are accompanied by a Model-Driven development environment. Conclusions: Despite their relatively low level of compatibility, Model-Driven development methods seem to show a great potential for adoption. That said, however, further experimentation is needed to make it possible to generalize the results to a different population, different methods, other languages and tools, different domains or different application sizes.

Incremental model transformation for the evolution of model-driven systems

Model transformations are an integral part of model-driven development. Incremental updates are a key execution scenario for transformations in model-based systems, and are especially important for the evolution of such systems. This paper presents a strategy for the incremental maintenance of declarative, rule-based transformation executions. The strategy involves recording dependencies of the transformation execution on information from source models and from the transformation definition. Changes to the source models or the transformation itself can then be directly mapped to their effects on transformation execution, allowing changes to target models to be computed efficiently. This particular approach has many benefits. It supports changes to both source models and transformation definitions, it can be applied to incomplete transformation executions, and a priori knowledge of volatility can be used to further increase the efficiency of change propagation.

Essays on Development Policy and the Political Economy of Conflict

Electoral Rules and Leader Selection: Experimental Evidence from Ugandan Community Groups. Despite a large body of work documenting how electoral systems affect policy outcomes, less is known about their impact on leader selection. We study this by comparing two types of participatory decision making in Ugandan community groups: (i) vote by secret ballot and (ii) open discussion with consensus. Random assignment allows us to estimate the causal impact of the rules on leader types and social service delivery. Vote groups are found to elect leaders more similar to the average member while discussion group leaders are positively selected on socio-economic characteristics. Further, dropout rates are significantly higher in discussion groups, particularly for poorer members. After 3.5 years, vote groups are larger in size and their members save less and get smaller loans. We conclude that the secret ballot vote creates more inclusive groups while open discussion groups favor the already economically successful. Preparing for Genocide: Community Meetings in Rwanda. How do political elites prepare the civilian population for participation in violent conflict? We empirically investigate this question using data from the Rwandan Genocide in 1994. Every Saturday before 1994, Rwandan villagers had to meet to work on community infrastructure. The practice was highly politicized and, according to anecdotal evidence, regularly used by the political elites for spreading propaganda in the years before the genocide. This paper presents the first quantitative evidence of this abuse of the community meetings. To establish causality, we exploit cross-sectional variation in meeting intensity induced by exogenous weather fluctuations. We find that an additional rainy Saturday resulted in a five percent lower civilian participation rate in genocide violence. Selection into Borrowing: Survey Evidence from Uganda. In this paper, I study how changes to the standard credit contract affect loan demand and selection into borrowing, using a representative sample of urban micro enterprises, most with no borrowing experience. Hypothetical loan demand questions are used to test whether firm owners respond to changes in loans' contractual terms and whether take-up varies by firms' risk type and other firm owner characteristics. The results indicate that contracts with lower interest rates and less stringent collateral requirements attract less risky borrowers, suggesting that there is scope for improvement of standard financial contract terms. Credit Contract Structure and Firm Growth: Evidence from a Randomized Control Trial. We study the effects of credit contract structure on firm outcomes among small and medium sized firms. A randomized control trial was carried out to distinguish between some of the key constraints to efficient credit use connected to the firms' business environment and production function, namely (i) backloaded returns (ii) uncertain returns and (iii) indivisible fixed costs. Each firm was followed for the 1-year loan cycle. We describe the experiment and present preliminary results from the first 754 out of 2,340 firms to have completed the loan cycle. Firms offered a grace period have higher profits and higher household income than firms receiving a rebate later on as well as the control group. They also increased the number of paid employees  and reduced the number of unpaid employees, an effect also found among firms that received a cash subsidy at the beginning of the loan cycle. We discuss potential mechanisms behind these effects.

Extending Automated Testing To High-level Software Requirements : A study on the feasibility of automated acceptance-testing

Automated acceptance testing is the testing of software done in higher level to test whether the system abides by the requirements desired by the business clients by the use of piece of script other than the software itself. This project is a study of the feasibility of acceptance tests written in Behavior Driven Development principle. The project includes an implementation part where automated accep- tance testing is written for Touch-point web application developed by Dewire (a software consultant company) for Telia (a telecom company) from the require- ments received from the customer (Telia). The automated acceptance testing is in Cucumber-Selenium framework which enforces Behavior Driven Development principles. The purpose of the implementation is to verify the practicability of this style of acceptance testing. From the completion of implementation, it was concluded that all the requirements from customer in real world can be converted into executable specifications and the process was not at all time-consuming or difficult for a low-experienced programmer like the author itself. The project also includes survey to measure the learnability and understandability of Gherkin- the language that Cucumber understands. The survey consist of some Gherkin exam- ples followed with questions that include making changes to the Gherkin exam- ples. Survey had 3 parts: first being easy, second medium and third most difficult. Survey also had a linear scale from 1 to 5 to rate the difficulty level for each part of the survey. 1 stood for very easy and 5 for very difficult. Time when the partic- ipants began the survey was also taken in order to calculate the total time taken by the participants to learn and answer the questions. Survey was taken by 18 of the employers of Dewire who had primary working role as one of the programmer, tester and project manager. In the result, tester and project manager were grouped as non-programmer. The survey concluded that it is very easy and quick to learn Gherkin. While the participants rated Gherkin as very easy.