This paper shows how Design Patterns may be used to reveal properties of object-oriented development methods. The responsibility-driven and event-driven design methods are contrasted in the way they transform and layer systems. Each method elevates a different modularising principle: contract minimisation and existence dependency. Different design patterns, such as Mediator, Chain of Responsibility, Template Method, Command and Composite emerge for each method, illustrating the particular bias and the different design decisions each makes.

No abstract

No abstract

No abstract

It has been widely observed in the information technology (IT) communities that IT developers are coming increasingly under more pressure than ever in juggling between software quality and timely delivery in a tight budget. Developers are torn between the dilemma of either delivering quality software at a price of longer development time and higher cost or delivering software in a timely fashion neglecting quality. Many attempts have been made to tackle the challenge of: "Can-We-Have-It-All?". This paper recommends an approach to manage time and budget against quality and aims at achieving this tripartite objective. The paper covers the development of a Dynamic Business Object Architecture (DBOA) and its implementation through an insurance project case study. The structure and approach of the DBOA are explained through the development process and the case study is presented to demonstrate the initial result of this approach. Some insights resulting from applying the above techniques are also discussed.