Let's Dance: A Language for Service Behavior Modeling

In Service-Oriented Architectures (SOAs), software systems are decomposed into independent units, namely services, that interact with one another through message exchanges. To promote reuse and evolvability, these interactions are explicitly described right from the early phases of the development lifecycle. Up to now, emphasis has been placed on capturing structural aspects of service interactions. Gradually though, the description of behavioral dependencies between service interactions is gaining increasing attention as a means to push forward the SOA vision. This paper deals with the description of these behavioral dependencies during the analysis and design phases. The paper outlines a set of requirements that a language for modeling service interactions at this level should fulfill, and proposes a language whose design is driven by these requirements.

The guide to the project management body of knowledge (PMBOK Guide) : applicability and contribution to project success in Australia

The PMBOK Guide is one of the most influential publications concerning the knowledge of the project manangement. Moreover, the pervasion of this guide seems to be set to increase as the basis of accreditation - in conjunction with the increasing global trend toward obtaining project management professional status. However, despite the influence and strengthening profile of this guide, reports continue to be published that detail numerous project failures in a wide range of different industries. The PMBOK Guide comprises mainly declarative (know-what) and procedural (know-how) information. In this sense, the guide is largely normative and provides a very good example of the limitations of this approach as highlighted by proponents of a move to the genuine application of positibe theory in project management.----- The aim of this paper is to determine the applicability of the guide in Australia and to determine the extent to which project success can be attributed to the guide. Project Managers from a variety of organisations were surveyed. This postal survey yielded 48 replies. Descriptive statistics was used to assess the incidence and effectivieness of all the processes in the guide. The results indicate that there were no processes that could be considered as peripheral or as a candidate for elimination from the guide. More specifically, all the processes were identified as either a key routine process or a key selective process and positively related to the level of project success. However, the results also indicated that other major factors pertaining to causal knowledge (know-why) are, at least, equally important determinants of project success. It is concluded that declarative, procedural and causal knowledge are all valuable, and given the preponderance of the first two types of knowledge, there seems to be an urgent need to now ensure an equal quest for causal knowledge. In terms of developing causal knowledge, a good starting point would appear to be both positive theory from production and economics.