Software Engineering Fundamentals

Introduction to Software and Software Engineering

  • Definition of Software:

    • Computer programs.

    • Configuration data and files.

    • User and system documentation.

  • Definition of Software Engineering:

    • An engineering discipline concerned with all aspects of software production.

Software Engineering versus Computer Science

  • Differences Between Computer Science and Software Engineering:

    • Computer Science: Focuses on theory and fundamentals.

    • Software Engineering: Focuses on practical aspects of developing and delivering software.

  • Key Software Engineering Challenges:

    • Coping with legacy systems.

    • Coping with increasing diversity, including heterogeneous systems featuring many types of hardware and software.

    • Coping with demands for faster delivery and lower costs.

Software Process and Fundamental Activities

  • Definition of a Software Process:

    • A set of activities and associated results which produce a software product.

  • Four Fundamental Process Activities:

    • Software Specification: Defining system requirements and parameters.

    • Software Development: Designing and coding the software product.

    • Software Validation: Ensuring the software does what it is intended to do based on the software specification.

    • Software Evolution: Managing change, enhancement, and maintenance over time.

Software Process Models

  • Definition of a Software Process Model:

    • A representation of a software process from a specific perspective.

  • Examples of Software Process Models:

    • Workflow Model: Represents the sequence of activities in the process along with their inputs, outputs, and dependencies.

    • Data-Flow or Activity Model: Represents a set of activities that carry out data transformation (input→output\text{input} \rightarrow \text{output}).

    • Role/Action Model: Represents the roles of people involved in the software process and the specific activities for which they are responsible.

Software Development Paradigms

  • Paradigms and Models of Software Development:

    • The Waterfall Approach: Complete one phase (e.g., requirements, design, code, test) entirely before going to the next phase.

    • Evolutionary Development: Build quick, modify, and redo components until completion (prototyping is often used).

    • Formal Transformation: Transform specifications using mathematical methods into a program, guaranteeing program correctness.

    • System Assembly from Reusable Components: Assemble software systems from pre-existing parts and components.

    • Incremental Method: Design and deliver parts as they become available, producing many small deliverables.

Attributes of Good Software

  • Essential Attributes of Quality Software:

    • Maintainability: Software must be maintainable to evolve with changing needs; more than 40%40\% of software cost is due to maintenance.

    • Dependability: Encompasses reliability, security, and safety.

    • Efficiency: Optimal utilization of system resources, including memory and CPU time.

    • Usability: Ensures ease of use through a good UI (User Interface) and documentation.

Ethical Responsibilities

  • Core Ethical Obligations for Engineers:

    • Confidentiality: Respect and maintain the confidentiality of employers and clients.

    • Competence: Avoid misrepresenting the level of competence.

    • Intellectual Property Rights: Adhere to local laws, patents, and copyrights.

    • Computer Misuse: Refrain from misusing computing skills, such as creating viruses, hacking, or committing information theft.




NEW NOTES ABOUT IMPORTANT SLIDES


Different Philosophies of Software Engineering and Pracitices.

  • Software Development Lifecycle: Understand the phases from requirements gathering to deployment and maintenance.

  • Version Control: Use tools like Git to manage changes and collaborate effectively with team members.

  • Testing Methodologies: Familiarize with unit testing, integration testing, and end-to-end testing to ensure software quality.

  • Code Review Practices: Engage in peer reviews to catch bugs early and improve code quality through constructive feedback.

  • Agile Principles: Embrace iterative development and continuous improvement through frameworks like Scrum or Kanban.

Introduction to Software and Software Engineering

  • Definition of Software:

    • Computer programs.

    • Configuration data and files.

    • User and system documentation.

    

  • Definition of Software Engineering:

    • An engineering discipline concerned with all aspects of software production.

    

Software Engineering versus Computer Science

  • Differences Between Computer Science and Software Engineering:

    • Computer Science: Focuses on theory and fundamentals.

    • Software Engineering: Focuses on practical aspects of developing and delivering software.

    

  • Key Software Engineering Challenges:

    • Coping with legacy systems.

    • Coping with increasing diversity, including heterogeneous systems featuring many types of hardware and software.

    • Coping with demands for faster delivery and lower costs.

    

Software Process and Fundamental Activities

  • Definition of a Software Process:

    • A set of activities and associated results which produce a software product.

    

  • Four Fundamental Process Activities:

    • Software Specification: Defining system requirements and parameters.

    • Software Development: Designing and coding the software product.

    • Software Validation: Ensuring the software does what it is intended to do based on the software specification.

    • Software Evolution: Managing change, enhancement, and maintenance over time.

    

Software Process Models

  • Definition of a Software Process Model:

    • A representation of a software process from a specific perspective.

    

  • Examples of Software Process Models:

    • Workflow Model: Represents the sequence of activities in the process along with their inputs, outputs, and dependencies.

    • Data-Flow or Activity Model: Represents a set of activities that carry out data transformation (input→output\text{input} \rightarrow \text{output}).

    • Role/Action Model: Represents the roles of people involved in the software process and the specific activities for which they are responsible.