DEPARTMENT OF COMPUTER

TECHNOLOGY

VII-SEMESTER
Session: 2014-15
SOFTWARE ENGINEERING

UNIT NO.1
Introduction to Software Engineering

Mr. B. L. Parne
C. Tech. Dept.
1
 UNIT 1:- SYLLABUS

1 . Introduction

2 A Generic View of Process

3 Process Models

4 Requirement Engineering Tasks

5 Developing Use Case

6 Developing Analysis Model

DTEL 2
 UNIT-1 SPECIFIC OBJECTIVE / COURSE
OUTCOME

The student will be able to:

1 Understand the Different Software Process Models.

2 Understand the Concepts of Requirement Engineering.

DTEL 3
 Introduction
Adoption of Software Engineering Concepts will
give Solution to:
Why does it take so long to get software finished?
Why are development costs so high?
Why cant we find all errors before we give the software to
our customers?
Why do we spend so much time and effort maintaining
existing programs?
Why do we continue to have difficulty in measuring progress
as software is being developed and maintained? 4

DTEL 4
 Introduction

Software??
Characteristics of software
Software Applications
Software Engineering- A Layered Technology

Refer Content of Practical-1

DTEL 5
 Introduction Software Myths :

Software Myths beliefs about software and the

process used to build it.
Management Myths:
We already have a book thats full of standards and
procedures for building software. Wont that provide my
people with everything they need to know?
If we get behind schedule, we can add more
programmers and catch up.
If I decide to outsource the software project to a third
party, I can just relax and let that firm build it. 6

DTEL 6
 Introduction Software Myths :

Customer Myths:
A general statement of objective is sufficient to

begin writing programs we can fill in the details

later.
Project requirements continually change, but
change can easily accommodated because
software is flexible.
7

DTEL 7
 Introduction Software Myths :

Practitioners Myths:
Once we write the program and get it to work, our job is
done.
Until I get the program running, I have no way of assessing
its quality.
The only deliverable work product for a successful project
is the working program.
Software engineering will make us create voluminous and
unnecessary documentation and will invariably slow us
8
down.
DTEL 8
DEPARTMENT OF COMPUTER
TECHNOLOGY

VII-SEMESTER
Session: 2014-15
SOFTWARE ENGINEERING

UNIT NO.1
A Generic View of Process

9
 Introduction Fritz Bauer Definition of S. E. :

Software Engineering :
Software engineering is the establishment and use of
sound engineering principles in order to obtain
economically software that is reliable and works
efficiently on real machines.

10

DTEL 10
 Introduction IEEE Definition of S. E. :

Software Engineering :
The application of systematic, disciplined,
quantifiable approach to the development, operation,
and maintenance of software i.e. application of
engineering to software.
The study of approaches as above.

11

DTEL 11
 Introduction Software Engineering Layers :

Tools
Methods
Process Model
A quality focus

12

DTEL 12
 Process :

A software process is define as a framework for the task that are

required to build high quality software.
A process covers all activities starting from product inception
through delivery and retirement.
The software life cycle can be considered as the business process
for software development.
Process defines a framework for a set of key process areas
(KPAs) that must be established for effective delivery of software
engineering technology.
13

DTEL 13
 Methods :

Software engineering methods provide solution to the

technical how's for building software.
Methods encompass a broad array of tasks that include
requirements analysis, design, program construction,
testing, and support.
Include modeling activities and other descriptive
techniques.
14

DTEL 14
 Tools :

Software engineering tools provide automated or semi-

automated support for the process and the methods.
Tools are integrated so that information created by one tool can
be used by another.
A system for the support of software development, called
computer-aided software engineering, is established.
CASE combines software, hardware, and a software
engineering database to create a software engineering
environment.
15

DTEL 15
A Process Framework :

Establishes the foundation for a complete software

process by identifying a framework activities that are
applicable to all software projects, regardless of their
size or complexity.
In addition, the process framework encompasses a
set of umbrella activities that are applicable across
the entire software process.

16

DTEL 16
Generic Process Framework Activities :

Communication

Planning

Modeling

Construction

Deployment

17

DTEL 17
Umbrella Activities :

Umbrella activities occur throughout the software

process and focus primarily on project
management and tracking and control.

Software project tracking and control

Risk Management

Software Quality Assurance

Formal Technical reviews

18

DTEL 18
Umbrella Activities :

Continued..

Measurement

Software Configuration Management

Reusability Management

Work Product Preparation and production

19

DTEL 19
DEPARTMENT OF COMPUTER
TECHNOLOGY

VII-SEMESTER
Session: 2014-15
SOFTWARE ENGINEERING

UNIT NO.1
Prescriptive Process Models

20
 Introduction

Prescriptive Process Model

Attempt to organize the software life cycle by
defining activities involved in software
production
order of activities and their relationships
Goals of a software process
standardization, predictability, productivity, high
product quality, ability to plan time and budget
requirements
21

DTEL 21
 Introduction Code and Fix

The earliest approach

Write code
Fix it to eliminate any errors that have been
detected, to enhance existing functionality, or
to add new features.
Source of difficulties and deficiencies
Impossible to predict
Impossible to manage
22

DTEL 22
Process as Black Box

Informal
Requirements
Process

Product

Quality?
Uncertain /
Incomplete
requirement
In the beginning
23

DTEL 23
Process as Black Box Problems :

The assumption is that requirements can be

fully understood prior to development
Interaction with the customer occurs only at
the beginning (requirements) and end (after
delivery)
Unfortunately the assumption almost never
holds
24

DTEL 24
Process as a White Box

Informal
Requirements
Process

Product

feedback

25

DTEL 25
Process as a White Box Advantages:

Reduce risks by improving visibility

Allow project changes as the project
progresses
Based on feedback from the customer

26

DTEL 26
Prescriptive Process Model

Prescriptive process models define a distinct

set of activities, actions, tasks, milestones,
and work products that are required to
engineer high quality software.
These process models are not perfect, but
they do provide a useful roadmap for software
engineering work.
27

DTEL 27
The Waterfall Model :

The classical waterfall model is intuitively the

most obvious way to develop software.
It begins with customer specification of
requirements and progresses through Planning,
modeling, construction, and deployment.
The all other life cycle models are in some way or
other based on the classical waterfall model.
28

DTEL 28
The Waterfall Model :

29

DTEL 29
 THANK YOU

DTEL 30
 References Books:
Software Engineering A Practitioners Approach
(Sixth Edition) by Roger S. Pressman McGraw Hill.

References Web:
http://nptel.iitm.ac.in/courses/Webcoursecontents/IIT%20
Kharagpur/Soft%20Engg/New_index1.html
http://nptel.iitm.ac.in/courses/106101061/

DTEL 31