Software process model and work space control in the Adele system

It is argued that the most critical aspects for modeling and control, in a large software engineering environment, are inter/intrateam communication and synchronization. A solution based on a two-level approach is proposed. The Adele kernel supports multiple activities on shared objects, providing services like contextual behavior, active relationships, and general process support. The second level is the TEMPO formalism based on the role concept, which defines a software process step as a set of objects playing a role. Each object's characteristics and behavior depend on the role it plays in the software process it belongs to, and may be part of different simultaneous software processes. TEMPO clearly separates the description of the process from the description of the interaction and collaboration between the different processes.<>