|
| This Article | ||
| ||
| Share | ||
| Bibliographic References | ||
| Add to: | ||
| | ||
| Search | ||
| ||
| ASCII Text | x | ||
| Kai T. Hansen, "Project Visualization for Software," IEEE Software, vol. 23, no. 4, pp. 84-92, July/August, 2006. | |||
| BibTex | x | ||
| @article{ 10.1109/MS.2006.111, author = {Kai T. Hansen}, title = {Project Visualization for Software}, journal ={IEEE Software}, volume = {23}, number = {4}, issn = {0740-7459}, year = {2006}, pages = {84-92}, doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2006.111}, publisher = {IEEE Computer Society}, address = {Los Alamitos, CA, USA}, } | |||
| RefWorks Procite/RefMan/Endnote | x | ||
| TY - MGZN JO - IEEE Software TI - Project Visualization for Software IS - 4 SN - 0740-7459 SP84 EP92 EPD - 84-92 A1 - Kai T. Hansen, PY - 2006 KW - project management KW - software architecture KW - UML KW - tool support VL - 23 JA - IEEE Software ER - | |||
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/MS.2006.111
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.
Index Terms:
project management, software architecture, UML, tool support
Citation:
Kai T. Hansen, "Project Visualization for Software," IEEE Software, vol. 23, no. 4, pp. 84-92, July-Aug. 2006, doi:10.1109/MS.2006.111
Usage of this product signifies your acceptance of the Terms of Use.

