Software

Engineering

Lecture 3: Software Cost and

Manuals

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

2
 !"#$%&'#()$*+,%'-#'.//012+$1(3'
#()$*+,%

1. System software:
Designed to run a computer's hardware and
application programs. such as compilers,
editors, file management utilities , operating
system

2. Application software:
Applications software (also called end-user
programs) include such things as database
programs, word processors, Web browsers
and spreadsheets. stand-alone programs for
specific needs
 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.

• 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, Hospital
management system.

4
 Legacy Software
• legacy system is an old method or technology. Must be updated
to meet needs.
• Implies that the system is out of date or in need of replacement.

Why must it change?

– software must be adapted to meet the needs of new computing
environments or technology.
– software must be enhanced to implement new business
requirements.
– software must be extended to make it interoperable with other
more modern systems or databases.

Section 1.1.3 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book
5
 Legacy Software

Section 1.1.3 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book
6
 Software Components

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;

(1) data structures that enable the programs to adequately store and
manipulate information and

(1) documentation that describes the operation and use of the programs
7
 Program Vs. Software
Documentation of any fact of the program,
Operating procedures used to set up & operate the Software system.

Programs

Operating
Documentation Procedures

Software= Programs + Documentation + Operating Procedures

Documentation Manuals Formal Specification
Analysis/ Context Diagram
Specification
Data Flow Diagram

Flow Charts

Design
ER Diagram

Documentation
Manuals Source Code
Listings
Implementation
Cross- Reference
Listings

Test Data
Testing
Test Results
 4(25&%3$+$1(3'6+35+0#

• Operating procedures consist of instructions to set up & use the

software system & instructions on how to react to system failure.
• List of operating procedures is:
System Overview
Beginner’s Guide Tutorial
User Manuals

Reference Guide
Documentation
Manuals Installation
Guide
Operational
Manuals
System
Administration
Guide
Examples
Data Flow Diagram

11
Software Engineering; A Layered Technology

Quality which provides a continuous process improvement culture.

Process layer is the foundation that defines a framework with activities for effective delivery
of software engineering technology. How technical methods are applied, work products such
as models, documents, data, reports, forms, etc. are produced,
Method provides technical how-to’s for building software. It encompasses many tasks
including communication, requirement analysis, design modeling, program construction,
testing and support.
Tools provide automated or semi-automated support for the process and methods.

Figure 1.3 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book
12
 A Process Framework

Process Model

1. Framework activities:
Framework, encompassing five activities— communication, planning,
modeling, construction, and deployment

1. Umbrella Activities
if available you are safe, if not even than you don’t get in trouble.

Any standard software process model would primarily consist of two types of
activities: A set of framework activities, which are always applicable, regardless of
the project type, and a set of umbrella activities, which are the non SDLC
activities

Section 1. 4 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book

13
Framework Activities

1. Communication
2. Planning
3. Modeling
– Analysis of requirements
– Design
4. Construction
– Code generation
– Testing
5. Deployment

Section 1. 4 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book

14
Umbrella Activities

• Software project management

• Formal technical reviews
• Software quality assurance
• Software configuration management
• Reusability management
• Risk management

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

16
 Software Myths

Erroneous beliefs about software and the process that is

used to build it - can often mislead to serious problems.

• Myth 1: Once we write the program and get it to work, our job is done.
• Reality: the sooner you begin writing code, the longer it will take you to get done.
• 60% to 80% of all efforts are spent after software is delivered to the customer for the first
time.

• Myth 2: Until I get the program running, I have no way of assessing its quality.
• Reality: technical review are a quality filter that can be used to find certain classes of software
defects from the inception of a project.

• Myth 3: software engineering will make us create unnecessary documentation and will
invariably slow us down.
• Reality: it is not about creating documents. It is about creating a quality product. Better quality
leads to a reduced rework. Reduced work results in faster delivery times.
17
Section 1. 6 , Software Engineering A practitioner’s approach 7th ed. Roger S. Pressman Book
FAQ about software engineering

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 and easily 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 Computer science focuses on theory and fundamentals;
engineering and computer science? software engineering is concerned with the practicalities
of developing and delivering useful software.
What is the difference between software System engineering is concerned with all aspects of
engineering and system engineering? computer-based systems development including
hardware, software and process engineering. Software
engineering is part of this more general process.

18
Essential attributes of good software

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 Software dependability includes a range of characteristics
security 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.

19
 Revision Questions
Q01: Risk Assessment is part of software
engineering

A. True
B. False
C. Can't say
D. Non of the above

20
Q02: In the six phases of the classical SW life-
cycle Design comes before testing and analysis.

A. True
B. False

21
Q03: Which of the following is an Umbrella
activity

A. Requirement analysis
B. Reusability management
C. Testing
D. System Building

22
Q04: Installation guide of a software will fall
under the category of

A. Operations manual
B. User manual
C. Testing Manual

23