Chapter: Introduction To Software Engineering
Chapter: Introduction To Software Engineering
Chapter: Introduction To Software Engineering
Software Engineering
Chapter : Topic Covered
Evolving Role of Software
Hardware vs. Software
Software characteristics
Changing nature of software
Evolution of Software
Software Myths
Evolving Role of Software
Software is a product
Transforms information - produces, manages, acquires,
modifies, displays, or transmits information
Delivers computing potential of hardware and networks
Software is a vehicle for delivering a product
Controls other programs (operating system)
Effects communications (networking software)
Helps build other software (software tools &
environments)
What is Software ?
Software can define as:
Instructions when executed provide desire features, function &
performance.
Data structure enable the programs to adequately manipulate
information.
Documents describe the operation and use of the programs.
Software products may be developed for a particular customer or may be
developed for a general market.
Software products may be
Generic - developed to be sold to a range of different
customers e.g. PC software such as Excel or Word.
Bespoke (custom) - developed for a single customer
according to their specification.
Hardware vs. Software
Hardware Software
Application Software :
Application software consists of standalone programs that solve a specific
business need.
Application software is used to control the business function in real-time.
Myth1: Once we write the program and get it to work, our job
is done.
Reality: Someone once said that "the sooner you begin
'writing code', the longer it'll take you to get done." Industry
data indicate that between 60 and 80 percent of all effort
expended on software will be expended after it is delivered to
the customer for the first time.
Myth2: Until I get the program "running" I have no way of
assessing its quality.
Reality: One of the most effective software quality assurance
mechanisms can be applied from the inception of a projectthe
formal technical review.
Myth3: The only deliverable work product for a successful
project is the working program.
Practitioner's myths
Reality: A working program is only one part of a
software configuration that includes many
elements. Documentation provides a
foundation for successful engineering and,
more important, guidance for software support.
Myth4 : Software engineering will make us create
voluminous and unnecessary documentation
and will invariably slow us down.
Reality: Software engineering is not about creating
documents. It is about creating quality. Better
quality leads to reduced rework. And reduced
rework results in faster delivery times.