Software Systems Development Processes
Process Pattern Language
- Whitenack, B. G., Jr. (1994) RAPPeL: A Requirements Analysis Process Pattern
Language for Object Oriented Development. Technical Report Knowledge Systems Corporation.
- Abstract: RAPPeL is a pattern language that provides direction and rationale for guiding analysts, developers and project
managers in determining and defining requirements for business applications (e.g. information management
systems, decision support systems, work-flow management, scheduling, etc.) to be developed in an OO
environment. It weaves through the fabric of a business problem domain, threads of techniques for capturing
and validating the behavioral and nonbehavioral requirements of a software system. While RAPPeL assumes a
business application is to be built using object-oriented techniques and implemented in an object-oriented
language, some of the patterns are applicable to software requirements analysis in general.
Original
- Coplien, J. O. (1995)A Development Process Generative Pattern Language. Technical Report AT&T Bell Laboratories.
- Abstract: Many factors contribute to software quality and productivity, but development process has increased its share of
the spotlight in recent years. The Pasteur process research program has been gathering data on a wide spectrum of
software development organizations over the past two years. Most highly productive organizations exhibit the
same patterns of organization, process, and introspection. These patterns are missing from organizations that are
less productive or less successful. Using the emerging discipline of generative pattern languages, we can capture
the patterns underlying successful projects and use them to establish organizational structures and practices that
will improve the prospects for success in a new software development organization. This paper presents 43 such
patterns. Managers in highly productive cultures at Lucid, Borland, and AT&T have confirmed the presence of
most of these patterns in their organizations.
HTML Version
- DeBruler, D. I. (1995) Telecommunications Distributed Processing Patterns. Technical Report AT&T Bell Laboratories.
- Abstract: This paper consists of three sections. The first section is a ``meta'' section and
contains some thoughts about patterns and their use. The second section is the
charter of these proceedings--an edited version of the conference patterns. I learned
a lot at the conference and thus the editing is actually a rewrite. Consequently, I
have been unable to change all of the patterns. Thus the third section records the
conference patterns I have not been able to revisit. In short, this paper is like the
patterns movement in general--it is only a beginning.
- Cain, B. G. & J. O. Coplien (1993) A Role-Based Empirical Process Modeling Environment. In Proceedings of
Second International Conference on the Software Process, pages 125-133, Los Alamitos, California, February 1993. IEEE
Computer Press.
- Abstract: Much contemporary development process research is based on analyses of process steps, their duration, and the events they propagate. Our initial research in large, mature telecommunications development processes concluded that such models do not capture abstractions that remain stable over time. We turned our attention instead to empirical role-based models. The basic abstraction in the model is a "role," a longstanding, stable locus of associated responsibilities in a process. A process model evaluation prototyping environment is used to visualize the process data in several ways, including community-of-interest clustering, communication network clustering, and hierarchical rendering. Analyses of these models have led to powerful insights both into individual projects, and into the properties of software development processes in general.