This is the presentation I use to explain various software development models and the phases involved to the junior developers, freshers and interns.

1. Software Development Life Cycle
Presentation By
Ganapathi M

2. Managing Information
• A Computer-based
Information System
(CBIS) uses these
components to manage
and distribute
information.

3. Participants in Systems Dev.
Systems Analyst:
professional who
specializes in analyzing
and designing systems.
Stakeholders:
those that stand to
benefit from a new
system.

4. Systems Dev Life Cycle
Systems development
is the activity of creating
new or modifying existing
information systems.

5. System to Software Development
Program
Specification
Program Development Life Cycle

6. Program Development
Many Variations…

7. Program Development
Many Variations…

8. Program Development
Many Variations…

9. Program Development
Many Variations…

10. Analysis
The most important task in creating a
software product is extracting the
requirements or requirements analysis.
Customers typically have an abstract
idea of what they want as an end result,
but not what software should do.
Incomplete, ambiguous, or even
contradictory requirements are
recognized by skilled and experienced
software engineers.
From
http://en.wikipedia.org/wiki/Software_development_process

11. Design
• Specification is the task of precisely
describing the software to be written,
possibly in a rigorous way.
• A use case is a description of a
system’s behavior as it responds to a
request that originates from outside of
that system.
• Flowcharts and psuedo-code are
typically used.

12. Design

13. Implementation
• Implementation is the part of the
process where software engineers
actually program the code for the
project.

14. Testing
• Alpha testing – in-house
• Beta testing – select users
• Syntax errors – incorrect use of
language, causes system crashes
• Logic (semantic) errors – system
works, but gives the wrong result,
incorrect software design

15. Maintenance
• Maintenance and enhancing software
to cope with newly discovered
problems or new requirements can
take far more time than the initial
development of the software.

16. Program Design Models
• Waterfall Model: Analysis, Design,
Implementation, Testing, Maintanance, months
or years before product is presented
• Agile Software Development/Extreme
Programming (XP): Iterative,small steps,
automated testing, pair programming,
dependence on frequent user feedback
• Cowboy coding: anything goes