From: G. Ralph Kuntz, MD, MS on
I am trying to design a large, testable, client-server project. I am
reading Martin Fowler's book 'Patterns of Enterprise Application
Architecture' and have found it to be an excellent source.

I am a little confused as to who creates each object.

Take the case of an application frame using the MVP pattern. The
presenter is passed pointers to the view and model in its constructor,
where it expects ViewInterface and ModelInterface parameters (C# or
Java). What code actually creates the implementations of the view and
model, and how is that code tested with unit tests?

For example, if I create factory objects and call them from the
application main object using something like

IView view = ViewFactory.getCurrent().getView();

then I can't easily substitute a mock object for the factory.

Any ideas or references that cover this (books, papers, etc)?

Thanks, Ralph
From: Andrey on
Look at this http://martinfowler.com/articles/injection.html it wasn't
included in the book.


On Nov 30, 10:57 pm, "G. Ralph Kuntz, MD, MS" <g...(a)usa.net> wrote:
> I am trying to design a large, testable, client-server project. I am
> reading Martin Fowler's book 'Patterns of Enterprise Application
> Architecture' and have found it to be an excellent source.
>
> I am a little confused as to who creates each object.
>
> Take the case of an application frame using the MVP pattern. The
> presenter is passed pointers to the view and model in its constructor,
> where it expects ViewInterface and ModelInterface parameters (C# or
> Java). What code actually creates the implementations of the view and
> model, and how is that code tested with unit tests?
>
> For example, if I create factory objects and call them from the
> application main object using something like
>
> IView view = ViewFactory.getCurrent().getView();
>
> then I can't easily substitute a mock object for the factory.
>
> Any ideas or references that cover this (books, papers, etc)?
>
> Thanks, Ralph

From: WALLYWORLD on
the data analyst is the guy

data analyst does process modeling
enterprise data admin. overall information requirements keeps charts on the
strategic data model
database designer - chooses the data management application
application analyst does processing flows and interfaces
below that are the department managers, and divison managers

what you gonna calls this book? its called bob's free data analysis and
bean dip!

"Andrey" <andrey_ryabov(a)bk.ru> wrote in message
news:ea701c17-be31-4d6a-b482-f398c5b10590(a)x69g2000hsx.googlegroups.com...
> Look at this http://martinfowler.com/articles/injection.html it wasn't
> included in the book.
>
>
> On Nov 30, 10:57 pm, "G. Ralph Kuntz, MD, MS" <g...(a)usa.net> wrote:
> > I am trying to design a large, testable, client-server project. I am
> > reading Martin Fowler's book 'Patterns of Enterprise Application
> > Architecture' and have found it to be an excellent source.
> >
> > I am a little confused as to who creates each object.
> >
> > Take the case of an application frame using the MVP pattern. The
> > presenter is passed pointers to the view and model in its constructor,
> > where it expects ViewInterface and ModelInterface parameters (C# or
> > Java). What code actually creates the implementations of the view and
> > model, and how is that code tested with unit tests?
> >
> > For example, if I create factory objects and call them from the
> > application main object using something like
> >
> > IView view = ViewFactory.getCurrent().getView();
> >
> > then I can't easily substitute a mock object for the factory.
> >
> > Any ideas or references that cover this (books, papers, etc)?
> >
> > Thanks, Ralph
>