An Embedded Software Modeling and Process by Using Aspect-Oriented Approach

In recent years, mobile devices have become widespread and refined, and they have offered increased convenience in human life. For these reasons, a variety of embedded systems have been designed. Therefore, improving methods for developing of embedded software systematically has become an important issue. Platform-based design is one example of an embedded-system design method that can reduce the design cost via improving a design’s abstraction level. However, platform-based design lacks precise definitions for platforms and design processes. This paper provides an approach that combines the aspects and platform-based design methods for developing embedded software. The approach is built on platform-based design methodology and uses the separating of concerns (SoC) concept to define the aspects and to reduce the crosscutting concerns in embedded system modeling. For aspect issues, we use the extended UML notation with aspects to describe both the static structure and the dynamic structure of the embedded system. We used an example of a digital photo frame system to demonstrate our approach.

A Metamodel-Driven Business Process Modeling Methodology and Its Integrated Environment for Reusing Business Processes

Reusing business process models and best practices can improve the productivity, quality and agility in the early development phases of enterprise software systems. To help developers reuse the business process models and best practices, we propose a methodology and an integrated environment for business process modeling driven by the metamodel. Furthermore, we propose a process-template design method to unify the granularity and separate the commonality and variability of business processes so that business process models can be reused across different enterprise software systems. The proposed methodology enables to create reuse-oriented business process templates before the business process modeling. To support the proposed methodology, we developed an integrated environment for creating, reusing and verifying the business process models. As the key techniques, we describe the methodology and its integrated environment, including a metamodel and notations. We applied the methodology and integrated environment to an actual enterprise software development project, and evaluated that the productivity of business process modeling is improved by at least 46%. As the conclusion, this paper contributes to prove the effectiveness of the meta-model driven business process modeling methodology for the reuse of business process models.

Intelligent Agent Based Mapping of Software Requirement Specification to Design Model

Automatically mapping a requirement specification to design model in Software Engineering is an open complex problem. Existing methods use a complex manual process that use the knowledge from the requirement specification/modeling and the design, and try to find a good match between them. The key task done by designers is to convert a natural language based requirement specification (or corresponding UML based representation) into a predominantly computer language based design model—thus the process is very complex as there is a very large gap between our natural language and computer language. Moreover, this is not just a simple language conversion, but rather a complex knowledge conversion that can lead to meaningful design implementation. In this paper, we describe an automated method to map Requirement Model to Design Model and thus automate/partially automate the Structured Design (SD) process. We believe, this is the first logical step in mapping a more complex requirement specification to design model. We call it IRTDM (Intelligent Agent based requirement model to design model mapping). The main theme of IRTDM is to use some AI (Artificial Intelligence) based algorithms, semantic representation using Ontology or Predicate Logic, design structures using some well known design framework and Machine Learning algorithms for learning over time. Semantics help convert natural language based requirement specification (and associated UML representation) into high level design model followed by mapping to design structures. AI method can also be used to convert high level design structures into lower level design which then can be refined further by some manual and/or semi automated process. We emphasize that automation is one of the key ways to minimize the software cost, and is very important for all, especially, for the “Design for the Bottom 90% People” or BOP (Base of the Pyramid People).

Feature Modeling and Variability Modeling Syntactic Notation Comparison and Mapping

Feature Model (FM) became an important role in Software Product Line Engineering (SPLE) field. Many approaches have been introduced since the original FM came up with Feature Oriented Domain Analysis (FODA) introduced by Kang in 1990. The main purpose of FM is used for commonality and variability analysis in domain engineering, to optimize the reusable aspect of software features or components. Cardinality-based Feature Model (CBFM) is one extension of original FM, which integrates several notations of other extensions. In CBFM, feature model defined as hierarchy of feature, with each of feature has a cardinality. The other notation to express variability within SPLE is Orthogonal Variability Model (OVM). At the other hand, OMG as standard organization makes an effort to build standard generic language to express the commonality and variability in SPL field, by initiate Common Variability Language (CVL). This paper reports the comparison and mapping of FODA, CBFM and OVM to CVL where need to be explored first to define meta model mapping of these several approaches. Furthermore, the comparison and mapping of those approaches are discussed in term of R3ST (read as “REST”) software feature model as the case study.

Assessment and Prediction of Software Reliability in Mobile Applications

Software reliability is an important quality attribute, and software reliability models are frequently used to measure and predict software maturity. The nature of mobile environments differs from that of PC and server environments due to many factors, such as the network, energy, battery, and compatibility. Evaluating and predicting mobile application reliability are real challenges because of the diversity of the mobile environments in which the applications are used, and the lack of publicly available defect data. In addition, bug reports are optionally submitted by end-users. In this paper, we propose assessing and predicting the reliability of a mobile application using known software reliability growth models (SRGMs). Four software reliability models are used to evaluate the reliability of an open-source mobile application through analyzing bug reports. Our experiment proves it is possible to use SRGMs with defect data acquired from bug reports to assess and predict the software reliability in mobile applications. The results of our work enable software developers and testers to assess and predict the reliability of mobile software applications.

Learning to Support Derivation of Adaptable Products in Software Product Lines

Software product line engineering is a large scale development paradigm based on mass production. It consists in building a common platform from which a set of products can be derived. Under the constraints of continuous evolution and costs optimization, the derivation process must be able to answer customers’ requirements and provide adequate products in a short time without defects. However, this purpose cannot be achieved if the customer must wait for the change is implemented in the common platform. In this paper, we describe our work which proposes a framework to manage derivation of adaptable products. An adaptable product is obtained by deriving the most similar product from the common platform and changing it to support the new requirements. The aim of the framework is to give quick response to the customers need while the new requirements are being implemented in the common platform. The framework includes tools for processing natural language requirements, computing the similarity between products on the basis of their requirements, and the product adaptation effort measuring.

Knowledge Management of Software Productivity and Development Time

In this paper, we identify a set of factors that may be used to forecast software productivity and software development time. Software productivity was measured in function points per person hours, and software development time was measured in number of elapsed days. Using field data on over 130 field software projects from various industries, we empirically test the impact of team size, integrated computer aided software engineering (ICASE) tools, software development type, software development platform, and programming language type on the software development productivity and development time. Our results indicate that team size, software development type, software development platform, and programming language type significantly impact software development productivity. However, only team size significantly impacts software development time. Our results indicate that effective management of software development teams, and using different management strategies for different software development type environments may improve software development productivity.

角色建模工具RModeler的设计与实现

提倡在对象技术中基于角色识别对象及其协调关系,然后展开到类模型、接口模型、实体模型,同时对角色模型的形式化定义和表示方法进行了系统地研究,并在此基础上设计和实现了基于RML的可视化角色建模工具RModeler。RModeler目前完成了代码实现和测试工作,并在实际开发中使用,运行良好。RModeler支持业务过程中采用RML语言的建模,具备将RML模型转换为UML模型的功能,采用业界标准数据描述格式XMI来传递和共享建模信息。

Transformation of User Interface to Activity Models and Assessing Performance of WA/WS

Quality of Service is an important attribute of a software system. In retrospect, performance assessment based on user interaction with the system has given a better understanding of underlying disciplines of the product. In this paper, we capture user interaction with the prototype/User Interface (UI). An approach for developing activity model from the user interface model is presented using workflows and functional elements. A methodology is proposed to transform UI into activity diagram. The approach is validated by an experimental setup using Amazon service. The performance of Amazon service is assessed using activity based performance prediction methodology, and the simulation results are obtained using SMTQA.

Model-based robustness testing for avionics-embedded software

Robustness testing for safety-critical embedded software is still a challenge in its nascent stages. In this paper, we propose a practical methodology and implement an environment by employing model-based robustness testing for embedded software systems. It is a system-level black-box testing approach in which the fault behaviors of embedded software is triggered with the aid of modelbased fault injection by the support of an executable model-driven hardware-in-loop （HIL） testing environment. The prototype implementation of the robustness testing environment based on the proposed approach is experimentally discussed and illustrated by industrial case studies based on several avionics-embedded software systems. The results show that our proposed and implemented robustness testing method and environment are effective to find more bugs, and reduce burdens of testing engineers to enhance efficiency of testing tasks, especially for testing complex embedded systems.

Integrating behavior analysis into architectural modeling

Architectural modeling and behavior analysis are two important concerns in the software development. They are often implemented separately, and specified by their own supporting notations. Architectural modeling helps to guarantee the system design to satisfy the requirement, and behavior analysis can ensure the interaction correctness. To improve the trustworthiness, methods trying to combine architectural modeling and behavior analysis notations together have been proposed, e.g., establishing a one-way mapping relation. However, the one-way relation cannot ensure updating one notation specifications in accordance with the other one, which results in inconsistency problems. In this paper, we present an approach to integrating behavior analysis into architectural modeling, which establishes the interoperability between architectural modeling notation and behavior analysis notation by a bidirectional mapping. The architecture is specified by the modeling language, architecture analysis and design language （AADL）, and then mapped to behavior analysis notation, Darwin/FSP （finite state process） through the bidirectional transformation. The bidirectional transformarion provides traceability, which makes behavior analysis result provided by a model checker can be traced and reflected back to the original AADL specifications. In this way, the behavior analysis is integrated into architectural modeling. The feasibility of our approach is shown by a control system example.

Automated and controlled patch generation for enhanced fixing of communication software vulnerabilities

Software is a crucial component in the communication systems,and its security is of paramount importance.However,it is susceptible to different types of attacks due to potential vulnerabilities.Meanwhile,significant time and effort is required to fix such vulnerabilities.We propose an automated program repair method based on controlled text generation techniques.Specifically,we utilize a fine-tuned language model for patch generation and introduce a discriminator to evaluate the generation process,selecting results that contribute most to vulnerability fixes.Additionally,we perform static syntax analysis to expedite the patch verification process.The effectiveness of the proposed approach is validated using QuixBugs and Defects4J datasets,demonstrating significant improvements in generating correct patches compared to other existing methods.

基于业务流程的认知图谱

针对目前软件项目开发过程中无法充分利用已有业务资源,进而导致开发效率低、能力弱等问题,通过研究业务资源之间的关联,提出一种基于业务流程的认知图谱。首先,通过正式文档抽取业务知识,提出建立知识层级的方法并修正;其次,通过代码特征挖掘与代码实体相似度判断构建代码网络表示模型;最后,利用实际业务数据进行实验验证,并与向量空间模型(VSM)、多样化排序和深度学习等方法进行对比。最终构建的基于业务流程的认知图谱在代码检索方面优于目前基于文本匹配的方法和深度学习算法,分别在前5准确率(precision@5)、平均精度均值(mAP)、归一化折扣增益值(?-NDCG)这3项指标上高过多样化排序的代码检索方法4.30、0.38和2.74个百分点,有效解决了潜在业务词汇识别、业务认知推理表示等多个问题,提升了代码检索效果与业务资源利用率。

大语言模型驱动的交互式建筑设计新范式——基于Rhino7的概念验证

随着社会对建筑设计质量要求越来越高,建筑设计软件也变得越来越专业和复杂。现在的设计软件不仅学习成本高,而且交互模式复杂。大语言模型(LLM)的最新突破使计算机清晰地理解人类自然语言指令,并准确生成代码语言具有可行性,有望为人与软件的交互范式提供新思路。因此,本文提出了LLM驱动的交互式建筑设计新范式--将设计师通过多次键鼠操作与设计软件交互转变为LLM根据设计师自然语言指令生成并执行API调用脚本的方式;提出了技术路线并验证了其在建筑设计场景落地的可能性。该技术路线包括:①LLM根据用户指令从API库中搜索与任务相关的API;②LLM基于指令和候选API摘要信息编写程序脚本并运行;③LLM根据来自软件环境、用户等反馈改进优化所编写的程序脚本。通过Rhino7设计软件、GPT-4和CodeLlaMa完成多个设计任务,测试当前LLM是否具备执行该技术路线各关键环节的能力。测试结果不仅证明了LLM驱动的交互式设计范式在建筑设计场景已初具落地前景,也为技术落地提供经验和建议。该设计范式的落地可以降低软件的使用门槛和学习成本,提高设计师工作效率;有望在未来的建筑设计软件中发挥重要作用。

软件标识符的自然语言规范性研究

软件源代码的理解是软件协同开发与维护的核心,而源代码中占半数以上的标识符的理解则在软件理解中起到重要作用,传统软件工程主要研究通过命名规范限制标识符的命名过程以构造更易理解和交流的标识符。该文在梳理分析常见编程语言命名规范的基础上,该文提出一种全新的标识符可理解性评价标准。具体而言,首先总结梳理了常见主流编程语言中的命名规范并类比自然语言语素概念,提出基于软件语素的标识符构成过程,即标识符的构成可被视为软件语素的生成、排列和连接过程;在此基础上,该文提出一种结合自然语料库的软件标识符规范性评价方法,用来衡量软件标识符是否易于理解;最后,通过源代码理解数据集和Github平台中开源项目对规范性指标进行了验证性实验,结果表明,该文所提出的规范性分数能够很好衡量软件项目的可理解性。

基于容器技术的水文水动力模型软硬件适配方法

随着国产化软硬件系统的发展和普及,将现行的计算程序适配到国产硬件和操作系统上是科学研究和业务化应用的关键,亟待探索提出专业计算模型的软硬件适配方法。现有关于专业计算模型的软硬件适配方法存在缺乏通用性、硬件依赖性强等问题。鉴于此,系统解析了国产化适配需要解决的关键问题,并对比了现行的软件适配技术,筛选出容器技术作为水文水动力模型的国产适配技术。容器技术可将应用程序打包成独立的运行环境,摆脱对底层架构和操作系统的依赖。以水文水动力模型TELEMAC为例,详细说明了Docker镜像构成原理,并通过Dockerfile文件构建了TELEMAC镜像环境,开展了计算案例的验证。结果表明TELEMAC镜像能够安全运行在以鲲鹏920处理器为核心的openEuler和麒麟V10等国产软硬件平台上,且案例计算结果与标准结果相一致,模型计算效率高,实现了专业科学计算模型的国产化软硬件适配,该研究可为其他软件国产化适配提供参考借鉴。

基于Python的SAP2000向ANSYS模型转化技术及软件开发研究

工程人员常通过对比设计软件与有限元软件的分析结果,以验算和校核结构设计的合理性。然而,由于软件分析内核的差异,设计软件与有限元软件之间的模型信息往往难以直接传递并转化。针对SAP2000结构设计分析软件向ANSYS有限元分析软件的模型转化问题,基于Python语言和APDL参数化设计语言,编译并开发了STAMT V1.0(SAP2000 To ANSYS Model Transformation V1.0)模型转化程序。相比已有转化程序,STAMT程序实现了更多单元类型、材料属性、截面类型、荷载形式的转化,提高了模型转化的通用性。其次,其涵盖了节点坐标系变换、梁单元坐标系变换、梁端自由度释放、创建刚性域等必备功能,进一步满足了模型转化过程中的功能性需求。然后,采用先建立几何模型后生成有限元模型的转化思路,实现了梁单元网格数量的自定义以及板壳荷载向梁的传递,软件操作界面简洁,便于工程人员的使用。最后,通过单层工业厂房和多层框架结构的两个算例分析,得到转化后模型的质量与原模型一致,前5阶周期的平均误差不超过3%,满足精度要求。研究分析验证了STAMT程序可实现SAP2000模型向ANSYS模型的准确、快速转化。

大模型赋能软件供应链开发环节安全研究综述

随着信息技术的快速发展,软件的模块化与产业化趋势愈加显著,导致软件构建的复杂性持续攀升,从而暴露出更多的攻击面,引发了多起软件供应链攻击事件。软件供应链安全不仅具有攻击门槛低、攻击方式多样、攻击隐蔽性强等特点,而且能够影响软件供应链下游安全,显著扩大了攻击范围,成为业界广泛关注的焦点。首先,本文介绍了软件供应链安全的背景,以大模型及软件供应链安全的相关概念为出发点,描述了软件供应链安全防护的发展历程。接着,本文着重探讨了大模型在软件开发环节供应链安全防护中的应用研究,通过系统梳理和分析现有研究成果,分别从顶级源、依赖项、软件包构件及其构建过程四个维度,介绍了大模型赋能软件供应链安全防护技术的研究现状。在此基础上,本文通过对比传统软件供应链安全防护的技术与方法,重点分析了大模型赋能软件供应链开发环节安全方面的优势和机遇。最后,结合对当前研究现状的调研分析,本文总结了大模型在软件供应链安全防护技术中面临的数据集构建、模型训练微调、模型稳定性以及引入新的供应链安全等问题,并据此提出了未来可能的研究方向,以期为推动该领域的持续发展提供有益的参考和启示。

AIGC辅助软件单元测试的研究

介绍了一种基于AIGC的单元测试方法—CodeQwenTest,旨在提高软件测试的效率与质量。通过从开源平台Github收集的高质量的Java焦点方法及其相应的单元测试,构建了一个精心设计的焦点数据集。利用这一数据集,对6种领先的大型语言模型(LLMs)进行了深入的单元测试生成和代码生成任务实验。在这些实验的基础上,选择了CodeQwen1.5-7B-Chat模型,并对其进行了LoRA微调,以进一步提升其在单元测试代码生成任务中的表现。实验结果显示,经过微调的CodeQwenTest在行覆盖率方面显著优于基线模型,并且能够高效地生成断言。这一发现证实了AIGC技术在辅助软件单元测试中的有效性,为软件测试领域带来了新的工具和方法,为软件测试的自动化提供了新的视角。

基于状态图转形式化B模型的安全苛求系统开发方法

形式化方法精确且严格,较多应用于安全苛求系统开发,但目前仍存在学习成本高、使用复杂、重用性低等问题。常用的非形式化状态图模型虽易于使用却缺乏严格验证。针对这些问题,提出一种将状态图SCXML模型转译为形式化B模型的模型转化方法,从而结合状态图的易用性降低在安全苛求软件系统开发过程中使用形式化方法的复杂度。该转译方法分为映射规则、同步语义和程序实现3个部分,以保证自动转译后的模型自身含义与基础语义不变。在平交道口控制系统开发案例分析中,该方法根据图元模型自动生成了对应形式化模型,通过对形式化模型的分析改进系统在功能安全、数据安全、隐藏分支3个方面的非安全因素,并保证从需求至模型的一致性,证明了该方法可降低形式化方法建模难度,提高软件系统的正确性、可靠性与安全性。