It’s been a long time since my last blog post.
From now onwards, I will try to be more active on blogging. My blogs would be more around my randoms thoughts which I get time to time .
Just trying to come with an analogy between SDLC (software development life cycle) and human development life cycle (in short HDLC, it not High-Level Data Link Control sorry for coming with the same acronym).
Both are very sensitive when on production.
Well both needs to have high level and low level design and design should be scalable and flexible enough to onboard futuristic use cases but flexibility should not be extra ordinary because that comes with one's risk taking capability (definitely that may also give some awesome result at the end).
Before that both needs to define a proper requirement considering present requirement, taking futuristic requirement along with analysis around past events within the same domain for which requirements are getting defined.
In both cases, requirements are concluded at multiple levels. Like for SDLC, first step is taking requirements in terms of business requirements by business analysts and then the same is passed on to technical analyst for defining technical requirements and then the requirements are passed on to developers for implementation and upcoming changes and requirements are entertained upon the consent of developers based on the design capabilities. Also in case of HDLC, requirement for the product is defined by parents in first cut and then requirements are passed on to the child. Different child behaves differently with the requirements from parents and refreshes the requirements which are passed on from parents accordingly keeping their own requirements as well. Then comes the responsibility of implementation for requirements and again there can be many more requirements coming in during implementation phase whose accommodation is based on the design accommodated for earlier requirements and design flexibility.
At last in both cases wiser is one who keep a space in design in terms of flexibility to entertain future use cases.
Signing off for today, will try to be back soon with few more blogs....
From now onwards, I will try to be more active on blogging. My blogs would be more around my randoms thoughts which I get time to time .
Just trying to come with an analogy between SDLC (software development life cycle) and human development life cycle (in short HDLC, it not High-Level Data Link Control sorry for coming with the same acronym).
Both are very sensitive when on production.
Well both needs to have high level and low level design and design should be scalable and flexible enough to onboard futuristic use cases but flexibility should not be extra ordinary because that comes with one's risk taking capability (definitely that may also give some awesome result at the end).
Before that both needs to define a proper requirement considering present requirement, taking futuristic requirement along with analysis around past events within the same domain for which requirements are getting defined.
In both cases, requirements are concluded at multiple levels. Like for SDLC, first step is taking requirements in terms of business requirements by business analysts and then the same is passed on to technical analyst for defining technical requirements and then the requirements are passed on to developers for implementation and upcoming changes and requirements are entertained upon the consent of developers based on the design capabilities. Also in case of HDLC, requirement for the product is defined by parents in first cut and then requirements are passed on to the child. Different child behaves differently with the requirements from parents and refreshes the requirements which are passed on from parents accordingly keeping their own requirements as well. Then comes the responsibility of implementation for requirements and again there can be many more requirements coming in during implementation phase whose accommodation is based on the design accommodated for earlier requirements and design flexibility.
At last in both cases wiser is one who keep a space in design in terms of flexibility to entertain future use cases.
Signing off for today, will try to be back soon with few more blogs....
