CS101 Introduction to Computing
Lecture 20
SW Development Methodology
1
Docsity.com
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Software Development Methodology and Life-Cycle, Slides of Introduction to Computing
This document, part of the cs101 introduction to computing course, discusses the various phases of the software development process for systems of reasonable complexity. It presents the software life-cycle, a sequence of phases a software goes through from the concept to decommissioning, and the 'waterfall' model. Key issues such as the customer's lack of knowledge about requirements and lag are also addressed.
Typology: Slides
2011/2012
1 / 28
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Software Development Methodology and Life-Cycle and more Slides Introduction to Computing in PDF only on Docsity!
CS101 Introduction to Computing
Lecture 20
SW Development Methodology
During the last lecture …
- We discussed the role of programming languages
in computing
- We also discussed the differences among low- &
high-level, interpreted & compiled, and
structured & object-oriented programming
languages
- We also discussed the object-oriented and the
structured methodologies for SW design 2
Today’s Lecture
- Development process of reasonably complex SW
systems does not consist of “coding” only
- We will become familiar with the various phases
of the process that developers follow to develop
SW systems of reasonable complexity
SW Life-Cycle?
A Case in Point
- I didn’t discuss with the customer the specs of the HW & OS before developing a particular e-commerce SW
- I wrote it for the HW/OS that was easily available to me
- Unfortunately that HW/OS combination differed from what was easily available to the client
- Result: Huge amount of rework. Higher cost. Delayed delivery. Lower quality.
- Therefore, now before designing a SW system, I first write down the installation manual, and get it OK’d by the customer. I do the same with the Operation & Maintenance manual as well. (^) Docsity.com^7
Let us now take a look at a very simple SW life-
cycle
That was a very simple view
Now we look at a more detailed view of the life-
cycle for a SW system of a reasonable size
11
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
13
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
Concept: What needs
to be done?
Feasibility: Preliminary
exploration of possible
solutions, technologies,
suppliers
14
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
The user
documents as
much as he knows
about the job the
system must do
16
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
Detailed plan
specifying the
required
resources and
expected
deliverables
17
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
Architecture: Decompose the problem into
subsystems and define their relationships
Detailed Design: Decompose further such that
one person can manage each sub-subsystem
19
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement
Bring the sub-
subsystems together
to form subsystems
and test. Bring
subsystems together
to form the system
and test
20
Concept & Feasibility
User Requirements
Developer Specs
Planning
Design
Implementation
Integration Testing
Opr. & Maintenance
Retirement