In message <02fb01ca4c38$ab3ad6c0$01b084...@com>, Symeon Breen
<[email protected]> writes
Actually for many it is mass produced. Specification is being done to the
absolute minutia, for example in the Unified Rational process, when
generating use cases these get transmitted down to the architectural
specifications and become the actual classes in the code (there is even
software to build such skeleton code), with each method and property
defined, again this is then used by the test plan to test each
class/method/property etc. The coder kind of just fills in the gaps. In my
previous employment we had whole teams of BA's, DBA's, System Architects, UI
Designers, UX analysts etc, Then a bunch of people in the Philipines to do
exactly as was written down in front of them. This kind of scenario
happens a lot in larger projects.
Which is probably why so many larger projects are either a disaster from
the start, or rapidly turn into legacy (often before they're deployed)
as the business needs change.
Cheers,
Wol
--
Anthony W. Youngman <[email protected]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
