Professional Documents
Culture Documents
The purpose of doing an analysis on any software engineering article is to have an idea about the
nature of research, how the information is organized and what kind of structure they mostly used in research
paper so this helpful information can be used later. This article was published in the journal selected in the
previous assignment.
The researcher used the IMRD structure to organize their information as they first have an
abstract, introduction, background or literature review, agile process explanation in detail and conclusion at the
end [1]. In this paper, they used IEEE format for citation [1]and it is a problem-oriented research because the
author is discussing the problems occurred using agile methods and then they talked about how to overcome
these problems using traceability. The visual data type that is used in this paper is diagrams or figures to explain
This study summarized that Three features that traceability model should support to be less
dependent on specific development processes: 1) User defined traceability links 2) roles 3) linkage rules [1]. In
this paper, After introducing three features into traceability models, two main advantages are obtained 1) the
support they can provide to agile process stakeholders is significantly more extensive and 2) it will be possible
In this article, the object of study which is also a Move 1 [2] is Traceability is recognized to
be more important for supporting agile development processes [1]. It is move 1 because its the most centralized
idea of the paper mean the whole research paper is related to this sentence.
In this paper, the trace is defined as the relationship between two or more products of development
and traceability is defined as the degree to which every element of software development made its reason for
existing [1], which is also a move 1 [2]. The exigence which is also a move 2 [2] is to study the processes of
agile from the perspective of traceability, then mentioning some requirements of traceability to support
effectively processes of agile and then explaining traceability meta-model (TmM) in detail and how it can assist
The purpose of this paper which is also Move 3 [2] is to identify the difference between agile and
traditional processes using traceability concepts specifically from the perspective of traceability meta-model
(TmM) [1].
This paper will help researchers to improve or provide more support to processes of agile and
specifically the automation process [1]. It will also help people to understand how the traceability meta-model
(TmM) can be used to differentiate between the processes of old and agile [1]. This research paper has enough
information to help me understand the different processes of software development such as TDD, SDD and TmM
and which are appropriate for agile processes.
References
[1] A. Espinoza and J. Garbajosa, "A study to support agile methods more effectively through," Innovations in
System and Software Engineering, vol. 7, no. 1, pp. 53-69, 2011.
[2] J. M. Swales and B. C. Feak, Academic Writing for Graduate Students, 3rd Edition, Michigan: Michigan
Publishing University of Michigan Press, 2012.