Analogy-based domain analysis approach to software reuse

Domain analysis is an expansion of conventional requirements analysis. Domain analysis can support effective software reuse. However, domain analysis is time consuming and is limited to a particular application area. Analogical approaches to software reuse, on the other hand, often occur across domains. Analogical problem solving is a process of transferring knowledge from a well-understood base domain to a new target problem area. Analogy can facilitate software reuse for poorly understood problems or new application areas. Analogy shares similar concepts with reuse and some analogy theories have been applied to software reuse. However, current research on software analogy often overlooks the importance of analysis for the base domain and does not consider some critical aspects of analogy concepts. Reuse must be based on high quality artifacts, especially reuse across domains. This paper presents an approach to integrate domain analysis and analogy methods. In our view, domain analysis and software analogy have complementary roles. Domain analysis is regarded as a process to identify and supply necessary information for analogical transfer. Software analogy can provide the analyst with similar problems and solutions to reuse previous domain analysis knowledge or artifacts for a new domain. This paper presents case studies to demonstrate the increase of efficiency in applying the approach. Evaluation of the approach from various perspectives is also reported.     

An empirical investigation on factors affecting the acceptance of CASE by systems developers

This paper presents the findings of an empirical study of factors affecting the acceptance of CASE by systems developers. Based on two research models (technology acceptance and personal computer utilization) recently published in IS literature, an integrated model which consists of six variables and incorporates key elements of both models was developed to examine determinants of CASE acceptance. The findings indicate that ease of use has the largest influence on CASE acceptance, followed by long-term consequences. Both transitional support and near-term usefulness do not have a significant direct effect on the acceptance but exhibit their indirect influence through ease of use and/or long-term consequences. The implementation gap was found to have a relatively small and negative effect on CASE acceptance through its influence on ease of use, near-term usefulness, and long-term consequences. Implications of the findings, from both a research and a managerial perspective are discussed in this paper.     

An empirical analysis of the impact of software development problem factors on software maintainability

Many problem factors in the software development phase affect the maintainability of the delivered software systems. Therefore, understanding software development problem factors can help in not only reducing the incidence of project failure but can also ensure software maintainability. This study focuses on those software development problem factors which may possibly affect software maintainability. Twenty-five problem factors were classified into five dimensions; a questionnaire was designed and 137 software projects were surveyed. A K-means cluster analysis was performed to classify the projects into three groups of low, medium and high maintainability projects. For projects which had a higher level of severity of problem factors, the influence on software maintainability becomes more obvious. The influence of software process improvement (SPI) on project problems and the associated software maintainability was also examined in this study. Results suggest that SPI can help reduce the level of severity of the documentation quality and process management problems, and is only likely to enhance software maintainability to a medium level. Finally, the top 10 list of higher-severity software development problem factors was identified, and implications were discussed.     

Determinants of users’ intention to adopt wireless technology: An empirical study by integrating TTF with TAM

This paper reported the results of a survey study and provided evidences of empirically testing a model that integrates both technology acceptance model (TAM) and task-technology fit (TTF) model in understanding the determinants of users’ intention to use wireless technology in organizations. Questionnaires were distributed to organizations that bring mobile commerce into practice through the wireless handheld devices. The results indicated that both technology acceptance model and task-technology fit model are robust models by themselves. First, both perceived usefulness and ease of use significantly influence users’ behavior intention to utilize wireless technology. Perceived ease of use has significant effect on perceived usefulness. Second, characteristics of technology and task significantly predict the fit between these two constructs. Significant effect of characteristics of technology on perceived ease of use and usefulness were observed. Finally, significant relationships between TAM and TTF model were also observed. Task-technology fit is a significant direct predictor of technology adoption intention. Overall, users’ intention to adopt wireless technology in organizations was determined directly by fit between characteristics of task and technology as well as users’ perceived ease of use and usefulness.     

An empirical analysis of open source software developers’ motivations and continuance intentions

We investigated open source software (OSS) developers’ intentions to continue their involvement in future projects. The research goal was to analyze the motivations of OSS developers systematically and identify those factors that influenced their continuation. A work motivation model for OSS developers was proposed and a research model was empirically validated using data from a field survey of 148 OSS participants. The results showed that OSS developers’ feelings of satisfaction and their intentions to continue with OSS development was influenced by both helping behavior and economic incentives and also that adequate motivators existed, though OSS developers did not benefit equally and there was substantial room to improve their experiences as OSS developers.     

Effects of interface style on user perceptions and behavioral intention to use computer systems

This study examines the influence of two interface styles (menu- and command-based) on the perceived ease of use, perceived usefulness, and behavioral intention of the user to use the system. We have treated the system interface style as an external factor in the technology acceptance model (TAM) to examine its direct and indirect effects on behavioral intention to accept and use a system. The results showed that the interface style had direct effects on perceived ease of use and perceived usefulness which, in turn, demonstrated significant effects on behavioral intention to use the system. Further, the results showed that perceptions of the menu-based interface were more favorable than perceptions of the command-based interface. These results provide several theoretical and practical implications for designing an effective system.     

A study of software reuse in NASA legacy systems

Software reuse is regarded as a highly important factor in reducing development overheads for new software projects; however, much of the literature is concerned with cost and labor savings that reuse brings to industrial software development and little is known about the inherent risks associated with reuse, particularly in the case of mission and safety-critical software systems. We present the preliminary findings of a research project geared toward assessing the impact of risk in National Aeronautics and Space Administration (NASA) legacy software in flight control systems. We introduce the concept of context variables and the impact they have on reuse within these legacy systems as well as the genealogy classification models, which provide a simple, concise method of mapping reuse between families of software projects. This research was conducted at Global Science and Technology, Inc. under NASA grant number NCC0NNG06GI57G.     

The effect of positive mood on intention to use computerized decision aids

While psychology research has indicated that positive mood enhances cognition and behavior, MIS researchers have largely ignored such potential effects on user acceptance of new IT. Using two cognitive theories on mood and memory, positive mood theory and the affect infusion model (AIM), we developed hypotheses about the contribution of these mood conditions on user acceptance of new IT with two levels of uncertainty. These hypotheses were investigated via an experiment using a computerized decision making aid. We found that positive mood increased acceptance, under both levels of uncertainty. These results held for both induced and naturally occurring positive mood. The results were consistent with positive mood theory but not with the AIM.     

一种软件生产过程的复用技术模型研究

体系结构设计在软件开发整个过程中扮演着重要角色。软件复用是提高软件开发效率和改善软件质量的一项重要技术。基于上述原因,提出了软件开发过程的复用技术模型。     

An empirical analysis of software life spans to determine the planning horizon for new software

This paper presents an empirical analysis of the life span of over 180 systems aimed at developing a model for determining the planning horizon for new software at the business case stage of software acquisition. At this early stage, the firm has limited knowledge about the project, but must make crucial decisions, such as scope (breadth of requirements), approach (both insource vs. outsource and custom vs. package) and technology, including fit with standards (adhere to current vs. adopt new technology). These decisions are associated with different system lifetimes that, in turn, impact both the costs incurred and benefits received from the system. The failure to explicitly and properly address these differences can lead to the implementation of systems better left undone or to unintended consequences, such as the Y2K problem. We find that technology and approach, but not scope decisions are strongly related to system lifetime. In particular, systems that use an operating system that conforms to the firm’s standard or are acquired using a blended team entail longer system life. On the other hand, shorter system life is indicated if the system is technically complex, custom developed or uses an older programming language. Furthermore, modified packaged software is shorter lived than is a vanilla package. In addition, environmental variables also impact the appropriate horizon. For example, as one would expect, strategic systems are used longer. On the other hand, somewhat surprisingly, systems sponsored by executives last less long and despite the quickening pace of technological and business process advancement, a small trend toward longer lived systems is uncovered.     

An empirical study of FOSS developers patterns of contribution: Challenges for data linkage and analysis

The majority of Free and Open Source Software (FOSS) developers are mobile and often use different identities in the projects or communities they participate in. These characteristics pose challenges for researchers studying the presence and contributions of developers across multiple repositories. In this paper, we present a methodology, employ various statistical measures, and leverage Bayesian networks to study the patterns of contribution of 502 developers in both Version Control System (VCS) and mailing list repositories in 20 GNOME projects. Our findings shows that only a small percentage of developers are contributing to both repositories and this cohort is making more commits than they are posting messages to mailing lists. The implications of these findings for understanding the patterns of contribution in FOSS projects and on the quality of the final product are discussed.     

The adoption of software measures: A technology acceptance model (TAM) perspective

The use of software measures for project management and software process improvement has been encouraged for many years. However, the low level of acceptance and use of software measures in practice has been a constant concern. In this paper we propose and test a model which explains and predicts the use of software measures. The model is based on the technology acceptance model (TAM) and operationalizes the perceived usefulness construct according to the “desirable properties of software measures.” Our research provides guidance for software engineers in selecting among different software measures and for software metrics coordinators who are planning measurement programs.     

Mining significant factors affecting the adoption of SaaS using the rough set approach

Despite that Software as a Service (SaaS) seems to be the most tempting solution among different types of cloud services, yet it has not been adopted to-date with as much alacrity as was originally expected. A variety of factors may influence the adoption of SaaS solutions. The objective of this study is thus to explore the significant factors affecting the adoption of SaaS for vendors and enterprise users. An analytical framework is proposed containing two approaches—Technology Acceptance Model (TAM) and Rough Set Theory (RST). An empirical study on the IT/MIS enterprises in Taiwan is carried out. The results have revealed a considerable amount of meaningful information, which not only facilitates the SaaS vendors to grasp users’ needs and concerns about SaaS adoption, but also helps the managers to introduce effective marketing strategies and actions to promote the growth of SaaS market. Based on the findings, some managerial implications are discussed.     

Quality,productivity and economic benefits of software reuse: a review of industrial studies

Systematic software reuse is proposed to increase productivity and software quality and lead to economic benefits. Reports of successful software reuse programs in industry have been published. However, there has been little effort to organize the evidence systematically and appraise it. This review aims to assess the effects of software reuse in industrial contexts. Journals and major conferences between 1994 and 2005 were searched to find observational studies and experiments conducted in industry, returning eleven papers of observational type. Systematic software reuse is significantly related to lower problem (defect, fault or error) density in five studies and to decreased effort spent on correcting problems in three studies. The review found evidence for significant gains in apparent productivity in three studies. Other significant benefits of software reuse were reported in single studies or the results were inconsistent. Evidence from industry is sparse and combining results was done by vote-counting. Researchers should pay more attention to using comparable metrics, performing longitudinal studies, and explaining the results and impact on industry. For industry, evaluating reuse of COTS or OSS components, integrating reuse activities in software processes, better data collection and evaluating return on investment are major challenges.

On the use of software design models in software development practice: An empirical investigation

Research into software design models in general, and into the UML in particular, focuses on answering the question how design models are used, completely ignoring the question if they are used. There is an assumption in the literature that the UML is the de facto standard, and that use of design models has had a profound and substantial effect on how software is designed by virtue of models giving the ability to do model-checking, code generation, or automated test generation. However for this assumption to be true, there has to be significant use of design models in practice by developers.This paper presents the results of a survey summarizing the answers of 3785 developers answering the simple question on the extent to which design models are used before coding. We relate their use of models with (i) total years of programming experience, (ii) open or closed development, (iii) educational level, (iv) programming language used, and (v) development type.The answer to our question was that design models are not used very extensively in industry, and where they are used, the use is informal and without tool support, and the notation is often not UML. The use of models decreased with an increase in experience and increased with higher level of qualification. Overall we found that models are used primarily as a communication and collaboration mechanism where there is a need to solve problems and/or get a joint understanding of the overall design in a group. We also conclude that models are seldom updated after initially created and are usually drawn on a whiteboard or on paper.     

An empirical, path-oriented approach to software analysis and testing

Error flow analysis and testing techniques focus on the introduction of errors through code faults into data states of an executing program, and their subsequent cancellation or propagation to output. The goals and limitations of several error flow techniques are discussed, including mutation analysis, fault-based testing, PIE analysis, and dynamic impact analysis. The attributes desired of a good error flow technique are proposed, and a model called dynamic error flow analysis (DEFA) is described that embodies many of these attributes. A testing strategy is proposed that uses DEFA information to select an optimal set of test paths and to quantify the results of successful testing. An experiment is presented that illustrates this testing strategy. In this experiment, the proposed testing strategy outperforms mutation testing in catching arbitrary data state errors.     

Selection of third party software in Off-The-Shelf-based software development—An interview study with industrial practitioners

The success of software development using third party components highly depends on the ability to select a suitable component for the intended application. The evidence shows that there is limited knowledge about current industrial OTS selection practices. As a result, there is often a gap between theory and practice, and the proposed methods for supporting selection are rarely adopted in the industrial practice. This paper's goal is to investigate the actual industrial practice of component selection in order to provide an initial empirical basis that allows the reconciliation of research and industrial endeavors. The study consisted of semi-structured interviews with 23 employees from 20 different software-intensive companies that mostly develop web information system applications. It provides qualitative information that help to further understand these practices, and emphasize some aspects that have been overlooked by researchers. For instance, although the literature claims that component repositories are important for locating reusable components; these are hardly used in industrial practice. Instead, other resources that have not received considerable attention are used with this aim. Practices and potential market niches for software-intensive companies have been also identified. The results are valuable from both the research and the industrial perspectives as they provide a basis for formulating well-substantiated hypotheses and more effective improvement strategies.     

An empirical investigation of end-users’ switching toward cloud computing: A two factor theory perspective

With the diffusion of cloud services, they are becoming an alternative to traditional information technology (IT). Despite the importance of cloud services, relatively few studies have been devoted to an empirical examination of the switching behavior from traditional IT to cloud services at the individual level. Therefore, this study attempts to explore the switching factors (i.e. switching enablers and switching inhibitors) and to empirically examine the relationships between those and users’ intention to switch to cloud services, based on the two-factor theoretic perspective. This study uses a longitudinal design to get survey data from undergraduate students at two universities in Korea in the context of IT switching to Google Apps settings. According to our findings, this study found that users’ switching intention to cloud services was not only positively influenced by expected switching benefits whose antecedents are omnipresence of cloud services and collaboration support, but also negatively influenced by expected switching costs whose antecedents are satisfaction with incumbent IT and breath use of inclement IT. The impacts of switching benefits and costs on switching intention were also positively moderated by end users’ personal innovativeness.