Article

Free access

The impact of inserting a tool into a software process

Author:

Tilmann BruckhausAuthors Info & Claims

CASCON '93: Proceedings of the 1993 conference of the Centre for Advanced Studies on Collaborative research: software engineering - Volume 1

Pages 250 - 264

Published: 24 October 1993 Publication History

Abstract

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.

References

[1]

V. R. Basili and H. D. Rombach. Tailoring the software process to project goals and environments. In Proc. 9th Int. Conf. on Soft. Eng., pages 345--357, Monterey, California, April 1987. IEEE Computer Society Press.]]

Digital Library

[2]

V. R. Basili and D. M. Weiss. A methodology for collecting valid software engineering data. IEEE Transactions on Software Engineering, SE-10(3):728--738, 1984.]]

Digital Library

[3]

J. E. Botsford, G. Caldiera, G. E. Kaiser, M. I. Kellner, and N. H. Madhavji. The 1992 report on the Process Reuse Study (PRS) in CAS. Technical Report TR 74.106, IBM Canada Ltd. Laboratory, November 1992.]]

[4]

Information Development. Understanding IBM AIX Configuration Management Version Control/6000 Concepts. Number SC09-1433-00. IBM Canada Ltd. Laboratory, North York, Ontario, 1992.]]

[5]

A. Fugetta, R. Conradi, and V. Ambriola, editors. Proc. First European Workshop on Software Process Modelling, Milan, Italy, May 1991. CEFRIEL, Milan.]]

[6]

D. Harel, H. Lachover, A. Naamad, A. Pnueli, M. Politi, R. Sherman, A. Shtull-Tauring, and M. Trakhten-brot. Statemate: A working environment for the development of complex reactive systems. IEEE Transactions on Software Engineering, SE-16(4):403--414, April 1990.]]

Digital Library

[7]

D. Hoeltje. Building Software Process Models Using the Elicit Meta Process: A Case Study. Master's Thesis, Fern Universität Hagen, Germany, June 1993.]]

[8]

Proc. of 1st Int. Conf. on the Software Process, Redondo Beach, CA., Oct. 1991. IEEE Computer Society Press.]]

[9]

Proc. of 2nd Int. Conf. on the Software Process, Berlin, Germany, February 1993. IEEE Computer Society Press.]]

[10]

International Organization for Standardization. International Standard - ISO 9000, 1987-03-15 first edition, 1987.]]

[11]

Proc. 7th Int. Software Process Workshop, Yountville, CA, October 1991. ACM Press.]]

[12]

Proc. 8th Int. Software Process Workshop (to appear), Schloss Dagstuhl, Germany, March 1993. ACM Press.]]

[13]

IEEE International Symposium On Requirements Engineering, San Diego, CA, January 1993. IEEE Computer Society Press.]]

[14]

Proc. Int. Workshop on Experimental Software Engineering Issues (to appear), Dagstuhl Castle, Germany, September 1992. Springer Verlag.]]

[15]

M. Kellner. Modeling software maintenance processes. Confererence on Software Maintenance 1989, pages 93--94, Oct. 1989.]]

[16]

M. Kellner. Software process modelling support for management planning and control. In Proc. of 1st Int. Conf. on the Software Process, pages 8--28, Redondo Beach, CA., Oct. 1991. IEEE Computer Society Press.]]

[17]

M. I. Kellner. Supporting software process through software process modelling. In Proc. 6th Int. Workshop on the Software Process, ACM SIGSOFT, Hako-date, Japan, October 1990. ACM Press.]]

[18]

N. H. Madhavji, W. Hong, T. Bruckhaus, and J. E. Botsford. Elicit: A meta process and supporting tool for eliciting software process models. Technical Report SE-92.4, McGill University, Software Engineering Group, September 1992.]]

[19]

N. H. Madhavji, K. Toubache, and W. K. Hong. A framework for process maintenance. In Proc. of Conference on Software Maintenance, Orlando, Florida, November 1992.]]

[20]

N. H. Madhavji and W. Schäfer (eds.). Special issue on software process and its support. IEE/BCS Software Engineering Journal, 6(5), September 1991.]]

Digital Library

[21]

N. H. Madhavji, J. E. Botsford, T. Bruck-haus, and K. El Emam. Process-model-based process measurements. In V. R. Basili, H. D. Rombach, and R. Selby, editors, Proc. Workshop on Experimental Soft. Eng. Issues (to appear), Dagstuhl, Germany, Sept., 1992. Springer-Verlag.]]

[22]

B. Nejmeh. Strategic software process improvement planning. Technical Report Ref. No. 7-46-1, Software Design & Analysis Inc, March 91., 1991.]]

[23]

D. E. Perry, editor. Experience with software process models, Kennebunkport, Maine, USA, October 1989. ACM Press.]]

Digital Library

[24]

S. Pfleeger. Lessons learned in building a corporate metrics program. IEEE Software, 10(3):67--74, May 1993.]]

Digital Library

[25]

Douglas T. Ross. Structured analysis (SA): A language for communicating ideas. IEEE Transactions on Software Engineering, SE-3(1):16--34, January 1977.]]

Digital Library

[26]

Conference on Transferring software engineering tool technology, Piscataway, NJ, November 1987. Available from IEEE Service Cent (cat n 88TH0218-8).]]

Cited By

Wen LColvin RLin KSeagrott JYatapanage NDromey G(2007)"integrare", a collaborative environment for behavior-oriented designProceedings of the 4th international conference on Cooperative design, visualization, and engineering10.5555/1776926.1776940(122-131)Online publication date: 16-Sep-2007
https://dl.acm.org/doi/10.5555/1776926.1776940
Bruckhaus TBockus D(1995)Analyzing CASE impactProceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research10.5555/781915.781925Online publication date: 7-Nov-1995
https://dl.acm.org/doi/10.5555/781915.781925
Bruckhaus T(1994)TIMProceedings of the 1994 conference of the Centre for Advanced Studies on Collaborative research10.5555/782185.782192Online publication date: 31-Oct-1994
https://dl.acm.org/doi/10.5555/782185.782192

Recommendations

Change Impact Analysis of a Software Process Using Process Slicing
QSIC '09: Proceedings of the 2009 Ninth International Conference on Quality Software

A software process needs to be changed for various reasons during or before its enactment. To accommodate the change in the software process, it is necessary to analyze the impacts of the change. Few researches provide the methods to structurally analyze ...
Impact analysis in the software change process: a year 2000 perspective
ICSM '96: Proceedings of the 1996 International Conference on Software Maintenance

Software change impact analysis has gained considerable attention with recent challenges of the Year 2000 Date situation. As the software community recognizes the growing need to identify consequences of these changes, impact analysis is making its way ...
The Process Enactment Tool Framework-Transformation of software process models to prepare enactment

Rich development process models contain information about structures for project organization and also for concrete outcomes of a project. However, rich processes are hard to implement. They often contain hundreds of pages of documentation. Development ...

Comments

Information & Contributors

Information

Published In

cover image DL Hosted proceedings

CASCON '93: Proceedings of the 1993 conference of the Centre for Advanced Studies on Collaborative research: software engineering - Volume 1

October 1993

12 pages

Editors:
Ann Gawman
IBM Toronto Laboratory
,
Evelyn Kidd
National Research Council
,
Per-Åke Larson
University of Waterloo
,
Program Chairs:
Jacob Slonim
IBM Centre for Advanced Studies
,
W. Morven Gentleman
NRC Software Engineering Laboratory

Sponsors

IBM Centre for Advanced Studies (CAS)
NRC: National Research Council - Canada

Publisher

IBM Press

Publication History

Published: 24 October 1993

Qualifiers

Article

Acceptance Rates

Overall Acceptance Rate 24 of 90 submissions, 27%

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

3
Total Citations
View Citations
401
Total Downloads

Downloads (Last 12 months)17
Downloads (Last 6 weeks)7

Reflects downloads up to 05 Mar 2025

Other Metrics

View Author Metrics

Citations

Cited By

Wen LColvin RLin KSeagrott JYatapanage NDromey G(2007)"integrare", a collaborative environment for behavior-oriented designProceedings of the 4th international conference on Cooperative design, visualization, and engineering10.5555/1776926.1776940(122-131)Online publication date: 16-Sep-2007
https://dl.acm.org/doi/10.5555/1776926.1776940
Bruckhaus TBockus D(1995)Analyzing CASE impactProceedings of the 1995 conference of the Centre for Advanced Studies on Collaborative research10.5555/781915.781925Online publication date: 7-Nov-1995
https://dl.acm.org/doi/10.5555/781915.781925
Bruckhaus T(1994)TIMProceedings of the 1994 conference of the Centre for Advanced Studies on Collaborative research10.5555/782185.782192Online publication date: 31-Oct-1994
https://dl.acm.org/doi/10.5555/782185.782192

View Options

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

Figures

Tables

Media

View Table of Conten