HDTenEightyP/NetNews huggingface dataset:
From: erskine@cs.dal.ca (Neil Erskine)
Subject: Request for survey
Organization: Math, Stats & CS, Dalhousie University, Halifax, NS, Canada
Distribution: na
Date: Thu, 1 Oct 1992 14:35:46 GMT

][b
	I'm trying to find a software cost model (or tool implementing
a possibly proprietary model) that works well for predicting costs in
maintenance phase.  I would appreciate pointers to any suggestions,
particularly to survey papers you or others have written.

    Thanks,
        Neil Erskine
||!][b

-- 
Neil Erskine		erskine@cs.dal.ca
			uunet!dalcs!erskine
Newsgroups: comp.software-eng,comp.parallel
From: kornfeld@leland.Stanford.EDU (Judith Kornfeld)
Subject: Info Needed:Scalar-to-parallel conversion tools
Organization: DSG, Stanford University, CA 94305, USA
Distribution: usa
Date: Sat, 3 Oct 92 21:37:36 GMT


Looking for tools and methods to convert scalar FORTRAN and C to
parallel FORTRAN and C. Sources sought for 3rd-party products and 
techniques to support the conversion process.

email:	kornfeld@leland.stanford.edu
voice:	(415)327-2216

Thanks!
From: kambic@iccgcc.decnet.ab.com (Bonus, Iniquus, Celer - Delegitus Duo)
Newsgroups: comp.software-eng
Subject: Re: Code Reviews
Date: 28 Sep 92 11:02:49 EST

In article <1992Sep26.094229.15951@cadreor.cadre.com>, neil@cadreor.cadre.com (Neil W. Van Dyke) writes:
> brad@spike.insci.com (Brad Segal) writes:
>>I need to find some information on code reviews and how to implement them.
> One book I've found especially helpful for all types of technical reviews is:
>     Yourdon
>     *Structured Walkthroughs*, 4th Ed.
>     1989, Prentice-Hall
> 
> It also has a short appendix specific to code reviews.
> Two other useful books which have chapters on technical reviews are:
> 
>     Gause & Weinberg
>     *Exploring Requirements: Quality Before Design*
>     1989, Dorset House
> 
>     Humphrey
>     *Managing the Software Process*
>     1989, Addison Wesley
> 
> I also liked DeMarco's & Lister's *Peopleware* for general information on team
> software development.

All of these are good, but you also need to add

Handbook of Walkthroughs, Inspections and technical reviews, by Freedman and
Weinberg, Dorset House,

Tom Gilb, Principles of Software Engineering Management, Specifically Chapter
12,

Fagan's papers in the IBM systems journal, 1975, and 1976.

Carolyn Jones and Dave(?) Mays in the IBM systems Journal. 1985, 1990.

Fowler in the ATT Technical Journal, 1986.

Gilb also has a manuscript out on a new book that really details the Inspection
process.  Date to be published?????


George Kambic
sd

Newsgroups: comp.software-eng
From: sudhakar@flower.CS.MsState.Edu (Sudhakar)
Subject: Need Info on Z and VDM
Organization: Mississippi State Univ.
Date: Sun, 27 Sep 1992 19:01:32 GMT

I need information on Z language and VDM. I would appreciate if anyone
sends me  a mail with the names the journals which have the info.

Thanx in advance.

Sudhakar.
sab3@ra.msstate.edu
sudhakar@walt.cs.msstate.edu
From: Jonathan.Bowen@prg.oxford.ac.uk (Jonathan Bowen)
Newsgroups: comp.software-eng
Subject: Re: Too many standards
Date: 6 Oct 92 12:52:24 GMT
Organization: Programming Research Group, Oxford University, UK
X-Mailer: mail-news 2.0.3

In article <1992Oct2.161426.6074@inesc.pt>:

|I'm a little confused with software engineering standards, there are
|so many: DoD-2167A, ANSI/IEEE, ISO, ...
|
|I would like to classify them in order to have a clue to decide
|when I should choose one or another!
|Can anyone help me?

You might find the following reference helpful (if a little out of
date now, in this ever changing world):

    Hall, P.A.V.: Software development standards,
    Software Engineering Journal, May 1989, 4(3), pp. 143-147

-- 

--
Jonathan Bowen, <Jonathan.Bowen@comlab.ox.ac.uk>
Oxford University Computing Laboratory.
Newsgroups: comp.software-eng
From: bvs@osf.org (Brian Van Schaick)
Subject: distributed testing tools?
Keywords: distributed test tools
Organization: Open Software Foundation
Date: Wed, 30 Sep 1992 17:20:37 GMT


Does anyone know of any distributed test environment toolkits/scaffolds? What we're looking for is a test scaffold in the public domain (or soon to be in the public domain) that supports testing in a distributed computing environment. Any information would be greatly appreciated. Please direct all replies to me via email: bvs@osf.org or uunet!osf.org!bvs.

Thanks.
Newsgroups: comp.software-eng
From: wegner@gmd.de (Eberhard Wegner)
Subject: Re: Too many standards
Keywords: 2167A, IEEE, ISO
Organization: GMD, Sankt Augustin, Germany
Date: Mon, 5 Oct 1992 11:58:18 GMT

In <1992Oct2.161426.6074@inesc.pt> belen@rabbit.inesc.pt (Belen de Vicente) writes:
>I'm a little confused with software engineering standards, there are
>so many: DoD-2167A, ANSI/IEEE, ISO, ...
>I would like to classify them in order to have a clue to decide
>when I should choose one or another!
>Can anyone help me?

ISO, IEC and ISO/IEC standards are Internationals standards (i.e. worldwide).
ANSI/IEEE standards are national US standards, adopted by the US national
standards body, viz. ANSl.
IEEE standards are non standards proper but were adopted by a registered
association.
DoD standards are organization-internal standards, also known outside that
organization.
There are also CCITT recommendations (telecommunication) having more
binding force than all these standards (which are recommendations).

>Are there also any european standards being used as much as american ones?
Some ISO, IEC and ISO/IEC standards were adopted as European standards - which
is useful because then the members of the European Committee for Standard-
ization (CEN), all being national standards bodies and members of ISO, have
to withdraw different standards on the same topic. By this identity there are
European standards which are at the same time International standards
adopted as US national standards. - I do not know of any European standard
not being an International standard but adopted as an ANSI standard --
please ask ANSI.

>Which is the rigth way to select an standard when you do not have
>one already imposed?
International standards first, national standards of your country then,
professional standards (like IEEE) and standards from manufacturers'
associations (like ECMA) next, organization-internal ones last.

>Too many questions, I'm sorry.
No. Please ask more questions.
>-- 

>	Belen de Vicente
>	E-mail.- belen@rabbit.inesc.pt
>
From: bxk@gsbdom.uchicago.edu (B. D. Kim)
Newsgroups: comp.software-eng
Subject: Need information on software reading finger prints
Summary: Would anybody tell me about a software reading finger prints and matching a n
Keywords: finger prints
Date: 28 Sep 92 19:02:17 GMT
Organization: University of Chicago Computing Organizations

Would anybody tell me about a software reading finger prints, storing these
image data, creating databases and searching a new finger prints over the
finger print databases.
	The softwares can be unix, dos, etc.
Also, I will appreciate letting me know any articles related to this issue
or any companies working on this area.

(Name) Byung-Do Kim
(home) 708-882-8023
(office) 312-702-0654
(e-mail) bxk@gsbdom.uchicago.edu
Newsgroups: comp.software-eng
From: craigh@cserver.plexus.com (Craig Heilman)
Subject: Re: Code Reviews
Organization: Plexus Corp. -- Neenah Wisconsin
Date: Mon, 28 Sep 1992 15:14:42 GMT

neil@cadreor.cadre.com (Neil W. Van Dyke) writes:

>brad@spike.insci.com (Brad Segal) writes:
>>I need to find some information on code reviews and how to implement them.

>One book I've found especially helpful for all types of technical reviews is:

>    Yourdon
>    *Structured Walkthroughs*, 4th Ed.
>    1989, Prentice-Hall

>Two other useful books which have chapters on technical reviews are:

>    Gause & Weinberg
>    *Exploring Requirements: Quality Before Design*
>    1989, Dorset House

>    Humphrey
>    *Managing the Software Process*
>    1989, Addison Wesley

>I also liked DeMarco's & Lister's *Peopleware* for general information on team
>software development.

You might also want to check out:

	Freedman & Weinberg
	"Handbook of Walkthroughs, Inspections, and Technical Reviews"
	Third Edition, 1990, Dorset House
--
*                           * "I just found out that the brain is like a   *
* Craig A. Heilman          * computer.  If that's true, then there really *
* craigh@cserver.plexus.com * aren't any stupid people.  Just people       *
*                           * running DOS." - VH1's Stand Up Spotlight     *
From: tholome@bangalore.esf.de (Eric Tholome)
Newsgroups: comp.software-eng
Subject: CFP 4th European Software Engineering Conference
Date: 1 Oct 92 15:03:48 GMT

Call for Papers

Fourth European Software Engineering Conference

Garmisch, Germany September 13 -17 1993

In 1968, an international workshop was held in Garmisch which coined the
term 'software engineering'. 

In recognition of the 25th anniversary of this key historic event, the 4th 
European Software Engineering Conference will be held in Garmisch in 1993. 
Original papers are invited on any aspect of software engineering and
papers on the following topics are particularly welcome:

Software engineering and CSCW
Software engineering for distributed systems
Software measurement and experimentation
Software maintenance
Requirements engineering
Critical systems engineering
Computer-based systems engineering
Comparisons between development methods and paradigms
Reports on practical experience with new techniques


Submissions  
Papers should be no longer than 6000 words and should include a title page
with a short abstract and 
the authors' addresses. If you prefer not to be identified to reviewers,
you should not include authors' names in the body of the paper.  

Four copies of papers must be received by
the Programme Chair by 23rd November 1992. 

We welcome correspondence by fax or E-mail but fax or 
electronic copies of papers will not be accepted.

Submissions will be reviewed by the program committee for originality,
significance, timeliness, soundness and quality of presentation.  

You should make clear what is novel about your work and 
should compare it with related work.  Theoretical papers should show how
the theory relates to software engineering practice; 
practical papers should discuss lessons learned and the 
causes of success or failure.

Calendar

Papers due:		23rd November 1992
Notification:		12th March 1993
Camera-ready papers due:	16th April 1993
Conference:                     13th-17th September 1993

Programme Chair

Prof. Ian Sommerville,
Computing Dept.,
Lancaster University,
LANCASTER LA1 4YR
UK
Phone: +44 524 65201
Fax: +44 524 381707
E-mail: is@comp.lancs.ac.uk


Newsgroups: comp.software-eng
From: troyer@mitre.org (Tom Royer)
Subject: Re: Software Inspections
Organization: The MITRE Corporation
Date: Tue, 6 Oct 1992 17:11:16 GMT

In article <1992Oct6.154654.4673@m.cs.uiuc.edu> marick@m.cs.uiuc.edu 
(Brian Marick) writes:

> My approach to inspections is different from Fagan's and others.  I
> believe that full-blown inspections are usually not cost-competitive
> with testing in the long run, assuming your product will be actively
> maintained.  When looking for bugs in code, I use testing whenever
> possible and reserve inspections for those bugs that testing is poor
> at discovering.  The checklist is therefore narrowly focused, but it
> can be used as a supplement to your inspection/code-reading process,
> whatever that may be.

This is exactly opposite from my experience.  However, I do agree that
the formal (moderator, scribe, etc.) inspection can be very costly.

The most successful inspection/walkthrough process I ever saw
consisted of a code-review by a software engineer's team leader and
one or more peers selected mutually by the engineer and the team
leader.  At this particular company, the team leaders were 
assigned responsibility for the completion of specific sections of
the total project and their merit reviews were based on their success:
they had a lot of incentive to carefully review
the code (they were also selected for a combination of technical
ability and leadership -- the first step on the management
ladder, actually, if they were so inclined)

--
Tom Royer

Newsgroups: comp.software-eng
From: lucyc@suite.sw.oz.au (Lucy Chubb)
Subject: Re: Z Specification Language -- Does anyone use it?
Organization: Softway Pty Ltd
Date:  2 Oct 92 04:44:12 GMT

From article <1992Oct1.004147.1757@panix.com>, by fhd@panix.com (Frank Deutschmann):
> I have been reading a great deal about Z, the formal specification
> language recently, and I was curious if anyone out here on the net has
> experience with or actively uses Z (or another formal specification
> language/system) in real and/or academic projects.

I used Z to do the functional specification of a project I led
last year.  I use Z all the time in my (part time) Phd, but that
was the first time I had used it at work.

> I'm not real interested in Z theory, but rather I am interested in
> real-world, real-project experience with Z. What sort of projects do
> people actually specify in Z? Do they tend to be multi-gazillion
> dollar century-long projects, or do-it-in-a-week projects, or
> everything in between? How do programmers, analysts, end users, and
> everyone in between react to Z?

The project was something like a man-year of effort over three
months of real time. It involved communications and databases.
The Z spec ended up being an appendix to the functional design
document.

There was a mixed reaction from others, but I was designing
the thing and I find that specs end up having too many holes
in them unless I use some form of formal specification. In other
words, I needed to do it to help me understand the problem and
design a solution. I'm most familiar with Z, so Z was what I used.

		Lucy Chubb.

Softway Pty Ltd,		Phone: +61 2 698 2322;
P.O. Box 305,			Fax: +61 2 699 9174;
Strawberry Hills,		Email: lucyc@softway.oz.au
NSW 2012,
AUSTRALIA
Newsgroups: comp.software-eng
From: joshua@cc.uow.edu.au (Poh Onn Joshua Fan)
Subject: Looking for Dani A. C. Foo
Keywords: Foo
Organization: University Of Wollongong
Date: Wed, 30 Sep 92 08:26:33 GMT




Prof. Dani A.C. Foo
Business Information Systems
University of Eastern Asia



Can you please contact


Prof. Michael Gaffikin
Department of Accountancy
University of Wollongong
Northfields Avenue
Wollongong
N.S.W.
Australia 2522
Phone: 042-213718
Fax: 042-213097
E-mail: gaffikin@uow.edu.au


Thanks!
From: cwh@acpub.duke.edu (CLAYTON HOLT)
Newsgroups: comp.software-eng
Subject: Team Organization
Date: 28 Sep 92 18:03:29 GMT

Hi,

I hope this is the correct newsgroup to get this started in. If you feel
that it would also be appropriate to others let me know or post it
yourself.

The company that I work for is currently changing from an MIS department
to a *real* software shop. As part of this process we are evaluating
changes to our team structure, methodologies, etc. We felt that it might
be a good idea to ask others in industry how their organizations are
set-up so that we can try to make the correct decisions early on. 

We are a small group (~15 programmers currently) , but as soon as we add
a client then it could easily double in size. Weneed information on
actual grouping of teams, job descriptions, incentive programs. WE would
prefer information on modern flat management type organizations. If you
would consider sharing some of your information on these areas pleasse
contact me by e-mail at cwh@raphael.acpub.duke.edu. This is one time
when I would like lots of responses, so if you have anything to share
along these liens please do respond.

Thanks in advance,
Wally Holt
Programmer/Analyst
Teleflex Information Systems, Inc.
.
Newsgroups: comp.software-eng
From: nh@cbnewsg.cb.att.com (nicholas.hounsome)
Subject: Re: Request for Info: SADT or IDEF activity modeling tools
Organization: AT&T
Date: Fri, 2 Oct 1992 07:48:09 GMT

From article <wrb2.717993681@Ra.MsState.Edu>, by wrb2@Ra.MsState.Edu (Warren R Bennett):
> I work for the U.S. Army in a research laboratory.  We are using IDEF
> to model business processes.  We want to use these models to drive
> subsequent designs of automated information systems.
> 
> I am looking for tools that assist the business process modeler by
> storing SADT or IDEF activity models in a repository, presenting the 
> activity models on screen and hard copy and able to produce reports of 
> the stored objects.
> 
> Any help is greatly appreciated.
> 
> Warren Bennett (u4imcwb1@wescs1.wes.army.mil)
> 

Verilog do CASE tools for SADT and SDL.

Verilog Inc.
3010 LBJ Freeway
Suite 900
DALLAS
TEXAS 75234

It seems okay if you like that sort of thing - we mainly use the SDL.

Nick Hounsome
AT&T Network Systems
From: hasker@m.cs.uiuc.edu (Rob Hasker)
Newsgroups: comp.software-eng
Subject: Re: Do Software Engineers Actualy Do So Badly?
Date: 6 Oct 92 19:04:53 GMT
Article-I.D.: m.1992Oct6.190453.14230
Organization: University of Illinois, Dept. of Comp. Sci., Urbana, IL

kmagel@plains.NoDak.edu (ken magel) writes:

>     As a second example, we are moving in to a new $11 million
>dollar building next month.  During one redrawing of the diagrams for 
>a portion of that building, the architect left off the white boards for 
>all faculty offices in our portion of the building.

Even bigger mistakes abound:  Here at U. of Illinois in Urbana-Champain,
the newly constructed computer science building was to have a glass-covered
atrium.  This was sort of nice, because it meant that by giving inside
offices windows onto the atrium, those offices could get nice cheary
sunlight.  Well, somewhere late in the design process, they discovered that
this would mean that it would be impractical to cool the atrium, so they
covered it with metal instead, so the building is pretty dreary inside.
Now the office windows only serve to let others see in while you're working
(annoying when you're in a corridor with lots of traffic).

At this point, the building plans probably should have been scrapped and
they should have come up with something better.  Unfortunately, it was
discovered too late in the design process (or possibly when they started
to build), and the building was built with a roofed-in atrium.  (At least,
this is the story told me by one of the professors who was involved in
the design process.)

So I see no real reason why software engineers should hang their heads
in apology.  We aren't the only ones to make mistakes.

Rob
From: martinc@grover.cs.unc.edu (Charles R. Martin)
Newsgroups: comp.software-eng
Subject: *Theory* of configuration management
Date: 29 Sep 92 02:28:25 GMT
Distribution: comp
Organization: UNC Department of Computer Science

Has anyone read anything about the theory of configuration management?
That is, not "this is a new CM system" but "this is the mathematical
basis that underlies CM"?

Any pointers gratefully accepted....
--
Charles R. Martin/(Charlie)/martinc@cs.unc.edu/(ne crm@cs.duke.edu) 
O/Dept. of Computer Science/CB #3175 UNC-CH/Chapel Hill, NC 27599-3175
H/3611 University Dr #13M/Durham, NC 27707/(919) 419 1754
----------------------------------------------------------------------
"I am he who walks the States with a barb'd tongue, questioning every
one I meet,/Who are you that wanted only to be told what you knew
before?/ Who are you that wanted only a book to join you in your
nonsense?"  _Leaves of Grass_ xxiii.4.
Newsgroups: comp.software-eng
From: sharma@mcs.kent.edu (Naveen Sharma)
Subject: Looking for a good KBSE book.
Originator: sharma@Condor.mcs.kent.edu
Organization: Kent State University
Date: Tue, 6 Oct 1992 22:40:01 GMT

 Hi netters,
    I am looking for a good Graduate level text for 
    Knowledge Based Software Engineering.

    I would like to use the text as a reference in my research 
    mostly.

    Thanks for help

__________________________________________________________________________
Naveen Sharma	  		                |                  /      \
Research Associate                              |      /  ---      /     |
Institute for Computational Mathematics         |<     /  ----     /       |
Department of Mathematics and Computer Science  |<__    / ____     /       |
Kent State University		    		|  | O| | |   | O| | |O  | |
Kent Ohio 44242 		    		|  |  | | | O |  | | |-- | | 
e-mail: sharma@mcs.kent.edu          (internet)	|  |O |_| |/  |  |_| |___| |
----------------------------------------------------------------------------
From: bryk@IDA.ORG (Bill Brykczynski)
Subject: Rework estimates for SW
Organization: IDA, Alexandria, VA
X-Newsreader: Tin 1.1 PL4
Date: Mon, 5 Oct 92 18:51:42 GMT

I am looking for published data regarding the magnitude of
rework that occurs during the software development lifecycle.  I've
seen pie charts that maintain that testing occupies about half of the 
software development lifecycle (i.e., requirements, design, code,  
test).  I suspect that much of that testing effort is due to rework caused
by defects in the requirements, design, and code.  However, I 
have found very little reference to rework in the literature.  Any
pointers would be greatly appreciated.  Thanks.
 
bill
----

Newsgroups: comp.software-eng
From: jon@cs.washington.edu (Jon Jacky)
Subject: Re: *Theory* of configuration management
Summary: Woodcock and Loomes, SOFTWARE ENGINEERING MATHEMATICS, pps 100-109
Keywords: Configuration management, formal methods, Z
Organization: Computer Science & Engineering, U. of Washington, Seattle
Distribution: comp
Date: Tue, 29 Sep 92 16:21:49 GMT

In article <MARTINC.92Sep28222825@grover.cs.unc.edu> martinc@grover.cs.unc.edu (Charles R. Martin) writes:
>Has anyone read anything about the theory of configuration management?
>That is, not "this is a new CM system" but "this is the mathematical
>basis that underlies CM"?
>

See section 6.4, pps. 100 - 109, "A Configuration Manager," in Jim Woodcock and
Martin Loomes' excellent textbook, SOFTWARE ENGINEERING MATHEMATICS, 
Addison-Wesley, 1989.  It's a tutorial that uses CM to motivate some material
about relations and introduce the schema, a central constuct in the Z notation.

- Jon Jacky, jon@radonc.washington.edu, University of Washington, Seattle


Newsgroups: comp.software-eng
From: wrb2@Ra.MsState.Edu (Warren R Bennett)
Subject: Request for Info: SADT or IDEF activity modeling tools
Keywords: SADT IDEF
Organization: Mississippi State University
Date: Fri, 2 Oct 1992 02:41:21 GMT

I work for the U.S. Army in a research laboratory.  We are using IDEF
to model business processes.  We want to use these models to drive
subsequent designs of automated information systems.

I am looking for tools that assist the business process modeler by
storing SADT or IDEF activity models in a repository, presenting the 
activity models on screen and hard copy and able to produce reports of 
the stored objects.

Any help is greatly appreciated.

Warren Bennett (u4imcwb1@wescs1.wes.army.mil)
From: belen@rabbit.inesc.pt (Belen de Vicente)
Newsgroups: comp.software-eng
Subject: Too many standards
Keywords: 2167A, IEEE, ISO
Date: 2 Oct 92 16:14:26 GMT
Organization: INESC - Portugal

Hi!

I'm a little confused with software engineering standards, there are
so many: DoD-2167A, ANSI/IEEE, ISO, ...

I would like to classify them in order to have a clue to decide
when I should choose one or another!
Can anyone help me?

Are there also any european standards being used as much as american ones?

Which is the rigth way to select an standard when you do not have
one already imposed?

Too many questions, I'm sorry.

I would appreciate any help.
-- 

	Belen de Vicente
	E-mail.- belen@rabbit.inesc.pt
From: bert@unirsvl.RSVL.UNISYS.COM
Newsgroups: comp.software-eng
Subject: Code Inspection Tools Wanted
Date: 26 Sep 92 16:10:23 GMT

I'm looking for information on code inspection tools for C and/or C++.
Commercial, free, shareware, DOS, Unix etc. is OK.
Pointers to journal articles about the subject would be appreciated as well.

Thanks,

Bert Hyman
Unisys
Roseville, MN
(612) 635-7791
bert@rsvl.unisys.com