IEEE P1003.0 Draft 14 - November 1991 Copyright (c) 1991 by the Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street New York, NY 10017, USA All rights reserved as an unpublished work. This is an unapproved and unpublished IEEE Standards Draft, subject to change. The publication, distribution, or copying of this draft, as well as all derivative works based on this draft, is expressly prohibited except as set forth below. Permission is hereby granted for IEEE Standards Committee participants to reproduce this document for purposes of IEEE standardization activities only, and subject to the restrictions contained herein. Permission is hereby also granted for member bodies and technical committees of ISO and IEC to reproduce this document for purposes of developing a national position, subject to the restrictions contained herein. Permission is hereby also granted to the preceding entities to make limited copies of this document in an electronic form only for the stated activities. The following restrictions apply to reproducing or transmitting the document in any form: 1) all copies or portions thereof must identify the document's IEEE project number and draft number, and must be accompanied by this entire notice in a prominent location; 2) no portion of this document may be redistributed in any modified or abridged form without the prior approval of the IEEE Standards Department. Other entities seeking permission to reproduce this document, or any portion thereof, for standardization or other activities, must contact the IEEE Standards Department for the appropriate license. Use of information contained in this unapproved draft is at your own risk. IEEE Standards Department Copyright and Permissions 445 Hoes Lane, P.O. Box 1331 Piscataway, NJ 08855-1331, USA +1 (908) 562-3800 +1 (908) 562-1571 [FAX] P1003.0/D14 Annex D (informative) Electronic-Mail _R_e_s_p_o_n_s_i_b_i_l_i_t_y: _K_e_v_i_n _L_e_w_i_s The following table lists currently-known e-mail addresses for active working group members. To correct your entry, send e-mail directly to Hal Jespersen, listed below. Michelle Aden Sun Microsystems aden@ebay.sun.com Carolyn Baker MITRE cgb@d74sun.mitre.org Timothy Baker Ford Aerospace Ralph Barker UniForum ralph@techcomm.uniforum.org e Rich Bergman NOSC rich@tecr.nosc.mil Andy Bihain GTE Telops arb1@bunny.gte.com e Jacques Cazier Mitre cazier@mitre.org e Bud Conrad Tandem conrad_bud@tandem.com e Joseph Cote Treasury Board tbsitm@nrcvm01 e of Canada Bernard Cox NASA JSC Francis Deckelman US Navy deckelman@a.151.edo e Matt Einseln Datafocus e Don Folland CCTA def@cctal.co.uk David Folsom CDC dbf@udlv.cdc.com e Thomas Ford USAF tford@xpt.ssc.af.mil Bob Gambrel Unisys rjg@rsvl.unisys.com Al Hankinson NIST/NCSL alhank@swe.ncsl.nist.gov E. Lee Hutchins USAF thutch@ssmct62.ssc.af.mil e Jim Isaak DEC isaak@decvax.dec.com Petr Janecek X/Open p.janecek@xopen.co.uk Astrid Jeffries Unisys astridj@convergent.com e Hal Jespersen POSIX Software Group hlj@posix.com Lorraine Kevra AT&T L.Kevra@att.com Ruth Klein AT&T ruthlk@attunix.att.com Doris Lebovits AT&T lebovits@attunix.att.com Kevin Leininger Fermilab kevin@fnalf.fnal.gov e Kevin Lewis DEC klewis@gucci.dec.com Heinz Lycklama Interactive Systems heinz@ism.isc.com Copyright (c) 1991 IEEE. All rights reserved. This is an unapproved IEEE Standards Draft, subject to change. Annex D Electronic-Mail 295 P1003.0/D14 GUIDE TO THE POSIX OPEN SYSTEMS Randolph Lynwood NASA Doug MacDonald General Electric Roger Martin NIST rmartin@swe.ncsl.nist.gov Dick McNaney SAIC saic-02@huachuca-emh2.army.mil Pete Meier IBM ...uunet!aixsm!meier Howard Michel USAF michelhe@hqafsc-vax.af.mil e Gary Miller IBM ...uunet!aixsm!miller e Kevin Murphy BT murphy_k_v@bt-web.bt.co.uk e Mary Lynne Nielsen IEEE m.nielsen@ieee.org Patricia Oberndorf NADC tricia@nadc.navy.mil Jim Oblinger NUSC oblinger@ada.nusc.navy.mil e Pat Patterson NASA patterso@gmuvax2.gmu.edu David Pruett NASA JSC dpruett@nasamail.nasa.gov Wendy Rauch Emerging Technologies ...uunet!etg!wrauch Group Lynwood Randolph NASA HQ randolph@nasamail.nasa.gov e Brad Reed EDS reed@eds.com Gregory Sawyer Space & Naval Warfare e Systems Command e Carl Schmiedekamp NADC schmiede@nadc.navy.mil Fritz Schulz OSF fschulz@osf.org Richard Scott Chemical Abstracts uunet!osu-cis!chemabs!rls27 Service Glen Seeds Systemhouse Charles Severance Mich. State Univ. crs@convex.cl.msu.edu Lewis Shannon NCR lew.shannon@dayton.ncr.com Peter Smith DEC psmith@decvax.dec.com Keith Stobie Tandem stobie_keith@tandem.com e Sandra Swearingen USAF tic-tisc@afcc-oal.af.mil Jong Sung Sunwoo NCA e Marti Szczur NASA/GSFC msxcxur@postman.gsfc.nasa.gov Ravi Tavakley CDC ravi@kiran.under.cdc.com e Martial Van Neste CGI Group vanneste@bond.crim.ca Robert Voigt Space & Naval Warfare voigt@nusc.ada.arpa Systems Command Gentry Watson UNIX Int'l glw@ui.org Alan Weaver IBM ...uunet!aixsm!weaver John Wilbur e John Williams GM-CPC Hdqts. jwill08@c4.eds.com e Arnold Winkler Unisys winkler@pre.unisys.com e George Zerdian Hughes george@eos.wel.scg.hac.com Copyright (c) 1991 IEEE. All rights reserved. This is an unapproved IEEE Standards Draft, subject to change. 296 D Electronic-Mail P1003.0/D14 Annex E (informative) Additional Material E.1 Software Development Environments _R_e_s_p_o_n_s_i_b_i_l_i_t_y: _D_o_n _F_o_l_l_a_n_d E.1.1 Overview and Rationale Software Development Environments are dealt with as a particular application area needing special attention for the following reasons: - The domain of Software Development Environments is one of prime importance. Software development is a major area of expenditure for government and large commercial organizations. - The need for standardization is being driven not only by the SDE vendors and users, but also by the Independent tool developers who want to get their tool products on as many vendor platforms as possible. - The SDE domain calls not only for portability, but also for particular integration and interoperability requirements. - The domain is primarily of interest to that user community that has large complex software development requirements, but it is also of interest to all application areas as software development is an enabling technology for all applications. Software engineers seek more powerful assistance to improve productivity and quality in the software development process. Considered opinion currently favors Project Support Environments (PSE) underpinned in such a way that the facilities are capable of being implemented on different machines. A PSE needs a base holding information such as specifications, designs, code, schedules, configuration plans, tests, etc., to support the developers. The interface between the base and the tools must ensure portability of the tools. Again, these tools will be supported by relevant language standards. Copyright (c) 1991 IEEE. All rights reserved. This is an unapproved IEEE Standards Draft, subject to change. E.1 Software Development Environments 297