By Topic

Project visualization for software

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$33 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
K. T. Hanson ; ABB Corp. Res., Billingstad, Norway

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

Published in:

IEEE Software  (Volume:23 ,  Issue: 4 )