In recent years, the significance of soft skills in software engineering has been increasingly recognized, and their value has been substantiated by a body of literature. While the Software Engineering Body of Knowledge (SWEBOK) provides a well-established framework for technical competencies, Sedelmaier and Landes proposed the Software Engineering Body of Soft Skills (SWEBOS) as a framework for soft skills. SWEBOS shows three top soft skills and the following seven soft skills and presents a hierarchical structure of these skills; however, it does not explicitly define the interrelationships among them. In this study, we propose a model that elucidates the relationships among the three top soft skills—namely, “Problem awareness and solving,” “Collaboration,” and “Personal competencies”—as well as the hierarchical relationships across varying levels of abstraction inherent to the framework.

In the National Curriculum Standard for Kindergartens (revised in 2017), it is stated that kindergartens shall endeavor to nurture qualities and abilities. In order to support teachers in understanding children’s development, this paper proposes tools that use generative AI to assess the degree of relevance (relatedness) between observed behaviors of children described in childcare records and qualities and abilities. Multiple methods based on different prompts were designed to calculate the relatedness score for each sentence, and validity was examined by comparing these scores to those assessed by experts. The results for a “foundation of knowledge and skills” and a “basic abilities of thinking, judgement, and expression, etc.” showed high agreement with expert assessments under several methods. Although the overall agreement rate for the “learning dispositions and humanity, etc. to advance towards learning” was low, all methods showed correlation with expert assessments. Furthermore, three visualization methods were proposed, and received a certain level of positive evaluation by teachers and university students, suggesting that they could serve as helpful references for understanding children and grasping the qualities and abilities.

Project-Based Learning (hereafter, PBL) is adopted as a method of human resource development for software engineers. It is clarified that PBL has high learning effectiveness, especially technical and soft skills acquisition. Bastarrica et al. conducted a survey on learners' initial and final perception about the relative value and difficulty of different dimensions involved in their agile development projects: technical challenge, teamwork, planning and negotiation with the client. Technical challenge is an abstract item. This study aims to clarify learners' skills acquisition in a waterfall model based software engineering project course by conducting a questionnaire survey that is composed of 24 items regarding technical and soft skills before, during and after PBL. The learners recognized they acquired both technical and soft skills at high level at the end of the course. At the survey before the course, scores of soft skills are relatively higher than those of technical skills. As the course progresses, the technical skills where the learners experienced increased. Meetings and/or reviews within team and/or feedback by the teaching staff such as inspection and/or acceptance testing contribute to their learning. While acquisition of soft skills increase through activities of upstream phases, it does not increase through activities of downstream phases.

There have been many practices using software development as a subject for Project-Based Learning (PBL). While PBL for software development has high educational effects, it is difficult for learners to realize many of its educational effects because they overly focus on the activities themselves. Therefore, this paper proposes a support system for visualization of acquired skills in PBL for software development using i-Competency Dictionary. We also describe the data acquisition method for the realization of the system.

This study regards inspections conducted in project-based learning (PBL) for software development as learning feedback. To solve the problem that inspection comments are distributed separately across platforms, which is an obstacle to classification of comments, we develop a script, Comment Gatherer, which aggregates inspection comments between GitHub and Figma. Then, we describe the concept of a support application that enables the automatic classification of inspection comments by machine learning.

In light of the social demand for the training of software engineers and the increasing attention to ProjectBased Learning (PBL), many studies have conducted software development as the subject matter of PBL. However, the educational effectiveness of PBL for software development and its measurement methods are not uniform, as many methods have been reported. This study conducted a systematic literature review of the educational effectiveness of PBL for software development.

In software development, screen scenarios (screen diagrams with intuitive transitions) are often created to design the contents. However, there is a problem that it is difficult to review them in conjunction with version control tools such as GitHub. To solve this problem, we propose a system that converts project files created using the screen design system Figma into text format and automatically uploads them to GitHub.

In recent years, software development is generally done in the form of a team project. Correspondingly, educational institutions have adopted project-based software development exercises (called project-based learning (PBL) of software development in this paper). The PBL of software development can perform various processes in software development, which will be a great experience for students to play an active role in their profession in the future. However, an individual evaluation of students in such a team project is difficult and involves several problems. Therefore, to evaluate students fairly, this research proposes an evaluation method to measure the contributions of individuals in the implementation phase in the PBL of software development. Particularly, it is an evaluation method that applies the function point method, which is known as the size estimation method.

With the spread of highly functional mobile devices, anyone can send messages in a simple manner. On the other hand, risks regarding the leakage of privacy information have increased in number. Software engineers must prevent the leakage of privacy information caused by problems of software systems. The need to tackle privacy issues in the early stage of the software development cycle is called Privacy by Design (PbD). However, a body of knowledge for privacy friendly software development has not been built. Since software developers are not always privacy experts, to provide such a body of knowledge is significant. This paper proposes a metamodel that manages knowledge for development of privacy friendly software and presents a knowledge base that embodies the metamodel by the already known knowledge. We also show an example using the knowledge base to present its usefulness.

To examine requirements and design of a system, using graphical models such as UML is one of the effective ways because it helps developers to understand the system and activities using the system. Usually, more than two types of notations are used to represent a system. At the age of digital transformation, relationships among several different systems should be also discussed and they are of course represented in several different notations. To improve the development and the analysis of several systems using such several notations, traceability among elements in the different notations should be managed, but most techniques focus on the traceability among a single project. In this paper, we present a tool to manage traceability on several different models. The tool is developed as a plugin of an existing graphical modeling tool called Astah. Astah enables us to describe UML models as well as mind maps, data flow diagrams, flow charts and so on. To evaluate our tool, we performed a method to elicit requirements of several different systems together by using the tool. We confirmed our tool was helpful to perform the method, but some additional functions would improve the performance more than now. The additional functions are as follows: tracing links transitively, annotating each link to clarify its type and recording an end of a link while the end is removed from a model.

Due to the widespread proliferation of today's Internet of Things (IoT), a system designer needs the IoT system and software design patterns to assist in designing scalable and replicable solutions. Patterns are encapsulations of reusable common problems and solutions under specific contexts. Many IoT patterns have been published, such as IoT design patterns and IoT architecture patterns to document the successes (and failures) in IoT systems and software development. However, because these patterns are not well classified, their adoption does not live up to their potential. To understand the reasons, we conducted a systematic literature review. From the 32 identified papers, 143 IoT architecture and design patterns were extracted. We analyzed these patterns according to several characteristics and outlined directions for improvements when publishing and adopting IoT patterns. Of the extracted patterns, 57% are non-IoT patterns, suggesting that IoT systems and software are often designed via conventional architecture and design patterns that are not specific to IoT design. Although most IoT design patterns are applicable to any domain, IoT architecture patterns tend to be domain specific, implying that the unique nature of IoT adoption in specific domains appears at the architecture level. As more domains adopt IoT, the number of domain-specific IoT design patterns should increase. In terms of quality attributes, many IoT patterns address compatibility, security, and maintainability.

Huge amount of techniques for creating, maintaining and/or recovering traceability among software development artifacts have been proposed. It is thus not easy for a potential user of such techniques to choose a technique suitable for his/her project because too many techniques exist and projects are different from each other. In this paper, we proposed a model for characterizing a traceability technique with respect to its users. The model can become a meta-model of the knowledge base for such users. The model is designed on the basis of the contents of existing technical papers so that we can easily describe model instances on the basis of technical papers. The model is represented in a feature model, and it has four mandatory features: source, destination, consequence and process. The user can at least understand a technique is unsuitable for him/her by referring such features. If a technique estimates the traceability relationships, the instance of its feature model may contain the quality metrics of its estimation such as precision and recall. It has also several optional features: assumptions, preprocess and tool. Although we sometimes cannot obtain such optional features from technical papers, they are so helpful for a user to decide a technique suitable for him/her. On the basis of the feature model, we described model instances of several techniques in technical papers. We also examined and discussed who the suitable user for each technique is.

In recent years, the paradigm of social coding in software development has attracted attention to developers all over the world, and GitHub which is a social coding tool has spread to the area like education. There are many cases using it as a platform of PBL (Project Based Learning). However, since GitHub is not a tool for education, it is difficult to evaluate learners. This research focuses on the contribution of learners and proposes a system that teachers can grasp the contribution of learners.

With the growing number of services on the Internet, the need for secure software development has increased. It is required for secure software development to consider security in the whole development life cycle. It is indispensable for secure software development to use various types of security knowledge. This study deals with security requirement analysis. Existing security requirements modeling systems do not provide a function to create an artifact while referring to security knowledge in an integrated manner. In this paper, the authors develop a modeling support system for a misuse case diagram that enables the association of knowledge with elements that constitute the diagram. The results of an experiment using the system show the system's usefulness in both the integration of the knowledge base with the artifact creation environment and the association of the knowledge with the elements of the diagram.

Project Based Learning targeted at software development (SD-PBL) has been paid attention to as a practical education method. A number of studies regarding communication support in SD-PBL have been conducted. However, systematic review in the field does not exist as far as we know. Therefore, this paper conducts systematic literature review regarding communication support in SD-PBL and shows current trends. We find this research field has been actively conducted since 2011, in addition, more studies used existing tools rather than developed original tools, in particular, Learning Management Systems were used. On the other hand, no used software engineering tools like contemporary popular GitHub and Slack combination.

Traceability is important knowledge for improving the artifacts of software and systems and processes related to them. Even in a single system, various kinds of artifacts exist. Various kinds of processes also exist, and each of them relates to different kinds of artifacts. Traceability over them has thus large diversity. In addition, developers in each process have different types of purposes to improve their artifacts and process. Research results in traceability have to be categorized and analyzed so that such a developer can choose one of them to achieve his/her purposes. In this paper, we report on the results of Systematic Literature Review (SLR) related to software and systems traceability. Our SLR is preliminary one because we only analyzed articles in ACM digital library and IEEE computer society digital library. We found several interesting trends in traceability research. For example, researches related to creating or maintaining traceability are larger than those related to using it or thinking its strategy. Various kinds of traceability purposes are addressed or assumed in many researches, but some researches do not specify purposes. Purposes related to changes and updates are dominant.

We propose a metamodel for handling security and privacy in cloud service development and operation. The metamodel is expected to be utilized for building a knowledge base to accumulate, classify and reuse existing cloud security and privacy patterns and practices in a consistent and uniform way. Moreover the metamodel and knowledge base are expected to be utilized for designing and maintaining architectures for cloud service systems incorporating security and privacy.

An information system can store personal information of its primary users such as shopping histories, and some third party wants or happens to know such information. Because the system usually provides its privacy policy and its users have to give their consent to it, they sometimes have to partially give up the protection of their privacy. On the other hand, a chance of a third party to know such information is too limited if the policy is too defensive. We proposed a method to explore trade-offs between protection of such information and access permissions for a third party, and exemplified it. In this method, operation logs of a system are focused. The structure of each log is then modelled for analysing what kinds of information can be accessed by a third party. Access limitations of each third party are explored so as to balance the protection of privacy information against access right of third parties.

In recent years, importance on software security technologies has been recognized and various types of technologies have been developed. On the other hand, in spite of recognition of necessity of providing cases that deal with full life cycle for secure software development, only few are reported. This paper describes a case-based management system (CBMS) that consists of an artifact management system and a knowledge-based management system (KBMS) to manage cases for secure software development. The former manages the artifacts created in secure software life cycle. The latter manages software security knowledge. The case-based management system also manages association between artifacts and software security knowledge and supports both visualization among software security knowledge and between artifacts and software security knowledge. We conducted an experiment to evaluate the system. We describe the effectiveness and future work of the system.

Under the global competition of business, software development is required to be conducted more efficiently. In particular, software maintenance holds the majority in the costs of software development. Developers must understand a project to conduct software maintenance efficiently. Therefore this study develops a support system for understanding a project in software maintenance. This study proposes to use the program package name. To utilize function name as the program package name is required. By using the name, the system extracts associations with parts of functional specification. Furthermore, based on the cosine similarity using the vector space model between design documents or communication messages and the parts extracted by the program package name, related artifacts are recommended by the system.

Recent years, the practical software engineering education has been carried out in universities and other higher education institutions. In this paper, we propose a software development exercise support system that collects a finer-grained history of students' activities. This system makes it easy to understand the status and progress of students learning by teachers. Then, this system will help support for learning.

As the services on the network increase, importance of the server administration increases. Sophistication and abundant experience are necessary for server administration, and the knowledge transfer to novice server administrators is important. We think that knowledge and experience of the administrators are condensed in operations histories. Therefore, in this paper, for the purpose of knowledge transfer support for server administration, the authors describe a system for knowledge transfer support of server administration using operations histories.

With an increase in the services on the Internet, importance for software security technologies has been recognized. A number of research and development programs regarding software security have been carried out thus far. However, it is not clear how these technologies can be combined in order to utilize them effectively. This paper proposes a conceptual model for a body of knowledge regarding software security. In addition, this paper introduces an overview of technologies developed for different pieces of knowledge and the current status of research that has clarified the relationships between these pieces of knowledge. Finally, the author discusses the future direction of this field.

The importance of software security technologies is increasingly being recognized with the increase in services available on the Internet. It is important to foster human resources with knowledge and skills relevant to software security technologies. This paper proposes a learning process for software security and a learning environment that supports the learning process. In the learning process, learners create artifacts for software security from artifacts created in a traditional software engineering course, without dealing with software security, by referring to the reference information for software security (standards, methodologies, guidelines, security patterns, and so on). The learning environment supports storage of (1) the artifacts created in a traditional software engineering course, (2) artifacts created in a software security course, (3) the reference information and the relationships between different pieces of the reference information, (4) the rationale and association of the reference information with the artifacts created in a software security course, and (5) review comments and their association with the artifacts created in a software security course.

In recent years, research on recommendation systems for software development has been actively conducted. The systems are mainly divided into know-how systems and know-who systems. The target of this study is education domain, and developers are university students. They are novice for software development and they leave the course after finishing it. Therefore know-how acquisition and sharing are very important. The authors developed a know-how recommendation system using the content filtering technique of which targets are stored know-how and inquiry sentences written in natural language. The results of a preliminary experiment in a project-based course of a university showed that the system could recommend appropriate pieces of know-how for four inquiries of which although solutions of inquiries were stored in the database, developers could not find solutions and the teaching staff showed the location of the corresponding know-how.

Summary form only given, as follows. The complete presentation was not made available for publication as part of the conference proceedings. Along with this trend, distributed collaborative modeling supporting systems have been proposed. These systems provide a UML diagrams editor and some sort of communication tools such as bulletin board system, annotation, and so on. However, UML diagrams and conversation contents the systems generate are not associated with each other. Therefore it is difficult to trace rationale with respect to elements of the diagram. The authors developed a distributed collaborative modeling supporting system for UML diagrams, called Libra-on-Chat, which solved the issue. Libra-on-Chat provides UML diagrams editor, chat-based communication tool, and their association facility. As the result of experiment, the authors found that the system allows participants to focus on elements in a diagram under discussion. It also enables developers to grasp design rationale in reviewing the diagram. On the other hand, that awareness information should be provided was recognized.

The authors created a Web-based collaborative learning system, which supported question-posing by learners, assessment from peers, and communications with question-posers and peers. They applied it to an actual university course. As the results, they identified some features to be enhanced, i.e., communication support, solution to a problem with respect to quality of posed questions, and motivation improvement. This paper describes a learning community support system based on question-posing called Concerto II to solve the problems.

Software development is knowledge-intensive and collaborative. Problem solving processes are performed iteratively during software development. This paper proposes a learning process model that is based on reflection and knowledge collaboration for problem solving in a software engineering education. This paper also describes an overview of a support system and a preliminary result from its application.

Software development is knowledge-intensive as well as collaborative work carried out by several persons. In this type of education, project-based exercises are conducted in order to acquire skills. Object-oriented software development has recently emerged as the primary branch of learning. However, it is difficult for novice students to develop software using the object-oriented paradigm. This paper proposes a method of education and a learning environment for object-oriented software engineering based on the cognitive apprenticeship model.

The authors have been conducting software engineering education in the form of group learning in a university. We developed a group learning support system and applied it to an actual class. Our experience showed us that it was difficult for some groups to develop software smoothly, because development was often performed in a distributed environment. Thus we understood that awareness to ascertain the situation of the other members (including the teaching staff) was needed. We describe how we considered the awareness support requirements in software engineering education, and provided functions to meet the requirements. In doing so, we applied a group learning support system that provided awareness support to an actual class, and found an action pattern in the activity on the system after using awareness support functions. The results we obtained from questionnaires showed that the awareness support function was also useful in enabling the members to determine other members' situations.

Software development is knowledge-intensive work. In a software project, various types of problems need to be resolved. One approach to acquiring the knowledge necessary for software development in a university education environment is for the students to experience project-based software development. For this kind of education to succeed, collaboration is inevitable between both the teacher side (teacher and teaching assistants) and student groups and within the group membership. This paper describes a collaborative software engineering education environment that in particular focuses on supporting collaboration between the student groups and the teacher side, its application to a real class and the results. The system supports four aspects of collaboration; inspection, acceptance testing, comments attachment for artifacts, and informal communication.

The authors have been developing an education system that supports university-level group exercises related to the design and implementation of information systems. The system is composed of three sub-systems: group organization, electronic textbook creation and software development process support. These are flexibly integrated via databases. The authors applied this system to an actual class at their university, and evaluated the system based on quantitative data from exercise outputs and student questionnaires. The questionnaire results indicated that the system was especially effective for document creation and for monitoring progress among group members. Groups that used the system created more documents than those that did not. Personal progress reports were the most frequently created documents.

The author has been performing education on design and implementation of an information system in the form of group exercises in a university. He describes the class design, results of three years' practice, and a learning support system of the exercises. As for the class design, he mainly focuses on team organization to ensure to minimize the difference of ability between teams and interactions between the teacher and the students (introduction of design inspection). Effectiveness of the class, the approach to team organization, and introduction of design inspection are found.

Workers in software projects are usually engaged in main development and other work, concurrently. Other work might put pressure on the schedule of the whole project. Therefore an order to manage the whole project appropriately, not only the main development work but also other work should be dealt with as management objects. The paper clarifies a framework to support various types of work and different granularity of processes in an integrated manner and shows the behavior of the system using an example. This framework enables appropriate process management of the whole project by taking into consideration workers' workloads (who is doing what activity at what workload at what time).

The authors aim at constructing an integrated software project management system with an object database. This paper describes a process model for software project management that forms the basis of the system. This paper also describes a framework for inducing the sequence of operations that the project manager must perform: issuing instructions to workers in accordance with a plan based on the process model, progress evaluation based on progress reports sent from the workers, and analysis of the impacts of any problems detected. In order to provide these facilities, we analyse the actions triggered per unit of activity from the viewpoint of project management. Based on this analysis, this paper proposes a finite state machine model involving the actions and the states changed by the actions. When an action is triggered, the system checks whether the action is effective or not, and provides the necessary information to the appropriate persons by referring to the relationships specified in the process model. This paper also describes prototype system based on the framework.>

Development of large-scale software generally involves in setting up of a project. Intensive management offers a practical approach to such development. Therefore, the key to success of a project is to develop technology which provides strong support for project management. This paper describes the requirements for a system which supports the process management of a software development project, placing emphasis on the following requirements for that system: (1) The activities and the resources which perform activities must be specified for a software development project. These resources include people resources and non-people resources such as tools and machines. (2) The relationships between the activities and resources must be established. This paper proposes a process model which specifies the relationships between the activities and the resources according to the above requirements. This paper also explains the behavior of the model by an example and discusses the usefulness of the model.>