%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % Forum for Academic Software Engineering % % (The Electronic Version) % % % % Volume 2, Number 7, June 30, 1992 (FASE No. 8) % % % % _____________________________________________________________________ % % % % 1 Advance Program and Registration for 1992 Conference on Software % % Engineering Education % % % % 2 Software Engineering Reading List % % % % 3 Curriculum Development in Software Engineering and ADA - DARPA CFP % % % % 4 Computer Ethics Curriculum Kit % % % % 5 FBI raids alleged pirated software bulletin board % % % % 6 A Review and Desk Copies Information for a New Software % % Engineering Book % % % % % % 7 Petri Nets 93 - Call for Papers and Announcement % % % % _____________________________________________________________________ % % % % % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 1====================================1====================================1 From: Carol Sledge Subject: Advance Program and Registration for CSEE '92 1992 CONFERENCE ON SOFTWARE ENGINEERING EDUCATION SAN DIEGO, CALIFORNIA OCTOBER 5-7, 1992 INVITATION The Software Engineering Institute (SEI) invites educators, trainers, managers, and administrators interested in software engineering education and training to attend its sixth annual Conference on Software Engineering Education, CSEE 1992. The conference will be held in San Diego, California, at the Hyatt Islandia Hotel on October 5-7. The goal of CSEE '92 is to provide a forum for discussion of software engineering education and training among members of the academic, industry, and government communities and to promote interaction and cooperation among these communities. The program includes refereed papers from an international group of software engineering educators, along with reports from the SEI, panel discussions, and invited speakers. There will be opportunities for informal discussion, and a variety of educational materials will be on display. Proceedings will be published by Springer-Verlag and distributed to each attendee. The theme of CSEE '92 is "Putting the Engineering into Software Engineering". Two keynote speakers will set the stage for exploring the conference theme. Watts Humphrey will present "Toward a Discipline for Software Engineering." Humphrey was the first director of the SEI Process Program. In addition to designing and implementing the methodology for assessing software development processes, he has served on the Board of Examiners for the Malcolm Baldrige National Quality Award, and served on an Air Force advisory board. The second speaker, Anthony Hall will ask, "Is Software Engineering?" He will examine what it means to be an engineer, and what this implies for software engineering education. Hall is from the United Kingdom, where he is a principal consultant at Praxis Systems plc. His primary interests are the practical improvement of software development on real projects through the use of formal methods and other rigorous techniques, and understanding how to make software into a proper engineering discipline. CSEE '92 is presented in cooperation with the ACM and the IEEE Computer Society. The Software Engineering Institute (SEI) is a federally funded research and development center operated by Carnegie Mellon University under contract to the U.S. Department of Defense. The SEI's objective is to provide leadership in software engineering and in the transition of new software engineering technology into practice. KEYNOTE SPEAKERS Watts S. Humphrey Fellow, Software Engineering Institute Humphrey founded the SEI Software Process Program and is currently a research scientist on the institute staff. The Process Program provides leadership in establishing advanced software engineering processes, metrics, methods, and quality programs for the U.S.Government and its contractors. >From 1959 to 1986, Humphrey was associated with IBM Corporation. Among his assignments was the responsibility for IBM's commercial software development, including the first 19 releases of OS/360. He also managed IBM's Endicott, New York, development laboratory and was IBM director of policy development. As director of programming quality and process, Information Systems & Technology Group, he was responsible for establishing plans and implementation programs to improve the quality and productivity of IBMUs 370 programming systems development. Humphrey is the author of three books, Managing the Software Process; Managing for Innovation - Leading Technical People; and Switching Circuits with Computer Applications. He has been issued five U.S. patents. Anthony Hall Principal Consultant, Praxis Systems Hall has a first degree in Natural Sciences and a doctorate in Theoretical Chemistry. After a period of postdoctoral research, he joined the British Museum, where he established the computer section of the Research Laboratory. In 1980 he moved to Systems Programming Ltd., where he worked on compilers, databases, and software tools. He was a member of the UK Ada project, first as consultant on the Kernel APSE team and later as project manager. In 1984 he joined Systems Designers, where he was the principal consultant responsible for project support environments. During this time, Hall developed an interest in formal methods and was responsible for the formal specification of the Aspect Public Tool Interface. In 1986 Hall joined Praxis. He played a leading technical role on CASE, a project that used Z to specify a software engineering toolset for a Praxis client. Most recently, Hall has been leading the analysis and design team on CDIS, a large system development for the London Air Traffic Control Centre. This project is completely based on the use of formal methods and is probably the largest such project in existence. It is pioneering the practical application of such methods throughout the development lifecycle. PRELIMINARY CONFERENCE PROGRAM Sunday, October 4, 1992 ----------------------- 6:30 p.m. - 9:30 p.m. Registration and Reception Monday, October 5, 1992 ----------------------- 7:30 - 8:15 Continental Breakfast 8:15 - 8:30 Welcome and Introductions 8:30 - 9:30 Keynote Address: Toward a Discipline for Software Engineering Watts S. Humphrey 9:30 - 10:00 Break 10:00 - 11:30 Session 1: Papers Software Engineering Education in the 1990s--The Way Forward Douglas D. Grant, Swinburne Institute of Technology, Victoria, Australia Experience with a Course on Architectures for Software Systems David Garlan, Mary Shaw, Chris Okasaki, Curtis M. Scott, Carnegie Mellon University, Pittsburgh, Pennsylvania, and Roy F. Swonger, Digital Equipment Corporation, Nashua, NH On Teaching the Rational Design Process Terry Shepard, Royal Military College of Canada, Ontario, Canada,and Dan Hoffman, University of Victoria, British Columbia, Canada 11:30 - 1:30 Lunch 1:30 - 3:00 Session 2: Papers Teaching an Industry-Oriented Software Engineering Course Bernd Bruegge, Carnegie Mellon University, Pittsburgh, PA Integrating Research, Reuse, and Integration into Software Engineering Courses A. Jefferson Offutt and Roland H. Untch, Clemson University, Clemson, South Carolina Software Reuse in an Educational Perspective Guttorm Sindre, Even-Andre Karlsson, and Tor Staalhane, Norwegian Institute of Technology, Norway 3:00 - 3:30 Break 3:30 - 5:00 Session 3: Panel What Does Industry Want? A Panel Discussion of User Requirements for Academic and Continuing Education Program in Software Engineering Timothy J. Lulofs, Pacific Bell, San Ramon, California 5:00 End of Day I Session 7:30 - 9:00 Birds-of-a-feather Videotape viewing PRELIMINARY CONFERENCE PROGRAM Tuesday, October 6, 1992 ------------------------ 8:00 - 8:15 Continental Breakfast 8:30 - 9:30 Keynote Address: Is Software Engineering? Anthony Hall 9:30 - 10:00 Break 10:00 - 11:30 Session 4: Papers Formal Methods and the Engineering Paradigm Michael J. Lutz, Rochester Institute of Technology, Rochester, New York Formal Methods for Software Engineers: Tradeoffs in Curriculum Design David Garlan, Carnegie Mellon University, Pittsburgh, Pennsylvania Teaching Protocol Engineering in Honours Year Richard Lai, La Trobe University, Victoria, Australia 11:30 - 1:30 Lunch 1:30 - 3:00 Session 5: Panel Across the Wire: Teaching Software Engineering at a Distance Peter H. Lutz, Rochester Institute of Technology, Rochester, New York 3:00 - 3:30 Break 3:30 - 5:00 Session 6: Panel Issues in Licensing Professional Software Engineers Donald Gotterbarn, East Tennessee State University, Johnson City, Tennessee 5:00 End of Day II Session 7:30 - 9:00 Birds-of-a-feather Videotape viewing Wednesday, October 7, 1992 -------------------------- 7:30 - 8:00 Continental Breakfast 8:00 - 9:30 Track I Session 7: Papers Teaching Software Verification and Validation to Practitioners Captain David R. Luginbuhl and Captain James E. Cardow, Air Force Institute of Technology, Wright-Patterson AFB, Ohio (Continuing) Education of Software Professionals Ilkka J. Haikala, Tampere University of Technology, Tampere, Finland and Jukka Marijarvi, Nokia Telecommunications, Tampere, Finland The Software Engineering - Patent Law Interface: A Practitioner's View George M. Taulbee, Esq., Charlotte, North Carolina PRELIMINARY CONFERENCE PROGRAM Wednesday, October 7, 1992 (continued) -------------------------- 8:00 - 9:30 Track II Session 8: Papers A Joint Masters Level Software Engineering Subtrack Don Eply, The University of Iowa, Iowa City, Iowa Planning for Software Engineering Education Within a Computer Science Framework James W. Hooper, Marshall University, Huntington, West Virginia Integrating Object-Oriented Software Engineering in the Computer Science Curriculum Raj Tewari and Frank Friedman, Temple University, Philadelphia, Pennsylvania Track III Session 9: Tutorial Putting the Engineering into Software Engineering Software Architectures Engineering Project: Richard D'Ippolito, Kenneth Lee, Charles Plinta, Jeffrey Stewart, Software Engineering Institute, Pittsburgh, Pennsylvania 9:30 - 10:00 Break 10:00 - 11:30 Track I Session 10: Panel Software Process Improvement A. Winsor Brown, McDonnell Douglas Space Systems Company, Huntington Beach, California Track II Session 11: Papers Undergraduate Software Engineering Laboratory William M. Lively and Mark Lease, Texas A&M University, College Station, Texas Software Engineering Course Projects: Failures and Recommendations Manmahesh Kantipudi, Ken W. Collier, James S. Collofello, and Scott Medeiros, Arizona State University, Tempe, Arizona Use of the Individual Exchange Project Model in an Undergraduate Software Engineering Laboratory J. Kaye Grau and Norman Wilde, The University of West Florida, Pensacola, Florida Track III Session 9: Tutorial (continued) Putting the Engineering into Software Engineering Software Architectures Engineering Project: Richard D'Ippolito, Kenneth Lee, Charles Plinta, Jeffrey Stewart, Software Engineering Institute,Pittsburgh, Pennsylvania 11:30 - 1:00 Lunch PRELIMINARY CONFERENCE PROGRAM Wednesday, October 7, 1992 (continued) -------------------------- 1:00 - 3:00 Track I Session 12: Papers Creating a Software Engineering Training Program in a Level I Organization Rich Pavlik and Kathy Jacobs, Honeywell Air Transport Division, Phoenix, Arizona Corporate Software Engineering Education for Six Sigma: Course Development and Assessment of Success S. Coker, Motorola University, Schaumburg, Illinois; B. Glick, Motorola-SRD, Rolling Meadows, Illinois; L. Green, Purdue University, Hammond, Indiana; and A. vonMayrhauser, Colorado State University, Fort Collins, Colorado The IBM Cleanroom Software Engineering Technology Transfer Program Richard C. Linger and R. Alan Spangler, IBM, Gaithersburg, MD Experiences with an Interactive Video Code Inspection Laboratory Michael G. Christel, Software Engineering Institute, Pittsburgh, Pennsylvania Track II Session 13: Panel and Papers Panel: National Science Foundation Programs for Funding Curriculum, Educational Infrastructure, Faculty Development and Instrumentation Doris K. Lidtke, National Science Foundation, Washington, D.C. Paper: Some Observations Regarding Individual and Team Behavior in Software Engineering Practicums Using Different Development Paradigms William Junk and Paul Oman, University of Idaho, Moscow, Idaho Paper: Engineering Principles and Software Engineering Alfs T. Berztiss, University of Pittsburgh, Pittsburgh, PA Track III Session 9: Tutorial (continued) Putting the Engineering into Software Engineering Software Architectures Engineering Project: Richard D'Ippolito, Kenneth Lee, Charles Plinta, Jeffrey Stewart, Software Engineering Institute, Pittsburgh, Pennsylvania 3:00 - 3:15 Closing Remarks ACTIVITIES-INFORMATION Tutorial Session - Abstract --------------------------- Putting the 'Engineering' into Software Engineering The Software Architectures Engineering (SAE) Project at the Software Engineering Institute (SEI) has observed that the essential element of an engineering discipline is the use of models. Models are reusable, adaptable engineering assets that are patterns expressed in their most general, scalable form. The existence of proven models in a technology base provides economic and risk-avoidance incentives for engineers to constrain their design activities by expressing solutions in terms of existing models. This results in routine designs that are less complex, more maintainable, and more predictable in both cost and behavior. SAE classifies models as two major types: product models and practice models. The product model, when scaled, results in a component of the delivered product. Practice models guide the selection and use of product models during application development. Engineered products are composed from product models, which include domain-specific models and composition models, which capture patterns from certain disciplines. Domain-specific models capture the domain knowledge in a field of engineering expertise (e.g., control systems, signal processing). Composition models capture patterns of control and information flow particular to software. Thus, composition models specify the manner in which the domain-specific models are controlled and connected, providing a mechanism for implementing domain-specific models. In the tutorial "Putting the Engineering into Software Engineering," SAE will discuss the role of models in traditional engineering disciplines, relate that to the engineering of software, and present an example that includes the following models: * Domain-specific product models from the control systems domain. * The Object-Connection-Update (OCU) Model: - a product model providing a control and connection framework for composing applications from domain-specific models. * Model-Based Software Development (MBSD): - a practice model guiding development using product models. Finally, we will discuss our experiences transitioning the OCU model and MBSD approach to organizations and the resulting implications on software engineering education curricula. ACTIVITIES-INFORMATION Birds-of-a-feather ------------------ Monday, October 5, 1992 7:30 p.m. - 9:00 p.m. 1. SEI Continuing Education Instructor Training: A Class Reunion This session is for industry and government instructors who have received training for teaching an SEI Continuing Education course. "SEI alumni" will have the opportunity to meet old friends and to share experiences, tailoring approaches, and updates to the materials. 2. Undergraduate Software Engineering Education. This session is an open discussion of problems and issues in undergraduate software engineering education. Possible discussion topics include incorporation of software engineering topics throughout a computer science curriculum, software engineering project courses, and the potential for complete undergraduate degree programs in software engineering. Tuesday, October 6, 1992 7:30 p.m. - 9:00 p.m. "Selling Software Engineering Education to Your Organization: Creative Financing." This session will give industry and government educators the opportunity to share ideas and experiences in obtaining resources for employee education. Applicable topics include marketing, financing, headcount issues, return-on- investment arguments, and measuring educational effectiveness with respect to corporate goals. Videotapes ---------- Monday and Tuesday, October 5-6, 1992 7:30 p.m. - 9:00 p.m. SEI videotapes will be available for viewing each evening. There will be selections from the Academic Series, Continuing Education Series, and Technology Series. They include: *Executive Leadership for Software, Watts Humphrey *Software and Some Lessons From Engineering, Mary Shaw *Applying Software Engineering Skills to Writing, Linda Pesante *Software Project Management: Causal Analysis *Software Requirements Engineering: Introduction to *Software Requirements Analysis *Software Creation & Maintenance: Maintenance Tools and Environments *Software Project Management: The Nature of Software Production SEI Educational Products ------------------------ During the conference breaks and lunch hours, SEI materials will be on display. Take this opportunity to browse through curriculum modules, packages of classroom materials, and information on practitioner and executive courses. ACTIVITIES-INFORMATION Industry-University Initiative for Software Engineering Education ----------------------------------------------------------------- The program committee has established an Industry-University Initiative for Software Engineering Education as a catalyst for bringing together university educators and nearby industry and government organizations. We encourage industry to sponsor a faculty member's participation in CSEE '92, with the hope of stimulating further collaboration and interest in understanding one another's needs. We have early commitments from Bell Northern Research and Motorola of Southern Florida, and we've heard from others who have sponsorship plans under way. If you are interested in sponsoring a local professor to attend CSEE, contact Carol Sledge at the SEI, call (412) 268-7708, or send mail to cas@sei.cmu.edu. Hotel Information ----------------- A block of rooms has been reserved at the Hyatt Islandia, 1441 Quivira Road, San Diego, CA 92109-7898. The hotel will hold these rooms until September 4, 1992. Hotel arrangements should be made directly with the Hyatt Islandia at (619) 224-1234. To receive the special rate of $95 per night or the government rate of $77 per night, please mention the "Sixth SEI Conference on Software Engineering Education" when making your hotel arrangements. Again, this rate is only available until September 4, 1992. Location/Transportation Facts ----------------------------- The Hyatt Islandia is a newly renovated year-round business resort on Mission Bay, with a seascape view of the Marina, Pacific Ocean and La Jolla in the distance. It is five miles (10 minutes) from San Diego's business center; bordered on the east by West Mission Bay Drive; three-quarters of a mile from I-5; and one-half mile from I-8. The hotel is five miles (15 minutes) from San Diego International Airport: taxi $8-10, Super Shuttle $5. Two 11-passenger courtesy cars offer complimentary shuttle to the airport and Seaworld. Program Committee Members ------------------------- Maribeth B. Carpenter, Software Engineering Institute Neal Coulter, Florida Atlantic University Gary Ford, Software Engineering Institute Chris Gustafson, Lockheed Norm E. Gibbs, Software Engineering Institute Nancy R. Mead, Software Engineering Institute Keith Pierce, University of Minnesota, Duluth Carol A. Sledge, Software Engineering Institute--Conference Chair Anneliese von Mayrhauser, Colorado State University Administrative Contact ---------------------- Mary Ellen Rizzo Software Engineering Institute Telephone: 412-268-3007 Carnegie Mellon University FAX: 412-268-5758 Pittsburgh, PA 15213-3890 Internet: mer@sei.cmu.edu REGISTRATION FORM October 5-7, 1992 SAN DIEGO, CA ----------------------- Please complete this form and send to: | For Office Use Only | | Date rec'd _________| Helen E. Joyce | Date ent'd _________| Software Engineering Institute | Ck # _______________| Carnegie Mellone University | PO # _______________| Pittsburgh, PA 15213-3890 | JE# ________________| FAX (412) 268-5758 | Amt$________________| | ____________________| | PA Approval | Registration Fees (check one) ----------------------- CSEE.......$350 _____ discount*..$300 _____ _____________________ _____________________ _____________________ SEI Subscriber IEEE Membership # ACM Membership # Membership Number Registration fee includes conference materials, continental breakfast, breaks, and one reception on 10/4. Completed registration materials should be received by the SEI no later than September 4, 1992. Questions concerning registration or payment should be directed to Helen E. Joyce at (412)268-6504. Questions concerning conference materials should be directed to Mary Ellen Rizzo at (412)268-3007. Please make checks or purchase orders payable to SEI/CMU. Credit cards are not accepted. No refunds will be issued. If your organization has not made prior arrangements for reimbursements of training expenses, please provide a letter of authorization (1556) from your agency at the time of registration. Participant Information ----------------------- (please print or type information) ___ Mr. ___ Mrs. ___ Ms. Name _______________________________________________ Title ________________________________________________________________________ Company ______________________________________________________________________ Division _____________________________________________________________________ Address ______________________________________________________________________ ______________________________________________________________________ City _____________________ State __________________ Zip ____________________ Business Phone ________________________ Emergency Number ____________________ FAX Number ____________________________ E-Mail Address ______________________ Dietary/Access Requirements __________________________________________________ U.S. Citizen ___ yes ___ no If no, citizen of _____________________(country) 2====================================2====================================2 From: hossein@unocss.unomaha.edu (hossein - saiedian) Subject: Software Engineering Reading List Dear Colleagues, I found the following item in the comp.soft.eng. I thought it might of interest to you (of course if you haven't seen it before). Regards, Hossein Saiedian Internet: hossein@unocss.unomaha.edu Assit Prof. of Computer Science Bitnet : hossein@unoma1.bitnet Dept. of Computer Science Voice : (402) 554-2849 Omaha, NE 68182 Fax : (402) 554-3518 ---------------------------------------------------------------------------- This is the monthly "frequently asked questions" (FAQ) posting on reading materials for software engineers. Topics include: Textbooks Periodicals on Software Engineering Other sources of information General reading for software engineers Metrics User Interface Design Human Factors Software Testing Requirements Analysis Collaborative Requirements Analysis Training for Object-Oriented Analysis Programming Style Formal Specification Software Process Look for lines starting with "Subject:" (control-G command in rn). Be warned: the only mechanism we use to compose this list is to gather information submitted by people around the net, post it regularly, and incorporate feedback. All evaluations are the opinions of those who submitted them; your mileage may vary. Send comments to dalamb@qucis.queensu.ca (David Alex Lamb). ------------------------------------------------------------------------ Subject: Textbooks Date: 12 May 1992 Originally collected by: hsrender@happy.colorado.edu (Hal Render) Numbers 1-8 are Hal Render's original list in his rough order of preference. 1. _Software Engineering: The Production of Quality Software_ by Shari Pfleeger, 2nd Edition, Macmillan, 1991, ISBN 0-02-395115-X hsrender@happy.colorado.edu: Like #2, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). 2. _Software Engineering: A Practitioner's Approach_ by Roger Pressman, 2nd Edition, McGraw-Hill, 1987, ISBN 0-07-050783-X (3rd edition available fall 1991) hsrender@happy.colorado.edu: Like #1, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). robb@iotek.uucp (Robb Swanson): the definitive book on the subject as far as I'm concerned. johnson@aplcen.apl.jhu.edu (Michelle Johnson): a good text book as well as reference 3. _Software Systems Engineering_ by Andrew Sage and James D. Palmer hsrender@happy.colorado.edu: Like #1, had the best explanations of what I want to cover (different engineering lifecycles, methods, and tools). 4. _Fundamentals of Software Engineering_ by Ghezzi, Jayazeri and Mandrioli Prentice-Hall, 1991 hsrender@happy.colorado.edu: Like #5, good, and covered the issue of specifications and verification better, but at the expense of other aspects of the development process. I may use one of them for a graduate course in software engineering. Nancy Leveson : Better than Sommerville, although I like much of Sommerville. 5. _Software Engineering with Abstractions_ by Valdis Berzins and Luqi Addison Wesley, 1991, 624 pages. hsrender@happy.colorado.edu: Like #4, good, and covered the issue of specifications and verification better, but at the expense of other aspects of the development process. I may use one of them for a graduate course in software engineering. straub@cs.UMD.EDU (Pablo A. Straub): Both this and #9 have a good emphasis on using formal techniques (i.e., doing engineering properly), but they do not disregard informal methods; chapters are roughly organized around the traditional lifecycle. #5 is longer and can be used in a two-term sequence or for graduate students (it's possible to use it in a one-term undergrad course by covering only part of the material). One thing I like is that management and validation is given in all chapters, so that these activities are integrated into the development process. Emphasizes the use of formally specified abstractions. Uses the authors' specification language (Spec) to develop a project in Ada. 6. _Software Engineering_ by Ian Sommerville Addison-Wesley, ISBN 0-201-17568-1 hsrender@happy.colorado.edu: Our current text, and my basic problem with it is the vague way it covers many of the topics. 7. _Software Engineering with Student Project Guidance_ by Barbara Mynatt hsrender@happy.colorado.edu: Like #8, not bad, but fairly low-level and doesn't cover many tools and techniques I consider valuable. 8. _Software Engineering_ by Roger Jones hsrender@happy.colorado.edu: Like #7, not bad, but fairly low-level and doesn't cover many tools and techniques I consider valuable. 9. _Software Engineering: Planning for Change by David Alex Lamb, Prentice-Hall, 1988, 298 pages straub@cs.UMD.EDU (Pablo A. Straub): Both this and #5 have a good emphasis on using formal techniques (i.e., doing engineering properly), but they do not disregard informal methods; chapters are roughly organized around the traditional lifecycle. #9 has the advantage of being shorter, yet covering most relevant topics (lifecycle phases, formal specs, v&v, configurations, management, etc.). It is very appropriate for an undergrad course. It emphasizes that maintenance is a given and should be taken into account (hence the title). Several specification techniques are covered and used to develop a project in Pascal. 10._A Practical Handbook for Software Development_ by N.D. Birrell and M.A. Ould, Cambridge University Press, 1985/88. ISBN 0-521-34792-0 (Paper cover); ISBN 0-521-25462-0 (Hard cover) ewoods@hemel.bull.co.uk (Eoin Woods) 11._Fundamentals of Computing for Software Engineers_ by Eric S. Chan & Murat M. Tanik, Van Nostrand Reinhold kayaalp@csvax.seas.smu.edu (Mehmet M. Kayaalp MD) 12._Software Engineering_ by Stephen R. Schach, Aksen Associates (ISBN 0-256-08515-3); also Richard D. Irwin, Inc., 1990. 13._Practical Software Engineering_ by Stephen R. Schach, Aksen Associates and Richard D. Irwin Inc. (ISBN 0-256-11455-2), 1992. Advertised as sophomore through senior level, emphasizing teams, maintenance, reuse, CASE tools. ------------------------------------------------------------------------ Subject: Periodicals on Software Engineering Date: 12 May 1992 Professional Journals Meant for working professionals with technical backgrounds. IEEE Software summary: often presents recent research work, but much more readably than typical research journals. publisher: IEEE (Institute of Electrical and Electronic Engineers) subscriptions: IEEE Service Center, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331, USA Software Engineering Notes summary: unrefereed newsletter; includes digest of comp.risks publisher: ACM (Association for Computing Machinery) SIGSOFT (Special Interest Group on Software engineering), subscriptions: ACM, 11 West 42d St, New York, NY 10036, USA Software Maintenance News summary: monthly report on people and technology in maintenance; aimed at practitioners publisher: Software Maintenance News Inc, B10 Suite 237, 4546 El Camino Real, Los Altos, CA 94022, USA subscriptions: as above Software Testing, Verification and Reliability summary: aimed at practitioners; dissemination of new techniques, methodologies and standards publisher: John Wiley & Sons Ltd, Baffins Lane, Chichester, West Sussex PO19 1UD, UK The Software Practitioner (TSP) summary: started late 1990; meant for real practitioners; still finding its place publisher: Computing Trends, P.O. Box 213, State College, PA 16804, USA Mixed Research and Practice Journal of Software Maintenance: Research and Practice summary: refereed; intended for both researchers and practitioners; joint US/UK editorial board publisher: Wiley (see above) subscriptions: Journals Subscription Department, at above address Software Engineering Journal (SEJ) summary: full spectrum of articles from practical experience to long-term research publisher: IEE (Institution of Electrical Engineers) and BCS (British Computer Society); write to IEE Publication Sales, PO Box 96, Stevenage, Herts, SG1 2SD, United Kingdom. Software: Practice and Experience summary: not always software engineering; good reputation for practice publisher: Wiley (see above) The Software Quality Journal summary: academic research and industrial case studies and experience publisher: Chapman & Hall, Journals Promotion Department North America:29 West 35th Street, New York, NY 10001-2291, USA Europe: 2-6 Boundary Row, London SE1 8HN, UK Research Journals Meant for presenting recent research results. Information and Software Technology (IST) summary: broad spectrum, much software engineering, software process, but also computer science topics. publisher: Butterworth-Heineman, Linacre House, Jordan Hill, Oxford, UK Transactions on Software Engineering (TSE) summary: main software engineering research journal publisher: IEEE (see above) Transaction on Software Engineering Methodology (TOSEM) summary: first issue dated January 1992; not enough track record for an opinon yet. publisher: Association for Computing Machinery Journal of Systems and Software summary: meant to be more practitioner-oriented than other research journals publisher: Elsevier Other magazines: Software summary: "For Managers of Enterprise-Wide Software Resources" primarily aimed at Management Information Systems (MIS) world publisher: Sentry Publishing Company, Inc, 1900 West Park Drive, Westborough, MA 01581, (508) 366-2031 ------------------------------------------------------------------------ Subject: Other sources of information Date: 1 Aug 1991 Software Quality Engineering has a publication division called Single Source, Publications, Books, and Information for Software Practitioners and Managers: Software Quality Engineering -- Single Source 3000-2 Hartley Road Jacksonville, FL 32257 (904) 268-8639 FAX (904) 268-0733 TOLL FREE 1-800-423-8378 They do regular reviews of most of the literature relevant to testing, s-eng, and management. The books which are deemed useful by the reviewers are purchased for reselling. Their catalog includes most of the literature that I've come across on Software Testing. One of the items in the catalog is a publication which the company puts together itself, The Testing Tools Reference Guide, a sort of catalog of tools that have passed certain criteria, (number of unit sold, at least three verifiable references, etc.) They charge $145.00 for this guide. This includes two bi-annual updates. I've found the guide very useful in tracking down vendors which specialize in CASE and testing tools, although it seems to be heavily biased towards IBM mainframe hardware and COBOL programming (shudder!). Each text is described and summarized I'm sure SQE would be happy to send catalogs free of charge and most of the prices seem reasonable. - Glenn Stowe glenn8@odie.cs.mun.ca ------------------------------------------------------------------------ Subject: General reading for software engineers Date: 11 Oct 1991 Originally collected by: cml@cs.UMD.EDU (Christopher Lott) Summary: responses to "what should every software engineering have read?" 1. General a. Read about 100 pages of comp.risks b. Frederick P. Brooks, Jr., The Mythical Man-Month, Addison Wesley, 1978. ISBN 0-201-00650-2 c. The anecdotal books of Robert L. Glass, from Computing Trends, P.O.Box 213, State College, PA 16804, including: "Tales of Computing Folk: Hot Dogs and Mixed Nuts", "The Universal Elixir and other Computing Projects Which Failed", "The Second Coming: More Computing Projects Which Failed", "The Power of Peonage", "Computing Catastrophes", "Computing Shakeout", "Software Folklore" d. Paul W. Oman & Ted G. Lewis, Milestones in Software Evolution, IEEE Computing Society, ISBN 0-8186-9033-X. e. J.A. McDermid (editor), Software Engineer's Reference Book, Butterworth-Heinemann Ltd., 1991. ISBN No: 0 750 61040 9. Focuses on the foundations, and subject matter that is not volatile. The book is divided into three major parts: Theory and Mathematics; Methods, Techniques, and Technology; Principles of Applications. For a beginner, the first two parts are indispensible. It does not provide details of current research, but points an interested reader to the right sources. 2. Programming in the large a. Grady Booch, Software Engineering with Ada, second edition, Benjamin/Cummings, 1987 b. Bertrand Meyer, Object-Oriented Software Construction, Prentice-Hall, 1988. c. David L. Parnas, On the Criteria to be Used in Decomposing Systems into Modules, Communications of the ACM 15,2 (December 1972). 3. Programming in the small a. Jon Louis Bentley, Writing Efficient Programs, Prentice-Hall, 1982. b. Jon Bentley, Programming Pearls, Addison-Wesley, 1986. c. Jon Bentley, More Programming Pearls, Addison-Wesley, 1988. d. O.-J. Dahl, E.W. Dijkstra, C.A.R. Hoare, Structured Programming, Academic Press, 1972. e. Brian W. Kernighan, and P.J. Plauger, Software Tools, Addison-Wesley, 1976. f. Brian W. Kernighan & P.J. Plauger, The Elements of Programming Style, Second Edition, McGraw-Hill, 1978. ISBN 0-07-034207-5. 4. Mathematical Approaches a. Edsger W. Dijkstra, A Discipline of Programming, Prentice-Hall, 1976. b. E.W.Dijkstra. Selected writings on computing: a personal perspective. Springer Verlag, 1982. c. David Gries (editor), Programming methodology. A collection of articles by members of IFIP Working Group 2.3. Springer Verlag, 1978. 5. Other a. Barry W. Boehm, Software Engineering Economics, Prentice-Hall, 1981. b. Daniel P. Freedman and Gerald M. Weinberg, Handbook of Walkthoughs, Inspections and Technical Reviews, 3rd edition Dorset House Publishing, 1990, ISBN 0-932633-19-6. Originally published by Little, Brown & Company, 1982: ISBN 0-316-292826. c. Tom Gilb, Principles of Software Engineering Management, Addison-Wesley, 1988, ISBN 0-201-19246-2 d. Glenford J. Myers, The Art of Software Testing, Wiley, 1979. e. Herb Simon, The Sciences of the Artificial, Second Edition, MIT Press, 1981 f. Gerald M. Weinberg, The Psychology of Computer Programming, Van Nostrand Reinhold, 1971. ISBN 0-442-29264-3 ------------------------------------------------------------------------ Subject: Metrics Date: 9 Sep 1991 Thanks especially to Horst Zuse, who sent his extensive bibliography on metrics. a. David N. Card and Robert L. Glass. Measuring Software Design Quality Prentice Hall, Engewood Cliffs, New Jersey, 1990 b. S.D. Conte, H.E. Dunsmore, V.Y. Shen. Software Engineering Metrics and Models. Benjamin/Cummings Publishing Company, Menlo Park, 1984 ISBN: 0- 8053-2162-4 c. Tom DeMarco. Controlling Software Projects: Management, Measurement and Estimation. Englewood Cliffs, N.J.: Prentice Hall, 1982 d. Lem Ejiogu. Software Engineering with Software Metrics. QED Information Sciences, 1991 e. 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. f. Robert B. Grady and Deborah L. Caswell. Software Metrics: Establishing a Company-Wide Program, Prentice-Hall, 1987, ISBN 0-13-821844-7 g. M.H. Halstead. Elements of Software Science. New York, Elsevier North- Holland, 1977 h. S. Henry, D. Kafura, "Software Structure Metrics Based on Information Flow", IEEE Transactions on Software Engineering, Vol.SE-7, No.5, September 1981. i. 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 j. 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 k. T.J. McCabe, A Complexity Measure, IEEE Transactions on Software Engineering, VOL. SE-2, NO. 4, Dec. 1976. l. Alan Perlis, Frederick Sayward, Mary Shaw. Software Metrics: An Analysis and Evaluation. The MIT Press, 1981 m. 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. n. M. Shepperd, Software Engineering Metrics, McGraw-Hill, for publication 1991. ISBN 0-07-707410-6 (UK) McGraw-Hill Book Company (UK) Limited, Shoppenhangers Road, Maidenhead, Berkshire, SL6 2QL. Tel: +44 (0)698 23431/2 Fax: +44 (0)698 770224 o. Horst Zuse, Software Complexity: Measures and Methods, de Gruyer (200 Saw Mill River Road, Hawthorne, NY 10532 - 914/747-0110) ------------------------------------------------------------------------ Subject: User Interface Design Date: 9 Jul 1991 See also the item on Human Factors. a. John M. Carroll (editor). Interfacing Thought: Cognitive Aspects of Human-Computer Interaction, MIT press, 1987. This book has several good theoretical papers. b. Brad A. Myers, Creating User Interfaces by Demonstration London: Academic Press, 1988 c. Donald A. Norman, The Psychology of Everyday Things. Basic Books, 1988. ISBN 0-465-06709-3 (hardback). Trade paperback version is called "The Design of Everyday Things" d. Donald A. Norman & Stephen W. Draper (editors), User Centered System Design: New Perspectives on Human-Computer Interaction, Lawrence Erlbaum Associates, 1986. e. Ben Shneiderman, Designing the User Interface: Strategies for Effective Human-Computer Interaction, Addison-Wesley, 1987. Seems to be aimed at the practitioner. ------------------------------------------------------------------------ Subject: Human Factors Date: 20 Sep 1991 Originally collected by: rjc@cstr.ed.ac.uk (Richard Caley) a. Martin Helander, Handbook of Human-Computer Interaction North-Holland 1988. A huge collection of papers on various subjects; quite expensive. b. Sidney L. Smith, Jane N. Mosier. Guidelines for Designing User Interface Software Technical report ESD-TR-86-278 Electronic Systems Division The MITRE Corporation Bedford, MA 01730. A tech report rather than a book, but looks to be a good refence for issues. Also available as a hypertext. c. Paul Heckel, The Elements of Friendly Software Design: The New Edition. Sybex Inc. 1991. Original edition: Warner Books, 1984. d. Walter E. Gilmore, The User-Computer Interface in Process Control: A Human Factors Engineering Handbook. Boston:Academic Press, 1989. Is said to give references to research upon which it is based. e. Edward A. Fox (editor), Resources in Human-Computer Interaction, ACM Press, 1990. ISBN 0-89791-373-6. f. Gavriel Salvendy (editor), Handbook of Human Factors, John Wiley and Sons, 1987. ------------------------------------------------------------------------ Subject: Software Testing Date: 9 Jul 1991 The original request that prompted the posting of this information asked for recent work, not buried in a Software Engineering tome. a. Boris Beizer, Software Testing Techniques, Van Nostrand Reinhold, 1990 (2nd edition) ISBN 0-442-20672-0. 503 pages, $43. Has 37-page annotated bibliography of references. b. Cheatham and Mellinger, Testing Object Oriented Software Systems, Proceedings of the 1990 ACM SCS Conference c. William C. Hetzel, The Complete Guide to Software Testing, Second edition, QED Information Services INC, 1988. ISBN 0-89435-242-3 ------------------------------------------------------------------------ Subject: Requirements Analysis Date: 18 Sep 1991 a. Al Davis, Software Requirements: Analysis and specification. Prentice/Hall, 1990. Has some treatment of all of the popular requirements analysis and specification methods including OOA, Structured Analysis, SREM, FSM, but not the "trendy" stuff (Information Engineering, JAD). b. Donald C. Gause and Gerald M. Weinberg, Exploring Requirements: Quality before design. Dorset House Publishing, 353 West 12th Street, New York, NY 10014 ------------------------------------------------------------------------ Subject: Collaborative Requirements Analysis Date: 12 Jan 1991 Originally collected by: anton@cc.gatech.edu (Annie I. Anton) a. Palmer, J.D., Aiken, P. and Fields, N.A. "A Computer Supported Cooperative Work Environment for Requirements Engineering and Analysis", Proceedings of the Requirements Engineering and Analysis Workshop, Software Engineering Institute, March 12-14, 1991. b. Palmer, J.D. and Aiken, P.H. "Utilizing Interactive Multimedia to Support Knowledge-based Development of Software Requirements", Proceedings of the 5th Annual RADC Knowledge-Based Software Assistant Conference, Syracuse, NY, September 24-28, 1990. c. Marca, D. "Specifying Groupware Requirements From Direct Experience", Proc 6th International Workshop On Software Specification And Design, October 1991 d. Marca, D. "Augmenting SADT To Develop Computer-Supported Cooperative Work", Proceedings of the International Conference on Software Engineering; May 1991 e. Marca, D. "Experiences in Building Meeting Support Software", Proceedings of the 1st Groupware Technology Workshop; August 1989 f. Marca, D. "Specifying Coordinators: Guidelines for Groupware Developers", Proceedings of the 5th International Workshop on Software Specification and Design; May 1989 ------------------------------------------------------------------------ Subject: Training for Object-Oriented Analysis Date: 4 Feb 1992 Originally collected by: haim@taichi.uucp (24122-kilov) a. Bertrand Meyer. Object-oriented software construction. Prentice-Hall, 1988 For the somewhat advanced - perhaps, with some programming maturity. b. B. Henderson-Sellers. A book of object-oriented knowledge. Prentice-Hall, 1992. This has quite a few viewgraphs in it! c. Grady Booch. Object-oriented design with applications. Addison-Wesley, 1991. ------------------------------------------------------------------------ Subject: Programming Style Date: 19 Sep 1991 Originally collected by: oman@cs.uidaho.edu (Paul W. Oman) a. N. Anand (1988) "Clarify Function!" ACM SigPLAN Notices, 23(6), 69-79. Advocates the use of mnemonic names for entities in a system. Rules are presented for naming procedures, variable, pointers, etc. b. S. Henry (1988) "A Technique for Hiding Proprietary Details While Providing Sufficient Information for Researchers; or, do you Recognize this Well- known Algorithm?," Journal of Systems and Software, 8(1), 3-11. Suggests encryption of variable names as part of a technique for encoding algorithms, while still providing sufficient information to researchers. c. R. Brooks (1980) "Studying Programmer Behavior Experimentally: The Problems of Proper Methodology," Communications of the ACM, 23(4), 207-213. Discusses issues and tradeoffs in proper control of experiments involving computer programmers. d. E. Thomas & P. Oman "A Bibliography of Programming Style Literature," ACM SIGPLAN Notices, Vol. 25(2), Feb. 1990, pp. 7-16. ------------------------------------------------------------------------ Subject: Formal Specification Date: 3 Feb 1992 a. 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. ------------------------------------------------------------------------ Subject: Software Process Date: 5 Feb 1992 Originally collected by: cml@cs.umd.edu (Christopher Lott) a. Watts S. Humphrey. Managing the Software Process. Addison-Wesley Publishing Co., Reading, Massachusetts, 1989; Chapters 13--15, 18. b. 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. c. 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. d. 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. e. Barry W. Boehm. "A Spiral Model of Software Development and Enhancement", IEEE Computer, v.~21, n.~5, May 1988, pp.~61--72. f. 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. g. J. J. Horning and B. Randell. "Process Structuring", Computing Surveys, v.~5, n.~1, March 1973, pp.~5--30. h. 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. i. Leon Osterweil. "Software Processes are Software Too", Proceedings of the Ninth International Conference on Software Engineering, Monterey, CA, March 1987, pp.~2--13. j. 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. k. Peter H. Feiler and Watts S. Humphrey. "Software Process Development and Enactment: Concepts and Definitions", Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, 1991. l. 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. m. 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. n. 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. o. 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. p. 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. q. 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. r. 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. s. 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. 3====================================3====================================3 From: krp@SEI.CMU.EDU Subject: Curriculum Development in Software Engineering and ADA -- DARPA CFP The Defense Advanced Research Projects Agency (DARPA), in conjunction with the Ada Joint Program Office (AJPO), is soliciting proposals to support the development of undergraduate software engineering curricula and courses. Of particular interest is the development of courses and course materials that use the Ada programming language effectively in a traditional computer science curriculum. This program is intended to advance the capability of United States postsecondary educational institutions to help provide a highly qualified software engineering work force into the 21st century. Proposals will be accepted in Categories (1) and (2) as elaborated below. Category (1): Ada in Traditional Computer Science Courses: Proposals should describe research in the use of the Ada programming language in advanced undergraduate computer science courses and the development of materials useful to educators. This can include investigating the effectiveness of Ada as an implementation language in courses that traditionally use other languages, or the issues raised by the Ada language itself in areas such as compiler construction or operating systems. Results of the project should be embodied in educational materials suitable for wide dissemination and use in undergraduate computer science education. Awards in this category are expected to support one principal investigator for approximately two to three months of full-time effort, or the equivalent level of effort part-time during the academic year. Schools without an appropriate Ada implementation may also request funding for compilers and associated software tools. A school planning to introduce Ada throughout its curriculum is encouraged to submit a separate proposal for each appropriate course. Category (2): Significant New Course Sequences: Proposals submitted in this category should describe the design and implementation of significant new course sequences in an undergraduate curriculum. For example, proposals may describe the conversion of an introductory programming/data structures sequence to use the Ada language, or the development of a year-long sequence in software engineering. Results of the work should include complete packages of materials suitable for adoption by educators planning similar course sequences. Awards in this category are expected to support one principal investigator for approximately four to five months of full-time effort, or the equivalent level of effort part-time during the academic year. It is expected that the project's results in Categories (1) and (2) will be integrated into the institution's academic programs within the period of the award or in the immediately following academic term. Categories (1) and (2): Each proposal must be in a single volume and shall include the following sections A - G (inclusive) each section starting on a new page (where a `'page'' is 8-1/2 x 11 inches with type not smaller than standard 12-pitch). Non-conforming proposals may be rejected without review. A. One cover page including BAA number, proposal title, technical and administrative points of contact (including telephone numbers and electronic mail addresses, if any) followed by an official cover letter. If your institution is recognized as a Historically Black College or University (HBCU) or Minority Institution (MI), so indicate in the cover page. B. This section limited to total of five (5) pages for Category (1) proposals, and total of ten (10) pages for Category (2) proposals which pages shall include: a summary of the innovative claims for the proposed curriculum development, a clear Statement of Work (SOW) outlining the scope of the effort and citing specific tasks to be performed and time frame for performance, a technical rationale including technical arguments to substantiate innovative claims, intrinsic merit, utility/relevance and expected impact of proposed curriculum development, a technical approach description consistent with Sections C and D (see below), identification of offeror's previous accomplishments in this or related areas, full description of facilities to be used for the proposed effort, bibliography of relevant technical papers, research notes (published & unpublished) and course curriculum development which document the ideas and approach upon which the proposal is based. Note: Copies of not more than five (5) relevant papers can be included with proposal submission. C. This section limited to two (2) pages and shall include a summary of the deliverables associated with the proposal and a description of anticipated results, products, and transferable technology expected from a prospective user's point of view. D. This section limited to one (1) page and shall include a summary of schedule and milestones for proposed project and a list of key personnel along with the amount of effort to be expended by each. E. A one-page summary of any proprietary claims to results and other artifacts supporting and/or necessary for the use of the curriculum to be developed. If there are no proprietary claims, this shall be so stated. F. A one-page summary of qualifications of key personnel along with other major sources of support. This section shall include all other related pending proposals. G. A cost breakdown to the level of major tasks and equipment. Where the effort consists of multiple portions which could reasonably be partitioned for purposes of funding, these should be identified as contract options with separate cost estimates for each. Ten (10) copies of each proposal should be addressed to BAA #92-25, DARPA/SISTO, 3701 North Fairfax Drive, Arlington, VA 22203-1714. Facsimile or electronic submissions will not be accepted. Restrictive notices notwithstanding, proposals will be handled for administrative purposes by a support contractor. FFRDC employees may participate in the review process. Requests for extraordinary handling of proposals should be submitted prior to proposal submission, in writing, to Mr. Ed Brown, DARPA/SISTO, 3701 N. Fairfax Drive, Arlington, VA 22203-1714. Proposals may be reviewed and acted on as they arrive. The closing date for proposals for work to begin in the summer or fall of 1992 is 22 June 1992, 4:00 PM; for work to begin in the winter or spring and of 1993, the deadline is 1 August 1992, 4:00 PM. A follow-on BAA of this nature is anticipated for the 1993/1994 academic year. Proposals will be evaluated through a Government process involving peer or scientific review according to the following criteria listed in descending order of relative importance: (1) Capability of the investigator(s) and the adequacy of the institutional resources to carry out the proposed work, (2) Intrinsic merit of the proposed project, (3) Utility or relevance of the proposed project, (4) Expected impact of the proposed project, (5) Fund availability, cost realism and reasonableness. This notice itself constitutes the BAA as contemplated in FAR 6.102(d)(2). Except for the below white paper, no additional written information is available, nor will a formal RFP or other solicitation regarding this announcement be issued. Requests for same will be disregarded. Projected total funding available for this work is expected to be in the range of $300,000 to $800,000 for this year. The Government reserves the right to select for award all, some, or none of the proposals received. Only responsible degree-granting educational institutions capable of satisfying the Government's needs may submit a proposal which shall be considered by DARPA. A portion of this BAA shall be set aside for Minority Institutions and Historically Black Colleges and Universities participation. Individual proposal evaluations will be based on acceptability or unacceptability without regard to other proposals submitted under the announcement, however, all selected proposals may not be funded due to budgetary constraints. Proposals selected for funding may result in a contract, grant or other agreement depending upon the nature of the work proposed, the required degree of interaction between parties and other factors. Inquiries of a technical nature may be directed via electronic mail to Dr. John Kramer at kramer@stars.rosslyn.unisys.com or via telephone at (703) 243-8655. A white paper with additional information can be requested from the above individual. (0125) SPONSOR: Defense Advanced Research Projects Agency (DARPA), Contracts Management Office (CMO), 3701 North Fairfax Drive, Arlington, VA 22203-1714 SUBFILE: PSE (U.S. GOVERNMENT PROCUREMENTS, SERVICES) SECTION HEADING: A Research and Development PUBLICATION DATE: MAY 6, 1992 ISSUE: PSA-0589 ********************** ********************** Winners of Fall's DARPA Grant Program ********************** ********************** This list is the winners from BAA 91-18 that closed last fall. Dr. John Beidler Computing Sciences Depart University of Scranton Scranton, PA 18510 An Object-based Approach to CS 2/CS 3 Professor Charles B. Engle, Jr. Florida Institute of Technology 150 W. University Drive Melbourne, FL 32901 The Marriage of Ada and Joe College: The Future is Now David Garlan School of Computer Science Carnegie Mellon University Pittsburgh, PA 15213 Architectures for Software Systems Professor Samuel L. Gulden Packard Laboratory #19 Lehigh University Bethlehem, PA 18015 Development of a Compiler Design Course with Ada as the Implemenation Language Prof. Harold W. Carter, PI ECE Department, ML 30 University of Cincinnati Cincinnati, OH 45221-0300 Undergraduate Software Engineering Education Using Ada: An Integrated Approach Professor George C. Harrison Norfolk State University 2401 Corpew Avenue Norfolk, VA 23504 A Comprehensive Software Engineering Educational Experience Dr. James Hooper Marshall University 400 Hal Greer Blvd. Huntington, WV 25755 Ada-Based Software Engineering: A Two-Course Sequence Sandra H. Adams Project Director 5151 Park Avenue, Sacred Heart University Fairfield, CT 06432-1000 Ada in Introductory Computer Science Courses Hany Ammar 213 Glennlock Hall West Virginia University Morgantown, WV 26506 The Development of a Course Sequence in Real-Time Systems Design Dr. Arun Gupta Division of Computer and Applied Sciences Georgia Southwestern College Americus, GA 31709-4693 An Undergraduate Course Sequence for Software Engineering Students Dr. Warren G. Powell Department of Computer Science Moravian College Bethlehem, PA 18018 Curriculum Enhancement Using Ada Herbert L. Dershem Department of Computer Science Hope College Holland, MI 49423 Use of Ada, Laboratories, and Visualization in the Teaching of Data Structure Duane Jarc 1636 D Beekman Place, NW University of Maryland Unviersity College Washington, DC 20009 Introductory Course Sequence in Ada Janusz Zalewski Department of Computer Science Southwest Texas State University San Marcos, TX 78666-4616 Curriculum and Course Development for Real-Time Systems Edward L. Lamie 801 West Monte Vista Aven Ca. State U., Stanislaus Turlock, CA 95380 Teaching a Computer Simulation Course with Ada Don M. Coleman Howard University 2300 Sixth Street, N.W. Washington, DC 20059 Proposal to Conduct a Program in Software Engineering and Ada Undergraduate 4====================================4====================================4 From: pnlee@cs.uh.edu Subject: Computer Ethics Curriculum Kit From: Walter Maner Subject: COMPUTER ETHICS CURRICULUM KIT To: Multiple recipients of list ETHCSE-L TEACHING SOCIAL AND ETHICAL IMPLICATIONS OF COMPUTING: A "STARTER KIT" The Research Center on Computing and Society at Southern Connecticut State University and Educational Media Resources, Inc. (a not-for-profit organization specializing in educational programming) have assembled a "Starter Kit" for teachers who wish to introduce social and ethical implications of computing into their computer science or computer engineering classes. The "Kit" can also help computer science departments fulfill national accreditation requirements (CSAC/CSAB). The "Starter Kit" includes three video tapes and two monographs: VIDEO TAPES: No. 1--Teaching Computing and Human Values (45 min.) No. 2--What Is Computer Ethics (45 min.) No. 3--Examples and Cases in Computer Ethics (45 min.) MONOGRAPHS: No. 1--Teaching Computer Ethics (110 pages) No. 2--Computing and Social Responsibility: A Collection of Course Syllabi (142 pages) Further information is available from the Research Center on Computing and Society at Southern Connecticut State University: E-Mail: RCCS@SCSU.CTSTATEU.EDU Phone: (203) 397-4423 (Center and answering machine) FAX: (203) 397-4681 5====================================5==================================== From: pnlee@cs.uh.edu Subject: FBI raids alleged pirated software bulletin board From: banawan (Sayed Atef Banawan) Subject: Beware of pirated software -- FBI is taking actions Article: 1747 of clari.tw.computers Subject: FBI raids alleged pirated software bulletin board Date: Wed, 10 Jun 92 12:04:30 PDT United Press International FBI agents Wednesday raided a Boston area computer bulletin board suspected of illegally distributing copyright software to subscribers in 36 states and 11 foreign countries -- including Iraq. No arrests were made by agents in the raid on the Davy Jones Locker bulletin board in Millbury, Mass., but several computers and various telecomunications equipment were seized, along with financial and other business records. An FBI spokesman in Boston said evidence seized will be used in a continuing investigation to determine whether criminal charges will be brought against individuals involved in the bulletin board operation. The raid was conducted using a search warrant issued on the basis of evidence gathered by investigators for the Software Publishers Association, a Washbngton-based computer software industry trade group. ``We do a lot of investigation, and this one looked like it was serioous enough to be of interest to the FBI, and indeed, they thought it was,'' said Ilene Rosenthal, director of litigation for the industry group. Following the raid, the SPA filed a civil suit in federal court charging board operators with copyright infringement and seeking an unspecified amount of compensatory damages. The SPA said the Millbury bulletin board offered subscribers more than 200 pirated programs. The offerings included many high-priced and sophisticated business programs like Microsoft Word, Microsoft Excel, Lotus 1-2-3. Even AutoCAD, a sophisticated design and engineering program with a suggested retail price of $3,500, was among the pirated offerings. Rosenthal said the SPA investigation showed Davy Jones Locker even had beta copies -- pre-release versions of programs sent to colleagues, selected major customers and reviewers for evaluation and suggestions -- of a number of programs. ``What really upset (publishers) is that this board was somehow getting software prior to the time the companies went public worth the program -- allowing members to copy software that was not even on the market yet,'' she said. She said the SPA investigation was prompted by the discovery that a beta version of a program by Lotus Development was on the bulletin board before the software was on the market. Even a beta version of IBM's new OS/2 Version 2.0 operating system was available on the bulletin board before the final program was available from IBM. ``The SPA applauds the FBI's action today,'' said Rosenthal. ``This is one of the first instances that we are aware of where the FBI has shut down a pirate bulletin board for distributing copyright software. ``It clearly demonstrates a trend that the government is recognizing the seriousness of software copyright violation. It is also significant that the Senate passed ... a bill that would make illegal distribution of copyrighted software a felony,'' she said. Rosenthal said that, for a fee of $49 for three months or $99 for one year, Davy Jones Locker offered subscribers access to a special section of the bulletin board where they could download copyright software. The amount of time subscribers could spend in the special section was limited, as was the number of programs they could download. To expand the number of programs available, Rosenthal said, Dave Jones Locker gave credits -- exchangeable for extra connect time or the right to download more programs -- to subscribers who provided new copyright software for the bulletin board. The SPA estimates software pircacy, worldwide, costs the industry $10 billion to $12 billion a year. The SPA described Davy Jones Locker as an international business with paid subscribers in 36 states and 11 foreign countries, including Australia, Canada, Croatia, France, Germany, Iraq, Israel, the Netherlands, Spain, Sweden and the United Kingdom. 6====================================6====================================6 From: jalote@cs.UMD.EDU (Pankaj Jalote) Subject: A Review and Desk Copies Information for a New Software Engineering Book I have some copies of my book "AN INTEGRATED APPROACH TO SOFTWARE ENGINEERING", published by Springer Verlag, 1991. I would like to give these as "desk copies" to interested faculty members (particularly, since many persons have told me that Springer is not giving out desk copies very freely). The book is best suited as a text for a project-oriented introductory course in software engineering. It presents an integrated approach - it has a running case study for which major outputs like requirements document, management plan, design document, code, test plan, test case specification etc. are all given; and quality assurance activities and management activities are combined with the phase in which they have to be performed. A review of the book appears in June 92 issue of ACM Computing Reviews. A scan of it is appended to this note. If a faculty member is interested in considering this book as text, kindly send me your name and departmental address by e-mail, and I will send you a copy. If you have any other questions, feel free to contact me. Thanks. Pankaj Jalote (jalote@cs.umd.edu) ---------------------------------------------------------------------- From ACM Computing Reviews, June 1992. -------------------------------------- JALOTE, PANKAJ (Indian Institute of 9206-0323 Technology Kanpur, Kanpur, India) AN INTEGRATED APPROACH TO SOFTWARE ENGINEERING. Springer-Verlag New York, Inc., New York, NY, 1991, 375 pp., $49.50, ISBN 0-387-97561-6. [Springer Compass International series.] This book is for students who have not had any previous training in software engineering.... In order to limit the scope ... advanced topics ... have not been in- cluded. It was felt that in an introductory course . . . it is best to introduce the student to the discipline of soft- ware engineering and to some of the important topics, thus preparing the student for . . . advanced courses in software engineering. One of the goals of the book is to include only as much material as can be learned in a semester course, which might be the only soft- ware engineering course in a computer science student's education. -From the Preface Chapter 1, "Introduction to Software Engineering," intro- duces the major topics: the engineering approach to problem solving, the phases of software development, development process (life-cycle) models, the role of management, and metrics and measurement. The chapter is well written and lays out the topics and problems well. While the text utilizes the waterfall life-cycle model throughoutQperhaps best for a one-semester courseQadequate attention is paid to other models in this chapter. Chapter 2, "Software Requirements Specification," dis- cusses the need to specify requirements in detail; methods of analyzing problems and describing solutions; the charac- teristics, components, and structure of an SRD and require- ments specification languages, such as PSL/PSA; validation of requirements including the SRS (and SRD); and metrics that can be applied to an SRS. While not attempting to teach a complete course in systems analysis, the author leaves out nothing of importance. Techniques, tools, and standards are covered and examples are given. The chapter concludes with the problem analysis and the resulting SRS document (SRD) in augmented IEEE/ANSI standard format for the case study used throughout the remainder of the book. Chapter 3, "Planning a Project," covers cost estimation, project scheduling, staffing and personnel planning, team structure, software configuration management, quality assur- ance plans, project monitoring plans, and risk management planning. The chapter ends with a project plan for the case study. Once again, the necessities are covered well while the more advanced and esoteric topics are avoided. Costing is done using the COCOMO model, and the Gantt chart is used for time-related planning. Jalote mentions PERT and implies that it is the same as CPM. A PERT analysis of the case study would benefit students who, if they do not take a systems analysis course, will come across PERT and CPM at work, but know little more than what the acronyms stand for. Having taught the basics of PERT and CPM to second year students in a one-quarter systems analysis course, I do not believe that covering them would add that much time to this course. Chapter 4, "System Design," covers the objectives of de- sign, modularization techniques (such as modules, interfaces, hiding, and bottom-up versus top-down), object-oriented de- sign, handling anomalies, and verification and design met- rics. The chapter ends with the case study's system design. This chapter is excellent. Topics such as cohesion and cou- pling are covered, but Jalote does not beat the student to death with 20 kinds of each in excruciating detail. Design methodologies are presented, concentrating on structured de- sign (SDM) and object-oriented approaches (including the use of Ada). Both are well done and in enough detail that the students can utilize either in their own work. The author covers the outputs of the system design process, methods of design verification, and appropriate metrics. Chapter 5, "Detailed Design," covers module specifica- tion; detailed design and the use of design languages; veri- fication; metrics; and monitoring and control. The detailed design document for the case study concludes the chapter. One of the things I like best about this chapter is the way it brings together topics covered in abstract form in computa- tion and language theory courses, such as pre- and postconditions, axiomatic specification, and symbolic execution, with real-world activities. Since "PDL" is a commercial product, and PDL (not pdl) is treated in the text as a real, existing program design language, references should be included as they are for requirements specifications languages and tools. Chapter 6, "Coding," is about writing software. The major subheadings are programming practices, verification, metrics, and monitoring and control. As Jalote states, "the goal during this phase is not to simplify the job of the programmer. Rather, the goal should be to simplify the job of the tester and the maintainer" (p. 234). Can it be said any better? If students have not learned the programming practices discussed in this chapter by the third year of study, they should never write a program to be used or maintained by someone other than its author. The section on verification is good. Under "Code Reading," desk checking or review is discussed but reading by an independent third party is not. Proofreaders and editors can serve well in the code review process, as well as at other steps of the life cycle. Chapter 7, "Testing," looks at testing fundamentals (what, why, where, and when), functional and structural testing, the testing process, a comparison of verification and validation techniques, testing phase metrics, and test monitoring and control. The chapter concludes with a test plan for, and the results of testing, the case study. This chapter is concerned with finding those errors that were not detected and corrected earlier in the life cycle. After giving the IEEE definitions of terms (error, failure, fault, reliability, and static and dynamic testing) and a discussion of how they relate to each other and to the problems of verification and validation, the text gets on to the more practical problems of testing. Once again, the text is more than adequate in providing tools, techniques, and evaluation along with discussion geared to its audience. The earnest student will learn how to test software and be reasonably well assured as to the quality of the testing, although the student will not be versed in all possible metrics, controls, and so forth. The remainder of the book consists of Pascal code for the case study, references, and an adequate index with no major items missing. The text is clearly written, the typeface is acceptable, and I found no significant errors. The end-of-chapter exercises are sufficient. No answers or hints are provided, however. The references are sufficient, covering both historical and recent (1988-1990) material. In theory-intense courses, lab portions often lead while the lecture lags behind. Therefore, I like two-semester sequences with a lab course following the theory course. This book will work well, however, in environments where this luxury does not exist, such as in most technical schools and applied programs like MIS and CIS. I can recommend this book for classroom adoption or individual study and would be willing to use it in my classes. If an instructor's manual exists and is as well thought out as the book, it should prove useful as well. - C. A. Wolfe, Sylmar, CA 7====================================7====================================7 From: Tadao Murata Subject: Petri Nets 93 - Call for Papers and Announcement Call for Papers and Announcement 14th INTERNATIONAL CONFERENCE ON APPLICATION AND THEORY OF PETRI NETS Bismarck Hotel, Chicago, USA, June 21-25, 1993 Important Dates: Paper Submission Due: November 16, 1992 Notification Sent: February 22, 1993 Final Version Due: April 1, 1993 Tutorials: June 21-22, 1993 Conference: June 23-25, 1993 The 14th Annual International Petri Net Conference and Tutorial will be held in the Bismarck Hotel, Chicago on June 21-25, 1993. The conference will be organized by the Dept. of Electrical Engineering and Computer Science, University of Illinois at Chicago (UIC), with the assistance of Meta Software Corporation, Cambridge, USA. Papers presenting original contributions in any area of application and theory of Petri nets are sought. The language of the conference is English. Topics include but are not limited to: System design and verification using nets Causality/partial order theory of concurrency Analysis and synthesis, structure and behavior of nets Net-based semantical, logical and algebraic calculi Higher-level net models Timed and stochastic nets Relationships between net theory and other approaches Symbolic net representation (graphical, textual, ....) Computer tools for nets Experience with using nets, case studies Educational issues related to nets Applications of nets to: office automation flexible manufacturing programming languages protocols and interfaces hardware structures real-time systems performance evaluation operations research embedded systems The conference takes place in cooperation with the IEEE Computer Society, as well as AFCET SIG "Systemes Paralleles et Distribues" and CNRS-C3, AICA, BCS SIG "Formal Aspects of Computing Science", EATCS and GI SIG "Petri Nets and Related system Models". PAPER SUBMISSIONS Authors are invited to submit papers for the conference. Each paper must be no more than 20 pages, and should be in such a form that it can be immediately included in the proceedings without major revisions. The title page must contain a short abstract and a classification of the topics covered, preferably using the list of topics above. The paper must clearly state the problem being addressed, the goal of the work, the results achieved and the relation to other work. Submissions for papers (8 copies) must be received by the Program Committee Chair, Prof. Ajmone-Marsan (address shown below), no later than November 16, 1992. Use of express or courier mail is recommended. Submissions received too late and submissions sent by e-mail or fax will not be accepted. Authors will be notified of acceptance/rejection by February 22, 1993. The proceedings will be published by Springer-Verlag. The final version of accepted papers must be received by the Program Committee Chair no later than April 1, 1993. Each final paper must be no more than 20 pages and be in a form that can be included in the proceedings without any changes. Detailed instructions about formatting will be sent to the authors of accepted papers. Program Committee Chair: Prof. Marco Ajmone-Marsan Dipartimento di Elettronica Politecnico di Torino Corso Duca degli Abruzzi 24 I-10129 Torino, ITALY Phone: +39 11 5644032 Fax: +39 11 5644099 E-mail: ajmone@itopoli.bitnet Organizing Committee Co-Chair Profs. T. Murata and S. M. Shatz EECS Dept. (m/c 154) University of Illinois at Chicago (UIC) Chicago, IL 60680-4348 USA Phone: +1 312 996 5488 Fax: +1 312 413 0024 E-mail: pn93@bert.eecs.uic.edu TUTORIALS Dr. Carl Adam Petri plans to give tutorial lectures. In addition, two types of tutorials are planned: introductory and advanced. The introductory tutorial will be offered to participants who have little or no prior experience with Petri nets; it will help them understand the basic ideas in many of the conference contributions. The advanced tutorial will be offered to those who have some knowledge of Petri nets, and will be divided into two groups of talks. One will be directed towards the practical use of Petri nets, while the other will be more theoretical. A detailed description of the tutorials will be included in the final program. Tools, Meetings and Courses There will be an exhibition of computer tools for Petri nets.Tuesday will be the main day of the tool exhibition, and each tool will have its own scheduled time for a coherent presentation for a large audience. Moreover, periods will be set aside during the conference in which tools can be demonstrated for small groups. It will be possible to arrange meetings for different groups, e.g., participants in international Petri net projects. It will also be possible to arrange small educational courses, e.g., with respect to some of the demonstrated Petri net tools. Monday and Tuesday will be the days for these activities. They are free of charge for the participants. Submissions for tools and submissions for meetings and courses should contain a 2-5 page description. They must be received by the Program Committee Chair before January 1, 1993. Program Committee M. Ajmone Marsan, Italy, Chair E. Best, Germany J. Billington, Australia M. Diaz, France S. Donatelli, Italy C. Girault, France K. Jensen, Denmark H. C. M. Kleijn, The Netherlands B. Krogh, USA A. Mazurkiewicz, Poland J. F. Meyer, USA M. Molloy, USA T. Murata, USA G. Nutt, USA K. Onaga, Japan L. Pomello, Italy W. Reisig, Germany M. Silva, Spain P. S. Thiagarajan, India W. M. Zuberek, Canada Steering Committee M. Ajmone Marsan, Italy J. Billington, Australia H. J. Genrich, Germany C. Girault, France K. Jensen, Denmark G. De Michelis, Italy T. Murata, USA C. A. Petri, Germany (honorary member) W. Reisig, Germany G. Roucairol, France G. Rozenberg, The Netherlands, Chair M. Silva, Spain --------------------------------------------------------------------- Other major activities of the Petri net community: The Petri Net Newsletter The newsletter is published three times a year by the Special Interest Group on Petri Nets and Related System Models of the Gesellschaft fr Informatik. The newsletter contains short research articles, announcements of meetings, abstracts of recent publications, etc. The newsletter is edited by O. Herzog, W. Reisig and R. Valk and can be ordered from the following address: Prof. W. Reisig Institut fur Informatik, TU Munchen Postfach 202420 D-8000 Munchen 2 Germany Phone: +49 89 2105 2405 Fax: +49 89 2105 8207 E-mail: reisig@lan.informatik.tumuenchen.dbp.de Advances in Petri Nets This series is published by Springer-Verlag (within the Lecture Notes in Computer Science series). The volumes are edited by G. Rozenberg. The intention of this series is to present the most significant recent results in the application and theory of Petri Nets to the broad computer science community. Research papers and survey articles for the Advances can be submitted directly to: Prof. G. Rozenberg Dept. of Math & Computer Science University of Leiden, Niels Bohr Weg 1 P.O. Box 9512, NL-2300 CA Leiden The Netherlands Phone: +31 71 27 70 55 Fax: +31 71 27 58 19 E-mail: rozenber@rulcri.LeidenUniv.nl Advanced Courses on Petri Nets These courses are organized periodically in order to present the progress in Petri nets in a systematic way. There have been two such previous courses: Hamburg 1979 and Bad Honnef 1986. The material from these courses has also been published by Springer-Verlag (as Lecture Notes in Computer Science series). Petri Net Mailing Group The Petri net mailing group is used to disseminate conference calls, technical questions, and all other kinds of Petri net related information. It works in a similar way to a news group. The mailing group is maintained by the Computer Science Department at Aarhus University, Denmark. More information about the mailing group can be obtained by sending an email to: PetriNets-request@daimi.aau.dk History of the Conference The conference was formerly called the European Workshop on Applications and Theory of Petri Nets. Listed below are the conference sites from 1980 (1st) to 1993 (14th): 1.1980 Strasbourg, France 2.1981 Bad Honnef, Germany 3.1982 Varenna, Italy 4.1983 Toulouse, France 5.1984 Aarhus, Denmark 6.1985 Espoo, Finland 7.1986 Oxford, UK 8.1987 Zaragoza, Spain 9.1988 Venice, Italy 10.1989 Bonn, Germany 11.1990 Paris, France 12.1991 Aarhus, Denmark 13.1992 Sheffield, UK 14.1993 Chicago, USA The aim of the conference is to create a forum for discussing progress in application and theory of Petri nets. Typically, the conferences have 150-200 participants - one third of these coming from industry, the rest from universities and research institutions. The conference takes place in the last week of June. End=================================End=================================End %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% % % % Managing Editor: Pen-Nan Lee % % fase@cs.uh.edu % % % % % % % % % % % % % % Organizing Committee % % % % Keith Pierce % % University of Minnesota, Duluth % % Currently on leave at the Software Engineering Institute % % Carnegie Mellon University % % Pittsburgh, PA 15213-3890 % % Telephone: (412)268-8145 % % Fax: (412)268-5758 % % Email: krp@sei.cmu.edu % % % % % % Laurie Werth % % Dept. of Computer Science % % Taylor Hall 2.124 % % University of Texas at Austin % % Austin, Texas 78712 % % Telephone: (512) 471-9535 % % Fax: (512)471-8885 % % Email: lwerth@cs.utexas.edu % % % % % % Pen-Nan Lee % % Dept. of Computer Science % % University of Houston % % Houston, TX 77204-3475 % % Telephone: (713)743-3342, 743-3350 % % Fax: (713)743-3335 % % Email: pnlee@cs.uh.edu % % Email: fase@cs.uh.edu % % % % % %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%