Systems Development LifeCycle
A Rose Is A Rose Is A Rose
A Systems Development Lifecycle is a methodology for implementing software in a consistent manner that encourages optimization of the process, incorporates feedback loops, and is the closest you can get to the benefits of factory style production when every single product is custom designed.
At the heart of any SDLC is the urge to find a solution to a problem. The solution must allow the organization to stay competitive or to move it into a new area of business. Typically, these problems are pondered by executives setting the strategies for the company, and they then call upon their employees to implement their vision for the solution.
Often, finding the solution to a problem is part and parcel of the SDLC, as the executives will send people off to discover the best possible solution for problem. Regardless, it is an idea, or a vision for a solution, that starts any SDLC.
The most basic SDLC is as follows:
Some of the SDLC structure will be dictated by an organization's structure, and how they have evolved their ability to solve problems and develop solutions. Each of the above phases can have their own world of complexity.
There is no one single SDLC that will work for everyone; instead, the SDLC is best created with the specifics of your organization in mind. There are guidelines that can and should inform your design of the SDLC, starting with the two basic types.
Project SDLC
The Project SDLC is one that is intended to be used for project based development. Project based development is when the team members are pulled from a variety of groups within the company for the express purpose of accomplishing the project's goals. The team members are chosen because of their abilities and availability.
A Project SDLC is often more of a guideline than a set of commandments. The team members may be unfamiliar with the SDLC because they were just plucked out of their non-development jobs to participate in the solution. Job performance measurements may have nothing to do with the SDLC.
Organization SDLC
Some organizations integrate project, or ad hoc, development into their structure so that there is never a reason to assemble teams of people to build something.
Employees will have a specific job function that is straight out of the company's SDLC, and may never do any other part of the SDLC. In fact, the SDLC may not even be recognized as such; it may have been so thoroughly absorbed by the organization that it is not referred to as the SDLC, but is simply the way things get done.
The Organizational SDLC may be stagnant, or slow to respond to needed changes, but you probably never, ever wonder what is your part of the process.
The ensuing articles will elaborate on the six major steps, and I'll be explaining templates and tools to help you find your own SDLC. Meanwhile, post your comment or suggestions.
