From portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalamb Sun Mar 12 16:25:27 1995Path: portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalambFrom: dalamb@qucis.queensu.ca (David Alex Lamb)Newsgroups: comp.software-eng,comp.answers,news.answersSubject: Comp.software-eng FAQ (Part 0): periodic postings and archivesSupersedes: <faqmsg_791979328@qucis.QueensU.CA>Followup-To: comp.software-engDate: 12 Mar 1995 10:16:28 GMTOrganization: Computing and Information Science, Queen's University at Kingston, Ontario,  K7L 3N6, CanadaLines: 232Approved: news-answers-request@MIT.EduDistribution: worldExpires: 23 Apr 1995 10:15:37 GMTMessage-ID: <faqmsg_795003337@qucis.QueensU.CA>Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb)NNTP-Posting-Host: quilt.qucis.queensu.caKeywords: FAQOriginator: dalamb@qucis.queensu.caXref: portal.gmu.edu comp.software-eng:12710 comp.answers:7500 news.answers:23636Last-Modified: 12 Mar 1995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 four others, eachsummarizing a set of "frequently asked questions" (FAQs):    Comp.software-eng FAQ (Part 1): questions and answers    Comp.software-eng FAQ (Part 2): CASE tools summary    Comp.software-eng FAQ (Part 3): readings    Comp.software-eng FAQ (Part 4): CASE tool vendors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/part4.------------------------------------------------------------------------Subject: World-Wide Web archivesDate: 28 Oct 1994The information in the FAQs and the comp.software-eng archives is availablethrough the World-Wide Web (via browsers such as Mosaic and Lynx) at URL    http://www.qucis.queensu.ca:1999/Software-Engineering/Everything visible through the Web is also available via FTP;  the above URLleads to the same directory as you get via anonymous FTP to    ftp://ftp.qucis.queensu.ca/pub/software-eng/www------------------------------------------------------------------------Subject: other newsgroupsDate: 28 Oct 1994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.human-factors	  Human factors, including user interfaces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.software.testing     Software testingcomp.software.config-mgmt Configuration management and problem trackingcomp.specification        Formal specification methodscomp.specification.z      The Z formal specification notationcomp.sw.components        Reusable software components------------------------------------------------------------------------Subject: comp.software-eng archivesDate: 29 Oct 1994The following files are available via anonymous FTP from    ftp://ftp.qucis.queensu.ca/pub/software-eng/archive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/archive 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 <bytes>' command to set a threshold, above which the server willsplit files into several messages.Readings  26 Jan 1993 ada: bibliography on Ada and software engineering  13 May 1992 aiswe: readings: artificial intelligence and soft.eng.   7 Jul 1992 fault: Fault Tolerance references  13 Feb 1992 readcase: Bibliography on CASE  22 May 1992 reflist: Tero Ahtee's software engineering reference list  15 Feb 1992 statecharts: Reference list on Harel's statecharts  10 Apr 1992 verification: References on program verifier designBook reviews  27 Mar 1992 reviewJapanSoftFactory.html: Michael A. Cusumano: "Japanese              Software Factories"  31 Mar 1992 reviewFowlerRifkin.html: Priscilla Fowler and Stan Rifkin:              "Software Engineering Process Group Guide"  31 Mar 1992 reviewMarksTesting.html: David M. Marks "Testing Very Big              Systems"  29 Oct 1994 reviewNeumannRisks.html: Peter G. Neumann's "Computer-Related              Risks"  31 Mar 1992 reviewOuldTesting.html: Ould and Unwin's "Testing in Software              Development"  31 Mar 1992 reviewWeinbergQuality.html: Gerald M. Weinberg's "Quality              Software Management - Volume 1: Systems Thinking"Tools   2 Oct 1991 CASEexp: experience with CASE tools  31 Jul 1993 cmtools: Configuration management tools  31 Jul 1993 diagramedit: Diagram editors and tools for building them   7 Jul 1992 pdcase: Public-domain CASE tools  26 Mar 1993 performance: performance analysis tools   7 Jul 1992 petri: Petri net tools  30 Jul 1993 pmtools: Project management and design tools  13 Apr 1992 probtrack: Problem tracking tools   7 Jul 1992 restruct: Tools for restructuring and reverse engineering  21 Oct 1991 statsTool: X-based statistics and graphing packages  30 Jul 1993 syslevel: Realtime/hardware system-level CASE tools  31 Jul 1993 testTools: Tools for testing  15 Feb 1992 transynth: Transformation/synthesis systems   3 Aug 1993 uims: User Interface Management SystemsUncatalogued topics  31 Jul 1993 2167a: DoD-Std-2167a and life cycle models  31 Jul 1993 anecdote: Anecdotes/stories about software engineering  10 Sep 1991 bachman: Bachman information modeling   9 Jul 1993 bookTOC: Tables of contents of books  31 Jul 1993 cdif: CASE Data Interchange Format  30 Jul 1993 cleanroom: Cleanroom software development   4 Jun 1992 color: Ergonomics of color displays  31 Jul 1993 concur: Concurrent Engineering  28 Feb 1992 cubicle: Productivity effect of offices vs. cubicles  26 Mar 1993 defect: Defect tracking   7 Jul 1992 designchange: Effect of design changes  30 Jul 1993 education: Software Engineering education and degree programs  15 May 1992 environment: Software Engineering environments  11 Dec 1992 ethics: ACM code of ethics  18 Sep 1991 facet: Faceted classification and multiple inheritance  29 Oct 1994 FDA.html: Food and Drug Administration and Software  31 Jul 1993 formal: formal methods in the USA  10 Apr 1992 funcpoints: function/feature points   2 Oct 1991 hood: Hierachical Object-Oriented Design  31 Jul 1993 horror: Computer horror stories  11 Oct 1991 hungarian: papers on Hungarian notation   2 Oct 1991 ieee: IEEE software engineering standards  30 Jul 1993 inspect: Code inspection techniques  31 Jul 1993 knowuser: Discussion on whether to ``know the user''  31 Jul 1993 lotos: Language of Temporal Ordering of Specifications   9 Apr 1992 maint: Software maintenance laws   6 Mar 1992 manuals: Guidelines for software manuals  31 Jul 1993 maturity: SEI Capability Maturity Model  30 Jul 1993 oodb: Object-oriented databases  10 Jan 1992 ooformat: Format for object-oriented design documents  10 Apr 1992 oomaint: maintenance and complexity in o-o systems  31 Jul 1993 oomethod: Object-oriented methodologies  30 Jul 1993 portableC: writing portable C code  18 Sep 1991 productivity: Feature point productivity for several countries   7 Jul 1992 proto: Prototyping  15 Feb 1992 readintro: Introducing your manager/customer to SE ideas  15 Feb 1992 realtime: Information on realtime software development  31 Jul 1993 reqelicit: Requirement Elicitation  31 Jul 1993 reuse: Discussion of software re-use.  31 Jul 1993 safety: Formal methods and software safety  31 Jul 1993 SEorigin: Origin of term ``software engineering''  15 Feb 1992 specmark: SPEC modern architecture benchmarks  10 Jan 1992 spiral: References on Spiral life-cycle model  31 Jul 1993 standards: standards relevant to software engineering   2 Nov 1994 static.html: Software metrics and static analysis  31 Jul 1993 strucAD: Stuctured analysis and design and SADT  10 Apr 1992 techTransfer: Technology transfer  31 Jul 1993 testing: Discussion of testing (and inspection)  31 Jul 1993 vdm-z: formal methods Z and VDM------------------------------------------------------------------------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.Books  22 Oct 1994 ooexample: Berard Software Engineering's "A Complete Object-              Oriented Design Example"  22 Oct 1994 ooproj: Berard Software Engineering's "A Project Management              Handbook for Object-Oriented Software Development"   4 Nov 1994 FKNprocess.html: Finkelstein et al.'s Software Process              Modelling and Technology  31 Jul 1993 jaloteSEtext: P.Jalote's "An Integrated Approach to Software              Engineering"  31 Jul 1993 schach2e: Schach's "Basic Software Engineering" textDiscussion of tools  31 Jul 1993 cvs: CVS version management tool  31 Jul 1993 ief: TI Information Engineering Facility (IEF)  31 Jul 1993 PCTE-ATIS-CAIS: Discussion of PCTE vs ATIS vs CAIS  29 Oct 1994 ooadTools.html: Evaluation of OO Analysis and Design Tools  31 Jul 1993 rcs: RCS version control system  31 Jul 1993 rdd-100: RDD-100 Requirements Driven Developer  31 Jul 1993 stp-teamwork: Comparison of Software Thru Pictures and Cadre              TeamworkSubmissions from vendors  31 Jul 1993 aegis: AEGIS project change supervisor  31 Jul 1993 autoplan: AUTOPLAN project scheduling tool  28 Oct 1994 ccover.html: Bullseye Software's C-Cover test coverage              analyser  27 Oct 1994 cadre.html: Cadre Technologies Inc.  31 Jul 1993 caseware: CASEWARE configuration management and problem              tracking  27 Oct 1994 cmvc: IBM Configuration Management Version Control (CMVC)  27 Oct 1994 CMZ: CMZ source code management system  27 Oct 1994 DDTS: Distributed Defect Tracking System (QualTrak)  31 Jul 1993 FIELD: Brown University FIELD environment  12 Dec 1994 Hindsight.html: Advanced Software Automation's Hindsight              toolset  31 Jul 1993 IFAD: IFAD VDM-SL toolbox  27 Oct 1994 LDRA: LDRA testbed   8 Dec 1994 MacAnalyst.html: Excel Software's MacAnalyst and MacDesigner              tools   1 Nov 1994 OOD.html: Prof. Taegyun Kim's Object Oriented Designer  31 Jul 1993 objectime: ObjecTime real-time object-oriented methodology              tool  31 Jul 1993 ParaSET: ParaSET parametric software development  31 Jul 1993 parcplace: ParcPlace Smalltalk and C++ tools  31 Jul 1993 PurePulse: Pure Pulse software newsletter  31 Jul 1993 rational: Rational Inc. Ada environment, Rose OOD tool  31 Jul 1993 RAZOR: RAZOR issue tracking, configuration management  23 Jan 1995 robochart.html: Robochart diagram editor  31 Jul 1993 sextant: SEXTANT UNIX/C environment  31 Jul 1993 shapetools: shapetools version management/make-like tool  31 Jul 1993 specbox: SpecBox VDM support tool  31 Jul 1993 telelogic: Telelogic Environment for CCITT SDL  27 Oct 1994 TomSawyer: Graph Layout Toolkit from Tom Sawyer Software  31 Jul 1993 vista: Vista Technologies  31 Oct 1994 Westmount.html: Westmount Technology BV I-CASE tools   4 Nov 1994 Vantive.html: Vantive Qualtity problem tracking system  28 Oct 1994 VSF.html: Virtual Software Factory products-- 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	From portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!swrinde!cs.utexas.edu!uwm.edu!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalamb Sun Mar 12 16:25:27 1995Path: portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!swrinde!cs.utexas.edu!uwm.edu!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalambFrom: dalamb@qucis.queensu.ca (David Alex Lamb)Newsgroups: comp.software-eng,comp.answers,news.answersSubject: Comp.software-eng FAQ (Part 1): questions and answersSupersedes: <questmsg_791979328@qucis.QueensU.CA>Followup-To: comp.software-engDate: 12 Mar 1995 10:16:32 GMTOrganization: Computing and Information Science, Queen's University at Kingston, Ontario,  K7L 3N6, CanadaLines: 312Approved: news-answers-request@MIT.EduDistribution: worldExpires: 23 Apr 1995 10:15:37 GMTMessage-ID: <questmsg_795003337@qucis.QueensU.CA>References: <faqmsg_795003337@qucis.QueensU.CA>Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb)NNTP-Posting-Host: quilt.qucis.queensu.caKeywords: FAQOriginator: dalamb@qucis.queensu.caXref: portal.gmu.edu comp.software-eng:12711 comp.answers:7501 news.answers:23637Last-Modified:  5 Dec 1994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: 27 Oct 1994Archive file: casemsg (thanks to Scott McGregor <mcgregor@netcom.com> 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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: 27 Oct 1994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: 27 Oct 1994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: 27 Oct 1994Archive file: static.html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: 27 Oct 1994This is answered regularly in the comp.lang.c FAQ.  Try "Recommended C styleand Coding Standards", via anonymous FTP to site archive.cis.ohio-state.edu indirectory pub/style-guide------------------------------------------------------------------------Subject: What is 'Hungarian Notation'?Date: 27 Oct 1994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: 27 Oct 1994Archive file: static.html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 Software Engineering Economics, claims thatanomalies that seriously "fool" the LOC metric show up rarely in real code.-    R. Nelson Software Date Collection and Analysis at RADC, Rome Air     Development Center, Rome, NY.  1978.------------------------------------------------------------------------Subject: Should software professionals be licenced/certified?Date: 27 Oct 1994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: 27 Oct 1994Try using the World-Wide Web via URL http://www.sei.cmu.edu/.  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)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: 31 Oct 1994API stands for Application Programming Interface.  For a useful subset ofstandard APIs that NIST considers relevant to US Federal government needs, youcan look at NIST SP 500-187 "Application Portability Profile," using theWorld-Wide Web via URL http://nemo.ncsl.nist.gov/app-ose/, or send mail tomail-server@nemo.ncsl.nist.gov with    send app-ose/app2.txtin the body, or 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 Software       Testing Techniques 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           computer 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: 28 Oct 1994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.ANSI and ANSI equivalent ISO standards are available from    ASQC Quality Press    Customer Service Department    P.O. Box 3066    Milwaukee, WI 53201-3066    Voice: (800) 248-1946    FAX:   (414) 272-1734For ITU (formerly CCITT) standards, see the ITU using the World-Wide Web viaURL gopher://info.itu.chor use their mail server: mail to itudoc@itu.ch withno subject and the following body:    START    HELP    END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	From portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalamb Sun Mar 12 16:25:27 1995Path: portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalambFrom: dalamb@qucis.queensu.ca (David Alex Lamb)Newsgroups: comp.software-eng,comp.answers,news.answersSubject: Comp.software-eng FAQ (Part 2): CASE tools summarySupersedes: <casemsg_791979328@qucis.QueensU.CA>Followup-To: comp.software-engDate: 12 Mar 1995 10:16:34 GMTOrganization: Computing and Information Science, Queen's University at Kingston, Ontario,  K7L 3N6, CanadaLines: 276Approved: news-answers-request@MIT.EduDistribution: worldExpires: 23 Apr 1995 10:15:37 GMTMessage-ID: <casemsg_795003337@qucis.QueensU.CA>References: <faqmsg_795003337@qucis.QueensU.CA>Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb)NNTP-Posting-Host: quilt.qucis.queensu.caKeywords: FAQOriginator: dalamb@qucis.queensu.caXref: portal.gmu.edu comp.software-eng:12712 comp.answers:7502 news.answers:23638Last-Modified:  4 Mar 1995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    Configuration management and problem tracking tools    CASE tools for object-oriented design and analysis    CASE tools for educational use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: Configuration management and problem tracking toolsDate: 28 Oct 1994This FAQ used to contain information on configuration management and problemtracking tools.  With the advent of newsgroup comp.software.config-mgmt, it'smore appropriate to go looking in its FAQs, available using the World-Wide Webvia URL http://www.iac.honeywell.com/Pub/Tech/CM/.------------------------------------------------------------------------Subject: CASE tools for object-oriented design and analysisDate:  4 Mar 1995Originally collected by: calvo@nssdca.gsfc.nasa.gov (Sherri Calvo)Berard Object & Class Specifier (BOCS) by Berard Software Engineering (see  vendor list).BOCS is an object-oriented analysis and design CASE tool for developing modelsof software & business systems and their underlying objects (classes,parameterized classes, and instances of classes).  BOCS is used to createprogramming language independant specifications, then automatically generateformatted documentation combining text and graphics into popular publishingpackages.  BOCS also provides code generation for C++ and Smalltalk.  Thetraceability tool allows users to trace requirements to design and code.  BOCSruns on Microsoft Windows 3.1 (TM).  $595 per copy.  - [russ@bse.com (RussellHopler)]Cadre Teamwork (see http://www.qucis.queensu.ca:1999/Software-  Engineering/blurb/cadre.html) by Cadre Technologies, Inc (see vendor list).Associated with Project Technology.  ObjecTeam for Shlaer/Mellor, Rumbaugh.Ada structure graphs (Booch/Buhr).CASET .714-496-8670 IPSYS ToolBuilderHOOD (Hierarchical Object Oriented Design) by 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@logica.comNow mandatory for several European Space Agency projects.by Interactive Development Environments (see vendor list).Extension of Ada design tools to handle OOPLs, primarily C++.  IDE also has aproduct called StP/OMT (Software through Pictures/Object Modeling Technique)which is solded both through IDE and through the Advanced Concepts Center (ACC)of Martin Marietta (MMC).  Both companies also provide training on the tool.The tool supports the Rumbaugh OMT methodology.ObjecTime (see http://www.qucis.queensu.ca:1999/Software-  Engineering/blurb/objectime) by 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) by Mark V Systems, Ltd. (see vendor list).Runs under Windows, X11, VMS (Mac under development).  Support for OMT(Rumbaugh et al), Booch, Coad-Yourdon, and other object-oriented and structuredmethods.  Tailorable for new (and combinations of existing) methods.  Codegeneration and reverse engineering for Ada, C/C++ (others planned).  Generationof diagrams from the repository.  Support for process modeling notations.Interoperation with other tools via DDE, OLE, TCP/IP, etc.  - [dwig@markv.com(Don Dwiggins)]OOAtool by Object International, Inc. (see vendor list).Runs under Windows, Mac, and X11.  Supports methodology in Peter Coad's books"Object-Oriented Analysis" and "Object-Oriented Design".OOTher .(OO Documentation Tool); once called OoaToolFree Rel 1.06a (for win 3.1).Supports Coad's OOA/OOD, Jacobson OOSE (parts) and Finite State Machinenotation (a subset of SDL) and C++ header file generaetion.  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:<msdos.windows3>OOT-106d.ZIP UUENCODEParadigm Plus / EVB Edition by EVB Software Engineering, Inc. (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 by Rational (see vendor list).Supports Booch methodology.  Available for SunOS, AIX, MS Windows, OS/2.Robochart (see http://www.qucis.queensu.ca:1999/Software-  Engineering/blurb/robochart.html) by Digital Insight (see vendor list).Interactive diagram editor for OPEN LOOK & Motif ($495); Does hierarchicalERDs, dataflows, etc. Educational discounts. Free evaluation copy via anonymousFTP to site ftp.csn.org in directory digins.System Architect by Popkin Software & Systems (see vendor list).Supports ER diagrams, Booch methodology for Ada and C++, Coad/Yourdon.  Diagrameditor checks for consistency and rule violations.  Runs under MS-Windows.VSF (see http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/VSF.html)  by Virtual Software Factory Ltd. (see vendor list).(formerly Systematica) Tool of same name as company is a meta-CASE configurabletool incorporating a KBS.Unirel Openlook Toolkit by Unirel (see vendor list).An Eiffel wrapper for Xlib.  US $2000Objectory by Objective Systems (see vendor list).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.MetaEdit by MetaCase Consulting OY (see vendor list).An upper-CASE tool that supports most available structured and OO analysis anddesign methods, and can be customized to support user-defined methods.  As ofSeptember 1993 it supports Booch, Coad/Yourdon, Demeter, Express-G, Rumbaugh,Gane-Sarson, ER, JSP, and many more. MetaEdit is available for MS-Windows 3.1.Its as metaed10.zip. A method definition workbench for users who want to definetheir own methods themselves is available. Academic and educational licensescan also be obtained.Graphical Designer by Advanced Software Technologies, Inc. (see vendor list).A Unix based software development tool supporting Rumbaugh, Shlaer-Mellor,Booch, Data Flow, Entity-Relationships and others A custom methodology can becreated as needed to express high and low level designs in a graphical format.Generates detailed C++, C and Ada code.  Also provides extensive diagram layoutfeatures and user extensible symbol sets.  It is available on HP9000/7-800 (HP-UX), SPARC (SunOS, Solaris), and SGI (IRIX).  - [riedesel@advancedsw.com (JoelRiedesel)]------------------------------------------------------------------------Subject: CASE tools for educational useDate:  7 Nov 1994Originally collected by: render@zeppo.colorado.edu (Hal Render)Teamwork by Cadre Technologies, Inc (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) by IPSYS Software Plc (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 by FZI (see vendor list).(see also 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 <schiefer@fzi.de>]Rational Environment by 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<rjg@gator.Rational.COM>]Objectory by Objective Systems (see vendor list).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.OOD (see http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/OOD.html)  by Prof. Taegyun Kim of Pusan University in South Korea.A free tool for educational use, based on Rumbaugh's Object Modeling Technique.Prof. Kim has built it on a SPARC, but it should build on most UNIX systemswith X11-R5, Motif-1.2 and a "reasonable" C++ compiler.-- 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	From portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalamb Sun Mar 12 16:25:28 1995Path: portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!howland.reston.ans.net!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalambFrom: dalamb@qucis.queensu.ca (David Alex Lamb)Newsgroups: comp.software-eng,comp.answers,news.answersSubject: Comp.software-eng FAQ (Part 3): readingsSupersedes: <readmsg_791979328@qucis.QueensU.CA>Followup-To: comp.software-engDate: 12 Mar 1995 10:16:36 GMTOrganization: Computing and Information Science, Queen's University at Kingston, Ontario,  K7L 3N6, CanadaLines: 761Approved: news-answers-request@MIT.EduDistribution: worldExpires: 23 Apr 1995 10:15:37 GMTMessage-ID: <readmsg_795003337@qucis.QueensU.CA>References: <faqmsg_795003337@qucis.QueensU.CA>Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb)NNTP-Posting-Host: quilt.qucis.queensu.caKeywords: FAQOriginator: dalamb@qucis.queensu.caXref: portal.gmu.edu comp.software-eng:12713 comp.answers:7503 news.answers:23639Last-Modified:  5 Dec 1994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        Professional Journals        Mixed Research and Practice        Research Journals        Other magazines    Other sources of information    General reading for software engineers        General        Programming in the large        Programming in the small        Mathematical Approaches        Other    Formal Specification    Metrics        Metrics - General        Metrics for object-oriented systems    Object-Oriented Analysis and Design    Programming Style    Real-Time Systems    Requirements Analysis        Requirements Analysis - General        Collaborative Requirements Analysis    Software Process    Software Testing    User Interfaces        Human-Computer Interaction -- General        User Interface Development -- General        User Interface Design -- Principles and Guidelines        User Interface Development - Software        User Interface Evaluation        Styleguides for Specific Platforms        Human Factors and Ergonomics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: 22 Oct 1994Originally collected by: hsrender@happy.colorado.edu (Hal Render)The first 8 items are Hal Render's original list in his rough order of prefer-ence.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&#3, 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&#3, 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&#2, 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@murphy.ICS.UCI.EDU (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: 27 Oct 1994A. Professional JournalsMeant for working professionals with technical backgrounds.   1.  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   2.  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   3.  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   4.  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   5.  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B. Mixed Research and Practice   1.  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   2.  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.   3.  Software: Practice and Experience       summary: not always software engineering; good reputation for practice       publisher: Wiley (see above)   4.  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C. Research JournalsMeant for presenting recent research results.   1.  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   2.  Transactions on Software Engineering (TSE)       summary: main software engineering research journal       publisher: IEEE (see above)   3.  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   4.  Journal of Systems and Software       summary: meant to be more practitioner-oriented than other research         journals       publisher: ElsevierD. Other magazines   1.  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   2.  Testing Techniques Newsletter       summary: E-mailed on a monthly basis to support the publisher's         customers and to provide information of general use to the testing         community.       publisher: Software Research, Inc.,  625 Third Street,  San Francisco,         CA 94107-1997; Phone: (415) 957-1441; Toll Free: (800) 942-SOFT; FAX:         (415) 957-0730; E-MAIL: ttn@soft.com.------------------------------------------------------------------------Subject: Other sources of informationDate: 22 Oct 1994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?"A. General   1.  Read about 100 pages of comp.risks   2.  Frederick P. Brooks, Jr., The Mythical Man-Month, Addison Wesley, 1978.       ISBN 0-201-00650-2   3.  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"   4.  Paul W. Oman & Ted G. Lewis, Milestones in Software Evolution, IEEE       Computing Society, ISBN 0-8186-9033-X.   5.  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.B. Programming in the large   1.  Grady Booch, Software Engineering with Ada, second edition,       Benjamin/Cummings, 1987   2.  Bertrand Meyer, Object-Oriented Software Construction, Prentice-Hall,       1988.   3.  David L. Parnas, On the Criteria to be Used in Decomposing Systems into       Modules, Communications of the ACM 15,2 (December 1972).C. Programming in the small   1.  Jon Louis Bentley, Writing Efficient Programs, Prentice-Hall, 1982.   2.  Jon Bentley, Programming Pearls, Addison-Wesley, 1986.   3.  Jon Bentley, More Programming Pearls, Addison-Wesley, 1988.   4.  O.-J. Dahl, E.W. Dijkstra, C.A.R. Hoare, Structured Programming,       Academic Press, 1972.   5.  Brian W. Kernighan, and P.J. Plauger, Software Tools, Addison-Wesley,       1976.   6.  Brian W. Kernighan & P.J. Plauger, The Elements of Programming Style,       Second Edition, McGraw-Hill, 1978. ISBN 0-07-034207-5.D. Mathematical Approaches   1.  Edsger W. Dijkstra, A Discipline of Programming, Prentice-Hall, 1976.   2.  E.W.Dijkstra.  Selected writings on computing: a personal perspective.       Springer Verlag, 1982.   3.  David Gries (editor), Programming methodology. A collection of articles       by members of IFIP Working Group 2.3. Springer Verlag, 1978.E. Other   1.  Barry W. Boehm, Software Engineering Economics, Prentice-Hall, 1981.   2.  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.   3.  Tom Gilb, Principles of Software Engineering Management, Addison-Wesley,       1988, ISBN 0-201-19246-2   4.  Glenford J. Myers, The Art of Software Testing, Wiley, 1979.   5.  Herb Simon, The Sciences of the Artificial, Second Edition, MIT Press,       1981   6.  Gerald M. Weinberg, The Psychology of Computer Programming, Van Nostrand       Reinhold, 1971. ISBN 0-442-29264-3------------------------------------------------------------------------Subject: Formal SpecificationDate: 29 Mar 1993See also the comp.specification.z FAQ.1.  J.M.Spivey.  "Understanding Z: a specification language and its formal    semantics".  Cambridge University Press, 1988.2.  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.3.  B.Potter, J.Sinclair & D.Till.  "An introduction to formal specification    and Z".  Prentice Hall International Series in Computer Science, 1991.4.  D.Bjorner & C.B.Jones.  "Formal Specification & Software Development",    Prentice-Hall International Series in Computer Science, 1980.5.  N.Gehani & A.D.McGettrick (eds).  "Software Specification Techniques",    Addison-Wesley Publishing Company, 19866.  I. van Horebeek & J.Lewi.  "Algebraic Specifications in Software    Engineering", Springer Verlag, 1989.7.  J.Bergstra, P.Klint & J.Heering.  "Algebraic Specification", ACM Frontier    Press Series. The ACM Press in co-operation with Addison-Wesley, 1989.8.  J.Wing.  "A specifiers introduction to formal methods", IEEE Computer    23(9):8-24, 1990.9.  Prehn & Soetenel (eds).  "Formal Software Development Methods, VDM'91",    LNCS 551 and 552, Springer-Verlag.------------------------------------------------------------------------Subject: MetricsDate: 22 Oct 1994A. Metrics - General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.   1.  David N. Card and Robert L. Glass.  Measuring Software Design Quality       Prentice Hall, Engewood Cliffs, New Jersey, 1990   2.  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   3.  Tom DeMarco.  Controlling Software Projects: Management, Measurement and       Estimation.  Englewood Cliffs, N.J.: Prentice Hall, 1982   4.  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.   5.  Reiner Dumke.  Softwareentwicklung nach Ma`s - Sch`atzen - Messen -       Bewerten, Vieweg Verlag, 1992.   6.  Lem Ejiogu.  Software Engineering with Formal Metrics.  QED Information       Sciences, 1991   7.  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.   8.  Robert B. Grady and Deborah L. Caswell.  Software Metrics: Establishing       a Company-Wide Program, Prentice-Hall, 1987, ISBN 0-13-821844-7   9.  Robert B. Grady.  Practical Software Metrics for Project Management and       Process Improvement.  Prentice Hall 1992 ISBN 0-13-720384-5   10. M.H. Halstead.  Elements of Software Science.  New York, Elsevier North-       Holland, 1977   11. S. Henry, D. Kafura, "Software Structure Metrics Based on Information       Flow", IEEE Transactions on Software Engineering, Vol.SE-7, No.5,       September 1981.   12. 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   13. 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   14. T.J. McCabe, A Complexity Measure, IEEE Transactions on Software       Engineering, VOL. SE-2, NO. 4, Dec. 1976.   15. Alan Perlis, Frederick Sayward, Mary Shaw.  Software Metrics: An       Analysis and Evaluation.  The MIT Press, 1981   16. 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.   17. 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   18. Horst Zuse, Software Complexity: Measures and Methods, de Gruyer (200       Saw Mill River Road, Hawthorne, NY 10532 - 914/747-0110) 1991B. Metrics for object-oriented systems   1.  Morris Kenneth L.  Metrics for Object-Oriented Software Development       Environments (master's thesis). 1989, MIT.   2.  Rocacher, Daniel: Metrics Definitions for Smalltalk.  Project ESPRIT       1257, MUSE WP9A, 1988.   3.  Rocacher, Daniel: Smalltalk Measure Analysis Manual.  Project ESPRIT       1257, MUSE WP9A, 1989.   4.  Lake, Al: A Software Complexity Metric for C++.  Annual Oregon Workshop       on Software Metrics, March 22-24, 1992, Silver Falls, Oregon, USA.   5.  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: Object-Oriented Analysis and DesignDate: 26 Mar 1993Originally collected by: haim@taichi.uucp (24122-kilov)1.  Bertrand Meyer.  Object-oriented software construction. Prentice-Hall, 1988    For the somewhat advanced - perhaps, with some programming maturity.2.  B. Henderson-Sellers.  A book of object-oriented knowledge. Prentice-Hall,    1992.  This has quite a few viewgraphs in it!3.  Grady Booch.  Object-oriented design with applications.  Addison-Wesley,    1991.4.  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)1.  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.2.  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.3.  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.4.  E. Thomas & P. Oman "A Bibliography of Programming Style Literature," ACM    SIGPLAN Notices, Vol. 25(2), Feb. 1990, pp.  7-16.------------------------------------------------------------------------Subject: Real-Time SystemsDate: 22 Oct 1994Originally collected by: jaws@sj.ate.slb.com (John Willmore)1.  Derek J. Hatley and Imtiaz A. Pirbhai.  Strategies for Real-Time System    Specification Dorset House, 19872.  Paul Ward and Stephen Mellor.  Structured Development for Real-Time Systems    Yourdon Press, 1985------------------------------------------------------------------------Subject: Requirements AnalysisDate: 29 Oct 1994A. Requirements Analysis - General   1.  Al Davis, Software Requirements: Objects, Functions, & States.       Prentice-Hall, 1993.  A revision of #2 (below).   2.  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).   3.  Donald C. Gause and Gerald M. Weinberg, Exploring Requirements: Quality       before design.  Dorset House Publishing, 353 West 12th Street, New York,       NY 10014   4.  Richard H. Thayer and Merlin Dorfman (editors), Software Requirements       Engineering, IEEE Computer Society Press, Los Alamitos, CA, 1990.B. Collaborative Requirements Analysis(thanks to Annie I. Anton, anton@cc.gatech.edu).   1.  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.   2.  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.   3.  Marca, D.  "Specifying Groupware Requirements From Direct Experience",       Proc 6th International Workshop On Software Specification And Design,       October 1991   4.  Marca, D.  "Augmenting SADT To Develop Computer-Supported Cooperative       Work", Proceedings of the International Conference on Software       Engineering; May 1991   5.  Marca, D.  "Experiences in Building Meeting Support Software",       Proceedings of the 1st Groupware Technology Workshop; August 1989   6.  Marca, D.  "Specifying Coordinators: Guidelines for Groupware       Developers", Proceedings of the 5th International Workshop on Software       Specification and Design; May 1989------------------------------------------------------------------------Subject: Software ProcessDate: 25 Oct 1994Originally collected by: cml@cs.umd.edu (Christopher Lott)1.  Watts S. Humphrey.  Managing the Software Process.  Addison-Wesley    Publishing Co., Reading, Massachusetts, 1989; Chapters 13--15, 18.2.  Bill Curtis, Marc I. Kellner and Jim Over.  "Process Modeling,"    Communications of the ACM, Sept 92, Vol 35, No 9, 75-90.3.  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.4.  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.5.  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.6.  Barry W. Boehm.  "A Spiral Model of Software Development and Enhancement",    IEEE Computer, v.~21, n.~5, May 1988, pp.~61--72.7.  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.8.  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.9.  Leon Osterweil.  "Software Processes are Software Too", Proceedings of the    Ninth International Conference on Software Engineering, Monterey, CA, March    1987, pp.~2--13.10. 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.11. Peter H. Feiler and Watts S. Humphrey.  "Software Process Development and    Enactment:  Concepts and Definitions", Software Engineering Institute,    Carnegie Mellon University, Pittsburgh, PA, 1991.12. 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.13. 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.14. 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.15. 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.16. 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.17. 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.18. 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.19. 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.------------------------------------------------------------------------Subject: Software TestingDate: 27 Oct 1994The original request that prompted the posting of this information asked forrecent work, not buried in a Software Engineering tome.1.  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.2.  Cheatham and Mellinger, Testing Object Oriented Software Systems,    Proceedings of the 1990 ACM SCS Conference3.  William C. Hetzel, The Complete Guide to Software Testing, Second edition,    QED Information Services INC, 1988.  ISBN 0-89435-242-34.  Testing Techniques Newsletter (see periodicals)------------------------------------------------------------------------Subject: User InterfacesDate: 25 Oct 1994Originally collected by: perlman@cis.ohio-state.edu (Gary Perlman)This collection of recommended books for user interface developers is based onsearches of The HCI Bibliography, a free-access online bibliography on Human-Computer Interaction.  The bibliography contains the tables of contents ofalmost all of the books listed.  See the files abooks.bib (authored books),ebooks.bib (edited books), and reports.bib (technical reports).  About 10,000bibliographic entries on books, conference proceedings, and journal articlescan be accessed via anonymous FTP to site archive.cis.ohio-state.edu indirectory /pub/hcibib, or email requests can be sent to:     hcibib@cis.ohio-state.eduA. Human-Computer Interaction -- General   1.  Ronald M. Baecker & William A. S. Buxton (Editors).  Readings in Human-       Computer Interaction: A Multidisciplinary Approach.  Los Altos, CA:       Morgan-Kaufmann Publishers, 1987.  ISBN 0-934613-24-9.  This and the       second edition are excellent collection of readings, integrated with       clear and thought-provoking prose by the editors.  This excellent       introduction to the field is also a great value, making it the most used       university text on HCI.   2.  Ronald M. Baecker, Jonathan Grudin, William A. S. Buxton & Saul       Greenberg (Editors).  Readings in Human-Computer Interaction: Toward the       Year 2000 (Second Edition).  Los Altos, CA: Morgan-Kaufmann Publishers,       1994.  ISBN 1-55860-246-1.  This new version is very different from the       first and should be considered a different snapshot of the field.  An       excellent introduction to the field.   3.  Stuart K. Card, Thomas P. Moran & Allen Newell.  The Psychology of       Human-Computer Interaction.  Hillsdale, NJ: Lawrence Erlbaum Associates,       1983.  This classic defines the early theoretical basis for HCI.  It is       primarily for researchers.   4.  Alan Dix, Janet Finlay, Gregory Abowd & Russell Beale.  Human-Computer       Interaction.  Hillsdale, NJ: Prentice Hall, 1993.  ISBN 0-13-458266-7       (hardback); 0-13-437211-5 (paperback) only outside USA.  This is a broad       introduction to HCI, including a clear statement of a user interface       development process.  It should be useful to researchers in training and       practitioners.   5.  Martin Helander (Editor).  Handbook of Human-Computer Interaction.       Amsterdam: North-Holland, 1988.  ISBN 0-444-88673-7 (paper).  This       collection of survey papers contains excellent reference material for       both researchers and practitioners.  The softcover edition is reasonably       affordable.   6.  Jenny Preece, Yvonne Rogers, Helen Sharp, David Benyon, Simon Holland &       Tom Carey.  Human-Computer Interaction.  Wokingham, UK: Addison Wesley,       1994.  ISBN 0-201-62769-8.  This is the latest general HCI textbook.  It       is the first one to contain all the pedagogical features (examples,       exercises, etc.) to make it good for undergraduate and graduate level       use.B. User Interface Development -- General   1.  Deborah Hix & H. Rex Hartson.  Developing User Interfaces: Ensuring       Usability Through Product and Process.  New York, New York: John Wiley &       Sons, Inc., 1993.  ISBN 0-471-57813-4.  This book generated a lot of       positive reviews when it came out.   2.  Ben Shneiderman.  Designing the User Interface: Strategies for Effective       Human-Computer Interaction (Second Edition).  Reading, MA: Addison-       Wesley Publishing Co., 1992.  ISBN 0-201-57286-9.  This is the second       edition of a very popular textbook.  Although it is a survey of user       interface development, it can also be used as a guide for practitioners.C. User Interface Design -- Principles and Guidelines   1.  C. Marlin "Lin" Brown.  Human-Computer Interface Design Guidelines.       Norwood, NJ: Ablex Publishing Corp., 1988.  ISBN 0-89391-332-4.  An good       source of guidelines for graphical interfaces.   2.  James D. Foley, Andries van Dam, Steven K. Feiner & John F. Hughes.       Computer Graphics: Principles and Practice (2nd Edition).  Reading, MA:       Addison-Wesley Publishing Co., 1990.  ISBN 0-201-12110-7.  The second       edition of this classic contains a few chapters on input and output       devices and user interface architecture.   3.  Brenda Laurel (Editor).  The Art of Human-Computer Interface Design.       Reading, MA: Addison-Wesley Publishing Co., 1990.  This is a popular       collection of inspiring readings on design.   4.  Clayton Lewis & John Rieman.  Task-Centered User Interface Design: A       Practical Introduction.  Boulder, Colorado: University of Colorado,       Boulder, 1993.  ftp ftp.cs.colorado.edu/pub/cs/distribs/clewis/HCI-       Design-Book This is the first shareware book on UI design.   5.  Aaron Marcus.  Graphic Design for Electronic Documents and User       Interfaces.  Reading, MA: Addison-Wesley Publishing Co. (ACM Press),       1992.  ISBN 0-201-54363-9; ACM Order number 703900.  This book contains       many examples and includes a comparative study of graphical user       interfaces on different platforms.   6.  Deborah J. Mayhew.  Principles and Guidelines in Software User Interface       Design.  Englewood Cliffs, NJ: Prentice Hall, 1992.  ISBN 0-13-721929-6.       This is an excellent practical guide for effective design.   7.  Donald A. Norman.  The Psychology of Everyday Things.  New York: Basic       Books, 1988.  ISBN 0-465-06709-3.  Also published as The Design of       Everyday Things, 1990, Doubleday ISBN 0-385-26774-6 (paperback).  This       is a very popular book on good (and bad) design of the devices with       which we interact on a daily basis, and as such it provides insights and       inspiration about how to design usable software.   8.  Donald A. Norman & Stephen W. Draper (Editors) User Centered System       Design: New Perspectives on Human-Computer Interaction.  Hillsdale, NJ:       Lawrence Erlbaum Associates, 1986.  ISBN 0-89859-872-9 (paper).  This is       an early set of readings that defined the idea of designing systems for       users first.   9.  Sidney L. Smith & Jane N. Mosier.  Guidelines for Designing User       Interface Software.  ESD-TR-86-278.  Bedford, MA 01730: The MITRE       Corporation, 1986.  ftp archive.cis.ohio-state.edu/pub/hci/Guidelines       This set of guidelines is widely used in military systems, but is based       on mid-80s technology with little on graphical user interfaces.   10. Bruce Tognazzini.  Tog on Interface.  Reading, MA: Addison-Wesley, 1992.       ISBN 0-201-60842-1.  A collection of inspiring columns by the user       interface "evangelist" of the Apple Macintosh.   11. U.S. Department of Defense.  Military Standard: Human Engineering Design       Criteria for Military Systems, Equipment and Facilities.  MIL-STD-1472D       Washington, DC: U.S. Government Printing Office, March 14, 1989.       Section 5.15 of this standard is largely drawn from the MITRE       guidelines.  Macintosh HyperCard stack available via anonymous FTP to       site archive.cis.ohio-state.edu in directory /pub/hci/1472/.D. User Interface Development - Software   1.  Dan R. Olsen, Jr.  User Interface Management Systems: Models and       Algorithms.  Mountain View, CA: Morgan Kaufmann, 1992.  ISBN       1-55860-220-8.  Len Bass & Joelle Coutaz.  Developing Software for the       User Interface.  Reading, MA: Addison-Wesley, 1991.  ISBN 0-201-51056-4.E. User Interface Evaluation   1.  Joseph S. Dumas & Janice C. Redish.  A Practical Guide to Usability       Testing.  Norwood, NJ: Ablex Publishing, 1993.  ISBN 0-89391-991-8.       This step-by-step guide provides checklists and offers insights for       every stage of usability testing.   2.  Jakob Nielsen.  Usability Engineering.  Boston, MA: Academic Press,       1993.  ISBN 0-12-518405-0.  This book immediately sold out when it was       first published.  It is an practical handbook for people who want to       evaluate systems.   3.  Jakob Nielsen & Robert L. Mack (Eds.) Usability Inspection Methods.  New       York: John Wiley & Sons, 1994.  ISBN 0-471-01877-5.  This book contains       chapters contributed by experts on usability inspections methods such as       heuristic evaluation, cognitive walkthroughs, and others.   4.  Randolph G. Bias & Deborah J. Mayhew (Eds.) Cost-Justifying Usability.       Boston: Academic Press, 1994.  ISBN 0-12-095810-4.  This edited       collection contains 14 chapters devoted to the demonstration of the       importance of usability evaluation to the success of software       development.   5.  Michael E. Wiklund (Ed.) Usability in Practice: How Companies Develop       User-Friendly Products.  Boston: Academic Press, 1994.  ISBN       0-12-751250-0.  This collection of contributed chapters describes       usability practices of 17 companies: American Airlines, Ameritech,       Apple, Bellcore, Borland, Compaq, Digital, Dun & Bradstreet, Kodak, GE       Information Services, GTE Labs, H-P, Lotus, Microsoft, Silicon Graphics,       Thompson Consumer Electronics, and Ziff Desktop Information.  It amounts       to the broadest usability lab tour ever.F. Styleguides for Specific PlatformsThe following style guides define (or redefine) a standard to which allapplications on that platform should conform.  Thanks to Samu Mielonen(f1sami@uta.fi) Univ. of Tampere, Finland, for compiling an earlier version ofthe styleguide list.   1.  Apple Computer, Inc.  Macintosh Human Interface Guidelines.  Reading,       MA: Addison-Wesley Publishing Co., 1992.  ISBN 0-201-62216-5.  There is       an interactive animated companion CD-ROM to these Mac guidelines called       "Making it Macintosh", Addison-Wesley, 1993.  ISBN 0-201-62626-8.   2.  Commodore-Amiga, Inc.  Amiga User Interface Style Guide.  Reading,       Mass.: Addison-Wesley, 1991.  ISBN 0-201-57757-7.   3.  GO Corporation.  PenPoint User Interface Design Reference.  Reading, MA:       Addison-Wesley, 1992.  ISBN 0-201-60858-8.   4.  Hewlett-Packard, IBM, Sunsoft Inc. & USL.  Common Desktop Environment:       Functional Specification (Preliminary Draft).  X/Open Company Ltd.,       1993.  ISBN 1-85912-001-6.  ftp XOPEN.CO.UK/pub/cdespec1/cde1_ps.Z   5.  IBM.  Object-Oriented Interface Design: IBM Common User Access       Guidelines.  Carmel, Indiana: Que, 1992.  ISBN 1-56529-170-0.   6.  James Martin, Kathleen Kavanagh Chapman & Joe Leben.  Systems       Application Architecture: Common User Access.  Englewood Cliffs, NJ:       Prentice-Hall, 1991.  ISBN 0-13-785023-9.   7.  Microsoft Corporation.  The GUI Guide: International Terminology for the       Windows Interface.  Redmond, WA: Microsoft Press, 1993.  ISBN       1-55615-538-7.   8.  Microsoft Corporation.  The Windows Interface: An Application Design       Guide.  Redmond, WA: Microsoft Press, 1992.  ISBN 1-55615-384-8.   9.  Open Software Foundation.  OSF/Motif Style Guide.  Englewood Cliffs, NJ:       Prentice Hall, 1993.  ISBN 0-13-643123-2.   10. NeXT Computer, Inc.  NeXTSTEP User Interface Guidelines (Release 3).       Reading, Mass.: Addison-Wesley Publishing, 1992.  ISBN 0-201-63250-0.   11. Sun Microsystems, Inc.  OPEN LOOK Graphical User Interface Application       Style Guidelines.  Reading, Mass.: Addison-Wesley, 1989.  ISBN       0-201-52364-7.   12. Sun Microsystems, Inc.  OPEN LOOK Graphical User Interface Functional       Specification.  Reading, Mass.: Addison-Wesley, 1989.  ISBN       0-201-52365-5.G. Human Factors and Ergonomics   1.  Barry H. Kantowitz & Robert D. Sorkin.  Human Factors: Understanding       People-System Relationships.  New York, NY: John Wiley & Sons, 1983.       ISBN 0-471-09594-X.   2.  Kenneth R. Boff & Janet E. Lincoln (Editors).  Engineering Data       Compendium: Human Perception and Performance.  Wright-Patterson Air       Force Base, Ohio: Harry G. Armstrong Aerospace Medical Research       Laboratory, 1988.   3.  Ernest J. McCormick & M. S. Sanders.  Human Factors in Engineering and       Design.  New York, NY: McGraw-Hill Book Company, 1987.  Perlman expects       soon to review the new edition (7th?) dated 1993.   4.  David Meister.  Human Factors Evaluation and Testing.  Amsterdam:       Elsevier, 1986.   5.  Richard Rubinstein & Harry Hersh.  The Human Factor: Designing Computer       Systems for People.  Maynard, MA: Digital Press, 1984.  ISBN       0-932376-44-4.   6.  Gavriel Salvendy (Editor).  Handbook of Human Factors.  New York: John       Wiley & Sons, 1987.  ISBN 0-471-88015-9.-- 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	From portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!swrinde!cs.utexas.edu!uwm.edu!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalamb Sun Mar 12 16:25:28 1995Path: portal.gmu.edu!hearst.acc.Virginia.EDU!concert!gatech!swrinde!cs.utexas.edu!uwm.edu!spool.mu.edu!torn!news.ccs.queensu.ca!qucis.queensu.ca!dalambFrom: dalamb@qucis.queensu.ca (David Alex Lamb)Newsgroups: comp.software-eng,comp.answers,news.answersSubject: Comp.software-eng FAQ (Part 4): CASE tool vendorsSupersedes: <vendmsg_791979328@qucis.QueensU.CA>Followup-To: comp.software-engDate: 12 Mar 1995 10:16:37 GMTOrganization: Computing and Information Science, Queen's University at Kingston, Ontario,  K7L 3N6, CanadaLines: 566Approved: news-answers-request@MIT.EduDistribution: worldExpires: 23 Apr 1995 10:15:37 GMTMessage-ID: <vendmsg_795003337@qucis.QueensU.CA>References: <faqmsg_795003337@qucis.QueensU.CA>Reply-To: dalamb@qucis.queensu.ca (David Alex Lamb)NNTP-Posting-Host: quilt.qucis.queensu.caKeywords: FAQOriginator: dalamb@qucis.queensu.caXref: portal.gmu.edu comp.software-eng:12714 comp.answers:7504 news.answers:23640Last-Modified: 12 Feb 1995Archive-name: software-eng/part4This is a list of contact information for CASE tool vendors, originallycompiled by Scott Marcus <marcuss@sol.cs.fau.edu> and/or Theo Heavey<theo@cs.fau.edu>, CASE research group, Dept. of Computer Science, FloridaAtlantic University; sponsored by Florida Industry High Technology Council.After they lost their funding for this list, the only way we've been able tokeep it up to date is if people volunteer to tell us what needs to change.Please e-mail corrections to dalamb@qucis.queensu.ca.This information is available through the World-Wide Web as	http://www.qucis.queensu.ca:1999/Software-Engineering/vendor.htmlAdpac Corp.   Adpac CASE Tools   340 Brannan St.; San Francisco, CA 94107; 415-974-6699Advanced Concepts Center   Martin Marietta Corporation; 640 Freedom Business Center; King of Prussia,      PA  19406; 1-800-438-7246; Fax: (610) 992-6499Advanced Logical Software   Anatool   9903 Santa Monica Blvd., suite 108; Beverly Hills, CA 90212; 213-653-5786Advanced Software Automation   Hindsight (ASA20/20, SQA, TCA) (see      http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/Hindsight.html)   3130A Coronado Dr.; Santa Clara, CA 95054; Tel: 800-4-ASAINC; 800-427-2462;      Fax: 408-492-1669Advanced Software Technologies, Inc.   Graphical Designer   7800 S. Elati Street, Suite 300, Littleton, CO 80120-4456; 303-730-7981;      FAX: 303-730-7983; sales@advancedsw.comAdvanced System Technologies Inc.   QASE (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 (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 (front end)   880 First Ave.; King of Prussia, PA 19406; 215-265-1550American Management Systems, Inc.   Life Cycle Productivity System (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 (front end)   Route 206 and Orchard Rd.; CN-8; Princeton, NJ 08543Arthur Andersen & Co.   Design/1 (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 (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 (see http://www.atria.com/)   ClearCase   24 Prime Park Way, Natick, MA 01760; tel. (508)-650-5100; info@atria.comBachman Information Systems   BACHMAN Product Set, BACHMAN/Analyst (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.Berard Software Engineering   Berard Object and Class Specifier (BOCS)   902 Wind River Lane, Suite 203; Gaitherburg, Maryland 20878; 301-417-9884;      Fax: (301) 417 0021; info@bse.comBullseye Software   C-Cover (test coverage analyzer, measurement) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/ccover.html)   5129 24th Ave NE STE 9; Seattle WA 98105-3230; 800-278-4268; email      info@bullseye.comCadre Technologies, Inc (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/cadre.html)   ObjecTeam, Teamwork   222 Richmond St.; Providence, RI 02903; 401-351-5950; 401-351-CASEThe CADWARE Group, Ltd   SYLVA Series (Front end)CASE Methods Development Corp.   CASE/FRAMEWORK--METHODOLOGY, CASE/FRAMEWORK--SYNERGY (Information      Engineering Methodology)   100 N. Central Exwy.; Suite 710; Richardson, TX 75080; tel: 214-644-8173      fax: 214-644-8175CaseWare, Inc (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/caseware)   CaseWare/CM (formerly Amplify Control), CaseWare/PT   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 (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 (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CodeME s.a.r.l.   CMZ (configuration management) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/CMZ)   14 Rue de l'Eglise, F-01630 St. Genis-Pouilly, France; +33 50420914; FAX +33      50420914; codeme@cernvm.cern.chCoding Factory   CoFac (Cobol generator)   100 Netro Park South; Laurence Harbor, NJ 08878; 908-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 (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 (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, COHESIONworX, COHESION Team/SEE (PCMS)   DECdirect; Continental Blvd.; Merrimack, NH 03054; 800-344-4825Digital Insight (see http://www.csn.net:80/digins/)   Robochart (flow diagram editor) (see      http://www.csn.net/digins/prodinfo.html)   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 (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Eslog Genie logiciel   Andromede (IPSE (incl. CMS - Tools Mngt - Architecture Mngt))   4bis BuroSpace; 91571 BIEVRES Cedex; Tel: (33-1) 69-85-51-51; Fax: (33-1)      69-85-50-18; eslog@victoria.frmug.fr.net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Excel Software   MacAnalyst/MacDesigner (Analysis, Design & Reengineering) (see      http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/MacAnalyst.html)   P.O. Box 1414, Marshalltown, IA 50158  USA; ph. 515-752-5359;  fax      515-752-2435; CASETOOLS@AOL.COMForschungszentrum Informatik (FZI)   STONE   Haid-und-Neu-Str. 10-14,; D-7500 Karlsruhe, Germany; +49-721-6906-731IBM   CMVC (Configuration Management Version Control) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/cmvc)ICONIX Software Engineering Inc.   PowerTools Series (front end, back end, RE/M)   2800 Twenty Eighth St, Suite 320; Santa Clara, CA 90405; 310-458-0092; FAX      310-396-3454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 (front-end)   8th Floor, 106 Ho-Ping E. Rd.; Taipei, Taiwan, R.O.C.Institute of Applied Computer Science (IFAD)   VDM-SL Toolbox (see http://www.ifad.dk/products/toolbox.html), VDM-to-C++      Code Generator (see http://www.ifad.dk/products/codegen.html)   Forskerparken 10, DK-5230 Odense M, Denmark; Phone: +45-63157131; Fax:      +45-65-932999; Email: peter@ifad.dkIntasoft   SMS (configuration management)   153 Sweetbrier Lane; Exeter EX1 3DG; EnglandIntegrated Systems, Inc.   AutoCode, MATRIXx/Systembuild   3260 Jay Street; Santa Clara, CA  95054-3309; (408) 980-1500IntelliBase nv/sa   RIDL* (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 (front end), C Development Environment   595 Market St., 10th Floor; San Francisco, CA 94105; 415-543-0900;      sales@ide.comIntersolv (merger of Index and Sage)   Excelerator 1.84 (I-CASE (front end, back end, RE/M)), Polytron Version      Control System (PVCS), APS Development Center   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.   Application Development Workbench (ADW), RECODER, INSPECTOR   3340 Peachtree Rd.; Atlanta, GA 30026; 404-231-8575; 800-338-4130Language Technology (defunct; products acquired by KnowledgeWare)LDRA Group of Companies   LDRA Testbed (static/dynamic analysis test toolset) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/LDRA)   (ALL E-mail ijh@ldra.com)   LDRA Technology Inc.: 3000-3 Hartley Road, Jacksonville, FL 32257, USA; 904      268 3267; Fax: 904 268 0733.   Program Analysers Ltd,: 56a Northbrook Street, Newbury, Berks, RG13 1AN, UK;      0635 528828; Fax: 0635 528657.   LDRA Technologie S.A.: Off Shore Voie No1, BP17 Batiment Stratege, 31312      Labege, Cedex, France; 33 61 39 77 77; Fax: 33 61 39 23 22.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 (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 (Front end, back end)   131 Hartwell Ave; Lexington, MA 02173-3126; 617-863-5800Mathworks   MATLAB/Simulink   24 Prime Park Way; Natick, MA  01760-1520; (508) 653-1415Mark V Systems, Ltd.   ObjectMaker 2.1 (aka Adagen) (cross-lifecycle)   16400 Ventura Blvd., Suite 303; Encino, CA 91436; 818-995-7671 (voice)      818-995-4267 (fax); mo@markv.comMatterhorn, Inc.   HIBOL (back end)McCabe & Associates   ACT, BAT, DCT, CodeBreaker (Reverse Engineering/Maintenance)   5501 Twin Knolls Road, Suite 111; Columbia, Maryland 21045; 800-638-6316McDonnell Information Systems (MDIS)   ProKit*WORKBENCH, PRO-IV Workbench (windows ver of DOS ProKit) (upper CASE),      PRO-IV Application Development (lower CASE)   Mail Code 3065600, 325 McDonnell Blvd., Hazelwood, MO 63042; 1-800-225-7760;      Fax: 1-314-233-6331Mentor Graphics Corp.   Analyst/RT, Designer, Auditor (front end)   8500 Southwest Creekside Place; Beaverton, OR 97005; 503-626-7000Meridian Software Systems, Inc.   OpenSELECT CASE (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) (front end, RE/M)   315 E. Eisenhower Parkway, Suite 200; Ann Arbor, MI 48108; 313-663-6027MetaCase Consulting OY   MetaEdit (o-o upper CASE tool)   P.O. Box 449; FIN-40101 Jyvaskyla, Finland; tel. & fax. +358-41-650 400Micro Focus, Inc.   COBOL/2 Workbench   2465 East Bayshore Rd.; Palo Alto, CA 94303; 415-856-4161Mortice Kern Systems   RCS (for DOS/Windows, OS/2, NT, some UNIX and HP systems), MKS Toolkit (for      DOS, OS/2, NT)   Customer Service; Mortice Kern Systems Inc.; 185 Columbia Street West;      Waterloo, Ontario  N2L 5Z5; (519)884-2251; (519)884-8861 FAX      (800)265-2797; inquiry@mks.comNetron, Inc.   NETRON/CAP   99 St. Regis Crescent N; Downsview, Ontario; Canada M3J 1Y9; 416-636-8333Object International, Inc.   OOAtool (object-oriented analysis)   8140 N. MoPac Expwy, 4-200; Austin, TX 78759-8864 USA (512) 795-0202      (voice); (512) 795-0332 (fax)ObjecTime Ltd.   ObjecTime (real-time object-oriented) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/objectime)   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 (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 (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/parcplace)   Objectworks\C++, Objectworks\Smalltalk (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 (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QualTrak Corporation   DDTS (see http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/DDTS)   3160 De La Cruz, Suite 206, Santa Clara, California, 95054; 408-748-9500;      FAX 408-748-8468; (product information: cris@qualtrak.com)Rational (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/rational)   Rational Environment (integrated interactive software engineering      environment for Ada), Rational Rose (object-oriented analysis and design      tool)   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SACO Software and Consulting GmbH   CONQUEST CASE tools (RTM)   SACO GmbH, Auhofstr. 9, D-63741 Aschaffenburg, GERMANY; E-Mail:      psc@saco.ufra.com, FAX: ++49 6021 498747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 (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/sextant)   Sextant for C (programming environment for C)   3881 Sparrow Wood, Ann Arbor, MI 48108; 313-677-0952; info@sextant.comSix Sigma Case   Canonizer   13456 SE 27th Place; Bellevue, WA 98005; 206-643-6911Softlab, Inc.   Maestro (front end, back end, RE/M)   1000 Abernathy Road, Suite 1000, Atlanta GA 30328-5613 Tel: 404-6688-811,      Fax: 404-668-8812Softool Corporation   CCC (configuration management)   340 South Kellogg Ave., Goleta, CA 93117; 805-683-5777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 (now Template Software)Software Emancipation Technology, Inc.   ParaSET (software engineering environment) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/ParaSET)   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 (estimation, measurement, front end)   77 South Bedford St.; Burlington, MA 01803; 617-273-0140Software Research, Inc.   Software TestWorks (STW); STW/Regression (CAPBAK/X, SMARTS, EXDIFF);      STW/Coverage (TCAT, S-TCAT, TCAT-PATH, T-SCOPE); STW/Advisor (METRIC,      STATIC, TDGEN)   625 Third Street; San Francisco, CA 94107-1997 USA; (415) 957-1441;      1-800-942-SOFT; FAX: (415) 957-0730; support@soft.comSQL Software, Ltd.   Product Configuration Mangement System (PCMS)   Harlow, United Kingdom; 44-279-641-021StarSys, Inc.   MacBubbles (front end)   11113 Norlec Dr.; Silver Spring, MD 20902; 301-946-0522StructSoft, Inc.   TurboCASE 3.0 (front end (for the Mac))   5416 156th Ave. SE; Bellevue, WA 98006; tel: 206-644-9834; fax: 206-644-7714Structured Solutions   STRADIS (system development methodology)   400 Interstate North Parkway, Suite 800, Atlanta, Georgia 30339; (404)      618-7900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.  (now Virtual Software Factory Ltd.)TeamOne Systems Inc,   TeamNet (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 (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/telelogic)   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   German distributor: S&P Media; Gadderbaumerstr. 19; D-33602 Bielefeld,      Germany: Tel. +49 521 1450301, Fax: +49 521 1450350; info_sdt@comic.sp-      media.de, support_sdt@comic.sp-media.deTemplate Software, Inc.   SNAP - Strategic Networked Application Platform   13100 Worldgate Drive, Suite 340, Herndon, VA 22070-4382Texas Instruments Inc.   Information Engineering Facility (IEF) 5.3   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 Sawyer Software   Graph Layout Toolkit (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/TomSawyer)   1824B Fourth Street, Berkeley, CA 94710; 510.848.0853; fax: 510.848.0854;      info@TomSawyer.COMTom Software   Application Xcellence   127 SW 156th Street; Seattle, WA 98166; 206-246-7022Tower Concepts, Inc.   RAZOR (issue tracking, configuration management) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/RAZOR)   103 Sylvan Way; New Hartford, NY  13413; (315) 724-3540;  sales@tower.com,      razor-info@tower.com, razor-manual@tower.coUnirel   Unirel Openlook Toolkit   Centro Commerciale Osmannoro; Via Volturno, 12; 50019 Sesto Fiorentino,      Italy; +39 55 301279 (voice); +39 55 318525 (fax)Unisys Corp.   Linc Design Assistant, Linc, Mapper, DMS II   P.O. Box 500; Bluebell, PA 19424; 215-986-4011Vantive Corporation   Vantive Quality (problem-tracking) (see      http://www.qucis.queensu.ca:1999/Software-Engineering/blurb/Vantive.html)   1890 N. Shoreline Blvd., Mountain View, CA 94043; Tel. (415) 691 1500; Fax:      (415) 691 1515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Virtual Software Factory Ltd.  (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/VSF.html)   VSF (Virtual Software Factory), Recycle-SF, BIf (Business Integration      Facility), SSADM4-SF, Texel-SF   Crest House, Castleman Business Centre, Ringwood, Hants. BH24 1EU, United      Kingdom;  Tel: +44 (425) 474484; Fax: +44 (425) 474233;      sales@vsfl.demon.co.ukVisible Systems Corp.   Visible Analyst Workbench (front end)   950 Winter St.; Waltham, MA 02154; 617-969-4100Vista Technologies, Inc.  (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/vista)   PCTE Workbench, HyperWeb (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 (front end)   3945 Freedom Circle, Suite 540; Santa Clara, CA 95054; 408-988-7575Westmount Technology B.V.  (see http://www.qucis.queensu.ca:1999/Software-      Engineering/blurb/Westmount.html)   Westmount I-CASE for Yourdon, Ward/Mellor, OMT, SSADM (full life-cycle)   Westmount USA Inc.; 1555 Wilson Blvd., Suite 300; Arlington, VA 22209,      U.S.A.; 703 875 8799; FAX 703 527 5709   Olof Palmestraat 24, P.O.Box 5063, 2600 GB  DELFT, The Netherlands; Tel.      (+31) (0)15 - 141212; Fax. (+31) (0)15 - 120267; email gen@wmt.nlXA Systems Corporation   PATHVU, RETROFIT (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 (front end), CADiZ (Computer Aided Desigin      in Z), ACE (ADA Compiler Environment)   University of York; York, England YO1 5DD; tel: +44 (0)904 433741 fax: +44      (0)904 433744Yourdon, Inc.   Analyst/Designer Toolkit, Cradle (front end)   1501 Broadway; New York, NY 10036;-- 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	