The IEEE Transactions on Software Engineering is an archival journal published monthly. We are interested in well-defined theoretical results and empirical studies that have potential impact on the construction, analysis, or management of software. The scope of this Transactions ranges from the mechanisms through the development of principles to the application of those principles to specific environments. Since the journal is archival, it is assumed that the ideas presented are important, have been well analyzed, and/or empirically validated and are of value to the software engineering research or practitioner community. Specific topic areas include: a) development and maintenance methods and models, e.g., techniques and principles for the specification, design, and implementation of software systems, including notations and process models; b) assessment methods, e.g., software tests and validation, reliability models, test and diagnosis procedures, software redundancy and design for error control, and the measurements and evaluation of various aspects of the process and product; c) software project management, e.g., productivity factors, cost models, schedule and organizational issues, standards; d) tools and environments, e.g., specific tools, integrated tool environments including the associated architectures, databases, and parallel and distributed processing issues; e) system issues, e.g., hardware-software trade-off; and f) state-of-the-art surveys that provide a synthesis and comprehensive review of the historical development of one particular area of interest.
The CSDP program is the sole brand name professional credential in software development.
Code of Ethics
Code of Ethics
You do not have the roles required to access this portlet.
Download the latest Version (Feb. 16, 2005)
The software engineering body of knowledge is an all-inclusive term that describes the sum of knowledge within the profession of software engineering. Since it is usually not possible to put the full body of knowledge of even an emerging discipline, such as software engineering, into a single document, there is a need for a Guide to the Software Engineering Body of Knowledge. This Guide will seek to identify and describe that subset of the body of knowledge that is generally accepted, even though software engineers must be knowledgeable not only in software engineering, but also, of course, in other related disciplines.
"Generally accepted" means that the knowledge and practices described are applicable to most projects most of the time, and that there is widespread consensus about their value and usefulness. "Generally accepted" does not mean that the knowledge and practices described are or should be applied uniformly on all projects; the project management team is always responsible for determining what is appropriate for any given project.
Software engineers must not only be knowledgeable in what is specific to their discipline, but they also, of course, have to know a lot more. The goal of this initiative is not, however, to inventory everything that software engineers should know, but to identify what forms the core of software engineering. It is the responsibility of other organizations and initiatives involved in the licensing and certification of professionals and the development of accreditation criteria and curricula to define what a software engineer must know outside software engineering. We believe that a very clear distinction must be made between the software engineering body of knowledge and the contents of software engineering curricula. (www.swebok.org)
Software Engineering Technical Council
The Software Engineering Technical Council encourages the application of engineering methods and principles to the development of computer software, and works to increase professional knowledge of techniques, tools, and empirical data to improve software quality. The TC cosponsors conferences, including the International Conference on Software Engineering, and several informal workshops every year. A TC subcommittee develops proposals for IEEE software engineering standards. A quarterly newsletter, Software Engineering, informs members of current events and technical results.
Software & Systems Engineering Standards Committee
The IEEE Computer Society is the largest association for computer professionals in the world. Founded more than 50 years ago, it is now the largest of the technical societies of the IEEE. Any IEEE Computer Society standards project is assigned to one of a dozen or so "sponsors." For software engineering standards, and systems engineering standards for systems containing software, the sponsor is the Software and Systems Engineering Standards Committee (S2ESC).
In addition to the development of standards and supporting knowledge products, the S2ESC sponsors or cooperates in annual U.S. or international conferences and workshops in its subject area. The S2ESC also participates in international standards-making as a member of the U.S. Technical Advisory Group (TAG) to ISO/IEC JTC1/SC7 and as a direct liaison to SC7 itself.
IEEE Software's mission is to build the community of leading and future software practitioners. The magazine delivers reliable, useful, leading-edge software development information to keep engineers and managers abreast of rapid technology change. The authority on translating software theory into practice, the magazine positions itself between pure research and pure practice, transferring ideas, methods, and experiences among researchers and engineers. Peer-reviewed articles, topical interviews, and columns by seasoned practitioners illuminate all aspects of the industry, including process improvement, project management, development tools, software maintenance, Web applications and opportunities, testing, usability, and much more.
Guide to the Software Engineering Body of Knowledge
The software engineering body of knowledge is an all-inclusive term that describes the sum of knowledge within the profession of software engineering. Construx
Software Development Best Practices : Resources & Tools Software Engineering Radio
Podcasts for Professional Software Developers Dr. Dobb's Portal
The World of Software Development Real World Software Development
Articles, forums and blogs Software Engineering Institute
The SEI is a federally funded research and development center conducting software engineering research in acquisition, architecture and product lines, process improvement and performance measurement, security, and system interoperability and dependability. Software Engineering Institute : CMMI
Capability Maturity Model Integration (CMMI) is a process improvement approach that provides organizations with the essential elements of effective processes. It can be used to guide process improvement across a project, a division, or an entire organization. R.S. Pressman & Associates
R.S. Pressman & Associates, Inc. has assembled over 1000 software engineering resources to help you gather information on a variety of software engineering topics. Project Management Institute
Software Engineering Project Management. AKAAS.NET
Includes information and FAQs for several software development tools.
Software Engineering Category of IEEE ReadyNotes
- Designing and Implementing Softcoded Values - Michael Blaha
- Designing Databases with Object-Oriented Methods - Robert J. Muller
- Digital Avionics: A Computing Perspective - Elisabeth A. Strunk and John C. Knight
- Evaluating the Performance of Software Engineering Professionals - Lawrence Peters
- Global Software Engineering - Christof Ebert
- IEEE Software Engineering Standards Support for ISO 9001: Getting Your Organization Started - Susan K. Land and John W. Walz
- IEEE Software Engineering Standards Support for the CMMI Project Planning Process Area - Susan K. Land
- Introduction to Python for Artificial Intelligence - Steven L. Tanimoto
- The Poor Person's Guide to Estimating Software Development Costs - Donald J. Reifer
SE Online's mission is to be the most trusted, non commercial, and objective source of software engineering knowledge on the web.
By providing trusted, objective software engineering knowledge developers, teachers, and students can solve problems, locate educational resources, develop contacts, understand trends, and advance their careers. The support and drive is the community members who have expertise to share, want feedback on projects and papers, need to complete certification requirements, and want to serve the profession and advance their careers.
If any of these items sound like something you would be interested in, you may express your interest in joining us by contacting the moderator of the site.
Software Engineering Standards: A User's Road Map
- James W. Moore
This book describes the scope, roles, uses, and development trends of the most widely used software engineering standards. The book concentrates on important software engineering activities-quality and project management, system engineering, dependability, and safety. The analysis and regrouping of the standard collections exposes you to key relationships between standards. James Moore provides valuable insights that allow you to select standards to fill your specific needs with precision. Software Management, Seventh Edition
- Donald J. Reifer
This Seventh Edition of Donald Reifer's popular, bestselling tutorial summarizes what software project managers need to know to be successful on the job. The text provides pointers and approaches to deal with the issues, challenges, and experiences that shape their thoughts and performance. To accomplish its goals, the volume explores recent advances in dissimilar fields such as management theory, acquisition management, globalization, knowledge management, licensing, motivation theory, process improvement, organization dynamics, subcontract management, and technology transfer. Software Safety and Reliability
- Debra S. Herrmann
This original text introduces the concepts, techniques, and approaches used to achieve and assess software safety and reliability. Debra Herrmann presents a cross-section of current safety and reliability standards that cross multiple industrial sectors while focusing on the additional required activities to achieve software safety and reliability. In organizing this text, the she has three objectives. The first is to raise the reader's awareness on the importance of software safety and reliability and on its role in mission critical systems by presenting many illustrative, ever day examples. The second objective is to provide practical information about the current methods used to achieve and assess software safety and reliability. The final objective is to improve the understanding and practice of software safety and reliability by consolidating the latest research so that it can be compared and analyzed for the future. Software Reuse - A Standards-Based Guide
- Carma McClure
This book provides specific instructions for implementing reuse within the context of the IEEE Software Reuse Process Standard 1517 as well as the IEEE/EIA Standard 12207 - Standard for Information Technology - Software Life Cycle Processes. This new guide aids the reader in interpreting the meaning of the standard, implementing the standard, and applying the standard. Like IEEE Std. 1517, this book is written for both managers and technical personnel involved in acquiring, supplying, or developing software applications and systems or reusable assets. Software Change Impact Analysis
- Robert Arnold, Shawn Bohner
The book identifies key impact analysis definitions and themes and illustrates those themes through a collection of representative papers. It includes reports on software source code dependency analysis and software traceability analysis and proposes how results from both areas can more effectively support impact analysis in software engineering repositories. The papers provide fundamental information of enduring value, illustrate the important themes, and equip you with a solid understanding for tackling impact analysis problems.