Design and Code Review
Any software project efforts, howsoever carefully planned and implemented, still need to be reviewed periodically. So much so, that the pragmatic view considers SDLC not as a straight-line sequential process, but rather as a series of steps with each and every step to be reviewed before the next one in chronological sequence is taken up.
The reason behind this need for reviewing the design and code (and all other stages in SDLC for that matter) approach is two-fold.
Firstly, the software development aims at simulating the real life processes of the concerned application into cyber world that needs tremendous discerning. There are umpteen aspects that demand simultaneous attention of system designer. Again many of these points are inter-related and hence numbers of dependencies are involved that have to be satisfied. Besides, each issue has its own size-wise and complexity-wise considerations to be looked into.
Secondly, being a real life project, software development has to meet constraints of cost and time that further underline the utter need to manage the project within the budgetary sanctions and time deadlines. As we will see in the section, any wrong steps taken in software development cost dearly for their rectification. Furthermore, the time wasted in the process might dissatisfy the clients and have repercussions on future business. The obvious rule to curb such things is earlier the better. Hence a review is essential as an effective preventive control at almost all the steps of SDLC.
Expertsmind.com offers software engineering assignment help - homework help, some of software engineering topics are given below....
Comments
Post a Comment