Book on OO Component Design?

From: kenandeva (_at_yahoo.com)
Date: 10/29/03


Date: Wed, 29 Oct 2003 08:20:33 -0500

Hi.

Can anyone recommend a good book about building systems out of OO SW
components? I have some fine books on OO design, but now that I'm on a
project that needs to build a system by creating components, I'm finding
that there are aspects to such a process that distinguish it from simply
designing an OO system. Our goal is to make components that will
facilitate the system that we are designing now, but that will be able
to be reused in the future to build systems in a similar product
domain. Easy to say, tough to do.

One more note: the system we are making is a real-time system, with most
parts being "soft" real time and a small subset being hard real time. I
say this because that rules out using things like JAVA, J2EE and things
like that. For now we'll be using C++.

Ideally, I'd like to find a book that incorporates the use of patterns
and UML and contains sample case studies, but mainly, I just want it to
be a great, pragmatic book.

Thanks for any input,

Ken



Relevant Pages

  • Re: uC recommendation
    ... unit by designing our own hardware. ... >>Can anyone recommend a uC that fits the bill? ... > Your examples cover quite a broad range of potential candidates - ... > core modules therefore will save you a lot. ...
    (comp.arch.embedded)
  • Re: Book on OO Component Design?
    ... > Can anyone recommend a good book about building systems out of OO SW ... > facilitate the system that we are designing now, ... I'd like to find a book that incorporates the use of patterns ... It does not discuss real time systems though, ...
    (comp.object)
  • Re: REQ: any utilities for designing front-ends for databases
    ... I recommend using MS Access. ... Anyone have any utilities for designing MS Access front-ends? ... Access' tools are pretty vanilla. ...
    (comp.databases.ms-access)
  • Re: Making money from Java
    ... all; it's been mostly designing. ... They recommend when you're stumped on a problem, to walk away from it for a short while, think about something else, and then come back to it. ... you may even produce a half-cocked solution, with an awareness that it fits, even though it is cumbersome in implementation. ... Digging the shovel into the soil doesn't stop your thought juices and almost in a casual way, you see the spark of an alternative to what you had previously designed. ...
    (comp.lang.cobol)