RE: [GD-General] Architecture Design

[Jeremy G. <jga...@nc...>]

We use both use-case analysis (UML) and XP methodologies, as odd a combo
as that
sounds.  Both work well in different situations - UML works especially
well
with C++ coding, since the barrier to change after you code is high,
even=20
with refactoring techniques - for instance, headers, constructors all
must be
rewritten, etc.  Extreme Programmming is great with easier-to-code
languages=20
like Python, since the cost of change is much smaller.  In all cases,
however,=20
some beforehand design saves a lot of future changes, and some ability
to be=20
flexible when the spec changes is quite useful too.

-jg


> -----Original Message-----
> From: Tom Nuydens [mailto:t.n...@vr...]
> Sent: Monday, October 08, 2001 6:39 AM
> To: gam...@li...
> Subject: RE: [GD-General] Architecture Design
>=20
>=20
> Hi,
>=20
> Even if you split up the work and just piece things together=20
> later on, I
> think at least _some_ design work is necessary. At the very least,
> shouldn't the project lead have an overview of how everything works?
>=20
> We don't get excessively formal about the design process=20
> either, but we
> do use UML class diagrams as a means of communication. I find the
> diagrams to be very helpful when trying to explain ideas to other team
> members (or the other way around). You _do_ occasionally discuss your
> code with your fellow team members, don't you?
>=20
> - Tom
>=20
>=20