Functional measurement of a software considers various aspects like type and scope of the measurement, appropriate identification of boundaries and correct granularity of BFCs.
These aspects often have different relevance and impact in the various architectures. From the theoretical point of view, technological evolution should not influence functional measurement for an application. When defining the same boundary and identifying the same user functions within an application, functional measurement should not change.
In parallel with evolution of architectures, also user requirement have evolved, digging from the functional level into technical and technological aspects. We are facing a change in level of acknowledgement of application functions and user view of the application, and a variety of counting purposes beyond simple “application sizing”. Therefore, boundaries can be re-defined, for all stakeholders’ advantage, and even measurement granularity can change, as a consequence of this new “user view”.
In this perspective, we will cover following in this webinar - Some counting examples of microservices architectures , comparing measurements with different approaches, and highlighting critical aspects of functional measurement and their relevance on the accuracy of the results.