Top Banner
SDLC
39
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: SDLC

SDLC

Page 2: SDLC

(S)oftware (d)evelopment (l)ife (c)ycle

Page 3: SDLC

a systematic and disciplined approach to develope a software with low cost , superior quality and with no schedule slippage

Page 4: SDLC

PHASES IN

SDLC

Page 5: SDLC

1. feasibility analysis2.requirement analysis & specification3. design4. coding5. testing6.maintanence

Page 6: SDLC

FEASIBILITY ANALYSIS

Page 7: SDLC

1.analysis of project requirements : 1. input data and desired output 2. processing required to transform input to output 3.cost benifit analysis 4.schedule of project 2.technical feasibility : focuses on: 1. availability of software tools 2.availability of hardware 3.availability of skilled software professionals

Page 8: SDLC

at the end of this phase a feasibility report is generated.

Page 9: SDLC

REQUIREMENT

ANALYSIS

AND

SPECIFICATION

Page 10: SDLC

1.an SRS ( software requirement specification) document is generated.

2. SRS is a formal document includes performance, functional, software ,hardware and network requirements of the project.

3.it acts as an agreement between development team and customer .

Page 11: SDLC

DESIGN :

Page 12: SDLC

SRS requirement translated into a raw and logical structure .

Page 13: SDLC

CODING

Page 14: SDLC

implementing the design specified in design document to an executable programming language code.

Page 15: SDLC

TESTING

Page 16: SDLC

code is mapped against design document

test plan involves:1. test case generation2. testing criteria3. resourse allocation for testing

Page 17: SDLC

MAINTENANCE

Page 18: SDLC

1. handling errors that may exist in software even after testing phase

2. implementation of new requirements after software is deployed at customer location.

Page 19: SDLC

SOFTWARE DEVELOPMENT

APPROACHES

Page 20: SDLC

WATERFALL APPROACH

Page 21: SDLC

uses linear approach , that means it provide no process to go back to previous phase to handle changes in the requirement.

Page 22: SDLC

PROTOTYPING APPROACH

Page 23: SDLC

2. a prototype is generated acc to requirements of software that tells customer how the software is going to function and to get better knowledge of requirements.

until the customer approves the prototype , generating a new prototype is continued ( before finalizing and frozing the requirements )

Page 24: SDLC

types of prototypes :1. throwaway prototypes: those

prototypes that are eventually discarded rather than becoming a part of finally delivered software.

2. evolutionary prototypes: are those that evolve into the final system through iterative incoorperation of user(ustomer) feedback.

Page 25: SDLC

SPIRAL APPROACH

Page 26: SDLC

includes both iterative nature of prototyping approach and linear nature of waterfall approach.

example: evolution of windows operating system from windows 3.1 to windows 2000

Page 27: SDLC

WIN WIN SPIRAL APPROACH

Page 28: SDLC

here the concept is same as spiral approach but also includes time of identifying requirements,communication and planning

Page 29: SDLC

INCREMENTAL APPROACH

Page 30: SDLC

there are number of functional units , each containing group of similar tasks.

each functional unit is implemented with an increment and final product is acheived after all units are implemented in the development process.

Page 31: SDLC

limitation:

applicable only to large applications.

Page 32: SDLC

Various object oriented

concepts

Page 33: SDLC

1. classes and objects

classes: an abstract data type that contains set of attributes and functions.object: instance of class

all the objects share same copy of member functions ,but maintain a seperate copy of the member data.

Page 34: SDLC

2. inheritance :

sharing of attributes and behaviours among classes based upon hierarchial relationship.

Page 35: SDLC

3. abstraction:

focuses on essential inherent aspects of an entity ignoring its implementation detdails .

Page 36: SDLC

4. encapsulation:

also called information hiding .it involves preventing access to non-essential details .

Page 37: SDLC

5. polymorphism

concept of using same operatiors or functions in different ways depending on what they are operating on.

Page 38: SDLC

ROLE OF OOAD IN SDLC

Page 39: SDLC

ooad is a tool used in sdlc to reduce complexity of software