From rbotting@wiley.csusb.edu Sat Feb 5 20:47 PST 1994 Return-Path: Received: from wiley.csusb.edu by silicon.csci.csusb.edu (5.0/SMI-SVR4) id AA25704; Sat, 5 Feb 94 20:46:43 PST Received: by wiley.csusb.edu (5.67a/1.34) id AA03521; Sat, 5 Feb 1994 20:47:57 -0800 Date: Sat, 5 Feb 1994 20:47:57 -0800 From: rbotting@wiley.csusb.edu ("Dr. Richard Botting") Message-Id: <199402060447.AA03521@wiley.csusb.edu> To: dick@silicon.csci.csusb.edu Subject: (fwd) FAQ 1: comp.software-eng questions and answers Newsgroups: comp.software-eng Content-Type: text Content-Length: 14038 Status: RO Newsgroups: comp.software-eng,comp.answers,news.answers Path: csus.edu!netcom.com!netcomsv!decwrl!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!qucis.queensu.ca!dalamb From: dalamb@qucis.queensu.ca (David Alex Lamb) Subject: FAQ 1: comp.software-eng questions and answers Message-ID: Followup-To: comp.software-eng Keywords: FAQ Sender: dalamb@qucis.queensu.ca (David Lamb) Supersedes: Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb) Organization: Computing and Information Science, Queen's University at Kingston, Ontario, K7L 3N6, Canada References: Date: Sat, 5 Feb 1994 13:05:14 GMT Approved: news-answers-request@MIT.Edu Expires: Sat, 26 Mar 1994 13:05:06 GMT Lines: 311 Xref: csus.edu comp.software-eng:15930 comp.answers:3681 news.answers:17815 Last-Modified: 30 Nov 1993 Archive-name: software-eng/part1 This message gives brief answers to questions that have occurred in comp.software-eng; in many cases they are also topics many readers would like NOT to see discussed again soon. Questions are: What's a CASE Tool? What's a 'function point'? What's the 'spiral model'? What is a 'specmark'? Where can I find a public-domain tool to compute metrics? How do I write good C style? What is 'Hungarian Notation'? Are lines-of-code (LOC) a useful productivity measure? Should software professionals be licenced/certified? How do I get in touch with the SEI? What is the SEI maturity model? Where can I get information on API? What's a 'bug'? Where can I get copies of standards?? ------------------------------------------------------------------------ Subject: What's a CASE Tool? Date: 26 Mar 1993 (see also the archive file "casemsg") (thanks to Scott McGregor for inspiring this question) CASE stands for Computer Aided Software Engineering; it can be used to mean any computer-based tool for software planning, development, and evolution. Various people regularly call the following 'CASE': Structured Analysis (SA), Structured Design (SD), Editors, Compilers, Debuggers, Edit-Compile-Debug environments, Code Generators, Documentation Generators, Configuration Management, Release Management, Project Management, Scheduling, Tracking, Requirements Tracing, Change Management (CM), Defect Tracking, Structured Discourse, Documentation editing, Collaboration tools, Access Control, Integrated Project Support Environments (IPSEs), Intertool message systems, Reverse Engineering, Metric Analyzers. ------------------------------------------------------------------------ Subject: What's a 'function point'? Date: 31 Jul 1993 (see also the archive file "funcpoints") Function points and feature points are methods of estimating the "amount of functionality" required for a program, and are thus used to estimate project completion time. The basic idea involves counting inputs, outputs, and other features of a description of functionality. If interested, for a fee you can join: International Function Point Users Group 5008-28 Pine Creek Drive Blendonview Office Park Westerville, Ohio 43081-4899 ------------------------------------------------------------------------ Subject: What's the 'spiral model'? Date: 19 Sep 1991 (see also the archive file "spiral") (1) Barry Boehm, "A Spiral Model of Software Development and Enhancement", ACM SIGSOFT Software Engineering Notes, August 1986. (2) Barry Boehm "A Spiral Model of Software Development and Enhancement" IEEE Computer, vol.21, #5, May 1988, pp 61-72. Basically, the idea is incremental development, using the waterfall model for each step; it's intended to help manage risks. Don't define in detail the entire system at first. The developers should only define the highest priority features. Define and implement those. With this knowledge, they should then go back to define and implement more features in smaller chunks. ------------------------------------------------------------------------ Subject: What is a 'specmark'? Date: 19 Sep 1991 (see also the archive file "specmark") The SPECmark is the geometric mean of a series of benchmarks done by the SPEC group. There are a couple of suites, but in general SPECmark refers to the results of the first suite. The suite includes FORTRAN and C codes, mostly well known codes but slightly hacked versions. SPEC c/o NCGA 2722 Merrilee Drive, Suite 200 Fairfax, VA 22031 Phone: (703) 698-9600 FAX: (703) 560-2752 ------------------------------------------------------------------------ Subject: Where can I find a public-domain tool to compute metrics? Date: 17 Jan 1992 (see also the archive file "static") Volume 20 of newsgroup comp.sources.unix contained a public-domain package called "metrics", which computes McCabe and Halstead metrics. There are many comp.sources.unix archives around the net. ------------------------------------------------------------------------ Subject: How do I write good C style? Date: 19 Sep 1991 This is answered regularly in the comp.lang.c FAQ. Try "Recommended C style and Coding Standards", on host archive.cis.ohio-state.edu (128.146.8.52) via anonymous ftp in directory pub/style-guide. ------------------------------------------------------------------------ Subject: What is 'Hungarian Notation'? Date: 19 Sep 1991 (see also the archive file "hungarian") A naming convention for C code. See Charles Simonyi and Martin Heller, "The Hungarian Revolution", BYTE, Aug. 1991 (vol. 16, no. 8). There are other naming conventions; see, e.g. "A Guide to Natural Naming", Daniel Keller, ETH, Projekt-Zentrum IDA, CH-8092 Zurich, Switzerland. Published in SIGPLAN Notices, Vol. 25, No. 5, pages 95-102. ------------------------------------------------------------------------ Subject: Are lines-of-code (LOC) a useful productivity measure? Date: 26 Jan 1993 (see also the archive file "static") Not unless you are very careful. Capers Jones' book has a detailed and insightful discussion of Lines of Code, including anomalies, and shows how to use it sensibly (eg in a single job shop, with a single language, and a standard company coding style). It is easy to cook up anomalies where LOC gives different numbers for code written in different styles, but pathological cases should get caught in code inspections. References: - T. Capers Jones, Programming Productivity, McGraw-Hill, New York, 1986 - Capers Jones, Applied Software Measurement: Assuring Productivity and Quality, McGraw-Hill, Inc., 1991, 494 pages ISBN 0-07-032813-7 The appendices of the latter give rules for counting procedural source code, as well as rules for counting function points and feature points. The following study, cited in Boehm's _S_o_f_t_w_a_r_e _E_n_g_i_n_e_e_r_i_n_g _E_c_o_n_o_m_i_c_s, claims that anomalies that seriously "fool" the LOC metric show up rarely in real code. - R. Nelson _S_o_f_t_w_a_r_e _D_a_t_e _C_o_l_l_e_c_t_i_o_n _a_n_d _A_n_a_l_y_s_i_s _a_t _R_A_D_C, Rome Air Development Center, Rome, NY. 1978. ------------------------------------------------------------------------ Subject: Should software professionals be licenced/certified? Date: 19 Sep 1991 This is a very controversial and political question. Generally, certification is something voluntary, while licencing is regulated by governments. Certification generally means some agency warrants you meet its standards; licencing generally means that to claim to practice a certain profession requires a government licence, often administered through a professional organization. In theory both are supposed to help judge if someone is capable of doing certain jobs. Licencing isn't currently required for computing professionals; some people would like to see some jobs require it, as with established branches of engineering. Others don't like government intervention, and/or believe many people who wouldn't get licenced are perfectly competent. Computing professionals in the USA have had a certification program for years, administered by the Institute for Certification of Computer Professionals (708-299-4227), a meta-organization with representatives from ACM, IEEE-CS, ADAPSO, ICCA, IACE, AIM, DPMA, AISP, COMMON, ASM, CIPS, and AWC. There are three certificates aimed at different broad types of practitioner, and many areas of specialization. To keep a certificate requires at least 40 hours of continuing education each year; credit can also be obtained for self-study, teaching, publication, etc. ------------------------------------------------------------------------ Subject: How do I get in touch with the SEI? Date: 29 Nov 1993 For general information about the SEI, contact the customer relations department of the Software Engineering Institute at: internet: customer-relations@sei.cmu.edu Phone: (412) 268-5800 A subscriber service is available to U.S. mailing addresses. Subscribers receive the SEI quarterly newsletter, Bridge; invitations to SEI public events; and first notification of course offerings and new publications. To become a subscriber, contact Customer Relations. To order an SEI publication, contact NTIS, DTIC, or RAI directly: National Technical Information Service (NTIS) U.S. Department of Commerce Springfield, VA 22161-2103 Telephone: (703) 487-4600 Defense Technical Information Center (DTIC) ATTN: FDRA Cameron Station Alexandria, VA 22304-6145 Telephone: (703) 274-7633 Research Access Inc. (RAI) 3400 Forbes Avenue Suite 302 Pittsburgh, PA 15213 Telephone: (412) 682-6530 FAX: (412) 682-6530 ------------------------------------------------------------------------ Subject: What is the SEI maturity model? Date: 31 Jan 1992 Originally-From: mcp@sei.cmu.edu (Mark Paulk) (see also the archive file "maturity") Maturity is not an easy concept to get down to a single paragraph, but consider this. Premise: The quality of a software system is largely governed by the quality of the process used to develop and maintain the software. Basics: The first step in improving the existing situation is to get management buy-in and management action to clean up the software management processes (walk the talk, as TQMers frequently say). Integration: The second step is to get everyone working together as a team. Measurement: The third step is to establish objective ways of understanding status and predict where things are going in your process. Continuous improvement: Understand that this is building a foundation for continually getting better. ------------------------------------------------------------------------ Subject: Where can I get information on API? Date: 14 Feb 1992 API stands for Application Programming Interface. For general information on API standards, you can look at NIST Spec. Pub. 500-187, "Application Portability Profile." (contact Barbara Blickenstaff, 301-975-2816). Many of the open systems APIs are being developed in the IEEE POSIX groups. An article in the Dec. 1991 IEEE Spectrum describes these and related API standards. IEEE standards aren't distributed electronically, but both of the documents above tell how to obtain copies. ------------------------------------------------------------------------ Subject: What's a 'bug'? Date: 12 May 1992 You can take your pick: (1) Don't use "bug", use "fault" (an incorrect instruction or definition), "failure" (an incorrect result), or "mistake" (a human action leading to a failure). Paraphrased from IEEE Standard Computer Dictionary Standard 610, ISBN 1-55937-079-3 Institute of Electrical and Electronic Engineers, Inc. 345 East 47th Street New York, NY 10017-2394 USA $49.50 (US$) for IEEE members (2) Beizer, in a footnote on page 33 of the second edition of _S_o_f_t_w_a_r_e _T_e_s_t_i_n_g _T_e_c_h_n_i_q_u_e_s says (paraphrased): I'm sticking with "bug" because everyone knows what it means, there are several "standards" for other terms that are incon- sistent with each other, the OED says that the conventional com- puter meaning of "bug" is ancient, and short Anglo-Saxon words are preferable to long Norman ones. ------------------------------------------------------------------------ Subject: Where can I get copies of standards?? Date: 26 Jan 1993 ISO, ANSI, and IEEE standards are usually sold to raise some of the funds that the various national and international standards bodies (who usually own the copyright) need to keep afloat; thus they are not normally avail- able electronically. Also, the organizations are concerned that electron- ic copies would make it too easy for people to disseminate doctored ver- sions of the standards. ISO standards may be purchased from: In Canada: Standards Council of Canada / Conseil canadien des normes 1200-45 O'Connor, Ottawa K1P 6N7 Phone: (613) 238-3222 Fax: (613) 995-4564 On CD-ROM: Omnicom, Inc. 115 Park St. SE Vienna, VA 22180-4607 1-800-OMNICOM Also available through the National Technical Information Service (NTIS), 5284 Port Royal Rd., Springfield, VA 22161, (703) 487-4650. There were once some CCITT standards on-line at the University of Colorado, but the arrangement to make them available via the Internet was terminated at the end of 1991. -- Software Technology Laboratory dalamb@qucis.queensu.ca (David Alex Lamb) Computing and Information Science phone: (613) 545-6067 Queen's University, Kingston, Ontario, Canada K7L 3N6 -- rbotting@wiley.csusb.edu. rbotting::=`Dr. Richard J. Botting`, wiley::=`Faculty EMail System`, csusb::=`California State University, San Bernardino, CA 92407, USA`. From rbotting@wiley.csusb.edu Sat Feb 5 20:47 PST 1994 Return-Path: Received: from wiley.csusb.edu by silicon.csci.csusb.edu (5.0/SMI-SVR4) id AA25703; Sat, 5 Feb 94 20:46:42 PST Received: by wiley.csusb.edu (5.67a/1.34) id AA03517; Sat, 5 Feb 1994 20:47:55 -0800 Date: Sat, 5 Feb 1994 20:47:55 -0800 From: rbotting@wiley.csusb.edu ("Dr. Richard Botting") Message-Id: <199402060447.AA03517@wiley.csusb.edu> To: dick@silicon.csci.csusb.edu Subject: (fwd) Comp.software-eng periodic postings and archives Newsgroups: comp.software-eng Content-Type: text Content-Length: 13467 Status: RO Newsgroups: comp.software-eng,comp.answers,news.answers Path: csus.edu!netcom.com!netcomsv!decwrl!uunet!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!qucis.queensu.ca!dalamb From: dalamb@qucis.queensu.ca (David Alex Lamb) Subject: Comp.software-eng periodic postings and archives Message-ID: Followup-To: comp.software-eng Keywords: FAQ Sender: dalamb@qucis.queensu.ca (David Lamb) Supersedes: Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb) Organization: Computing and Information Science, Queen's University at Kingston, Ontario, K7L 3N6, Canada Date: Sat, 5 Feb 1994 13:05:11 GMT Approved: news-answers-request@MIT.Edu Expires: Sat, 26 Mar 1994 13:05:06 GMT Lines: 236 Xref: csus.edu comp.software-eng:15933 comp.answers:3684 news.answers:17818 Last-Modified: 4 Aug 1993 Archive-name: software-eng/part0 Welcome to comp.software-eng, a newsgroup for discussion of software engineering and related topics. This message is followed by three others, each summarizing a set of "frequently asked questions" (FAQs): FAQ 1: comp.software-eng questions and answers FAQ 2: CASE tools summary FAQ 3: Software engineering readings Be warned: the only mechanism we use to compose these lists is to gather information submitted by people around the net, post it regularly, and incorporate feedback. All evaluations are the opinions of those who submitted them; your mileage may vary. Send comments to dalamb@qucis.queensu.ca (David Alex Lamb). Many FAQs, including this one, are available on the archive site rtfm.mit.edu in the directory pub/usenet/news.answers. The name under which a FAQ is archived appears in the Archive-name line at the top of the article. This FAQ, and the parts that follow, are archived as software-eng/part0 through software-eng/part3. ------------------------------------------------------------------------ Subject: other newsgroups The following other newsgroups discuss topics related to software engineering; consequently, coverage of these topics in this newsgroup (and thus the comp.software-eng archives) tends to be sparse. Many of these groups have their own FAQ's, which you can find in the appropriate *.answers group (e.g. comp.answers for any group whose name starts with "comp."). comp.groupware Software & hardware for shared interactive environments comp.lang.* Discussion of specific programming languages. comp.newprod Announcements of new products comp.object Object-oriented analysis, design, programming, & systems comp.programming Programming, especially algorithms and data structures comp.realtime Computer-based realtime systems comp.specification Formal specification methods comp.specification.z The Z formal specification notation comp.sw.components Reusable software components ------------------------------------------------------------------------ Subject: comp.software-eng archives The following files are available via anonymous FTP from directory pub/software-eng on host ftp.qucis.queensu.ca (130.15.1.93). Log in with user ID 'anonymous' and use your mailing address as the password. Each file has a header (in e-mail or news format) that credits the original collector. If you cannot use FTP, send mail to archive-server@qucis.queensu.ca containing a line of the form send software-eng f1 f2 ... where f1, f2, and so on are the names of the files from this list; the mail server should respond within an hour or so plus mailing delays (which can themselves be substantial if you're not directly on the internet). If you want to find out more about the archive server, send mail to the same address with a line containing the word 'help'; if you do this you can't also request files in the same message. If your mailer has trouble with large files, use the 'size ' command to set a threshold, above which the server will split files into several messages. Name Changed Description faqmsg 31 Jul 1993 comp.software-eng periodic postings and archives questmsg 31 Jul 1993 FAQ 1: comp.software-eng questions and answers casemsg 31 Jul 1993 FAQ 2: CASE tools summary readmsg 31 Jul 1993 FAQ 3: Software engineering readings README 31 Jul 1993 This list of files 2167a 31 Jul 1993 DoD-Std-2167a and life cycle models ada 26 Jan 1993 bibliography on Ada and software engineering aiswe 13 May 1992 readings: artificial intelligence and soft.eng. anecdote 31 Jul 1993 Anecdotes/stories about software engineering bachman 10 Sep 1991 Bachman information modeling bookTOC 9 Jul 1993 Tables of contents of books bookreview 10 Apr 1992 Book reviews CASEexp 2 Oct 1991 experience with CASE tools cdif 31 Jul 1993 CASE Data Interchange Format cleanroom 30 Jul 1993 Cleanroom software development cmtools 31 Jul 1993 Configuration management tools color 4 Jun 1992 Ergonomics of color displays concur 31 Jul 1993 Concurrent Engineering cubicle 28 Feb 1992 Productivity effect of offices vs. cubicles defect 26 Mar 1993 Defect tracking designchange 7 Jul 1992 Effect of design changes diagramedit 31 Jul 1993 Diagram editors and tools for building them education 30 Jul 1993 Software Engineering education and degree programs environment 15 May 1992 Software Engineering environments ethics 11 Dec 1992 ACM code of ethics facet 18 Sep 1991 Faceted classification and multiple inheritance fault 7 Jul 1992 Fault Tolerance references formal 31 Jul 1993 formal methods in the USA funcpoints 10 Apr 1992 function/feature points hood 2 Oct 1991 Hierachical Object-Oriented Design horror 31 Jul 1993 Computer horror stories hungarian 11 Oct 1991 papers on Hungarian notation ieee 2 Oct 1991 IEEE software engineering standards inspect 30 Jul 1993 Code inspection techniques knowuser 31 Jul 1993 Discussion on whether to ``know the user'' lotos 31 Jul 1993 Language of Temporal Ordering of Specifications maint 9 Apr 1992 Software maintenance laws manuals 6 Mar 1992 Guidelines for software manuals maturity 31 Jul 1993 SEI Capability Maturity Model oodb 30 Jul 1993 Object-oriented databases ooformat 10 Jan 1992 Format for object-oriented design documents oomaint 10 Apr 1992 maintenance and complexity in o-o systems oomethod 31 Jul 1993 Object-oriented methodologies pdcase 7 Jul 1992 Public-domain CASE tools performance 26 Mar 1993 performance analysis tools petri 7 Jul 1992 Petri net tools pmtools 30 Jul 1993 Project management and design tools portableC 30 Jul 1993 writing portable C code probtrack 13 Apr 1992 Problem tracking tools productivity 18 Sep 1991 Feature point productivity for several countries proto 7 Jul 1992 Prototyping readcase 13 Feb 1992 Bibliography on CASE readintro 15 Feb 1992 Introducing your manager/customer to SE ideas realtime 15 Feb 1992 Information on realtime software development reflist 22 May 1992 Tero Ahtee's software engineering reference list reqelicit 31 Jul 1993 Requirement Elicitation restruct 7 Jul 1992 Tools for restructuring and reverse engineering reuse 31 Jul 1993 Discussion of software re-use. safety 31 Jul 1993 Formal methods and software safety SEorigin 31 Jul 1993 Origin of term ``software engineering'' specmark 15 Feb 1992 SPEC modern architecture benchmarks spiral 10 Jan 1992 References on Spiral life-cycle model standards 31 Jul 1993 standards relevant to software engineering statecharts 15 Feb 1992 Reference list on Harel's statecharts static 31 Jul 1993 Software metrics and static analysis statsTool 21 Oct 1991 X-based statistics and graphing packages strucAD 31 Jul 1993 Stuctured analysis and design and SADT syslevel 30 Jul 1993 Realtime/hardware system-level CASE tools techTransfer 10 Apr 1992 Technology transfer testing 31 Jul 1993 Discussion of testing (and inspection) testTools 31 Jul 1993 Tools for testing transynth 15 Feb 1992 Transformation/synthesis systems uims 3 Aug 1993 User Interface Management Systems vdm-z 31 Jul 1993 formal methods Z and VDM verification 10 Apr 1992 References on program verifier design ------------------------------------------------------------------------ Subject: more detailed information on specific products The following files are in the "blurb" subdirectory of the software engineering archives at qucis.queensu.ca; retrieve them as described for the main archives, except that for the mail archive server you say send software-eng/blurb f1 f2 .... The files consist of comments on individual products or companies. When a vendor sends me detailed information on a product that won't fit into the FAQ, I put it here - along with other comments from the net. Name Changed Description FIELD 9 Jul 1993 Brown University FIELD environment IFAD 9 Jul 1993 VDM-SL toolbox PCTE-ATIS-CAIS 31 Jul 1993 Discussion of PCTE vs ATIS vs CAIS ParaSET 9 Jul 1993 parametric software development PurePulse 9 Jul 1993 Pure software newsletter aegis 29 Mar 1993 project change supervisor autoplan 26 Jan 1993 project scheduling tool cadreTeam 31 Jul 1993 Cadre TEAMWORK caseware 26 Jan 1993 configuration management and problem tracking cvs 30 Jul 1993 CVS version management tool ief 31 Jul 1993 TI Information Engineering Facility jaloteSEtext 31 Jul 1993 P.Jalote's "An Integrated Approach to Software Engi objectime 26 Mar 1993 real-time object-oriented methodology parcplace 22 Mar 1993 Smalltalk and C++ tools rational 26 Jan 1993 Rational Inc. Ada environment, Rose OOD tool razor 26 Jan 1993 issue tracking, configuration management rcs 5 Oct 1992 version control system rdd-100 31 Jul 1993 Requirements Driven Developer robochart 26 Jan 1993 diagram editor schach2e 28 Apr 1993 Schach's "Basic Software Engineering" text sextant 9 Jul 1993 UNIX/C environment shapetools 26 Jan 1993 shapetools version management/make-like tool specbox 31 Jul 1993 VDM support tool stp-teamwork 31 Jul 1993 Comparison of Software Thru Pictures and Cadre Team telelogic 26 Jan 1993 Environment for CCITT SDL vista 26 Mar 1993 Vista Technologies ------------------------------------------------------------------------ Subject: WAIS server I have created a WAIS database that indexes the comp.software-eng archives. It's still experimental; I'm still playing with appropriate "file types" for the various files, so you get a subsection of a file in response to a query, instead of the whole giant file (at the moment only a few of the files are subdivided, and not always in a useful way). The .src file follows at the end of this message. The following is taken from the WAIS FAQ.txt file: WAIS is available via anonymous FTP from a variety of sources. The main distributor is think.com, in the wais subdirectory. a. a mac client? think.com:/wais/WAIStation0.62.hqx b. a unix client? a few UNIX based clients are available in the core distribution, which can be found on think.com: think.com:/wais/wais-8-b#.tar.Z, where # is the most recent version (4 at this time). This includes the server, and clients for X Windows, GNU Emacs and a couple of simple shell-based clients. c. a dos client? The University of North Carolina has been a main developement site for WAIS software. Several DOS clients can be found in the FTP archives on wais.oit.unc.edu. d. a NeXT client? A client for NeXT can be found in think.com:/wais/XXX e. a VMS client? WAIS has been ported to VMS by the folks at the University of North Carolina. f. the server? An example WAIS server is part of the core distribution. (:source :version 3 :ip-address "130.15.1.93" :ip-name "ftp.qucis.queensu.ca" :tcp-port 210 :database-name "software-eng" :cost 0.00 :cost-unit :free :maintainer "dalamb@qucis.queensu.ca" :description "Server created with WAIS release 8 b5.1 on Jun 17 16:10:48 1993 by dalamb@quilt The files of type mail_digest used in the index were: /usr/local/ftp/pub/software-eng/casemsg /usr/local/ftp/pub/software-eng/questmsg /usr/local/ftp/pub/software-eng/readmsg /usr/local/ftp/pub/software-eng/color /usr/local/ftp/pub/software-eng/testTools /usr/local/ftp/pub/software-eng/pmtools /usr/local/ftp/pub/software-eng/static /usr/local/ftp/pub/software-eng/petri /usr/local/ftp/pub/software-eng/inspect /usr/local/ftp/pub/software-eng/proto /usr/local/ftp/pub/software-eng/fault /usr/local/ftp/pub/software-eng/performance " ) -- Software Technology Laboratory dalamb@qucis.queensu.ca (David Alex Lamb) Computing and Information Science phone: (613) 545-6067 Queen's University, Kingston, Ontario, Canada K7L 3N6 -- rbotting@wiley.csusb.edu. rbotting::=`Dr. Richard J. Botting`, wiley::=`Faculty EMail System`, csusb::=`California State University, San Bernardino, CA 92407, USA`. From rbotting@wiley.csusb.edu Sat Feb 5 20:47 PST 1994 Return-Path: Received: from wiley.csusb.edu by silicon.csci.csusb.edu (5.0/SMI-SVR4) id AA25706; Sat, 5 Feb 94 20:46:47 PST Received: by wiley.csusb.edu (5.67a/1.34) id AA03529; Sat, 5 Feb 1994 20:48:01 -0800 Date: Sat, 5 Feb 1994 20:48:01 -0800 From: rbotting@wiley.csusb.edu ("Dr. Richard Botting") Message-Id: <199402060448.AA03529@wiley.csusb.edu> To: dick@silicon.csci.csusb.edu Subject: (fwd) FAQ 3: Software engineering readings Newsgroups: comp.software-eng Content-Type: text Content-Length: 32649 Status: RO Newsgroups: comp.software-eng,comp.answers,news.answers Path: csus.edu!netcom.com!netcomsv!decwrl!sdd.hp.com!vixen.cso.uiuc.edu!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!qucis.queensu.ca!dalamb From: dalamb@qucis.queensu.ca (David Alex Lamb) Subject: FAQ 3: Software engineering readings Message-ID: Followup-To: comp.software-eng Keywords: FAQ Sender: dalamb@qucis.queensu.ca (David Lamb) Supersedes: Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb) Organization: Computing and Information Science, Queen's University at Kingston, Ontario, K7L 3N6, Canada References: Date: Sat, 5 Feb 1994 13:05:29 GMT Approved: news-answers-request@MIT.Edu Expires: Sat, 26 Mar 1994 13:05:06 GMT Lines: 581 Xref: csus.edu comp.software-eng:15932 comp.answers:3683 news.answers:17817 Last-Modified: 31 Jul 1993 Archive-name: software-eng/part3 This is the monthly "frequently asked questions" (FAQ) posting on reading materials for software engineers. Topics include: Textbooks Periodicals on Software Engineering Other sources of information General reading for software engineers Metrics Metrics for object-oriented systems User Interface Design Human Factors Software Testing Requirements Analysis Collaborative Requirements Analysis Object-Oriented Analysis and Design Programming Style Formal Specification Software Process Look for lines starting with "Subject:" (control-G command in rn). Be warned: the only mechanism we use to compose this list is to gather information submitted by people around the net, post it regularly, and incorporate feedback. All evaluations are the opinions of those who submitted them; your mileage may vary. Send comments to dalamb@qucis.queensu.ca (David Alex Lamb). ------------------------------------------------------------------------ Subject: Textbooks Date: 28 Apr 1993 Originally collected by: hsrender@happy.colorado.edu (Hal Render) Numbers 1-8 are Hal Render's original list in his rough order of preference. 1. _Software Engineering: The Production of Quality Software_ by Shari Pfleeger, 2nd Edition, Macmillan, 1991, ISBN 0-02-395115-X hsrender@happy.colorado.edu: Like #2, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). 2. _Software Engineering: A Practitioner's Approach_ by Roger Pressman, 2nd Edition, McGraw-Hill, 1987, ISBN 0-07-050783-X (3rd edition available fall 1991) hsrender@happy.colorado.edu: Like #1, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). robb@iotek.uucp (Robb Swanson): the definitive book on the subject as far as I'm concerned. johnson@aplcen.apl.jhu.edu (Michelle Johnson): a good text book as well as reference 3. _Software Systems Engineering_ by Andrew Sage and James D. Palmer hsrender@happy.colorado.edu: Like #1, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). 4. _Fundamentals of Software Engineering_ by Ghezzi, Jayazeri and Mandrioli Prentice-Hall, 1991 hsrender@happy.colorado.edu: Like #5, good, and covered the issue of specifications and verification better, but at the expense of other aspects of the development process. I may use one of them for a graduate course in software engineering. Nancy Leveson : Better than Sommerville, although I like much of Sommerville. 5. _Software Engineering with Abstractions_ by Valdis Berzins and Luqi Addison Wesley, 1991, 624 pages. hsrender@happy.colorado.edu: Like #4, good, and covered the issue of specifications and verification better, but at the expense of other aspects of the development process. I may use one of them for a graduate course in software engineering. straub@cs.UMD.EDU (Pablo A. Straub): Both this and #9 have a good emphasis on using formal techniques (i.e., doing engineering properly), but they do not disregard informal methods; chapters are roughly organized around the traditional lifecycle. #5 is longer and can be used in a two-term sequence or for graduate students (it's possible to use it in a one-term undergrad course by covering only part of the material). One thing I like is that management and validation is given in all chapters, so that these activities are integrated into the development process. Emphasizes the use of formally specified abstractions. Uses the authors' specification language (Spec) to develop a project in Ada. 6. _Software Engineering_ by Ian Sommerville Addison-Wesley, ISBN 0-201-17568-1 hsrender@happy.colorado.edu: Our current text, and my basic problem with it is the vague way it covers many of the topics. 7. _Software Engineering with Student Project Guidance_ by Barbara Mynatt hsrender@happy.colorado.edu: Like #8, not bad, but fairly low-level and doesn't cover many tools and techniques I consider valuable. 8. _Software Engineering_ by Roger Jones hsrender@happy.colorado.edu: Like #7, not bad, but fairly low-level and doesn't cover many tools and techniques I consider valuable. 9. _Software Engineering: Planning for Change by David Alex Lamb, Prentice-Hall, 1988, 298 pages straub@cs.UMD.EDU (Pablo A. Straub): Both this and #5 have a good emphasis on using formal techniques (i.e., doing engineering properly), but they do not disregard informal methods; chapters are roughly organized around the traditional lifecycle. #9 has the advantage of being shorter, yet covering most relevant topics (lifecycle phases, formal specs, v&v, configurations, management, etc.). It is very appropriate for an undergrad course. It emphasizes that maintenance is a given and should be taken into account (hence the title). Several specification techniques are covered and used to develop a project in Pascal. 10._A Practical Handbook for Software Development_ by N.D. Birrell and M.A. Ould, Cambridge University Press, 1985/88. ISBN 0-521-34792-0 (Paper cover); ISBN 0-521-25462-0 (Hard cover) ewoods@hemel.bull.co.uk (Eoin Woods) 11._Fundamentals of Computing for Software Engineers_ by Eric S. Chan & Murat M. Tanik, Van Nostrand Reinhold kayaalp@csvax.seas.smu.edu (Mehmet M. Kayaalp MD) 12._Software Engineering, 2nd Edition_ by Stephen R. Schach, Aksen Associates (ISBN 0-256-12998-3); also Richard D. Irwin, Inc., 1993. 13._Practical Software Engineering_ by Stephen R. Schach, Aksen Associates and Richard D. Irwin Inc. (ISBN 0-256-11455-2), 1992. Advertised as sophomore through senior level, emphasizing teams, maintenance, reuse, CASE tools. ------------------------------------------------------------------------ Subject: Periodicals on Software Engineering Date: 12 May 1992 Professional Journals Meant for working professionals with technical backgrounds. IEEE Software summary: often presents recent research work, but much more readably than typical research journals. publisher: IEEE (Institute of Electrical and Electronic Engineers) subscriptions: IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331, USA Software Engineering Notes summary: unrefereed newsletter; includes digest of comp.risks publisher: ACM (Association for Computing Machinery) SIGSOFT (Special Interest Group on Software engineering), subscriptions: ACM, 11 West 42d St, New York, NY 10036, USA Software Maintenance News summary: monthly report on people and technology in maintenance; aimed at practitioners publisher: Software Maintenance News Inc, B10 Suite 237, 4546 El Camino Real, Los Altos, CA 94022, USA subscriptions: as above Software Testing, Verification and Reliability summary: aimed at practitioners; dissemination of new techniques, methodologies and standards publisher: John Wiley & Sons Ltd, Baffins Lane, Chichester, West Sussex PO19 1UD, UK The Software Practitioner (TSP) summary: started late 1990; meant for real practitioners; still finding its place publisher: Computing Trends, P.O. Box 213, State College, PA 16804, USA Mixed Research and Practice Journal of Software Maintenance: Research and Practice summary: refereed; intended for both researchers and practitioners; joint US/UK editorial board publisher: Wiley (see above) subscriptions: Journals Subscription Department, at above address Software Engineering Journal (SEJ) summary: full spectrum of articles from practical experience to long-term research publisher: IEE (Institution of Electrical Engineers) and BCS (British Computer Society); write to IEE Publication Sales, PO Box 96, Stevenage, Herts, SG1 2SD, United Kingdom. Software: Practice and Experience summary: not always software engineering; good reputation for practice publisher: Wiley (see above) The Software Quality Journal summary: academic research and industrial case studies and experience publisher: Chapman & Hall, Journals Promotion Department North America:29 West 35th Street, New York, NY 10001-2291, USA Europe: 2-6 Boundary Row, London SE1 8HN, UK Research Journals Meant for presenting recent research results. Information and Software Technology (IST) summary: broad spectrum, much software engineering, software process, but also computer science topics. publisher: Butterworth-Heineman, Linacre House, Jordan Hill, Oxford, UK Transactions on Software Engineering (TSE) summary: main software engineering research journal publisher: IEEE (see above) Transaction on Software Engineering Methodology (TOSEM) summary: first issue dated January 1992; not enough track record for an opinon yet. publisher: Association for Computing Machinery Journal of Systems and Software summary: meant to be more practitioner-oriented than other research journals publisher: Elsevier Other magazines: Software summary: "For Managers of Enterprise-Wide Software Resources" primarily aimed at Management Information Systems (MIS) world publisher: Sentry Publishing Company, Inc, 1900 West Park Drive, Westborough, MA 01581, (508) 366-2031 ------------------------------------------------------------------------ Subject: Other sources of information Date: 1 Aug 1991 Software Quality Engineering has a publication division called Single Source, Publications, Books, and Information for Software Practitioners and Managers: Software Quality Engineering -- Single Source 3000-2 Hartley Road Jacksonville, FL 32257 (904) 268-8639 FAX (904) 268-0733 TOLL FREE 1-800-423-8378 They do regular reviews of most of the literature relevant to testing, s-eng, and management. The books which are deemed useful by the reviewers are purchased for reselling. Their catalog includes most of the literature that I've come across on Software Testing. One of the items in the catalog is a publication which the company puts together itself, The Testing Tools Reference Guide, a sort of catalog of tools that have passed certain criteria, (number of unit sold, at least three verifiable references, etc.) They charge $145.00 for this guide. This includes two bi-annual updates. I've found the guide very useful in tracking down vendors which specialize in CASE and testing tools, although it seems to be heavily biased towards IBM mainframe hardware and COBOL programming (shudder!). Each text is described and summarized I'm sure SQE would be happy to send catalogs free of charge and most of the prices seem reasonable. - Glenn Stowe glenn8@odie.cs.mun.ca ------------------------------------------------------------------------ Subject: General reading for software engineers Date: 11 Oct 1991 Originally collected by: cml@cs.UMD.EDU (Christopher Lott) Summary: responses to "what should every software engineering have read?" 1. General a. Read about 100 pages of comp.risks b. Frederick P. Brooks, Jr., The Mythical Man-Month, Addison Wesley, 1978. ISBN 0-201-00650-2 c. The anecdotal books of Robert L. Glass, from Computing Trends, P.O.Box 213, State College, PA 16804, including: "Tales of Computing Folk: Hot Dogs and Mixed Nuts", "The Universal Elixir and other Computing Projects Which Failed", "The Second Coming: More Computing Projects Which Failed", "The Power of Peonage", "Computing Catastrophes", "Computing Shakeout", "Software Folklore" d. Paul W. Oman & Ted G. Lewis, Milestones in Software Evolution, IEEE Computing Society, ISBN 0-8186-9033-X. e. J.A. McDermid (editor), Software Engineer's Reference Book, Butterworth-Heinemann Ltd., 1991. ISBN No: 0 750 61040 9. Focuses on the foundations, and subject matter that is not volatile. The book is divided into three major parts: Theory and Mathematics; Methods, Techniques, and Technology; Principles of Applications. For a beginner, the first two parts are indispensible. It does not provide details of current research, but points an interested reader to the right sources. 2. Programming in the large a. Grady Booch, Software Engineering with Ada, second edition, Benjamin/Cummings, 1987 b. Bertrand Meyer, Object-Oriented Software Construction, Prentice-Hall, 1988. c. David L. Parnas, On the Criteria to be Used in Decomposing Systems into Modules, Communications of the ACM 15,2 (December 1972). 3. Programming in the small a. Jon Louis Bentley, Writing Efficient Programs, Prentice-Hall, 1982. b. Jon Bentley, Programming Pearls, Addison-Wesley, 1986. c. Jon Bentley, More Programming Pearls, Addison-Wesley, 1988. d. O.-J. Dahl, E.W. Dijkstra, C.A.R. Hoare, Structured Programming, Academic Press, 1972. e. Brian W. Kernighan, and P.J. Plauger, Software Tools, Addison-Wesley, 1976. f. Brian W. Kernighan & P.J. Plauger, The Elements of Programming Style, Second Edition, McGraw-Hill, 1978. ISBN 0-07-034207-5. 4. Mathematical Approaches a. Edsger W. Dijkstra, A Discipline of Programming, Prentice-Hall, 1976. b. E.W.Dijkstra. Selected writings on computing: a personal perspective. Springer Verlag, 1982. c. David Gries (editor), Programming methodology. A collection of articles by members of IFIP Working Group 2.3. Springer Verlag, 1978. 5. Other a. Barry W. Boehm, Software Engineering Economics, Prentice-Hall, 1981. b. Daniel P. Freedman and Gerald M. Weinberg, Handbook of Walkthoughs, Inspections and Technical Reviews, 3rd edition Dorset House Publishing, 1990, ISBN 0-932633-19-6. Originally published by Little, Brown & Company, 1982: ISBN 0-316-292826. c. Tom Gilb, Principles of Software Engineering Management, Addison-Wesley, 1988, ISBN 0-201-19246-2 d. Glenford J. Myers, The Art of Software Testing, Wiley, 1979. e. Herb Simon, The Sciences of the Artificial, Second Edition, MIT Press, 1981 f. Gerald M. Weinberg, The Psychology of Computer Programming, Van Nostrand Reinhold, 1971. ISBN 0-442-29264-3 ------------------------------------------------------------------------ Subject: Metrics Date: 31 Jul 1993 Thanks especially to Horst Zuse, who sent his extensive bibliography on metrics. He has an extensive database with over 500 entries on metrics; contact ZUSE%DB0TUI11.BITNET@vm.gmd.de. a. David N. Card and Robert L. Glass. Measuring Software Design Quality Prentice Hall, Engewood Cliffs, New Jersey, 1990 b. S.D. Conte, H.E. Dunsmore, V.Y. Shen. Software Engineering Metrics and Models. Benjamin/Cummings Publishing Company, Menlo Park, 1984 ISBN: 0- 8053-2162-4 c. Tom DeMarco. Controlling Software Projects: Management, Measurement and Estimation. Englewood Cliffs, N.J.: Prentice Hall, 1982 d. T.Denvir, R.Herman and R.Whitty (Eds.). Proceedings of the International BCS-FACS Workshop: Formal Aspects of Measurement, May 5, 1991, South Bank Polytechnic, London, UK, Series edited by Professor C.J. van Rijsbergen, ISBN 3-540-19788-5. Springer Publisher, 1992, 259 pages. e. Reiner Dumke. Softwareentwicklung nach Ma`s - Sch`atzen - Messen - Bewerten, Vieweg Verlag, 1992. f. Lem Ejiogu. Software Engineering with Formal Metrics. QED Information Sciences, 1991 g. N.E. Fenton, (Editor). Software Metrics: A Rigorous Approach, 1991 United Kingdom: Chapman & Hall, 2-6 Boundary Row, London SE1 8HN, ISBN 0-412- 40440-0. United States: Van Nostrand Reinhold, 115 5th Avenue, New York NY 10003, ISBN 0-442-31355-1. h. Robert B. Grady and Deborah L. Caswell. Software Metrics: Establishing a Company-Wide Program, Prentice-Hall, 1987, ISBN 0-13-821844-7 i. Robert B. Grady. Practical Software Metrics for Project Management and Process Improvement. Prentice Hall 1992 ISBN 0-13-720384-5 j. M.H. Halstead. Elements of Software Science. New York, Elsevier North- Holland, 1977 k. S. Henry, D. Kafura, "Software Structure Metrics Based on Information Flow", IEEE Transactions on Software Engineering, Vol.SE-7, No.5, September 1981. l. IEEE. Standard Dictionary of Measures to Produce Reliable Software. The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York. IEEE Standards Board, 1989 m. IEEE. Guide for the Use of Standard Dictionary of Measures to Produce Reliable Software. The Institute of Electrical and Electronics Engineers, Inc 345 East 47th Street, New York. IEEE Standard Board, Corrected Edition, October 23, 1989 n. T.J. McCabe, A Complexity Measure, IEEE Transactions on Software Engineering, VOL. SE-2, NO. 4, Dec. 1976. o. Alan Perlis, Frederick Sayward, Mary Shaw. Software Metrics: An Analysis and Evaluation. The MIT Press, 1981 p. V.Y. Shen, S.D. Conte, H.E. Dunsmore, Software Science Revisited: A Critical Analysis of the Theory and Its Empirical Support, IEEE Transactions on Software Engineering, Vol. SE-9, No. 2, March 1983. Abstract: a critical evaluation of Halstead's software science metric. q. Martin Sheppard, Software Engineering Metrics, McGraw-Hill Book Company (UK) Limited, Shoppenhangers Road, Maidenhead, Berkshire, SL6 2QL. ISBN 0-07-707410-6 (UK). Contains 24 selected papers; 1992. Tel: +44 (0)698 23431/2 Fax: +44 (0)698 770224 r. Horst Zuse, Software Complexity: Measures and Methods, de Gruyer (200 Saw Mill River Road, Hawthorne, NY 10532 - 914/747-0110) 1991 ------------------------------------------------------------------------ Subject: Metrics for object-oriented systems Date: 26 Jan 1993 Originally collected by: ZUSE%DB0TUI11.BITNET@vm.gmd.de (Horst Zuse) a. Morris Kenneth L. Metrics for Object-Oriented Software Development Environments (master's thesis). 1989, MIT. b. Rocacher, Daniel: Metrics Definitions for Smalltalk. Project ESPRIT 1257, MUSE WP9A, 1988. c. Rocacher, Daniel: Smalltalk Measure Analysis Manual. Project ESPRIT 1257, MUSE WP9A, 1989. d. Lake, Al: A Software Complexity Metric for C++. Annual Oregon Workshop on Software Metrics, March 22-24, 1992, Silver Falls, Oregon, USA. e. Bieman, J.M.: Deriving Measures of Software Reuse in Object Oriented Systems. Technical Report #CS91-112, July 1991, Colorado State Universty, Fort Collins/ Colorado, USA. ------------------------------------------------------------------------ Subject: User Interface Design Date: 9 Jul 1991 See also the item on Human Factors. a. John M. Carroll (editor). Interfacing Thought: Cognitive Aspects of Human-Computer Interaction, MIT press, 1987. This book has several good theoretical papers. b. Brad A. Myers, Creating User Interfaces by Demonstration London: Academic Press, 1988 c. Donald A. Norman, The Psychology of Everyday Things. Basic Books, 1988. ISBN 0-465-06709-3 (hardback). Trade paperback version is called "The Design of Everyday Things" d. Donald A. Norman & Stephen W. Draper (editors), User Centered System Design: New Perspectives on Human-Computer Interaction, Lawrence Erlbaum Associates, 1986. e. Ben Shneiderman, Designing the User Interface: Strategies for Effective Human-Computer Interaction, Addison-Wesley, 1987. Seems to be aimed at the practitioner. ------------------------------------------------------------------------ Subject: Human Factors Date: 20 Sep 1991 Originally collected by: rjc@cstr.ed.ac.uk (Richard Caley) a. Martin Helander, Handbook of Human-Computer Interaction North-Holland 1988. A huge collection of papers on various subjects; quite expensive. b. Sidney L. Smith, Jane N. Mosier. Guidelines for Designing User Interface Software Technical report ESD-TR-86-278 Electronic Systems Division The MITRE Corporation Bedford, MA 01730. A tech report rather than a book, but looks to be a good refence for issues. Also available as a hypertext. c. Paul Heckel, The Elements of Friendly Software Design: The New Edition. Sybex Inc. 1991. Original edition: Warner Books, 1984. d. Walter E. Gilmore, The User-Computer Interface in Process Control: A Human Factors Engineering Handbook. Boston:Academic Press, 1989. Is said to give references to research upon which it is based. e. Edward A. Fox (editor), Resources in Human-Computer Interaction, ACM Press, 1990. ISBN 0-89791-373-6. f. Gavriel Salvendy (editor), Handbook of Human Factors, John Wiley and Sons, 1987. ------------------------------------------------------------------------ Subject: Software Testing Date: 9 Jul 1991 The original request that prompted the posting of this information asked for recent work, not buried in a Software Engineering tome. a. Boris Beizer, Software Testing Techniques, Van Nostrand Reinhold, 1990 (2nd edition) ISBN 0-442-20672-0. 503 pages, $43. Has 37-page annotated bibliography of references. b. Cheatham and Mellinger, Testing Object Oriented Software Systems, Proceedings of the 1990 ACM SCS Conference c. William C. Hetzel, The Complete Guide to Software Testing, Second edition, QED Information Services INC, 1988. ISBN 0-89435-242-3 ------------------------------------------------------------------------ Subject: Requirements Analysis Date: 18 Sep 1991 a. Al Davis, Software Requirements: Analysis and specification. Prentice/Hall, 1990. Has some treatment of all of the popular requirements analysis and specification methods including OOA, Structured Analysis, SREM, FSM, but not the "trendy" stuff (Information Engineering, JAD). b. Donald C. Gause and Gerald M. Weinberg, Exploring Requirements: Quality before design. Dorset House Publishing, 353 West 12th Street, New York, NY 10014 ------------------------------------------------------------------------ Subject: Collaborative Requirements Analysis Date: 12 Jan 1991 Originally collected by: anton@cc.gatech.edu (Annie I. Anton) a. Palmer, J.D., Aiken, P. and Fields, N.A. "A Computer Supported Cooperative Work Environment for Requirements Engineering and Analysis", Proceedings of the Requirements Engineering and Analysis Workshop, Software Engineering Institute, March 12-14, 1991. b. Palmer, J.D. and Aiken, P.H. "Utilizing Interactive Multimedia to Support Knowledge-based Development of Software Requirements", Proceedings of the 5th Annual RADC Knowledge-Based Software Assistant Conference, Syracuse, NY, September 24-28, 1990. c. Marca, D. "Specifying Groupware Requirements From Direct Experience", Proc 6th International Workshop On Software Specification And Design, October 1991 d. Marca, D. "Augmenting SADT To Develop Computer-Supported Cooperative Work", Proceedings of the International Conference on Software Engineering; May 1991 e. Marca, D. "Experiences in Building Meeting Support Software", Proceedings of the 1st Groupware Technology Workshop; August 1989 f. Marca, D. "Specifying Coordinators: Guidelines for Groupware Developers", Proceedings of the 5th International Workshop on Software Specification and Design; May 1989 ------------------------------------------------------------------------ Subject: Object-Oriented Analysis and Design Date: 26 Mar 1993 Originally collected by: haim@taichi.uucp (24122-kilov) a. Bertrand Meyer. Object-oriented software construction. Prentice-Hall, 1988 For the somewhat advanced - perhaps, with some programming maturity. b. B. Henderson-Sellers. A book of object-oriented knowledge. Prentice-Hall, 1992. This has quite a few viewgraphs in it! c. Grady Booch. Object-oriented design with applications. Addison-Wesley, 1991. d. Ivar Jacobson Object-Oriented Software Engineering. Addison-Wesley, 1992. This book gives a complete look at Object-orientation from requirement- analysis to last phase in design and implementation. ------------------------------------------------------------------------ Subject: Programming Style Date: 19 Sep 1991 Originally collected by: oman@cs.uidaho.edu (Paul W. Oman) a. N. Anand (1988) "Clarify Function!" ACM SigPLAN Notices, 23(6), 69-79. Advocates the use of mnemonic names for entities in a system. Rules are presented for naming procedures, variable, pointers, etc. b. S. Henry (1988) "A Technique for Hiding Proprietary Details While Providing Sufficient Information for Researchers; or, do you Recognize this Well- known Algorithm?," Journal of Systems and Software, 8(1), 3-11. Suggests encryption of variable names as part of a technique for encoding algorithms, while still providing sufficient information to researchers. c. R. Brooks (1980) "Studying Programmer Behavior Experimentally: The Problems of Proper Methodology," Communications of the ACM, 23(4), 207-213. Discusses issues and tradeoffs in proper control of experiments involving computer programmers. d. E. Thomas & P. Oman "A Bibliography of Programming Style Literature," ACM SIGPLAN Notices, Vol. 25(2), Feb. 1990, pp. 7-16. ------------------------------------------------------------------------ Subject: Formal Specification Date: 29 Mar 1993 See also the comp.specification.z FAQ. a. J.M.Spivey. "Understanding Z: a specification language and its formal semantics". Cambridge University Press, 1988. b. David Lightfoot. "Formal Specification Using Z". MacMillan, 1991, ISBN 0-333-54408-0. A clear introduction to Z and the discrete mathematics that underlies it. c. B.Potter, J.Sinclair & D.Till. "An introduction to formal specification and Z". Prentice Hall International Series in Computer Science, 1991. d. D.Bjorner & C.B.Jones. "Formal Specification & Software Development", Prentice-Hall International Series in Computer Science, 1980. e. N.Gehani & A.D.McGettrick (eds). "Software Specification Techniques", Addison-Wesley Publishing Company, 1986 f. I. van Horebeek & J.Lewi. "Algebraic Specifications in Software Engineering", Springer Verlag, 1989. g. J.Bergstra, P.Klint & J.Heering. "Algebraic Specification", ACM Frontier Press Series. The ACM Press in co-operation with Addison-Wesley, 1989. h. J.Wing. "A specifiers introduction to formal methods", IEEE Computer 23(9):8-24, 1990. i. Prehn & Soetenel (eds). "Formal Software Development Methods, VDM'91", LNCS 551 and 552, Springer-Verlag. ------------------------------------------------------------------------ Subject: Software Process Date: 26 Apr 1993 Originally collected by: cml@cs.umd.edu (Christopher Lott) a. Watts S. Humphrey. Managing the Software Process. Addison-Wesley Publishing Co., Reading, Massachusetts, 1989; Chapters 13--15, 18. b. Bill Curtis, Marc I. Kellner and Jim Over. "Process Modeling," Communications of the ACM, Sept 92, Vol 35, No 9, 75-90. c. Victor R. Basili. "Iterative Enhancement: A Practical Technique for Software Development". IEEE Transactions on Software Engineering. v.~SE-1, n.~4, December 1975, pp.~390--396. d. Victor R. Basili and H. Dieter Rombach. "The TAME Project: Towards Improvement-Oriented Software Environments", IEEE Transactions on Software Engineering, v. SE-14, n. 6, June 1988, pp.~758--773. e. Victor R. Basili, "Software Development: A Paradigm for the Future", Proceedings of the Thirteenth Annual International Computer Science and Applications Conference, Orlando, Florida, September 1989, pp.~471--485. f. Barry W. Boehm. "A Spiral Model of Software Development and Enhancement", IEEE Computer, v.~21, n.~5, May 1988, pp.~61--72. g. Frank DeRemer and Hans H. Kron. "Programming-in-the-Large Versus Programming-in-the-Small", IEEE Transactions on Software Engineering, v.~SE-2, n.~2, June 1976, pp.~80--86. h. J. J. Horning and B. Randell. "Process Structuring", Computing Surveys, v.~5, n.~1, March 1973, pp.~5--30. i. M. M. Lehman. "Process Models, Process Programs, Programming Support", Proceedings of the Ninth International Conference on Software Engineering, Monterey, CA, March 1987, pp.~14--16. j. Leon Osterweil. "Software Processes are Software Too", Proceedings of the Ninth International Conference on Software Engineering, Monterey, CA, March 1987, pp.~2--13. k. Winston W. Royce. "Managing the Development of Large Software Systems: Concepts and Techniques", 1970 WESCON Technical Papers, v.~14, Western Electronic Show and Convention, Los Angeles, Aug. 25-28, 1970; Los Angeles: WESCON, 1970, pp.~A/1-1 -- A/1-9; Reprinted in Proceedings of the Ninth International Conference on Software Engineering, Pittsburgh, PA, USA, ACM Press, 1989, pp.~328--338. l. Peter H. Feiler and Watts S. Humphrey. "Software Process Development and Enactment: Concepts and Definitions", Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 1991. m. Watts S. Humphrey. "Session Summary: Review of the State-of-the-Art", Proceedings of the Fifth International Software Process Workshop, Kennebunkport, Maine, USA, 10-13 October 1989, IEEE Computer Society Press, Los Alamitos, CA, 1990. n. Gail E. Kaiser. "Rule-Based Modeling of the Software Development Process", Proceedings of the 4th International Software Process Workshop, Moretonhampstead, Devon, UK, 11-13 May 1988, ACM Press, Baltimore, MD, 1989, pp.~84--86. o. Takuya Katayama. "A Hierarchical and Functional Software Process Description and its Enaction", Proceedings of the Ninth International Conference on Software Engineering, Pittsburgh, PA, USA, ACM Press, 1989, pp.~343--352. p. Marc I. Kellner and H. Dieter Rombach. "Comparisons of Software Process Descriptions", Proceedings of the Sixth International Software Process Workshop, Hakodate, Hokkaido, Japan, 29-31 October 1990, IEEE Computer Society Press, 1991. q. Jayashree Ramanathan and Soumitra Sarkar. "Providing Customized Assistance for Software Lifecycle Approaches", IEEE Transactions on Software Engineering, v.~14, n.~6, June 1988, pp.~749--757. r. H. Dieter Rombach. "An Experimental Process Modeling Language: Lessons Learned from Modeling a Maintenance Environment", Proceedings of the Conference on Software Maintenance - 1989, IEEE, October 16-19, 1989. s. H. Dieter Rombach. "MVP--L: A Language for Process Modeling In--the-- Large", University of Maryland Institute for Advanced Computer Studies Technical Report UMIACS--TR--91--96, CS--TR--2709, Department of Computer Science, University of Maryland, College Park, MD, 20742. t. Stanley M. Sutton, Jr. "APPL/A: A Prototpye Language for Software Process Programming", Department of Computer Science Report CU-CS-448-89, University of Colorado, Boulder, CO, 1989. -- Software Technology Laboratory dalamb@qucis.queensu.ca (David Alex Lamb) Computing and Information Science phone: (613) 545-6067 Queen's University, Kingston, Ontario, Canada K7L 3N6 -- rbotting@wiley.csusb.edu. rbotting::=`Dr. Richard J. Botting`, wiley::=`Faculty EMail System`, csusb::=`California State University, San Bernardino, CA 92407, USA`. From rbotting@wiley.csusb.edu Sat Feb 5 20:47 PST 1994 Return-Path: Received: from wiley.csusb.edu by silicon.csci.csusb.edu (5.0/SMI-SVR4) id AA25705; Sat, 5 Feb 94 20:46:45 PST Received: by wiley.csusb.edu (5.67a/1.34) id AA03525; Sat, 5 Feb 1994 20:47:59 -0800 Date: Sat, 5 Feb 1994 20:47:59 -0800 From: rbotting@wiley.csusb.edu ("Dr. Richard Botting") Message-Id: <199402060447.AA03525@wiley.csusb.edu> To: dick@silicon.csci.csusb.edu Subject: (fwd) FAQ 2: CASE tools summary Newsgroups: comp.software-eng Content-Type: text Content-Length: 41774 Status: RO Newsgroups: comp.software-eng,comp.answers,news.answers Path: csus.edu!netcom.com!netcomsv!decwrl!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!qucis.queensu.ca!dalamb From: dalamb@qucis.queensu.ca (David Alex Lamb) Subject: FAQ 2: CASE tools summary Message-ID: Followup-To: comp.software-eng Keywords: FAQ Sender: dalamb@qucis.queensu.ca (David Lamb) Supersedes: Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb) Organization: Computing and Information Science, Queen's University at Kingston, Ontario, K7L 3N6, Canada References: Date: Sat, 5 Feb 1994 13:05:24 GMT Approved: news-answers-request@MIT.Edu Expires: Sat, 26 Mar 1994 13:05:06 GMT Lines: 920 Xref: csus.edu comp.software-eng:15931 comp.answers:3682 news.answers:17816 Last-Modified: 30 Nov 1993 Archive-name: software-eng/part2 This is the monthly "frequently asked questions" (FAQ) posting on Computer-Aided Software Engineering (CASE) tools: ECMA Reference Model Other sources of information What version control systems are available on UNIX Other configuration Management tools CASE tools for object-oriented design and analysis Problem Tracking systems CASE tools for educational use CASE Vendor list Look for lines starting with "Subject:" (control-G command in rn). Most products are trademarks or registered trademarks of their vendors. Send comments to dalamb@qucis.queensu.ca (David Alex Lamb). ------------------------------------------------------------------------ Subject: ECMA Reference Model Date: 12 May 1992 Originally collected by: ant@hpfcbig.SDE.HP.COM (Anthony Earl) The European Computer Manufacturer's Association (ECMA) adopted TR/55, "Reference Model for Frameworks of Software Engineering Environments", 2nd edition, in December of 1991. In Europe, it's available for free from The European Computer Manufacturers Association 114 Rue du Rhone CH-1204 Geneva Switzerland Tel: +41 22 735 36 34 Fax: +41 22 786 52 31 In the United States, it is for sale by the National Institute of Standards and Technology as NIST Special Publication 500-201. Contact: the Superintendent of Documents, US Government Printing Office, Washington DC 20402. There is a PostScript version of the document in the PSESWG archives. You may be able to retrieve it using their mail-server by sending email to psesarch@nadc.navy.mil with the subject: get nist-sp500-201.ps It is long (about half a Meg) so it may not make it through some mailers/nets. ------------------------------------------------------------------------ Subject: Other sources of information Date: 26 Mar 1993 There is a Hypercard stack that you can get by anonymous FTP from the info- mac/card directory at sumex-aim.stanford.edu. The version 1.1 runs under various Hypercard versions including 2.0v2 on newer Macs: -rw-r--r-- 1 macmod 286168 Jan 29 12:13 case-products-11.hqx A short companion report (about 60 pp. including tool signal info and my view of why and where this market is going) can be obtained from GMD; Western US office is: GMD, 1942 University Ave. #207, Berkeley CA 94704.) Heinz W. Schmidt hws@icsi.berkeley.edu [edsr!bigdaddy!cdm@uunet.UU.NET (Clifford D. Morrison) did a search with Archie and points out that this file isn't available at sumex anymore; possible locations follow. A file with a .Z ending usually means you need to retrieve it in binary/image mode and run it through UNIX 'uncompress': Host wuarhive.wustl.edu (128.252.135.4) Location: /mirrors2/info-mac/Old/card FILE rw-r--r-- 248003 Jun 30 1991 case-products-11.hqx.Z Host utsun.s.u-tokyo.ac.jp (133.11.11.11) Location: /Mac/info-mac/card FILE rw-rw-r-- 286168 Feb 12 10:39 case-products-11.hqx See also the Mar. 1, 1992 issue of Datamation. There are over 400 products listed for different purposes and platforms. Entries in the listing describe Company, Product, Product Type, and Operating System. Some of the product types are: Structured Analysis, Planning and Design, Strategic Planning, Analysis and Design, User Interface Konstruction, DBMS Design, Design, Prototyping, Project Management, Verification, Validation, (Data) Modeling, Simulation , Diagramming, Methodology, Software Metrics and Static Analysis, Configuration and Release Management, Project Management, Maintenance, Code Generation, Restructuring and Reverse Engineering, Performance, Testing. (sprinzl@edvz.tuwien.ac.at) ------------------------------------------------------------------------ Subject: What version control systems are available on UNIX Date: 29 Mar 1993 Originally collected by: media01!rla@relay.nluug.nl (Raymond van der Laan) (see also the archive file "cmtools") SCCS is free and comes with most Unix-distribution, ported to everything and its brother. It is no longer being enhanced or improved. Clumsy and not suited to many users working on the same project. Many people place scripts around the various SCCS commands to help the user. RCS, better than SCCS, but still requires scripts to make life easier on the developer. Originally by Walter Tichy (now at Karlsruhe) and still maintained by Purdue (rcs-bugs@cs.purdue.edu); available on the GNU distribution, widely ported, and free. Available via anonymous FTP from several sources: site filename ftp.cs.ruu.nl /pub/GNU/rcs-5.6.tar.Z cs.purdue.edu pub/RCS/rcs.5_6.tar.Z prep.ai.mit.edu pub/gnu/rcs-5.6.tar.Z ftp.uu.net packages/gnu/rcs-5.6.tar.Z ftp.virginia.edu pub/vms/*.zoo (VAX VMS version) It works best with GNU diff 2.0; look for diff-2.0.tar.Z. Many case tools interface with RCS. CVS extends RCS to control concurrent editing of sources by several users working on releases built from a hierarchical set of directories. "RCS is assembly language, CVS is Pascal", according to the author. Brian Berliner's CVS 1.3 C version is in cvs-1.3.tar.Z at MIT and UUnet. Dick Grune's original shell script version, CVS 3.0, is available at RUU. Berliner (berliner@Sun.COM) and Jeff Polk (polk@BSDI.COM) continue to maintain CVS; the 1.3 release was in April 1992. The shape toolkit (ShapeTools) is a set of commands for change control, developed by Axel Mahler, Andreas Lampen and others at the Technical University of Berlin. It consists of a repository (the Attributed File System), version control programs, a build driver (compatible with make), release management system, and EMACS editor interface. ShapeTools 1.3 was released in late May 1992; it runs on many UNIX variants. It's available from site file coma.cs.tu-berlin.de pub/shapeTools/shapeTools-1.3.tar.Z gatekeeper.dec.com pub/plan/shapeTools-1.3.tar.Z gatekeeper has a mail archive server; send a message to ftpmail@gatekeeper.dec.com whose body contains the single line "help". Aegis is a project change supervisor distributed under the GNU piblic licence. CVS provides a repository; aegis provides a repository, a baseline, mandatory reviews and mandatory testing. It's available via anonymous ftp from: Host: ftp.nau.edu (134.114.64.70) Dir: /pub/Aegis File: aegis.1.3.tar.Z # the complete source File: aegis.1.3.patch.Z # patch to take 1.2 to 1.3 File: aegis.1.3.ps.Z # PostScript of the User Guide Many large and expensive case-tools exist which have version control in them. (Teamwork, Backplane) All VCS we know about are file-based. Database-oriented VCS's do not seem to exist. ------------------------------------------------------------------------ Subject: Other configuration Management tools Date: 28 Apr 1993 Originally collected by: rene@Cadence.COM (Rene Churchill) and zdlc03@trc.amoco.com (Dan L. Cummings) DSEE (pronounced dizzy) [Domain Software Engineering Environment] by Apollo (now HP) is an excellent program that has excellent version control and does builds for the user. These builds can be easily customized to a specific purpose and spread out over several different machines simultaneously. Excellent for large development projects. Problem: Cannot be ported to other machines. Uses non-standard facilities of Domain/OS; David Lubkin of the DSEE Project says it will be available on other operating systems, at least HP's OSF offering. I don't know their main phone number, but their help line could get you in touch with somebody. (1-800-227-6556) ClearCase, by Atria software (see vendor list) runs on Silicon Graphics, HP, and Sun systems. It was influenced by DSEE. For SGI machines, it's available through regular SGI sales channels (US customers can call 1-800-800-SGI1). Softool Corp. sells a "Family of change and configuration control products" The literature looks good. This program does code control, builds, merging and other items that look good for group projects. It has also been ported to DEC, IBM, Sun HP, Harris, and IBM PC computers. It's been around for a long time, so it's a very mature product. Softool Corp.; 340 S. Kellogg Ave.; Goleta, CA 93117 (805) 683-5777 Imperial Software Technology Limited sells some CASE tools that do builds and manage source code. The literature is not that glossy, and the impression I got was of a immature set of programs. I also sent them a fax and email and have yet to get a response. (6+ months) Imperial Software Technology Ltd.; 95 London Street; Reading RG1 4QA United Kingdom Phone: 0734-587055 (add England country code) Usenet: apg@ist.co.uk Aide-de-Camp is another good looking product from its literature. Sounds very mature and has many good feature mentioned above. Rather than independent versions of each file, it stores which groups of files change together: a nice idea for tracking widespread changes. Software Maintenance & Development Systems, Inc. PO Box 555; Concord, MA 01742 (508) 369-7398 Procase is an interesting database for code control. It creates a database of all of your code and will display call graphs and other very fancy functions. It requires you to use its editor, rather than vi or emacs (though it does have emulation modes for them) It has a very impressive user interface, just not enough flexibility for me. Procase; 210 Canegie Center, Suite 101; Princeton, NJ 08540 (609) 452-8848 Digital Equipments Corp.'s VAXSET: CMS: Code Management System; Code libraries and configuration control MMS: Module Management System; Like MAKE integrated to CMS LSE: Language Sensitive Editor - Provided programming support as part of the editors functioning for all supported VMS languages SCA: Source Code Analyzer - Provide variable information, call trees, etc. Integrated into LSE and CMS. DTM: DEC Test Manager; Automated scripting tool for performing tests of software, creating benchmarks and helping with regression testing PCA: Performance and Coverage Analyzer - Allows for program analysis. Validates path coverage of testing. All these product are operational on VAX VMS platforms. Additionally there is the interactive debugger, the Common Data Dictionary (repository), DEC Design, DEC Plan, and other tools. CaseWare/CM (formerly Amplify Control) from CaseWare, Inc. is an interactive development environment emphasizing configuration management and tool integration. It provides user-modifiable graphical and non-graphical user interfaces. The graphical interfaces supports Motif. It also supports several configuration management methodologies via its flexible object- oriented data modeling. They supply a generic software process model, which you can customize. The related CaseWare/PT problem tracking system is driven from the same configration management database. (see vendor list for address). CMZ is a code manager for C and Fortran; besides version archiving, it also provides many editing, checking, and library management functions. It currently runs on Apollo, IBM VM/CMS, IBM MVS, IBM RS/6000, VAX/VMS, Ultrix, Gould UTX, Cray Unicos, Sun, SGI, HPUX. All European High Energy Physics laboratories will get it from CERN; others must pay a licence fee. Contact codeme@cernapo.cern.ch. SMS from Intasoft [see vendor list] runs on PCs, Unix and VAXen. Facilities include source code control, a preprocessor, a build tool and a menu driven front end. I find it very usable, it is reasonably priced and it has all the facilities I need. nyo@dcs.ex.ac.uk (Neil Youngman) "Merge Ahead" is not a full fledged Version or Configuration mangement tool, but it addresses one of the most important parts of such systems, support for management and integration of multiple versions and releases. While Merge Ahead does not provide check-in and check-out it is designed to work closely with other tools that do: integrations for RCS and SCCS are contributed, and integrations to CASEWare/CM and Atherton Technology Software BackPlane re supported by those vendors. Integrations to other CM tools (Atria ClearCase, TeamOne TeamNet, etc.) and even custom and internal tools are easy--even if files are versioned only by different names or extensions. Merge Ahead is available from: Prescient Software, Inc. (see vendor list) RAZOR from Tower Concepts, Inc (see vendor list) is an easily tailored configuration management system with an integrated problem tracking system. It offers control and coordination of file versioning and product build management. The graphical interface is built on OpenLook. Its easily parsed ASCII database encourages users to generate their own scripts for report generation and process control. Contact razor-info@tower.com for a detailed description, or razor-manual@tower.com for a postscript copy of their manual. ------------------------------------------------------------------------ Subject: CASE tools for object-oriented design and analysis Date: 29 Nov 1993 Originally collected by: calvo@nssdca.gsfc.nasa.gov (Sherri Calvo) Cadre Teamwork 401-351-5950 associated with Project Technology. Shlaer/Mellor OOA capability including ERDs in upcoming V.4.0. Ada structure graphs (Booch/Buhr). CASET 714-496-8670 IPSYS ToolBuilder HOOD (Hierarchical Object Oriented Design) HOOD User's Group: HUG Administration Logica Space and Communications Ltd Business Park No 4 Randalls Way Leatherhead Surrey, KT22 7TW U.K. Attn: Jardine Barrington-Cook email: barrington-cookj@logica.co.uk Now mandatory for several European Space Agency projects. Interactive Development Environments (IDE) Vienna, VA ofc. 703-848-8808 San Francisco 415-543-0900 sales@ide.com Extension of Ada design tools to handle OOPLs, primarily C++ ObjecTime ObjecTime Ltd. (see vendor list) ObjecTime is an Object-Oriented CASE tool for real-time systems. It supports the Real-Time Object-Oriented Modeling (ROOM) methodology, including a highly iterative development process enabled by the creation of executable models (not just diagrams). Object-oriented paradigms are integral to the tool and support reusable design components. ObjectMaker (a/k/a Adagen) Mark V Systems, Ltd.; 16400 Ventura Blvd., #319; Encino, CA 91436 818-995-7671 (voice) 818-995-4267 (fax) Runs under Windows, X11, Mac. Tools for Yourdon, Booch, Buhr methodologies Code generation and reverse engineering for Ada, C/C++ (may be under development.) OOAtool by Object International Inc. in the vendor list. Runs under Windows, Mac, and 11. Supports methodology in Peter Coad's books "Object-Oriented Analysis" and "Object-Oriented Design". OOTher (OO Documentation Tool); once called OoaToolFree Rel 1.05a (for win 3.0/3.1). Supports Coad's OOA/OOD and Finite State Machine notation (a subset of SDL). Available on SIMTEL20 and CICA. Free for Students, $70 home users, $170 site licese for 5 users for others. e-mail: conrozi@KK.ericsson.se. To fetch from simtel-20 (via mail in uuencoded format): Send e-mail to listserv@vm1.nodak.edu, set the subject string to SIMTEL20-request. The message body should be: /PDGET MAIL PD1:OOT-104d.ZIP UUENCODE Paradigm Plus / EVB Edition EVB Software Engineering (see vendor list). Supports the EVB Ada Object Oriented Development (AOOD) methodology. Can be configured to support other methods. Has Ada code generation. Rational Rose Rational (see vendor list) Supports Booch methodology. Available for SunOS, AIX, MS Windows, OS/2. Robochart Digital Insight (see vendor list) Interactive diagram editor for OPEN LOOK & SunView ($495); Does hierarchical ERDs, dataflows, etc. Educational discounts. System Architect Popkin Software. 212-571-3434 (voice) 212-571-3436 (FAX) 11 Park Place, New York, NY 10007 Supports ER diagrams, Booch methodology for Ada and C++, Coad/Yourdon. Diagram editor checks for consistency and rule violations. Runs under MS- Windows. Systematica Virtual Software Factory England (0202)297292 (voice) Hierarchical OO design package based on GOOD Unirel Openlook Toolkit Unirel; Centro Commerciale Osmannoro; Via Volturno, 12; 50019 Sesto Fiorentino, Italy +39 55 301279 (voice) +39 55 318525 (fax) An Eiffel wrapper for Xlib. US $2000 Objectory (Objective Systems; see vendor list) is an object-oriented Analysis and Design method with supporting CASE-tool. The tool is a multi-user tool with a central repository and includes multiple diagram and documentation techniques, consistency checks, traceability, etc. It covers several models including Requirements, Analysis and Design models and also C++ code generation. The tool runs on multiple platforms. An overview of Objectory can be found in "Object-Oriented Software Engineering - A use case driven approach", by Jacobson et al, published by Addison-Wesley 1992. ------------------------------------------------------------------------ Subject: Problem Tracking systems Date: 28 Apr 1993 Originally collected by: pyke@escaegate2.boeing.com (Ronald B Pyke) The only commercial product for the Apollo mentioned was: DDTS Qualtrak Corporation 3315 San Filipe Road, Suite 16; San Jose, CA 95135-2000 1-408-274-8867 Several responses mentioned software available to Software Productivity Consortium (SPC) members, and also software developed at Boeing. RAZOR, by Tower Concepts, Inc (see vendor list) offers an issue tracking system that runs on Sparc platforms. Contact razor-info@tower.com for a detailed description, or razor-manual@tower.com for a postscript copy of their manual. ------------------------------------------------------------------------ Subject: CASE tools for educational use Date: 9 Jul 1993 Originally collected by: render@zeppo.colorado.edu (Hal Render) Teamwork (Cadre Technologies: see vendor list) It runs on SUN, ULTRIX, VMS, HP, APOLLO, OS2, etc, with X window support on most of the platforms with more to come soon (including some low-cost PC X emulators. [from cadreri!sat@Sun.COM (Scott A. Trachtenberg)] We have been using for the past few years the following two tools: (Schemacode International Inc; see vendor list) SCHEMACODE: automatically translates schematic pseudocode design into source code. Works for most programming language except ADA. Available on PC, soon on UNIX. Educational licence 250$ + 50$ per PC. IEEE Computer had a good report on this tool. Sometime last fall. DATRIX: a tool for software quality assessment on PC and UNIX machines. Works for C, FORTRAN and PASCAL. Measures up to 40 metrics and provides a unique representation of the control flow, which is useful for testing, program understanding, and program evaluation. Expensive; educational licence for 500$, including up to 10 workstations. We have been using these tools for the past three years in 4th year undergrad and grad soft.eng. courses Ecole Polytechnique in Montreal. [from robillar@rgl.polymtl.ca (P. N. Robillard)] ToolBuilder (formerly TBK) from IPSYS (see vendor list) It provides meta-tools (design editors, structure editors) a single underlying ERA database (supporting fine structure) and a uniform UI based on Motif. Tools exist for HOOD (design for Ada). Might have educational discounts. STONE (FZI, see vendor list and archives file "environments") - An SEE for research and education. An OODBS called OBST is used as the core of the environment. OBST is available via anonymous ftp from gate.fzi.de [141.21.4.3]. OBST provides currently an interface to C++. A call interfaces to C is also available, as well as an embedding of OBST into the interactive tool command language TCL. [from Bernhard Schiefer ] Rational Environment (Rational, see vendor list). A tightly integrated, interactive software engineering environment for total lifecycle control of Ada projects. Supports design, development, unit test, maintenance, verification, document generation, configuration management, subsystem tools, incremental compilation. Can also integrate with external front-end CASE tools and external target compilers. [from: Bob Geiger ] Objectory (Objective Systems; see vendor list) is an object-oriented Analysis and Design method with supporting CASE-tool. The tool is a multi-user tool with a central repository and includes multiple diagram and documentation techniques, consistency checks, traceability, etc. It covers several models including Requirements, Analysis and Design models and also C++ code generation. The tool runs on multiple platforms. An overview of Objectory can be found in "Object-Oriented Software Engineering - A use case driven approach", by Jacobson et al, published by Addison-Wesley 1992. ------------------------------------------------------------------------ Subject: CASE Vendor list Date: 29 Sep 1993 Originally collected by: Scott Marcus and/or Theo Heavey , CASE research group, Dept. of Computer Science, Florida Atlantic University; sponsored by Florida Industry High Technology Council Adpac Corp. Adpac CASE Tools 340 Brannan St.; San Francisco, CA 94107; 415-974-6699 Advanced Logical Software Anatool 9903 Santa Monica Blvd., suite 108; Beverly Hills, CA 90212; 213-653-5786 Advanced System Technologies Inc. QASE Category: information systems development environment 12200 E. Briarwood Ave., Suite 260; Englewood, Colorado 80112 Fax: (303) 790-2816; Tel: (303) 790-4242 Advanced Technology International, Inc. SuperCase category: back-end, reverse engineering Corporate HQ: 1501 Broadway, Suite 1314; New York, NY 10036 Tel: (212) 354-8280 West Coast Office: 8950 Villa La Jolla Drive, Suite 1200; La Jolla, CA 92037 Tel: (619) 453-3050 AGS Management Systems, Inc. Multi/CAM category: front end 880 First Ave.; King of Prussia, PA 19406; 215-265-1550 American Management Systems, Inc. Life Cycle Productivity System category: front end, back end 1777 North Kent St.; Arlington, VA 22209; 703-841-6060 Applied Business Technology Corp. Project Workbench 361 Broadway; New York, NY 10013; 212-219-8945 Applied Data Research, Inc. DEPICTOR category: front end Route 206 and Orchard Rd.; CN-8; Princeton, NJ 08543 Arthur Andersen & Co. Design/1 (part of Foundation Series) category: front end, back end, RE/M 33 West Monroe St.; Chicago, IL 60603 69 West Washington; Chicago, IL 60602; 312-580-0069; 312-580-0033 312-507-5161 Ascent Logic Corporation RDD-100 category: systems engineering, requirements analaysis 180 Rose Orchard Way, Suite 200; San Jose, CA 95134; phone: 408-943-0630 FAX: 408-943-0705 ASYST Technologies, Inc. The Developer One Naperville Plaza; Naperville, IL 60540; 800-361-3673 Atherton Technology Software BackPlane, Project Softboard, Integration Softboard 1333 Bordeaux Drive; Sunnyvale, CA. 94089; Tele: 408 734-9822 Fax: 408 744-1607 Atria Software ClearCase 24 Prime Park Way, Natick, MA 01760; tel. (508)-650-1193; info@atria.com Bachman Information Systems BACHMAN Product Set, BACHMAN/Analyst category: reverse engineering, front end 8 New England Executive Park; Burlington, MA 01803; 617-273-9003 800-BACHMAN Bell-Northern Research ObjecTime now supplied through ObjecTime Ltd. Cadre Technologies, Inc Teamwork OS/2 3.0 category: front end 222 Richmond St.; Providence, RI 02903; 401-351-5950; 401-351-CASE The CADWARE Group, Ltd SYLVA Series category: Front end CASE Methods Development Corp. CASE/FRAMEWORK--METHODOLOGY, CASE/FRAMEWORK--SYNERGY category: Information Engineering Methodology 100 N. Central Exwy.; Suite 710; Richardson, TX 75080; tel: 214-644-8173 fax: 214-644-8175 CaseWare, Inc CaseWare/CM, CaseWare/PT (formerly Amplify Control) 108 Pacifica; Irvine, CA 92718-3332; voice: (714) 453 2200 FAX: (714) 453 2276 CASEWorks, Inc. CASE:PM 1 Dunwoody Park, Suite 130; Atlanta, GA 30338; 404-399-6236 Fax: 404-399-9516 The Catalyst Group PATHVU Series category: RE/M Peat Marwick Main & Co.; 303 East Wacker Dr.; Chicago, IL 60601 800-323-3059; 312-938-5352 CGI Systems, Inc. PACBase, PACBench, PACDesign, Transform category: front end, back end, RE/M 1 Blue Hill Plaza; Pearl River, NY 10965; 914-735-5030 Chen & Associates ER-Designer (ERD) 4884 Constitution Ave, Ste 1E; Baton Rouge, LA 70808; 504-928-5765 Cincom Systems, Inc. Supra, Mantis, Easy PC Contact, CASE Interchange 2300 Montana Ave.; Cincinnati, OH 45211; 800-888-0115 Coding Factory CoFac 100 Netro Park South; Laurence Harbor, NJ 08878; 201-290-0090 Cognos PowerCASE 67 S. Bedford St.; Burlington, Mass. 01803; 617-229-6600 Computer Associates International, Inc. CA-Datacom, CA-Ideal, CA-Dataquery, CA-Dataquery PC Computer Associates World Headquarters; 711 Stewart Ave. Garden City, NY 11530; 516-227-3300 Computer Data Systems Scan/COBOL, SuperStructure 1 Curie Court; Rockville, MD 20850; 202-921-7000 Computer Sciences Corp Design Generator category: front end 3610 Fairview Park Dr; Falls Church, VA 22042; 703-876-1000 Computer Systems Advisers, Inc Picture Oriented Software Environment (POSE) 4.0, SilverRun 50 Tice Blvd.; Woodcliff Lake, NJ 07675; 800-537-4262; 201-391-6500 Compuware Corporation CATI tools: Abend-AID, CICS Abend-AID, CICS RADAR, File-AID family, TransRELATE, PLAYBACK, File PLAYBACK, SIMULCAST, dBUG-AID, XPEDITER, NAVIGATOR 31440 Northwestern Highway; Farmington Hills, Michigan 48018-5550 Cortex Corp. CorVision, Application Factory category: front end, back end, RE/M 138 Technology Dr.; Waltham, MA 02154 100 Fifth Avenue; Waltham, MA 02154-9863; 617-894-7000 Cullinet Software, Inc. IDMS/Architect D. Appleton Company IDEF/Leverage 1334 Park View Ave., Suite 220; Manhattan Beach, CA 90266; 213-546-7575 Deft Inc. Deft 567 Dixon Rd., suite 110; Rexdale, ON M9W 1H7; Canada; 416-249-2246 Deloitte, Haskins & Sells 4Front 200 East Randolph Dr.; Chicago, IL 60601; 312-856-8168 Digital Equipment Corp. DECASE DECdirect; Continental Blvd.; Merrimack, NH 03054; 800-344-4825 Digital Insight Robochart category: flow diagram editor P.O. Box 533; Simi Valley, CA 93062-0533; USA; phone: (805) 583-3627 fax: (805) 583-3809; e-mail: rc-sales@digins.com Digital Tools Inc. AutoPLAN category: project scheduling tool 18900 Stevens Creek Blvd.; Cupertino, California 95014; phone: 408-366-6920 fax: 408-446-2140 ECS Associates SQL-Link-Plus 3812 Sepulveda Blvd.; Torrance, CA 90505; 213-378-9260 EVB Software Engineering, Inc. Paradigm Plus / EVB Edition - OOA/OOD CASE Tool (Unix and DOS); HeragrapH - Ada 2D/3D Graphics and GUI toolkit (Unix/X windows and DOS); GRACE - Reusable Ada Software Components; RLT - Reuse Library Toolset (Unix and DOS); Ada, Object Oriented Development and Software Engineering Training; 5303 Spectrum Drive,; Frederick, MD 21701; VOICE 301-695-6960 FAX 301-695-7734; info@evb.com Evergreen CASE Tools EasyCASE (shareware), EasyCASE plus (commercial) 11025 164th Ave NE; Redmond WA 98052; 206-881-5149 Forschungszentrum Informatik (FZI) STONE Haid-und-Neu-Str. 10-14,; D-7500 Karlsruhe, Germany; +49-721-6906-731 ICONIX Software Engineering Inc. PowerTools Series category: front end, back end, RE/M 2800 Twenty Eighth St, Suite 320; Santa Clara, CA 90405; 213-458-0092 i-Logix StateMate 22 Third Ave.; Burlington, MA 01803; 617-272-8090 Index Technology Corp. (merged with Sage to form Intersolv) Insoft Ky Prosa P.O.Box 9; SF-90101 Oulu; Finland; tel. +358-81-226128; fax. +358-81-221754 Institute for Information Industry KangaTool Series category: front-end 8th Floor, 106 Ho-Ping E. Rd.; Taipei, Taiwan, R.O.C. Institute of Applied Computer Science (IFAD) VDM-SL Toolbox Forskerparken 10,; DK-5230 Odense M, Denmark; Phone: +45-65932300 Fax: +45-65-932999; Email: poul@ifad.dk Intasoft SMS category: configuration management 153 Sweetbrier Lane; Exeter EX1 3DG; England Integrated Systems, Inc. AutoCode 2500 Mission College Blvd.; Santa Clara, CA 95054; 408-980-1500 IntelliBase nv/sa RIDL* category: I-CASE for Nijssen's Information Analysis Method Plantin en Moretuslei 220; B-2018 Antwerp; BELGIUM; tel. (+32) 3 235 9596 fax. (+32) 3 235-7955 Interactive Development Environments Software through Pictures, C Development Environment category: front end 595 Market St., 10th Floor; San Francisco, CA 94105; 415-543-0900 Intersolv (merger of Index and Sage) Excelerator 1.84, Polytron Version Control System (PVCS), APS Development Center category: I-CASE (front end, back end, RE/M) Corporate HQ: 3200 Tower Oaks Blvd.; Rockville, Maryland 20852; 301-230-3200 International HQ: Abbey View; Everard Close; St. Albans; Herts AL1 2PS United Kingdom; Tel: 0727812812 IPSYS Software Plc, ToolBuilder Marlborough Court,; Pickford Street,; MACCLESFIELD, Cheshire, SK11 6JD United Kingdon; Tel: +44 625 616722; E-mail: support@ipsys.co.uk KnowledgeWare, Inc. IEW/WS, RECODER, INSPECTOR category: front end 3340 Peachtree Rd.; Atlanta, GA 30026; 404-231-8575; 800-338-4130 Language Technology (defunct; products acquired by KnowledgeWare) RECODER, INSPECTOR Learmonth & Burchett Management Systems, Inc. (LBMS) System Engineer (nee Auto-Mate Plus) 1800 West Loop South, Suite 1800; Houston, TX 77027; 713-682-8530 800-231-7515 MAGEC Software MAGEC category: Full Cycle Cobol database apps 4054 INFOMART; 1950 Stemmons Freeway; Dallas, TX 75207; 800-336-2432 214-746-4000; FAX: 214-746-4099 Manager Software Products, Inc. Manager Series category: Front end, back end 131 Hartwell Ave; Lexington, MA 02173-3126; 617-863-5800 Mark V Systems, Ltd. ObjectMaker 2.0 (aka Adagen) category: cross-lifecycle 16400 Ventura Blvd., Suite 303; Encino, CA 91436; 818-995-7671 (voice) 818-995-4267 (fax); mo@markv.com Matterhorn, Inc. HIBOL category: back end McCabe & Associates ACT, BAT, DCT, CodeBreaker category: Reverse Engineering/Maintenance 5501 Twin Knolls Road, Suite 111; Columbia, Maryland 21045; 800-638-6316 McDonnell-Douglas ProKit*Workbench STRADIS, PRO-IV category: front end P.O. Box 516; Dept. L515, MS 2812301; St. Louis, MO 63166; 800-325-1087 800-822-7337; 314-232-5715 Mentor Graphics Corp. Analyst/RT, Designer, Auditor category: front end 8500 Southwest Creekside Place; Beaverton, OR 97005; 503-626-7000 Meridian Software Systems, Inc. OpenSELECT CASE category: front end 10 Pasteur Street; Irvine, CA 92718; 714-727-0700 (ext. 224) fax: 714-727-3583 Meta Systems QuickSpec, Structured Architect (SA), Structured Architect-Integrator (SA-I), PSL/PSA, Report Specification Interface (RSI), View Integration System (VIS). category: front end, RE/M 315 E. Eisenhower Parkway, Suite 200; Ann Arbor, MI 48108; 313-663-6027 Micro Focus, Inc. COBOL/2 Workbench 2465 East Bayshore Rd.; Palo Alto, CA 94303; 415-856-4161 Mortice Kern Systems RCS (for DOS), MKS Toolkit Customer Service; Mortice Kern Systems Inc.; 35 King St. N. Waterloo, Ont. Can. N2J 2W9; (519)884-2251; (519)884-8861 FAX (800)265-2797 (Continental US only) Netron, Inc. NETRON/CAP 99 St. Regis Crescent N; Downsview, Ontario; Canada M3J 1Y9; 416-636-8333 Object International, Inc. OOAtool catgegory: object-oriented analysis 8140 N. MoPac Expwy, 4-200; Austin, TX 78759-8864 USA (512) 795-0202 (voice); (512) 795-0332 (fax) ObjecTime Limited ObjecTime category: real-time object-oriented ObjecTime Limited,; 340 March Road, Suite 200, Kanata, Ontario, Canada K2K 2E4 telephone: 1-800-567-TIME; (613) 592-3128; fax: (613) 591-3784 internet: sales@objectime.on.ca Objective Systems Objectory PO Box 1128; S-116 24 Kista; Sweden; Fax +46 8 751 30 96; Tel +46 8 703 45 84; Email: freli@os.se On-Line Software International AD/VANCE DataModeler 2 Executive Dr.; Ft. Lee Executive Park; Ft. Lee, NJ 07024; 201-592-0009 Optima, Inc. DesignVision 1.7, DesignMachine 2.0 category: front end, back end Oracle Systems Corp. CASE*Designer, CASE*Dictionary, CASE*Generator, SQL*Forms, SQL*Report, SQL*QMX, Oracle, SQL*Louder Oracle World Headquarters; 500 Oracle Pkwy; Redwood Shores, CA 94065 415-506-7000 ORACLE Corporation; 20 Davis Drive; Belmont, CA 94002; 800-345-DBMS Pansophic Systems Inc. Telon 2400 Cabot Drive; Lisle, IL 60532; 312-505-6000; 800-323-7335 ParcPlace Systmems ObjectworksC++, ObjectworksSmalltalk category: back-end Corporate HQ: 999 E. Arques; Sunnyvale, CA 94086-4593; Tel: (408) 481.9090 Fax: (408) 481.9095; Email: info@parcplace.com Performance Awareness Corp. preVue, preVue-X, XStudio 8521 Six Forks Rd., Suite 200; Raleigh, NC 27615, USA; Phone: (919) 870-8800 e-mail: prodinfo@PACorp.com Phoenix Technologies, Ltd. P-Source, P-Tools 846 University Ave.; Norwood, MA 02062; 617-551-4000 Popkin Software & Systems System Architect 111 Prospect St., Suite 505; Stamford, CT 06901; 203-323-3434 11 Park Place, NY, NY 10007; tel. 212-571-3434; fax. 212-571-3436 Prescient Software, Inc. Merge Ahead 3494 Yuba Avenue; San Jose, CA 95117-2967; E-mail: mcgregor@netcom.com tel: 408-985-1824; fax: 408-985-1936 PROCASE Corporation SMARTsystem; C/Spot/Run 2694 Orchard Parkway; San Jose, CA 95134; fax. (408) 435-2600 tel. (408) 433-9500; customer support: 800-777-4776 ProMod, Inc. ProMod Series category: front end, back end, RE/M 23685 Birtcher Dr.; El Toro, CA 92630; 714-855-3046; 800-255-2689 ProtoSoft, Inc. Paradigm Plus 17629 El Camino Real Suite 202, Houston TX 77058; 713-480-3233 FAX 713-480-6606 Rational 1. An integrated, interactive software engineering environment for Ada 2. Rational Rose, object-oriented analysis and design tool Category: front end, back end, development environment, reverse engineering, configuration management 3320 Scott Blvd; Santa Clara, CA 95054; 1-800-767-3237; (408) 496-3600 (ask for Terri Baxter) Ready Systems Corp. CardTools 470 Potrero Ave.; P.O. Box 60217; Sunnyvale, CA 94086 Reasoning Systems Inc. category: reverse engineering, re-engineering 3260 Hillview Ave.; Palo Alto, CA 94304; 415-494-6201 (voice) 415-494-8053 (FAX); reasoning@reasoning.com Sage Software Inc. (merged with Index to form Intersolv) Sapiens International Perfect, Object-Modeller, Sapiens, Quix, Vision Sapiens USA; P.O. Box 4349, Cary, NC, 27519-4349; 1-800-858-9473 Schemacode International Inc Schemacode, Datrix 89 Gleenbrooke, suite 100; Dollard des Ormeaux, Quebec H9A 2L7 514-683-8693; fax 514-683-6792; e-mail: datrix@rgl.polymtl.ca SETT, Inc. GRAMMI - Ada X window GUI builder 5303 Spectrum Drive,; Frederick, MD 21701; (301) 695-6960; info@evb.com Sextant, Incorporated product: Sextant for C category: C programming environment 3881 Sparrow Wood, Ann Arbor, MI 48108; 313-677-0952; info@sextant.com Siemens Nixdorf Industries Sigraph-SET category: case for realtime systems, SDL (CCITT) Postfach 4848, D-8500 Nuernberg 1, Germany; Mr. L. Luedecke; +49 911 895 4362 Six Sigma Case Canonizer 13456 SE 27th Place; Bellevue, WA 98005; 206-643-6911 Softlab, Inc. Maestro category: front end, back end, RE/M 1000 Abernathy Road, Suite 1000, Atlanta GA 30328-5613 Tel: 404-6688-811, Fax: 404-668-8812 Software AG of North America, Inc. Adabas, Natural, Construct, Predict, Predict Case, Super Natural 11190 Sunrise Valley Drive; Reston, VA 22091; 703-860-5050 Software Architecture and Engineering Strategic Networked Application Platform 1600 Wilson Blvd.; Arlington, VA 22209; 703-276-7910 Software Emancipation Technology, Inc. product: ParaSET category: software engineering environment 245 Winter Street; Waltham, MA 02154-8709; +1 (617) 466-8600; 1-800-372-7273; +1 (617) 466-9845 (FAX); sales@setech.com Software Productivity Research, Inc. Checkpoint, SPQR/20 category: estimation, measurement, front end 77 South Bedford St.; Burlington, MA 01803; 617-273-0140 S & P Media GmbH Sigraph-SET category: case for realtime systems, SDL (CCITT) Gadderbaumerstr. 19; D-4800 Bielefeld, Germany StarSys, Inc. MacBubbles category: front end 11113 Norlec Dr.; Silver Spring, MD 20902; 301-946-0522 StructSoft, Inc. TurboCASE 3.0 category: front end (for the Mac) 5416 156th Ave. SE; Bellevue, WA 98006; tel: 206-644-9834; fax: 206-644-7714 Syscorp International, Inc. MicroStep 1.3 9420 Research Blvd., Suite 200; Austin, TX 78759; 512-338-0591 System Software Associates AS/Set 500 W. Madison; Chicago, Ill. 60606; 312-641-2900 Systematica Ltd. VSF (Virtual Software Factory) Eastern Regional Office; 703-368-9864; 408-437-7743 (Katie Wiederholt) TeamOne Systems Inc, TeamNet category: Configuration Management 2700 Augustine Drive; Santa Clara, CA 95054; 800-442-6650 [Aug 1992 e-mail gave address: 710 Lakeway Drive, Suit 100; Sunnyvale, CA 94086; Tel: 408-730-3500] TeleLOGIC Malmoe AB SDT - The SDL Design Tool Kungsgatan 6; Box 4128; S-203 12 Malmoe; Sweden; Tel. +46-40 17 47 00 FAX: +46-40 17 47 47; E-Mail: Support@TeleLOGIC.se US and Canadian distributor: Anonymix inc.; 50 University Ave. Los Gatos, CA 95030; Phone: (408) 399-5030; Fax: (408) 399-5032 Texas Instruments Inc. Information Engineering Facility (IEF) 4.0 6550 Chase Oaks Blvd.; Plano, TX 75023 Local Address: 2950 N.W. 62nd St. Suite 100; Ft. Lauderdale, FL 33309 800-527-3500 TGS Systems Prograph (visual o-o programming environment) Suite 200, 2745 Dutch Village Road; Halifax, Nova Scotia B3L 4G7; Canada; 902/455-4446; FAX: 902/455-2246; tgs-support@fox.nstn.ns.ca Tom Software Application Xcellence 127 SW 156th Street; Seattle, WA 98166; 206-246-7022 Tower Concepts, Inc. Razor category: Issue Tracking and Configuration Management 103 Sylvan Way; New Hartford, NY 13413; (315) 724-3540; sales@tower.com, razor-info@tower.com, razor-manual@tower.co Unisys Corp. Linc Design Assistant, Linc, Mapper, DMS II P.O. Box 500; Bluebell, PA 19424; 215-986-4011 Verilog S.A 150, rue Nicolas-Vauquelin; 31081 Toulouse Cedex-France; Tel:(33)61403888 Fax:(33)61408452; Telex: VERILOG532288F VERILOG USA Inc.; Beauregard Square; #340 6303 Little River Turnpike Alexandria, VA 222312; TEL: (703)354-0371 ViaSoft, Inc. Via/Insight, Via/SmarTest 3033 North 44th St., Suite 280; Phoenix, AZ 85018; 602-952-0050 Visible Systems Corp. Visible Analyst Workbench category: front end 950 Winter St.; Waltham, MA 02154; 617-969-4100 Vista Technologies, Inc. PCTE Workbench, HyperWeb category: Hypermedia-based software development environments 1100 Woodfield Road, suite 108; Schaumburg, IL 60173-5121 USA 708 706-9300 (voice); 708 706-9317 (fax) Visual Software, Inc. vsDesigner, vsSQL, vsObject Maker category: front end 3945 Freedom Circle, Suite 540; Santa Clara, CA 95054; 408-988-7575 Westmount Technology B.V. ISEE, TSEE, RTEE category: front end 5655 Lindero Canyon Road, Suite 521; Westlake Village, CA 91362 818-597-9119; email wmt!gen@nluug.nl Westmount Technology B.V.; Poortweg 8, 2612 PA Delft P.O.Box 5063, 2600 GB Delft; The Netherlands; tel. +31 15 610815 Fax. +31 15 565701 A Systems Corporation PATHVU, RETROFIT category: RE/M 983 University Avenue; Los Gatos, CA 95030; 800-344-9223 (U.S.) 800-344-9224 (Canada) York Software Engineering Ltd. Personal-SELECT, Project-SELECT, CADiZ (Computer Aided Desigin in Z), ACE (ADA Compiler Environment) category: front end University of York; York, England YO1 5DD; tel: +44 (0)904 433741 fax: +44 (0)904 433744 Yourdon, Inc. Analyst/Designer Toolkit, Cradle category: front end 1501 Broadway; New York, NY 10036; 212-391-2828 -- Software Technology Laboratory dalamb@qucis.queensu.ca (David Alex Lamb) Computing and Information Science phone: (613) 545-6067 Queen's University, Kingston, Ontario, Canada K7L 3N6 -- rbotting@wiley.csusb.edu. rbotting::=`Dr. Richard J. Botting`, wiley::=`Faculty EMail System`, csusb::=`California State University, San Bernardino, CA 92407, USA`.