Using a bottom up perspective to design management and software systems

Development techniques almost always use top down approaches to develop software and business systems. Humans need to simplify the external world by using cognitive models to build a boundary around a problem. These necessary, but artificial, boundaries help us cope with the complexity of the problem at hand. However, this deductive process produces dilemmas, as it leads to misconceptions about the real behavior of systems. This paper will look at system design using the system elements (and their interactions) as the starting point of design, that is an inductive approach. Whilst this will not replace the top down approach, its use will enhance problem solutions. In a contemporary world of loosely coupled organisational elements, it is necessary to view the system from this perspective to fully understand it. In its original format, Object Oriented Design offered one way of producing software, which vaguely represented the complexity, and problematic nature of the 'real' world. This paper will offer a preliminary methodol to approach system design using 'bottom up' thinking, and map it onto the Object Oriented Design process. This view is not the opposite of top down thinking but a supplement to it. It results in asking questions about the desired system, which are fundamentally different in nature to conventional techniques.