Abstract
The general systems model based on inputs, processes, and outputs is useful for defining and documenting a development project, but it may not be the mental model that analysts and programmers actually use to differentiate system elements. An exploratory study using multidimensional scaling suggests that employing other dimensions during requirements analysis, functional decomposition, and even final documentation may help manage some of the complexity of today's software.