Software Engineering Introduction

• Problems in software engineering are due to a lack of technical competence

Announcements

• TA office hours are available Monday to Friday
• HW2 is available and due in 9 days. You need to install/learn Ruby and Ruby on Rails

What is Software Engineering

• Software engineering applies engineering principles to software development
• Concepts from CE/CS, management, math, and systems engineering are used
• Involves analysis, design, implementation, and maintenance of software systems
• Aims to improve software products, projects, and processes.
• The ultimate goal is to create high-quality software that meets user needs economically

Brief History of Software Engineering

• 1968: The term "Software Engineering" was first used
• 1975: The first journal, "Transactions on Software Engineering," was published by the IEEE Computer Society
• 1976: IEEE-CS established a standard committee on SWE
• 1993: IEEE-CS/ACM began working to establish SWE as a discipline
• 1996: IEEE-CS/ACM drafted the SWE body of knowledge (SWEBOK)
• 2000: ACM withdrew support
• 2001, 2004, 2013, 2024: The SWEBOK Guide has been published and revised

History of SWE Body of Knowledge (SWEBOK)

• First Draft (1996): Intended to define the boundaries and topics of the SWE body of knowledge
• First SWEBOK Guide (2001): Began discussions about the nature of the SWE discipline, and the required skills for software engineers
• Second SWEBOK Guide (2004): Expanded knowledge and skills included gathering input from professionals, societies, and agencies. It published 10 general knowledge areas
• SWEBOK V3 (2013): Current version
• SWEBOK V4 (April 15, 2024): Incorporates public review, Agile, DevOps, Software Architecture and Software Security

Software Engineering Body of Knowledge (SWEBOK) Main Objectives

• Promotes a consistent understanding of software on a global scale
• Defines the scope and clarifies the relationship between software engineering and other fields
• Characterizes the core content of software engineering
• Provides organized access to the body of information
• Provides a basis for curriculum development, certification, and licensing

15 General Knowledge Areas in SWEBOK Guide

• Software Requirements involves analyzing, specifying, and validating the needs and constraints for a software product
• Manage requirements during the software product lifecycle
• Software Design defines the architecture, components, interfaces, and other characteristics of a system
• Software Construction involves creating working software through coding, verification, testing, and debugging
• Software Testing validates that software behaves as expected through a set of test cases
• Software Maintenance plans for post-delivery operations and maintainability
• Software Configuration Management tracks and controls changes in the software as it evolves
• Software Engineering Management includes planning, estimating, measuring, controlling, and managing risk
• Software Engineering Process focuses on work activities for developing, maintaining, and operating software
• Software Engineering Models & Methods structures software engineering activities
• Software Quality ensures conformance to all requirements
• Software Engineering Professional Practice promotes ethical conduct
• Software Engineering Economics involves decision-making in a business context
• Computing Foundations include understanding the environment in which the software evolves
• Mathematical Foundations include using basic techniques for reasoning
• Engineering Foundations includes skillsets that are relevant to all engineering activities

Software Engineering Benefits

• Software engineering improves programming knowledge and skills
• The software engineering applies engineering principles bringing 3 improvements: in product, project and process
• Software product improvement involves enhancing the quality and aspects of individual software components or complete systems through increased function and design quality
• Software project improvement helps mitigate problems during software development like effort estimations, scheduling and requirements
• Software process improvement contributes to a more skilled and disciplined software development for building and maintaining high-quality systems

Software Deterioration

• Software does not wear out; it deteriorates with changes, defects and instability
• Software engineering techniques are intended to reduce overall deterioration

Related Disciplines

• Software engineering is sometimes viewed as a subset of computer science
• It is sometimes considered a separate discipline
• It shares boundaries with computer science, mathematics, management, and computer/system engineering
• The Software Related Body of Knowledge Guide V3 (SWRBOK V3) is related to all listed

The "Software Engineer" Title

• U.S. law restricts the use of "engineer" titles without a license
• It depends on practicing software engineering for the employer, focusing on the employer's products, and avoid offering services to other parties
• State laws may vary

Certification

• Certifications in American Society for Quality improve employability
• IEEE Computer Society Associate/Professional Software Developer/Master

Four Cs to Become Certified

• Current: To stay current with industry best practices
• Connected: To network with experts in the field
• Career-minded: To improve for promotion or opportunity
• Committed: To advance the profession

Code of Ethics & Professional Practice

• IEEE-CS/ACM has two goals: educating engineers and informing the public
• Code of Ethics has eight principles in its short version
• Two versions both provide sub-principles.

All Eight Principles for Software Engineers

• Public: Act in the public interest
• Client & Employer: Act in the best interest of the client and employer
• Product: Ensure the highest standards
• Judgment: Maintain integrity and independence
• Management: Promote an ethical approach to management
• Profession: Advance integrity
• Colleagues: Support colleagues
• Self: Promote ethical practice