-
Notifications
You must be signed in to change notification settings - Fork 2
Metrics
jonaswk edited this page Jul 17, 2017
·
1 revision
In order to use MobSOS with the CAE to get meaningful metrics from its usage, a list of stats worthwhile tracking has to be created. This page lists them and is meant to be the place for discussion and development of those metrics. From this list a MobSOS success model will be created.
- Applications
- Number of services
- Number of frontend components
- Microservices
- Database schema complexity (number of tables, ...)
- API complexity (are services fulfilling a single purpose or more complex ones?)
- Number of endpoints / type of endpoints
- Response media types
- Frontends
- Number of elements (to measure complexity of frontends)
- Number / type of backend calls
- Consumed media types
- General metrics
- Time spent editing
- Model quality
- Component complexity
- Average number of services in application
- Average number of frontend components in application
- Average number of databases in microservice
- Average number of tables in microservice
- Average number of columns in table
- Average number of HTTP methods in microservice
- Average number of HTTP responses in microservice
- Average number of HTTP payloads in microservice
- Average number of Internal Service Calls
- Average number of Service Call Parameters
- Average number of HTML element
- Average number of functions
- Average number of events
- Average number of IWC reponses
- Average number of IWC calls
- Average number of input parameters
- Average number of microservice calls
- Component complexity