What is the software development life cycle?

Question

Our investor wants to get an SDLC. I have never written it before, and I don’t have enough time to go buy a book or spend a lot of time studying them. From what they told me about them, they consist of requirements (what needs to be done), and the list is done. Is it correct?

Update

I found this article that really helps explain things in simple words and very quickly. Not that I thought SDLC needed to be done quickly. In my case, I have no other choice.

Answer 1

There are many ideas about SDLC. You cannot rock a cat without hitting it.

What did you do to develop the software that attracted your investor in the first place? Can't you describe it? Why should you go out and “study alone”?

There are several options:

• Waterfall: requirements-> design-> assembly-> testing-> deployment, all in sequence
• Iterative: It looks like a waterfall, but you break the design into smaller pieces lasting 1-2 weeks, which are delivered at the end of the iteration.
• Extreme Programming (XP): Kent Beck's Approach; No BDUF (Big Design Up Front). Everything is designed, built and delivered in small pieces.
• Scrum: flexible, iterative, but not as dogmatic as XP.
• Rational Unified Process: Waterfall by IBM.

Answer 2

Not really; which is more project management. This is what you need when you figure out how you are going to develop software.

For the "how" of software development, the two "biggies" are Agile and Waterfall; with a weird hybrid in between.

But only one part of the software development life cycle : you still need to have a maintenance and deployment plan.

My question is for you: if someone gives you money and they need a plan, aren't you interested in reading a book about SDLC and giving them a plan?

Answer 3

If your investor wants you to describe the SDLC, he wants you to describe what the life of a software project looks like, which you make from its plan, birth, from growth to maturity and death. It is for this reason that she has “life” on her behalf. The result of the SDLC should be "software", therefore the first word. Part of the "development" comes from the fact that you are responsible for planning, defining, developing and implementing software, you must create (develop) software. And finally, “cycle” means that when an investor looks at you SDLC and thinks he is good (he produces quality and value for the business), he may ask you to use the same process again in another project.

Answer 4

A full SDLC means that you need to do requirements collection and analysis-> Design (creating a design document) → Coding and unit testing → Testing (system and integrated testing) → Deployment and support → Maintenance

I found this blogg really useful.