Performance Test load Model (7)

In many cases, the system that we want to sort out the business scenario is a brand-new product or a new business. In this case, when analyzing the requirements of scenario modeling, not to mention the original data, even comparable similar systems do not have, at this time, we have no data to refer to. At this time, we can only observe the functional modules of the product or business and users, combined with classical mathematical modeling methods for modeling. I use this way of observation as a bystander perspective modeling method.

Spectator perspective

This bystander perspective usually focuses on a certain focus to observe a certain aspect of the system. For example, for a system, we can take the system function module as the center, user activity as the center, system role as the center and so on. We call it product-centered, activity-centered and role-centered modeling methods respectively.

When modeling, it is a good choice to estimate with the principle of 80-20. For example, our estimation principles for different perspectives are as follows:

Product-centric modeling: 80% of business processes are done by 20% of functions

Activity-centric modeling: 80% of things are done in 20% of the time

Role-centric modeling: 80% of data processing is done by 20% of role users

.

After the above estimates, the product-centric perspective can tell us which functions to test, and the activity-centric perspective can tell us at least how much time we need to test. the role-centric perspective tells us which users to choose when testing.

By comprehensively summarizing the data observed from different perspectives, we can get the key information that needs to be mined in our business scene modeling theory, which is our business scene model.