Towards a computer-aided process engineering environment
Pages 499 - 512
Abstract
This paper reports on issues in software process reuse and Computer-Aided Process Engineering (CAPE). The views described in this paper are a first outcome of the Process Reuse Study (PRS). PRS is an ongoing project involving four universities and one industrial partner that investigates opportunities of and approaches to process reuse.In this paper, is a framework for Computer Aided Process Engineering. Services that support efficient process engineering are defined. This definition is an outline of requirements for a CAPE environment. It is described how CAPE services can be used to practice process reuse. Subsequently, a scale is proposed to measure the explicitness of process and project context descriptions, and is followed by a scale to measure the conformance of process description and context description to the enacted process and actual context.The setting of PRS is briefly described. The current status of process and context descriptions is described by applying the scale of explicitness. The current conformance of descriptions to enacted process and actual context is described by applying the scale of conformance. The goal of PRS is formulated by phrasing it as an effort to move from one level of a scale to another.
References
[1]
V. Ambriola, P. Ciancarini, and C. Montangero. Software process enactment in oikos. In Proceedings of the Fourth ACM SIGSOFT/SIGPLAN Software Engineering Symposium on Practical Software Development Environments, Irvine, CA, 1990.
[2]
R. Balzer, T. E. Cheatham, and C. Green. Software technology in the 1990s: Using a new paradigm. IEEE Computer, November 1983.
[3]
B. W. Boehm. A spiral model of software development and enhancement. IEEE Computer, May 1988.
[4]
J. F. Brooks. No silver bullet. IEEE Computer, 19(4), April 1987.
[5]
B. Curtis, H. Krasner, and N. Iscoe. A field study of the software design process for large systems. Communications of the ACM, 31(11), November 1988.
[6]
Jack Dawson. Toronto laboratory requirements process. Technical Report (IBM Internal Use Only), IBM Canada Lab, Toronto, ON, September 1991.
[7]
P. H. Feiler and W. Humphrey. Software process development and enactment: Concepts and definitions. Technical report, Software Engineering Institute, CMU, Pittsburgh, PA, Dec. 1991.
[8]
G. F. Hoffnagle and W. E. Beregi. Automating the software development process. IBM Systems Journal, 24(2), 1985.
[9]
W. S. Humphrey, D. Kitson, and J. Gale. A comparison of u.s. and japanese software process maturity. Proc. 13th Int. Conf. on. Soft. Eng., May 1991.
[10]
S. Sutton Jr., D. Heimbigner, and L. J. Osterweil. Language constructs for managing change in process-centred environments. Proc. of the fourth ACM SIGSOFT Symposium on Software Development Environments, ACM Software Engineering Notes, 15(6), December 1990.
[11]
G. E. Kaiser. Experience with marvel. Proc. 5th Int. Workshop on the Software Process, ACM SIGSOFT, October 1989.
[12]
M. I. Kellner. Software process modelling: Value and experience. Technical Review, 1989.
[13]
D. Kitson and W. S. Humphrey. The role of assessment in software process improvement. Technical Report CMU/SEI-89-TR-3, Software Engineering Institute, CMU, Pittsburgh, PA, Dec. 1989.
[14]
M. M. Lehman. Process models, process programs, programming support. Proc. 9th Int. Conf. on Soft. Eng., April 1987.
[15]
M. M. Lehman, V. Stenning, and W. M. Turski. Another look at software design methodology. ACM Software Engineering Notes, 9(2), April 1984.
[16]
N. H. Madhavji. The prism model of changes. Proc. 13th IEEE/ACM Int. Conf. on Soft. Eng., May 1991.
[17]
N. H. Madhavji. The process cycle. IEE/BCS Software Engineering Journal, 6(5), September 1991.
[18]
N. H. Madhavji, W. Hong, T. F. Bruckhaus, and J. E. Botsford. Elicit: A meta process and supporting tool for eliciting software process models. Technical Report Technical Report SE-92.4, School of Computer Science, McGill University, Montreal, September 1992.
[19]
N. H. Madhavji, K. Toubache, and W. Hong. A framework for process maintenance. In Proceedings of the IEEE Conference on Software Maintencance (to appear), Orlando, FL, November 1992.
[20]
N. H. Madhavji, K. Toubache, and W. Hong. Communications and iterations in the process cycle. In To appear, Proc. 7th Int. Software Process Workshop, ACM SIGSOFT, Yountville, CA., October 1991. ACM Press.
[21]
N. H. Madhavji, K. Toubache, and W. Hong. A framework for process evolution. Technical Report Technical Report SE-91.3, School of Computer Science, McGill University, Montreal, September 1991.
[22]
D. McCracken and M. Jackson. Life-cycle concept considered harmful. ACM Software Engineering Notes, April 1982.
[23]
L. Osterweil. Software processes are software too. Proc. 9th Int. Conf. on Soft. Eng., April, 1987.
[24]
R. Prieto-Diaz and P. Freeman. Classifying software for reusability. IEEE Software, January 1987.
[25]
R. A. Radice, N. Roth, Jr. A. C. O'Hara, and W. Ciarfella. A programming process architecture. IBM Systems Journal, 24(2), 1985.
[26]
S. T. Redwine. Constructing enactable models (or process models for process models): Session summary. Proc. 4th Int. Software Process Workshop, ACM SIGSOFT, 14(4), May 1988.
[27]
W. W. Royce. Managing the development of large software systems. Proc. IEEE Wescon, Aug 1970.
Recommendations
Applying agent technology to software process modeling and process-centered software engineering environment
SAC '05: Proceedings of the 2005 ACM symposium on Applied computingThe software processes can be analyzed, designed, and maintained as if it is a piece of software. This view enables the application of software engineering technologies to software process modeling (SPM) and process-centered software engineering ...
Towards a change-aware process environment for system and software process
ICSSP '15: Proceedings of the 2015 International Conference on Software and System ProcessManaging changes for knowledge-intensive processes like System and Software Engineering is a critical issue but far from being mastered due to the lack of supporting methods and practical tools. To manage changes systematically, a process environment is ...
Computer aided pattern-based collaboration process design: a computer aided collaboration engineering tool
CRIWG'07: Proceedings of the 13th international conference on Groupware: design implementation, and useAs many business processes are collaborative in nature, process leaders or process managers play a pivotal role designing collaboration processes for organization. To support the design task of creating a new collaborative business process, best ...
Comments
Information & Contributors
Information
Published In
Sponsors
- IBM Canada Ltd. Laboratory Centre for Advanced Studies
Publisher
IBM Press
Publication History
Published: 09 November 1992
Qualifiers
- Article
Acceptance Rates
Overall Acceptance Rate 24 of 90 submissions, 27%
Contributors
Other Metrics
Bibliometrics & Citations
Bibliometrics
Article Metrics
- 0Total Citations
- 496Total Downloads
- Downloads (Last 12 months)54
- Downloads (Last 6 weeks)2
Reflects downloads up to 05 Mar 2025
Other Metrics
Citations
View Options
Login options
Check if you have access through your login credentials or your institution to get full access on this article.
Sign in