An industrial case study on variability handling in large enterprise software systems

ContextEnterprise software systems (e.g., enterprise resource planning software) are often deployed in different contexts (e.g., different organizations or different business units or branches of one organization). However, even though organizations, business units or branches have the same or similar business goals, they may differ in how they achieve these goals. Thus, many enterprise software systems are subject to variability and adapted depending on the context in which they are used.ObjectiveOur goal is to provide a snapshot of variability in large scale enterprise software systems. We aim at understanding the types of variability that occur in large industrial enterprise software systems. Furthermore, we aim at identifying how variability is handled in such systems.MethodWe performed an exploratory case study in two large software organizations, involving two large enterprise software systems. Data were collected through interviews and document analysis. Data were analyzed following a grounded theory approach.ResultsWe identified seven types of variability (e.g., functionality, infrastructure) and eight mechanisms to handle variability (e.g., add-ons, code switches).ConclusionsWe provide generic types for classifying variability in enterprise software systems, and reusable mechanisms for handling such variability. Some variability types and handling mechanisms for enterprise software systems found in the real world extend existing concepts and theories. Others confirm findings from previous research literature on variability in software in general and are therefore not specific to enterprise software systems. Our findings also offer a theoretical foundation for describing variability handling in practice. Future work needs to provide more evaluations of the theoretical foundations, and refine variability handling mechanisms into more detailed practices.     

Managing readiness-relevant activities for the organizational dimension of ERP implementation

An organization requires performing readiness-relevant activities to ensure successful implementation of an enterprise resource planning (ERP) system. This paper develops a novel approach to managing these interrelated activities to get ready for implementing an ERP system. The approach enables an organization to evaluate its ERP implementation readiness by assessing the degree to which it can achieve the interrelated readiness relevant activities using fuzzy cognitive maps. Based on the interrelationship degrees among the activities, the approach clusters the activities into manageable groups and prioritizes them. To help work out a readiness improvement plan, scenario analysis is conducted.     

计算机集成制造系统（CIMS）国际发展动态

ＣＩＭＳ（计算机集成制造系统）是世界上高技术开发项目之一．ＣＩＭＳ是涉及广泛技术领域的复杂系统，当前的研究课题覆盖了ＣＩＭ中方法学、技术和应用领域的部分内容．本文简要讨论ＣＩＭＳ的国际发展动态．     

企业滋生腐败与防范中的问题研究

分析了产生腐败的内在因素和外在环境;提出了企业在反腐败工作中存在的自律方面的问题、权利作用问题和监督部门的设置问题,并提出建立“分离分立不分家,制约制衡不掣肘”的防范机制。     

智能工程与控制技术：历史,发展与未来

本文综述了智能工程和控制技术的发展历程和基本问题。文中着重论述了人工智能在过程控制系统中的必要性及开发实时智能控制系统的步骤；对符号推理系统、耦合推理系统、人工神经网络和集成分布式智能系统的特点和局限进行了比较。最后讨论了计算机集成过程系统（ＣＩＰＳ）的基本问题、基础技术和发展前景。     

CIMSCLASS─—面向CIM的零件分类软件开发工具

介绍了一个能为工厂设置零件编码系统和开发零件分类系统的工具系统。该系统能适应用户的具体环境，能对零件的特征信息做较详细的描述和建立相应目标的零件分类系统，从而能在ＧＴ（成组技术）基础上为机械加工零件开发ＣＡＤ／ＣＡＰＰ／ＣＡＭ集成系统提供支持，以满足ＣＩＭＳ的需要。     

CIMS环境中的数据模式转换

本文在分析CIMS环境中数据模式冲关类型的基础上，提出一种互连数据库系统模式结构，论述了在异构数据库集成中解决模式冲突的基本方法．在这种方法体系中，不需要建立整个企业的全局数据模式，各局部DBA以简单的方式定义应用所需的模式变换，系统根据这种定义自动完成各种转换，使用户看到的模式和数据结果与应用要求的一致．     

多台并行随机CIMS可靠性的扩散估计界

ＣＩＭＳ可靠性模型随机研究的突出特点是工作站的并行结构使系统的状态个数呈现指数级增大，同时，并行结构与有限的缓冲库相互交织在一起，这使系统状态呈爆炸趋势，显然，对系统作精确的分析与系统呈现的状态爆炸趋势构成了难以解决的矛盾，如何解决这一矛盾正是ＣＩＭＳ随机理论有待开发的重要课题。我们把扩散近似方法引入到多台并行的ＣＩＭＳ可靠性模型中，以简单的连续过程描述了具有状态爆炸趋势的复杂离散过程，给出了ＣＩ     

企业信息化建设中的问题及对策

我国企业在信息化建设过程中取得了一些成果 ,也出现了不少问题 ,本文主要针对这种现状 ,指出了企业存在的一些问题 ,并就信息系统开发、维护和集成 ,提出了一些建议。     

一种独立于被管系统的网络性能管理系统

本文提出了一种在广播信道上基于倾听机制的独立网络性能管理系统。这种系统适用于用物理广播信道连接，但存在多种协议体系结构的网络系统，例如ＣＩＭＳ网络。