Tailoring the software process to project goals and environments
ICSE '87 Proceedings of the 9th international conference on Software Engineering
STATEMATE: A Working Environment for the Development of Complex Reactive Systems
IEEE Transactions on Software Engineering
5th ISPW 5th Intl Software Process Workshop
Lessons Learned in Building a Corporate Metrics Program
IEEE Software
Emerging technologies that support a software process life cycle
IBM Systems Journal
CASCON '95 Proceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research
"integrare", a collaborative environment for behavior-oriented design
CDVE'07 Proceedings of the 4th international conference on Cooperative design, visualization, and engineering
| Hi-index | 0.00 |
The development of software systems can largely be facilitated by making use of software tools ranging from editors and compilers to integrated software engineering environments. The process of inserting a tool into a process involves numerous activities that are carried out more or less consciously by the project's decision maker. Some such activities are: determining areas for process improvement, designing how the tool is to be used, quantifying the expected benefit of inserting the tool, and monitoring the impact of inserting the tool. Omissions and misjudgements in this process can be costly. Often, considerable amounts of money are invested in acquisition of a tool, training of software developers, providing interfaces to other tools, and the like. A good understanding of the impact of inserting tools into processes is necessary to minimize the risk of such investments. This paper proposes a Method for Planned Tool Insertion (MPTI) that emphasizes techniques for understanding the impact of tool insertion. It describes the MPTI method in general and how MPTI is being applied, as well as lessons learned from using the MPTI method.