20 March 2007

System life span: system definition

By Andrew Clifford

If you want to increase the life span of your systems, you have to clearly define your systems so that you can manage them effectively.

To increase system life span, you need to manage:

Without clear definition, you can not know what needs to be owned, what needs to be kept separate, and what needs to be measured. Without definition, IT is unmanageable.

Definition is not the same as design. Different design methods divide IT in different ways: by process, by data, by components, or as services. You can not manage using many different design views. You have to define one consistent structure over your IT so that it can be managed. (Though of course you should still have design views of our IT, and map these to the structures used for management.)

The best way to structure your IT so that it can be managed is to split it into systems, and to define each system clearly. To define a system clearly, give it a name and clearly define the boundaries of its functionality and its implementation.

Much of IT is already split into systems, and if these are clearly defined then they are a good basis for management. Where system definition is not clear, we need some guidelines.

Defining systems is not hard. It does not matter exactly where you draw the boundaries between systems, as long as they are clearly defined. If you really need to, you can adjust definitions later, though you do need to manage this carefully.

System definition is critical. It is often overlooked, or misunderstood because it is confused with design views. But a clear definition is vital for effective ownership, decoupling and measurement. With clear definition, you can start to manage the life span of your systems.