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.

IT service desk process improvement : a narrative style case study

This paper is a detailed case narrative on how a Faculty of a leading Australian University conducted a rigorous process improvement project, applying fundamental Business Process Management (BPM) concepts. The key goal was to increase the efficiency of the faculty’s service desk. The decrease of available funds due to reducing student numbers and the ever increasing costs associated with service desk prompted this project. The outcomes of the project presented a set of recommendations which leads to organizational innovation having information technology as an enabler for change. The target audience includes general BPM practitioners or academics who are interested in BPM related case studies, and specific organisations who might be interested in conducting BPM within their service desk processes.

Program Annotations: Feedback for Students Learning to Program

This paper presents a novel program annotation mechanism which enables students to obtain feedback from tutors on their programs in a far simpler and more efficient way than is possible with, for example, email. A common scenario with beginning students is to email tutors with copies of their malfunctioning programs. Unfortunately the emailed program often bears little resemblance to the program the student has been trying to make work; often it is incomplete, a different version and corrupted. We propose an annotation mechanism enabling students to simply and easily annotate their programs with comments asking for help. Similarly our mechanism enables tutors to view students’ programs and to reply to their comments in a simple and structured fashion. This means students can get frequent and timely feedback on their programs; tutors can provide such feedback efficiently, and hence students’ learning is greatly improved.