http://www.martinfowler.com/ieeeSoftware/separation.pdf
Keep your user interface code separate from everything else.
Why do this?
1. It lets different people work on the separate pieces, which is useful when people want to hone more specialized skills.
2. Multiple presentations are possible
3. Pulling away the domain code also makes it easier to spot - and avoid - duplication in domain code
4. Presentations, particularly WIMPs and browser-based presentations, can be very difficult to test.
The difficulties
So why don't programmers seperate their code? Much of the reason lies in tools.
..
The biggest presentation tool has been the family of platforms for developing WIMP interfacees: Visual Basic, Delphi, Powerbuilder, and the like.
...
but the tools don't provide any place to extract the domain code.
citing
So, if you write an application with a WIMP (windows, icons, mouse, and pointer) GUI, you should be able to write a command line interface that does everything that you can do through the WIMP interface—without copying any code from the WIMP into the command line.
'Papers > Others' 카테고리의 다른 글
A longitudinal analysis of software maintenance patterns (0) | 2007.03.31 |
---|---|
Mocks Aren't Stubs (0) | 2007.02.17 |
Software testability(IEEE) (0) | 2007.02.17 |
ISO9126 (0) | 2007.02.17 |
Heuristics of Softwrae Testtability (0) | 2007.02.17 |