Software Engineering

Software Process

Faculty
Dr S Venu Gopal
Associate Professor
Department of CSE
 Today’s Session: Outlines
• What is Software Process
• Process framework Activities
• Umbrella Activities
• 7 Generic Principles
• Software Myths
• A Generic Process Model
• Process Assessment and Improvement

SOFTWARE ENGINEERING 2
 Software Process
What is a Process?
“ is a Collection of Activities, Actions, and Tasks are
performed to when the product is to be created’
It’s a broad Objective Set of tasks that A small, but well
produce major work defined objective
product
Ex: Communication Ex: Architectural Design Ex: Conducting Unit
with Customers Testing

SOFTWARE ENGINEERING 3
 Process framework Activities
 There are 5 (Five) Framework Activities
• To Gather Requirements
Communication

• “ Map” that is Software

Planning Project Plan

• Create a ‘Sketch” You will

Modeling understand the Big picture

• Code Generation (Manual or

Construction Automated Tool), and also
testing part

• Partial or Completed Product

Deployment delivered to Customer &
Collecting Feed Back

SOFTWARE ENGINEERING 4
 Process framework Activities
 With 5 (Five) Framework Activities , we have some

other umbrella activities

 Software project tracking and control
 Risk management
 Software quality assurance
 Technical reviews
 Measurement
 Software configuration management
 Reusability management
 Work product preparation and production
(such as models, documents, logs,
forms & Others)
SOFTWARE ENGINEERING 5
 Software Engineering Practice
 We have 5 (Five) Framework Activities and umbrella activities to sketch the
architecture for software engineering problem.

 How to does the practice of software engineering fit in? and you will
understand concepts and principles that apply to framework activities.

SOFTWARE ENGINEERING 6
 Software Engineering Practice
 We have 5 (Five) Framework Activities and umbrella activities to sketch the architecture
for software engineering problem.

 How to does the practice of software engineering fit in? and you will understand concepts
and principles that apply to framework activities.
 The Essence of Practice

 Understand the problem (Communication and analysis)

 Plan a solution (Modeling Solution)
 Carry out the Plan (Code Generation)
 Examine the Results for accuracy (Testing & Quality assurance)

SOFTWARE ENGINEERING 7
 A Generic Process Model
 The 5 framework activities are

Communication Planning Modeling Construction Deployment

in addition with Risk

Project Tracking
we have umbrella
Quality
activities thatTechnical
Configuration
are
& Controlling Management Assurance Management Reviews

But How “Process Flow” Executes within Framework

Activities

SOFTWARE ENGINEERING 8
“Process Flow”

SOFTWARE ENGINEERING 9
 “Process Flow”

Identifying a Task Set:

SOFTWARE ENGINEERING 10
 “Identifying a Task Set”
• Each software engineering action can be represented by a
number of different task sets
• For example: For a small, relatively simple project, the task set for
requirements gathering might look like this:
• 1. Make a list of stakeholders for the project.
• 2. Invite all stakeholders to an informal meeting.
• 3. Ask each stakeholder to make a list of features and functions
required.
• 4. Discuss requirements and build a final list.
• 5. Prioritize requirements.
• 6. Note areas of uncertainty.

SOFTWARE ENGINEERING 11
The Essence of Software Engineering Practice
 Understand the problem (Communication and
analysis)

SOFTWARE ENGINEERING 12
The Essence of Software Engineering Practice
 Plan a solution (Modeling Solution)

SOFTWARE ENGINEERING 13
The Essence of Software Engineering Practice
 Carry out the Plan (Code Generation)

 Examine the Results for accuracy (Testing &

Quality assurance)

SOFTWARE ENGINEERING 14
 Generic Principles
 These generic principles that focus on software
Engineering.

1. The Reason it All Exists

2. KISS (Keep It Simple, Stupid!)

3. Maintain the Vision

4. What you produce , others will consume.

5. Be open to the future

6. Plan ahead for Reuse

7. Think! Before you act.

SOFTWARE ENGINEERING 15
 7 Generic Principles
 1. The Reason it All Exists

“ Provide value to its user”

 2. KISS (Keep It Simple, Stupid!)

All Designs should be as

simple as possible,
but no simpler.

SOFTWARE ENGINEERING 16
 7 Generic Principles
 2. KISS (Keep It Simple, Stupid!)
Many educational sites Follow This Case Study #
Pattern

how I visually
educate users about
products they can
use when working from
home – from docking
stations to how to
maintain health while
working remotely for
weeks or months at a
time.
Case Study #2:
SOFTWARE ENGINEERING 17
 7 Generic Principles
 3. Maintain the Vision
“ A Clear vision is essential to the success of a software project”

 4. What you produce , others will consume.

SOFTWARE ENGINEERING 18
 7 Generic Principles
 5. Be open to the future

Notice the Changes

Adapt new Technologies
Be prepare for future problems

 6. Plan ahead for Reuse

Reuse saves time and effort
Reuse of Code and Design

SOFTWARE ENGINEERING 19
 7 Generic Principles
 7. Think!
Think
Results Before you Act
Side Effects

Customer Satisfaction

SOFTWARE ENGINEERING 20
 7 Generic Principles
 1. Provide value to its user

 2. KISS (Keep It Simple, Stupid!)

 3. Maintain the Vision

 4. What you produce , others will consume.

 5. Be open to the future

 6. Plan ahead for Reuse

 7. Think! Before you act.

SOFTWARE ENGINEERING 21
 Software Myths
 What is Myth?

“ false belief “

SOFTWARE ENGINEERING 22
 Software Myths

 Management Myths

 Customer Myths

 Practitioner’s Myths

SOFTWARE ENGINEERING 23
 Software Myths
 Management Myths
We have full of standards and procedures for building software
my Employees everything they need to know?

Reality ?
Management
Myths
Reality ?

If we get behind If I decide to out source

schedule, we can the software project to a
add more Reality ? third party, I can just
relax and let that firm
programmers and build it
SOFTWARE ENGINEERING 24
catch up
 Software Myths
• Customer Myths : a person, a technical group, a
marketing / sales department (Or) an outside company
A general statement of objectives is sufficient to
begin writing programs – We can fill in the detail
later

Reality ? Reality ?
Customer
Myths

Project requirements continually change, but

changes can be easily accommodated because
software is flexible
SOFTWARE ENGINEERING 25
 Software Myths
 Practitioner’s Myths: Reality ?
Once we write the Software engineering will make
program and get it to us create voluminous and
work our job is done unnecessary documentation
and will invariably slow us
down
Reality ? Practitioner’s
Myths

Reality ? Reality ?
Until I get the program The only deliverable
running – I have no way of work product for a
assessing its quality successful project is the
SOFTWARE ENGINEERING
working program 26
 A Generic Process Model
 What is a Process?
A Collection of work activities, actions, and tasks that
are performed when some work product is to be
created.
 Example:

SOFTWARE ENGINEERING 27
Process Assessment and Improvement
Why This?

 Existing s/w Process has no guarantee to delivered on time, and

meet the customer needs.
 It may exhibit technical characteristics

 In addition, the process itself can be assessed to ensure that it

meets a set of basic criteria , for a successful software
Engineering.

SOFTWARE ENGINEERING 28
Process Assessment and Improvement
 Different approaches to software process assessment and improvement have

been proposed over past few decades.

1. Standard CMMI Assessment Method for Process
Improvement (SCAMPI)
It’s a five (5) step process Assessment
1. initiating
2. Diagnosing
3. Establishing
4. Acting
5. Learning

SOFTWARE ENGINEERING 29
Process Assessment and Improvement

 CMMI Based Appraisal :

SOFTWARE ENGINEERING 30
Process Assessment and Improvement

 ISO 9001:2000 for Software

SOFTWARE ENGINEERING 31
 Problem Based Learning
 Clarify the evolving role of software?

 various characteristics of software?

Instructions to Student: “ follow any one”

 Prepare a short video (Less than or Equal to 30 Seconds)

 Prepare 10 Slides.

Note: Include Your Roll. No. , Name, Course Name, Date

“ Submit before 12PM today 08-07-2020 “

SOFTWARE ENGINEERING 32
SOFTWARE ENGINEERING 33