A system framework for OKP product planning in a cloud-based design environment

Nowadays, one-of-a-kind (OKP) companies, which generally operate in an 'engineer-to-order' business mode, strive to deliver individualized products with quality to achieve customer satisfaction. Thus, an accurate and prompt analysis of customer requirements (CRs) in the early design stage is critical to its success. However, most OKP companies are small or medium-sized enterprises (SMEs). Due to the limited resources and low product planning budget, they often cannot obtain abundant CR information nor can they afford the expense of complicated planning process. To address these issues, a system framework is proposed in support of OKP product planning process in a cloud-based design (CBD) environment. The challenges and future market niches of OKP companies are presented. The comparison of typical distributed systems shows that CBD, which utilizes advanced information technologies and business model, has advantages in providing sufficient resources, decreasing product development time span for OKP companies in a cost-efficient way. This article describes the proposed system architecture, the business interaction process and the information communication among customers, designers and marketing analysts at the product planning stage. To validate the proposed framework, a prototype system module MyProduct is under development in the CBD environment with an illustrative example.     

基于CAFISE Framework的高适应性面向服务软件开发

在企业及电子政务应用中,由资源分布异构及需求动态变化而产生的问题越来越严重,如何让应用快速适应这些变化一直是人们关注的一个研究难题.首先给出了一个面向服务的支持业务端编程的适应性软件结构框架CAFISE(convergent approach for information system evolution)Framework,然后给出了基于该框架的面向服务的适应性软件开发方法.CAFISE Framework对异构资源的服务化、业务化及开放动态的面向服务软件体系结构提供了较好的支持.基于该结构框架的开发方法,从对影响软件的环境要素分析入手,通过质量属性驱动的体系结构分析,重点针对应用要适应的变化进行结构设计,最终通过以体系结构为基础的业务端编程,实现面向服务应用的即时开发与演化.在实际项目中的使用及实验证明:用该框架和方法开发的面向服务应用,能够较好地适应异构资源的动态变化及用户业务变更,能以较低的代价实现企业及电子政务面向服务应用的持续演化.     

Linking Business Processes and Information Systems Provision in a Dynamic Environment

This paper discusses decision and communication processes which link strategic activity in a business with information systems development activity. We develop a model which illustrates these processes as observed in one company (AXA Sun Life, Bristol HQ), but we suggest there may be generalizable features. We use Role Activity Diagrams as our diagramming method.In most organizations it is impractical to achieve a fully articulated business model and IS architecture. Organizations do try to make development (or acquisition) of information systems which will serve business needs as orderly as they can, in circumstances which are inherently complex and unstable. We suggest that the degree of regularity which is achieved in IS development within the business context comes not so much from following one overarching plan, as from a continuous process of adjustment, in which local short-term plans are weighed against current understanding of the business's key interests. What is needed to aid this process is a general framework of communication and decision making within which plans can be reviewed and modified in the light of changing circumstances. This paper presents an attempt to reveal and represent such a framework.     

Multi-model driven collaborative development platform for service-oriented e-Business systems

Enterprises need to be responsive to meet dynamic businesses and requirements. Service-oriented architecture and Web services can improve e-Business systems to be integrated and flexible. This paper proposes a multi-model driven collaborative development platform for service-oriented e-Business systems. The platform provides engineers/consultants with three views, i.e., business view, process view, and service view to support service-oriented software engineering, top-down business design and bottom-up service composite and development. The views are kept consistent through model-driven translation mechanisms. The platform employs three models, i.e., service meta-model, process model and business model to implement the translation. On the platform, business and technical consultants/engineers can use the views designated for their roles to collaborate for a service-oriented e-Business system based at the distributed sites of, e.g., IT vendors and their clients. The collaboration is featured with visual development and rapid demonstration. Comparingly, most of the mainstream development environments focus on object-oriented application development other than service-oriented business process modeling. The platform has been developed and deployed in an innovation centre to be evaluated by visiting customers.     

基于SOA架构的立法决策支持系统研究

党的十八大报告将“全面推进依法治国”确立为推进政治建设和政治体制改革的重要任务,而立法工作是其中最重要的基础工作.立法工作相关信息化系统的建设为立法工作提供了重要技术支撑,而随着立法工作中各项业务系统的联系性需要更加紧密,集成度要求越来越高,信息资源的共享范围需要越来越广,使得各业务系统的互联互通和流程规范化等问题成为了立法工作信息化建设必须要面对的一个关键问题.单个的业务系统拓展、功能强化、硬件升级已经不能满足要求,而基于ESB（企业服务总线enterprise service bus）的架构平台,以服务作为基本管理单元提供了很好的解决方案,它可以消除不同业务系统之间的技术差异,让不同业务系统协调运作,从而实现不同业务之间的通信与资源整合.     

异构软件体系结构在军事领域的应用

信息化条件下,军事信息系统应满足互连、互通、互操作要求,实现横向集成和聚集。通过对比层次式软件体系结构和正交式软件体系结构,并将这两种异构的软件体系结构融合应用于军事信息系统的软件体系结构设计领域,提出了联合作战模拟系统的体系结构框架。这种异构软件体系结构的组合使得系统结构清晰,具有可扩展性,易于理解,同时提高了软件复用的粒度和开发效率,为军用软件体系结构设计提供了一种参考思路。     

业务流程管理与集成系统SynchroFLOW的软件体系结构

信息技术的快速发展和应用改变着企业的商业环境。面对市场竞争越来越激烈,如何提高系统柔性,以支持企业重组和业务流程再遣;如何集成异构系统,对原有系统资源的利用和保护。本文从业务域的角度提出了一种企业应用业务流程管理和集成系统SynchroFLOW的软件体系结构,该体系构架以企业业务需求的抽象与描述为基础,通过对企业应用业务流程、活动功能和活动参与者的信息交换机制的独立的封装,降低业务逻辑、业务数据和业务操作实体三者间的耦合,实现业务流程的柔性管理和异构环境下不同应用的功能集成。这样的系统不但具有较高的柔性和集成性,同时减轻需求确认和设计验证的难度和工作量,进而延长应用系统的生命周期。     

Architectural requirements for rapid development of agile manufacturing systems

As product life cycle becomes shortened, high product quality becomes necessary for survival, and continuous and unexpected change becomes key obstacles in success, the need for a method of rapidly and cost-effectively developing products, production facilities and supporting software including design, process planning, shop floor control systems becomes urgent. The essence of this concept of manufacturing would be characterized by adopting a new term “agility”. Agile manufacturing can be successfully accomplished using various well-defined system architecture. This paper provides a primary sketch of architectural requirements for rapid development of agile manufacturing systems.There are several aspects of system architecture : control, function, process, information, communication, distribution, development, and implementation.In the past, the confusion of those architectures prohibited the successful construction of the automated CIM systems.     

铁路客运专线信息系统总体架构设计

复杂信息系统的总体架构不仅定义了系统的组织结构和拓扑结构,并且显示了系统需求和构成系统元素之间的关系,是系统设计的核心工作、并对研发和实施具有重要的指导意义。实现一流信息化水平的基础前提是打造一流的总体技术架构。对于这一问题进行了研究,依据总体架构的结构,依次对业务系统设计原则、统一通讯网络平台、资源共享平台等6个方面进行了具体阐述,构建了统一的客运专线信息系统总体技术架构。     

An integration framework for product lifecycle management

The need for integrating business and technical information systems, allowing partners to collaborate effectively in creating innovative products, has motivated the design and deployment of a novel integration framework for product lifecycle management. The time is ripe for such an integration framework because of the convergence of three important developments, almost in a perfect storm: (1) maturity of standardized product data and meta-data models, and standardized engineering and business processes; (2) emergence of service-oriented architecture for information sharing; and (3) availability of robust middleware to implement them. These developments allow engineering and business objects and processes to be built or composed as modular pieces of software in the form of services that can communicate with each other and be used across different parts of a business. These modular software pieces can be reused and reconfigured in new ways as business conditions change, thereby saving time and money for companies. This paper describes the business and technical aspects of an integration framework for product lifecycle management using open standards and service-oriented architecture.     

业务活动驱动系统体系结构执行研究

针对可执行体系结构研究中难以将业务体系结构的执行对应到系统体系结构的执行,并最终形成内在一致的执行体,提出了业务活动驱动系统体系结构执行的方法。该方法根据DoDAF中业务活动与系统功能多对多的关系,将业务活动用更详细的业务过程模型进行描述,并将过程模型中的行为单元对应到系统功能并触发该功能的执行。系统功能的执行将相应地触发一系列系统功能的执行,系统功能之间的系统数据交换将通过系统通信描述（SV-2）中的连接来实现,这样就建立起业务体系结构与系统体系结构之间的联系,并最终形成整个体系结构内在一致的执行体。该方法有效地解决了业务活动与系统功能之间多对多,无法形成内在一致的执行体问题,为体系结构的执行提供了一个明确、具体的可实施方案。     

The adoption and design methodologies of component-based enterprise systems

One of the major investments of information technologies in large companies in the past decade has been the enterprise system. Although the enterprise system has the advantages of managing and integrating almost all of the business processes in the whole company, there have been strong criticisms that the enterprise system often imposes its own logic or business process on a company and lacks flexibility and adaptability in today's dynamic business environment. The goal of this paper is to outline a new approach in enterprise system development. We analyse the factors that affect the adoption of enterprise systems. Market and business changes, and advances in information technologies call for a more flexible, open, and scalable enterprise architecture. We describe the process that Dell Computer Corporation took in adopting its component-based enterprise system architecture. The Dell example has demonstrated the importance of fit between business information systems and fundamental organizational dimensions of the company including strategy, business environment, and organizational structure. We also discuss the design methodologies for component-based enterprise system design. We take a coordination perspective, both at the software level and the organizational level, in addressing the design methodologies for component-based enterprise system development.     

过程系统体系结构及信息集成

体系结构是指导大型复杂综合自动化系统的原则和框架,信息集成是分布式综合自动 化系统成功运行的基础.以石化企业为背景,综合研究了过程企业体系结构和信息集成问题.提 出了包含信息、功能、组织、产品和资源等五个视图及需求分析,初步设计和详细设计三个主要 阶段的体系结构.进一步探讨了过程企业方法库、管理数据库、实时数据库和装置模型库的构建 方法,提出了基于C0RBA标准的分布式信息集成模型.     

管理领域面向方面软件体系结构及软件过程

软件体系结构设计是构建大型管理领域系统的关键步骤,同时面向方面的软件开发已成为解决软件复杂性的有效方法。该文基于面向方面软件开发方法提出了管理领域系统建设的“4+1”关注点视图,针对“4+1”关注点视图提出了面向管理领域、基于服务实现的面向方面软件体系结构。基于该软件体系结构开发的管理业务支持平台及其支持下的软件开发过程可以缩短软件开发周期,改善软件一致性和可维护性,使软件具有更好的演化能力。     

BP''s multi-enterprise asset management system

BP is one of the largest energy companies in the world with 2003 revenues of $233 billion. In this paper, we analyse its use of an innovative ‘multi-enterprise asset management system’ that supports and enables the asset management strategy of BP's exploration and production division on the UK continental shelf (UKCS). The analysis focuses on how BP connects its business processes with over 1500 suppliers to co-ordinate the maintenance, operation and repair of specialised exploration and production equipment. The systems strategy is novel because it takes the enterprise computing concept and implements it across organisational boundaries—hence the term ‘multi-enterprise system’. This use of a shared system with all of its suppliers is distinctive from the most common way of connecting with economic partners which is to use shared data systems based on common data standards and communication technologies such as EDI and more recently XML-based systems within vertical industries such as RosettaNet. The design of the multi-enterprise system is based on a sophisticated business process management system called Maximo and this is used to illustrate the systems design aspect of the overall information system in the broader contexts of business strategy and information technology infrastructure.     

EAFoC: Enterprise Architecture Framework Based on Commonality

The recent rapid development in information systems （ISs） has resulted in a critical need for integration and interoperability between heterogeneous ISs in various domains, using specific commonalities. However, stovepipe systems have been caused due to inconsistencies in planning IS architecture among stakeholders. So far, there has been no research on an enterprise architecture framework （EAF） that can satisfy with the coefficient factors of system architecture （SA） and enterprise architecture （EA）. This paper proposes a new EAF that can resolve the problems inherent in existing legacy EAFs and their features. EAFoC （Enterprise Architecture Framework based on Commonality） is based on commonality that can be satisfied as the coefficient factors in both SA and EA within a common information technology （IT） domain. Thus, it should be possible to integrate an established heterogeneous framework for each stakeholder＇s view. Consequently, the most important contribution of this paper is to establish the appropriate EAFoC for the development of consistent IS architecture, smooth communication among stakeholders, systematic integration management of diversified and complicated new IT technologies, interoperability among heterogeneous ISs, and reusability based on commonality with other platforms.     

基于Java ME和Java EE的移动商务系统设计与实现

随着移动通信广泛应用和电子商务技术的成熟壮大,移动商务已经具备了发展的基础条件,电子商务逐渐向移动商务迁移,但移动商务服务领域仍很薄弱.本文针对移动商务环境,提出了一种基于Java ME和Java EE的移动商务系统架构,并进行系统分析与设计,采用Eclipse、WTK等开发工具编程实现,经过实验证明该系统能够有效地实现移动商务处理,该架构和开发技术可以应用于移动商务服务系统以及其他移动应用系统的构建.     

Formalization and analysis of the REST architecture from the process algebra perspective

As one of the most promising architectural styles, REpresentational State Transfer (REST) was proposed to support a scalable and reliable design for large-scale distributed hypermedia systems such as the World Wide Web (WWW). However, the rapid development of RESTful systems brings the misunderstanding and misapplying of the REST architecture. As a consequence, considerable confusions about REST exist and many examples of supposedly RESTful applications violate key REST constraints. Thus, it is of significant importance to give a better and explicit understanding of REST architecture to guide the design and implementations of RESTful systems.In this paper, we give a formalization and analysis of the REST architecture from the perspective of Communicating Sequential Processes (CSP), which is one of the most famous process algebras. In particular, we present a formal model to capture essential features for the REST architecture, where components (together with one connector) of RESTful systems are modeled as CSP processes. Besides, resources are also abstracted as CSP processes. Furthermore, all the REST constraints, including Client–Server, Cacheable, Stateless, Uniform Interface, Layered and Code-On-Demand, are described in our framework and implemented in the model checker Process Analysis Toolkit (PAT) to check whether a system breaks REST constraints or not. It is difficult to ensure that a system is RESTful system, because many unRESTful systems may also contain unRESTful properties besides satisfying the six REST constraints. Thus, a complementary approach is proposed in this paper to check the system from a different perspective; that is, if a system breaks any specification of the REST constraints, then it is not a RESTful system. Finally, to show the feasibility of our approach, we illustrate a case study about an application scenario for environment monitoring. One feature of the proposed framework for the REST architecture is that it not only confines to HyperText Transport Protocol (HTTP) but can also be applied to other REST-compliant protocols, e.g., Constrained Application Protocol (CoAP). Consequently, through the general framework, a better understanding of the REST architecture can be achieved, and moreover, implementations and designs of RESTful systems can benefit from it.     

基于以太网的民用飞机客舱网络架构设计

客舱系统是民机航电系统的重要组成部分,主要包括客舱核心系统、机载娱乐系统和外部通信系统三大部分.本文通过对客舱典型业务、客舱网络设计要求和客舱常用设备的分析,结合对以太网技术的研究,设计出一套满足当前客舱典型业务的一体化网络架构方案,并对该网络架构中重要连接设备做出了详细功能说明的,最后使用OPNET网络仿真工具对该网络架构进行了仿真验证,表明了客舱一体化网络架构的优越性和可行性.