Question

You are an IT consultant, and you have been approached by an entrepreneur in need of a business plan to obtain funding. Part of this business plan centers on an IT presence. Create a 2-page executive summary that explains how the SDLC applies to your customer’s organization. Be creative. You can select any business you like, but remember the conversation must focus on IT operations, particularly a system design or software or application presence. Introduce the organization, providing its background and a breakdown of the task at hand.

Answer 1

Building a software is an incremental process, Eventually, the software is delivered to the customer. The sequence of steps used by these methods is commonly referred to as the Software Development Lifecycle (SDLC.)

How does the SDLC work?

The process of software development is a never-ending cycle. The first release of a software application is rarely “finished.” There are almost always additional features and bug fixes waiting to be designed, developed, and deployed.

Benefits of the SDLC

It’s very difficult to carry out a complex, team effort such as software development without some kind of a plan. There is much debate about which method is best overall, which is best suited to a particular type of software, and how to measure success in software development. One thing, however, is certain: any plan is better than no plan.

A formally defined method for software development in the form of the SDLC achieves a number of benefits:

-Defined communication channels between development teams and stakeholders

-Clear roles and responsibilities among developers, designers, business analysts, and project managers

-Clearly-defined inputs and outputs from one step to the next

A deterministic “definition of done” that can be used to confirm whether a step is truly complete

Since we see that all the steps are properly documented and communication is two way with stakeholders that would ensure a proper funding in an ideal situation.

Following are the steps involved in a SDLC:-

Planning

For development projects, the planning phase includes gathering requirements, such as: what exactly the system should accomplish, your deadline, when you think you’ll be able to finish, your total budget, and the resources you’ll need.

For example, say your client has a hard deadline for when they need a finished product. You don’t have enough team members to finish on time, so you’ll need to hire a freelancer. That’ll have to come out of your budget, meaning you’ll have less money to spend in other areas.

Our next feasible plan of action may look like this:

Reallocate funding for a freelancer (or ask for more money from your client)

Write and a post job description, or reach out to reliable freelancers you’ve worked with before

Balance the team’s workload with the new freelancer in mind.

Defining

The defining phase of SDLC is the point at which we take all of our approved requirements and document them . Defining is a buffer phase between gathering requirements and acting on them. It helps your team ensure they’re on the right track before they start working on the project.

Why this phase is important

Spending some time defining and clarifying can save you some giant headaches in the future. You don’t need to spend too much time on this phase, but you can think of it as getting the green light for your project.

Designing

The design phase should include specifications as broad as how team members will communicate during the project and as specific as the internal design of the software (i.e., how the finished project is coded, etc.).

Building

The building phase is the part where We do all the work you’ve talked about for so long in all the other phases.

With all the bits and pieces, such as our requirements and approved design ideas, we now get to put something together that’s usable and does what it needs to do.

Testing

Testing is important, each component of our system has to make sure that all the individual moving parts work by themselves and, as you build out the system, that they all work together as part of a one single unit.

Why this phase is important

Without testing, we might have created totally useless or really buggy software and as a result of that we not get paid for our hardwork .

Deployment

Why this phase is important

This is the part where your final product goes into the real world At this point, we have looked at this system for so long that we don’t understand what it’s like to interact with it for the first time. People who will use the system every day can provide you with honest feedback about whether you’ve built a high-quality product or whether there’s room for improvement.

Maintenance

It’s important to note that our job as a software developer doesn’t end after the final deadline or after the product launches

Maintenance is a never-ending process of updating your system periodically, improving it for more efficient use, and fixing bugs as they occur.

Without maintenance, we won’t improve our product. And without improvements or updates, our product will deteriorate over time. And our reputation as a developer will deteriorate right along with it.