嵌入式实时软件模型开发环境研究

为保证嵌入式实时软件的功能安全和实时性,基于模型驱动开发方法,研究了嵌入式实时软件的模型开发环境的体系结构,设计了一个嵌入式实时软件模型开发环境的原型MDE环境.其中应用任务模型使用两层模型机制:上层模型用于建模应用任务的功能行为与性能特征并支持形式化功能安全验证和实时性分析,下层模型用于模型测试和自动生成支持嵌入式实时操作系统API接口和驱动函数接口的应用任务源代码.通过工具集成实现了建模、分析验证、代码生成和测试等嵌入式实时软件的完整模型化开发过程,为将来进一步完善和改进嵌入式实时软件模型开发环境的构建技术提供了应用验证.     

模型组合技术研究与实现*

近年来模型组合技术的研究与应用越来越广泛,但针对各种文件格式的模型资源进行统一管理、组合与服务调度的模型库系统尚未发现。根据多种文件格式的模型资源的特点,设计并实现了一个通用模型组合工具,利用XML语言描述组合模型的控制流程和参数传递流程,实现了对多种文件格式的模型资源的可视化组合和服务调度。     

基于服务架构的OpenFOAM求解客户端设计

针对OpenFOAM解算软件缺乏GUI功能用户交互体验性差问题，研究设计了一个OpenFOAM求解客户端软件。设计了基于服务的“云+端”计算架构，设计开发了一个OpenFOAM求解器服务，GUI客户端远程调用访问求解器服务，并集成可视化服务实现了数据可视化分析功能，实现了云端协同的求解计算功能；研究设计了基于界面模板的动态GUI界面生成方法，实现了客户端软件界面用户自定义配置功能。该软件支持基于服务的功能扩展集成，支持用户界面自定义、求解器用户设置界面自定义功能，用户界面友好，可扩展性强。通过实际的算例进行解算，验证表明了客户端软件能够通过远程调用云端求解服务、可视化服务实现完整的求解计算流程。     

基于本体的服务网络平台及其构建方法

在基于语义关系的大规模Web服务组织结构：服务网络模型的基础上,构建了服务网络系统平台。提供了对Web服务和服务关系的描述,使得Web服务的自动化处理成为可能。设计了可动态优化的服务网络系统内核,实现了服务网络的数据存储、网络优化和关系挖掘;设计和实现了系统创建维护工具、系统服务增长工具、可视化工具等一整套核心工具;给出了服务关系构成建的基本方法和流程,完善了网络结构。最后,一些基于服务网络的应用证明了该系统的有效性和广泛适用性。     

基于WS-BPEL的服务组合流程建模工具的设计与实现

详细介绍了基于BPEL语言的可视化Web服务组合流程建模工具的体系结构;引入节点和弧的概念实现可视化流程编辑器;采用图形化方法和流程图到WS-BPEL元素的映射技术,实现了Web服务组合流程模型的建立、编辑和配置等功能,简化了抽象流程到可执行流程的转化;提出了基于Web服务QOS约束的服务查询、QOS本体表示和QOS筛选方案,使得符合用户需求的Web服务能够被动态灵活地绑定到业务流程中.     

基于深度学习的可视化仪表板生成技术研究

仪表板是支持制造企业开展数据可视化分析和经营决策的重要手段。为解决可视化仪表板设计与实现过程中用户对专业知识依赖性强及流程迭代繁杂的问题，提出了一种基于深度学习技术YOLOv5s算法的可视化仪表板自动识别与生成方法。首先，基于YOLOv5s算法对仪表板图像及手绘草图中包含的可视化图表组件进行检测，并针对在检测过程中出现的手绘草图中不规则线条对识别图表的干扰及误检等问题，引入CA注意力机制来增强模型对重要特征的关注及目标精确定位能力，从而提高模型的识别精度；其次，将图表检测模型部署在Web中，服务器根据模型检测结果调用封装好的可视化图表组件代码，生成多组件组合的初始仪表板；最后，基于此Web设计，开发了一款数据可视化仪表板构建平台，为用户提供可修改配置仪表板样式及数据的详细选项，以方便用户快速构建完整的仪表板。通过收集Tableau, Power BI等可视化工具产生的仪表板图像及企业应用过程中手绘仪表板草图形成数据集，基于该数据集进行实验验证，改进的模型识别精度比原YOLOv5s模型提升了2.1%,mAP为98.4%,并通过系统部署应用验证了图表识别方法及开发的平台可有效识别及生成相应...     

基于时间自动机的嵌入式系统调度分析工具

为验证嵌入式实时系统开发过程中任务集的可调度性,设计并实现一种嵌入式系统调度分析工具。提出通用任务模型,建立任务与事件到达自动机和任务状态自动机的状态关系映射,利用基于模型检测的时间自动机可达性方法判定系统的可调度性。仿真实例结果表明,该工具的分析准确性较高。     

可视化网格工作流过程定义工具的设计与实现

网格服务的出现对工作流建模提出了新的要求,现有工作流模型的构建一般是通过工作流建模语言对流程进行描述来完成,鉴于这种方式较为复杂且容易出错,故根据MVC模式设计并实现了基于网格业务流程执行语言GBPEL的可视化过程定义工具GWF_PDTool,使用户可以通过简捷地拖拉流程活动图标来组建网格工作流程,并同步生成以GBPEL描述的流程文档,实时检验流程的正确性.     

用户界面设计中任务建模方法研究

基于模型的用户界面设计方法是通过用户界面模型开发用户界面的新方法。任务模型作为其中一个主要模型,刻画的是用户与界面交互过程中动态行为方面的信息。详细介绍了HTA,UAN,GOMS,CTT,Wisdom五种常用的任务模型建模方法,分析了各方法的优缺点及适用环境,并对任务建模方法的未来发展方向进行了展望。     

基于GMF的WS-Security安全策略配置工具研究与实现

现有的基于WS-Security(Web服务安全)的安全工具在技术层面上提供了Web服务安全的基础设施,但是这些工具需要用户拥有丰富的安全知识,并且没有提供展现业务上下文的手段,给业务用户对安全设施的使用带来了困难。基于MDA的思想设计了一个与业务流程结合的安全策略模型。在这个安全模型中,将描述业务流程的应用模型和描述协同应用安全信息的安全模型结合起来,并基于安全模型使用GMF框架实现了相应的配置工具。业务人员可以在可视化的业务流程之上,基于预定义的安全策略模型,配置Web服务安全策略。工具自动将配置的安全策略转换为WS-Security Policy规范文档。     

Design, construction, and application of a generic visual languagegeneration environment

The implementation of visual programming languages (VPLs) and their supporting environments is time-consuming and tedious. To ease the task, researchers have developed some high-level tools to reduce the development effort. None of these tools, however, can be easily used to create a complete visual language in a seamless way as the lex/yacc tools do for textual language constructions. This paper presents the design, construction and application of a generic visual language generation environment, called VisPro. The VisPro design model improves the conventional model-view-controller framework in that its functional modules are decoupled to allow independent development and integration. The VisPro environment consists of a set of visual programming tools. Using VisPro, the process of VPL construction can be divided into two steps: lexicon definition and grammar specification. The former step defines visual objects and a visual editor, and the latter step provides language grammars with graph rewriting rules. The compiler for the VPL is automatically created according to the grammar specification. A target VPL is generated as a programming environment which contains the compiler and the visual editor. The paper demonstrates how VisPro is used by building a simple visual language and a more complex visual modeling language for distributed programming     

Managing the exchange of engineering product data to support through life ship design

An approach for managing the exchange of engineering product data between geographically distributed designers and analysts using a heterogeneous tool set for the through-life design of a ship is described. The approach was developed within a pan-European maritime project called VRShips-ROPAX 2000 that demonstrated how information technology could be integrated into the design process. This paper describes the development of a common model containing neutral ship product data through a bottom-up consideration of the requirements of the tools to be integrated, as well as a top-down consideration of the data requirements for through life design. This common model was supported within an Integrated Design Environment (IDE) that co-ordinated design activity distributed across Europe. The IDE ensured that the users were provided with the right data in the right form at the right time to do the right task, i.e., that the design activity was timely and appropriate. The strengths and weaknesses of the approach are highlighted.     

Can the case for CASE technology be advanced by Process Improvement?

Findings of a case study that focused on understanding how software development proceeded in a small Information Systems Department (ISD) located within a major public sector service are presented. The observations collected relate to a period prior to, during and after the introduction of a CASE (Computer Aided Software Engineering) tool. They are based on a combination of minutes from quality circle meetings, interviews and regular on-site observations by the first author. The study used a framework loosely based on SEI's CMM model to characterize the state of practice before and after the introduction of the tool and to assess process improvement.Prior to the introduction of the first CASE tool a typical ISD software development task was a standalone single reporting application. The software development process model consisted simply of requirements acquisition and program development. Both these activities for a particular application were carried out by an individual developer within a few months. The former activity involved the client/user, with the level of participation dependent on the developer. Similarly, program development varied from one developer to another, with most effort being expended on coding and testing. Not surprisingly, maintenance was locked to the original developer.A decision that ISD should develop larger and more complex applications triggered the purchase of a CASE tool. Typically, the larger applications would be developed by a team of about five people over a period of twelve or more months. The introduction of CASE tools, first Case Designer 5.1 then Designer 2000, had a marked effect on the working practices of ISD. Specifically two more stages were introduced into the development activity: designing via an entity-attribute relationship model and validation via rapid prototyping; and greater attention was paid to the management of testing and fault reporting.The paper explores whether the benefits accrued by ISD can be attributed to the CASE tool, the changes in work practices, or a combination of both.     

Experiences developing architectures for realizing thin‐client diagram editing tools

Diagram‐centric applications such as software design tools, project planning tools and business process modelling tools are usually ‘thick‐client’ applications running as stand‐alone desktop applications. There are several advantages to providing such design tools as Web‐based or even PDA‐ and mobile‐phone‐based applications. These include ease of access and upgrade, provision of collaborative work support and Web‐based integration with other applications. However, building such thin‐client diagram editing tools is very challenging. We have developed several thin‐client diagram editing applications realized as a set of plug‐in extensions to a meta‐tool for visual design environment development. In this paper, we discuss key user interaction and software architecture issues, illustrate examples of interacting with our thin‐client diagram editing tools, describe our design and implementation approaches, and present the results of several different evaluations of the resultant applications. Our experiences will be useful for those interested in developing their own thin‐client diagram editing architectures and applications. Copyright © 2007 John Wiley & Sons, Ltd.     

基于统一建模语言的软件开发实例

统一建模语言(UML)是功能强大的可视化建模语言, 针对UML在建模方面的优势, 以汉中茶叶客户投诉管理系统为例, 从系统的功能分析、系统设计到系统实施, 重点描述了基于UML的软件系统开发建模过程, 并通过建模工具Power Designer 15, 构建了系统的需求模型、静态模型和动态模型.     

CTTE: support for developing and analyzing task models for interactive system design

While task modeling and task-based design are entering into current practice in the design of interactive software applications, there is still a lack of tools supporting the development and analysis of task models. Such tools should provide developers with ways to represent tasks, including their attributes and objects and their temporal and semantic relationships, to easily create, analyze, and modify such representations and to simulate their dynamic behavior. In this paper, we present a tool, CTTE, that provides thorough support for developing and analyzing task models of cooperative applications, which can then be used to improve the design and evaluation of interactive software applications. We discuss how we have designed this environment and report on trials of its use.     

Design and evaluation of the ModelHealth toolchain for continuity of care web services

Motivation: Systems interoperability is a key challenge in providing continuity of care to all patients. The challenge is addressed with information standards and new approaches to systems integration based on service-oriented architectures. Model-driven development promise utilities that are suitable for software service development in the healthcare domain, but development tools are still immature and their industry uptake is low. The knowledge about how model-driven development tools can become more useful to the healthcare software developers should be strengthened. Approach: This paper presents the ModelHealth toolchain that was created in four design/assess cycles, involving 28 students and 41 professional developers in the period 2007–2010. The toolchain provides design assistance for creating software services based on concepts from the CEN-13940 standard for continuity of care, which facilitates development of interoperable software services. Results: The CEN-13940 standard was successfully incorporated into the ModelHealth Toolchain assisting developers in creating software service design models that adhered to the standard. The developers expressed that improved understanding of the target system, documentation generation, and artifact traceability were essential utilities of the model-driven approach. Conclusion: The paper concludes healthcare domain knowledge can be successfully incorporated in a model-driven development toolchain, providing valuable input to the healthcare software service design process. A set of recommendations on how to incorporate domain specific concepts into model-driven development tools is provided. To our knowledge, no other scientific publications have reported from healthcare specific model-driven tool design and evaluations. Our recommendations extend and nuance existing knowledge on model-driven development tooling in general.     

A Design Process for a Customer Journey Map: A Case Study on Mobile Services

A customer journey map (CJM) is a widely used tool to represent user experience with a service. Although numerous companies have used this tool to improve existing services or to develop new services, the maps are neither consistent nor mutually compatible because no clear design process for a CJM has been presented. This study aimed to develop a design process and rule sets for a CJM based on a human factors approach. The 10‐step process and the rule sets were built on case studies of 25 categories of mobile services. Large‐scale case studies were conducted with mobile service providers and combined with the result of a user diary method that collected users’ daily activities and the difficulties that the user perceived when performing a task. We suggested various methods for using the CJM to generate new service opportunities. The proposed design process and the way for opportunity discovery can help service designers to develop unified CJMs and to identify innovative service ideas.     

Evaluating availability of functional products through simulation

A functional product is an integrated package consisting of hardware, software and a service support system that provides a customer with a certain function and is sold under a performance-based contract that includes a functional availability guarantee. For the availability performance, prediction, optimisation and management of risk are therefore important concerns during product development. This paper describes a software tool that can generate an integrated model of a functional product from its design details and analyse it through simulation to provide availability performance information. The model’s application to the analysis of a real industrial system is demonstrated. Such tools are important for the development and widespread adoption of functional products. The resulting analysis gave an indication of a suitable guaranteed functional availability level for the product and could be used to compare the performance of different design options.     

一个MDA支撑工具的设计与实现

MDA是OMG提出的用于解决中间件集成问题的软件开发方法。MDA开发方法以系统模型作为软件开发的主线。在这样的开发过程中,强有力的模型转换支撑工具是MDA思想能够得到广泛应用的关键。而从平台无关模型PIM到平台相关模型PSM的转换工具尤其重要。描述了一个从PIM自动转换到PSM的工具的设计思想。工具使用EDOC profile的一个子集作为PIM的描述方法,使用J2EE作为目标平台。基于一组从PIM到J2EE平台上软件模型的转换规则,工具实现了从PIM到J2EE平台上的PSM的自动转换。