The scouts motto is "be prepared," and this advice is valuable forrnmore than remembering to pack an extra pair of socks and a poncho. When followed, these simple words of wisdom can make a dramatic impact on system architecture and technical design. Being prepared means hoping for the best butrnplanning for the worst.rnAll projects, from the simplest extract, transform and load mapping to the largest enterprise application, should have a technical design review process. The code/process to be reviewed is presented to peers and leads. The review includes checks for functionality,rndevelopment standard adherence, performance consideration and, hopefully, a what-if review. Most designs are good at meeting requirements when everything goes smoothly, but what is included in the design to prepare for the things that go wrong? The sidebar on page 33 lists a few what-if sample questions for yourrnnext review process. I've chosen ETL as the focus here, but the same approach could be applied to a data model, reporting environment, campaign or any other aspect of a project.
展开▼
