Week 1

Software Engineering
3EC32D202 (2021 – 2022, EVEN)

Course Coordinator
Dr. Akash Mecwan (PH. D., RF VLSI Design)
Assistant Professor, EC, IT, NU (D – 201)
Email: akash.mecwan@nirmauni.ac.in
Site: https://sites.google.com/nirmauni.ac.in/akash-mecwan/dr-akash-i-mecwan
08-03-2022 SOFTWARE ENGINEERING_CHAPTER 1

Course Outcomes
After successful completion of this course, students will be able to
1. Propose the use of software model and understand the software engineering
process in terms of requirements, design, and implantation for given applications.
2. Apply software engineering process to an embedded software project.
3. Produce software design based on requirements and conduct verification, validation
and documentation.

Teaching and Evaluation Scheme
Course
Code
Course
Name
Continuous Evaluation Scheme (CE) SEE
Test Special Assignment SEE Exam
No. Wt No. Wt Wt
3EC32D202 Software
Engineering
2 0.7 1 0.3 1
0.6 0.4
Credit Details :
L T P C
3 – – 3

Course Contents
 Introduction
 Project Management
 Design Concept and Methods
 Change Request Management
 Verification and Validation
 CASE Tool
 Maintenance and Evolution

Suggested Readings
ROGER S. PRESSMAN, SOFTWARE
ENGINEERING, MCGRAW-HILL INTERNATIONAL
IAN SOMMERVILLE, SOFTWARE
ENGINEERING, ADDISON WESLEY

Chapter - 1
INTRODUCTION

Software Engineering
What are your expectations
from the subject

Why Software Engineering?
What do you think??

Outline Lecture 1
Category of Software
Challenges in Software Design
Failure of Software
Reasons for Failures

Software Categories
Software
Simple/
Complex
Internal/
Public
Single Function/
Enterprise wide
Local/
Distributed
Batch/
Real time
Informational/
Mission Critical

Challenges in Software Design
 Effort Intensive
 High Cost
 Long Development time
 Changing needs or user
 High risk of failures

Failures in Software
Which software is considered successful???
 Development Completed
 It is useful
 It is used

Failures in Software
 Schedule missed
 Cost overrun
 Does not solve the problem
 Poor quality

Reasons for failure (Adhoc Development)
 Unplanned Development: No milestones defined
 Deliverables not identified
 Poor understanding of requirements
 No control or review
 Technical incompetency of developer
 Poor understanding of cost and efforts by designers or users

Chapter - 1
INTRODUCTION (LECTURE 2)

Summary of Lecture 1
 Course introduction, teaching and evaluation scheme
 Why software engineering?
 Categories of Software
 What is a successful software?
 When a software is called failure?
 Reasons for failure of the software

Outline
 Software Project Engineering Approach
 Software Developer Role
 Process of Software Development
 Process Flow
 Step in a Process
 Waterfall Model

Engineering Projects
 Specifications
 Cost Effectiveness
 Quality
 Repeatable
 Predictable

Engineering Approach to Software
Development
 Estimation of Cost and efforts
 Plan and schedule of work
 Involvement of user
 Identifying stages in development
 Define clear milestones
 Review of work and quality
 Define Deliverables
 Plan extensive testing

Software Developer
 Dealing with users
 Dealing with technical teams
 Dealing with management

Software Process
 Process consists of steps to be follow in a specific order
to complete a task
 Software process deals with both technical and
management issues
 There may be multiple processes involved in a software
project

Software Process

Process Flow

Process Flow (Cont…)

Chapter - 1
INTRODUCTION (LECTURE 3)

Summary of Lecture 2
 Software Project Engineering Approach
 Software Developer Role
 Process of Software Development
 Process Flow

Outline
 Types of Process in Software Development
 Step in a Process
 Waterfall Model
 Incremental Model

Software Process (Cont…)
 Development Process
 Management Process
 Change Process
 Configuration Process
 Process of managing the above processes

Steps in a Process
 Each step must have well defined objectives
 There should be people available with specific skill sets
 Specific inputs and outputs must be well defined
 Entry and exit of a step must be well defined
 Uses specific tools, techniques, guidelines and conventions

A Step in a Process (Cont…)
 A step must be executed as per the
plan that specifies schedule, resource
requirement, efforts require and
constraint if any
 A step must produce information that
can be reviewed
 A step ends in verification of the
outcomes and corrective measures

Waterfall Model

V - Model

Drawbacks of Waterfall Model
 Real project does not follow the sequential flow
 Changes may cause confusion as the design progresses if iterations are involved
 Difficult for customer to define all the requirement specifically
 Difficult to accommodate uncertainty and immediate expectations from customer
 Designer and customer have to have patience.
 Immediate output will not be available. If the final output is not proper the entire
designing has to be repeated after review.

Week 1

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Week 1

Similar to Week 1 (20)

Recently uploaded

Recently uploaded (20)

Week 1