DEV Community

Ahmet Sönmez
Ahmet Sönmez

Posted on

A different look at SDLC

In this article, I do not want to waste your time by repeating the definition and explanations of SDLC, which has pages full of examples and definitions. Of course, I am not sure how successfully these will be applied in real life. These are purely well-intentioned engineering wishes.

There are only a few things I want to talk about.

  • Why each step in the SDLC process does not have a percentage value.
  • Why companies do not comply with this standard and all the documents presented remain so-called.

So far, I have reviewed many SDLC documents and been involved in the process. What particularly caught my attention was that no percentage values were assigned to the parts of the SDLC process. In other words, I believe that the analysis and planning process and the development, maintenance and testing processes have different costs, added value and structure.

Image description

For example, let’s assume that an SDLC process is a whole percentile. I think that 50% of this should definitely have the first 3 steps, namely the determination of needs, analysis/planning and the design sub-process. Because, the more time and effort is spent here, all the remaining processes will proceed in a more understandable and close to zero error manner.

After the desired demands are clarified and the necessary planning is made on them, 20% more will be sufficient for the development phase.

The subprocess I expect to have another 20% slice is testing/deployment. I think that a well planned and developed product will need a good test time at least as much as the development rate.

Finally, I think that a 10% surplus will suffice for the maintenance sub-process.

If you wish, you can use these steps in general product development or apply different methodologies to the sub-processes for each part at different rates.

Because developing a process in which the needs are clearly identified and analyzed and appropriately planned can turn out to be almost child’s play. Otherwise, after the product hits the market, it can become extremely costly or even impossible to change and develop many places.

Likewise, if you think your process will be technically advanced, you can manipulate these percentages by giving sincere values. The point is, what do you really value most and what exactly are you interested in in this process.

In general, the parts that I want to focus on are underestimated and the application development phase is started after almost a short analysis and planning. The reason for this haste may be sometimes the desire to reach the money early, sometimes the desire to get ahead of the competitors, and sometimes due to inexperience.

Of course, due to the problems experienced after skipping all these important steps, no one will hesitate to show many factors as the reason for the failure.

In Summary,

“By failing to prepare, you are preparing to fail.”

Benjamin Franklin

Top comments (0)