Initially, software engineering was seen as a reactive measure to the 'software crisis,' focusing on resolving basic project failures . Over time, as technological advances like the Internet of Things and edge computing have developed, software engineering evolved significantly . Modern software ecosystems require integrating complex system components, emphasizing architecture as a foundational element. This evolution is marked by an intertwined relationship with systems engineering, where effective system architecture and integration become essential, reflective of software’s centrality in modern systems .

Standards bodies like ISO/IEC JTC 1/SC 7 have played a crucial role in compiling and publishing the Software Engineering Body of Knowledge (SWEBOK), which consolidates best practices in software engineering . This document provides a framework for the industry, guiding both academic curricula and professional standards for practitioners. The recognition and development of SWEBOK have influenced the software engineering profession by promoting a consistent set of guidelines and practices worldwide, thus enhancing the quality and predictability of software development projects .

Margaret Hamilton's work during the Apollo missions was instrumental in promoting software engineering as a legitimate discipline by emphasizing systematic approaches to software development, which was crucial for the success of these critical missions . She coined the term 'software engineering' to reinforce the importance and legitimacy of their rocesses in managing complex software systems. Her advocacy helped validate the discipline within the context of high-stakes, mission-critical applications .

The primary challenges that necessitated the establishment of software engineering as a distinct field in the 1960s included projects that were over budget, missed deadlines, required extensive debugging, and often failed to meet consumer needs or were never completed . These challenges were addressed during the first NATO conference on software engineering in 1968, where best practices and guidelines for software development were established to tackle the 'software crisis' . This conference laid the foundation for formal methodologies in the discipline, helping to standardize processes and improve project management practices.

The Capability Maturity Model Integration (CMMI) is used to evaluate the process maturity and capabilities of software development teams, particularly by the US Government, to assess and improve their performance . The Software Engineering Institute (SEI), established at Carnegie Mellon University, played a pivotal role in the formation of CMMI through its Software Process Program, which was founded by Watts Humphrey to understand and manage software engineering processes . The CMMI framework helps organizations improve their development processes and achieve higher levels of process maturity.

Notable definitions of software engineering include: the Bureau of Labor Statistics' description as the 'systematic application of scientific and technological knowledge' , IEEE's portrayal as a 'systematic, disciplined, quantifiable approach' , Ian Sommerville's view of it as concerned with all aspects of software production , and Google’s emphasis on programming integrated over time . These definitions collectively reflect the discipline’s comprehensive scope involving both theoretical principles and practical applications necessary for developing and maintaining software systems.

The Software Engineering Institute (SEI) significantly influenced modern software engineering practices and standards through initiatives like the Software Process Program, which Watts Humphrey founded. This program laid the groundwork for understanding and refining software engineering processes, leading to developments such as the Capability Maturity Model Integration (CMMI). SEI's work guided organizations in enhancing their software development processes, thereby improving the quality and consistency of software products and impacting official assessments and certifications globally .

Modern technological trends such as Edge Computing and the Internet of Things have emphasized the prominence of software in integrating complex system components, thus influencing the relationship between software engineering and systems engineering . These trends highlight the need for software to be a critical factor in systems architecture, leading to a closer intertwining of the two disciplines. Good systems engineering is essential in enabling effective software engineering, as it provides the framework for incorporating software solutions into broader system landscapes .

The 'software crisis' emerged during the 1960s due to widespread issues in software projects that were over budget, behind schedule, and unreliable . This crisis was publicly addressed in the first NATO conference in 1968, highlighting these often catastrophic failures . The term 'software crisis' catalyzed the establishment of software engineering as a formal discipline, underpinning the urgency for developing structured methods and practices to avoid similar project failures in the future, thereby shaping the industry's focus on processes and tooling.

The legitimacy of software engineering as an engineering discipline is contentious. David Parnas argues that it qualifies as a form of engineering . In contrast, Steve McConnell asserts that it is not currently recognized as such, though it should be . Donald Knuth views programming as both an art and a science, suggesting a hybrid nature , while Edsger W. Dijkstra has criticized the misuse of 'software engineering' in the US . These perspectives highlight the diversity in opinion regarding whether software engineering measures up to traditional engineering disciplines and emphasize the unique qualities that differentiate it.