Requirements are consistent and complete whether the

This preview shows page 12 - 14 out of 35 pages.

requirements are consistent and complete, whether the project is of good quality or whether the code is ready to be tested. Some project managers measure process and product attribute to be able to tell when the software will be ready for delivery or if the budget will be exceeded. The maintenance can be used the measurement to assess whether the product needs to be improved. As it is an abstract product, measuring the quality of software is an arduous task. In order to contribute to this, software metrics are one way of performing quality control. Product and process metrics are used to address anomalies that may be linked to quality. Measurement is the capture of information about entity attributes . Examples of attributes are the area of a room, the time of a trip or the cost of a software development project. In software engineering, there are three classes of entities: processes, products , and resources. In this case what matters are the product results of activity of the development process. • “External attributes are reliability, ease of comprehension, maintainability, usability, integrity, e±ciency, reusability, portability and interoperability“ (Metricas, 2005, p.24). •” Internal attributes are a little more subjective, for example, speci²cations can be evaluated in terms of size, reuse, redundancy, and syntax correction” (Metricas, 2005, p.24). Users often consider internal attributes as unimportant, as they are primarily concerned with the ²nal functionality, quality, and utility of the software. However, internal attributes can be very useful in suggesting what is likely to be found when evaluating external attributes . For example, knowing the relationship between some internal attributes of the project and the propensity for software failures or di±culty of maintenance, developers want to be able to identify the modules, still in the design stage, whose pro²le, in terms of internal attributes measures , shows that they are likely candidates to later experience some failure or di±culty to maintain. Clarifying then ... the internal attribute “the cyclomatic complexity measures the structural complexity of a process. Translating to the world of software engineering, it measures the structural complexity of a method, class, or any logical unit that can be found in a software system” (Gomede, 2010). Internal attributes such as cyclomatic complexity and external as maintenance have in common the characteristic of being static methods of measurement, which in contrast to dynamics (relatively easy to measure because they are directly related to the quality attributes of the software, such as performance or number of failures), are more complicated to estimate, due to the subjective relationship with quality attributes.
01.04.2019 CS 2401 - AY2019-T3: Week 6 Discussion Question As the theme of this DF itself addresses, it is not impossible to relate these two attributes to measurement, but beyond the addressed at above paragraph there is the fact that cyclomatic complexity as an internal attribute, can be evaluated from the
13/35

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture