@ericbouwers

Separation of Concerns: An Organizational Approach

. In OOPSLA 2000 Workshop on Adavanced Separation of Concerns, (2000)

Description

Building on top of the tyranny of the dominant decomposition of Tarr et al, this paper introduces the notion of "the tyranny of source files". The author explains that the breaking down of program-code into source-files is never optimal for separating all types of concerns. A solution is proposed in the form of a software configuration management system (SCM) repository. This repository can be queried to dynamically assemble code-snippets into virtual source files. As the author explains, "this approach allows programmers to dynamically separate concerns for the purpose of viewing and understanding programs without affecting their semantic structure".

Links and resources

Tags