Software Development Life Cycle

Jan 3, 2024

Godofredo T. Avena
PUP, Part time Instructor
 History of Software Engineering
• Key dates in the history of software engineering are:
• 1968: Nato conference on software engineering. Publication of note on the dangers of the goto statement in programs.
• Early 1970s. Development of the notions of structured programming. Development of Pascal programming language. Development of
Smalltalk languages which introduced notions of object-oriented development.
• Late 1970s. Early use of software design methods such as Yourdon and Constantine’s structured design. Development of first
programming environments.
• Early 1980s. CASE tools introduced to support design methods. Development of algorithmic approaches to software costing and
estimation. Publication of the 1st edition of this book as the first student textbook on software engineering.
• Late 1980s. Increased use of object-oriented programming through languages such as C++ and Objective-C. Introduction of object-
oriented design methods. Extensive use of CASE tools.
• Early 1990s. Object-oriented development becomes a mainstream development technique. Commercial tools to support requirements
engineering become available.
• Late 1990s. Java is developed and released in the mid-1990s. Increasing attention paid to notions of software architecture. Client-server
distributed architectures are increasingly used. Notion of component-based software engineering is proposed. The UML is proposed,
integrating several separately developed notations for representing object-oriented systems.
• Early 2000s. Use of integrated development environments becomes more common. Use of stand-alone CASE tools declines. Use of the
UML becomes widespread. Increasing use of scripting languages such as Python and PERL for software development. C# developed as a
competitor to Java. Agile methods proposed and many companies experiment with these approaches.
• 2009-2010 –. Emergence of web-based systems and software as a service. Services become the dominant approach to reuse and agile
methods emerge into the mainstream. Agile approaches evolve to cope with larger system development. An app industry emerges to
develop software for increasingly capable mobile devices. Government and enterprise systems continue to grow in size. Node JS first
introduced, Deep Learning becomes feasible
Software engineering
• Engineering – application of science, theories, tools and methods to find
cost effective solutions to problems.
• Software engineering - is an engineering discipline that is concerned
with all aspects of software production from the early stages of system
specification through to maintaining the system after it has gone into
use.
• IEEE defines software engineering as: It is defined as systematic,
disciplined and quantifiable approach for the development, operation
and maintenance of software
• All aspects of software production
• Not just technical process of development. Also project management and the development
of tools, methods etc. to support software production.
Software Engineering: Definition
Software Engineering is a collection of techniques,
methodologies and tools that help
with the production of

• a high quality software system

• with a given budget
• before a given deadline

while change occurs.

20
Importance of software engineering
• More and more, individuals and society rely on advanced software
systems. We need to be able to produce reliable and trustworthy
systems economically and quickly.
• It is usually cheaper, in the long run, to use software engineering
methods and techniques for software systems rather than just write
the programs as if it was a personal programming project. For most
types of system, the majority of costs are the costs of changing the
software after it has gone into use.
Software costs
• Software costs often dominate computer system costs. The costs of
software on a PC are often greater than the hardware cost.
• Software costs more to maintain than it does to develop. For systems
with a long life, maintenance costs may be several times
development costs.
• Software engineering is concerned with cost-effective software
development.
 Software Crisis
• It was a term used in the early days of computing science to describe the difficulty of
writing a useful and efficient program in the allotted project time line.
• There were many difficulties in the development of large software systems during the
1960s and 1970s.
• never completed systems
• missed deadlines
• exceeded budgets
• a system that does not do all that is required of it
• a system that works but is difficult to use
• a system difficult to modify to meet changes in organizational needs and practices
• a loss of trust from users, who may experience many problems with using the software.

• These problems were largely due to the lack of any framework for the planning and organization
of software development projects. Although some software projects were organized, and these
were often the more successful ones, it was the luck of the draw whether a project manager had
good intuitions for software development, and whether or not problems arose due to
misunderstandings between the customers and the developers of the system. Likewise, there
were no clear methods to monitor whether a system was soon to go over budget or miss
deadlines.
 Software development lifecycle (SDLC)

The software development lifecycle (SDLC) is the cost-effective and time-efficient process that development
teams use to design and build high-quality software. The goal of SDLC is to minimize project risks through
forward planning so that software meets customer expectations during production and beyond. This
methodology outlines a series of steps that divide the software development process into tasks you can assign,
complete, and measure.

Here are some benefits of SDLC:

•Increased visibility of the development process for all stakeholders involved
•Efficient estimation, planning, and scheduling
•Improved risk management and cost estimation
•Systematic software delivery and better customer satisfaction
The software process
• A structured set of activities required to develop a
software system.
• Many different software processes but all involve:
• Specification – defining what the system should do;
• Design and implementation – defining the organization of the system and
implementing the system;
• Validation – checking that it does what the customer wants;
• Evolution – changing the system in response to changing customer needs.
• A software process model is an abstract representation of a process.
It presents a description of a process from some particular
perspective.

30/10/2014 Chapter 2 Software Processes 10

Software process descriptions
• When we describe and discuss processes, we usually talk about the
activities in these processes such as specifying a data model,
designing a user interface, etc. and the ordering of these activities.
• Process descriptions may also include:
• Products, which are the outcomes of a process activity;
• Roles, which reflect the responsibilities of the people involved in the process;
• Pre- and post-conditions, which are statements that are true before and after
a process activity has been enacted or a product produced.

30/10/2014 Chapter 2 Software Processes 11

Plan-driven and agile processes
• Plan-driven processes are processes where all of the process activities
are planned in advance and progress is measured against this plan.
• In agile processes, planning is incremental and it is easier to change
the process to reflect changing customer requirements.
• In practice, most practical processes include elements of both plan-
driven and agile approaches.
• There are no right or wrong software processes.

30/10/2014 Chapter 2 Software Processes 12

 Software process models

30/10/2014 Chapter 2 Software Processes 13

Software process models
• The waterfall model
• Plan-driven model. Separate and distinct phases of specification and
development.
• Incremental development
• Specification, development and validation are interleaved. May be plan-
driven or agile.
• Integration and configuration
• The system is assembled from existing configurable components. May be
plan-driven or agile.
• In practice, most large systems are developed using a process that
incorporates elements from all of these models.

30/10/2014 Chapter 2 Software Processes 14

The waterfall model

30/10/2014 Chapter 2 Software Processes 15

Waterfall model phases
• There are separate identified phases in the waterfall model:
• Requirements analysis and definition
• System and software design
• Implementation and unit testing
• Integration and system testing
• Operation and maintenance
• The main drawback of the waterfall model is the difficulty of
accommodating change after the process is underway. In principle, a
phase has to be complete before moving onto the next phase.

30/10/2014 Chapter 2 Software Processes 16

Waterfall model problems
• Inflexible partitioning of the project into distinct stages makes it
difficult to respond to changing customer requirements.
• Therefore, this model is only appropriate when the requirements are well-
understood and changes will be fairly limited during the design process.
• Few business systems have stable requirements.
• The waterfall model is mostly used for large systems engineering
projects where a system is developed at several sites.
• In those circumstances, the plan-driven nature of the waterfall model helps
coordinate the work.

30/10/2014 Chapter 2 Software Processes 17

Incremental development

30/10/2014 Chapter 2 Software Processes 18

Incremental development benefits
• The cost of accommodating changing customer requirements is
reduced.
• The amount of analysis and documentation that has to be redone is much less
than is required with the waterfall model.
• It is easier to get customer feedback on the development work that
has been done.
• Customers can comment on demonstrations of the software and see how
much has been implemented.
• More rapid delivery and deployment of useful software to the
customer is possible.
• Customers are able to use and gain value from the software earlier than is
possible with a waterfall process.
30/10/2014 Chapter 2 Software Processes 19
Incremental development problems
• The process is not visible.
• Managers need regular deliverables to measure progress. If systems are
developed quickly, it is not cost-effective to produce documents that reflect
every version of the system.
• System structure tends to degrade as new increments are added.
• Unless time and money is spent on refactoring to improve the software,
regular change tends to corrupt its structure. Incorporating further software
changes becomes increasingly difficult and costly.

30/10/2014 Chapter 2 Software Processes 20

Integration and configuration
• Based on software reuse where systems are integrated from existing
components or application systems (sometimes called COTS -
Commercial-off-the-shelf) systems).
• Reused elements may be configured to adapt their behaviour and
functionality to a user’s requirements
• Reuse is now the standard approach for building many types of
business system
• Reuse covered in more depth in Chapter 15.

30/10/2014 Chapter 2 Software Proceses 21

Software application
development

Agile Scrum methodology

Learning outcome:
1. Understand the phases of software development using Scrum
framework
Agile Scrum methodology
Agile is an iterative and incremental approach to software development that
values flexibility, collaboration, and continuous improvement. The Agile project
development is based on the Agile Manifesto, which was created in 2001 by a
group of software developers who were dissatisfied with the limitations of
traditional software development approaches.

Agile Scrum is a popular framework or methodology for software

development that is based on the Agile principles. It emphasizes on
delivering working software in small increments, rather than trying to
deliver a complete product all at once. The methodology is named after the
rugby term “scrum,” which refers to a strategy in which players huddle
together to restart play.
Scrum Roles/Personas

SCRUM MASTER : a servant-leader for the team, the one protecting the good
practice of the method. Responsible for helping ensure the success of the project,
removes impediments for the team, help the team make responsible decisions and
basically support the team in any way possible.

PRODUCT OWNER : is to be the bridge between the business part and the technical
part of the project. Therefore, they are the link between the client and the
development team

DEVELOPMENT TEAM : is responsible for transforming the expressed needs into usable
functionalities. The team can be multidisciplinary and involve several types of people:
developers, software architects, functional analysts, graphic designers, systems engineers,
testers, etc.
Events, ceremonies or meetings in Scrum
Sprint Planning: This meeting is held at the beginning of each Sprint and is defined
how it will approach the project coming from the Product Backlog stages and deadlines

Backlog Grooming: refinement on-demand meeting for features that need reviewing

Daily Stand up: Three questions are answered individually: What did I do yesterday? What
am I going to do today? What help do I need?

Sprint Review : focused on inspecting the product increment/demo

Sprint Retrospective:
The 3 important questions of the meeting are:
1.What did the team do well?
2.What didn’t go well?
3.What can be improved?

Sprint: is the basic unit of work for a Scrum team. This is the main feature
that marks the difference between Scrum and other models for agile
development.
Scrum Artifacts

Product Backlog: is a list of new features, enhancements, bug fixes, tasks, or work
requirements needed to build a product. The product backlog is a “live” artifact in
that it is updated on-demand as new information is available.

Sprint backlog: The sprint backlog is a set of product backlog tasks that have been
promoted to be developed during the next product increment. Sprint backlogs are
created by the development teams to plan deliverables for future increments and detail
the work required to create the increment.

Product increment: A product increment is the customer deliverables that were produced by
completing product backlog tasks during a sprint. It also includes the increments of all
previous sprints.
Scrum charts
Burndown/up chart: A burn down chart is a run chart of outstanding work. It is
useful for predicting when all of the work will be completed.

Velocity: The velocity chart displays the average amount of work a scrum team completes during a sprint.
Thank you!