Evolution of software; Characteristics of software; Software applications; Components of software; Software myths; Software problems; Software reuse; Overview of risk management; Process visibility; Professional responsibility.

1. Chapter 1
Software & Software Engineering
1
Introduction to Software Engineering

2. What is Software?
2
The product that software professionals build and then support
over the long term.
Software encompasses: (1) instructions (computer programs)
that when executed provide desired features, function, and
performance; (2) data structures that enable the programs to
adequately store and manipulate information and (3)
documentation that describes the operation and use of the
programs.

3. Software products
• Generic products
– Stand-alone systems that are marketed and sold to
any customer who wishes to buy them.
– Examples – PC software such as editing, graphics
programs, project management tools; CAD software;
software for specific markets such as appointments
systems for dentists.
• Customized products
– Software that is commissioned by a specific customer
to meet their own needs.
– Examples – embedded control systems, air traffic
control software, traffic monitoring systems.
3

4. Why Software is Important?
• The economies of ALL developed nations are
dependent on software.
• More and more systems are software controlled (
transportation, medical, telecommunications,
military, industrial, entertainment,)
• Software engineering is concerned with theories,
methods and tools for professional software
development.
• Expenditure on software represents a
significant fraction in all developed countries.

5. 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.

6. Features of Software?
• Its characteristics that make it different from other things human being
build.
Features of such logical system:
• Software is developed or engineered, it is not manufactured in the
classical sense which has quality problem.
• Software doesn't "wear out.” but it deteriorates (due to change).
Hardware has bathtub curve of failure rate ( high failure rate in the beginning,
then drop to steady state, then cumulative effects of dust, vibration, abuse occurs).
• Although the industry is moving toward component-based
construction (e.g. standard screws and off-the-shelf integrated
circuits), most software continues to be custom-built. Modern reusable
components encapsulate data and processing into software parts to be
reused by different programs. E.g. graphical user interface, window,
pull-down menus in library etc.
6

7. Wear vs. Deterioration
7

8. Software Applications
• 1. System software: such as compilers, editors, file management utilities
• 2. Application software: stand-alone programs for specific needs.
• 3. Engineering/scientific software: Characterized by “number crunching”algorithms.
such as automotive stress analysis, molecular biology, orbital dynamics etc
• 4. Embedded software resides within a product or system. (key pad control of a
microwave oven, digital function of dashboard display in a car)
• 5. Product-line software focus on a limited marketplace to address mass consumer
market. (word processing, graphics, database management)
• 6. WebApps (Web applications) network centric software. As web 2.0 emerges, more
sophisticated computing environments is supported integrated with remote database
and business applications.
• 7. AI software uses non-numerical algorithm to solve complex problem. Robotics, expert
system, pattern recognition game playing
8

9. Overview of Risk Management:
• Risk Index: Generally risks are categorized into
two factors namely impact of risk events and
probability of occurrence. Risk index is the
multiplication of impact and probability of
occurrence. Risk index can be characterized as
high, medium, or low depending upon the
product of impact and occurrence. Risk index is
very important and necessary for prioritization of
risk
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009).
Slides copyright 2009 by Roger Pressman. 9

10. • Risk Assessment: Risk assessment is another
important case that integrates risk
management and risk analysis. There are
many risk assessment methodologies that
focus on different types of risks. Risk
assessment requires correct explanations of
the target system and all security features. It
is important that a risk referent levels like
performance, cost, support and schedule
must be defined properly for risk assessment
to be useful.
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009).
Slides copyright 2009 by Roger Pressman. 10

11. Software Risk Management:
• Risk Analysis: There are quite different types of risk
analysis that can be used. Basically, risk analysis is used to
identify the high risk elements of a project in software
engineering. Also, it provides ways of detailing the impact
of risk mitigation strategies. Risk analysis has also been
found to be most important in the software design phase to
evaluate criticality of the system, where risks are analyzed
and necessary counter measures are introduced. The main
purpose of risk analysis is to understand risks in better ways
and to verify and correct attributes. A successful risk
analysis includes important elements like problem
definition, problem formulation, data collection
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009).
Slides copyright 2009 by Roger Pressman. 11

12. Software—New Categories
• Open world computing—pervasive, ubiquitous, distributed computing due to
wireless networking. How to allow mobile devices, personal computer,
enterprise system to communicate across vast network.
• Netsourcing—the Web as a computing engine. How to architect simple and
sophisticated applications to target end-users worldwide.
• Open source—”free” source code open to the computing community (a
blessing, but also a potential curse!)
• Also … Data mining
– Grid computing
– Cognitive machines
– Software for nanotechnologies
These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides
copyright 2009 by Roger Pressman.
12

13. 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.
13

14. FAQ about software engineering
14
Question Answer
What is software? Computer programs, data structures and associated
documentation. Software products may be developed for
a particular customer or may be developed for a general
market.
What are the attributes of good software? Good software should deliver the required functionality
and performance to the user and should be
maintainable, dependable and usable.
What is software engineering? Software engineering is an engineering discipline that is
concerned with all aspects of software production.
What is the difference between software
engineering and computer science?
Computer science focuses on theory and fundamentals;
software engineering is concerned with the practicalities
of developing and delivering useful software.
What is the difference between software
engineering and system engineering?
System engineering is concerned with all aspects of
computer-based systems development including
hardware, software and process engineering. Software
engineering is part of this more general process.

15. Essential attributes of good software
15
Product characteristic Description
Maintainability Software should be written in such a way so that it can evolve to
meet the changing needs of customers. This is a critical attribute
because software change is an inevitable requirement of a
changing business environment.
Dependability and
security
Software dependability includes a range of characteristics
including reliability, security and safety. Dependable software
should not cause physical or economic damage in the event of
system failure. Malicious users should not be able to access or
damage the system.
Efficiency Software should not make wasteful use of system resources such
as memory and processor cycles. Efficiency therefore includes
responsiveness, processing time, memory utilisation, etc.
Acceptability Software must be acceptable to the type of users for which it is
designed. This means that it must be understandable, usable and
compatible with other systems that they use.

16. Important components of Software
Engineering are:
1. Software Development Life Cycle(SDLC)
2. Software Quality Assurance
3. Software project Management
4. Software Management
5. Computer Aided Software Engineering
(CASE)
These slides are designed to accompany
Software Engineering: A Practitioner’s
Approach, 7/e (McGraw-Hill 2009). Slides
16

17. Management Myths [Pressman]
• We already have standards and procedures for building
software; isn’t that enough?
– How widely used is it?
– How relevant to the team?
– How useful to the project?
• If we’re behind schedule, we’ll just add more programmers to
catch up
– “Adding people to a late project makes it later” [Brooks]
– Ramp-up time
– Interference
• If I outsource a project, I can just relax
– Management issues are much more difficult, and if not understood,
will sink the project

18. Customer Myths [Pressman]
• A general statement of work is sufficient to kick
off the project, and we can fill in the details later
– Loosey-goosey
– Nonlinear effect of added requirements: O(n) added
text does not make for O(n) added work
• Requirements can change, and that’s OK because
software is so flexible
– See above
– Most software project failures can be traced to
inadequacy of requirement specifications

19. Software Engineers’ Myths [Pressman]
• Once the program is written, I’m done
– Between 60-80% of effort expended after delivery
• Until the program is written, quality is uncertain
– Formal design reviews
– Formal code reviews
– Test-first approaches
– Prototyping to verify design and structure
– Prototyping to validate requirements
• The only deliverable is the program itself
– Lots of documentation: installation guides, usage guides,
maintenance guides, API defintions and examples

20. Software Engineers’ Myths [Pressman]
• Documentation is Software-Engineering busy
work
– Focus is on quality, not quantity
– Documentation can be hard for engineers to
write, just as C++ may be difficult for poets.
– Conserve energy: documented code can serve as
a basis for useful documentation
• JavaDoc
• Doxygen

21. The Essence of Practice
(Software Problems)
• How does the practice of software engineering
fit in the process activities mentioned above?
Namely, communication, planning, modeling,
construction and deployment.
• George Polya outlines the essence of problem
solving, suggests:
1. Understand the problem (communication and
analysis).
2. Plan a solution (modeling and software design).
3. Carry out the plan (code generation).
4. Examine the result for accuracy (testing and
quality assurance).
21

22. Understand the Problem
• Who has a stake in the solution to the
problem? That is, who are the stakeholders?
• What are the unknowns? What data,
functions, and features are required to
properly solve the problem?
• Can the problem be compartmentalized? Is it
possible to represent smaller problems that
may be easier to understand?
• Can the problem be represented graphically?
Can an analysis model be created?
22

23. Professional Visibility
1. Confidentiality: You should normally respect the confidentiality of
your employers or clients irrespective of whether a formal
confidentiality agreement has been signed.
2. Competence: You should not misrepresent your level of
competence. You should not be knowingly accept work that is
outside your computer.
3. Intellectual property rights: You should be aware of local laws
governing the use of intellectual property such as patents and
copyrights. You should be careful to ensure that the intellectual
property of employers and clients is protected.
4. Computer misuse. You should not use your technical skills to
misuse other people computers. Computer misuse ranges from
relatively trivial to extremely serious.

24. Software reuse
• In most engineering disciplines, systems are
designed by composing existing components
that have been used in other systems
• Software engineering has been more focused
on original development but it is now
recognised that to achieve better software,
more quickly and at lower cost, we need to
adopt a design process that is based on
systematic reuse

25. Benefits of reuse
• Increased reliability
– Components exercised in working systems
• Reduced process risk
– Less uncertainty in development costs
• Effective use of specialists
– Reuse components instead of people
• Standards compliance
– Embed standards in reusable components
• Accelerated development
– Avoid original development and hence speed-up
production

26. Process Visibility
1. Maintainability: Software should be written in such a way that is
may evolve to meet the changing needs of customers. This is a
critical visibility because software change is an inevitable
consequence of changing business environment.
2. Dependability: Software dependability has a range of
characteristics, including reliability , security & safety. Dependable
software should not cause physical or economic damage in the
event of system failure.
3. Efficiency: Software should not make wasteful use of system
resources such as memory & processor cycles. Efficiency therefore
includes responsiveness, processing time, memory utilization etc.
4. Usability: Software must be usable, without undue effort, by the
type of user for whom it is designed. This means that it should
have an appropriate user interface & adequate documentation.