<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0">
<channel>
<title>Journal of Software Engineering - Current Issue</title>
<link>https://scialert.net</link>
<description>Journal of Software Engineering</description>
<language>en-us</language>
<copyright>Science Alert</copyright>
<pubDate>Thu, 11 Jun 2026 18:11:57 +0200</pubDate>
<lastBuildDate>Thu, 11 Jun 2026 18:14:14 +0200</lastBuildDate>
<generator>RssPublisher 0.2.0 beta</generator>
<image>
<url>https://scialert.net/images/logo.gif</url>
<title>Journal of Software Engineering - Current Issue</title>
<link>https://scialert.net</link>
<height>41</height>
<width>233</width>
<description>Journal of Software Engineering</description>
</image>
<item>
A Meta-Model for Model-Based Testing Technique: A Review<title><![CDATA[A Meta-Model for Model-Based Testing Technique: A Review]]></title> 
<description><![CDATA[In software testing field, model-based testing technique is a prominent validation technique that assures the high performance and evaluation of the systems. It is proposed to replace the manual way by generating automatically test cases from requirements. From the fact to its high practical relevance, several approaches that support model-based testing technique have been proposed in academic and industrial research. Although, most of these approaches differ on several important points like the specification paradigm, the model used to design requirements but share common principal, common challenges and common characteristic that are inherited from the fundamental concepts of model-based testing technique. In this context, proposed through this study a meta-model that represents model-based testing concepts and characteristics in order to define the structure and entities that must take any new model-based testing approach.]]></description>
<link>https://scialert.net/abstract/?doi=jse.2018.1.11</link> 
<pubDate>11 June, 2026</pubDate>
</item>
<item>
Toward a Reference Model for Adopting Software Continuous
Delivery: A Practical Approach<title><![CDATA[Toward a Reference Model for Adopting Software Continuous
Delivery: A Practical Approach]]></title> 
<description><![CDATA[Releasing a new version of a software system is a relatively complex process that requires lengthy and complicated preparation and
coordination between different role-players of the development and operation teams. The difficulty originates during the early stages
of gathering requirements and continues to the stages of software deployment and maintenance. Enhancing the software development
process and overcoming some of the obstacles encountered by developers can be achieved through the utilization of continuous delivery
(CD) practices. This analytical study investigated the currently available CD implementations in industry to identify the key characteristics
of CD from a practical perspective and to evaluate them based on the commonly defined characteristics in the literature. A number of
solutions were examined and a taxonomy that highlighted the similarity and variations in every solution was generated. Subsequently,
a discussion of the requirements needed for a CD reference model was presented, which represents the key contribution of this work.
The proposed analytical framework was evaluated in terms of a taxonomy that was generated in this work. The key characteristics of a
CD model were highlighted at both the conceptual and implementation levels in light of the currently available technologies and the
overall results obtained favored the assertion made in this work regarding the essence of generating a standard reference model for CD.
The experiment also identified the common underlying components of a CD model, which were believed to be essentially the building
blocks for the successful implementation of a CD model. The model proposed in this work may act as a baseline for defining a reference
model for CD in practice. Software development organizations can refer to this model for the implementation of their underlying delivery
pipelines. This model was investigated thoroughly in the context of web-portal development environments.]]></description>
<link>https://scialert.net/abstract/?doi=jse.2018.12.19</link> 
<pubDate>11 June, 2026</pubDate>
</item>
</channel>
</rss>