Abstract 5: Cloud applications monitoring: An industrial study

(1)Modern software systems employ large IT infrastructures hosted in on-premise clouds or using “rented”
cloud resources from specific vendors. (2) The unifying force across any cloud strategy is incremental product
and application improvement against conservation of those resources. (3) This is where monitoring of cloud
applications becomes a key asset. (4) To shed light over the status of monitoring practices in industry, we
study: (a) monitoring practices and tools adoption in industry; (b) size and complexity of industrial monitoring
problems; (c) the role of software architecture and software process with respect to monitoring strategies. (5)
We conduct mixed-methods empirical research featuring interviews and a web survey featuring 140+
practitioners from over 70 different organizations. (6) Even if the market makes available a significant set of
monitoring tools, our results show a rather unappealing picture of industrial monitoring: (a) industrial decision-
makers do not perceive monitoring as a key asset even though the downtime of their applications correlates
heavily with the level of automation and responsiveness enabled by monitoring; (b) monitoring is done with
crude technology, mostly MySQL querying or similar (e.g., Nagios); finally, (c) incidents are discovered by
clients rather than application owners. (7) We conclude that the road toward the industrial adoption of cutting-
edge monitoring technology is still one of the less travelled, presumably in connection to the considerable
investment required. (8) Furthermore, the lack of industrial cloud monitoring standards does not help in
addressing the proliferation of multiple tool combinations, with varying effectiveness. (9) Further research
should be invested in looking into and addressing these major concerns.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2,3,4 5 6 7,8,9
(e.g 1,2,3..)

Abstract 6: Governance and Management of Green IT: A Multi-Case Study

(1) The changes that are taking place with respect to environmental sensitivity are forcing organizations to
adopt a new approach to this problem. (2) Implementing sustainability initiatives has become a priority for the
social and environmental awareness of organizations that want to stay ahead of the curve. (3) One of the
business areas that has, more than others, proven to be a vital asset and a potential ally of the environment, is
the area of Information Technology (IT). (4) Through this area, Green IT practices advocate sustainability in
and by IT. (5) However, organizations have a significant handicap in this regard, due to the lack of specific
Green IT standards and frameworks that help them carry out this type of sustainability practices. (6) Objective:
We have developed the “Governance and Management Framework for Green IT” (GMGIT), which establishes
the necessary characteristics to implement Green IT in organizations, from the point of view of the governance
and management of this area. (7) After developing and validating a first version of this framework, we have
performed a set of improvements, obtaining the GMGIT 2.0, which we want to validate. (8) We have conducted
a series of empirical validations at international level based on case studies, whose characteristics and results
are presented in this study. (9) The results of this multi-case study show an example of the current situation of
organizations in Green IT, as well as the resolution of problems encountered during the validations conducted
with the GMGIT 1.0. (10) The findings obtained demonstrate the usefulness, applicability, and validity of the
framework when implementing, auditing, and improving Green IT in organizations in a systematic and
progressive manner.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2,3,4,5,6,7 8 9 10
(e.g 1,2,3..)
Abstract 7: A unified framework for declarative debugging and testing
(1) Debugging is the most challenging and time consuming task in software development. (2) However, it is
not properly integrated in the software development cycle, because the result of so much effort is not available
in further iterations of the cycle, and the debugging process itself does not benefit from the outcome of other
phases such as testing. (3) We propose to integrate debugging and testing within a single unified framework
where each phase generates useful information for the other and the outcomes of each phase are reused. (4)
We consider a declarative debugging setting that employs tests to automatically entail the validity of some
subcomputations, thus decreasing the time and effort needed to find a bug. (5) Additionally, the debugger
stores as new tests the information collected from the user during the debugging phase. (6)This information
becomes part of the program test suite, and can be used in future debugging sessions, and also as regression
tests. (7) We define a general framework where declarative debugging establishes a bidirectional collaboration
with testing. (8) The new setting preserves the properties of the underlying declarative debugging framework
(weak completeness and soundness) while generating test cases that can be used later in other debugging
sessions or even in other cycles of the software development. (9) The proposed framework is general enough
to be instantiated to very different programming languages: Erlang (functional), Java (imperative, object-
oriented), and SQL (data query); and the experimental results obtained for Erlang programs validate the
effectiveness of the framework. (10) We propose a general unified framework for debugging and testing that
simplifies each phase and maximizes the reusability of the outcomes in the different phases of the software
development cycle, therefore reducing the overall effort.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2,3 4,5,6 7,8,9 10
(e.g 1,2,3..)

Abstract 8: What skills do IT companies look for in new developers? A study with Stack Overflow jobs
(1) There is a growing demand for information on how IT companies look for candidates to their open
positions. (2) This paper investigates which hard and soft skills are more required in IT companies by analyzing
the description of 20,000 job opportunities. (3) We applied open card sorting to perform a high-level analysis
on which types of hard skills are more requested. (4) Further, we manually analyzed the most mentioned soft
skills. (5) Programming languages are the most demanded hard skills. (6) Communication, collaboration, and
problem-solving are the most demanded soft skills. (7) We recommend developers to organize their resum´e
according to the positions they are applying. (8) We also highlight the importance of soft skills, as they appear
in many job opportunities.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2 3,4 5,6 7
(e.g 1,2,3..)
Abstract 9: A Method to Estimate Software Strategic Indicators in Software Development: An Industrial
Application

(1) Exploiting software development related data from software-development intensive organizations to
support tactical and strategic decision making is a challenge. (2) Combining data-driven approaches with
expert knowledge has been highlighted as a sensible approach for leading software-development intensive
organizations to rightful decision-making improvements. (3) However, most of the existing proposals lack of
important aspects that hinders their industrial uptake such as: customization guidelines to fit the proposals to
other contexts and/or automatic or semi-automatic data collection support for putting them forward in a real
organization. (4) As a result, existing proposals are rarely used in the industrial context. (5) Support software-
development intensive organizations with guidance and tools for exploiting software development related data
and expert knowledge to improve their decision making. (6) We have developed a novel method called SESSI
(Specification and Estimation of Software Strategic Indicators) that was articulated from industrial experiences
with Nokia, Bittium, Softeam and iTTi in the context of Q-Rapids European project following a design science
approach. (7) As part of the industrial summative evaluation, we performed the first case study focused on the
application of the method. (8) We detail the phases and steps of the SESSI method and illustrate its application
in the development of ModelioNG, a software product of Modeliosoft development firm. (9) The application
of the SESSI method in the context of ModelioNG case study has provided us with useful feedback to improve
the method and has evidenced that applying the method was feasible in this context.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2,3,4,5 6,7 8 9
(e.g 1,2,3..)

Abstract 10: Case Study Research in Software Engineering—It is a Case, and it is a Study, but is it a
Case Study?
(1) Case studies are regularly published in the software engineering literature, and guidelines for conducting
case studies are available. (2) Based on a perception that the label ‘‘case study’’ is assigned to studies that are
not case studies, an investigation has been conducted. (3) The aim was to investigate whether or not the label
‘‘case study’’ is correctly used in software engineering research. (4) To address the objective, 100 recent articles
found through Scopus when searching for case studies in software engineering have been investigated and
classified. (5) Unfortunately, the perception of misuse of the label ‘‘case study’’ is correct. (6) Close to 50% of
the articles investigated were judged as not being case studies according to the definition of a case study. (7)
We either need to ensure correct use of the label ‘‘case study’’, or we need another label for its definition. (8)
Given that ‘‘case study’’ is a well-established label, it is probably impossible to change the label. (9) Thus, we
introduce an alternative definition of case study emphasising its real-life context, and urge researchers to
carefully follow the definition of different research methods when presenting their research.

Structure Aims-background Methods Findings Conclusion/ implications

Sentence Number 1,2,3 4 5,6 7,8,9
(e.g 1,2,3..)