If software development is a team effort, how then is the design of a
software most efficiently and effectively communicated

a. among team members, if one part of the team changed it and another
part needs to work on the changed parts?
b. to new team members who have no/little knowledge of the overall
software system?

By "efficient" I mean quickly. How long does it take to inform
somebody about a design?
By "effectively" I mean, the person getting informed about the design
should finally have the same mental model of the design as the others,
and this mental model should mostly closely match the de facto design.

By "design" I mean overall system structure: which functional units
are there, what´s their purpose, how do they interact to realize some
user value (fulfill certain requirements, e.g. implement a feature).

-Ralf

--
You received this message because you are subscribed to the Google Groups "software_craftsmanship" group.
To post to this group, send email to software_craftsmanship-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
To unsubscribe from this group, send email to software_craftsmanship+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org.
For more options, visit this group at http://groups.google.com/group/software_craftsmanship?hl=en.