1,721,200 research outputs found
Going Beyond Counting First Authors in Author Co-citation Analysis
Full text linkThe present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
Mobile multiplatform development: An experiment for performance analysis
No full textPair Programming is one of the most studied and
debated development techniques. However, at present, we do
not have a clear, objective, and quantitative understanding of
the claimed benefits of such development approach. All the
available studies focus on the analysis of the effects of Pair
Programming (e.g., code quality, development speed, etc.) with
different findings and limited replicability of the experiments.
This paper adopts a different approach that could be
replicated in an easier way: it investigates how Pair
Programming affects the way developers write code and
interact with their development machine. In particular, the
paper focuses on the effects that Pair Programming has on
developers’ attention and productivity. The study was
performed on a professional development team observed for
ten months and it finds out that Pair Programming helps
developers to eliminate distracting activities and to focus on
productive activitie
Preparing Mobile Software Development Processes to Meet Mission-Critical Requirements
No full textMobile systems have evolved to a level where they are required to carry out their operations in a wide range
of environments, from voice communication, networking and entertainment to complex business
applications. Software running on mobile devices has as well grown to a point in which it has earned a
major role and impact on the overall performance and capability of a system. This situation attracts a
genuine interest of knowing in a more detailed fashion the conditions under which mobile software systems
are conceived, designed, implemented, and maintained, both from process and product point of views.
In parallel, “mission-critical” is a recurrent concept in Software Engineering that refers to software
systems in which a malfunction may lead to injuries, loss of lives or loss of significant investment. As
consequence, these systems require the highest care through all steps of the software development cycle [1].
Application areas of mission-critical software comprehend manufacturing control, transportation systems,
weapon delivery systems, space programs, air traffic control, medical systems and many others [2].
The continuous growth in capabilities in software applications running in mobile devices allows them to
become an attractive platform to be part of more complex systems, including safety-critical or missioncritical
systems. As mentioned above, due to the nature of these environments, such mobile software system
would be required to meet strict assurance practices with regard to safety, security and performance, being
subject to attain certifications from competent authorities before entering into service.
Currently we count on several software processes and quality management systems intended to support
the development of general-purpose (e.g. CMMi, ISO 12207, ISO 15504) or application-specific (e.g.
RTCA/DO-178B, ISO 62304, EN 50128) software. These models were conceived and developed without
considering restrictions given by a specific target platform, and are general enough to accommodate any
execution environments (e.g. embedded, desktop, etc.), so they are prepared to suit the needs and
restrictions of mobile equipment.
On the other hand, the number of published development models specific for mobile software systems
(e.g. Mobile-D [3] or RaPiD7 [4]) is still limited, and they present addressable shortcomings. These models
converge in the selection of Agile methodologies to provide a development framework, calling attention on
the necessity of adapting the processes and practices to the evolving needs of mobile software, shorting the
development cycles. As a common characteristic, they have claimed little level of criticality on mobile
applications, so Agile quality assurance practices do not necessarily fulfill the requirements imposed by
application-critical standards or certification procedures [5].
In summary, currently it is not available a methodology or framework to manage the assurance of
mobile software so as to produce application-critical, certifiable software, taking into account the needs,
boundaries, and particular conditions given by a mobile environment. Such conditions may impact the
quality of the software product within a mission-critical system, and deserve to be carefully considered in
addition to the practices already dictated by safety-critical software development standards.
We believe that it is necessary to study (i.e. survey, leverage) current software assurance practices
adopted by mobile development, and analyze the existing gap between them and mission-critical software
standards. After knowing such distance, we may identify the ways in which current practices can be
strengthened or adapted to have a robust mobile software assurance process that positively aids mobile
developers to produce software able to be incorporated into a certifiable mission-critical environment
Defining relevant software quality characteristics from publishing policies of mobile app stores
No full textPublishing a product in a mobile app store implies a process that
makes a software product
accessible to millions of users. Developers require the
means to evaluate the quality of the mobile software product from a viewpoint
that considers the mobile business, users, target platforms and app stores. In this
paper, we surveyed the publishing guidelin
es of six major app stores to identify
the most important software quality requirements set upon mobile apps. We le-
veraged the ISO/IEC 25010 quality standard as a mechanism to assure the ful-
fillment of the quality requirements from the mobile app stores, and we defined
an association between such requirements and the characteristics of the quality
standard. Finally, we introduced a Mobile App Quality Model, which aims to
provide a reference to assure the development of mobile-specific, market-
compliant mobile software applications
Agile Software Development Processes for mobile systems: Accomplishment, Evidence and Evolution
No full textMobile
software
applications
have to cope with a
particular
execution
environment
that includes
limited resources, high autonomy
requirement
s
, market
regulations
,
and
many
other
constraints
.
To provide a
software
development process that responds to these challenges, several
methodologies
proposed
the adoption of Agile practices
;
however,
it is not clear
how a software development process would help to solve
all
the iss
ues present
in the mobile domain. Moreover, the rapid evolution of the mobile environment
questions
several of the premises upon which the proposed methodologies were
designed
. In this paper, we present a review on Agile software development
processes for
mobile applications and their implementations, with the objective
of knowing the
contribution of Agile methods to address the needs of the
mobile soft
ware in a
real
production environmen
t
.
In addition, we
aim
to put up
to date
the discussion abou
t
what are the best
practices that facilitate the
creation of high quality
software products
in the current mobile domai
Using a Partially Instantiated GQM to Measure the Quality of Mobile Applications (S)
No full textM
obile
application markets
manage hundreds of
thousands of
products
involving millions of downloads. The
quality of these applications is normally contr
olled by market
policies
;
h
owever, there is no link between the quality goals of the
mobile software market and the practices that have to be
exercised to
assure
a compliant application. In this paper, we
propose a GQM
-
based strategy to supply
the
mechanis
ms to
measure
the quality of mobile software products.
By partially
instantiating a GQM
structure
, we can have a schema previously
furnished to consider beforehand the conditions of the mobile
domain that typically impact the quality of the final product
.
O
ur
approach
offers to apply a strong
quality model in a
field that
requires strong quality metrics to assess
products generated in
short development cycles
,
with a potential impact of millions of
users, executed in a
very
limited environment
Managing TETRA Channel Communications in Android
No full textMobile systems have evolved to a level in which they have to carry out their operations in environments demanding high availability and short response time. An excellent radio transmission protocol is necessary to provide the means to satisfy such requirements. TETRA standard offers a large number of features designed for safety and emergency use; however, to access a TETRA network it is compulsory the use of a standard-specific device. In this paper we explore the conditions that have to be fulfilled to extend Android's capabilities to access TETRA networks from a general-purpose mobile device, and set a path for a future development aimed to accomplish it
Software Assurance Practices for Mobile Applications
No full textMobile software applications have to cope with a particular environment that involves small size, limited resources, high autonomy requirements, competitive business models and many other challenges. To provide development guidelines that respond to these needs, several practices have been introduced; however, it is not clear how these guidelines may contribute to solve the issues present in the mobile domain. Furthermore, the rapid evolution of the mobile ecosystem challenges many of the premises upon which the proposed practices were designed. In this paper, we present a survey of the literature on software assurance practices for mobile applications, with the objective of describing them and assessing their contribution and success. We identified, organized and reviewed a body of research that spans in three levels: software development processes, software product assurance practices, and software implementation practices. By carrying out this literature survey, we reviewed the different approaches that researchers on Software Engineering have provided to address the needs that raise in the mobile software development arena. Moreover, we review the evolution of these practices, identifying how the constant changes and modernization of the mobile execution environment has impacted the methods proposed in the literature. Finally, we introduced discussion on the application of these practices in a real productive setting, opening an area for further research that may determine if practitioners have followed the proposed assurance paradigms
Variations on the Author
Full text link“Variations on the Author” discusses two of Eduardo Coutinho’s recent films (Um Dia na Vida, from 2010, and Últimas Conversas, posthumously released in 2015) and their contribution to the general question of documentary authorship. The director’s filmography is characterized by a consistent yet self-effacing form of authorial self-inscription: Coutinho often features as an interviewer that rather than express opinions propels discourses; an interviewer that is good at listening. This mode of self-inscription characterizes him as an author who is not expressive but who is nonetheless markedly present on the screen. In Um Dia na Vida, however, Coutinho is completely absent form the image, while Últimas Conversas, on the contrary, includes a confessional prologue that moves the director from the margins to the center of his films. This article examines the ways in which these works stand out in the filmography of a director who offers new insights into the notion of cinematic authorship
- …
