ADITYA ENGINEERING COLLEGE

(Affiliated to Jawaharlal Nehru Technological University Kakinada) (ADB Road, Surampalem)

DEPT. OF ELECTRONICS AND COMMUNICATION & ENGINEERING

The Current Presentation is About

Software Development Life Cycle

PRESENTED BY

A.Sri Ram Kartik III B.Tech

kartik4b9@gmail.com

K.B.K.Naga Teja III B.Tech

kbknteja@hotmail.com

ABSTRACT:
Traditionally, development of any software or application has followed cyclic approach. SDLC is a process of developing software through investigation, analysis, design, implementation and maintenance. This life cycle approach is the oldest and most widely used for developing business applications like Core Banking applications for Banks etc.,

documentation driven paradigm. The next revolutionary new look at the development lifecycle was the "Spiral model", presented by Boehm in 1985. The spiral model is focused on risk management.

SDLC PHASES:

INTRODUCTION:
In our daily life we meddle with many different kinds of softwares. These softwares make our work easier over the computer. Each software has its own predominant use. Based on the requirements, we use different kinds of softwares. These can be already existing ones or should be newly developed. This development of software has followed cyclic approach which earned it a nameSoftware Development Life Cycle. A software life cycle model depicts the significant phases or activities of a software project from conception until the product is retired. It specifies the relationships between project phases, including transition criteria, feedback mechanisms, milestones, baselines, reviews, and deliverables

The software Development Life Cycle framework provides a sequence of activities for software developers to follow. It consists of a set of steps or phases in which each phase of the SDLC uses the results of the previous one. A Software Development Life Cycle (SDLC) adheres to important phases that are essential for developers, such as analysis, requirements, design, selection, development, testing, and deployment. Feasibility study and analysis phase: In this phase, the main aim is to identify the problem, and then to go for feasibility study for the new system. The analyst will then investigate current system, and will check for possible solutions, and will evaluate all data

HISTORY OF SDLC:
The "Waterfall model", documented in 1970 by Royce was the first publicly documented life cycle model. The model was developed to help cope with the increasing complexity of aerospace products. The waterfall model followed a

collected and will then takes a decision to continue. Requirements phase:

meeting the requirements. In this phase the preparation of request for proposal from suppliers of packaged system is also done. Development phase:

The next comes the requirements phase. The main goal of this phase is to check for the requirements for developing the software. The effort is to gather the requirements from the user and to document them. This can be either a customized approach or a vendor supplied software package. After all the requirements are documented, the next stage is the Design phase. Design phase: In software design, the design functions and operations are described in detail, including screen layouts, business rules, process diagrams and other documentation. Design elements describe the desired software features in detail, and generally include functional hierarchy diagrams, screen layout diagrams, tables of business rules, business process diagrams, pseudocode, and a complete entity-relationship diagram with a full data dictionary. These design elements are intended to describe the software in sufficient detail that skilled programmers may develop the software with minimal additional input design. In this phase, the software developer looks for hardware/ software to be used. The developer also checks for the user interfaces like the inputs and the outputs. Selection phase: This is the most important phase of all the SDLC phases, as in this phase the main aim is to single out best suitable product

The product that is selected in the above phase is sent through the development phase in which it gets developed or enhanced based on the requirements that are documented by the user. In this stage, the effort is made to develop a new software or to build a new software based on the features of the softwares that are readily available in the market. After this phase, the software is then sent for testing that accounts for the Testing phase. Testing phase: Various kinds of testings are organized on these softwares in this phase. These testings include white box testing, black box testing, alpha, beta, Uat, Qat testings. These developed softwares are thoroughly checked for any errors in this testing phase and if there are no errors, the product is sent to the next phase that is Deployment phase. If there are any debugs or deficiencies found in the product, the product is again sent through the feasibility, analysis, and rest of the stages of software development. As this appears in a cyclic fashion, this is called Software Development Life Cycle. Deployment phase: This is the final stage of the SDLC. Now, the users install the program and will use the program for its intended purpose. The requirement of the user is accomplished.

These constitute the phases of the software development life cycle.

3. CMM model 4. RAD model

ADVANTAGES:
There are many advantages of using this method. As the software can be very difficult and complex, we need the SDLC as a framework to guide the development to make it more systematic and efficient. We will be able to tell how long it will take to complete the project, to test and deploy. Not only that, you will have easier time debugging and finding flaws in the software program or make enhancement to it. Different models in SDLC: A software process model is an abstract representation of each software process can be defined in a variety of ways using text, figures, or combination of both software engineers have developed various formats for processing the description of a software process known as the process models. There are many different models in software development life cycle. They are1. Waterfall model 2. Incremental model

5. Throwaway prototyping model

6. Spiral model

7. Evolutionary prototyping model

Deficiencies: 1. All requirements must be known upfront 2. Deliverables considered for each phase are considered frozeninhibits flexibility 3. Can give a false impression of progress 4. Does not reflect problem solving nature of software 5. Integration is one big bang at the end 6. Little opportunity for the customer to preview the system

8. Automated software synthesis 9. V-shaped SDLC model Now, we will have a glance at the different models of the software development life cycle.

Waterfall model: When to use this model: 1. 2. 3. 4. 5. Requirements are very well known Product definition is stable Technology is understood New version of an existing product Porting an existing product to a new platform

V-shaped SDLC model: The least flexible and most obsolete of the life cycle models. Well suited to projects that have low risk in the areas of user interface and performance requirements, but high risk in budget and schedule predictability and control. Strengths: 1. Easy to understand, easy to use 2. Provides structure to inefficient staff 3. Milestones are well understood 4. Sets requirements stability 5. Good for management control A variant of the waterfall that emphasizes the verification and validation of the product. Testing of the product is planned in parallel with a corresponding phase of development.

Strengths: 1. Emphasize planning for verification and validation of the product in early stages of product development 2. Each deliverable must be testable 3. Project management can track progress by milestones 4. Easy to use Deficiencies: 1. Does not easily handle concurrent events 2. Does not handle iterations or phases 3. Does not easily handle dynamic changes in requirements 4. Does not contain risk analysis activities

Note: Nevertheless, SDLC is no exception to Murphys Law. Anything can go wrong will go wrong.

When to use V-shaped model: 1. Excellent choice for systems requiring high reliability hospital patient control applications 2. All requirements are known upfront 3. When it can be modified to handle changing requirements beyond analysis phase 4. Solution and technology are known Conclusion: Finally the object of SDLC is to introduce various design tools and concepts. But this small part of SDLC contains different phases and models. The process models combine the software development life cycle with various tools to implement the different phases to projects.