Darío Macchi

Darío Macchi
Universidad ORT Uruguay | ORT · Faculty of Engineering

MSc

About

4
Publications
7,340
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
14
Citations
Introduction
I am currently interested in doing scientific research in the area of software engineering to add value to their body of knowledge but at the same time to meet some practical needs of the industry (especially technology issues). I've finished a Master of Engineering in order to bring some tools from the scientific environment to the daily activities of software development companies. Also I'm gaining knowledge about new tools that will allow me to achieve this goal.
Additional affiliations
August 2011 - present
Universidad ORT Uruguay
Position
  • Software Inspection Adoption
Description
  • Factors that difficult the adoption and how to avoid or overcome them. We carried out a mapping study to identify the factors causing low adoption, evidence of the problem and proposed solutions.
Education
August 2010 - March 2013
Universidad ORT Uruguay
Field of study
  • Computer Science
March 2000 - December 2008
Universidad ORT Uruguay
Field of study
  • Computer Science

Publications

Publications (4)
Conference Paper
Technical Debt is a metaphor that explains a phenomenon that occurs in software development when programmers are faced with trade-off decisions (usually ship first vs. quality assurance). This work analyses the amount of technical debt incurred by undergraduate students using different coding techniques. This observational study uses source code fr...
Conference Paper
Full-text available
There are different fault detection static techniques, but the reviews are specials because they don't require the execution of the artifact to be evaluated. The objective of this research is to understand how different artifacts are being reviewed during the software development process. It performs a survey for software development professionals...
Conference Paper
Full-text available
In Software Engineering technical literature the references about the benefits of software inspections are abundant. In contrast, some authors raise the problem of low adoption of this process. From this issue a literature review is made to produce a map on most researched topics in the area, factors causing low adoption and possible solutions. Res...

Questions

Questions (7)
Question
I'm doing my master thesis about software inspections and I want to call the process in the same way in every place. So, I'm asking if I should call inspections with small i or Inspection with capital I because is the name of a process.
I'm tending to use Inspection with capital I, what do you think about it?
Note 1: when i'm talking about software inspection I'm referring to the formal review process, known as Fagan Inspection.
Note 2: the IEEE standard about Software Reviews and Audits (1028) name it inspection, with small i, but Tom Gilb and Dorothy Graham in the preface of "Software Inspection" name it with capital I.
Question
About the IEEE1028 I have a question. Do you think that the methods "Technical Review" it's the same that Karl Weigers called "Team Review" in his book "Peer Reviews in Software: A Practical Guide"? Because I'm trying to merge his list of review methods ordered by formality with the methods of the IEEE1028 for my thesis work and I need to know where to put the "Technical Review".
Question
I'm doing some literature review using Scopus as bibliographic database. I know that the inclusion of other databases could improve the scope of the research but I'm asking if the use of only one database can be a threat to validity. (in this case I'm worried about Scopus vs. IEEE Explore + Springerlink + ACM)

Network

Cited By