Abstract-Recently, software size becomes larger, and consequently, not only a software developer but also a software purchaser suffers considerable losses by software project failure. So avoiding project failure is also important for purchasers. Project monitoring with a purchaser and a developer (stakeholders) is expected for the purchaser to suppress risk of project failure. It is performed by sharing software metrics during the project for the purchaser to grasp the status of the project. Although there are some software measurement models, they cannot describe two kinds of metrics which are used to monitor projects with stakeholders. One metric is to indicate project goal achievement after finishing project. The other one is to measure to progress toward the goal. In addition, the models cannot represent countermeasures when symptoms of project failure are found. We propose the model for project monitoring with stakeholders. The model is based on the measurement information model defined by ISO/IEC 15939, and added stakeholder's goal, key goal indicator (KGI), key performance indicator (KPI), corrective action, and check timing. With our model, project monitoring with stakeholders can be described more rigorously.
The Project Monitoring with Stakeholders Model is based on the measurement information model defined by ISO/IEC 15939, and added stakeholder's (a purchaser and a developer) goal, key goal indicator, key performance indicator, corrective action, and check timing REF .
Modeling Software Project Monitoring with Stakeholders
2010 IEEE/ACIS 9th International Conference on Computer and Information Science
2010 IEEE/ACIS 9th International Conference on Computer and Information Science
Computer Science