SDLC Concepts IVS Task Group SDLC – A Brief Introduction SDLC – A BRIEF INTRODUCTION IVS-TRAINING.
SDLC
-
Upload
pooja-chaddha -
Category
Documents
-
view
1.552 -
download
4
Transcript of SDLC
![Page 1: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/1.jpg)
SDLC
![Page 2: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/2.jpg)
(S)oftware (d)evelopment (l)ife (c)ycle
![Page 3: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/3.jpg)
a systematic and disciplined approach to develope a software with low cost , superior quality and with no schedule slippage
![Page 4: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/4.jpg)
PHASES IN
SDLC
![Page 5: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/5.jpg)
1. feasibility analysis2.requirement analysis & specification3. design4. coding5. testing6.maintanence
![Page 6: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/6.jpg)
FEASIBILITY ANALYSIS
![Page 7: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/7.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/8.jpg)
at the end of this phase a feasibility report is generated.
![Page 9: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/9.jpg)
REQUIREMENT
ANALYSIS
AND
SPECIFICATION
![Page 10: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/10.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/11.jpg)
DESIGN :
![Page 12: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/12.jpg)
SRS requirement translated into a raw and logical structure .
![Page 13: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/13.jpg)
CODING
![Page 14: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/14.jpg)
implementing the design specified in design document to an executable programming language code.
![Page 15: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/15.jpg)
TESTING
![Page 16: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/16.jpg)
code is mapped against design document
test plan involves:1. test case generation2. testing criteria3. resourse allocation for testing
![Page 17: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/17.jpg)
MAINTENANCE
![Page 18: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/18.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/19.jpg)
SOFTWARE DEVELOPMENT
APPROACHES
![Page 20: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/20.jpg)
WATERFALL APPROACH
![Page 21: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/21.jpg)
uses linear approach , that means it provide no process to go back to previous phase to handle changes in the requirement.
![Page 22: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/22.jpg)
PROTOTYPING APPROACH
![Page 23: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/23.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/24.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/25.jpg)
SPIRAL APPROACH
![Page 26: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/26.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/27.jpg)
WIN WIN SPIRAL APPROACH
![Page 28: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/28.jpg)
here the concept is same as spiral approach but also includes time of identifying requirements,communication and planning
![Page 29: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/29.jpg)
INCREMENTAL APPROACH
![Page 30: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/30.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/31.jpg)
limitation:
applicable only to large applications.
![Page 32: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/32.jpg)
Various object oriented
concepts
![Page 33: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/33.jpg)
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](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/34.jpg)
2. inheritance :
sharing of attributes and behaviours among classes based upon hierarchial relationship.
![Page 35: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/35.jpg)
3. abstraction:
focuses on essential inherent aspects of an entity ignoring its implementation detdails .
![Page 36: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/36.jpg)
4. encapsulation:
also called information hiding .it involves preventing access to non-essential details .
![Page 37: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/37.jpg)
5. polymorphism
concept of using same operatiors or functions in different ways depending on what they are operating on.
![Page 38: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/38.jpg)
ROLE OF OOAD IN SDLC
![Page 39: SDLC](https://reader036.fdocuments.in/reader036/viewer/2022070321/558cfdaad8b42a534b8b45bd/html5/thumbnails/39.jpg)
ooad is a tool used in sdlc to reduce complexity of software