While modern methods for Information system development generally accept that users should be involved In some way (151, the form of the involvement differs considerabiy. Mostly, users are viewed as reiativeiy passive sources of information, and the invoivement is regarded as "f unctionai," in the sense that it shouid yieid better system requirements and increased acceptance by users. 'We also inciude some valuable comments from two researchers, Cl. Bradley and A. Kjicr, who responded to our initial que.stionnaire, but whose projects did nol in llie end lit our < riteria for PD piojects.

No abstract

For a variety of reasons, today's middleware systems are highly complex. This complexity surfaces internally in the middleware construction, and externally in the programming models supported and features offered. We believed that aspectorientation could help with these problems, and undertook a case study based on members of an IBM® middleware product-line. We also wanted to know whether aspect-oriented techniques could scale to commercial project sizes with tens of thousands of classes, many millions of lines of code, hundreds of developers, and sophisticated build systems. This paper describes the motivation for our research, the challenges involved, and key lessons that we learnt in refactofing both homogeneous and heterogeneous crosscutting concerns in the middleware.

No abstract

No abstract

No abstract

No abstract

No abstract