Scribd
Upload
319 views17 pages

Software Engineering Myths and Paradigms

This document discusses software engineering myths and paradigms. It describes myths that managers, customers, and practitioners believe about software development. Common management myths include thinking that standards fully define the development process and that outsourcing removes the need to manage projects. Customer myths involve underestimating requirements definition and overestimating flexibility to change requirements. Practitioner myths involve thinking delivery is the only product and quality cannot be assessed early. The document also outlines popular software development paradigms, including the waterfall, spiral, incremental, and agile models. It describes the phases and characteristics of each paradigm.

Uploaded by

MAMO EMIRU
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
319 views17 pages

Software Engineering Myths and Paradigms

This document discusses software engineering myths and paradigms. It describes myths that managers, customers, and practitioners believe about software development. Common management myths include thinking that standards fully define the development process and that outsourcing removes the need to manage projects. Customer myths involve underestimating requirements definition and overestimating flexibility to change requirements. Practitioner myths involve thinking delivery is the only product and quality cannot be assessed early. The document also outlines popular software development paradigms, including the waterfall, spiral, incremental, and agile models. It describes the phases and characteristics of each paradigm.

Uploaded by

MAMO EMIRU
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

*SOFTWARE

ENGINEERING
MYTHS AND
PARADIGMS
SWE myths and paradigms slide 1
* 1. SOFTWARE
ENGINEERING MYTHS
MYTHS:
Something that many people believe but that does not exist or is
not true.
Sw myths: Beliefs about software and the process used to build
it.

Devided in to 3
1. Management myths
2. Costumer myths
3. Practitioner’s myths
SWE myths and paradigms slide 2
* 1.1.managementMyths

• Managers with software responsibility


• Managers in most disciplines
• Managers are often under pressure
• to maintain budgets,
• keep schedules on time,
• and improve quality.
• Software manager often grasps at belief in a software myth.

SWE myths and paradigms slide 3


*
Myth1: We already have a book that's full of standards
and procedures for building software, it does provide my
people with everything they need to know.
Reality: The book of standards may very well exist. But,
• but is it used?
• Are software practitioners aware of its existence?
• Does it reflect modern software engineering practice?
• Is it complete? Is it adaptable?
• Is it stream lined to improve time-to-delivery while
still maintaining a focus on quality?
• the answer to all of these questions is “no.”

SWE myths and paradigms slide 4


*
Myth2: If I decide to outsource the software
project to a third party, I can just relax and
let that firm build it.
Reality: If an organization does not
understand how to manage and control
software projects internally, it will invariably
struggle when it outsources software projects.

SWE myths and paradigms slide 5


* 1.2. Customer myths

A customer who requests computer software may


be
• a person at the next desk,
• the marketing/sales department,
• or an outside company that has requested
software under contract.
The customer believes myths about software. b/c
SW managers and practitioners do little to correct
misinformation.
Myths lead to false expectations (by the customer)
and, ultimately, dissatisfaction with the developer.

SWE myths and paradigms slide 6


* •Myth1: A general statement of objectives is
sufficient to begin writing programs.
•Reality: A poor up-front definition is the major
cause of failed software efforts.
A formal and detailed description of the
information domain, function, behavior,
performance, interfaces, design
constraints, and validation criteria is
essential.

SWE myths and paradigms slide 7


* •Myth2: Project requirements continually
change, but
change can be easily accommodated because
software is flexible.
Reality: It is true that software requirements
change, but the impact of change varies with
the time at which it is introduced.
when requested, the cost impact is
relatively small.
However, as time passes, the cost
impact grows rapidly

SWE myths and paradigms slide 8


* 1.3. Practitioner’s myths
Myths that are still believed by software practitioners
have been fostered by over 50 years of programming
culture.
During the early days, programming was viewed as an
art form. Old ways and attitudes die hard.

SWE myths and paradigms slide 9


*
•Myth1: The only deliverable work product for a
successful project is the working program.

•Reality: A working program is only one part of a


software configuration that includes many
elements.
•Myth2: Until I get the program "running" I have no
way of assessing its quality.

•Reality:Oneof the most effective software quality


assurance mechanisms can be applied from the
inception of a project—the formal technical review.
SWE myths and paradigms slide 10
* 2. SOFTWARE
Paradigms:
PARADIGMS
A model or example for something that may be copied.
• Also known as Software process models or Software
Development life cycle.
The Software Engineering Paradigms(Process Models)
Devided in to 4
1. Waterfall Model
2. The Spiral Model
3. Incremental Process Model
4. Agile Development Model
SWE myths and paradigms slide 11
* 2.1. Waterfall Model
• known as the linear sequential model and as classic life cycle
model.
• developed in 1970
• It is the oldest and most commonly used software engineering.
• make the software development process more structured.

SWE myths and paradigms slide 12


*

1. Requirements Analysis This answers the ‘What is the


software system to be developed’ question.
2. Design This answers the ‘How is the software system
will be developed’ question.
3. Coding Involves the writing of the code. The actual
design is turned into a set of programs.
4. Testing The code that is developed in the
implementation phase is tested during the testing
phase.
5. Delivery In this phase the system is made operational.

SWE myths and paradigms slide 13


* 2.2 The Spiral Model

• developed by Barry Boehm in 1989


the same steps (requirements analysis, planning, design,
coding, testing, and delivery) as the waterfall
• requirements are not complete at project start.
The steps go through a cyclical motion as requirements
and design.

SWE myths and paradigms slide 14


* 2.3 Incremental Process Model

• uses the same phases as the waterfall


• requirements are not complete at project start
• smaller than the waterfall phases
• They do not need to wait for the whole system to be
completed

SWE myths and paradigms slide 15


* 2.4 Agile Development Model

• includes only 4 phases


1. planning
2. design
3. coding
4. testing.
promotes development iterations throughout the life-cycle of the
project.

SWE myths and paradigms slide 16


*Thanks
For your
attention!!!

SWE myths and paradigms slide 17

You might also like