Take a look at the new version of this page: [ beta version ]. Tell us what you think.

ABSTRACT

Change is pervasive during software development, affecting objects, processes, and environments. In process centered environments, change management can be facilitated by software-process programming, which formalizes the representation of software products and processes using software-process programming languages (SPPLs). To fully realize this goal SPPLs should include constructs that specifically address the problems of change management. These problems include lack of representation of inter-object relationships, weak semantics for inter-object relationships, visibility of implementations, lack of formal representation of software processes, and reliance on programmers to manage change manually. APPL/A is a prototype SPPL that addresses these problems. APPL/A is an extension to Ada.. The principal extensions include abstract, persistent relations with programmable implementations, relation attributes that may be composite and derived, triggers that react to relation operations, optionally-enforceable predicates on relations, and five composite statements with transaction-like capabilities. APPL/A relations and triggers are especially important for the problems raised here. Relations enable inter-object relationships to be represented explicitly and derivation dependencies to be maintained automatically. Relation bodies can be programmed to implement alternative storage and computation strategies without affecting users of relation specifications. Triggers can react to changes in relations, automatically propagating data, invoking tools, and performing other change management tasks. Predicates and the transaction-like statements support change management in the face of evolving standards of consistency. Together, these features mitigate many of the problems that complicate change management in software processes and process-centered environments.

REFERENCES

• 1: Mack W. Alford. A requirements engineering methodology for real-time processing requirements. IEEE Trans. on Software Engineering, SE-3(1):60 - 69, January 1977.
• 2: Malcolm P. Atkinson, Peter J. Bailey, K. J. Chisholm, W. P. Cockshott, and Ronald Morrison. An approach to persistent programming. The Computer Journal, 26(4):360-365, 1983.
• 3: H J Barnard , R F Metz , A L Price, A recommended practice for describing software designs: IEEE standards project 1016, IEEE Transactions on Software Engineering, v.12 n.2, p.258-263, Feb. 1986
• 4: E. Bell, Thomas, David C. Bixler, and Margaret E. Dyer. An extendable approach to computer-aided software requirements engineering. IEEE Trans. on Software Engineering, SE-3(1):49 - 59, January 1977.
• 5: Michael J. Carey , David J. DeWitt , Daniel Frank , M. Muralikrishna , Goetz Graefe , Joel E. Richardson , Eugene J. Shekita, The architecture of the EXODUS extensible DBMS, Proceedings on the 1986 international workshop on Object-oriented database systems, p.52-65, September 23-26, 1986, Pacific Grove, California, United States
• 6: Michael J. Carey, David J. Dewitt, Daniel Frank, Goetz Graefe, Joel E. Richardson, Eugene J. Shekita, and M Muralikrishna. The architecture of the EXODUS extensible DBMS: a preliminary report. Technical Report Computer Sciences Technical Report #644, University of Wisconsin, Madison, Computer Sciences Department, May 1986.
• 7: Thomas E. Cheatham, Process programming and process models, Proceedings of the 5th international software process workshop on Experience with software process models, p.49-51, October 10-13, 1989, Kennebunkport, Maine, United States
• 8: Geoffrey M. Clemm and Leon J. Osterweil. A mechanism for environment integration. Technical Report CU-CS-323-86, University of Colorado, Department of Computer Science, Boulder, Colorado 80309, 1986.
• 9: Don Cohen. AP5 Manual. Univ. of Southern California, Information Sciences Institute, March 1988.
• 10: Cheatham, Jr. Thomas E. The E-L software development database - an experiment in extensibility. In Proc. 1989 ACM SIGMOD Workshop on Software CAD Databases, pages 21 - 25, 1989. Napa, California, February.
• 11: Stuart I. Feldman. Make - a program for maintaining computer programs. Software - Practice and Experience, 9:255 - 265, 1979.
• 12: Shehab A. Gamalel-din and Leon J. Osterweil. New perspectives on software maintenance processes. In Proceedings of the Conference on Software Maintenance, pages 14 - 22. IEEE, October 1988.
• 13: Dennis Heimbigner. Triton reference manual. Technical Report CU-CS-483-90, University of Colorado, Department of Computer Science, Boulder, Colorado 80309, August 1990.
• 14: Dennis Heimbigner , Steven Krane, A graph transform model for configuration management environments, Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments, p.216-225, November 28-30, 1988, Boston, Massachusetts, United States
• 15: S. E. Hudson , R. King, The Cactis Project: Database Support for Software Environments, IEEE Transactions on Software Engineering, v.14 n.6, p.709-719, June 1988 [doi>10.1109/32.6152]
• 16: L. Krzanik, Enactable models for quantitative evolutionary software processes, Proceedings of the 4th international software process workshop on Representing and enacting the software process, p.103-110, April 1988, Devon, United Kingdom
• 17: Yohihiro Matsumoto , Kiyoshi Agusa , Tsuneo Ajisaka, A software process model based on unit workload network, Proceedings of the 5th international software process workshop on Experience with software process models, p.95-97, October 10-13, 1989, Kennebunkport, Maine, United States
• 18: Kurt Michael Olender , Leon J. Osterweil, Cecil/cesar: specification and static evaluation of sequencing constraints, 1988
• 19: Leon J. Osterweil. Using data flow tools in software engineering. In Muchnick and Jones, editors, Progarm Flow Analysis: Theory and Application. Prentice-Hall, Englewood Cliffs, N. J., 1981.
• 20: L. Osterweil, Software processes are software too, Proceedings of the 9th international conference on Software Engineering, p.2-13, March 1987, Monterey, California, United States
• 21: D L Parnas , P C Clements, A rational design process: How and why to fake it, IEEE Transactions on Software Engineering, v.12 n.2, p.251-257, Feb. 1986
• 22: D. Richardson , S. Aha , L. Osterweil, Integrating testing techniques through process programming, ACM SIGSOFT Software Engineering Notes, v.14 n.8, p.219-228, Dec. 1989
• 23: Joel E. Richardson , Michael J. Carey, Programming constructs for database system implementation in EXODUS, Proceedings of the 1987 ACM SIGMOD international conference on Management of data, p.208-219, May 27-29, 1987, San Francisco, California, United States
• 24: Mark J. Rochkind. The source code control system. IEEE Trans. on Software Engineering, SE-1:364 - 370, December 1975.
• 25: Lawrence A. Rowe , Michael Stonebraker, The POSTGRES Data Model, Proceedings of the 13th International Conference on Very Large Data Bases, p.83-96, September 01-04, 1987
• 26: Craig Schaffert , Topher Cooper , Bruce Bullis , Mike Kilian , Carrie Wilpolt, An introduction to Trellis/Owl, Conference proceedings on Object-oriented programming systems, languages and applications, p.9-16, September 29-October 02, 1986, Portland, Oregon, United States
• 27: John M. Smith, Steve Fox, and Terry Landers. Reference manual for ADAPLEX. Technical Report CGA-83-08, Computer Corporation of America, May 1981.
• 28: Michael Stonebraker , Lawrence A. Rowe, The design of POSTGRES, Proceedings of the 1986 ACM SIGMOD international conference on Management of data, p.340-355, May 28-30, 1986, Washington, D.C., United States
• 29: Stanley M. Sutton, Jr., APPL/A: a prototype language for software-process programming, University of Colorado at Boulder, Boulder, CO, 1991
• 30: Stanley M. Sutton, Jr. FCM: A flexible consistency model for software processes. Technical Report CU-CS-462-90, University of Colorado, Department of Computer Science, Boulder, Colorado 80309, March 1990.
• 31: Stanley M. Sutton, Jr. A flexible consistency model for persistent data in software-process programming languages. In Proc. of the Fourth International Workshop on Persistent Object Systems, 1990. Martha's Vineyard, Massachusetts.
• 32: Stanley M. Sutton, Jr., Dennis Heimbigner, and Leon J. Osterweil. APPL/A: A prototype language for software process programming. Technical Report CU-CS-448-89, University of Colorado, Department of Computer Science, Boulder, Colorado 80309, October 1989.
• 33: Richard N. Taylor , Frank C. Belz , Lori A. Clarke , Leon Osterweil , Richard W. Selby , Jack C. Wileden , Alexander L. Wolf , Michael Young, Foundations for the Arcadia environment architecture, Proceedings of the third ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments, p.1-13, November 28-30, 1988, Boston, Massachusetts, United States
• 34: United States Department of Defense. Reference Manual for the Ada Programming Language, 1983. ANSI/MIL-STD-1815A-1983.

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING

Additional Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.7 Distribution, Maintenance, and Enhancement
          Subjects: Version control
      D.2.9 Management
          Subjects: Software configuration management
  D.3 PROGRAMMING LANGUAGES
      D.3.2 Language Classifications

          Nouns: Ada

General Terms:
Algorithms, Design, Languages, Management