A software product "blueprint" let stakeholders view a software project's status at any point in the development. The work on requirements analysis and design when only the designers understand a software project's progress can be frustrating. Although a project leader should give progress presentations to stakeholders before the software is ready for demonstration, a presentation showing fragments of code is hardly useful. The lack of useful information makes it difficult for stakeholders to give constructive criticism on the project's progress or to set priorities. It might also damage their confidence in the project's progress and quality and their faith in the plans