The use of mobile applications continues to experience exponential growth. Using mobile apps typically requires the disclosure of location data, which often accompanies requests for various other forms of private information. Existing research on information privacy has implied that consumers are willing to accept privacy risks for relatively negligible benefits, and the offerings of mobile apps based on location-based services (LBS) appear to be no different. However, until now, researchers have struggled to replicate realistic privacy risks within experimental methodologies designed to manipulate independent variables. Moreover, minimal research has successfully captured actual information disclosure over mobile devices based on realistic risk perceptions. The purpose of this study is to propose and test a more realistic experimental methodology designed to replicate real perceptions of privacy risk and capture the effects of actual information disclosure decisions. As with prior research, this study employs a theoretical lens based on privacy calculus. However, we draw more detailed and valid conclusions due to our use of improved methodological rigor. We report the results of a controlled experiment involving consumers (n=1025) in a range of ages, levels of education, and employment experience. Based on our methodology, we find that only a weak, albeit significant, relationship exists between information disclosure intentions and actual disclosure. In addition, this relationship is heavily moderated by the consumer practice of disclosing false data. We conclude by discussing the contributions of our methodology and the possibilities for extending it for additional mobile privacy research.

When features are added to an existing IS product in response to market demands it is important to assess their business value before implementing them into the product. But how does one estimate the true value of a new feature? Is it sufficient to consider only the customer reward for including a feature into the product or is it also useful to evaluate the customer penalty for not building the feature into the product? The current methods for feature selection capture only the customer inputs for building a feature into the product. The implications of not building the feature are not captured. This study investigates the adequacy of such an approach and discovers that additional business information can be derived by considering both, the reward as well as the penalty perspective of the customer. This information can be utilized by IS developers in adopting the right strategy for product enhancement.

Social traps are situations within which individuals or groups face the prospect of adopting seemingly beneficial behaviors that have negative consequences over time or for a larger collective (Platt, 1973). While on the one hand, the Agile manifesto has been welcomed by many in the software developer community who often perceived formal processes as management generated inefficiency that gets in the way of productivity (Anderson, 2005). On the other hand proponents of formal plan-driven approaches argue that in spite of the lofty ideals and claims made, Agile development only postpone costs for the developing organization. Following the threads of this debate through a review of extant literature this conceptual study suggests that there is a real risk of developers using Agile methods falling into social trap' of compromising the longterm goals for short-term gains.

Information systems portfolio management assumes that software will evolve to maintain alignment with operational needs, a goal that must be met through effective ongoing maintenance. Thus, a primary goal of software maintainers is to ensure that production code is updated without the introduction of defects. However, there is a dearth of research that examines the work product defects that occur as these applications evolve. The goal of this study is to characterize software evolution lifecycle work product defects and factors that may increase or reduce their occurrence. The study takes place within a global consulting organization conducting ongoing software maintenance for a Fortune 100 telecommunications firm by a project team assessed at Capability Maturity Model Integration (CMMI) Level 3. This study reports on 991 work product reviews conducted across the evolution activities of the ISO/IEC 12207 Software Development Life Cycle Processes. After controlling for team and expertise differences, the study's major finding is that corrective evolution projects inject a greater number of work product defects than enhancive evolution projects. This result does not arise from the schedule compression often associated with corrective evolution. Rather, it is concluded that the increase in work product defects is associated with the increased complexity of analysis-stage problem diagnosis found in corrective evolution projects. The analysis is augmented by additional covariates including the number of work product reviewers, preparation time of reviewers, and size of the project.

This study examines temporal patterns of software systems defects using the Autoregressive Integrated Moving Average (ARIMA) approach. Defect reports from ten software application projects are analyzed; five of these projects are open source and five are closed source from two software vendors. Across all sampled projects, the ARIMA time series modeling technique provides accurate estimates of reported defects during software maintenance, with organizationally dependent parameterization. In contrast to causal models that require extraction of source-code level metrics, this approach is based on readily available defect report data and is less computation intensive. This approach can be used to improve software maintenance and evolution resource allocation decisions and to identify outlier projects—that is, to provide evidence of unexpected defect reporting patterns that may indicate troubled projects.

The theories of social exchange, task-technology fit, and technology acceptance are utilized in a field study of software development methodologies. This investigation includes the effects of user experiences on perceptions of acceptance and usage of a methodology. More specifically, perceptions of the outputs and deliverables from a methodology and perceptions of challenges and obstacles to using and applying a methodology were found to significantly and positively influence perceived usefulness and negatively influence ease of use of a methodology, respectively, within a developer’s organization. Perceived usefulness was a positive and strong antecedent to perceptions of fit between the methodology and client problems, and the strengthening of efficacy beliefs about the methodology.

research-article Share on Reflections today prevent failures tomorrow Authors: Gary W. Brock United States Army United States ArmyView Profile , Denise J. McManus University of Alabama, AL University of Alabama, ALView Profile , Joanne E. Hale University of Alabama, AL University of Alabama, ALView Profile Authors Info & Claims Communications of the ACMVolume 52Issue 5May 2009 pp 140–144https://doi.org/10.1145/1506409.1506443Published:01 May 2009Publication History 6citation708DownloadsMetricsTotal Citations6Total Downloads708Last 12 Months30Last 6 weeks5 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my Alerts New Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access

research-article Share on Software project scope alignment: an outcome-based approach Authors: Richard W. Woolridge University of Alabama, Alabama University of Alabama, AlabamaView Profile , David P. Hale University of Alabama, Alabama University of Alabama, AlabamaView Profile , Joanne E. Hale University of Alabama, Alabama University of Alabama, AlabamaView Profile , R. Shane Sharpe University of Alabama, Alabama University of Alabama, AlabamaView Profile Authors Info & Claims Communications of the ACMVolume 52Issue 7July 2009 pp 147–152https://doi.org/10.1145/1538788.1538822Online:01 July 2009Publication History 5citation1,308DownloadsMetricsTotal Citations5Total Downloads1,308Last 12 Months130Last 6 weeks16 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my Alerts New Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteGet Access

The Department of Information Systems, Statistics and Management Science, prediction of software defects and defect patterns is and will continue to be a critically important software evolution research topic. This study presents a time series analysis of multi-organizational multi-project defects reported during ongoing software evolution efforts. Using data from monthly defect reports for eight open source software projects over five years, this study builds and tests time series models for each sampled project. The resulting model accounts for the ripple effects of defect detection and correction by modeling the autocorrelation of code defect data. The autoregressive integrated moving average model (0,1,1) was found to hold for all sampled projects and thus provide a basis for both descriptive and predictive software defect analysis that is computationally efficient, comprehensible, and easy to apply. The model may be used to evaluate and compare the reliability of candidate software solutions, and to facilitate planning for software evolution budget and time allocation. Copyright © 2008 John Wiley & Sons, Ltd.

Those charged with implementing information technology often face the daunting task of assessing the total organizational costs of such initiatives. Our study posits evaluating such expenditures as IT transition costs – organizational resource expenditures stemming from a positive IT investment decision. A content analytic review of academic, ITrelated articles yielded 57 cases germane to the construct. Data produced a meaningful and comprehensive taxonomy that distinguished IT transition costs by two dimensions: goal (prescriptive, evaluative, adaptive, corrective) and target (human, structure, process, technology). The significance of the taxonomy as a useful guide to both practitioners and future research is discussed.

Enterprise architecture enables strategic alignment through creation of a unified business and IS view of the target state of the business. Using a design science approach, this paper proposes an intent-based technique as an extension to existing modeling techniques for strategic alignment. The proposed approach defines a reference architecture of enterprise intent that includes vocabulary, rules, and structure for development of purposefully aligned strategic-level enterprise architecture. The proposed approach results in interacting hierarchies that can be analyzed through network science approaches.

Managing software projects can often degrade into fighting fires lit by the embers of unrecognized and unmanaged risks. Stakeholders are a recognized source of significant software project risk, but few researchers have focused on providing a practical method for identifying specific project stakeholders. Furthermore, no methods provide guidance in identifying and managing project risks arising from those stakeholders. We developed the outcome-based stakeholder risk assessment model to provide this practical guidance. OBSRAM offers the project team a step-by-step approach to identifying stakeholders during requirements engineering, identifying stakeholder influences on the project, identifying the project's impact on stakeholders, and assessing the risks that their potential negative responses pose. We illustrate OBSRAM using a case study of a simulated airline-crew-scheduling system project that aims to reduce aircraft ground turnaround time to 30 minutes or less