Design Methodologies w/Ada95

Design Methodologies w/Ada95

[dR_Zeuss]

Does anyone know of a good book on Ada95.  I am not looking for just
code but something that will provide insight into design, structures,
etc.

They have us coding, but will not provide structure or interface
guidelines.  I suppose it better that way.  It keeps the project costs
down.  Hell, if they trained us think of the lose when they lay us off
in a couple of months.  They are so far over budget, I can see the
Engineers will take it up the butt again.  Remember when all is lost, it
is the programmers who will be blamed.

Re: Design Methodologies w/Ada95

[dennison]

In article <35B174F3.15ED523F@whovil.com>,
  dR_Zeuss <dRzeussus@whovil.com> wrote:
> down.  Hell, if they trained us think of the lose when they lay us off
> in a couple of months.  They are so far over budget, I can see the
> Engineers will take it up the butt again.  Remember when all is lost, it
> is the programmers who will be blamed.

I see the Grinch has made more than one trip to whovil...
:-)


Rather than getting yourself an Ada book, consider purchasing a copy or two
of "The Mythical Man-Month" by Fredrick P. Brooks, Jr. for your management.
It'll give them something useful to read during their copious free time after
they go home at 5PM every day. (Yes, I've been there. Will probably be there
again too.)

For yourself, I'd seriously consider getting a copy of "Death March" (by
Yourdon I believe).

T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum

Re: Design Methodologies w/Ada95

[Rangler_Roy]

I know what you mean.  They low ball the contract to get the job, and
wonder why you will not work OT for free.  They have people putting
schedules together who have never even programmed.  But if you can 
not meet schedule, even at 60 hours a week, your unprofessional.

You got to love DoD work, really enjoy pain, not to mention the 1% and
2% annual raises.

Re: Design Methodologies w/Ada95

[Michael F Brenner]

   > They expect you to do unpaid overtime.

One of the biggest reasons that ordinary metrics fail to predict the
true cost of projects is that metrics for backlogs (such as overtime
that will never be paid, service requests that are on hold for ever,
documentation that will never be written, and testing that is too
expensive to do) are not created. 

Once you start accounting for the backlogs, you will find they
exceed anything that is correlated to line-of-code, complexity,
or any other volume metric. 

This is one of the primary justifications for doing true 
rate-of-return studies on the backlog of each project, and 
for keeping backlog and clustering metrics instead of volume metrics.

The converse of this is that if you are subject to an expectation of
overtime work that will never be paid, then you can publish
these metrics yourself on your door and on your status reports.

The first law of metrics is that as soon as they are posted on the
door the people who see them take whatever steps are needed to
improve them. Such as burning the poster at the stake along with
the door she posted the metrics on, improving management techniques, 
cancelling the project, actually making these metrics a part 
of the project management process so that the TRUE cost of the 
project gets measured, and, for future projets, making this true
cost the basis of the estimates and bids.

Seeking Truth,
Mike Brenner