Influence of Software Modeling and Design on Domain-Specific Abstract Thinking: Student’s Perspective

Software engineering has been taught at many institutions as individual course for many years. Recently, many higher education institutions offer a BSc degree in Software Engineering. Software engineers are required, especially at the small enterprises, to play many roles, and sometimes simultaneously. Beside the technical and managerial skills, software engineers should have additional intellectual skills such as domain-specific abstract thinking. Therefore, software engineering curriculum should help the students to build and improve their skills to meet the labor market needs. This study aims to explore the perceptions of software engineering students on the influence of learning software modeling and design on their domain-specific abstract thinking. Also, we explore the role of the course project in improving their domain-specific abstract thinking. The study results have shown that, most of the surveyed students believe that learning and practicing modeling and design concepts contribute to their ability to think abstractly on specific domain. However, this finding is influenced by the students’ lack of the comprehension of some modeling and design aspects (e.g., generalization). We believe that, such aspects should be introduced to the students at early levels of software engineering curriculum, which certainly will improve their ability to think abstractly on specific domain.

“SPECIFICATION PLUS TRANSFORMATION TO PROGRAM”：A NEW MODEL OF SOFTWARE DEVELOPMENT

In this paper, a formal specification language and a tool systembased on it are presented. With the tool system, the new model of softwaredevelopment─“specification plus transformation to program” can be im-plemented.

Conversion of Object Oriented System into Software Product Line with Delta Modeling Abstract Behavioral Specification

This article contains a system conversion from object oriented design into Software Product Line (SPL) using delta modeling of Abstract Behavioral Specification (ABS). ABS is a modeling language which targets system with high level of variety and supports SPL development with delta modeling. The case study of this thesis is a digital library system called Library Automation and Digital Archive (LONTAR). Originally, LONTAR only uses SOAP-based web service. With ABS, LONTAR will be converted into SPL and implement another web service called REST. The motivation of this conversion of LONTAR from object oriented into SPL is because it is easier to develop system with ABS than using regular object oriented. Product definition in ABS is relatively easier than creating a new subclass and do customization to make it works well.

An Evaluation of Value-Oriented Review for Software Requirements Specification

A software requirements specification(SRS)is a detailed description of a software system to be developed.This paper proposes and evaluates a lightweight review approach called value-oriented review(VOR)to detect defects in SRS.This approach comprises setting core values based on SRS and detecting the defects disturbing the core values.To evaluate the effectiveness of the proposed approach,we conducted a controlled experiment to investigate whether reviewers could identify and record the core values based on SRS and find defects disturbing the core values.Results of the evaluation with 56 software engineers showed that 91%of the reviewers identified appropriate core values and 82%of the reviewers detected defects based on the identified core values.Furthermore,the average number of defects detected using the proposed approach was slightly smaller than that detected using perspective-based reading(PBR);however,PBR requires defining review scenarios before attempting to detect any defects.The results also demonstrated that the proposed approach helped reviewers detect the omission defects,which are more difficult to detect from SRS than defects because of ambiguity or incorrect requirements.

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).

Decomposition-Based Visual Function Specification and Auto-Generation of Function

On the software module, this paper proposes a visual specification language(VSL). Based on decomposition, the language imitates men's thinking procedure that decomposes aproblem into smaller ones, then independently solves the results of every small problem to get theresult of original problem (decomposition and synthesis). Besides, the language mixes visual withspecification. With computer supporting, we can implement the software module automatically. It willgreatly improve the quality of software and raise the efficiency of software development. Thesimple definition of VSL, the principle of auto-generation, an example and the future research areintroduced.

Computer Aided Call for Tenders: A Tool for Software Bidding

Under a broad comprehension of Software Engineering, it is preferred the term software life cycle instead of just software production. The reason is that cycle starts at software conception and stops when the software is relegated. Given contemporary companies’ market strategies of focusing on their competitive advantages, most of them have externalized their software production to outsourced services. Therefore, the call for software tenders has become a common step in the software life cycle. In this paper, we present a tool which aids non-experts to specify call for software tenders. The motivation was Chile situation of most of rural and semi-urban city halls which do not have engineering teams to build call for software tenders. We describe the problem in terms of lack of competitiveness and empty biddings generated by low quality calls for tenders. As a second step, we show the technical considerations to develop the proposed tool and its features. We include an initial tool perception from a first group of users.

An Integration of UML Sequence Diagram with Formal Specification Methods—A Formal Solution Based on Z

UML Diagrams are considered as a main component in requirement engineering process and these become an industry standard in many organizations. UML diagrams are useful to show an interaction, behavior and structure of the system. Similarly, in requirement engineering, formal specification methods are also being used in crucial systems where precise information is required. It is necessary to integrate System Models with such formal methods to overcome the requirements errors i.e. contradiction, ambiguities, vagueness, incompleteness and mixed values of abstraction. Our objective is to integrate the Formal Specification Language (Z) with UML Sequence diagram, as sequence diagram is an interaction diagram which shows the interaction and proper sequence of components (Methods, procedures etc.) of the system. In this paper, we focus on components of UML Sequence diagram and then implement these components in formal specification language Z. And the results of this research papers are complete integrated components of Sequence diagram with Z schemas, which are verified by using tools and model based testing technique of Formal Specifications. Results can be more improved by integrating remaining components of Sequence and other UML diagrams into Formal Specification Language.

An Approach to Generation of Process-Oriented Requirements Specification

In service-oriented computing, process model may serve as a link to connect users’ requirements with Web Services. In this paper, we propose an approach and related key techniques to generate process-oriented requirements specification from user’s goal. For this purpose, a requirements description language named SORL will be provided to capture users’ requirements. Then, a unified requirements meta-modeling frame RPGS will be used to construct reusable domain assets, which is the basis of generating requirements specifications. Finally, a set of rules are defined to extract process control structures from users’ requirements described with SORL, so that we can convert requirements description into process-oriented requirements specification smoothly.

The Analysis and Proposed Modifications to ISO/IEC 25030—Software Engineering—Software Quality Requirements and Evaluation—Quality Requirements

The quality of the software product is a crucial factor that contributes to its success. Therefore, it is important to specify the right software quality requirements that will establish the basis for desired quality of the final system/software product. There are several known methodologies/ processes that support the specification of the system/software functional requirements starting from the user needs to finally obtain the system requirements that the developers can implement through their development process. System/software quality requirements are interdependent with functional requirements, which means that the system/software quality requirements are meant to be specified in parallel with the latter. The ISO/IEC 25000 [1] SQuaRE series of standards include the standard ISO/IEC 25030—Software engineering—Software Quality Requirements and Evaluation—Quality requirements [2], which has as main goal to help specify software quality requirements. As to date, this standard does not offer clear and concise steps that a software quality engineer could follow in order to specify them. This article presents modifications recommended for ISO/IEC 25030 standard, with, among the others, a new requirements definition process that allows for specifying the system/software quality requirements taking into account the existing published system and software quality model ISO/IEC 25010 [3] as well as all the stake- holders of the project.

油田开发中精细油藏描述成果平台建设研究

精细油藏描述是油田开发最基础的工作之一,历来受到研究者的高度重视。目前精细油藏描述中存在的突出问题主要包括研究成果继承性差、基础资料存储不规范、专业软件需求缺口大、成果应用需加强和成果存储管理不规范等5方面。文章通过精细油藏描述成果平台建设,可以从基础数据的整理准备、专业软件共享和协同研究、成果标准规范化存储管理等方面解决上述问题。精细油藏描述数据管理主要包括项目整体数据信息的统计和分析、项目研究数据的整理和统计、成果平台与其他数据平台的对接和数据调用等。精细油藏描述协同研究过程主要包括专业软件的平台实现和使用、不同专业软件之间中间成果的转换和调用、研究工作的自动化实现和完成。精细油藏描述成果存储和管理主要包括成果上传管理中格式的统一规范、成果存储上传中的质量控制、成果生产应用中的跟踪和更新。

基于光学显微技术的淀粉粒计量方法及其在中药三七中的应用

目的:建立基于光学显微技术的淀粉粒计量方法,并应用于中药三七中淀粉粒的计量。方法:基于光学显微技术的原理,利用淀粉遇碘液变蓝紫色的性质,采用稀碘液对淀粉粒染色;利用Image J软件对染色的淀粉粒进行自动计量。以中药三七粉末样品为测量材料,对稀碘液浓度、样品浓度、显微测量区域进行考查。结果:以0.002 mol/L浓度的稀碘液、15 mg/mL的样品浓度、显微测量9个区域为最佳实验条件,对样品中的淀粉粒面积占比进行测量。此方法的精密度、重复性、重现性的RSD均小于10.5%,表明该方法稳定、可靠。采用该方法测定三七中淀粉粒,结果表明不同规格等级三七中淀粉粒的面积占比差异均有统计学意义,淀粉粒变化规律为:40头>60头>120头>无数头>筋条>绒根≈剪口。结论:本研究建立基于光学显微技术的淀粉粒计量方法,在不同规格等级三七中得到很好的应用,为植物样品中淀粉粒显微计量提供了有效方法。

青年人群慢性非特异性腰背痛的MRI研究

目的:采用SIEMENS Verio 3.0T磁共振成像(MRI)系统及Image J软件测量椎旁肌[多裂肌(multifidus muscle,MF);竖脊肌(erector spinae,ES)]影像学参数,包括横截面积(cross-sectional area,CSA)及脂肪浸润程度(fatty infiltration,FI),评价椎旁肌CSA和FI与慢性非特异性腰背痛的关系,并探讨不同性别人群椎旁肌影像学参数是否有差异。方法:选取2020年6月至2021年5月于我院行腰椎常规MRI T2WI(T2-weighted imaging)序列矢状位、T2WI轴位扫描的慢性非特异性腰背痛青年患者53例设为腰背痛组进行回顾性分析,其中男28例,女25例,所有患者均有明确腰背痛病史,病程超过12周,年龄18~40周岁,且排除其他特异性疾病;并选同时间段内于我院进行MRI相同序列检查的体检青年人员50例设为对照组,其中男25例,女25例。用Image J软件手动勾画L1~S1所有椎间盘中心层面椎旁肌感兴趣区域(ROI),并测量轴位图像椎旁肌CSA和FI。采用t检验比较腰背痛组与对照组之间及不同性别患者椎旁肌CSA、FI的差异。结果:腰背痛组与对照组多节段多裂肌、竖脊肌的CSA比较,差异均无统计学意义;腰背痛组患者多裂肌、竖脊肌FI均大于对照组(P<0.05)。男性组多裂肌、竖脊肌的CSA均大于女性组;多裂肌、竖脊肌FI均小于女性组,差异均有统计学意义(P<0.05)。结论:在青年人群中,慢性非特异性腰背痛患者的多裂肌、竖脊肌脂肪浸润程度较正常人群更加严重;青年男性多裂肌、竖脊肌的CSA大于青年女性、FI低于青年女性。

面向大规模定制的软件开发模式

在领域工程、基于构件的软件工程和并行工程的基础上 ,提出了面向大规模定制的软件开发模式 .该模式以大规模开发标准软件的效益满足用户的个性化需求 .介绍了面向大规模定制的软件开发过程 ,面向大规模定制的软件产品族体系结构 ,以及面向大模型定制软件开发的产品集成过程模型 .

构件化领域框架设计与实现

文中介绍了由东北大学软件中心研究开发的构件化领域框架系统ＮＥＳＣ．它以构件技术、软件体系结构技术和应用软件开发技术为基础，采用了界面、规则和存储的层次化结构，实现了规则控制、时空关系描述、可视化信息表达、构件静态组合、功能动态组合、分布式构件管理等功能．框架体系结构设计通过应用－技术二维划分、功能提取、局部封闭和全局分层等技术实现，可望达到合理规划设计构件，简化依赖关系，提高运行效率，增强构件通用性以及清晰应用系统概念和结构的目的．

软件重用与移植的比较研究

回顾了软件重用和移植方面的研究,并对其进行比较。其目的是对两个领域的共性进行分析,以期对以后的研究工作有所裨益。通过比较,发现软件重用和软件移植在几个方面具有共同的研究领域,包括分类、规格说明和测试、软件确认、软件程序的发行、工程管理等。可移植软件需要按其移植属性进行分类,其目的与软件重用分类不同,但它们可具有相同或类似的机制。同时指出,在软件开发过程中同时对软件移植进行综合考虑并不难,然而困难的是对其进行管理。

软件体系结构开发方法及其应用

简要介绍了软件体系结构开发方法的作用和内容,对领域专用的软件体系结构的意义和开发方法进行了阐述。通过分析机场领域中信息系统的通用功能需求,提出了系统的拓扑结构,采用统一建模语言建立系统模型,并利用设计模式、中间件、构件等技术实现了领域的软件框架,为领域内系统的实现提供了基础,大大提高了系统的开发效率。

嵌入式软件智能合成框架及关键科学问题

程序合成是提高软件开发效率和质量的有效途径,也是计算机科学重要的前沿方向之一。首先,概述了程序合成方法的国内外研究现状及其存在的问题。在此基础上,提出了软件知识产权(intellectual property,IP)的概念和一种基于软件IP的嵌入式软件智能合成开发模式(IP-based embedded software intelligent synthesis,IPESIS)及其框架。最后,阐述了IPESIS需要解决的关键科学问题和主要研究内容。IPESIS通过定义领域需求描述语言,在更高的抽象层次上对目标软件进行刻画,以软件IP为粒度缩小程序搜索空间,采用机器学习等人工智能技术自动合成程序,有望突破现有方法的局限,进而实现嵌入式软件开发从手工编程模式到软件IP研发和基于软件IP的智能合成模式的转变。

关于软件需求中的不一致性管理

复杂软件系统开发的一个关键问题是分析和处理可能存在的不一致的需求描述.这个问题解决得好坏直接影响到需求规格说明的质量,进而影响到最终软件产品的质量.在目前公认的一个不一致需求管理框架的基础上,就需求不一致性管理方面的有代表性的工作,进行了较为系统的分析,以期建立对当前需求工程中,关于不一致的需求管理方法和技术的全面认识.最后,对需求不一致性管理方面的研究进行了展望.

基于限定自然语言需求模板的AADL模型生成方法

随着嵌入式软件系统在汽车、核工业、航空、航天等安全关键领域的广泛应用,其失效将会导致财产的损失、环境的破坏甚至人员的伤亡,使得保障软件安全性成为系统开发过程中的重要部分.传统的安全性分析方法主要应用在软件的需求分析阶段和设计阶段,然而需求与设计之间的鸿沟却一直是软件工程领域的一大难题.正是由于这一鸿沟的存在,使得需求分析阶段的安全性分析结果难以完整而详尽地反映在软件设计中.其根本原因是:当前的软件需求主要通过自然语言描述,存在二义性与模糊性,且难以进行自动化处理.为了解决这一问题,面向构件化嵌入式软件,首先提出了一种半结构化的限定自然语言需求模板用于需求规约,能够有效地降低自然语言需求的二义性与模糊性;然后,为了降低自动化处理的复杂性,采用需求抽象语法图作为中间模型,实现基于限定自然语言需求模板规约的软件需求与AADL模型之间的转换,并在此过程中自动记录两者之间的可追踪关系;最后,基于AADL开源工具OSATE对所提出方法进行了插件实现,并通过航天器导航、制导与控制系统(guidance,navigation and control,简称GNC)进行了实例性验证.