The Code Trip
The Code Trip
Sometimes the best way to understand a concept is to equate it another concept. In this articles, one dev uses this trick to explain the SDLC.
Join the DZone community and get the full member experience.Join For Free
The Agile Zone is brought to you in partnership with Techtown Training. Learn how DevOps and SAFe® can be used either separately or in unison as a way to make your organization more efficient, more effective, and more successful in our SAFe® vs DevOps eBook.
We usually plan our trips with family to various destinations and locations to get relieved from the pressures we feel at work. If we give some thought to the entire process of a trip, it turns out to be a complete development cycle. In SDLC, requirements can change overnight; but a few basic steps that need to be followed never change. We are going to relate this fictitious trip with the SDLC of the software industry in order to get a better understanding of Agile processes.
Basically, SDLC has six steps, as iterated below (related to trip arrangements):
1. Requirement gathering and analysis - The very first step is to decide the destination and locations to visit. The following points should be taken into consideration while deciding:
a) Will the weather of preferred location suit the requirements?
b) Are general commodities easily available and accessible?
This is the same as requirement gathering in the SDLC while preparing a design.
2. Design - The second step is to decide the 'HOW' and 'WHAT' factors. The below points are important to consider:
a) How will we reach the destination (personal, public, or hired transportation)?
b) What clothes are required and necessary as per the weather conditions?
c) How will we reach the sight-seeing locations and what activities will we do there?
This is the same as the creation of a design to be worked upon by the team(s) in the form of modules.
3. Implementation or Coding - The third step is to get ready by packing clothes, necessary commodities, and to leave for a comfortable journey to your destination. This is same as the coding and development of the requirements from the prepared design.
4. Testing - The fourth step is to reach the destination and enjoy the various locations along with the variety of food available. Prepare a list of good or bad experiences to provide feedback or reviews. Take photographs wherever necessary. Suggest the unexplored places of the destination in your feedback list which you have seen in the trip. This is same as the 'Validation and Verification' of the developed design to suit the requirements.
5. Deployment - The fifth step is to pack your bags for the return journey and provide your feedback or review online for people who like to know exactly the places they should go to stay, visit, and enjoy the food. This is same as the deployment of the verified code for user experience (with existing risks and dependencies in the developed application).
6. Maintenance - The sixth and last step is to collect your memories in the form of pictures taken and save them in a folder so you can cherish them for a lifetime. This is the same as the maintenance where code is regularly executed to check the proper functioning and removal of any ambiguities.
Conclusion: Whenever you get stuck with work, try to relate it to a problem you resolve daily in your vicinity. By doing this, the biggest problems get resolved in no time, which helps to build your confidence, patience, and decision making abilities in the worst situations.
Opinions expressed by DZone contributors are their own.