Software engineering (3rd ed.): a practitioner's approach
Software engineering (3rd ed.): a practitioner's approach
Elements of a realistic CASE tool adoption budget
Communications of the ACM
Software Engineering Journal - Special issue on software process and its support
Total Quality Management for Software
Total Quality Management for Software
Assessing the State of Tools Assessment
IEEE Software
Capability Maturity Model, Version 1.1
IEEE Software
CASCON '95 Proceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research
A quantitative approach for analyzing the impact of tools on software productivity
A quantitative approach for analyzing the impact of tools on software productivity
Using version control data to evaluate the impact of software tools
Proceedings of the 21st international conference on Software engineering
Empirical Software Engineering
IEEE Transactions on Software Engineering
Risk analysis in software development
AIC'08 Proceedings of the 8th conference on Applied informatics and communications
Product Line Tools are Product Lines Too: Lessons Learned from Developing a Tool Suite
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Automatic mining of change set size information from repository for precise productivity estimation
Proceedings of the 2011 International Conference on Software and Systems Process
ICWE'12 Proceedings of the 12th international conference on Web Engineering
| Hi-index | 0.00 |
To stay competitive, software organizations must continuously improve product quality and customer satisfaction, as well as lower software development costs and shorten delivery time. One way to do this is to adopt appropriate software tools. However, to make effective use of specific tools you should first understand how a tool will affect these critical variables in your project. Because we don't know how to analyze a tool's impact on specific projects, we generally adopt them based on an intuitive understanding of their expected impact. In many cases, the actual results of this practice are disappointing. The problem is aggravated because tool adoption often brings considerable costs. The authors did a case study on the impact of tool insertion in ongoing software projects. The result of their study was a method that organizations can use to assess the impact of tool insertion on software productivity.