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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,bf72ca9e8a6b3cf
X-Google-Attributes: gid103376,public
From: "Robert I. Eachus" <eachus@mitre.org>
Subject: Re: Software Engineering in Florida
Date: 1999/11/12
Message-ID: <382C47FA.9E03A196@mitre.org>#1/1
X-Deja-AN: 547807217
Content-Transfer-Encoding: 7bit
References: <1e0rgtb.6j187t1hibcsaN@[209.132.126.64]>
 <7vv26t$tju$1@nnrp1.deja.com> <lpdV3.8$C%6.715@typhoon.nyu.edu>
 <804plo$dvs$1@nntp5.atl.mindspring.net> <3828A2D7.F23C91AE@mitre.org>
 <80ah1d$rvg$1@nnrp1.deja.com>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@news.mitre.org
X-Trace: top.mitre.org 942425747 1204 129.83.41.77 (12 Nov 1999 16:55:47 GMT)
Organization: The MITRE Corporation
Mime-Version: 1.0
NNTP-Posting-Date: 12 Nov 1999 16:55:47 GMT
Newsgroups: comp.lang.ada
Date: 1999-11-12T16:55:47+00:00
List-Id: <comp.lang.ada>

Robert Dewar wrote:
  
> I disagree with the above, unless you are using programming
> to mean coding.

  I think we are in agreement.  Programming begins after low-level
design is complete.  But I still use coding to apply only to writing in
assembler or machine code.  In an Ada context, library unit
specifications should be an output of the design process, while bodies
and subunits are part of programming.
 
> For me programming = the entire process required to create
> a program, and most certainly one aspect of programming is
> software engineering (another is requirements engineering).

   I see it the other way around.  Software Engineering includes the
entire process from concept to deployment.  Programmers need not be
software engineers, but software engineers must be familar with the
entire process, including requirements analysis, human factors, user
interfaces, system architecture, software design, programming, testing,
and (gasp!) documentation.  The software engineer's role is to
compromise between all these areas to get the best possible product
within budget and schedule.

-- 

                                        Robert I. Eachus

with Standard_Disclaimer;
use  Standard_Disclaimer;
function Message (Text: in Clever_Ideas) return Better_Ideas is...