Participatory design and business modeling

En este proyecto miraremos como los campos de Diseño Participativo de las tecnologías de la información (DP, Participatory IT Design) y el diseño empresarial de modelos de negocio interactúan entre sí. Exploraremos el hueco que existe en los asuntos que aborda un proyecto de DP señalado por Kyng (2010). DP es una forma de enfocar el diseño para diseñar sistemas informáticos que tiene su propia ideología, haciendo mucho hincapié en la participación de los usuarios en el proceso. Esta ideología propia de DP da paso a un conjunto de métodos y herramientas para diseñar. DP tiene sus orígenes en Escandinavia en la década de los setenta cuando cambios de progreso social de la sociedad se introdujeron en el lugar de trabajo. Ya hay algunos investigadores del campo de DP que empiezan a estudiar este hueco señalado por Kyng. Un modelo de negocios es la forma en que un negocio crea, entrega y captura valor. En las últimas décadas las empresas informáticas han cambiado su modelo de negocios, transformándose en una oferta de servicios informáticos mayoritariamente. El mundo empresarial ya conoce los beneficios de las metodologías de diseño orientadas al usuario, sin embargo no acaban de ser adoptadas por las empresas informáticas. En el proyecto buscamos responder a las preguntas que surgen al juntar estas dos áreas de estudio. ¿Cómo interpreta la comunidad de DP el mundo empresarial? ¿La teoría empresarial como trata la metodología de diseño orientado al usuario? ¿Cómo afecta en una compañía real su política de usuario a su modelo de negocio y que técnicas utilizan para involucrar al usuario? ¿Qué intereses comunes y opuestos existen entre DP y el mundo empresarial? ¿Cuál es el futuro de DP en el mundo empresarial? En cuanto a la metodología del proyecto realice un estudio de la literatura de los campos de DP y el mundo empresarial usando fuentes recomendadas por expertos de cada área así como trabajos encontrados por mi propia cuenta que eran relevantes al tema tratado. Además realice un estudio de compañías desarrolladoras de software locales a Copenhague. Mediante una serie de visitas y entrevistas con esas compañías obtuve información del modelo de negocio y proceso de desarrollo de software de las mismas. También dialogamos en cuanto a su visión de DP y metodologías de diseño orientado al usuario y como se podrían beneficiar de ellas. Durante el desarrollo del proyecto he encontrado que DP y el mundo empresarial tienen dos visiones muy diferentes. Mientras uno busca obtener el máximo beneficio el otro busca apoderar a los usuarios en su área de trabajo. Aunque al igual que DP las empresas necesitan obtener información acerca de los usuario como sus necesidades, gustos, etc. Está claro que el software producido para el mundo empresarial tiene mucho espacio para mejorar ya que suele venir con manuales de instrucciones extensos y es necesario un entrenamiento previo para su utilización. Un problema importante de la introducción de DP en las empresas es la falta de predisposición de los usuarios en colaborar en el proceso de desarrollo ya que no hay demasiada tendencia a usuarios a dar feedback. El trabajo de investigacion de Timpka y Vimarlund (1998) Participatory Design In Economic Terms: A Theoretical Discussion llega a la conclusión de que DP es económicamente favorable para los desarrolladores. Pero omite muchos factores críticos de la economía de una empresa. En cuanto al futuro de DP en el mundo empresarial, DP tiene que adaptarse a las compañías desarrolladoras de software. A sus necesidades y teniendo en cuenta sus límites de recursos. Pero hay ciertos aspectos que deben ser abordados. El primer aspecto es el uso de recursos en las técnicas de DP, ya que utilizan demasiados. Otro aspecto que debería abordar es el uso de las nuevas tecnologías de comunicación y redes sociales, ya que apenas se han utilizado en DP. Mientras que otras áreas de estudio han hecho uso de estas nuevas tecnologías y se han revolucionado DP no ha sido capaz de integrarlas en sus técnicas. Por último en el proyecto realizo una comparativa del actual modelo de negocios y proceso de desarrollo de software de la compañía Forecast.it. En esta comparativa miro como cambiaria el negocio en el caso de que se produjeran cambios en ella al introducir la ideología de DP. Donde más se notan los cambios seria en su esquema de desarrollo de software ya que habría que hacer hueco para nuevos factores y pasos.

An Approach to Representing the Process of Information Business Modeling

The compact and visualized documenting of information business modeling is a major prerequisite for comprehending its basic concepts, as well as for its effective application and improvement. The documenting of this process is related to its modeling. Thus, the process of information business modeling can be represented by its own tools. Being based on this thesis, the authors suggest an approach to representing the process of information business modeling. A profile for its documenting has been developed for the purpose.

Business Modeling of the Application Architecture of the Bulgarian Folklore Artery

In an attempt to answer the need of wider accessibility and popularization of the treasury of Bulgarian folklore, a team from the Institute of Mathematics and Informatics at the Bulgarian Academy of Sciences has planned to develop the Bulgarian folklore artery within the national project ―Knowledge Technologies for Creation of Digital Presentation and Significant Repositories of Folklore Heritage‖. This paper presents the process of business modeling of the application architecture of the Bulgarian folklore artery, which aids requirements analysis, application design and its software implementation. The folklore domain process model is made in the context of the target social applications—e-learning, virtual expositions of folklore artifacts, research, news, cultural/ethno-tourism, etc. The basic processes are analyzed and modeled and some inferences are made for the use cases and requirements specification of the Bulgarian folklore artery application. As a conclusion the application architecture of the Bulgarian folklore artery is presented.

Pattern-based analysis of EAI languages : the case of the business modelling language

Enterprise Application Integration (EAI) is a challenging area that is attracting growing attention from the software industry and the research community. A landscape of languages and techniques for EAI has emerged and is continuously being enriched with new proposals from different software vendors and coalitions. However, little or no effort has been dedicated to systematically evaluate and compare these languages and techniques. The work reported in this paper is a first step in this direction. It presents an in-depth analysis of a language, namely the Business Modeling Language, specifically developed for EAI. The framework used for this analysis is based on a number of workflow and communication patterns. This framework provides a basis for evaluating the advantages and drawbacks of EAI languages with respect to recurrent problems and situations.

Parameter estimation and equation formulation in Business Dynamics

System Dynamics enables modelling and simulation of highly non-linear feedback systems to predict future system behaviour. Parameter estimation and equation formulation are techniques in System Dynamics, used to retrieve the values of parameters or the equations for ?ows and/or variables. These techniques are crucial for the annotations and thereafter the simulation. This paper critically examines existing and well established approaches in parameter estimation and equation formulation along with their limitations, identifying performance gaps as well as providing directions for potential future research.

Calculating the application criticality and business risk from technology obsolescence

The problem of technology obsolescence in information intensive businesses (software and hardware no longer being supported and replaced by improved and different solutions) and a cost constrained market can severely increase costs and operational, and ultimately reputation risk. Although many businesses recognise technological obsolescence, the pervasive nature of technology often means they have little information to identify the risk and location of pending obsolescence and little money to apply to the solution. This paper presents a low cost structured method to identify obsolete software and the risk of their obsolescence where the structure of a business and its supporting IT resources can be captured, modelled, analysed and the risk to the business of technology obsolescence identified to enable remedial action using qualified obsolescence information. The technique is based on a structured modelling approach using enterprise architecture models and a heatmap algorithm to highlight high risk obsolescent elements. The method has been tested and applied in practice in three consulting studies carried out by Capgemini involving four UK police forces. However the generic technique could be applied to any industry based on plans to improve it using ontology framework methods. This paper contains details of enterprise architecture meta-models and related modelling.

Advanced Business Simulations-Incorporating business and process execution data

Key Performance Indicators (KPIs) and their predictions are widely used by the enterprises for informed decision making. Nevertheless , a very important factor, which is generally overlooked, is that the top level strategic KPIs are actually driven by the operational level business processes. These two domains are, however, mostly segregated and analysed in silos with different Business Intelligence solutions. In this paper, we are proposing an approach for advanced Business Simulations, which converges the two domains by utilising process execution & business data, and concepts from Business Dynamics (BD) and Business Ontologies, to promote better system understanding and detailed KPI predictions. Our approach incorporates the automated creation of Causal Loop Diagrams, thus empowering the analyst to critically examine the complex dependencies hidden in the massive amounts of available enterprise data. We have further evaluated our proposed approach in the context of a retail use-case that involved verification of the automatically generated causal models by a domain expert.

基于样本程序的领域开发平台的研究与实践

为了解决行业应用软件开发存在的问题,在全面分析研究行业应用软件和大量实践的基础上,提出了与组件业务建模(CBM)不同的组装业务建模(ABM)和样本程序,并设计了一个企业级的基于样本程序的领域开发平台来支持行业应用的开发和提升行业应用的开发效率与效果。平台通过组装业务建模(ABM)与组件业务建模(CBM)来驱动行业应用软件的开发,并通过样本程序来对行业应用软件的开发工作进行实际指导。实验结果表明了该平台能够有效地提高软件复用率,极大地缩短行业应用软件的开发周期,减少信息系统的成本支出。

Modelling capability and affordance as properties of human/machine resource systems

Understanding how and why the capability of one set of business resources, its structural arrangements and mechanisms compared to another works can provide competitive advantage in terms of new business processes and product and service development. However, most business models of capability are descriptive and lack formal modelling language to qualitatively and quantifiably compare capabilities, Gibson’s theory of affordance, the potential for action, provides a formal basis for a more robust and quantitative model, but most formal affordance models are complex and abstract and lack support for real-world applications. We aim to understand the ‘how’ and ‘why’ of business capability, by developing a quantitative and qualitative model that underpins earlier work on Capability-Affordance Modelling – CAM. This paper integrates an affordance based capability model and the formalism of Coloured Petri Nets to develop a simulation model. Using the model, we show how capability depends on the space time path of interacting resources, the mechanism of transition and specific critical affordance factors relating to the values of the variables for resources, people and physical objects. We show how the model can identify the capabilities of resources to enable the capability to inject a drug and anaesthetise a patient.

KPIs and their properties defined with the EXTREME method

Key Performance Indicators (KPIs) are the main instruments of Business Performance Management. KPIs are the measures that are translated to both the strategy and the business process. These measures are often designed for an industry sector with the assumptions about business processes in organizations. However, the assumptions can be too incomplete to guarantee the required properties of KPIs. This raises the need to validate the properties of KPIs prior to their application to performance measurement. This paper applies the method called EXecutable Requirements Engineering Management and Evolution (EXTREME) for validation of the KPI definitions. EXTREME semantically relates the goal modeling, conceptual modeling and protocol modeling techniques into one methodology. The synchronous composition built into protocol modeling enables raceability of goals in protocol models and constructive definitions of a KPI. The application of the method clarifies the meaning of KPI properties and procedures of their assessment and validation.

Definição de requisitos de software baseada numa arquitetura de modelagem de negócios

Não é uma tarefa fácil definir requisitos para os sistemas de software que darão suporte a um negócio, dada a dinâmica de mudanças nos processos. O levantamento de requisitos tem sido feito de forma empírica, sem o apoio de métodos sistematizados que garantam o desenvolvimento baseado nos reais objetivos do negócio. A engenharia de software carece de métodos que tornem mais ordenadas e metódicas as etapas de modelagem de negócios e de levantamento de requisitos de um sistema. Neste artigo é apresentada uma metodologia de desenvolvimento de software resultante da incorporação de atividades propostas para modelagem de negócios e levantamento de requisitos, baseadas em uma arquitetura de modelagem de negócios. Essas atividades tornam o desenvolvimento de software mais sistemático e alinhado aos objetivos da organização, e podem ser incorporadas em qualquer metodologia de desenvolvimento baseada no UP (Unified Process - Processo Unificado).

Análise de linguagens de modelagem de processos de um modelo de referência na cadeia de suprimentos

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

Proposta de uma estrutura conceitual de modelagem de empresas para implementação do ERP5 baseada na ISO 19440:2007

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

Using ORG-Master for Knowledge Based Organizational Change

* Under Knowledge Infrastructure we imply all the means that enable effective knowledge management within organization ~ knowledge process support.