Information system analysis and conceptual database design in production environments with M1

A methodology, called M¹, for information system analysis and database design of production environments is presented in detail. The originality of M¹ is to recognize the importance of integrating factory analysis methods for data and user requirements definition with logical database design methods for database specification. M¹ is a pragmatic, complete, manual methodology involving three major phases: Enterprise Modelling and Analysis which is the phase devoted to accurate analysis of the structure of the enterprise and precise definition of the scope of the future database application; Conceptual Design which is the phase concerned with data modelling of both static and dynamic properties of the enterprise; and Implementation Design which is the phase dealing with adaptation of the conceptual schema to the data model specifications of the physical database system used for application development and tuning performances of the physical system. The methodology is explained and illustrated by means of an example related to a Flexible Manufacturing System for mechanical parts.     

Development Support Tools for Enterprise Resource Planning

Implementing an enterprise system involves capturing all information necessary to make business processes work in an integrated fashion, and reflecting this integration in source code. Enterprise resource planning implementations should also exploit reuse of existing system elements. ERP tools typically work on top of a framework, using prefabricated modules to create customized variants of the system. Among the free and open source ERP systems, only ERP5 offers a comprehensive set of tools tailored to its framework that, together with other off-the-shelf tools, provide support for creating new modules and entire new systems.     

Intelligent support for systems development: The notion and the issues

Enterprise modelling and information systems modelling have traditionally utilized techniques developed in the earlier disciplines of systems analysis and operational analysis. However, these tools have proved insufficient even for information systems modelling and their inadequacies make them less than ideal for enterprise modelling. Furthermore, it has proved difficult to integrate the techniques into a uniform framework representation. Extensive research since the early 1980s has produced support tools for information systems engineering in the academic sector which have generally failed to reach widespread commercial use. Commercially developed integrated support systems aimed at enterprise modelling and information system modelling use traditional techniques, with a lack of formalism. The purpose of this paper is to introduce a technique which overcomes the major inadequacies and which provides an integrating framework to represent both the information and the processing, at enterprise and systems modelling levels of abstraction. The technique is based on the use of a transition network, but extended to represent enterprise and system models in a meaningful way. The use of an intelligent repository, with associated processing of the formally defined requirements, specification and design statements, is novel, and provides the additional support to make the technique amenable to handling the design process from informal to formal specification. The use of a graphical user interface, linked directly to the deductive system and repository, ensures intuitive ease of use.     

Fundamentals of integrated dictionary/ directory systems

One of the most potent tools available to support achievement of control over an organization's information resource is the Integrated Dictionary/Directory (D/D) System. Use of a D/D System can assist in data inventory management, cost control and improving resiliency to changing requirements. A D/D System is composed of a database (describing the information resource), retrieval and analysis capabilities, interfaces (enabling other software to access the D/D) and data management tools. Some D/D Systems are independent from other software packages; some either are dependent on or are actually embedded in other data management systems. D/D Systems provide functions to assist in interfacing the D/D to other software and loading the D/D with meta-data from other software. Use of a D/D System is a first step toward achieving control of the data resource.     

Making Workflow Change Acceptable

Virtual professional communities are supported by network information systems composed from standard Internet tools. To satisfy the interests of all community members, a user-driven approach to requirements engineering is proposed that produces not only meaningful but also acceptable specifications. This approach is especially suited for workflow systems that support partially structured, evolving work processes. To ensure the acceptability, social norms must guide the specification process. The RENISYS specification method is introduced, which facilitates this process using composition norms as formal representations of social norms. Conceptual graph theory is used to represent four categories of knowledge definitions: type definitions, state definitions, action norms and composition norms. It is shown how the composition norms guide the legitimate user-driven specification process by analysing a case on the development of an electronic law journal.     

数据库系统应用基准测试规范设计方法

为准确度量数据库系统对领域应用系统的支撑能力,提出了一种应用基准测试规范设计方法,指导数据库系统的基准测试。提出以动作、环境、负载等信息项为框架,建立数据库系统使用需求集,规范初始信息格式;将使用需求初分为操作场景,建立关键变量矩阵,并应用K-means算法、层次式聚类等方法进行操作场景分组,确认典型应用系统集;设计了基准测试用例结构,提出了环境要求、事务要求、执行要求等重要信息项,并构建测试规范框架,描述了典型应用系统与应用基准测试规范的关系;通过实例应用,证明了该方法的可行性与适用性。所提方法可辅助解决应用系统在多个数据库系统中择优选型问题,也可用于数据库系统厂商自测,促进产品能力提升。     

敏捷开发平台的设计

敏捷开发平台是支持敏捷过程的软件开发平台,敏捷开发平台通过生成Java代码和读取存放在数据库中的配置数据,实现系统的可配置.这个平台包括一系列敏捷开发工具,敏捷组件、敏捷表单、敏捷查询等;同时,敏捷开发平台还实现了一套敏捷工作流系统和敏捷数据交换平台.敏捷开发平台对数据库的设计做了一些标准规范,有利于数据资源的有效利用.敏捷开发平台实现了系统设计标准化,能够支持在大型信息化项目中采用敏捷开发过程.     

Engineering model transformations with transML

Model transformation is one of the pillars of model-driven engineering (MDE). The increasing complexity of systems and modelling languages has dramatically raised the complexity and size of model transformations as well. Even though many transformation languages and tools have been proposed in the last few years, most of them are directed to the implementation phase of transformation development. In this way, even though transformations should be built using sound engineering principles—just like any other kind of software—there is currently a lack of cohesive support for the other phases of the transformation development, like requirements, analysis, design and testing. In this paper, we propose a unified family of languages to cover the life cycle of transformation development enabling the engineering of transformations. Moreover, following an MDE approach, we provide tools to partially automate the progressive refinement of models between the different phases and the generation of code for several transformation implementation languages.     

基于业务模式数据库的柔性ERP研究

传统的面向事务处理的经典ERP系统不能快速适应多变环境下的企业动态业务流程重组.提出了基于业务模式数据库的柔性ERP(BMDF-ERP)系统.该系统抽象企业无关的业务模式构建领域业务模式数据库,在具体实施时,根据需求将其映射为企业业务模式数据库,由明确完备的企业业务模式数据库来驱动实际运行的ERP系统,业务需求的变化只对应企业业务模式数据库中业务模式的配置.在电力行业的成功实施证明系统是可行的.     

Transfer of software engineering tools from information systems to production systems

This paper considers the prospects of transferring software-engineering methods and tools from the field of information systems (IS) to the field of production systems (PS). In particular, object-oriented programming is transferable to control programming by providing: (1) a standard, high-level, general purpose, real-time modules for controlling motion, logic and sequences; (2) detailed task specification; and (3) CAD/CAM database management and interaction with control. Additional transferable tools are man–machine interfaces for programmable logic controllers (PLC), robots, and numerically controlled (NC) machines. Current development of industrial standards should help provide full multi-platform support and connectivity and increase transfer of software development methods and tools from IS to PS.     

User interface specification with sequence diagrams: an application to the AIRBUS A380 Datalink system

The development of user interfaces for safety critical systems is driven by requirements specifications. Because user interface specifications are typically embedded within complex systems requirements specifications, they can be intractable to manage. Proprietary requirements specification tools do not support the user interface designer in modelling and specifying the user interface. In this paper, a new way of working with embedded user interface specifications is proposed, exploiting sequence diagrams with a hypertext structure for representing and retrieving use cases. This new tool concept is assessed through an application to the requirements specification for the Airbus A380 air traffic control Datalink system; engineers involved in the development of the Airbus cockpit used a prototype of the tool concept to resolve a set of user interface design anomalies in the requirements specification. The results of the study are positive and indicate the user interface to requirements specification tools which user interface designers themselves need.     

The construction of information management system prototypes in Ada

The use of a data-flow diagram and data dictionary for the requirements specification of an information management system is described together with the benefits to be gained from using prototypes. Construction of such prototypes in Ada is discussed in detail with a simple example being given. The use of a flexible user interface, generic data-flows, exception handlers for error conditions and a top-down design method that makes use of separate compilation indicates that Ada is an appropriate language for the development of such systems. Consideration is also given to the use of Ada in the construction of actual as well as prototype information systems.     

Enforceable component-based realtime contracts

We present enforceable component-based realtime contracts, the first extension of component-based software engineering technology that comprehensively supports adaptive realtime systems from specification all the way to the running system.To provide this support, we have extended component-based interface definition languages (IDLs) and component representations in repositories to express realtime requirements for components. The final software, which is assembled from the components, is then executed on a realtime operating system (RTOS) with the help of a component runtime system. RTOS resource managers and the IDL-extensions are based on the same mathematical foundation. Thus, the component runtime system can use information expressed in a component-oriented manner in the extended IDL to derive parameters for the task-based admission and scheduling in the RTOS. Once basic realtime properties can thus be guaranteed, runtime support can be extended to more elaborate schemes that also support adaptive applications (container-managed quality assurance).We claim that this study convincingly demonstrates how component-based software engineering can be extended to build systems with non-functional requirements.     

VIVACE: A framework for the systematic evaluation of variability support in process-aware information systems

ContextThe increasing adoption of process-aware information systems (PAISs) such as workflow management systems, enterprise resource planning systems, or case management systems, together with the high variability in business processes (e.g., sales processes may vary depending on the respective products and countries), has resulted in large industrial process model repositories. To cope with this business process variability, the proper management of process variants along the entire process lifecycle becomes crucial.ObjectiveThe goal of this paper is to develop a fundamental understanding of business process variability. In particular, the paper will provide a framework for assessing and comparing process variability approaches and the support they provide for the different phases of the business process lifecycle (i.e., process analysis and design, configuration, enactment, diagnosis, and evolution).MethodWe conducted a systematic literature review (SLR) in order to discover how process variability is supported by existing approaches.ResultsThe SLR resulted in 63 primary studies which were deeply analyzed. Based on this analysis, we derived the VIVACE framework. VIVACE allows assessing the expressiveness of a process modeling language regarding the explicit specification of process variability. Furthermore, the support provided by a process-aware information system to properly deal with process model variants can be assessed with VIVACE as well.ConclusionsVIVACE provides an empirically-grounded framework for process engineers that enables them to evaluate existing process variability approaches as well as to select that variability approach meeting their requirements best. Finally, it helps process engineers in implementing PAISs supporting process variability along the entire process lifecycle.     

通用信息管理系统开发平台的设计与实践

随着单位工作信息资源对于公开性、时效性、正确性的要求越来越严格,考虑到信息资源对决策的指导作用和部门信息共享的迫切需求,开发具备高度通用性与延伸性的可针对业务信息提供数据化解决方案的系统平台十分必要。在传统的信息系统基础上进行重新开发,基于规范化、专业化、人性化和模块化的设计思想,实现系统管理数据、规范化形成数据、规范化解析数据三大功能。简要阐述了本次通用信息管理系统设计开发的大致流程和具体事项。     

The role of context in decision making: some implications for database design

With increasing integration of computer systems through local and wide area communication networks, there exists the capability in many organizations to retrieve information from databases to support ad hoc decision making by many different users. The idea that information is a corporate resource is now something more than business school hype. But the implications of sharing data are only just dawning on the corporate mind. How do managers interpret data? Where decision making is carried out by several people, perhaps in several different locations for different purposes the same data is used in multiple decision contexts. This paper explores the role of context as a way of adding value to information from databases. Two types of context are defined and discussed in relation to some examples of decisions where the role of context is vital. These examples are taken from some empirical research conducted with users of spatial decision support systems. Here the use of background information on maps, for example roads, add context to maps which otherwise simply display statistical data. The paper concludes by suggesting a model of context based on the notion that context acts as a filter between user and database.     

A formal verification framework for static analysis

Static analysis tools, such as resource analyzers, give useful information on software systems, especially in real-time and safety-critical applications. Therefore, the question of the reliability of the obtained results is highly important. State-of-the-art static analyzers typically combine a range of complex techniques, make use of external tools, and evolve quickly. To formally verify such systems is not a realistic option. In this work, we propose a different approach whereby, instead of the tools, we formally verify the results of the tools. The central idea of such a formal verification framework for static analysis is the method-wise translation of the information about a program gathered during its static analysis into specification contracts that contain enough information for them to be verified automatically. We instantiate this framework with costa, a state-of-the-art static analysis system for sequential Java programs, for producing resource guarantees and KeY, a state-of-the-art verification tool, for formally verifying the correctness of such resource guarantees. Resource guarantees allow to be certain that programs will run within the indicated amount of resources, which may refer to memory consumption, number of instructions executed, etc. Our results show that the proposed tool cooperation can be used for automatically producing verified resource guarantees.     

Enterprise JavaBeans

Large web-based information systems make high demands on scalability, maintainability, reliability and security. In order to ease the development of such systems appropriate software architectures are needed. These architectures have to take into account business aspects as well as requisite tools and products. Such an architecture is offered by Sun Microsystems in the form of the Enterprise JavaBeans specification. Based on our experience from different projects we undertake a close examination of this architecture.