Search code examples
language-agnosticprogramming-languagessdlc

What is the Software Development Lifecycle?

Our investor wants a SDLC. I've never written one before, and I don't have enough time to go and buy a book, or spend much time learning about them. From what I've been told about them, they consist of requirements (what needs to be done), and a list is done. Is this correct?

Update:

I have found this article which really helps to explain things in simple terms and very quickly. Not that I think an SDLC should be done quickly. In my case, I have no other option.

Solution

  • There are lots of ideas about SDLC out there. You can't swing a cat without hitting one.

    What have you done to develop software that attracted your investor in the first place? Can't you describe that? Why do you have to go out and "learn one"?

    There's a number of choices:

    1. Waterfall: requirements->design->build->test->deploy, all in sequence
    2. Iterative: similar to waterfall, but you break the design into smaller pieces, of 1-2 week duration, that are delivered at the end of the iteration.
    3. Extreme Programming (XP): Kent Beck's approach; no BDUF (Big Design Up Front). Everything is designed, built, and delivered in small pieces.
    4. Scrum: Agile, iterative, but not as dogmatic as XP.
    5. Rational Unified Process: Waterfall from IBM.