Technical debt refers to the adoption of suboptimal solutions in software development in order to prioritize development costs, and is known as one of the barrier factors that hinder software evolution. A new aspect in technical debt is that not all of the debts are regarded as negative effects to be resolved, but rather certain debts are accepted and managed to prevent them from becoming negative effects. This paper provides an overview of technical debt and related technologies, and explains how technical debt relates to previous technologies related to design and code quality.

This paper provides five principles for creating consistent and easily verifiable business descriptions. The five principles are based on concepts in computer science, such as ontology, formal methods, state transition systems, and specification/implementation. The Hiratsuka city's local disaster management division commented that all of the principles were effective and that he would consider incorporating them into future revisions of the disaster management plan.

A program analysis targeting open-source software and student source codes in programming exercises requires parsing the source codes invalid in syntax and manipulating the generated syntax trees. We have built TEBA as a fundamental environment for program analysis, and used the module RewriteTokens which plays a central role in the pattern transformation of token sequences. Even for a simple analysis, because of controlling the backtracking occurring explosively and the poor design of the module, analysis tools have become complicated and had low readability and maintainability. To overcome this problem we experienced, we have implemented a new pattern-matching engine for token sequences and improved the syntax of rewriting rules. As a result, the ease of describing patterns is greatly improved and backtracking is naturally suppressed. This paper shows our new design and discusses the failure of the old design.

Implementing rich functionality while preserving high reliability is desired since embedded software is becoming large and complicated. A federated architecture where multiple processors host different functionality degrades a product's cost, area, and power. Therefore, virtualization is widely studied to host multiple software on one physical processor. Especially, ARM TrustZone realizes dual-OS environment which hosts two different OS and is often leveraged on virtualization for application processors; nevertheless, a few research presented methods for microcontrollers. This paper proposes SafeG-M, a virtualization environment for ARMv8-M architecture with TrustZone extension. The proposed method comes with a minor modification to an existing real-time OS. Evaluation experiments showed that SafeG-M induces a little runtime overhead.

Examining requirements specification documents, users often consult the table of contents (TOC). However, discrepancies between chapter and section titles can hinder the quick identification of key requirements using the TOC alone. This paper proposes a method leveraging automatic summarization technology to calculate and visualize a 'Page Trend', indicating the topic occurrence rate per page. This facilitates swift location and understanding of vital requirements. The effectiveness of the proposed method, as reflected in the Page Trend, is analyzed and compared with results derived from tf-idf values, demonstrating its utility in efficiently navigating requirement specification documents.