HDTenEightyP/NetNews huggingface dataset:
From: claird@NeoSoft.com (Cameron Laird)
Subject: Author-less inspections (was: Software Inspections.  How many does it take?)
Organization: NeoSoft Communications Services -- (713) 684-5900
Date: Thu, 17 Dec 1992 14:24:52 GMT

In article <BzB9J2.2q2E@austin.ibm.com> dugal@austin.ibm.com (Doug Gray) writes:
			.
			.
			.
>I'm not sure I see how that holds.  I would think that the author's ego would be a
>factor whether reviewed by 1 or by 20.  Their work is still being put on the line.  I
>can see how having the author be a part of the review can be a problem, though. 
>Generally, it seems that having the author as distanced as possible from the review
>is the best idea.
			.
			.
			.
I have no experience with reviews in which the
author(s) is (are) *not* present, but I like
the idea; is there anyone who can report on how
that works in practice?

My attraction to this has nothing to do with
"ego"; I just want to have the documents stand
on their own, without the explanations that the
author(s) inevitably carri(es).
-- 

Cameron Laird
claird@Neosoft.com (claird%Neosoft.com@uunet.uu.net)	+1 713 267 7966
claird@litwin.com (claird%litwin.com@uunet.uu.net)  	+1 713 996 8546
From: dalk@login.dkuug.dk (Lars Kalsen)
Newsgroups: comp.software-eng
Subject: PRO-IV
Date: 12 Dec 92 14:44:54 GMT
Organization: DKnet

Hi,

I am looking for information about a product called PRO-IV from McDonnell
Douglas. What is the status of this product - and the future ?. What is
the internal structure ?. How big applications are running with this 
product ?.

If someone has experience with this then please E-mail or fax me.

Greetings from Denmark,

Lars Kalsen


-------------------------------------------------------------------------------
Lars Kalsen, MIS-Manager
SONOFON, Skelagervej 1, 9000 Aalborg, Denmark
+45-99-367000 (tel), +45-99-367070 (fax), E-Mail : dalk@login.dkuug.dk
===============================================================================
From: herbst@seq.uncwil.edu (R.T. Herbst)
Newsgroups: comp.software-eng
Subject: C code Layout
Keywords: C code layout
Date: 12 Dec 92 12:24:53 GMT
Article-I.D.: seq.1992Dec12.122453.8582
Organization: Univ. of North Carolina @ Wilmington

While directing the eforts of 125 people in producing the 
A Data switching system for the Bell System- Good ol'
Ma bell-- I asked for a sample of code. I founr the comments to
be utter nonsense,. If one removed the code, the comments made no sense.
It was better to let the code speak for itself. If fact the code
was hidden in by the comments. Certainly we need well commented code.
Too many comments that try to say what the code is saying are IMHO
distracting. The code in this case was assembler. Since that time
higher level languages came into use. In particular C language.
My philosophy is to let the language speak for itself. Add comments
where necessary. Again while directing the efforts of hundreds of
people on the Safequard Anti-Balistic Missile System, we set standards
for commenting that let the code be seen. The project met its objectives
and schedule -- one of the few in that time frame. 
Flame on and damned be he or she who flames out.
herbst@seq.uncwil.edu
From: fester@cs.washington.edu (Lea Fester)
Newsgroups: comp.software-eng
Subject: Tools for and papers about RP
Date: 19 Dec 92 06:11:15 GMT
Article-I.D.: beaver.1992Dec19.061115.15751
Organization: Computer Science & Engineering, U. of Washington, Seattle

I'm looking for pointers to tools for and papers about rapid 
prototyping.  Basically, something like name and vendor for any
rapid prototyping tool you've used (a brief description would be
great, but is optional); and enough information to track down
the given paper, if you know of any on the subject.

Thanks in advance,
Lea                   fester@cs.washington.edu
Newsgroups: comp.software-eng
From: mcgregor@netcom.com (Scott Mcgregor)
Subject: Re: C code Layout
Organization: Netcom - Online Communication Services (408 241-9760 guest)
Date: Fri, 18 Dec 1992 06:33:44 GMT

In article <1992Dec17.081451@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:
>The point of that long ramble is that if you've got code with lots of
>detailed comments, you can push past a hardware barrier to displaying it,
>but you'll still run into eye/brain limits.  THOSE limits--our mental and
>physiological limits--we have to take into account when writing code.

This point is right on.  And once you realize this, you realize that
once you hold the choice of language constant (e.g. standard C code
conventions) you've strongly limited the freedom to get bigger chunks.
That's one of the reasons I was very interested in the alternate
schematic representation of the code, which resulted in a more
efficient horizontal usage without apparent increase in cognitive
load. The net result is that more could be understood in a glance.

I think that applying these principles WITHIN the restrictions of a
given language is entirely appropriate and should be done. But I don't
think we should allow ourselves to get so comfortable with these
restrictions that we don't push at the envelope and get some more
freedom from time to time.
-- 

Scott L. McGregor		mcgregor@netcom.com
President			tel: 408-985-1824
Prescient Software, Inc.	fax: 408-985-1936
3494 Yuba Avenue
San Jose, CA 95117-2967

Prescient Software sells Merge Ahead, the tool for Merging Text or Code and
offers consulting  & training in project management and design for usability.



Newsgroups: comp.software-eng
From: rcd@raven.eklektix.com (Dick Dunn)
Subject: Re: N/S diagram editor pointers
Organization: eklektix - Boulder, Colorado
Date: Sat, 12 Dec 1992 07:16:07 GMT

kambic@iccgcc.decnet.ab.com (Bonus, Iniquus, Celer - Delegitus Duo) writes:
>I am looking for information on Nassi/Schneidermann diagram editors, either
>commercial or otherwise.  Does anyone have any pointers?

I thought I had a pointer, but an attempt to dereference it produced a
segmentation fault.  (apparently it's only virtual, with no valid mapping
to reality any more.)

Seriously, sorry to digress from what is probably a real need to a question
of academic interest, but why do you have to produce N-S diagrams?  I
thought those died a well-earned death almost a decade ago.  (I'm not
flaming you at all; I'm just surprised they're still around.)
-- 
Dick Dunn    rcd@raven.eklektix.com   -or-   raven!rcd    Boulder, Colorado
	...Straight, but not narrow.
Newsgroups: comp.software-eng
From: kanze@us-es.sel.de (James Kanze)
Subject: Re: C code Layout
Organization: SEL
	<1992Dec14.235521.1557@cbnewsm.cb.att.com>
Date: 15 Dec 92 17:11:05

In article <1992Dec14.235521.1557@cbnewsm.cb.att.com>
lfd@cbnewsm.cb.att.com (Lee Derbenwick) writes:

|> One reason that I personally dislike very large comments embedded in
|> the code is that they greatly reduce the amount of code within my
|> visual field (whether on a screen or on paper): they increase the
|> number of fingers I need to read the code.  [An interesting
|> "difficulty" metric that I've seen attributed to Tom DeMarco.]

I was surprised that this argument wasn't mentioned earlier in this
thread, as it seems quite popular, at least amongst Cambridge
graduates, where it seems to be called the band width theory.  (A
screen or a sheet of paper has a certain "band width", determined by
the number of characters it can contain, and the goal is to use this
band width in an optimal fashion.)

Of course, this means that you also put several short statements on
the same line, code on the same line as the opening brace, etc.  And
of course, you never, never leave a line blank.

This also argues for short variable names.  (They increase the chances
of getting more than one statement on a line.)

In case it's not obvious from the tone of my comments, I am in total
disagreement with this style.
--
James Kanze                             email: kanze@us-es.sel.de
GABI Software, Sarl., 8 rue du Faisan, F-67000 Strasbourg, France
Conseils en informatique industrielle --
                   -- Beratung in industrieller Datenverarbeitung
From: tne@world.std.com (Thomas N Erickson)
Newsgroups: comp.software-eng
Subject: Re: Project Planning Software
Keywords: project planning
Date: 16 Dec 92 15:52:04 GMT
Organization: The World Public Access UNIX, Brookline, MA

downey@tripos.com (Tom Downey) writes:


>Hi,

>We are in need of a good project planning package.  We have evaluated several
>products but are not satisfied with any of them.  

>Can anyone suggest any good products?  It should run on Unix/X-Windows.

>Thanks, and sorry if this is a FAQ.


Try contacting PSDI, who have recently introduced a system called
Project/2 Series X.  It is a full function system running on several
platforms.


PSDI
20 University Road 
Cambridge, MA  02138
(617)661-1444


-- 
Tom Erickson
Alsys
tne@world.std.com
Newsgroups: comp.software-eng
From: mat@mole-end.matawan.nj.us
Subject: Re: Software Inspections.  How many does it take?
Summary: One way to do reviews
Organization: :
Date: Wed, 16 Dec 1992 15:31:25 GMT

In article <1992Dec14.192008.15480@gallant.apple.com>, neumann.m@applelink.apple.com (mark neumann) writes:
> Recently I have been reading Capers Jones new book "Applied Software
> Measurement", McGraw Hill.  ...
 
> ...  However, the inspection technique he describes  requires a
> bunch of people! ...

> All five (or more) may be present for large projects.  For small projects
> dual roles can be assigned, so that the minimum number for a true
> inspection is three: moderator, author, and one other person. "
  ...
> In my experience, when the schedule pressure is on, most of the attendees
> at large formal code walkthroughs are too busy with their own work to
> carefully go over the material being reviewed.  ...
 
> It seems obvious that having someone check your work is a good idea.  ...
 
> My question:  Is one person enough?  Does anybody else use a single
> reviewer approach?
 
> I believe that there are interpersonal dynamics which make one reviewer
> more effective than two of more.  With two or more people, the ego of the
> person whose work is being reviewed is more likely to become a factor.

I think just the opposite.  With one person, any sense of resentment can
more easily focus on the person.

I worked on a project that had a weekly change cycle.  The day before the
changes went in, people gathered in groups of three and four to review
each other's work.  Everyone would have a change to put in, everyone would
look over the code that others would be putting into their joint work.
Everyone could expect to have a problem found, but nobody was on the
spot because everyone would have their chance to have their mistakes
exposed.  And because we worked with each other every day, we were all
the more careful when we had to say `this is just no good,' which will
happen to the best of us from time to time.  On the other hand, nobody
was embarrassed to ask `could we have a comment on that?' when there
was something that we'd need to know when looking at the code again.

It took a couple of years to reach this stage, and not all the supervisory
groups were there yet.  But I think it could have continued indefinitely
and I know there were a number of bugs that were fixed before they went in.

And having everyone take their turn in one session kept it cooperative.

It seems to me that this would be an interesting topic for a psychologist.
Any experts on group dynamics care to comment?
-- 
 (This man's opinions are his own.)
 From mole-end				Mark Terribile

 mat@mole-end.matawan.nj.us, Somewhere in Matawan, NJ
From: kambic@iccgcc.decnet.ab.com (Bonus, Iniquus, Celer - Delegitus Duo)
Newsgroups: comp.software-eng
Subject: N/S diagram editor pointers
Date: 11 Dec 92 14:53:16 EST

I am looking for information on Nassi/Schneidermann diagram editors, either
commercial or otherwise.  Does anyone have any pointers?

email or post.

Thanks

George Kambic
kambic@iccgcc.decnet.ab.com
standard disclaime

Newsgroups: comp.software-eng
From: tdoan@bnr.ca (Tuan Doan)
Subject: Any papers on Metric Methodology?
Keywords: METRIC, METHODOLOGY, PARADIGM, SOFTWARE, ENGINEERING, PAPER, BOOK
Organization: Bell-Northern Research, Richardson, Tx.
Date: Tue, 15 Dec 1992 03:25:34 GMT

Hello,
 
   I was wondering if anyone know of any good paper/article/book in regard
to the review/critique/analysis of various metrics methodology/paradigm.
For example, I am interested whether there is any other "popular" metric
paradigms other than the Goal-Question-Metric (GQM) paradigm used by HP.

Thanks,

 __  __/  /   /   __  /    |   /    Tuan T. Doan
    /    /   /   /   /   / |  /     Advance Signalling Design
   /    /   /   __  /   /  | /      2201 Lakeside Blvd.  P.O. Box 833871
__/  ______/ __/ __/ __/  __/       Richardson, TX 75083-3871
                                    Phone: 6-444-4575/214-684-4575
Internet:  tdoan@bnr.ca             Fax:   6-444-3716/214-684-3716
      or   tdoan@x400gate.bnr.ca    
Newsgroups: comp.software-eng
From: bran@helix.ObjecTime.on.ca (Bran Selic)
Subject: Re: Rapid Prototyping
Reply-To: bran@ObjecTime.on.ca (Bran Selic)
Organization: ObjecTime Limited
Date: Wed, 16 Dec 92 00:37:00 GMT

In article <Bz6Mr4.I4J@ns1.nodak.edu>, overmyer@plains.NoDak.edu (Scott Overmyer) writes:
|> >
|> Is everyone speaking about rapid prototyping as an interactive,
|> "throw-away" simulation of the user interface to a system under
|> design/development?  If this is the common definition, then
|> I'm curious to know how people are using rapid prototyping in the
|> requirements arena.  Specifically, is anyone saying that rapid prototyping
|> can be used to specify requirements?

ROOM (Real-Time Object-Oriented Modeling) is methodology developed
originally at Bell-Northern Research which is based on a series of
executable formal models. The earliest models, in fact, primarily 
capture requirements. This is crucial since requirements for complex
distributed systems (such as communication protocol standards) are
invariably incomplete and inconsistent. Prototyping of requirements
is used to detect such flaws and also to build up an intuition 
about the requirements which no amount of intellectual foresight
can replace.

-- 
*------------------------------------------------------------*
* Bran Selic                 |  phone: (613) 591-3435        *
* Vice President R&D         |  fax: (613) 591-3784          *
* ObjecTime Limited          |  e-mail: bran@objectime.on.ca *
* 340 March Road             |                               *
* Kanata, Ontario, CANADA    |                               *
* K2K 2E4                    |                               *
*------------------------------------------------------------*
Newsgroups: comp.software-eng
From: sherrill@ruhroh.viewlogic.com (Sherrill St. Germain)
Subject: Value of Subscribing to SEI?
Originator: sherrill@ruhroh
Organization: Viewlogic Systems, Inc.
Date: Fri, 18 Dec 1992 14:02:10 GMT


Hi!

This question is directed to members of the Software Engineering 
Institute.  I was thinking about subscribing & I was wondering 
if you could tell me what value you & your company get out of 
being a member.

Thanks,
Sherrill
Newsgroups: comp.software-eng
From: herbst@seq.uncwil.edu (R.T. Herbst)
Subject: C Code Layout
Keywords: C Code
Organization: Univ. of North Carolina @ Wilmington
Date: Mon, 14 Dec 1992 19:31:11 GMT

From the comments on commenting I ferl that I should 
clarify my background.
One I spent 25 years a Bell Telephone Laboratories
Two I was involved in large and small projects. 
Three I am now a professor on mathematical sciences at UNCW.
four I teach software engineering.
five I once wrote a 1000 line SAP program for the IBM 704.
	The program had no comments even my name was missing.
	Months later i picked up the listing and asked 
	"Who wrote this mess"
	This was a long time ago-- circa 1958.
	I learned my lesson. Comments are essential.
	Comments that obscure the code can make
	reading the code very difficult. 
	The code is where the actions is.
	C language permits alongside commenting
	So comment along side the code.
	This allows the code to be continuous.
	Well commented code is needed, but
	Commenting is a small part of the entire process.
	I doubt that there will ever be a agreement on this
	subject. So what.
herbst@seq.uncwil.edu
From: martinc@hatteras.cs.unc.edu (Charles R. Martin)
Newsgroups: comp.software-eng
Subject: Re: average identifier length (was Comments: Code...)
Date: 16 Dec 92 16:13:09 GMT
	<1992Dec15.131302.22615@b30.ingr.com> <1992Dec16.080001@eklektix.com>
Organization: UNC Department of Computer Science
In-reply-to: rcd@raven.eklektix.com's message of 16 Dec 92 08:00:01 GMT

In article <1992Dec16.080001@eklektix.com> rcd@raven.eklektix.com (Dick Dunn) writes:

   >I'm glad someone else uses the 'ii' technique.  Means that there's some
   >code I may have to maintain someday that doesn't use 'i' <gag>.

   The use of a single 'i' as an index variable spreads across more
   languages than you've seen, and is backed up by centuries of
   mathematical usage.

Of course (he said innocently) you could always include a comment that
says "By convention, indices are doubled (eg, ii, jj, kk) to distinguish
them from other variables."
--
		Charles R. Martin/(Charlie)/martinc@cs.unc.edu
     Dept. of Computer Science/CB #3175 UNC-CH/Chapel Hill, NC 27599-3175
	    3611 University Dr #13M/Durham, NC 27707/(919) 419 1754
     "Oh God, please help me be civil in tongue, pure in thought, and able
      to resist the temptation to laugh uncontrollably.  Amen." -- Rob T
Newsgroups: comp.software-eng
From: jhull@vulcan-gw.den.mmc.com (Jeff Hull)
Subject: Re: Rapid Prototyping
Reply-To: jhull@vulcan-gw.den.mmc.com
Organization: Martin Marietta Astronautics Group
Date: Tue, 15 Dec 1992 23:44:06 GMT

In article I4J@ns1.nodak.edu, 
overmyer@plains.NoDak.edu (Scott Overmyer) writes:
|>...  Specifically, is anyone saying that rapid prototyping
|>can be used to specify requirements?

I am specifically saying that a particular form of rapid
prototyping - Executable Simulations of CASE Models - is
an excellent tool for specifying requirements because it
provides a ready method for ensuring that the requirements
are complete and consistent.

---
-- -- -- --  --
	   _   _
    /_    / ) / ) Jeff Hull           j.hull@vulcan-gw.den.mmc.com
   //_) -/- -/-   1544 S. Vaughn Cir  
/_/ \_/ /   /	  Aurora, CO 80012    303-977-1061

No matter where you go ... there you are.
#include <standard.disclaimer.h>

Newsgroups: comp.software-eng
From: joeb@cserver.plexus.com (Joe Brotz)
Subject: DIN801 European Standard??
Organization: Plexus Corp. -- Neenah Wisconsin
Date: Fri, 11 Dec 1992 20:38:15 GMT

I'm looking for a European standard DIN801 (I don't know the title).
I believe the standard deals with software reliability methods in 
safety control devices. If anyone has information on how I can obtain
this document, it would be greatly appreciated.

Thank You.
--
"Bob Gibson is the luckiest pitcher I ever    <Joseph A. Brotz         >
saw. Every time he pitches, the other team    <joeb@cserver.plexus.com >
doesn't score any runs." - Tim McCarver       <UUCP: spool!cserver!joeb>
Newsgroups: comp.software-eng
From: voges@iai.kfk.de (Udo Voges,IAI Zi. 207,5725)
Subject: Re: DIN801 European Standard??
Reply-To: voges@iai.kfk.de
Organization: Kernforschungszentrum Karlsruhe (Germany)
Date: Mon, 14 Dec 1992 07:40:49 GMT

DIN801 is not a European standard, but its correct title is
	DIN V VDE 0801/01.90
	Grundsaetze fuer Rechner in Systemen mit Sicherheitsaufgaben
	(Principles for computers in safety-related systems)
and it is a German Prestandard. As you can see from the title, the document is in
German and has some 170 pages. It is available (not for free) from
	Beuth Verlag Gmbh
	D-1000 Berlin 30
There exists an unofficial English translation, which might be available from
	DKE
	Mr. Burkert
	Referat GK 714
	Stresemannallee 15
	D-6000 Frankfurt/M 70

---
Dr. Udo Voges
Kernforschungszentrum Karlsruhe GmbH, Institut fuer Angewandte Informatik
Postfach 3640, W-7500 Karlsruhe, GERMANY
Tel: +49-7247-82-5725, Fax: +49-7247-82-5070 or +49-7247-82-5786
email: voges@iai.kfk.de
From: titus@dallas.sil.org
Newsgroups: comp.software-eng
Subject: Re: C code Layout
Date: 18 Dec 92 10:05:45 CST
Organization: Summer Institute of Linguistics, Dallas Center

  I guess I might as well throw in my two-cents worth, too.
My own style runs to:

      if (...)
        {
          statement;
        }
      else
        {
          statement;
        } /* End--<whatever was going on> */

I tend to follow the general rule of an END comment for the
}, no matter what the control structure was (i.e.--if, for,
while, etc.).

               * * * * * * * * * * * * * * * * *
Mike Titus, Programmer                  /\   Summer Institute
SIL                                    /  \        of
7500 West Camp Wisdom Road            /SIL \   Linguistics
Dallas, Texas  75236-5699            --------
U.S.A.
Voice    : (214) 709-2400             * Internet <titus@dallas.sil.org>
Facsimile: (214) 709-3387             * UUCP     ...utafil!txsil!dalsil!titus
HAM radio (not on packet yet) KB4ABZ  *

"I can do everything through Him who gives me strength."

      Philippians 4:13 (NIV)
Newsgroups: comp.software-eng,alt.sources.d,comp.sources.d
From: hb@vpnet.chi.il.us (hank barta)
Subject: Re: cscope? trus?
Followup-To: comp.software-eng,alt.sources.d,comp.sources.d
Organization: Vpnet - Free Usenet access
X-Newsreader: TIN [version 1.1 PL8]
Date: Sat, 19 Dec 1992 19:17:27 GMT

Jerry Heyman (jerry@austin.ibm.com) wrote:

: A user has just approached me asking if we have (or can get access to) a
: program called cscope.  It is a file browsing tool which will index and load
: files from a given directory and index based on the function names, identify
: where it is called and give the use the ability to switch immediately into
: that particular file/function call.  I don't know if this is PD or a commercial
: product, but if anyone is familiar with this I'd be glad to hear about it.

: Also, a program called 'trus' (or something similar) that will monitor a
: command and return back a list of each system call that is made, along with
: the first couple of arguments to that system call, and the actual return code
: from the system call.  Again, I do not know if it is PD or commercial, but if
: anyone is familiar with this I'd be glad to hear about them.

: you can post here, or I would prefer e-mail to: jerry@austin.ibm.com

: Thanks,

: jerry
: -- 
: Jerry Heyman                         e-mail   : jerry@austin.ibm.com
: IBM AWSD AIX Dev Env Tools MS 9631    "Software is the difference between
: Austin, TX  78758                        hardware and reality"
: *** All opinions expressed are exactly that - my opinions and NOT IBM's

   'cscope' shows up in the man pages of both SCO and ISC development
   kits w/out attribution to SCO, Microsoft or LPI, so I believe that
   it is probably part of the AT&T development tools. (And for this
   reason, may not work with ANSI code.)

   hank

Newsgroups: comp.software-eng