RESUMEN

Project team leaders can use software project "blueprints"--in the form of graphical expressions such as code- and function-oriented visualizations-to update stakeholders on the project's progress through the development cycle. These graphical visualization can represent artifacts produced in a software project. The author gives both theoretical and real-world examples showing how the visualizations map to architectural views and discusses how these visualizations could be linked to standard project management tools.