SIGIA-L Mail Archives: RE: [Sigia-l] Enterprise IA
RE: [Sigia-l] Enterprise IA
From: Lord, Ralph (rsl3_at_cdc.gov)
Date: Thu Apr 17 2003 - 09:21:55 EDT
> In my prototype-centric world the Dev team should be
> essentially constructing what's (functionally) indicated by
> the prototype, in much the same way a general contractor
> builds with an architect's blueprints.
> This is the most efficient way but with one crucial
> requirement: that the IA/Design team (IA, project manager,
> business analyst, UI designer, etc) understand the
> fundamentals of app design (at least) to the extent that they
> won't spec/prototype something too costly, too
> time-consuming, too hard to maintain, etc.
I couldn't agree more. I think this simple, but powerful, analogy of
dividing the labor on software projects in a manner similar to construction
of houses/buildings/etc is the right way and will become the preferred way
to structure software projects.
Many have suggested it (at least as far back as Brooks in MM-M) but it still
hasn't quite caught on. Perhaps evolution of
processes/tools/artifacts/roles will eventually make it widespread.
In the meantime, if you're responsible for designing the behavior of a
system but don't understand the fundamentals of app design, look to a
well-qualified developer type to work with much as architects (the boards
and bricks kind) work with consulting engineers when they're not sure what
they're designing is feasible/too costly/etc.
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments
Searchable list archive: http://www.info-arch.org/lists/sigia-l/
Sigia-l mailing list -- post to: Sigia-l_at_asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l
This archive was generated by hypermail 2.1.2
: Sun Nov 23 2003 - 22:55:43 EST