Hello World

1. Presenting To :
Mondira Chakraborty
Lecturer
Dept. of CSE
Notre Dame University Bangladesh
Course Title : Software Engineering and Information System Design
Course Code : CSE 3101
1

2. Presenting By :
Sajid Hossain Khan
ID: 0692210005101007
CSE 18
2
Course Title : Software Engineering and Information System Design
Course Code : CSE 3101

3. “Software Process, Models, Iterations and
Specification”
3

4. Process
We can think of a series of activities as a process
Specificati
on
Design
Implementi
ng
Testing
4

5. 4
3
2
1
Waterfall
Model
V Model Prototype
Model
Incremental
Model
5
Spiral
Model
5

6. Requirement Gathering and Analysis
System Design
Implementation
Testing
Development
Maintenance
Waterfall Model
The waterfall model follows
sequential stages: requirements,
design, implementation, testing,
deployment, maintenance.
Where to use?
• The waterfall model is efficient
and simple, suitable for
experienced teams.
• It eliminates extensive software
design deliberation with
predefined steps. 6

7. Advantage
1
Structured, systematic approach
to software development.
2 Encourages detailed planning
and documentation at every step.
3 Well-suited for projects with
fixed requirements, budgets,
and timelines.
Disadvantage
1
Difficulty adapting to
changes.
2
High risk: long development
cycles, missed market
opportunities.
3 Inability to quickly adapt to
new technologies
7

8. Requirement
Analysis
System
Design
Architecture
Design
Module
Design
Coding
Unit Testing
Integration
Testing
System
Testing
Acceptance
Testing
Developer’s life Cycle Tester’s life Cycle
Acceptance
Test Design
System
Test Design
Integration
Test Design
Unit
Test Design
V Model
The V model is an improvement
of waterfall model.The testing
occur at each stage, represented
by a downward flow on the right
side.
Where to use?
• The V model is beneficial in
uncertain project directions.
• It allows continual testing for
progress validation.
8

9. Advantage
1 Bugs are identified earlier
2 Reducing costs and preventing
potential issues from escalating
Disadvantage
1 Increased upfront work
2
Not suitable for projects with
rapidly changing
requirements
9

10. Requirements
Implementation
Design
Testing
Design
Implementation
Testing
Maintenance
Prototype Model
• Iterative prototyping develops a
model upfront.
• The system evolves with
customer-proposed features.
• Prototype may evolve or be
discarded.
Where to use?
• Prototype model suitable for
systems with extensive user
interaction.
• Ideal for online systems and
web interfaces.
10

11. Advantage
1 Users are actively involved
in the development
2 Errors can be detected much
earlier.
3
Quicker user feedback is
available leading to better
solutions.
Disadvantage
1 It may increase the complexity
2
High risk: long cycles, missed
market opportunities.
3 Incomplete or inadequate
problem analysis.
11

12. Define outline
requirements
Assign requirements
to increments
Design System
Architecture
Develop system
increment
Validate
Increment
Integrate
Increment
Validate
System
System incomplete
Final
system
Incremental Model
In Increment model, we complete
the software development process
multiple time.
Where to use?
• Suitable for clearly defined
system requirements.
• Allows some details to evolve
over time.
12

13. Advantage
1 In this model customer
can respond to each built.
2 Lowers initial delivery cost.
3 Lower risk of overall project
failure
Disadvantage
1 Total cost is higher than
waterfall.
2 The process is not visible.
3 System structure tends to
degrade as new increments
are added.
13

14. Spiral Model
• Spiral model manages risks through iterative cycles.
• Each cycle involves setting project goals, problem-fixing, software
building/testing, and planning for next cycle.
Where to use?
1. For medium to high-risk projects
2. Users are unsure of their needs
3. Requirements are complex
14

15. Spiral model of the software process
Risk
analys is
Risk
analysis
Risk
analysis
Risk
Proto-
analysis
type 1
Prototype 3
Prototype 2
Opera-
tional
protoyp e
Concept of
Operation
Simulations, models, benchmarks
S/W
requirements Prod uct
design Detailed
design
Code
Requirement
validation
Design
V&V
Acceptance
test
Service
Unit test
Integr ation
test
Develop, verify
next-level product
Evaluate alternatives
identify, resolve risks
Determine objectives
alternatives and
constraints
Plannext phase
Integration
and test plan
Develop ment
plan
Requirements plan
Life-cycle plan
REVIEW
15

16. Advantage
1 High amount of risk
analysis hence, avoidance
of Risk is enhanced.
2 Good for large projects.
Disadvantage
1 Can be a costly model to
use.
2 Doesn’t work well for smaller
projects.
16

17. References:
1.For model picture:
• Google Images. (n.d.). Retrieved from https://www.google.com/imghp
2.Model definition:
• Smith, J. (2021). Introduction to Software Development Models. [YouTube
Playlist]. Retrieved from
17
https://www.youtube.com/watch?v=AHrx96R_SgA&list=PLsNGqIqCp0u
_icl-VyDFikHjB5NGsW2ZE&index=1&t=10s&pp=gAQBiAQB

18. Thank you for your time and attention.
18