敦煌壁画计算机查询与管理信息系统设计

敦煌莫高窟是人类宝贵的文化遗产,利用飞速发展的计算机技术有效地管理和应用敦煌壁画有着重要意义。详细介绍了作为“敦煌壁画计算机存贮与管理信息系统”研究的一部分的查询与管理信息系统的组成、数据结构、系统设计与实施。该系统将为敦煌莫高窟壁画、塑像等文物图像数据永久保存、修复、还原和进一步开发研究等提供服务。     

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 KeY tool

KeY is a tool that provides facilities for formal specification and verification of programs within a commercial platform for UML based software development. Using the KeY tool, formal methods and object-oriented development techniques are applied in an integrated manner. Formal specification is performed using the Object Constraint Language (OCL), which is part of the UML standard. KeY provides support for the authoring and formal analysis of OCL constraints. The target language of KeY based development is Java Card DL, a proper subset of Java for smart card applications and embedded systems. KeY uses a dynamic logic for Java Card DL to express proof obligations, and provides a state-of-the-art theorem prover for interactive and automated verification. Apart from its integration into UML based software development, a characteristic feature of KeY is that formal specification and verification can be introduced incrementally.     

Verification of external specifications of reactive systems

External specification is currently approached by specification languages for describing and analyzing system requirements. The external specification can be defined during the early stages of the system development and can be very useful for: checking the class/system/subsystem requirements; checking the system composition; evaluating costs of reuse; defining validated reference requirements, histories, and traces for the final validation. The paper presents a collection of criteria in order to formally verify the external specification of reactive systems/subsystems. The verification criteria are grounded on the Tempo Reale object-oriented language (TROL) specification model for real-time systems. In TROL, the external specification is expressed in terms of ports and clauses with temporal constraints. The goal of the verification criteria presented is to check the completeness and consistency of the external specification with special attention to temporal constraints. These criteria can be applied to other real-time specification models and have been enforced in the tool object oriented machine state (TOOMS) tool. A practical example illustrates the verification process that embodies these criteria     

SMV的观察迁移系统的模型检测分析

模型检验技术是开发高可信系统的重要途径.提出了一种基于定理证明的模型验证方法,并实现了工具验证.它以代数规约语言CafeOBJ描述系统的无限状态并把它转换成有限状态的SMV规约.通过观察迁移系统,证明产生的SMV规约的反例即CafeOBJ规约的反例,来找出开发早期阶段的系统的潜在错误,从而避免时间、金钱的耗费及重复性的劳动.     

Computer-Aided Systems Engineering Methodology Support and Its Effect on the Output of Structured Analysis

The information systems development literature indicates that there is no conclusive, empirical evidence that CASE improves the quality of system specifications or the resulting information systems. One role of a CASE tool is to serve as a methodology companion—to assist an analyst in the creation of documentation passed to succeeding phases of the life cycle, and to guide the analyst through a particular systems development methodology. A framework for comparing the level of methodology support provided by a CASE tool is proposed and applied to 27 structured analysis methodology rules. The framework contains seven levels of rule enforcement, ranging from real-time enforcement of a rule to the absence of enforcement for a rule. The methodology enforcement framework is then applied to two popular, commercial CASE tools. Each CASE tool was used by eight project teams over a two month period to construct a functional specification for a hotel information system. The goal of the study was to examine the influence on the functional specification of the level of methodology support provided by the CASE tool for each structured analysis methodology rule. Methodology errors in the system specification were noted for each structured analysis methodology rule. An analysis of the frequency of errors indicates that internal consistency rules are easily adhered to regardless of the level of methodology support provided by the CASE tool, while hierarchical consistency rules are adhered to more frequently in the presence of rigorous methodology support.     

一个基于Web技术的网络银行系统的B方法设计与实现

B方法作为少数几种具有较强商业化工具支持的形式化方法之一,支持规格说明到代码生成的全部开发周期。文章将B方法应用于网络银行系统模型开发。此方法提供了系统的需求和可执行代码之间的中间过程。整个开发过程中的规格说明书写以及细化都使用Atelier B。     

A service creation environment based on scenarios

Scenarios are often constructed for illustrating example runs through reactive system. Scenarios that describe possible interactions between a system and its environment are widely used in requirement engineering, as a means for users to communicate their functional requirements. Various software development methods use scenarios to define user requirements, but often lack tool support. Existing tools are graphical editors rather than tool support for design. This paper presents a service creation environment for elicitation, integration, verification and validation of scenarios. A semi-formal language is defined for user oriented scenario representation, and a prototype tool implementing an algorithm that integrates them for formal specification generation. This specification is then used to automatically find and report inconsistencies in the scenarios.     

The RAISE language,method and tools

This paper presents the RAISE¹ software development method, its associated specification language, and the tools supporting it. The RAISE method enables the stepwise development of both sequential and concurrent software from abstract specification through design to implementation. All stages of RAISE software development are expressed in the wide-spectrum RAISE specification language. The RAISE tools form an integrated tool environment supporting both language and method.The paper surveys RAISE and furthermore, more detailed presentations of major RAISE results are provided. The subjects of these are (a) an example of the use of the RAISE method and language, and (b) a presentation of the mathematical semantics of the RAISE specification language.     

基于领域的需求规格生成工具的设计与实现

需求分析是软件开发过程中的重要环节。该文探讨需求分析过程中存在的问题,提出一个需求规格元模型,对用户功能性需求的获取、分析方法的规范和改进具有指导作用。基于该元模型实现了一个面向领域的需求规格生成工具,给出一个基于物流领域的定单管理系统的应用实例。     

Compositional performance modelling with the TIPPtool

Stochastic process algebras have been proposed as compositional specification formalisms for performance models. In this paper, we describe a tool which aims at realising all beneficial aspects of compositional performance modelling, the TIPPtool. It incorporates methods for compositional specification as well as solution, based on state-of-the-art techniques, and wrapped in a user-friendly graphical front end. Apart from highlighting the general benefits of the tool, we also discuss some lessons learned during development and application of the TIPPtool. A non-trivial model of a real life communication system serves as a case study to illustrate benefits and limitations.     

Towards a formal definition of methods

The absence of a formal specification of methods permits application engineers to interpret method concepts in any way they want. Further, different CASE tool designers can implement the same method concepts in different ways. The approach to formal method specification described here is in three levels: the generic level, the method independent level, and the method level. The generic level provides a model of a method which can be instantiated to yield a method-independent view of methods. This view can, in turn, be instantiated to yield the formal method of interest. The attempt is to represent methods independently of any underlying way-of-working or paradigm, remove the process/product dichtomy by tight coupling of the process and product aspects of methods, and permit extensibility of methods. The formal specification can be used as a basis for building CASE tools, as an output to be produced by a CAME tool, and for defining development processes.     

Case study: Digital's application generator

One approach to software reuse is to generate an application from a domain specific specification. The specification describes the application's problem or task, and it might take diverse forms, such as an interactive dialogue or a formal language. DECAdmire, an application generator provided by Digital Equipment, is an interactive application development tool that provides code generation for interactive management information-systems that involve relational database updates. DECAdmire provides 80 to 95 percent code reuse     

XML-based Specification of Diagram Editors

This paper describes a graphical specification tool for Dia Gen, a diagram editor generator based on hypergraph grammars and hypergraph transformation. The specification tool greatly simplifies the process of specifying and generating diagram editors. It uses an XML-based specification language, and it is an extension of a generic XML editor which offers syntax-directed editing based on the DTD, i.e, syntax specification, of the underlying XML-based language.     

Development of verification and conformance testing tools for a railway signaling communication protocol

Verification and conformance testing for protocol specification, the key part of the protocol development process, are complementary technologies employed to increase confidence that a system will function as stated in its specifications. In this paper, we verify the safety and liveness of the protocol specified for the Labeled Transition System (LTS) by using a model-checking method and implementing the testing tool, which experimentally demonstrates the presence of deadlock and reachability from the initial state to a random state. Implementing the testing tool can use modal mu-calculus to assess whether protocol model properties, presented by modal logic, meet protocol specifications. In addition, we propose a conformance testing tool to check correct implementation of sequences that have been derived by the UIO method from the specification of the protocol being verified. This generating tool uses the C++ language in the Microsoft Windows NT environment.     

Experiences with software specification and verification using LP,the Larch proof assistant

We sketch a method for deduction-oriented software and system development. The method incorporates formal machine-supported specification and verification as activities in software and systems development. We describe experiences in applying this method. These experiences have been gained by using the LP, the Larch proof assistant, as a tool for a number of small and medium size case studies for the formal development of software and systems. LP is used for the verification of the development steps. These case studies include

? quicksort

? the majority vote problem

? code generation by a compiler and its correctness

? an interactive queue and its refinement into a network.

The developments range over levels of requirement specifications, designs and abstract implementations. The main issues are questions of a development method and how to make good use of a formal tool like LP in a goal-directed way within the development. We further discuss the value of advanced specification techniques, most of which are deliberately not supported by LP and its notation, and their significance in development, Furthermore, we discuss issues of enhancement of a support system like LP and the value and the practicability of using formal techniques such as specification and verification in the development process in practice.     

Detection of metamorphic and virtualization-based malware using algebraic specification

We present an overview of the latest developments in the detection of metamorphic and virtualization-based malware using an algebraic specification of the Intel 64 assembly programming language. After giving an overview of related work, we describe the development of a specification of a subset of the Intel 64 instruction set in Maude, an advanced formal algebraic specification tool. We develop the technique of metamorphic malware detection based on equivalence-in-context so that it is applicable to imperative programming languages in general, and we give two detailed examples of how this might be used in a practical setting to detect metamorphic malware. We discuss the application of these techniques within anti-virus software, and give a proof-of-concept system for defeating detection counter-measures used by virtualization-based malware, which is based on our Maude specification of Intel 64. Finally, we compare formal and informal approaches to malware detection, and give some directions for future research.