Re: Simple inheritence question




Robert C. Martin wrote:
On 1 Feb 2006 03:13:43 -0800, "Mark Nicholls"
<Nicholls.Mark@xxxxxxxxx> wrote:

If the software model solves the business model then the business model
must be consistent....i.e. there must be some sort of embedding of the
business model in the software one.......you cannot loose the ugliness
of the business model.

On the contrary, you certainly can. The structure of the software
does not need to be the same as the structure of the business model.
The ugliness of the business model can be moved outside the software
into configuration data, leaving the software itself unfettered.


I'm talking of the system as a whole...I do not especially distinguish
between the (structure of the ) configuration data and the software
itself....they are largely interchangable......we could potentially
move all the code into 'configuarion' and invoke the compiler and
execute the resultant code on execution....the system would behave
identically....yet would consist of a 2 line batch file, the compiler
and a huge lump of config.

I am splitting hairs though....in your terms I agree.....it cannot be
lost, just moved.

.



Relevant Pages

  • Re: LPC900/80C51 Compiler Toolchain
    ... Open source serves a niche that can't easily be ... served by commercial software in some cases. ... It's just that the business model of OSS is totally ... compiler and then pay a relatively ...
    (comp.arch.embedded)
  • Re: Richard Stallman is responsible for the shrinking economy
    ... uses a different business model from "proprietary" software. ... You do not have to pay an up front cost. ... For things like the GCC compiler there is no effective test suite so the ... at consultancy rates or you buy a support contract. ...
    (comp.arch.embedded)
  • Re: Did Borland doing well in Q4? Listen to the Earning CC
    ... But, to a business, Time is Money - and who exactly is going ... to pay for that time? ... Depends on your business model, ... Perhaps CodeGear's new compiler can issue hints for possible tricky ...
    (borland.public.delphi.non-technical)