Constraint-centered descriptions for automated tool invocation

One dominant approach to automate tool invocation in software development environments (SDEs) is to describe software development processes (SDPs) in terms of when and how to invoke tools. However, this causes difficulties in writing and understanding such descriptions. In contrast to this traditional approach (we refer to such descriptions as activity-centered descriptions), it is possible to describe constraints among software objects as specifications of SDPs that express what constraints to maintain. We refer to these descriptions as constraint-centered descriptions. This paper shows that constraint-centered descriptions are easier for designers to write and help users to understand specifications of SDPs, and that imperative constraint grammars are suitable to express constraint-centered specifications of SDPs.<
>