Search

The Hook model is used in digital products to engage and retain users through the mechanism of habit formation. This paper explores the use of Hook model techniques in two mobile applications, one being a popular taxi service (Uber taxi) and the other a social network (Instagram). The goal of this paper is to explore the Hook cycle patterns in the two products, and to identify commonalities and differences in how they are applied. Our results suggest that Hook cycle patterns appear with similar frequency; however, Instagram includes more internal Trigger calls. Uber uses fewer triggers to encourage usage, most probably because users already have a specific need for the application. For the same reason, Uber has less opportunity to fail in the reward delivery, while Instagram can use the failure (in providing a reward) as another trigger if the usage habit is already established. In addition, we introduce two types of Hook cycle patterns: internal (within a single use case) and external (transition between use cases). The insights obtained through the case studies serve as a practical reference for developing engaging and retention-focused applications. [ABSTRACT FROM AUTHOR]

The field of statistical computing is rapidly developing and evolving. Shifting away from the formerly siloed landscape of mathematics, statistics, and computer science, recent advancements in statistical computing are largely characterized by a fusing of these worlds; namely, programming, software development, and applied statistics are merging in new and exciting ways. There are numerous drivers behind this advancement, including open movement (encompassing development, science, and access), the advent of data science as a field, and collaborative problem-solving, as well as practice-altering advances in subfields such as artificial intelligence, machine learning, and Bayesian estimation. In this paper, we trace this shift in how modern statistical computing is performed, and that which has recently emerged from it. This discussion points to a future of boundless potential for the field. [ABSTRACT FROM AUTHOR]

Software regression testing techniques verify previous functionalities each time software modifications occur or new characteristics are added. With the aim of gaining a better understanding of this subject, in this work we present a survey of software regression testing techniques applied in the last 15 years; taking into account its application domain, kind of metrics they use, its application strategies and the phase of the software development process where they are applied. From an outcome of 460 papers, a set of 25 papers describing the use of 31 software testing regression techniques were identified. Results of this survey suggest that at the time of applying a regression testing techniques, metrics like cost and fault detection efficiency are the most relevant. Most of the techniques were assessed with instrumented programs (experimental cases) under academic settings. Conversely, we observe a minimum set of software regression techniques applied in industrial settings, mainly, under corrective and maintenance approaches. Finally, we observe a trend using some regression techniques under agile approaches. [ABSTRACT FROM AUTHOR]

With the gradual maturity of component oriented software development method, component-based software evolution technology has become hot research in academia and industry. Although many evolution rules are designed, they rarely consider component type-mismatched problem in evolution rules. This has led to evolution rules that often run error in software evolution execution. Hence, focusing on the mismatch problem of component type in software evolution, this paper addresses various evolution rules with condition constrains to support component type matching. First, we use the bigraph theory to model the software architecture and employ bigraph term language to describe the basic component evolution operations. Second, we join type system into the term language and use the type term language to express the condition constraints on position and connection for component evolution rules. These condition constraints can guarantee the type-matched among components that participate in software evolution. Furthermore, we show that the component type-matched still kept during a number of different evolution rules are used in the whole software evolution reaction system. Finally, two cases study of evolution progress of ATM system and tourism information system are presented. Two cases illustrate the effectiveness of our approach. [ABSTRACT FROM AUTHOR]

Minimization of data-processing time and reduction of software-development time are important practical problems to be tackled by modern computer science. This paper presents the authors' proposal of a family of statistical models for the estimation of program execution time, which is an approach focused on both of the above problems at the same time. The family consists of a general model and specific models and has been elaborated based on empirical data collected for pattern-program loops representing some arbitrarily selected features related to the program structure and the specificity of a program-execution environment. The paper presents steps to elaborate the aforementioned family as well as the results of the carried-out experimental research. The paper demonstrates how the elaborated models can be applied in iterative compilation for optimization purposes, allowing us to reduce the time of software development and produce code with minimal execution time. [ABSTRACT FROM AUTHOR]

Design patterns have gained popularity as they provide strategies for solving specific problems. This paper explores two common design patterns in iOS development field: Model View Controller (MVC) and Model View ViewModel (MVVM) design patterns. The paper investigates the problems with MVC design pattern. Then, it introduces a validation model that detects MVC problems, and helps programmers make the decision to switch between MVC and MVVM design pattern. The proposed validation model consists of two phases: phase one is to detect MVC problems, and phase two is to validate the relation between MVVM objects. The model was then applied to a Cloudy app as a case study. As a result, the model was able to detect MVC problems. The relation between MVVM objects was also validated. Further, this research provided some recommended solutions to satisfy the relations between MVVM objects in the project. [ABSTRACT FROM AUTHOR]

Computer science is a predominantly male field of study. Women face barriers while trying to insert themselves in the study of computer science. Those barriers extend to when women are exposed to the professional area of computer science. Despite decades of social fights for gender equity in Science, Technology, Engineering, and Mathematics (STEM) education and in computer science in general, few women participate in computer science, and some of the reasons include gender bias and lack of support for women when choosing a computer science career. Open source software development has been increasingly used by companies seeking the competitive advantages gained by team diversity. This diversification of the characteristics of team members includes, for example, the age of the participants, the level of experience, education and knowledge in the area, and their gender. In open source software projects women are underrepresented and a series of biases are involved in their participation. This paper conducts a systematic literature review with the objective of finding factors that could assist in increasing women's interest in contributing to open source communities and software development projects. The main contributions of this paper are: (i) identification of factors that cause women's lack of interest (engagement), (ii) possible solutions to increase the engagement of this public, (iii) to outline the profile of professional women who are participating in open source software projects and software development projects. The main findings of this research reveal that women are underrepresented in software development projects and in open source software projects. They represent less than 10% of the total developers and the main causes of this underrepresentation may be associated with their workplace conditions, which reflect male gender bias. [ABSTRACT FROM AUTHOR]

Digital transformation in the public sector provides digital services to the citizens aiming at increasing their quality of life, as well as the transparency and accountability of a public administration. Since adaptation to the citizens changing needs is central for its success, Agile methodologies seem best suited for the software development of digital services in that area. However, as well documented by an attempt to use Scrum for an important Public Administration in Italy, substantial modifications to standard Agile were needed, giving rise to a new proposal called improved Agile (in short, iAgile). Another notable example is the Scrum@IMI method developed by the City of Barcelona for the deployment of its digital services. However, given the importance of digital transformation in the public sector and the scarcity of efforts (documented in the scholarly literature) to effectively bring Agile within it, a strategically important contribution that Computer Science can offer is a general paradigm describing how to tailor Agile methodologies and, in particular, Scrum, for such a specific context. Our proposal, called Scrum@PA, addresses this strategic need. Based on it, a public administration has a technically sound avenue to follow to adopt Scrum rather than a generic set of guidelines as in the current state of the art. We show the validity of our proposal by describing how the quite successful Scrum@IMI approach can be derived from Scrum@PA. Although iAgile can also be derived from our paradigm, we have chosen Scrum@IMI as a pilot example since it is publicly available on GitHub. [ABSTRACT FROM AUTHOR]

The term solution space is widely used in the engineering community; yet there is little known about their evolution. Theoretical research in the field of systems science indicates that requirements can only reduce the solution space. Yet, some authors state that on the contrary requirements can be used to expand to or open new solution spaces. Furthermore, some practitioners defend that the requirement to use a previously nonexistent technology would actually increase the solution space or move it to a new area, while others state that more requirements make life more difficult. Who is right then? The present paper provides initial answers to this question using systems theory. In order to achieve this, the present paper differentiates between various types of solutions spaces, which depend on the systems they include. Finally, the paper provides practical examples to showcase the results of the theoretical findings within real contexts. [ABSTRACT FROM AUTHOR]

This paper will produce three areas of discussion in the field of cost estimation for unmanned autonomous systems. First, this paper will propose a common definition of an Unmanned Autonomous system. Second, it will introduce a method to estimate the cost of unmanned autonomous systems utilizing existing parametric cost estimation tools: SEER – HDR, COCOMO II, COSYSMO, and two relationships – weight and performance. The third discussion will focus on challenges surrounding autonomy. To address these challenges from a cost perspective, this paper recommends modifications to parameters within COCOMO II – via the use of object oriented function points in lieu of current methods, and COSYSMO – via the introduction of two cost driving parameters, namely, TVED and HRI-T. Finally, in summary this paper will identify areas of further research. [ABSTRACT FROM AUTHOR]

This paper discusses the use of model-based systems engineering (MBSE) models for physical protection systems (PPS) evaluation. We discuss why MBSE methodologies can be valuable in assessment of PPS. Next, we review the steps in vulnerability assessment (VA) and describe the use of SysML models in these steps. The paper presents examples of SysML models for a VA scenario. Such models can enable the development and integration of other VA tools and reduce the time and cost of conducting VA, which will lead to safer facilities. [ABSTRACT FROM AUTHOR]

We have developed a new system for measuring dental, gnathic, and facial areas with cephalogram-equivalent images created from computed tomographic imaging data. An advantage of this collaborative system is that a measurement template and automated processing are used. First, experienced orthodontists were provided with the measurement templates; they then moved the measurement markers to the specified landmarks on the cephalogram in the template. Subsequently, the program automatically detected the coordinates of the markers and calculated the distance between those coordinates. The appropriate use of this system leads to highly accurate results in large quantities of measurements in a short time by means of both manual and automatic processing. The system was developed to contribute to worldwide research into dental and craniofacial measurements; the research involved 500 patients, and the system worked successfully. [ABSTRACT FROM AUTHOR]

Arc welding is a thermal plasma process widely used to join metals. An arc welding model that couples fluid dynamic and electromagnetic equations was initially developed as a research tool. Subsequently, it was applied to improve and optimise industrial implementations of arc welding. The model includes the arc plasma, the electrode, and the workpiece in the computational domain. It incorporates several features to ensure numerical accuracy and reduce computation time and memory requirements. The arc welding code has been refactored into commercial-grade Windows software, ArcWeld, to address the needs of industrial customers. The methods used to develop ArcWeld and its extension to new arc welding regimes, which used the Workspace workflow platform, are presented. The transformation of the model to an integrated software application means that non-experts can now run the code after only elementary training. The user can easily visualise the results, improving the ability to analyse and generate insights into the arc welding process being modelled. These changes mean that scientific progress is accelerated, and that the software can be used in industry and assist welders' training. The methods used are transferrable to many other research codes. [ABSTRACT FROM AUTHOR]

Model-Based Software Engineering (MBSE) is an architecture-based software development approach. Agile, on the other hand, is a light system development approach that originated in software development. To bring together the benefits of both approaches, this article proposes an integrated Agile MBSE approach that adopts a specific instance of the Agile approach (i.e., Scrum) in combination with a specific instance of an MBSE approach (i.e., Model-Based System Architecture Process—"MBSAP") to create an Agile MBSE approach called the integrated Scrum Model-Based System Architecture Process (sMBSAP). The proposed approach was validated through a pilot study that developed a health technology system over one year, successfully producing the desired software product. This work focuses on determining whether the proposed sMBSAP approach can deliver the desired Product Increments with the support of an MBSE process. The interaction of the Product Development Team with the MBSE tool, the generation of the system model, and the delivery of the Product Increments were observed. The preliminary results showed that the proposed approach contributed to achieving the desired system development outcomes and, at the same time, generated complete system architecture artifacts that would not have been developed if Agile had been used alone. Therefore, the main contribution of this research lies in introducing a practical and operational method for merging Agile and MBSE. In parallel, the results suggest that sMBSAP is a middle ground that is more aligned with federal and state regulations, as it addresses the technical debt concerns. Future work will analyze the results of a quasi-experiment on this approach focused on measuring system development performance through common metrics. [ABSTRACT FROM AUTHOR]

This year’s ICCS conference theme promotes the use of computational science as a means to foster multidisciplinarity and synergies with other fields. Our thesis is that this trend towards multidisciplinarity should be accompanied by the use of best practices issued from the software engineering community in order to avoid obtaining overly complex and tangled code, difficult to validate, to maintain and to port. In this paper we argue for the need of applying separation of concerns principles when the development involves scientists from various application fields. We overview several strategies that may be used to achieve this separation, focusing mainly on two approaches drawn from our previous experiences with multidisciplinary projects, addressing two distinct patterns of multi-domain interaction that may occur in scientific software development. [ABSTRACT FROM AUTHOR]

There is an increase use of security driven approaches to support software development activities, such as requirements, design and implementation. The objective of this paper is to identify the existing software security approaches used in the software development lifecycle (SDLC). In order to meet our goal, we conducted a systematic mapping study to identify the primary studies on the use of software security techniques in SDLC. In total, we selected and categorized 118 primary studies. After analyzing the selected studies, we identified 52 security approaches and we categorized them in to five main categories, namely, ‘secure requirements modeling’, ‘vulnerability identification, adaption and mitigation’, ‘software security focused process’, ‘extended UML-based secure modeling profiles’, ‘non UML-based secure modeling notations’. The results show that the most frequently used approaches are static analysis and dynamic analysis that provide security checks in the coding phase. In addition, our results show that many studies in this review considered security checks around the coding stage of software development. This work will assist software development organizations in better understanding the existing software security approaches used in the software development lifecycle. It can also provide researchers with a firm basis on which to develop new software security approaches. [ABSTRACT FROM AUTHOR]

Software is constantly changing. To ensure the quality of this process, when preparing to change a program, developers must first identify the main consequences and risks of modifying the program locations they intend to change. This activity is called change-impact analysis. However, existing impact analysis suffers from two major problems: coarse granularity and large size of the resulting impact sets. Finer-grained analyses such as slicing give more detailed impact sets which, however, are also even larger in size. While various impact-set reduction approaches have been proposed at different levels of granularity, the challenge persists as very-large impact sets are still produced, impeding the adoption of impact analysis due to the great costs of inspecting those impact sets. To address these challenges, we present a novel dynamic-analysis technique called SensA which combines sensitivity analysis and execution differencing. SensA not only provides fine-grained (statement-level) impact sets but also prioritizes potential impacts via semantic-dependence quantification for program slices. We evaluated the benefits of impact prioritization using SensA with respect to static and dynamic forward slicing via an extensive empirical study of open-source Java applications and three case studies. Our results show that SensA can offer much better cost-effectiveness than slicing in assisting developers with impact inspection and fault cause-effect understanding. [ABSTRACT FROM AUTHOR]

This paper documents four years of a novel approach to teaching a two-course sequence in software engineering as part of the ABET-accredited computer science curriculum at the College of Charleston. This approach is team-based and centers on learning software engineering in the context of open source software projects. In the first course, teams develop automated testing frameworks for their chosen free open source software (FOSS) project, and in the second course, team members join and contribute to a selected open source project, documenting the process through regular blog and wiki posts and an oral presentation. Results point to the transformative nature of such coursework on students' perception of software engineering. Discussion focuses on potential future iterations of this capstone model. [ABSTRACT FROM AUTHOR]

Aspect Oriented Software Development is gaining wide attention because of its key feature modularization. Aspect Oriented paradigm supports the separation of concerns that are scattered over the system which helps in achieving modularity. Aspect Oriented Software Development encompasses software engineering abstractions and complexity at new and different dimensions. So Aspect Oriented Software Development requires models to assess its external quality attributes. The quality attribute maintainability is vital, because maintenance tasks employs major chunk of the total software development cost. The quality, maintainability is indicated using metrics. This paper proposes a framework to build maintainability model for aspect oriented systems using already defined software measures. [ABSTRACT FROM AUTHOR]

Process models are well suited to describe in a formal but still intuitive fashion what a system should do. They can thus play a central role in problem-based computational science education with regard to qualifying students for the design and implementation of software applications for their specific needs without putting the focus on the technical part of coding. eXtreme Model Driven Design (XMDD) is a software development paradigm that explicitly focuses on the What (solving problems) rather than on the How (the technical skills of writing code). In this paper we describe how we apply an XMDD-based process modeling and execution framework for scientific workflow projects in the scope of a computer science course for students with a background in natural sciences. [ABSTRACT FROM AUTHOR]

The dynamic planning for a system-of-systems is a challenging endeavor. Department of Defense (DoD) programs constantly face challenges to incorporate new systems and upgrade existing systems over a period of time under threats, constrained budget, and uncertainty. It is therefore necessary for the DoD to be able to look at the future scenarios and critically assess the impact of technology and stakeholder changes. The DoD currently is looking for options that signify affordable acquisition selections and lessen the cycle time for early acquisition and new technology addition. This paper gives an overview of a novel methodology known as the Flexible Intelligent & Learning Architectures in System-of-Systems (FILA-SoS). This approach allows for analyzing sequential decisions in evolving SoS architectures. An ISR SoS example illustrates an application of the method. [ABSTRACT FROM AUTHOR]

In an effort to explore the relationship between the disciplines of systems engineering and software engineering, professionals from academia, industry, and government gathered for a workshop to deliberate on the current state, to acknowledge areas of inter-dependence, to identify relevant challenges, and to propose recommendations for addressing those challenges with respect to four topical areas: 1) Development Approaches, 2) Technical, 3) People, and 4) Education. This paper presents the deliberations and recommendations that emerged from that workshop, and the proposed project to be launched. [ABSTRACT FROM AUTHOR]

Instead of developing each new product from scratch, firms strive to reuse prior components and technologies in new applications in order to improve robustness, reduce cost and shorten time-to-market. Technologies come in the forms of methods, designs and processes, and are suitable for reuse since they are concepts for solving certain problems that multiple products have use for. However, reuse of technology where the application context is different requires adaptation of both the technology and the product system into which it is introduced. In practice, the magnitude and sources for this effect are often underestimated, which leads to unanticipated uncertainty in product development projects with consequences for robustness and efficiency in development. Based on available literature and needs identified within a case company, this paper proposes a method for identifying potential challenges of technology reuse that may otherwise be overlooked or only implicitly acknowledged. The method features a scorecard that guides a workshop to be attended by technology experts and managers where the prospect for successful technology reuse is assessed. [ABSTRACT FROM AUTHOR]

The systems development, procurement and sustainment of a nation's military equipment is vital to its national interests, but the process is complex, constantly changing and highly adaptive, as well as time consuming and costly. The U.S. Department of Defense (DoD) expends both large amounts of capital and manpower to equip its armed forces. This research seeks to identify opportunities to gain better insight into the functioning of the defense acquisition system, building on previous simulations. A case is made that the DoD Requirements, Planning Acquisition, Technology and Logistics System is a complex adaptive system that has characteristics appropriate for exploration with agent-based modeling. This paper reviews relevant literature, existing models and presents preliminary analysis on an agent-based simulation of the DoD acquisition system. This research finds that agent-based modeling can provide insights to inform new acquisition theory. [ABSTRACT FROM AUTHOR]

The intent of this paper is to provide a brief description and critique on each of the 4 pillars of SysML. The description will cover in detail the type of modeling elements used in each pillar, the relationships between these elements, and the views used to represent the model data. The analysis and critique offered will follow the description for each pillar and is primarily from a functional perspective, covering the strengths, weaknesses and identified gaps in the language. In some cases, a recommendation for potential improvement will be provided. Additional modeling gaps that apply across all pillars will also be identified and discussed. Addressing current gaps in SysML would improve our capabilities to accurately represent a system in a modeling format and help better communicate the model to customers in support of a life cycle systems engineering process. [ABSTRACT FROM AUTHOR]

In computer science, functional orbits – i.e., tracks left by the iterations of a function – in a finite domain naturally appear at a high or a low level. This paper introduces a Coq logical orbit framework, the purpose of which is to help rigorously developing software systems with some complex data structures from specification to implementation. The result is a Coq library of orbit concepts formalized as definitions, lemmas and theorems. Most of them are inspired by our previous work in geometric modelling, where combinatorial hypermaps were used to describe surface subdivisions appearing in computational geometry problems, e.g., building convex hulls or Delaunay diagrams. Now, this domain remains a reference for us, but our results are drastically extended and usable in other computer science areas. The proof of Floyd's cycle-detection algorithm, known as “the tortoise and the hare”, confirms that point. The library contains operations to observe, traverse and update orbits – addition, deletion, mutation, transposition – with proofs of their behavior. It focuses on the important case where the involved function is a partial injection. In this case, it defines a connectivity relationship and evaluates the variation of the number of connected components during updates. [ABSTRACT FROM AUTHOR]

Copyright of Mendive - Revista de Educacion is the property of Universidad de Pinar del Rio and its content may not be copied or emailed to multiple sites or posted to a listserv without the copyright holder's express written permission. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)

Sustainable computing is a rapidly growing research topic spanning several areas of Computer Science. Particularly, it has received increasing attention in the Software Engineering field in the last years, with several studies discussing the topic from a range of perspectives. However, few studies have demonstrated the awareness of software practitioners about the underlying concepts of sustainability in the software development practice. In an earlier investigation, we performed a preliminary study on the practitioners' perception under four main perspectives: economic, social, environmental, and technical. This study extended the previous survey and reached a number of ninety-seven respondents from Brazilian companies. The extension aims to expand the results to compare and explore the previous findings in a more in-depth way. The novel results confirmed the evidence raised in the original survey that sustainability in the context of Software Engineering is a new subject for practitioners. However, professionals have shown interest in the topic, and there is a general understanding that sustainability should be treated as a quality attribute. Among the observed perspectives, we generated an initial theory that shows software practitioners know the subject around 'Green in Software', even unconsciously. This study brings evidence of how the industry understands and perceives sustainability practices in the software development process. [ABSTRACT FROM AUTHOR]

Current software engineering efforts typically rely heavily on industrial infrastructure. In a situation of civilizational collapse -- which various researchers have suggested could ensue in the next century via an assortment of environmental, economic, and/or social pathways -- this infrastructure may become less reliable. Previous research has offered some thoughts about what new forms of software may be relevant in the context of collapse. However, those papers did not consider how these new kinds of software would arise. Building on previous work in software engineering for sustainability (SE4S), information and communications technology for development (ICT4D), and collapse informatics, this paper explores how various forms of civilizational collapse would affect the software development process. [ABSTRACT FROM AUTHOR]

Many scientific disciplines rely on computational methods for data analysis, model generation, and prediction. Implementing these methods is often accomplished by researchers with domain expertise but without formal training in software engineering or computer science. This arrangement has led to underappreciation of sustainability and maintainability of scientific software tools developed in academic environments. Some software tools have avoided this fate, including the scientific library Rosetta. We use this software and its community as a case study to show how modern software development can be accomplished successfully, irrespective of subject area. Rosetta is one of the largest software suites for macromolecular modeling, with 3.1 million lines of code and many state-of-the-art applications. Since the mid 1990s, the software has been developed collaboratively by the RosettaCommons, a community of academics from over 60 institutions worldwide with diverse backgrounds including chemistry, biology, physiology, physics, engineering, mathematics, and computer science. Developing this software suite has provided us with more than two decades of experience in how to effectively develop advanced scientific software in a global community with hundreds of contributors. Here we illustrate the functioning of this development community by addressing technical aspects (like version control, testing, and maintenance), community-building strategies, diversity efforts, software dissemination, and user support. We demonstrate how modern computational research can thrive in a distributed collaborative community. The practices described here are independent of subject area and can be readily adopted by other software development communities. [ABSTRACT FROM AUTHOR]

The supply is not matching the demand on the market for software developers. While the enrolment in undergraduate computer science courses is increasing, few students are interested in and committed to becoming software developers. It could be that students are overwhelmed by the software development methodology that they are taught. We are consequently looking for a constructivist approach to software engineering able to effectively engage learners. We empirically evaluated whether test-driven development (TDD) is able to improve the quality of both learning and of software development in the classroom. Although numerous studies have outlined the benefits and effects of TDD in the classroom, none of those studies have focused on measuring students' interest in and attitudes toward using TDD in the classroom. We present a study evaluating the impact of TDD on the engagement and focus of learners of software development in the classroom. The results illustrate that the use of TDD in the classroom encourages learners to engage and focus. [ABSTRACT FROM AUTHOR]

The editorial discusses the complexity and rapid evolution of the field of computer science. It acknowledges that the breadth and depth of knowledge required to fully understand computing make it challenging for one person to grasp. The editorial highlights the theoretical and practical aspects of computing, as well as the continuous learning required to keep up with technological advancements. It also emphasizes the collaborative nature of computing projects and the need for specialization and teamwork. The author expresses gratitude to the experts who have contributed to the journal and wishes the readers a successful 2024. [Extracted from the article]

As gamification literature has matured, the gap between how different domains apply the theory has widened. This has positioned gamification as being more dependent on context, rather than being an independent theory per se. To address this notion, three concepts are identified as being central for how the designer gamifies a process. These are mechanics, psychological mediators and desired outcomes. Following this logic, a review was conducted using 79 (n) articles across seven disciplines, namely health and wellness, crowdsourcing, sustainability, computer science, software development, business, and tourism. The findings highlighted potential relationships between several concepts when gamifying a situation, context, service or/and process. This research presents an alternative and uniform perspective on the broad gamification research to better understand how gamification functions and can be employed to impact various outcomes. Furthermore, this research contributes to this rather eclectic domain, presenting a more categorized view in showing domain-specific mechanics and how these can be employed for empirical testing. Lastly, the conceptual model can be modified, employed and adjusted to investigate various effects of gamification on outcomes. [ABSTRACT FROM AUTHOR]

Software testing is an essential activity in software development projects for delivering high quality products. In a previous study, we reported the results of a survey of software engineering practices in the Costa Rican industry. To make a more in-depth analysis of the specific software testing practices among practitioners, we replicated a previous survey conducted in South America. Our objective was to characterize the state of the practice based on practitioners' use and perceived importance of those practices. This survey evaluated 42 testing practices grouped in three categories: processes, activities, and tools. A total of 92 practitioners responded to the survey. The participants indicated that: (1) tasks for recording the results of tests, documentation of test procedures and cases, and re-execution of tests when the software is modified are useful and important for software testing practitioners. (2) Acceptance and system testing are the two most useful and important testing types. (3) Tools for recording defects and the effort to fix them (bug tracking) and the availability of a test database for reuse are useful and important. Regarding the use and implementation of practices, the participants stated that (4) Planning and designing of software testing before coding and evaluating the quality of test artifacts are not a regular practice. (5) There is a lack of measurement of defect density and test coverage in the industry; and (6) tools for automatic generation of test cases and for estimating testing effort are rarely used. This study gave us a first glance at the state of the practice in software testing in a thriving and very dynamic industry that currently employs most of our computer science professionals. The benefits are twofold: for academia, it provides us with a road map to revise our academic offer, and for practitioners, it provides them with a first set of data to benchmark their practices. [ABSTRACT FROM AUTHOR]

The development of a reliable and efficient software application system requires a competent software architecture which can attune to any design improvement opportunity in the early stages of software architectural design. An Architectural Description Language provides a description of all the component elements and their interactions. The proposed model determines all possible ways of connecting the components and connectors, after eliminating the transitive and symmetric conflicts among the connections, followed by the generation of the software architectural specification. An estimate on the maximum number of architectural specifications generated for a given number of components has been carried out. The syntax for specifying the components and the connectors has been formulated. The model proposed in the current work is generic and it will significantly help a software architect in building reliable, efficient and flexible software architecture, for any valid combination of components and connectors. It has been successfully tested for two prototype applications that involve processing of images and documents. [ABSTRACT FROM AUTHOR]

Investing in documenting your bioinformatics software well can increase its impact and save your time. To maximize the effectiveness of your documentation, we suggest following a few guidelines we propose here. We recommend providing multiple avenues for users to use your research software, including a navigable HTML interface with a quick start, useful help messages with detailed explanation and thorough examples for each feature of your software. By following these guidelines, you can assure that your hard work maximally benefits yourself and others. [ABSTRACT FROM AUTHOR]

Integration of human-centered design in a company's software development practice requires a thorough analysis of its current practices by both researchers and practitioners. [ABSTRACT FROM PUBLISHER]