loading...

SDLC – Software Development Life Cycle Overview

pakainfocom profile image pakainfo ・6 min read

Software Development Life Cycle (SDLC) is a mechanisms used by the software industry to design, develop and test high quality software's. The SDLC aims to manufacture a high-quality software that meets or exceeds customer expectations, reaches completion within times as well as cost estimates.

  • SDLC is the signifies of Software Development Life Cycle.
  • This is also stands for a Software Development Process.
  • SDLC is a framework defining jobs execute at each step by step in the software development mechanisms.
  • ISO/IEC 12207 is an international standard (default) for software life-cycle processes. It aims to be the standard that specify all the jobs required for developing as well as maintaining software.

What is SDLC?

SDLC is a mechanisms followed for a software project or web application, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace as well as alter or enhance specific software. The life cycle specify a methodology for improving the quality of software with the overall development mechanisms.

The bellow figure is a diagram explanation of the different stages of a representative SDLC.

SDLC Models

bellow are the most helpful and useful for project SDLC models followed in the large business or industry −

  • Waterfall Model
  • Spiral Model
  • Big Bang Model
  • Iterative Model
  • V-Model

Stage 1: Planning and Requirement Analysis

Let's talk SDLC regarding the system development life-cycle. Any computer information system can take a bit of effort to develop and so it's a smart thing to break it down into distinct phases. For example, there is the analysis step where you talk to clients and find out what the issue is -- what they required. There's the design step where you take that information and you design an answer to the question, a clarification to the issue. There's the build step where you construct the system, and the deployment step where you hand it back to the client, and finally the support step where you help them use it to the best advantage. Each of these phases requires a different kind of thinking, a different kind of work, different activities, even different methods of communicating. In the analysis step you are talking to the client in their language.

It's SDLC Individualy you do over and over once more. In fact if you break the system down into a small enough peice, you can take just a subset of the features, completely analyze what they required to, design a great set of features, build them, and show them to the client in just a couple weeks or maybe a month. That way they can tell you right away, "Yes, that's the system we want." Do this a couple times and pretty soon you've got enough functionality that the client's ready to go. This is called an iterative process. The kinds of activities you do in the cycle whether it's the old fashioned long cycle or one of these new cycles, the activities are the same.

Stage 2: Defining Requirements

Occasionally what they tell you they want isn't really what they required so it's useful to go on ride onwards, to actually do their job with them, and observe them doing what they do. If you've got all large client base you can do surveys. There's all category of methods of finding out: what does the client required? How does the client think regarding it? In this step you create diagrams and documents and they're all in the client's language.

Stage 3: Designing the Product Architecture

You look at all of the range of: What can we do for this person? What can we use? What technologies are available to us? What other products can we buy that might do the same job? Again, you produce documents and diagrams and that sort of thing but in this SDLC step you also start prototyping. Early on you can even use little bits of paper and show the client, "Ok, you'll have a screen like this, and then it'll do Individualy else.

Stage 4: Building or Developing the Product

If they don't communicate, they're not any good Some folks move extremely quickly through the design document SDLC methodologies and actually move right to the code. Especially if you've broken it down into a tiny piece you don't do a lot of documenting -- you just get to the code. You make sure everybody understands what requireds to be built and you build it. This is production code.

Stage 5: Testing the Product

Let's go throughout the circle once more and talk regarding how you verify your phase by phase understanding at each phases. In the analysis step, once more, you've got those documents. In our course, when we're working on websites we'll show mockups, we'll talk regarding behaviors.

So we got through the five SDLC phases of the system development lifecycle. You may have seen that I've left out planning until this part of the presentation. That's because planning is part of every step. It fits in between every step of the application and it's done over and over once more.

So you go through your analysis, you sit back and you say, OK, how long this is gonna take us, what will it take... Are we gonna succeed or not? You go through the design, you find out: Is this technically feasible? Can we do this with our current budget? our person? Each time you look at it and you have to make that hard decision: should we continue with the application? Don't wait until you're way down the road before you cancel a application and waste a lot of money and time. Planning happens in every step. Why? Because planning reduces uncertainty. When you start a application, you can estimate all you like but you don't have a lot of information. You could be off by a component of 10. Your budgets or schedules, they can all be so far off that they're just misleading.

Stage 6: Deployment in the Market and Maintenance

You build a clarification, then scale it up and deliver it. In support you help the client and you attend to them. Each of these SDLC phases has unique kinds of outcomes or deliverables: user documents things that are in the user's voice, technical documents and precursors. Eventually you get to the point where you've got a functioning system and you can hand that to clients.

You can visit my Article with More Examples : click here

Posted on by:

pakainfocom profile

pakainfo

@pakainfocom

My name is Angular King. I'm a full-stack developer, entrepreneur and owner of Pakainfo. I live in India and I love to write

Discussion

pic
Editor guide