The Guide to the Software Engineering Body of Knowledge (the SWEBOK Guide) provides generally accepted knowledge for the software engineering profession. The content of the SWEBOK Guide is derived from academic sources and the best practices of the profession. The SWEBOK Guide is a reference document for many academic and industrial curricula, certification programs, accreditation criteria, and professional licensure. This paper provides an overview of the recently published Version 3 of the SWEBOK Guide and examines the potential impact of the changes in Version 3 on software engineering education and training for the academic and industrial sectors.

This panel will discuss recent trends in graduate software engineering programs, including adoption of GSwE2009, cooperative programs between schools, increasing use of distance education formats, and specialization of programs for industry partners. Panelists will also discuss the evolving relationship of software engineering to other disciplines, such as computer science and systems engineering.

This paper describes the relationships between systems engineering and software engineering and indicates ways in which systems engineering concepts can be integrated into the SE2004 curriculum guidelines for software engineering to produce software engineers who can effectively participate in systems engineering endeavors. This paper is a companion to “Teaching Software Engineering Concepts to Systems Engineers” which appears in the proceedings of the 2011 ASEE conference.

This paper presents the evolution of the COCOMO models for software estimation from COCOMO 81 to Ada COCOMO to COCOMO II and describes the many ways in which COCOMO has influenced, and continues to influence, software engineering education and training.

No abstract available.

Article Free Access Share on Recent advances in software estimation techniques Author: Richard E. Fairley View Profile Authors Info & Claims ICSE '92: Proceedings of the 14th international conference on Software engineeringJune 1992 Pages 382–391https://doi.org/10.1145/143062.143155Online:01 June 1992Publication History 12citation2,293DownloadsMetricsTotal Citations12Total Downloads2,293Last 12 Months42Last 6 weeks19 Get Citation AlertsNew Citation Alert added!This alert has been successfully added and will be sent to:You will be notified whenever a record that you have chosen has been cited.To manage your alert preferences, click on the button below.Manage my AlertsNew Citation Alert!Please log in to your account Save to BinderSave to BinderCreate a New BinderNameCancelCreateExport CitationPublisher SiteeReaderPDF

The authors present the results of six case studies of software reuse performed in five organizations: Digital Equipment Corporation (DEC), BTG Inc., the US Army, Raytheon Company and Hartford Insurance. The authors' objectives are to (1) report on reuse efforts currently under way and (2) identify recurring factors among these efforts. Perhaps the most important observation made by the authors is that there is no right or wrong way to practice software reuse. In some organizations, a more formal approach is appropriate, while in others less formal approaches work. It seems more important to find an approach that fits the culture than to follow some textbook method. Eighteen hypotheses concerning reuse efforts are formulated on the basis of these observations.>

Software development tools include pre-imple mentation tools for automated analysis and design of software, post-implementation tools for auto mated verification and validation of software, and the familiar implementation tools such as compilers, text editors, loaders, and diagnostic packages.

ALADDIN is an interactive facility for debugging and testing of assembly language programs. ALADDIN differs from traditional debuggers by allowing the user to specify breakpoint assertions, rather than breakpoint locations. Assertions are logical relations among various components of the program state. If an assertion becomes false during execution of the object program a breakpoint is executed and control is passed to the user's terminal. ALADDIN can also be used as a testing tool to verify that asserted behavior matches actual behavior under various sets of input data and test conditions.

This paper is a progress report from the IEEE Computer Society's Subcommittee on Model Curricula in Software Engineering. Both undergraduate and graduate curricula are discussed, and the current status of the effort is summarized. Some of the problems that remain to be solved are mentioned. The paper describes work in progress and should not be considered a final document.

This paper describes an experimental program testing facility called the interactive semantic modelling system (ISMS). The ISMS is designed to allow experimentation with a wide variety of tools for collecting, analyzing, and displaying testing information. The design methodology is applicable to procedural programming languages, and Algol 60 is being used as the vehicle for elaboration of design principles and implementation techniques. This paper discusses the ISMS design, and describes the various types of analysis and display tools being developed to facilitate program testing. The ISM Preprocessor is described, an an example is presented to illustrate the data structures utilized in the ISMS.

The Department of Computer Science at the University of Colorado has recently developed a graduate curriculum in Business-Oriented Computing. The program was developed in recognition of the increasing demand for individuals who are trained in both business methodology and computer science. The 30 semester hour program is designed to produce masters level computer scientists capable of integrating the needs of the business community with the technology of computer science.