Unit 1 Software Engineering mrsandy.

in

UNIT I: Software Engineering

1. Software Engineering
1.1 Introduction to Software Engineering
Software Engineering is the systematic application of engineering principles to the design,
development, maintenance, testing, and evaluation of software. It is a discipline that focuses on
applying engineering methods to ensure that software is built to meet specific requirements, is
reliable, efficient, and maintainable.
Software engineering involves:
Understanding user requirements
Designing software solutions
Writing, testing, and maintaining code
Managing the project and team
The goal of software engineering is to produce high-quality software in a cost-effective and timely
manner.
1.2 Software Development Life Cycle (SDLC)
Definition The SDLC is a well-defined, structured approach for managing the complete lifecycle of
software development. It encompasses phases designed to ensure consistency and quality
throughout the process.
Phases:
1. Requirement Analysis: Understanding and documenting user needs and constraints.
2. System Design: Architecting the solution by defining system components and their
interactions.
3. Implementation: Writing and integrating source code to build the system.
4. Testing: Conducting systematic evaluations to identify and resolve defects.
5. Deployment: Delivering the software to production environments.
6. Maintenance: Addressing updates, bug fixes, and feature enhancements post-
deployment.
Unit 1 Software Engineering mrsandy.in

Importance
Provides clarity and direction throughout project stages.
Facilitates better resource allocation and time management.
Supports risk mitigation by addressing potential challenges early in the process.

1.3 Software Metrics

Definition Metrics provide quantitative insights into the efficiency, quality, and effectiveness of
software development processes and products. They serve as benchmarks for assessing
performance and driving improvements.
Types of Metrics:
1. Process Metrics: Measure attributes of the development process, such as defect rates
and cycle times.
2. Product Metrics: Assess attributes of the software product, including reliability and
usability.
3. Project Metrics: Monitor project-specific parameters like budget, timeline adherence,
and resource utilization.
Examples
Defect Density: Number of defects per 1,000 lines of code.
Cyclomatic Complexity: Measures the complexity of a program's control flow.
Importance
Facilitates informed decision-making and continuous improvement.
Identifies bottlenecks and inefficiencies in development processes.
Ensures alignment with quality and performance standards.

1.3 Software Maintenance

Definition Software Maintenance involves activities undertaken post-deployment to ensure that
the software remains functional, relevant, and efficient.
Unit 1 Software Engineering mrsandy.in

Types:
1. Corrective Maintenance: Resolves errors and defects discovered post-release.
2. Adaptive Maintenance: Adjusts software to accommodate environmental changes such
as new operating systems.
3. Perfective Maintenance: Enhances existing features and introduces new
functionalities.
4. Preventive Maintenance: Proactively identifies and resolves potential future issues.
Importance
Ensures software adapts to evolving user needs and environmental changes.
Maintains software usability, reliability, and performance over time.
Prolongs the operational lifespan of software systems.

2. Software Characteristics
2.1 Main Characteristics of Software
Software is different from hardware in several important ways. Some of the primary characteristics
of software are:
1. Intangibility:
Software is intangible, meaning it cannot be physically touched or seen. It is represented by code
that is compiled and executed.
2. Complexity:
Software systems are often large and intricate, with many components that interact with each
other. The complexity of software arises from the need to meet various user needs and external
system requirements.
3. Conformity to specifications:
Software must behave as expected according to the specifications provided by stakeholders. A
software system must meet functional, performance, and security specifications.
Unit 1 Software Engineering mrsandy.in

4. Flexibility:
Software systems can be modified and adapted to new environments or to meet new
requirements. Unlike hardware, software can be changed easily after deployment.
5. Maintainability:
Software needs to be maintained throughout its lifecycle. This includes fixing bugs, improving
performance, and adapting to new technologies.
6. Reusability:
Parts of the software (modules, functions, etc.) can be reused in different systems or applications,
reducing the need to recreate common functionalities.

3. Software Components
Software components are self-contained, modular units of software that encapsulate specific
functionality. They are designed to be reusable, interchangeable, and independent, making them
essential for building complex software systems.
3.1 Major Components of Software
Software is typically composed of several key components, which include:
1. Functional Components:
These components define the functionality of the software and consist of the core logic or
algorithms that carry out the tasks required by users.
2. Non-Functional Components:
These are the supporting aspects of software, including:
Performance: How fast the software operates.
Security: Protection of data and systems.
Scalability: Ability to handle increased workloads.
Usability: How easy the software is to use.
3. User Interface (UI):
Unit 1 Software Engineering mrsandy.in

The part of the software that interacts with the user. A good UI ensures that users can easily
perform tasks and access the software's functionalities.
4. Data Storage:
The software typically requires data storage for information to be retained, retrieved, and
processed. This may involve databases, file systems, or other storage mechanisms.
5. Networking Components:
For software that requires communication with other systems or over the internet, networking
components are crucial for facilitating data transfer and connectivity.

4. Software Applications
It is a type of computer program designed to perform specific tasks for end-users. It serves as a
bridge between the user and the computer's hardware, allowing individuals to accomplish various
objectives without needing to understand the underlying technical details.
4.1 Types of Software Applications
Software can be used for a wide variety of applications. Some common categories include:
1. System Software:
System software manages hardware resources and provides the foundation for running application
software. Examples include operating systems (e.g., Windows, Linux), device drivers, and utility
programs.
2. Application Software:
This includes programs designed to perform specific tasks for the user. Examples include word
processors, web browsers, and spreadsheets.
3. Embedded Software:
Embedded software is designed to operate hardware systems. It is often used in devices such as
cars, medical devices, home appliances, etc.
4. Enterprise Software:
Unit 1 Software Engineering mrsandy.in

These are large-scale applications used by businesses and organizations for tasks such as
customer relationship management (CRM), enterprise resource planning (ERP), and human
resource management (HRM).
5. Mobile Applications:
Software designed specifically for mobile devices such as smartphones and tablets. Examples
include social media apps, games, and productivity tools.

5. Software Process Models

A software process model is a simplified representation of a software development process. It
outlines the various stages, activities, and tasks involved in creating a software product. These
models act as roadmaps, guiding development teams through the entire software lifecycle.
5.1 Waterfall Model
5.1.1 Definition
The Waterfall model is one of the earliest and most straightforward software development
process models. It follows a linear and sequential approach where progress flows downwards
through distinct phases, much like a waterfall.
5.1.2 Phases:
1. Requirement Analysis: Gather and document requirements from users.
2. System Design: Design system architecture and components.
3. Implementation: Write the code and develop the system.
4. Testing: Test the system for defects and ensure it meets requirements.
5. Deployment: Deploy the software to production.
6. Maintenance: After deployment, make any necessary updates or fixes.
5.1.3 Advantages:
Simple and easy to understand.
Well-documented process.
Phases are easy to manage and track.
5.1.4 Disadvantages:
Unit 1 Software Engineering mrsandy.in

Inflexible to changes once a phase is completed.

Not suitable for complex projects with evolving requirements.

5.2 Spiral Model

5.2.1 Definition
The Spiral model is a risk-driven model that allows for iterative development and refinement of
the software. It combines elements of both the Waterfall and Prototyping models.
5.2.2 Phases:
1. Planning: Define objectives, constraints, and requirements.
2. Risk Analysis: Identify potential risks and mitigate them.
3. Engineering: Build the software incrementally.
4. Evaluation: Test the software and get feedback.
5. Planning for the next iteration: Refine and repeat the cycle.
5.2.3 Advantages:
Flexible and allows for changes during the development.
Risk management is an integral part of the process.
5.2.4 Disadvantages:
Can be expensive due to iterative nature.
Requires skilled risk management.

5.3 Prototyping Model

5.3.1 Definition
The Prototyping model focuses on developing a prototype or an early version of the software to
gain user feedback and refine the system's requirements.
5.3.2 Phases:
1. Requirement Gathering: Gather initial requirements for the prototype.
2. Develop Prototype: Create a simple version of the software with limited functionality.
Unit 1 Software Engineering mrsandy.in

3. User Evaluation: Get feedback from users and identify changes.

4. Refinement: Iterate the prototype until it meets the users' needs.
5.3.3 Advantages:
Allows users to visualize and interact with the system early on.
Requirements can be clarified during the process.
5.3.4 Disadvantages:
Can lead to incomplete systems if users get attached to prototypes.
May result in scope creep as users continuously add new features.

5.4 Fourth Generation Techniques (4GT)

5.4.1 Definition
Fourth Generation Techniques (4GT) refer to a set of tools and methods that use higher-level
programming languages, visual tools, and automatic code generation. The aim is to reduce the
complexity of software development and speed up the process.
5.4.2 Examples:
Low-code/no-code platforms that allow users to build applications with minimal
programming knowledge.
Database query languages like SQL that simplify interaction with databases.
5.4.3 Advantages:
Faster development process.
Easier to use and understand, even for non-programmers.
5.4.4 Disadvantages:
May not be suitable for highly complex or specialized applications.
Limited flexibility compared to traditional programming languages.

6. Concepts of Project Management

Unit 1 Software Engineering mrsandy.in

6.1 Introduction to Project Management

Project Management in software engineering involves planning, organizing, and overseeing
software development projects. The goal is to ensure that projects are completed on time, within
budget, and meet the specified requirements.
6.2 Key Aspects of Software Project Management:
1. Scope Management: Define and control what is included in the project.
2. Time Management: Plan the timeline and meet deadlines.
3. Cost Management: Estimate costs and control expenses.
4. Quality Management: Ensure that the software meets required quality standards.
5. Risk Management: Identify, assess, and mitigate potential risks during development.
6. Team Management: Organize and lead the development team effectively.

7. Role of Metrics & Measurements

7.1 Importance of Metrics in Software Engineering
Metrics and measurements are crucial for assessing the effectiveness of the software
development process, managing the progress, and ensuring quality. Metrics help in understanding
whether the project is on track and in making data-driven decisions.
7.2 Types of Software Metrics:
1. Product Metrics: Measure characteristics of the software product itself (e.g., size,
complexity, performance).
2. Process Metrics: Measure the efficiency of the development process (e.g., time to fix bugs,
defect density).
3. Project Metrics: Measure the overall project performance (e.g., budget, schedule
adherence).
Examples:
Lines of Code (LOC): Measures the size of the software.
Cyclomatic Complexity: Measures the complexity of the software's code.
Defect Density: Measures the number of defects per unit of code.