Introduction to Software Engineering

Lecture 1 of CS605 Software Engineering - II establishes the academic foundation and industrial context for systematic software development. The lecture examines classical definitions of software engineering, contrasting casual hobbyist programming with disciplined, repeatable engineering methodologies. Students analyze Fritz Bauer's seminal definition emphasizing sound engineering principles to obtain economical, reliable software that executes efficiently on real computing machines, as well as the IEEE 610.12 standard. The historical emergence of the software crisis is investigated, highlighting how skyrocketing software costs, pervasive defects, schedule slippages, and maintenance nightmares necessitated structured engineering frameworks. The discussion details the multifaceted nature of software products, spanning executable programs, operating procedures, architectural documentation, and data structures. Special focus is placed on the dual nature of software as both an operational product delivering computational power and a vehicle for managing enterprise information. Learners review core principles distinguishing software engineering from traditional hardware manufacturing, particularly the reality that software does not wear out in the physical sense but inevitably deteriorates due to continuous environmental changes and unmanaged modifications. The curriculum systematically aligns practical industry development workflows with formal IEEE standards and CMMI process maturity levels. Reviewing the accompanying lecture handouts and conceptual diagrams reinforces understanding of project monitoring, statistical process control, and configuration baselines. Consistent evaluation of planning templates, estimation equations, and decomposition hierarchies ensures robust preparation for academic assessments. Students investigate the role of software process engineering in synchronizing development activities across multidisciplinary engineering teams. The discussion highlights how requirements traceability matrices prevent scope creep and ensure strict adherence to customer specifications. Key concepts such as configuration item identification, version control baselines, and formal change control board procedures are thoroughly analyzed. The lecture details algorithmic cost estimation models including Function Point Analysis to produce reliable effort and duration forecasts. Structured decomposition methods are demonstrated using task networks and PERT charts to evaluate critical path scheduling and project float. Network diagramming techniques provide deterministic and probabilistic insights into project milestones and resource dependencies.