Software Engineering

Comprehensive Guide for

Understanding Principles and
UGC NET Practices

CS Paper-2
Presented by: Prokash Barman

Kalyani University

02/03/25 Prokash Barman 1

 Introduction to Software Engineering

Definition: Software
Engineering is the systematic
- Ensures reliability,
application of engineering
Importance: scalability, and
principles to develop,
maintainability.
operate, and maintain
software systems.

Example: Software
- Provides a structured
- Reduces development time engineering ensures the
approach for quality
and cost. reliability of critical systems
assurance.
like flight control software.

02/03/25 Prokash Barman 2

 Software Engineering vs Programming
• Comparison:

Aspect Software Engineering Programming

Scope Broad, including design Writing code only

Focus Process and structure Syntax and logic

Tools UML, CASE Tools IDEs and Compilers

• Example: Software engineering handles the full project lifecycle, while

programming focuses on implementing specific functionalities.

02/03/25 Prokash Barman 3

 Software Development Life Cycle (SDLC)
Definition: SDLC defines a
structured process for - Requirement Analysis:
developing high-quality Phases: Understanding customer
software in a systematic needs.
manner.

- Implementation:
- Design: Creating - Testing: Verifying the
Writing and integrating
blueprints for the system. software's functionality.
code.

- Deployment: Delivering - Maintenance: Updating

the product to the and fixing issues after
customer. delivery.

02/03/25 Prokash Barman 4

 Software Development Models

- Waterfall Model: Sequential

Popular Models: stages, suitable for well-
defined requirements.

- Iterative Model: - Agile Model: Incremental,

Development occurs in cycles, emphasizes flexibility and
allowing for feedback. collaboration.

Example: Agile is commonly

- V-Model: Verification and
used for dynamic projects like
validation go hand-in-hand.
e-commerce platforms.

02/03/25 Prokash Barman 5

 Requirements
Engineering
• Definition: The process of defining, documenting, and
maintaining software requirements.
• Steps:
• - Elicitation: Collecting user needs.
• - Analysis: Understanding feasibility.
• - Specification: Documenting requirements.
• - Validation: Ensuring correctness and completeness.
• Tools: JIRA, Confluence.

02/03/25 Prokash Barman 6

 Software Design
• Types of Design:
• - Architectural Design: High-level structure of the software.
• - High-Level Design (HLD): Module-level design.
• - Low-Level Design (LLD): Detailed design of individual
components.
• Principles:
• - Modularity: Dividing software into smaller units.
• - Cohesion: Each module performs a single task.
• - Coupling: Reducing dependency between modules.

02/03/25 Prokash Barman 7

 Unified Modeling
Language (UML)
• Definition: UML is a standardized visual language
for modeling software systems.
• Key Diagrams:
• - Use Case Diagram: Depicts user interactions.
• - Class Diagram: Shows relationships between
classes.
• - Sequence Diagram: Represents order of
interactions.

02/03/25 Prokash Barman 8

 Agile Methodology
• Definition: Agile is an iterative approach focusing
on collaboration, flexibility, and customer
satisfaction.
• Principles:
• - Continuous delivery of valuable software.
• - Customer collaboration over contracts.
• - Embracing change at any stage of development.

02/03/25 Prokash Barman 9

 Scrum Framework
• Definition: A popular framework under Agile methodology.
• Key Roles:
• - Product Owner: Defines the product vision.
• - Scrum Master: Facilitates the process.
• - Development Team: Implements the product.
• Artifacts:
• - Product Backlog.
• - Sprint Backlog.
• - Increment.

02/03/25 Prokash Barman 10

 Software Testing
• Definition: Process of verifying that the software
meets customer expectations and is free of bugs.
• Types:
• - Unit Testing: Testing individual components.
• - Integration Testing: Ensuring modules work
together.
• - System Testing: Testing the entire system.
• - Acceptance Testing: Customer validation.

02/03/25 Prokash Barman 11

 Testing Techniques
• Black Box Testing: Focuses on inputs and outputs
without internal knowledge.
• White Box Testing: Examines internal structures or
workings of the application.
• Automation Tools: Selenium, JUnit.

02/03/25 Prokash Barman 12

 Software Metrics
• Definition: Quantitative measures to assess the
quality and performance of software
development.
• Categories:
• - Process Metrics: Efficiency of the process.
• - Product Metrics: Quality of the product.
• - Project Metrics: Timeline, budget, and resource
tracking.

02/03/25 Prokash Barman 13

 Software Configuration
Management (SCM)
• Definition: Managing changes to software to ensure
consistency and traceability.
• Activities:
• - Version Control: Tracking changes in source code.
• - Build Management: Automating the build process.
• - Change Management: Handling modifications
effectively.
• Tools: Git, Jenkins.

02/03/25 Prokash Barman 14

 Software
Maintenance
• Types:
• - Corrective: Fixing errors.
• - Adaptive: Adapting to new environments.
• - Perfective: Enhancing functionalities.
• - Preventive: Reducing future issues.

02/03/25 Prokash Barman 15

 Risk Management
• Definition: Identifying, analyzing, and mitigating
risks during software development.
• Steps:
• - Risk Identification: Listing potential risks.
• - Risk Analysis: Evaluating impact and probability.
• - Risk Mitigation: Implementing strategies to
minimize risks.

02/03/25 Prokash Barman 16

 DevOps
• Definition: Integration of development and IT
operations to shorten development cycles.
• Practices:
• - Continuous Integration (CI).
• - Continuous Deployment (CD).
• Tools: Jenkins, Docker, Kubernetes.

02/03/25 Prokash Barman 17

 Software Quality
Assurance (SQA)
• Definition: Ensures the quality of software through
process adherence and standards.
• Principles:
• - Verification: Ensures the product is built right.
• - Validation: Ensures the right product is built.

02/03/25 Prokash Barman 18

 Object-Oriented Programming
(OOP) Principles

• Core Concepts:
• - Encapsulation: Bundling data and methods.
• - Abstraction: Hiding implementation details.
• - Inheritance: Reusing code through hierarchy.
• - Polymorphism: Multiple forms of a function.

02/03/25 Prokash Barman 19

 Microservices
Architecture
• Definition: Building applications as a collection of
loosely coupled services.
• Advantages:
• - Scalability.
• - Fault Isolation.
• - Technology Independence.
• Examples: Netflix and Amazon use microservices
for scalability.

02/03/25 Prokash Barman 20

 Software Reliability
Engineering
• Definition: Ensures that software performs its intended
function without failure under specified conditions.
• Factors Affecting Reliability:
• - Fault Tolerance.
• - Error Detection and Correction.
• - Robustness of the Design.
• Applications: Critical systems like medical devices,
aerospace software.

02/03/25 Prokash Barman 21

 Ethical Issues in
Software Development
• Concerns:
• - Privacy violations.
• - Intellectual property.
• - Data misuse.
• Solutions:
• - Adhering to GDPR.
• - Conducting Ethical Audits.
• - Transparent Algorithms.

02/03/25 Prokash Barman 22

 Software
Performance Testing
• Definition: Evaluates the speed, responsiveness,
and stability of software under workload.
• Types:
• - Load Testing.
• - Stress Testing.
• - Scalability Testing.
• Tools: Apache JMeter, LoadRunner.

02/03/25 Prokash Barman 23

 Software Deployment
Strategies
• Methods:
• - Blue-Green Deployment: Running two identical
environments.
• - Canary Release: Gradual rollout to minimize risk.
• - Rolling Deployment: Updating software
incrementally.

02/03/25 Prokash Barman 24

 AI in Software
Testing
• Definition: Using AI tools to enhance testing
accuracy and efficiency.
• Capabilities:
• - Automated Bug Detection.
• - Regression Testing.
• - Predictive Analytics.
• Tools: Testim, Applitools.

02/03/25 Prokash Barman 25

 Containerization in
Software Engineering
• Definition: Packaging software along with its
dependencies for consistent deployment.
• Benefits:
• - Portability.
• - Scalability.
• - Isolation.
• Tools: Docker, Kubernetes.

02/03/25 Prokash Barman 26

 Code Review Best
Practices
• Principles:
• - Review Small Chunks of Code.
• - Focus on Logical Errors.
• - Ensure Adherence to Coding Standards.
• Tools: GitHub, Bitbucket.

02/03/25 Prokash Barman 27

 Software
Documentation
• Importance:
• - Simplifies Maintenance.
• - Assists New Developers.
• - Tracks Project Progress.
• Types:
• - Requirement Documentation.
• - API Documentation.
• - User Manuals.

02/03/25 Prokash Barman 28

 Software
Prototyping
• Definition: Building an early model of the software
to validate ideas and gather feedback.
• Benefits:
• - Reduces Risks.
• - Enhances Stakeholder Involvement.
• - Accelerates Time-to-Market.

02/03/25 Prokash Barman 29

 Secure Software Development
Life Cycle (SSDLC)

• Definition: Integrating security practices into each

SDLC phase.
• Key Practices:
• - Threat Modeling.
• - Static Code Analysis.
• - Security Testing.

02/03/25 Prokash Barman 30

 Software Design
Patterns
• Definition: Reusable solutions to common
software design problems.
• Types:
• - Creational (e.g., Singleton).
• - Structural (e.g., Adapter).
• - Behavioral (e.g., Observer).
• Example: The Singleton pattern ensures a class has
only one instance.

02/03/25 Prokash Barman 31

 Human-Computer
Interaction (HCI)
• Definition: Designing interfaces that allow users to
interact effectively with software.
• Principles:
• - Usability.
• - Accessibility.
• - Feedback Mechanisms.
• Tools: Figma, Adobe XD.

02/03/25 Prokash Barman 32

 Mobile Application
Development
• Key Considerations:
• - Cross-Platform Compatibility.
• - User Interface Design.
• - Performance Optimization.
• Frameworks: Flutter, React Native.

02/03/25 Prokash Barman 33

 Software Security
• Definition: Practices to protect software systems
from threats like unauthorized access and data
breaches.
• Key Aspects:
• - Secure Coding.
• - Encryption.
• - Vulnerability Assessment.
• Tools: OWASP ZAP, Burp Suite.

02/03/25 Prokash Barman 34

 Cloud Computing and
Software Engineering
• Definition: Utilizing cloud-based resources for
software development and deployment.
• Benefits:
• - On-Demand Scalability.
• - Cost-Effectiveness.
• - Remote Collaboration.
• Popular Platforms: AWS, Microsoft Azure, Google
Cloud.

02/03/25 Prokash Barman 35

 Emerging Trends in
Software Engineering
• Trends:
• - AI-Driven Development.
• - Low-Code/No-Code Platforms.
• - Edge Computing.
• - Blockchain for Secure Transactions.
• Examples: AI tools like Codex assist developers in
writing efficient code.

02/03/25 Prokash Barman 36

 Software
Documentation
• Importance:
• - Simplifies Maintenance.
• - Assists New Developers.
• - Tracks Project Progress.
• Types:
• - Requirement Documentation.
• - API Documentation.
• - User Manuals.

02/03/25 Prokash Barman 37

 Software
Prototyping
• Definition: Building an early model of the software
to validate ideas and gather feedback.
• Benefits:
• - Reduces Risks.
• - Enhances Stakeholder Involvement.
• - Accelerates Time-to-Market.

02/03/25 Prokash Barman 38

 Secure Software Development
Life Cycle (SSDLC)

• Definition: Integrating security practices into each

SDLC phase.
• Key Practices:
• - Threat Modeling.
• - Static Code Analysis.
• - Security Testing.

02/03/25 Prokash Barman 39

 Summary and Future
Directions
• Key Takeaways:
• - Software Engineering principles ensure quality and
efficiency.
• - Emerging trends like AI, DevOps, and Microservices are
shaping the future.
• - Ethical considerations and security are paramount in
modern development.
• Future Focus: Leveraging AI and automation for smarter
software development.

02/03/25 Prokash Barman 40