Forum for Advancing Software engineering Education (FASE) Volume 12 Number 08 (Issue 151) - August 2002 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Table of Contents Letter from the New Managing Editor On to a Different FASE! Articles CCSE - SEEK Development and Review by Tom Hilburn U.S. Undergraduate Software Engineering Programs by Tom Hilburn Calls for Participation ICSE'03 Experience Reports ICSE'03 Tutorial Proposals Workshop on SWEBOK and the Software Engineering Education BOK Contact and General Information about FASE ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ By: Susan A. Mengel Letter from the New Managing Editor I am very honored and pleased that Dr. Bagert asked me to take over FASE and that my appointment was welcomed by the rest of the FASE Staff. I realize that I am following in the footsteps of a fine editor and am joining a distinguished group of software engineering professionals who subscribe to and have contributed so wonderfully to FASE. FASE has always brought timely and welcome information on software engineering. This issue is no different as the joint IEEE-CS/ACM Computing Curriculum Volume on Software Engineering (CCSE) is requesting your help in reviewing the SEEK or software engineering education knowledge. I would like to encourage you to participate in this review because this body of knowledge will only be as good as the professionals who review it and give welcome suggestions for its improvement. Please stay tuned for further developments in the CCSE effort. This issue got a late start due to my husband and I buying a "fixer-upper" house and the beginning of the new semester. Because it did not go out on the 15th, however, the CCSE effort was able to be included as well as some other entries below. I look forward to serving the software engineering education community through FASE and other venues as well as working with the rest of the FASE staff. I appreciate this opportunity very much. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ By: Don Bagert (Professional Issues Editor) On to a Different FASE! This month marks the fifth anniversary of my first issue of FASE as its Managing Editor (although the job title was different at the time). Shortly after I took the position, I decided that five years was about the right amount of time to stay in this position. So, after exactly 60 issues, as has been long planned, I have stepped down as Managing Editor. As I leave this position, I am pleased to report that the FASE staff has been able to institute a number of beneficial changes over the last five years. Among them: * The newsletter was put on a regular monthly schedule, coming out (usually) on the 15th of the month. Although that did not give FASE quite the same degree of immediacy that it had under previous editors, it did provide it a structure that raised its stature in many quarters. (Besides, I am such a procrastinator, so if there wasn't a deadline of the 15th each month, you might still be waiting for my first issue! :) * A semi-regular feature of a section dedicated to a particular focus topic was instituted. This section generally consisted by several articles, edited by a guest editor, or by one of the FASE staff. Over the past five years, about 60% of the issues have contained such a topic section. * An increase in articles, and more visibility for the authors. Starting with the March 2001 issue, the names of guest editors, topic contributors, and article authors have appeared in the Table of Contents. We are glad to given these authors some extra visibility - we just wish we'd thought of it sooner! * An increased focus in professional issues mirrored increased efforts in that area by the software engineering community at large. FASE broke the news about licensing in Texas, and was among the first to report about ACM's withdrawal from the Software Engineering Coordinating Committee (SWECC). During the last five years, there have been significant developments in licensing, certification of software professionals, the development of a code of ethics, and the accreditation of degree programs, and FASE has covered them all. The increased load led to the creation of the position of Professional Issues Editor in June 2000. It is also pleasing to note that subscriptions have risen from 605 in 1997 to 870 as of August 4, 2002. However, the thing that I feel makes FASE most special and important to the software engineering community is its ability to maintain editorial impartiality throughout its entire existence, due to its status as an independent publication. This was especially important during the ACM/IEEE-CS split concerning SWECC. There are a number of people that I need to thank. Laurie Werth is only person who has been a member of the FASE staff throughout its entire existence. Her suggestions over the years have been invaluable. Nancy Mead is the other member of the FASE staff who has been here throughout my entire tenure as Managing Editor. Nancy was always there to give the advice that I needed, and to lend a hand when I needed support. She has been a true mentor to me in my development as a professional. Thanks, Nancy! I appreciate the efforts of the Corporate/Government editors, Kathy Beckman (who predated me by two years) and (currently) David Carter for their support and for their efforts in expanding FASE to focus on more than just academic education. Tom Hilburn is a true leader in the software engineering education community, and a true friend as well. FASE has been very fortunate to have Tom serve as the Academic Editor since June 2000 (when I shifted over to the newly-created Professional Issues editor position). Thanks also to all of the guest editors we have had over the years, including (in alphabetical order) Pierre Bourque (twice), Susan Burk, Robert Dupuis (twice), Helen M. Edwards, Don Gotterbarn, Peter Henderson, Tom Hilburn (twice, before he became Academic Editor), Stan Jarzabek, Joe Kasser, Pete Knoke (twice), Susan Mengel (twice), A Rajagopal, Bruce Schafer, Ahmed Seffah, Michael Ryan, J. Barrie Thompson and anyone else that I have accidentally omitted. Finally, I would like to welcome the newest member of the FASE staff, our incoming Managing Editor, Susan Mengel. I have known Susan for many years now, and have had the privilege of working across the hall from her at Texas Tech for the last six of those. I have complete confidence that Susan will lead FASE to new heights! As for me, I will continue as Professional Issues Editor, and possibly introduce a new feature (more on that in a later issue). On a personal note, I have also changing jobs, in order to become the Director of Software Engineering and a Professor of Computer Science and Software Engineering at the Rose-Hulman Institute of Technology in Terre Haute, Indiana (about a one-hour drive west from Indianapolis), as of August 19. (Of course, my job change and the change of managing editors is entirely coincidental!) Thanks again, and I'll be talking to you again sometime soon. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Articles ###################################################################### By: Tom Hilburn (Academic Editor) CCSE - SEEK Development and Review In April 2002 we reported on the work of the joint ACM and IEEE-CS project to develop the Computing Curricula Software Engineering Volume (CCSE), as part of the original Commuting Curriculum 2001 project. (That report can be viewed at http://www.cs.ttu.edu/fase/v12n04.txt and general information about CCSE is available at http://sites.computer.org/ccse). This is an update on CCSE activities since April and a call for participation in a public review of a draft of the Software Engineering Education Knowledge (SEEK) document. Development of the CCSE Volume has been divided into two groups: an Education Knowledge Area Group and a Pedagogy Focus Group. The Education Knowledge Area Group is responsible for defining and documenting a software engineering body of knowledge appropriate for guiding the development of undergraduate software engineering curricula (the SEEK). The Pedagogy Focus Group is responsible for using the SEEK to formulate guidance for pedagogy, and course and curriculum design to support undergraduate software engineering degree programs. The following is a list of activities since our last report: * In April the Knowledge Area Groups were formed and they began work on the initial definition of the SEEK. * On May 21st the initial outline of the SEEK was reviewed at the International Summit on Software Engineering Education held at ICSE 2002 (http://www.cet.sunderland.ac.uk/ssee) The review included discussion of the knowledge areas, the core, undergraduate software engineering curricula in different countries, the review process procedure, and international curricula concerns. * On June 14-17 a workshop was held in Chicago, IL, of the steering committee members, the chairs/representatives of the SEEK area groups, and the CCSE advisory board. This workshop resulted in further refinement of the SEEK, assigning Bloom levels to topics, and constructing an initial definition of the software engineering undergraduate core. After the workshop a complete draft of the SEEK was assembled. * In July and August a comprehensive review of the SEEK draft was conducted by SEEK volunteers and a group of experts in the field. Detailed review comments were received from leading software engineering educators, practitioners, and researchers (including Barry Boehm, Kai H. Chang, Jason Jen-Yen Chen, Tony Cowling, Vladan Devedzic, Laura Dillion, Dennis J. Frailey, Peter Henderson, Watts Humphrey, Hareton Leung, Haim Kilov, Yoshihiro Matsumoto, Bertrand Meyer, Luisa Mich, James W. Moore, Hausi Muller, Peter G. Neuman, David Notkin, David Parnas, Dietmar Pfahl, Mary Shaw, Ian Sommerville, Peraphon Sophatsathit, Steve Tockey, Massood Towhidnejad, and Leonard Tripp). * On August 15-16 the Steering Committee met to discuss reviewer comments and use them to revise the SEEK draft. As one would expect, there were diverse and sometimes conflicting opinions about the content, emphasis, and style of the SEEK; and there were also many areas where there was strong agreement. We believe the resulting SEEK document (called the "First Draft") embodies the CCSE principles and will serve as an excellent foundation for developing curriculum guidance. The next step is to conduct a more widespread and public review of the SEEK. We request your help and seek your efforts in reviewing the document. YOU CAN GO TO http://sites.computer.org/ccse/ TO CONDUCT AN ONLINE REVIEW OF THE SEEK DRAFT. Reviews must be submitted by SEPTEMBER 30TH. The CCSE team looks forward to a productive year of effort to complete development of the Software Engineering Volume, which will be an important influence on improving the education of the software engineering professionals and researchers of the future. We encourage your support and participation in this effort. Note: Due to recent changes in the SEEK some of the information about the SEEK in the above described STEP workshop on software engineering knowledge may not be current. ###################################################################### By: Tom Hilburn (Academic Editor) U.S. Undergraduate Software Engineering Programs The CCSE effort, described above, will provide much needed guidance for the development of new undergraduate software engineering programs. For many years it seems that software engineering education has received much more attention in Europe and Australia than in the U.S. This is beginning to change and in recent year there have been a number of new Bachelor of Science in Software Engineering (BSSE) programs. Here is a list of the ones we are aware of: * Auburn University * California Polytechnic State University * Clarkson University * Drexel University * Embry-Riddle Aeronautical University * Florida State University * Milwaukee School of Engineering * Mississippi State University * Monmouth University * Montana Tech * Penn State at Erie * Rochester Institute of Technology * Southern Polytechnic University * University of Michigan-Dearborn * University of Texas at Arlington * University of Texas at Dallas * University of Wisconsin-Platteville Note: If you know of other programs please send email to Joe Clifton (clifton@uwplatt.edu). In recent years the EAC (Engineering Accreditation Commission) of ABET has established program criteria for accrediting BSSE programs. Here is the current criteria: 1. Curriculum The curriculum must provide both breadth and depth across the range of engineering and computer science topics implied by the title and objectives of the program. The program must demonstrate that graduates have: the ability to analyze, design, verify, validate, implement, apply, and maintain software systems; the ability to appropriately apply discrete mathematics, probability and statistics, and relevant topics in computer science and supporting disciplines to complex software systems; and the ability to work in one or more significant application domains. 2. Faculty The program shall demonstrate that those faculty teaching core software engineering material have practical software engineering experience. Go to www.abet.org for more detail. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Calls for Participation ###################################################################### From: Margaret Burnett Attention Software Engineers CALL FOR PAPERS: ICSE'03 Experience Reports at the International Conference on Software Engineering 2003 May 3-10, 2003 Portland, Oregon, USA International Conference on Software Engineering (ICSE) is the premier software engineering conference. It provides a forum for presenting and discussing the most recent advances, trends, and concerns. For the 2003 conference, the technical program will include a track on Experience Reports. Goal. This track will provide accounts of the application of software engineering techniques, tools, and processes to a specific domain or the development of a significant software system. Scope. We welcome both "classic" experience reports and case studies. Classic experience reports give an account of a significant project accompanied by a critical review of the experience and a discussion of some general lessons to be drawn from the experience. Case studies describe a product (a piece of software, a software process, a software quality management system...) and give rationale for the key decisions made during the development of the product. Experience reports should be described and organized such that they are useful for study and insight and such that the key ideas and results can be reused by practitioners. How to Submit. Submission will be electronic via a specified web site. The submission site will be available no later than August 9 (hopefully sooner) at: http://www.icse-conferences.org/2003 Important Dates Paper submission: October 4, 2002 Notification of acceptance: December 2, 2002 Camera-ready copy: TBA Review Process. The Experience Reports Committee will review each contribution and will select quality contributions that fit the quality criteria, some of which are: Write with your intended audience in mind. Your paper must contain a take-home-message for your readers; something they can learn and apply to their own work. Avoid plain "how we did it" reports. Detailed criteria and suggestions for preparing a successful submission to this track can be found at http://www.icse-conferences.org/2003/ (click on the "Experience Reports" link). ICSE'03 Experience Reports Organizing Committee Martin Glinz, Co-Chair (Universitat Zurich, Switzerland) Judith Stafford, Co-Chair (Carnegie Mellon University, USA) Sjaak Brinkkemper (Baan R&D, The Netherlands) Ivica Crnkovic (Malardalen University, Sweden) David Garlan (Carnegie Mellon University, USA) Anthony Hall (Praxis Critical Systems, UK) Richard Hall (Freie Universitat Berlin, Germany) Pankaj Jalote (Indian Institute of Technology Kanpur, India) Guenter Merbeth (Softlab, Germany) Clemens Szyperski (Microsoft Corp., USA) Heinz Zuellighoven (Univ. of Hamburg/Workplace Solutions Ltd., Germany) Albert Zundorf (Technische Universitat Braunschweig, Germany) ---------------------------------------------------------------------- The other ICSE'03 open calls to participate are: Technical Papers (due Sept. 9, 2002) Software Engineering Education & Training Papers (due Oct. 4, 2002) Experience Reports (due Oct. 4, 2002) Intl. Workshop on Program Comprehension Papers (co-located event) Intl. SPIN Workshop on Model Checking of Software Papers (co-located event) Tutorial Proposals (due Oct. 4, 2002) Workshop and Co-located Event Proposals (due Oct. 4, 2002) Panel Proposals (due Oct. 4, 2002) Doctoral Symposium Applications (due Jan. 10, 2003) Research Demonstrations and Posters (due Jan. 10, 2003) Information on all of the above can be found at: http://www.icse-conferences.org/2003/ ###################################################################### From: Margaret Burnett ICSE 2003: 25th International Conference on Software Engineering The Hilton Portland Hotel, Portland, Oregon May 3-10, 2003 http://www.icse-conferences.org/2003/ Call for Tutorial Proposals ICSE is the premier software engineering conference. It provides a forum for researchers, practitioners, and educators to present and discuss the most recent advances, trends, and concerns. The ICSE tutorial program provides conference participants with the opportunity to gain new insights, knowledge, and skills in a broad range of areas of software engineering. Participants at the tutorials include software practitioners, managers, teachers, researchers, and students seeking to gain a better understanding of software engineering. Scope We are soliciting proposals for full-day (6-hour) or half-day (3-hour) tutorials. A tutorial can cover a wide range of topics, from practical techniques, guidelines, standards, and surveys, to theoretical issues. We encourage tutorials that reflect the conference themes and provide clear utility to practitioners. The topics are not limited to past ICSE tutorial offerings. We also encourage, where justified by the complexity of the subject matter, tutorials offered in two forms: introductory, and advanced. Offerers should clearly indicate such paired submissions, and describe how the submissions are related. For example, introductory tutorials might cover the same material in a more elementary way, or might cover material that is prerequisite to the subject of the advanced tutorial. Introductory/Advanced paired tutorials should otherwise be independent of each other, however. In particular, either or both such tutorials may be accepted. Tutorials are intended to provide independent instruction on a topic of relevance to software engineers. Therefore no commercial or sales-oriented presentations will be accepted. Potential presenters should keep in mind that there may be quite a varied audience, including novice graduate students, seasoned practitioners, and specialized researchers. They should be prepared to cope with this diversity unless they make clear that the tutorial is oriented to a particular subgroup. Also bear in mind that not everyone will have English as their first language. Thus, presenters should provide comprehensive notes written in clear, standard English. Idioms, irony, slang and culture-specific references should be avoided as far as possible. Review Process The Tutorial Committee will evaluate each tutorial proposal on its anticipated benefit for prospective participants and its fit within the tutorial program as a whole. Factors to be considered also include: relevance, timeliness, importance, and audience appeal; suitability for presentation in a half- or full-day tutorial format; effectiveness of teaching methods; and past experience and qualifications of the instructors. Topics of Interest In general, topics relevant to all aspects of software engineering will be considered. In particular, the following topics may be of special interest to conference attendees: Agent-based systems/agent design and programming Agile/eXtreme Programming Aspect-orient systems/ aspect design and programming Components/patterns/frameworks Development environments (ICASE) Embedded/reactive/real-time systems Hardware/software co-design Model checking OO technology and process Product lines/product families Project management/estimation/metrics Requirements engineering Software and system security Software architecture/component technology Software process modeling/programming/implementation Software product lines Testing/verification/validation Web services/XML/etc How to Submit In brief, the tutorial proposal should include a title, proposer's contact information, tutorial aims and objectives, duration (full- or half-day), purpose and scope, and summary of material to be covered. The format of tutorial proposals (ten pages or fewer each) may be: ASCII text (plain or HTML), or Adobe Portable Document Format (see instructions for submitting PDF files). Submit proposals via e-mail to the address below. Acceptance Each accepted tutorial will have two pages for a summary in the conference proceedings. This summary must conform to the ICSE 2003 paper format and should not exceed two pages, including all text, references, appendices, and figures. The final camera-ready copy and copyright release form are due: TBA. Tutorial Reimbursement Reimbursement for half-day tutorials is $350. Full-day tutorials are reimbursed at $700. In addition, actual travel and lodging expenses are reimbursed up to $1000 per tutorial with a limit of two nights lodging. Reimbursement and travel expenses must be shared among the speakers if two or more speakers present the tutorial. Conference fees are not waived for tutorial presenters. Important Dates Proposals Due: October 4, 2002 (FIRM!) Notification of acceptance: December 2, 2002 Camera-ready copy: TBA Contact Information Dick Fairley Computer Science Department OGI School of Science and Engineering, OHSU 20000 Walker Road, NW Beaverton, OR, USA 97007 VOICE +1-503-748-1558 FAX +1-503-748-1553 e-mail: dfairley@cse.ogi.edu ---------------------------------------------------------------------- Summary of other ICSE'03 open calls to participate: Technical Papers (due Sept. 9, 2002) Software Engineering Education & Training Papers (due Oct. 4, 2002) Experience Reports (due Oct. 4, 2002) Intl. SPIN Workshop on Model Checking of Software (co-located event, papers due Dec. 6, 2002) Intl. Workshop on Program Comprehension (co-located event, papers due Dec. 20, 2002) Tutorial Proposals (due Oct. 4, 2002) Workshop and Co-located Event Proposals (due Oct. 4, 2002) Panel Proposals (due Oct. 4, 2002) Doctoral Symposium Applications (due Jan. 10, 2003) Research Demonstrations and Posters (due Jan. 10, 2003) Information on all of the above can be found at: http://www.icse-conferences.org/2003/ ###################################################################### From: Tim Lethbridge CALL FOR PARTICIPATION WORKSHOP ON GUIDE TO THE SOFTWARE ENGINEERING BODY OF KNOWLEDGE (SWEBOK) AND THE SOFTWARE ENGINEERING EDUCATION BODY OF KNOWLEDGE (SEEK) OCTOBER 6, 2002 Ecole de technologie superieure Montreal, Quebec, Canada Workshop held during the SOFTWARE TECHNOLOGY AND ENGINEERING PRACTICE (STEP) 2002 http://iwcase.org/step2002/ STEP 2002 will be held in conjunction with: IEEE International Conference on Software Maintenance, ICSM'2002 http://web.ing.unisannio.it/icsm2002/index.html Workshop Co-chairs Pierre Bourque (SWEBOK) Ecole de technologie superieure Telephone: (1) 514-396-8623 pbourque@ele.etsmtl.ca Timothy Lethbridge (CCSE) University of Ottawa Tel: (613) 562-5800 x6685 tcl@site.uottawa.ca WORKSHOP DESCRIPTION Context The purpose of this workshop is to review proposals for two related international initiatives: the Guide to the Software Engineering Body of Knowledge (SWEBOK) project (www.swebok.org) and the Software Engineering Education Body of Knowledge (SEEK) that is being produced within the context of the development of a model software engineering undergraduate curricula (http://sites.computer.org/ccse/). Though both bodies of knowledge strongly overlap, their scope, their specifications, their target audiences and their intended uses are somewhat different therefore both initiatives can learn from each other. Results of this workshop will serve as input to a second (to be confirmed) workshop on this topic at the 2003 Conference on Software Engineering Education and Training (http://www.ls.fi.upm.es/cseet03/) that will be held in March 2003 in Madrid. Guide to the Software Engineering Body of Knowledge (SWEBOK) The Guide to SWEBOK is a project of the IEEE Computer Society to characterize the discipline of software engineering and to provide a topical guide to the literature describing the generally accepted knowledge within the discipline. The Guide is intended to be useful to industry, to policy-making organizations and to academia, for instance, in developing educational curricula and university degree program accreditation criteria. The Guide describes the portion of each KA that is both generally accepted and applicable to all software systems. Research topics and specialized topics are out of scope for the current version. The Guide also recognizes a list of related disciplines that are important to software engineers but not treated in this Guide. The level of coverage and depth is appropriate for a degreed software engineer with four years of professional experience. The Guide is currently available in a Trial Use Version that can be downloaded for free from the project web site. The trial use version was developed through a managed consensus process involving 8,000 comments from close to 500 reviewers in 42 countries. During the next years, trial usage and experimentation will lead to further refinement of the document. The SWEBOK Guide has been endorsed for trial usage by the Board of Governors of the IEEE Computer Society and is undergoing its final vote by the International Organization for Standardization (ISO) for publication as a Technical Report. Software Engineering Education Body of Knowledge (SEEK) The SEEK forms part of what will be called Computing Curriculum - Software Engineering (CCSE), an ACM/IEEE Computer Society initiative to define undergraduate software engineering curriculum recommendations. CCSE complements the long standing Computing Curriculum - Computer Science, as well as similar volumes being developed for computer engineering and software engineering. CCSE has been under development since 2001. The first stage is to produce SEEK, and the second stage will be to define how the contents of SEEK can be put together to form coherent sets of courses. As of late Summer 2002, SEEK had ten knowledge areas. The contents of each knowledge area had been developed by committees of volunteers, using SWEBOK as one of their key starting points. The results were then worked on by participants at a workshop and by the CCSE steering committee. The draft document was sent for review by top experts in software engineering in July 2002. By the time of this workshop SEEK will be in an intensive public review stage. SEEK proposes core topics that every software engineering student must be taught, as well as elective topics. The core topics include not only knowledge that is clearly part of software engineering, but also knowledge from foundational areas such as mathematics, computer science, professional ethics etc. Key Input Documents: * Trial Version of the Guide to the Software Engineering Body of Knowledge (SWEBOK) - Version 1.0, May 2001 * Current draft version of Software Engineering Education Body of Knowledge(SEEK) Outcomes: * Identification of alignments and differences between both bodies of knowledge * Rationale for and reasonableness of the alignments and differences * Proposals for improvements for the next version of Guide Software Engineering Body of Knowledge (SWEBOK) * Proposals for improvements for the next draft of the Software Education Engineering Body of Knowledge (SEEK) Participant Requirements: All participants will be assigned upon registration a knowledge area of the Guide to the Software Engineering Body of Knowledge (SWEBOK). More than one participant may be assigned per knowledge area. Participants will submit, prior to the workshop, a position paper based on a supplied and easy to follow template for their assigned knowledge area. Participants will be asked to work together when preparing the position paper if more than one participant is assigned to the same knowledge area. Although participants will be assigned a specific knowledge area, they will have to take the other knowledge areas into account because issues to be considered include duplication and consistency. A written report of the workshop will be produced. It will be published on the conference web site. There will be STEP2002 proceedings published after the conference by IEEE CS Press (to be confirmed). It will include refereed research papers and workshops results (to be confirmed). The position papers will: * Identify differences and alignments between the breakdown of topics proposed by both documents; * Propose a rationale for these differences and alignments and whether or not the alignments and differences are reasonable within the context of the defined objectives and specifications of each document; * Propose improvements to either or both documents. The agenda for the workshop will be to discuss the findings of each participant Current Structure of Each Document SWEBOK Knowledge Areas Software Requirements Software Design Software Construction Software Testing Software Maintenance Software Configuration Management Software Engineering Management Software Engineering Process Software Engineering Tools and Methods Software Quality SEEK Knowledge Areas Foundations Professional Practice Software Requirements Software Design Software Construction Software Verification and Validation Software Evolution and Maintenance Software Engineering Management Software Engineering Process Software Quality For further information on this workshop, please contact Pierre Bourque at pbourque@ele.etsmtl.ca ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Contact and General Information about FASE ###################################################################### FASE is published on the 15th of each month by the FASE staff. Article and Faculty Ad Submission Guidelines Send newsletter articles to one of the editors, preferably by category: Articles pertinent to academic education to Tom Hilburn ; corporate and government training to David Carter ; professional issues, faculty ads, and all other categories, to Don Bagert . If the article is for a FASE topic where there is a guest editor, the submission should instead be to that person, according to the schedule provided. Items must be submitted by the 8th of the month in order to be considered for inclusion in that month's issue. Also, please see the submission guidelines immediately below. FASE submission format guidelines: All submissions must be in ASCII format, and contain no more than 70 characters per line (71 including trailing blanks and the new line character). This 70-character/line format must be viewable in a text editor such as Microsoft Notepad WITHOUT using a "word wrap" facility. All characters (outside of the newline) should in the ASCII code range from 32 to 126 (i.e. "printable" in DOS text mode). All articles contain the viewpoints of their respective authors, and do not necessarily reflect the opinions of the FASE staff. _____ Subscribe/Unsubscribe Information Everyone that is receiving this by email is on the FASE mailing list. If you wish to leave this list, send a message to and, in the text of your message (not the subject line), write: unsubscribe fase To rejoin (or have someone else join) the FASE mailing list, write to and, in the text of your message (not the subject line), write: subscribe fase For instance, if your name is Jane Smith, write: subscribe fase Jane Smith But what if you have something that you want to share with everyone else, before the next issue? For more real-time discussion, there is the FASE-TALK discussion list. It is our hope that it will be to FASE readers what the SIGCSE.members listserv is to that group. (For those of you that don't know, SIGCSE is the ACM Special Interest Group on Computer Science Education.) To subscribe to the FASE-TALK list, write to and, in the text of your message (not the subject line), write: subscribe fase-talk For instance, if your name is Jane Smith, write: subscribe fase-talk Jane Smith Please try to limit FASE-TALK to discussion items related to software engineering education, training and professional issues; CFPs and other such items can still be submitted to the editor for inclusion into FASE. Anyone that belongs to the FASE-TALK mailing list can post to it. As always, there is no cost for subscribing to either FASE or FASE-TALK! (Subscriptions can also be maintained through the Web via http://lyris.acs.ttu.edu. From there, click on "TTU Faculty Mailing Lists", and then either "fase" or "fase-talk", depending on which list you desire.) _____ Back issues (dating from the very first issue) can be found on the web (with each Table of Contents) at in chronological order, or in reverse order. _____ The FASE Staff: Susan A. Mengel -- Managing Editor Department of Computer Science Texas Tech University 8th and Boston Lubbock TX 79409-3104 Phone: 806-742-1189 Fax: 806-742-3519 Email: mengel@ttu.edu URL: http://www.cs.ttu.edu/people/faculty/mengel.html Tom Hilburn -- Academic Editor Embry-Riddle Aeronautical University Department of Computing and Mathematics Daytona Beach FL 32114 USA Phone: 386-226-6889 Fax: 386-226-6678 Email: hilburn@erau.edu URL: http://faculty.erau.edu/hilburn/ David Carter -- Corporate/Government Editor 807 Hwy 1204 #B-2 Pineville LA 71360 USA Phone: 318-641-0824 Email: dacarter@bayou.com Don Bagert, P.E. -- Professional Issues Editor Director of Software Engineering Professor of Computer Science and Software Engineering CM 97 Rose-Hulman Institute of Technology 5500 Wabash Avenue Terre Haute IN 47803-3999 USA Phone: 812-877-8327 Email: Don.Bagert@rose-hulman.edu Fax: 812-872-6060 URL: http://www.cs.rose-hulman.edu/people/bagert.html Laurie Werth -- Advisory Committee Taylor Hall 2.124 University of Texas at Austin Austin TX 78712 USA Phone: 512-471-9535 Fax: 512-471-8885 Email: lwerth@cs.utexas.edu Nancy Mead -- Advisory Committee Software Engineering Institute 5000 Forbes Ave. Pittsburgh, PA 15213 USA Phone: 412-268-5756 Fax: 412-268-5758 Email: nrm@sei.cmu.edu