Metrics Estimation Analysis And Team Assignment Essay

Metrics Estimation Analysis And Team Assignment - Essay Example Various organizations have their specific measures that yield their desired goals; as well failure to measure project progress and performance reduces levels of monitoring and evaluation. Measurements are crucial in problem identification, the position of a certain program and their respective processes. It is good to pinpoint mistakes and errors at the initial stages by use of appropriate measurement tool which yields a more quantifiable accurateness of more complex projects (Pressman 2006). Metrics in its innate form can identify critical risks and accord resolutions before they happen. Importance of measurements therefore, is crucial a strategic, technical and project level. The goals of an organization are initially done before listing questions and identifying the measures to be undertaken. In order to have successful project development, the measures should each have attributes, evaluation, unit and counting rule. The measures are: 1. Support Definition: The supportability of a system e.g. software can be measured by tracking specific pertinent supportability features. The developer and acquirer have the opportunity to obtain knowledge which can be directed to supportability control. The systems support can be described in the form of memory size, I/O (input and output), the process, average module size, module complexity, error rate, supportability and lines of code change. Counting and Measurement: The metric can measure spare memory over time which should not be below any specification requirement. Metrics also tracks amounts of I/O that are reserved as functions of time again the capacity should not be below the given requirements. On the process, throughput capacity entails the amount of time and should not be below specification requirements. Average module size should not exceed requirement specification. Similar scenarios can be recorded by knowing the number of errors, average time required and average lines of code changed per deficiency. Estimation: the measurements need to start at project level and should include project planning, monitoring which will entirely depend on the gathered information through the process of measurement (Pressman 2006) Ana lysis: metrics used are representations of software and the process yielding them. Advanced process metrics is as a result of more mature software development process. It requires accurate data to provide good metrics process. There are indicators that are brought out by measurement of data. The indicator quality influences the analysis process since both objective and subjective measures are required when determining the current program state. The objective data constitutes staff hours, software lines of code, current function points, the prevailing components, list of items to be tested, number of coded units and the potentiality of changes and errors. On the other hand, subjective data could be based on the feelings of individuals or groups comprehension of certain features. Collected data must determine issues to be addressed, which requires understanding of metric meanings through performing multiple data sourcing, studying the data collection process at a lower level, separati on of collected data, emphasizing on different data sources and realizing the development process. 2. Risk Definition: To run projects effectively, risks have to be identified and solutions given appropriately. The users should beware of existing and potential limitations and give actions appropriately. There is good knowledge on the levels of risks that can occur in software development environments. To avoid risks understanding of all phases and data