Measurement Essay Example
Purpose of measurement is for understanding, control and improvement. Describe an aspect or incident of your life where this was true
During my experience at work, I have been constantly confronted with new technologies, competitive markets as well as more competition for experienced staff and demands for more rapid responsiveness. Therefore, I have witnessed measurement assisting in understanding, controlling and improving such aspects. This is because the above aspects necessitate understanding and controlling of uncontrolled changes, inadequate testing, insufficient training, inadequate funds and matters allied to standards, reliability and appropriateness of products and services. Therefore, measurement helped in clarifying and understanding these problems even if it did not solve them. In addition, measurements were also used in measuring quality aspects of products and processes that provided efficient foundation to initiate and manage process development and improvement activities. This is in line with Carleton et al (1998) who explain that measurements assist in enabling understanding and hence helps to develop attainable plans to produce and deliver products and services. Measurements also allow individuals to detect trends as well as predict problems and hence provide better and improved costs’ control, decreases risks, improves quality and also ensure that business goals are accomplished (Carleton et al, 1998).
Explain what cost and effort estimation is about
Estimation refers to the process of determining an estimate, which the value that can be utilized for some objective even if input data might be deficient, tentative, or unstable. Estimation establishes how much effort, finances, time and resources it will take to develop a certain system or product. The basis of estimation is on the past data/experience; available knowledge, hypothesis, as well as identified risks (Dolado, 2001).
The key elements of project costs include; hardware costs, travel/training costs and effort costs which are the costs for software engineers’ pay.
Effort cost is the dominant cost and the most challenging estimate to estimate and significantly affects the overall cost. It is important to ensure that software costing is performed objectively in order to accurately predict the cost of the engineer developing the software. Software cost estimation begins during the proposal phase and continues throughout the project’s lifetime and hence it is a constant activity (Dolado, 2001). Measurement of efforts can be done in terms of staff-hours or staff-months.
Representation condition of measurement
Representation condition of measurement refers to behavior of measures within number system requirements to be equivalent to the correlating components within the real world. Basically, a measurement that maps M should chart units into numbers and empirical correlations into numerical correlations in such a manner that empirical correlations preserve numerical correlations and empirical correlations are preserved using numerical correlations (Fenton, 1994). For example, taller than representation condition where A is taller than B iff M (A) > M(B), where M represents a mapping from the experiential world to the actual numbers. Whenever Hans is taller than Sam, the M (Hans) should be a greater number than M (Sam) and mapping of Mercy can be to a greater number than Faustin only if Mercy is taller than Faustin. The representation condition may also be used indicate software failures criticality and kinds of failures assessed include: deferred response, inaccurate output, and loss of data. At this point, the system relation includes 3 unary correlations namely; F1 for deferred response, F2 for inaccurate output, and R3 for loss of data.
Explain why software reliability modelling is a type of measurement
Software reliability is a type of measurement because it plays a significant role in measuring progresses, accomplishing efficient and effective test scheduling during the software development project, deciding on when to release a product or estimation of the number of service releases needed following a release to achieve a reliability target (Lin & Huang, 2008). Therefore, this is why there are statistical metrics to monitor the reliability and quality improvements. There are 2 strategies that are used to perform statistical reliability prediction for software and the basis of one strategy is on design parameters, estimating the number of defects within the software utilizing code traits for example the number of code line, loops nesting, external references, as well as input and output calls, among other elements. The other approach is about reliability growth analysis whose basis is on statistical comparisons of the authentic defect detection data acquired while testing. Software reliability modeling generates valid estimations of the future reliability of the software and also provides estimations adequately early during testing phase (Lin & Huang, 2008).
Dolado, J. J, 2001, «On the problem of the software cost function.» Information and Software Technology 43(1): 61-72.
Carleton A, Robert F & William F, 1998, Practical Software Measurement: Measuring for Process Management and Improvement, Pittsburg: Carnegie Mellon University.
Fenton, N., 1994, Software measurement: A necessary scientific basis. IEEE Transactions on software engineering, 20(3), pp.199-206.
Lin, C.T. & Huang, C.Y., 2008, Enhancing and measuring the predictive capabilities of testing-effort dependent software reliability models. Journal of Systems and Software, 81(6), pp.1025-1038.
More Important Things