Teaching chemical engineering using Jupyter notebook: Problem generators and lecturing tools

The primary objective of this study is to develop teaching materials for chemical engineering students (or students pursuing other related B.Sc./M.Sc. degrees) that encourage self-learning to facilitate understanding and the development of problem-solving skills. Tools are oriented to support the teaching of “Introduction to Chemical Engineering” courses to 1^st year B.Sc. students in Chemical Engineering, 2^nd year B.Sc. students in Chemistry, and 3^rd year B.Sc. students in Biochemistry at the Universidad Complutense de Madrid (UCM). Problem generators of standard exercises, as an additional complement to the exercises that are used in the lectures, seminars, and assignments to facilitate the learning of the students, have been developed. These generators provide exercises to students with “unlimited” initial values (with certain restrictions). The software that was used to develop these materials was Jupyter Notebook, which runs under the Python 3.6 language. The problem generators can be classified into fixed problem generators, case-based generators, and random problem generators. Additionally, lecturing tools have been developed to support teaching using live/interactive examples. These examples can learning understanding of various topics of the courses.     

Management of automotive software updates

Software updates are an important topic for increasingly software dependent and automated automotive systems. Besides ongoing technical developments, there are also regulatory requirements in development for such systems. We present here an overview of the automotive domain and the particular requirements on update systems, identify potentially suitable update frameworks and evaluate them based on automotive requirements. A focus is on a holistic view of requirements, considering safety, security, and availability.     

基于软件校准的短波发射机功率控制系统设计

短波发射机功率稳定一直是通信领域致力改善的重点问题,短波发射机功率不稳定会直接影响无线电通信质量,造成通信失真、表达不清晰等问题。针对上述问题,基于软件校准设计短波发射机功率控制系统。该系统借鉴MVC设计模式搭建系统数据库层、业务逻辑层、控制层以及界面显示层基础框架；将功率计与短波发射机相连,实时采集工作状态下的短波发射机功率数据,通过信号处理器实施处理后并存储,借鉴传输元件,将数据发送到控制器,通过控制器校准短波发射机功率与预期之间的偏差,以偏差量为输入,利用改进PID运算得出控制量,生成控制命令,通过输入输出信号接口板输出命令,控制驱动装置调节短波发射机运行参数,实现功率控制。结果表明：与 控制系统、自动调谐系统应用相比较,在所设计系统应用控制下,100s内短波发射机的功率变化曲线与预期曲线之间的拟合优度指数更大,更接近1,优于对比系统,说明相比于对比系统。本系统控制表现更好,更能维持短波发射机功率稳定,达到了研究目标。     

‘I am not a number’: Conceptualising identity in digital surveillance

Surveillance, now a commonplace phenomenon in everyday life, has been explored from various disciplines over three decades. Today's surveillance practices depend primarily upon many software technologies that collect, store and process personal data for the purposes of influence, management, protection or detection. The identification and categorisation of data have thus emerged as the technical signature of surveillance. An individual has many identities belonging to different contexts of his/her life, but in this paper, we explore the relationship between surveillance and identity in virtual contexts only. We argue that an understanding of identity purely as data is fundamental to understanding surveillance. We propose abstract general definitions of surveillance and identity that together create a conceptual framework, capturing key features common to many disparate surveillance situations. Our work concludes that the essence of surveillance is that of a surveillance context, which is precisely and solely defined by the availability of data about the behaviour and identity of its entities. The data that distinguishes the entities of the context we call identifiers; we explore the creation, provenance, comparison and transformation of identifiers. Abstractly, surveillance is a process that tests for properties of data, and sorts identifiers into categories.     

基于哈希链的软件定义网络路径安全

针对软件定义网络中，控制器无法保证下发的网络策略能够在转发设备上得到正确执行的安全问题，提出一种新的转发路径监控安全方案。首先以控制器的全局视图能力为基础，设计了基于OpenFlow协议的路径凭据交互处理机制；然后采用哈希链和消息验证码作为生成和处理转发路径凭据信息的关键技术；最后在此基础上，对Ryu控制器和Open vSwitch开源交换机进行深度优化，添加相应处理流程，建立轻量级的路径安全机制。测试结果表明，该机制能够有效保证数据转发路径安全，吞吐量消耗比SDN数据层可信转发方案（SDNsec）降低20%以上，更适用于路径复杂的网络环境，但时延和CPU使用率的浮动超过15%，有待进一步优化。     

A systematic review on the relationship between user involvement and system success

ContextFor more than four decades it has been intuitively accepted that user involvement (UI) during system development lifecycle leads to system success. However when the researchers have evaluated the user involvement and system success (UI-SS) relationship empirically, the results were not always positive.ObjectiveOur objective was to explore the UI-SS relationship by synthesizing the results of all the studies that have empirically investigated this complex phenomenon.MethodWe performed a Systematic Literature Review (SLR) following the steps provided in the guidelines of Evidence Based Software Engineering. From the resulting studies we extracted data to answer our 9 research questions related to the UI-SS relationship, identification of users, perspectives of UI, benefits, problems and challenges of UI, degree and level of UI, relevance of stages of software development lifecycle (SDLC) and the research method employed on the UI-SS relationship.ResultsOur systematic review resulted in selecting 87 empirical studies published during the period 1980–2012. Among 87 studies reviewed, 52 reported that UI positively contributes to system success, 12 suggested a negative contribution and 23 were uncertain. The UI-SS relationship is neither direct nor binary, and there are various confounding factors that play their role. The identification of users, their degree/level of involvement, stage of SDLC for UI, and choice of research method have been claimed to have impact on the UI-SS relationship. However, there is not sufficient empirical evidence available to support these claims.ConclusionOur results have revealed that UI does contribute positively to system success. But it is a double edged sword and if not managed carefully it may cause more problems than benefits. Based on the analysis of 87 studies, we were able to identify factors for effective management of UI alluding to the causes for inconsistency in the results of published literature.     

A systematic literature review on the usage of eye-tracking in software engineering

ContextEye-tracking is a mean to collect evidence regarding some participants’ cognitive processes. Eye-trackers monitor participants’ visual attention by collecting eye-movement data. These data are useful to get insights into participants’ cognitive processes during reasoning tasks.ObjectiveThe Evidence-based Software Engineering (EBSE) paradigm has been proposed in 2004 and, since then, has been used to provide detailed insights regarding different topics in software engineering research and practice. Systematic Literature Reviews (SLR) are also useful in the context of EBSE by bringing together all existing evidence of research and results about a particular topic. This SLR evaluates the current state of the art of using eye-trackers in software engineering and provides evidence on the uses and contributions of eye-trackers to empirical studies in software engineering.MethodWe perform a SLR covering eye-tracking studies in software engineering published from 1990 up to the end of 2014. To search all recognised resources, instead of applying manual search, we perform an extensive automated search using Engineering Village. We identify 36 relevant publications, including nine journal papers, two workshop papers, and 25 conference papers.ResultsThe software engineering community started using eye-trackers in the 1990s and they have become increasingly recognised as useful tools to conduct empirical studies from 2006. We observe that researchers use eye-trackers to study model comprehension, code comprehension, debugging, collaborative interaction, and traceability. Moreover, we find that studies use different metrics based on eye-movement data to obtain quantitative measures. We also report the limitations of current eye-tracking technology, which threaten the validity of previous studies, along with suggestions to mitigate these limitations.ConclusionHowever, not withstanding these limitations and threats, we conclude that the advent of new eye-trackers makes the use of these tools easier and less obtrusive and that the software engineering community could benefit more from this technology.     

Investigating software testing and maintenance reports: Case study

ContextAlthough many papers have been published on software development and defect prediction techniques, problem reports in real projects quite often differ from those described in the literature. Hence, there is still a need for deeper exploration of case studies from industry.ObjectiveThe aim of this study is to present the impact of fine-grained problem reports on improving evaluation of testing and maintenance processes. It is targeted at projects involving several releases and complex schemes of problem handling. This is based on our experience gained while monitoring several commercial projects.MethodExtracting certain features from detailed problem reports, we derive various measures and present analysis models which characterize and visualize the effectiveness of testing and problem resolution processes. The considered reports describe types of problems (e.g. defects), their locations in project versions and software modules, ways of their resolution, etc. The performed analysis is related to eleven projects developed in the same company. This study is an exploratory research with some explanatory features. Moreover, having identified some drawbacks, we present extensions of problem reports and their analysis which have been verified in another industrial case study project.ResultsFine-grained (accurate) problem handling reports provide a wider scope of possible measures to assess the relevant development processes. This is helpful in controlling single projects (local perspective) as well as in managing these processes in the whole company (global perspective).ConclusionDetailed problem handling reports extend the space and quality of statistical analysis, they provide significant enhancement in evaluation and refinement of software development processes as well as in reliability prediction.     

On the probability distribution of faults in complex software systems

ContextThere are several empirical principles related to the distribution of faults in a software system (e.g. the Pareto principle) widely applied in practice and thoroughly studied in the software engineering research providing evidence in their favor. However, the knowledge of the underlying probability distribution of faults, that would enable a systematic approach and refinement of these principles, is still quite limited.ObjectiveIn this paper we study the probability distribution of faults detected during verification in four consecutive releases of a large-scale complex software system for the telecommunication exchanges. This is the first such study analyzing closed software system, replicating two previous studies for open source software.MethodWe take into consideration the Weibull, lognormal, double Pareto, Pareto, and Yule–Simon probability distributions, and investigate how well these distributions fit our empirical fault data using the non-linear regression.ResultsThe results indicate that the double Pareto distribution is the most likely choice for the underlying probability distribution. This is not consistent with the previous studies on open source software.ConclusionThe study shows that understanding the probability distribution of faults in complex software systems is more complicated than previously thought. Comparison with previous studies shows that the fault distribution strongly depends on the environment, and only further replications would make it possible to build up a general theory for a given context.     

Blockchain verification and validation: Techniques,challenges, and research directions

As blockchain technology is gaining popularity in industry and society, solutions for Verification and Validation (V&V) of blockchain-based software applications (BC-Apps) have started gaining equal attention. To ensure that BC-Apps are properly developed before deployment, it is paramount to apply systematic V&V to verify their functional and non-functional requirements. While existing research aims at addressing the challenges of engineering BC-Apps by providing testing techniques and tools, blockchain-based software development is still an emerging research discipline, and therefore, best practices and tools for the V&V of BC-Apps are not yet sufficiently developed. In this paper, we provide a comprehensive survey on V&V solutions for BC-Apps. Specifically, using a layered approach, we synthesize V&V tools and techniques addressing different components at various layers of the BC-App stack, as well as across the whole stack. Next, we provide a discussion on the challenges associated with BC-App V&V, and summarize a set of future research directions based on the challenges and gaps identified in existing research work. Our study aims to highlight the importance of BC-App V&V and pave the way for a disciplined, testable, and verifiable BC development.