Conventional and Object Oriented Software Engineering

1
Presented by
Siva Ramakrishna Sani
(2301707301)
Research Scholar
(part time external)
CONVENTIONAL AND OBJECT ORIENTED
SOFTWARE ENGINEERING
PUDUCHERRY TECHNOLOGICAL UNIVERSITY
DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING
Under the Supervision of
Dr. N. Sreenath,
Professor,
Dept. of CSE,
PTU.

CONTENTS TO BE DISCUSSED
1. What is Software Engineering?
2. Importance of SE
3. Conventional SE
4. Principles of Conventional SE
5. Introduction to Object Oriented SE
6. Principles of Object Oriented SE
7. Benefits of Object Oriented SE

WHAT IS SOFTWARE ENGINEERING?
 Software Engineering provides a standard procedure to
design and develop a software.
(OR)
 Software Engineering is the process of designing,
developing, testing, and maintaining software.
 It is a systematic and disciplined approach to create high-
quality, reliable, and maintainable software.

IMPORTANCE OF SOFTWARE ENGINEERING

CONVENTIONAL SOFTWARE ENGINEERING
 Conventional software engineering refers to the
traditional and widely accepted practices,
methodologies, and approaches used in the
development of software systems.
 It encompasses a set of well-established principles,
processes, and techniques that have evolved over time
to address the challenges of building reliable, scalable,
and maintainable software.
 Conventional software engineering follows a structured
approach to software development known as the
Software Development Life Cycle.

SOFTWARE DEVELOPMENT LIFE CYCLE(SDLC)

WATERFALL MODEL
o The Waterfall Model is one of the earliest and most
straightforward SDLC models.
o It follows a linear and sequential flow, with each phase
building upon the outputs of the previous one.
o This model is well-suited for projects with clear and well-
defined requirements.
Advantages
 This model is simple to implement also the number of
resources that are required for it is minimal.
 The requirements are simple and explicitly declared; they
remain unchanged during the entire project development.
 The start and end points for each phase is fixed, which makes
it easy to cover progress.

 The release date for the complete product, as well as its
final cost, can be determined before development.
 It gives easy to control and clarity for the customer due to a
strict reporting system.
Disadvantages
 In this model, the risk factor is higher, so this model is not
suitable for more significant and complex projects.
 This model cannot accept the changes in requirements
during development.
 It becomes tough to go back to the phase. For example, if
the application has now shifted to the coding phase, and
there is a change in requirement, It becomes tough to go
back and change it.
 Since the testing done at a later stage, it does not allow
identifying the challenges and risks in the earlier phase, so
the risk reduction strategy is difficult to prepare.

“The success rate for software projects is very low”.
They are summarized as follows:
 Software development is still highly unpredictable. Only
10% of software projects are delivered successfully
within initial budget and scheduled time.
 Management discipline is more differentiator in success
or failure than are technology advances.
 The level of software scrap and rework is indicative of an
immature process.

PRINCIPLES OF CONVENTIONAL SOFTWARE
ENGINEERING
Conventional software engineering is guided by several
principles that form the foundation for the development
of reliable and high-quality software.
o Make quality
o High quality software is possible
o Give products to customer early
o Determine the problem before writing the requirements.
o Evaluate design alternatives
o Use an appropriate process model
o Use different language for different phases.:
o Minimize intellectual distance.

o Inspect Code
o Good management is more important than good
technique.
o Understand the customers priorities.
o Design without documentation is not the design
o Don’t test your own software
o Analyze causes for errors

OBJECT ORIENTED SOFTWARE ENGINEERING
 Object-oriented software engineering (OOSE) is an
approach to software design and development that is
based on the principles of object-oriented programming
(OOP).
 In the object-oriented design approach, the system is
considered a collection of objects (i.e., entities). An
object-oriented design is a model that works as a plan
for software creation.
 Object Oriented Design (OOD) in software engineering
focuses on improving the quality, usability, and
productivity of system analysis and design.

PRINCIPLES OF OBJECT-ORIENTED DESIGN
Object-oriented software engineering (OOSE) is an
approach to software design and development that is
based on the principles of object-oriented programming
(OOP).
o Object
o Class
o Abstraction
o Encapsulation
o Inheritance
o Polymorphism
o Modularity
o Dynamic Binding

BENEFITS OF OBJECT-ORIENTED DESIGN
 Reusability of code
 Modularity
 Flexibility and scalability
 Improved maintainability
 Reduced complexity

REUSABILITY OF CODE
 Code reuse can greatly optimize the development
process of applications and result in increased
productivity.
 It improves code quality, saves time, reduces
development risks, prevents code bloat, optimizes the
overall cost, and resolves the technical challenges
associated with software products.
 Thе inheritance propеrty in object-oriented dеsign
providеs reusability of codе by dеfining a nеw class
from thе already еxisting class.

Modularity
 In object-oriented dеsign, modularity is referred to
breaking down a problеm (program) into a sеt of
modulеs so as to rеducе thе overall complexity of thе
problem.
Flexibility and scalability
o Object-oriented dеsign hеlps developers dеsign
software systems that arе flеxiblе еnough to adapt for
any codе modification and to changing businеss
rеquirеmеnts.
o Inheritance and polymorphism provide flеxibility for your
codеbasе.

Improved maintainability
Object-oriented design promotes modular and reusable
design that helps easier code maintenance and update
over time.
Reduced complexity
Object-oriented design breaks down complex systems
into more manageable components ensuring easier
maintenance, code reuse, and efficient development.

 In Object-Oriented Software Engineering (OOSE),
various software development models can be applied.
 The choice of a specific model depends on the project's
requirements, size, and complexity.
Some of models are:
o Waterfall Model with Object-Oriented Concepts
o Iterative and Incremental Development
o Unified Process (UP)
o Agile Development
o Feature-Driven Development (FDD)
o Model-Driven Development (MDD)
o Component-Based Development (CBD)
o Spiral Model with Object-Oriented Concepts

Conventional and Object Oriented Software Engineering

Conventional and Object Oriented Software Engineering

More Related Content

What's hot (20)

Similar to Conventional and Object Oriented Software Engineering (20)

Recently uploaded (20)

Conventional and Object Oriented Software Engineering