Software Engineering Method And Theory Research Articles

SEMAT Essence Game: A Fun Way to Learn about the SEMAT Initiative

Objective: we aim to propose the SEMAT Essence game, a game-based simulation of the big picture related to the SEMAT Essence kernel. SEMAT (Software Engineering Method and Theory) is an initiative for re-founding software engineering based on a solid theory, proven principles, and best practices. SEMAT has the Essence kernel of universal elements for any software engineering endeavor. The SEMAT Essence has been taught by using workshops and some games, but such strategies only cover some topics related to the kernel. Materials and methods: We use the SEMAT Essence kernel as a starting point and we select a game to be the template of our game. Then, we define the metaphor linked to our field of study and design the game by defining equivalences to the game elements. Results and discussion: We also show the results of practicing the game with a set of students from four universities by summarizing the answers to a survey. Conclusions: Results are promising since practitioners report some usage of the SEMAT Essence kernel elements after the game and they are satisfied with the fun factor, realism, and the current version of the game.

Three Principles of Intellectualization of Automated Systems

Three Principles of Intellectualization of Automated Systems

Integration of the software engineering theory and the quality function deployment methodology for supporting the measurement of the state of progress in software projects

A fundamental practice to fulfill the objectives in a software project, is to measure its state of progress so that corrective actions can be taken timely. Most of approaches supporting measurement processes are focused on describing techniques to deal with these measurements from a project management perspective. However, these approaches lack of strategies that facilitate an adequate integration, understanding and application by professionals in software development area. In addition, the lack of rigor of such proposals hinders the establishment of common practices and give rise to unreliable results. This paper is aimed at providing an approach that satisfy the need of using frameworks standardized and easily adopted in order to support the measurement in the software development. To do this, we use the elements provided by SEMAT (Software Engineering Method and Theory) and the procedures established by QFD (Quality Function Deployment) by generating a proposal which includes a representation standardized and a method to analyze the needs of measurement from customer perspective. Also, a mapping review and a study based on interviews intended to assure the reliability of the findings exhibited in this paper were done.

A Proposal for Improving the Essence Standard by Using Terminology Unification

Context: SEMAT (Software Engineering Method and Theory) is promoting a software engineering theory with adequate terminology to improve the transference of methods and practices between teams. Terminologies should be uniform in order to eliminate ambiguity, improve communication among teams, and support new concepts. Method: The process of reaching uniformity is called terminology unification. In this paper we propose a method for improving the Essence standard based on terminology unification. This method comprises four stages: selection of base models and definitions for structuring terms, identification of terminology problems by comparing the base models and definitions, unification of terms among the base models and definitions, and measurement of the gap between the current standard terms and the proposed changes. Results: We propose a set of modifications to the Essence standard in constructs like: alpha state cards, relationships among alphas, and names of activity spaces. Conclusions: By solving such conflicts, we can define a common, unambiguous terminology for software engineering teams.

Towards Generating Essence Kernels Using Genetic Algorithms

Abstract The Software Engineering Method and Theory (SEMAT) community created the Essence kernel as a unifying framework for describing and analyzing software engineering endeavors. The Essence kernel is based upon human experience and judgment, not empirical data. Background At Carnegie Mellon University in Silicon Valley, we have collected data from masters of science in software engineering students as they complete a team-based project course as their capstone or practicum project using the Essence kernel. Each week, the team recorded their progress in an Essence Reflection meeting. This data serves as training data for evaluating the Essence kernel and alternative candidate kernels. Objective Generate candidate replacement kernels by using a fitness function based on empirical data. Method Using genetic programming, the kernel genotype is represented as a collection of linear state machines each with a collection of unique checklist items. Operations to evolve the genotypes include randomly moving checklist items, splitting states, and deleting states by moving their checklist items to other states. Results Genetic programming created random candidate essence kernels that scored higher fitness scores than the original essence kernel. The purpose of this exploratory work is to demonstrate one way to generate a candidate Essence kernel directly from empirical data, not to recommend a replacement for the original Essence kernel. Reducing the Essence kernel from seven alphas to one alpha results in higher fitness scores. Limitations Given the limited amount of data, the generated kernels may be over-optimized. Additional empirical data is required before recommending replacing the original kernel with a candidate kernel that fits the data. Conclusion The original Essence kernel is highly structured around human notions of order. Genetic algorithms can generate candidate kernels that humans might not normally consider. Based on the analysis of the fitness function, a kernel with a fundamentally different structure might more effectively recommend next steps for a team during Essence Reflection Meetings.

A Guideline for Product-Service-Systems Design Process

Product-Service Systems (PSS) has been regarded as an attractive business concept that create high added value by integrated provisions of products and services.Since both products and services are included in the design object, the PSS design process has become increasingly complicated. Thus, the designers need to organize reliably what they should accomplish during the PSS design process. However, it is difficult for designers to grapple what they need to focus on during PSS design process. To support such PSS design process, this paper proposes a PSS design guideline which based on Software Engineering Methods and Theory (SEMAT). The proposed guideline provides the designerswithPSS design perspective, milestones through the design process, and the way to manage the design process.

Integrating software engineering theory and practice using essence: A case study

Software engineering is complex and success depends on many inter-related factors. Theory Based Software Engineering (TBSE) is about providing a practical way for software teams to understand the relationships and the influence of these factors to thereby adapt the way they work. This paper proposes an approach to TBSE based on Essence, a software engineering kernel distilled by the SEMAT (Software Engineering Method and Theory) initiative. Essence supports TBSE by providing a domain model that is useful for organizing and relating software engineering factors. Essence also helps make recommended practices precise and actionable to software teams. We provide a step-by-step application of our approach on an industrial software process improvement case study. The case study achieved 21% productivity gains and 58% decrease in defects. But more importantly than these results, it demonstrates the value of Essence in supporting TBSE.

A FIRST COURSE IN SOFTWARE ENGINEERING METHODS AND THEORY

Even though the software engineering curriculum has been designed many times, some problems still remain: the gap between academy and industry, the failure to continuously update the courses, the difficulties for combining theory and practice, and the lack of a sound, widely accepted theoretical basis. The SEMAT (Software Engineering Methods and Theory) initiative has been proposed for addressing some of the aforementioned problems. Based on the main ideas related to SEMAT, in this paper we propose a first course that introduces students to the main issues about SEMAT. This course is planned to be included in the System and Informatics Engineering Program belonging to the Universidad Nacional de Colombia, Medellin Branch. Also, we discuss the way in which this course addresses the previously diagnosed problems.

Framework for Describing and Analyzing Context and Factors for Software Engineering Research: Applying the SEMAT Kernel

 Abstract—There is currently no widely accepted approach to report software engineering research findings. It is not easy to understand the context from which a research work is conducted and factors that influences the results, and hence difficult to evaluate the applicability of findings to another context. This paper proposes a framework for describing and analyzing context and factors for software engineering research. Our proposed framework is an approach towards Theory Based Software Engineering (TBSE) that relates contextual factors and process improvement objectives systematically. Our approach towards TBSE is centered on a software engineering kernel known as Essence. Essence originates from the recent global SEMAT (Software Engineering Method and Theory) initiative and is currently an emerging standard with OMG (Object Management Group). Essence helps identify architecture views to describe the context of a software engineering endeavor. It also helps identify factors of success and make recommendations precise and actionable. This paper demonstrates the application of our proposed approach on a telecommunications case study. This case study by itself is interesting because it yielded 21% productivity gains and 58% decrease in defects. But more importantly, it demonstrates the viability of our approach in making theory practical to development teams in a systematic manner.

Agile and SEMAT - Perfect Partners

Today, as always, many different initiatives are under way to improve the ways in which software is developed. The most popular and prevalent of these is the agile movement. One of the newer kids on the block is the SEMAT (Software Engineering Method and Theory) initiative. As with any new initiative, people are struggling to see how it fits into the world and relates to all the other things going on. For example, does it improve or replace their current ways of working? Is it like lean, which supports and furthers the aims of the agile movement, or is it more like waterfall planning, which is in opposition to an agile approach?

A Web-based modeling tool for the SEMAT Essence theory of software engineering

As opposed to more mature subjects, software engineering lacks general theories to establish its foundations as a discipline. The Essence Theory of software engineering (Essence) has been proposed by the Software Engineering Methods and Theory (SEMAT) initiative. Essence goal is to develop a theoretically sound basis for software engineering practice and its wide adoption. Essence is yet far from reaching academic and industry adoption. Reasons include a struggle to foresee its utilization potential and the lack of tools implementing it. SEMAT Accelerator (SematAcc) is a Web-positioning tool for a software engineering endeavor, which implements the SEMAT's Essence kernel. SematAcc allows using Essence, thus helping to understand it. The tool enables teaching, adopting, and researching Essence in controlled experiments and case studies.