When projects transition to production, the receiving team need some transition documentation to help with knowledge transfer and to guide them while they get accustomed to operating the application and can form their own documentation. This temple is a shell, which usually provides enough detail, with some updating, to provide a quick reference regarding the application. Also, having a temple can be a real time saver, as opposed to writing it from scratch.
Peer code review happens during the development phase and focus on the overall quality and compliance to standards of code and configuration artifacts. However, the hard part of performing a Peer code review isn’t, performing the review, but rather to achieving consistency and thoroughness in the review. This is where a checklist can contribute significantly, providing a list of things to check and providing a relative weight for the findings. I hope this template assists with your DataStage job review process.
A peer review is an examination of a Software Development Life Cycle (SDLC) work product by team members, other than the work Product’s author, to identify defects, omissions, and compliance to standards. This process provides an opportunity for a quality assurance, knowledge sharing, and product improvement early during the SDLC life cycle.