CSC: Experience. Results

Library

Browsing Library by Research

Home

• Re-building the systems development organisation
  1 Jul 03 | Journal Articles
  
  

  Because of recent advances in systems development it is time for organisations that have let their development skills atrophy to have another look at in-house development instead of buying packages. So agile and rapid have some companies become with their in-house developers, that packages represent a false economy. This article is thus timely when budget demands grow more incessant every day.

• Patterns, Components, Services and Objects – what’s the difference?
  1 Jul 03 | Journal Articles
  
  

  Patterns, components, services and objects are four of the most powerful concepts in modern business systems design and development. In this article, we provide a clear and useful set of distinctions that can help you realise the benefits of them all.

• Naked Objects - Achieving business agility through radical software design
  26 Jun 02 | Single Topic Reports
  
  

  CSC Research Fellow Richard Pawson offers a radical rethink of object-oriented systems design called ´Naked Objects´.

  Although the name might raise a few eyebrows, it well describes the approach; core business objects such as Customer, Product and Order showing directly through to the user instead of being masked behind the menus, scripts and dialogue boxes of a conventional user interface.

• Restoring the craft of software development: a review of Extreme Programming
  1 Nov 01 | Journal Articles
  
  

  Extreme Programming (XP) is the trendiest thing in systems development. Its proponents claim that XP delivers systems that meet the customer's requirements better, are delivered faster, and are easier to modify to meet future requirements. XP is well worth trying - in this article we explore the 12 practices that define XP and recommend steps to get you underway.

• What is the difference between objects and components?
  1 Mar 00 | Journal Articles
  
  

  In this article we tackle the longstanding question of the similarities and distinctions between object orientation and componentised software.
  
  Whilst it is clear that there is a great deal of overlap between the concepts, the authors show that objects and components have a clear technical distinction: components are created at development time and objects are created at run-time. This technical difference has profound implications.
  
  The authors conclude that the power of components lies in improving the software development process, whereas the power of objects lies in improving the product.
  
  In particular, objects enable the creation of a whole class of systems where the user is not constrained to following a standard process, but can model and explore individual business problems or opportunities

• Four approaches to software componentisation
  1 Nov 99 | Journal Articles
  
  

  A growing proportion of organisations now have a componentisation initiative within their systems delivery groups, but they do not all mean the same thing by ‘componentisation’. In this article, we argue that there are four distinct approaches to software componentisation: re-use, plug-and-play, business configurability and expressive systems.