+ All Categories
Home > Software > Software developement life_cycle_v1.1

Software developement life_cycle_v1.1

Date post: 15-Apr-2017
Category:
Upload: ganapathi-m
View: 134 times
Download: 0 times
Share this document with a friend
16
Software Development Life Cycle Presentation By Ganapathi M
Transcript
Page 1: Software developement life_cycle_v1.1

Software Development Life CyclePresentation By

Ganapathi M

Page 2: Software developement life_cycle_v1.1

Managing Information• A Computer-based

Information System (CBIS) uses these components to manage and distribute information.

Page 3: Software developement life_cycle_v1.1

Participants in Systems Dev.Systems Analyst: professional who specializes in analyzing and designing systems.

Stakeholders:those that stand to benefit from a new system.

Page 4: Software developement life_cycle_v1.1

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

Page 5: Software developement life_cycle_v1.1

System to Software Development

ProgramSpecification

Program Development Life Cycle

Page 6: Software developement life_cycle_v1.1

Program Development

Many Variations…

Page 7: Software developement life_cycle_v1.1

Program Development

Many Variations…

Page 8: Software developement life_cycle_v1.1

Program Development

Many Variations…

Page 9: Software developement life_cycle_v1.1

Program Development

Many Variations…

Page 10: Software developement life_cycle_v1.1

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.

Fromhttp://en.wikipedia.org/wiki/Software_development_process

Page 11: Software developement life_cycle_v1.1

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.

Page 12: Software developement life_cycle_v1.1

Design

Page 13: Software developement life_cycle_v1.1

Implementation

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

Page 14: Software developement life_cycle_v1.1

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

Page 15: Software developement life_cycle_v1.1

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.

Page 16: Software developement life_cycle_v1.1

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


Recommended