| Home : Testing : Project Metrics |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Project Metrics Listings
|
|
Total:
18 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
Sponsored Links
|
|
Step 6 is to identify and configure tools which are necessary to support the metrics program. Each tool is described and an example is given. Actions required for step 6, and an example are given. Author(s) : Software Productivity Center Inc.
Updated: 10/08/2005
|
|
|
Step 7 is to define and create the metrics database for the storage and retrieval of the software measurement data. Actions required for step 7 are given. Author(s) : Software Productivity Center Inc.
Updated: 10/08/2005
|
|
|
Step 8 is to outline the procedures necessary to enable good internal communication about the metrics data, the program goals, and the changes to the development process. Actions required for step 8, and an example are given. Author(s) : Software Productivity Center Inc.
Updated: 10/08/2005
|
|
|
This paper presents a system for measuring the Function Point software metric from specifications expressed in the form of an Entity Relationship (ER) diagram and a Data Flow Diagram (DFD). As a first step towards the implementation of the system, the informal Function Point counting rules have been translated into rigorous rules expressing properties of the ERDFD. Prolog was chosen for the implementation because of its declarativity and maintainability. Thanks to its relational representation, it was possible to directly represent the input ER-DFD with Prolog facts. Author(s) : Evelina Lamma, Paolo Mello and Fabrizio Riguzzi
Updated: 10/08/2005
|
|
|
This article introduces ISO/IEC 15939 software measurement process. Measurement- related actions are listed. The four measurement activities: establish capability, plan measurement, perform the measurement process, and evaluate measurement are illustrated. Author(s) : Peter Baxter
Updated: 10/08/2005
|
|
|
Most software metrics activities are carried out for the purposes of risk analysis of some form or another. Yet traditional metrics approaches, such as regression-based models for cost estimation and defects prediction, provide little support for managers wishing to use measurement to analyze and minimize risk. Significant improvements can be achieved by using causal models that require no new metrics. The new approach, using Bayesian nets, provides true decision-support and risk analysis potential. Author(s) : Norman Fenton and Martin Neil
Updated: 10/08/2005
|
|
|
This guide covers the following: it defines a metrics capability evaluation method that deals specifically with defining a customer's metrics capability, it presents metrics capability questionnaires that help gather metrics capability data, it outlines a metrics capability evaluation report that provides the basis for developing a metrics customer project plan, it provides a metrics customer profile form used to determine the initial information required to prepare for a metrics capability evaluation, and it provides a customer organization information form that helps guide the STSC in gathering cultural information about the organization that will help with developing and implementing the metrics customer project plan. Author(s) : Faye Budlong and Judi Peterson
Updated: 10/08/2005
|
|
|
This slide presentation on the Feedback Evolution, and Software Technology (FEAST/1) includes the following topics: the FEAST hypothesis, FEAST results, metrics of software evolution-some desired features, implications for the control of software evolution, and metrics in software evolution management. Author(s) : M.M. Lehman and J.F. Ramil
Updated: 10/08/2005
|
|
|
Pedagogies such as the Personal Software Process (PSP) shift metrics definition, collection, and analysis from the organizational level to the individual level. The authors research suggests that this "PSP adoption problem" may be due to two problems: the high overhead of PSP-style metrics collection and analysis, and the requirement that PSP users "context switch" between product development and process recording. This paper overviews the authors initial PSP experiences, their first attempt to solve the PSP adoption problem with the LEAP system, and their current approach called Hackystat. Author(s) : Philip M. Johnson, Hongbing Kou, Joy Agustin, Christopher Chan, Carleton Moore, Jitender Miglani, Shenyan Zhen and William E.J. Doane
Updated: 10/08/2005
|
|
|
This paper reports on an ongoing object oriented software measurement experiment which has been set up to monitor and evaluate team-based projects building OO software. The process, called the Software Assessment Through Ongoing Profile Sheets (SATOPS) which relies on manual form entries for recording measurement data in a project management framework is being automated using JAVA. The automated tracking of software process and resource activities will improve the metrics data collection and analysis phase. Author(s) : Sita Ramakrishnan, Tim Menzies, M. Hasslinger, P. Bok, H. Mccarthy, B. Devakadadcham and D. Moulder
Updated: 10/08/2005
|
|
|
Project Metrics Listings
|
|
Total:
18 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
