Sy Bsc (Computer Science)
Savitribai Phule Pune University
As per New Education Policy (NEP) 2020
Semester:- 3
Subject:-Software Engineering
Chapter 2:-Software Development Life Cycle
Lecture 1
What is the Software Development Life Cycle (SDLC)?
SDLC is a process followed for software building within a software organization. SDLC
consists of a precise plan that describes how to develop, maintain, replace, and enhance
specific software. The life cycle defines a method for improving the quality of software and
the all-around development process.
Stage-1: Planning and Requirement Analysis
Planning is a crucial step in everything, just as in software development. In this same stage,
requirement analysis is also performed by the developers of the organization. This is
attained from customer inputs, and sales department/market surveys.
Stage-2: Defining Requirements
In this stage, all the requirements for the target software are specified. These requirements get approval
from customers, market analysts, and stakeholders. This is fulfilled by utilizing SRS (Software
Requirement Specification). This is a sort of document that specifies all those things that need to be
defined and created during the entire project cycle.
Stage-3: Designing Architecture
SRS (Software Requirements Specification) is a reference for software designers to come up with the
best architecture for the software. Hence, with the requirements defined in SRS, multiple designs for the
product architecture are present in the Design Document Specification (DDS).
Stage-4: Developing Product
At this stage, the fundamental development of the product starts. For this, developers use a
specific programming code as per the design in the DDS. Hence, it is important for the coders
to follow the protocols set by the association. Conventional programming tools like compilers,
interpreters, debuggers, etc. are also put into use at this stage. Some popular languages like
C/C++, Python, Java, etc. ae put into use as per the software regulations.
Stage-5: Product Testing and Integration
After the development of the product, testing of the software is necessary to ensure its
smooth execution. Although, minimal testing is conducted at every stage of SDLC. Therefore,
at this stage, all the probable flaws are tracked, fixed, and retested. This ensures that the
product confronts the quality requirements of SRS.
Stage-6: Deployment and Maintenance of Products
After detailed testing, the conclusive product is released in phases as per the organization’s
strategy. Then it is tested in a real industrial environment. It is important to ensure its smooth
performance. If it performs well, the organization sends out the product as a whole. After
retrieving beneficial feedback, the company releases it as it is or with auxiliary improvements
to make it further helpful for the customers. However, this alone is not enough. Therefore,
along with the deployment, the product’s supervision.
Requirements engineering tasks
Requirements engineering tasks involve a structured process to identify, analyze, and
manage the needs and constraints of a software project. This ensures that the final
product meets user expectations and functions correctly.
What is Requirement Engineering?
Requirements engineering is a broad domain that focuses on being the connector
between modeling, analysis, design, and construction. It is the process that defines,
identifies, manages, and develops requirements in a software engineering design
process. This process uses tools, methods, and principles to describe the system's
behavior and the constraints that come along with it.
Requirements Engineering Tasks
The software requirements engineering process includes the following steps of
activities:
Inception
Elicitation
Elaboration
Negotiation
Specification
Validation
Requirements Management
Inception
The initial phase that outlines how to begin the project.
It focuses on:
● Understanding the problem
● Identifying stakeholders
● Exploring possible solutions
● Promoting communication between developers and customers
2. Elicitation
In this phase, requirements are gathered from stakeholders.
Key concerns:
● Scope issues – too detailed or vague requirements
● Understanding gaps – miscommunication between users and developers
● Volatility – changing requirements during the project
3. Elaboration
Refines and expands on the gathered requirements.
Involves:
● Creating models and prototypes
● Exploring features and constraints in detail
4. Negotiation
Discussion between customer and developer to:
● Prioritize requirements
● Balance scope, cost, time, and resources
● Resolve conflicts and agree on feasible solutions
5. Specification
Documenting the finalized requirements using:
● Written documents
● Use cases and prototypes
● Models like ER diagrams, DFDs, and Data Dictionaries A clear, understandable
specification is shared with the customer.
6. Validation
Ensures the requirements are correct and complete through:
● Formal technical reviews
● Prototyping, test-case generation, and consistency checks
● Involvement of stakeholders in verification
7. Requirements Management
Ongoing process to:
● Track and control changes in requirements
● Analyze the impact of new requirements
● Ensure smooth implementation and delivery
Connect With Us On Social Media
Telegram Doubt Discussion
Instagram Account
Telegram Channel Group
- You Can ask Your Doubt
- Pdfs, Notes are Shared. - You can also ask your
Personally. You can Dm me.
- Important Updates. doubts here, other
- Educational reels, Important
students or me can solve
Updates Through Stories.
your doubts.
Thank You
- Don’t Forget To Like Share and Subscribe.