From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: * X-Spam-Status: No, score=1.1 required=5.0 tests=BAYES_40,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 Xref: utzoo comp.lang.ada:5770 comp.lang.c++:14288 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!mips!pacbell.com!decwrl!netcomsv!jls From: jls@netcom.COM (Jim Showalter) Newsgroups: comp.lang.ada,comp.lang.c++ Subject: Re: chief programmer team organizations was (c++ vs ada results)H Message-ID: <1991Jun21.222536.18888@netcom.COM> Date: 21 Jun 91 22:25:36 GMT References: <1991Jun18.122812.18190@eua.ericsson.se> <1991Jun18.220609.19103@netcom.COM> <1991Jun19.170047.25064@software.org> <1991Jun20.143535.27176@software.org> Organization: Netcom - Online Communication Services UNIX System {408 241-9760 guest} List-Id: s64421@zeus.usq.EDU.AU (house ron) writes: >blakemor@software.software.org (Alex Blakemore) writes: >>In article <1991Jun18.220609.19103@netcom.COM> jls@netcom.COM (Jim Showalter) writes: >>> One of the most successful Ada projects I'm aware of organized job >>> descriptions and responsibilities in such a way that a relatively small >>> number of exceptionally clever people was responsible for the architecture >>> (as captured in subsystem decomposition and subsystem interface specification), >>This makes sense and sounds like it can work well. It's really just >>the chief programmer teams from the Mythical Man Month by Fred Brookes. >>One obvious caveat - you really better have the right people >>in the chief programmer roles or you are sunk. This organization >The book "Software that Works" by Michael Ward recommends against this for >exactly the reason you mention, among others. He feels that the programmers >must be involved in design, and that design/programming should alternate, >rather than one coming first in a big chunk followed by the other. >That's my potted version, anyway. Well, I certainly agree that design/programming should alternate--that's the basis of iterative development. On the other hand, I fail to see what this has to do with the notion that some people are better than others at design, and that those who are the BEST at design probably ought to be the ones making the most critical decisions on the project. If someone can provide me with an explanation for why junior programmers should be making architectural decisions affecting the entire project, I'm all ears. -- *** LIMITLESS SOFTWARE, Inc: Jim Showalter, jls@netcom.com, (408) 243-0630 **** *Proven solutions to software problems. Consulting and training on all aspects* *of software development. Management/process/methodology. Architecture/design/* *reuse. Quality/productivity. Risk reduction. EFFECTIVE OO usage. Ada/C++. *