登录查看更多内容

How can you avoid measurement pitfalls when using system testing metrics in Systems Design?

由人工智能和领英社区提供技术支持

System testing metrics are quantitative measures that help evaluate the quality, performance, and functionality of a system design. However, using them effectively requires careful planning, selection, and interpretation to avoid common measurement pitfalls. In this article, we will discuss some of the best practices and tips to help you use system testing metrics in systems design without falling into traps.

此文章中的业界达人

由社区从 5 条内容中精选。了解更多

Rakesh Kumar Sinha

Technology Lead @ Iris Software | Java | Microservices | Scalable & Resilient Systems | AWS | DevOps | Innovation &…
Rigoberto Zú?iga G

Director de Sistemas | Director de TI | Director de IT | CIO | CTO | Líder de Tecnología | PMO | Experto en…

1 Define your goals and criteria

Before you choose and apply any system testing metrics, you need to have a clear and specific goal and criteria for your system design. What are you trying to achieve? What are the expected outcomes and standards? How will you measure success and failure? By defining your goals and criteria, you can narrow down the relevant and meaningful metrics that align with your system design objectives and avoid irrelevant or misleading ones.

添加您的观点

Rakesh Kumar Sinha

Technology Lead @ Iris Software | Java | Microservices | Scalable & Resilient Systems | AWS | DevOps | Innovation & Growth
举报内容
Defining goals and criteria is crucial in systems design as it ensures that testing metrics are directly tied to the system's intended function and performance expectations. This focus helps in creating a benchmark for success and guides the selection of metrics that provide actionable insights, rather than an overload of data that may not contribute to meaningful improvements or decision-making.

已翻译

赞
Rigoberto Zú?iga G

Director de Sistemas | Director de TI | Director de IT | CIO | CTO | Líder de Tecnología | PMO | Experto en implementación y Optimización de ERP′s: SAP ECC, S/4HANA, Microsoft Dynamics 365 e Intelisis.
举报内容
Debemos considerar que puede haber escenarios diferentes, es decir, si nos dedicamos a desarrollar sistemas "Empresa que se dedica crear aplicaciones" o TI trabaja en una empresa para cubrir los requerimientos del CORE del negocio, son 2 casos diferentes: 1. Si el sistema está dirigido al público o a algún mercado en particular, los objetivos puede ser muy amplios, por lo que se deben acotar los objetivos o seccionar en procesos. 2. Por lo contrario si el sistema va dirigido solo para algunos usuarios en particular de una compa?ía los objetivos son mas chicos "no forzosamente menos complejos"

已翻译

赞
Steve Fouracre

Founder of SES a Salesforce app which vastly speeds up Salesforce development. Also working at Metacube as Head of Salesforce Europe.
举报内容
To know what your key metrics are is crucial. Such as the quantity of defects raised, severity of defects raised, quantity of defects as a ratio to story points because a more complicated story would expect to have more defects raised than a simple story, time to fix defect. Now you know the metrics you will capture you need to ensure the team is capturing these metrics consistently, the scrum master should monitor this on a daily basis.

已翻译

赞

2 Choose appropriate and balanced metrics

There are many types of system testing metrics, such as reliability, usability, efficiency, maintainability, security, and so on. However, not all metrics are equally important or applicable to every system design. You need to choose the metrics that suit your system design context, scope, and complexity, and balance them according to your priorities and trade-offs. For example, if your system design requires high reliability and security, you may focus more on metrics like defect density, mean time to failure, or vulnerability detection, and less on metrics like user satisfaction or response time.

添加您的观点

Rigoberto Zú?iga G

Director de Sistemas | Director de TI | Director de IT | CIO | CTO | Líder de Tecnología | PMO | Experto en implementación y Optimización de ERP′s: SAP ECC, S/4HANA, Microsoft Dynamics 365 e Intelisis.
举报内容
Este tema igualmente es complejo al tener varios escenarios, e independientemente de que las pruebas a realizarse deben ser muy completas y exhaustivas, debemos recordar que además de hacer nosotros "como expertos en TI" las pruebas, en quienes debemos apoyarnos más es en los clientes y/o usuarios que son expertos en el proceso, y saben todos los múltiples escenarios que se pueden presentar, esto es lo más importante-

已翻译

赞

3 Collect accurate and consistent data

The quality and validity of your system testing metrics depend largely on the data you collect during the testing process. You need to ensure that your data is accurate, reliable, and consistent, and that you use the same methods, tools, and standards for data collection and analysis. You also need to avoid any biases, errors, or anomalies that may skew your data and affect your results. For example, you may use automated tools or scripts to collect data, check for data integrity and validity, and use statistical methods to identify and remove outliers or noise.

添加您的观点

Rigoberto Zú?iga G

Director de Sistemas | Director de TI | Director de IT | CIO | CTO | Líder de Tecnología | PMO | Experto en implementación y Optimización de ERP′s: SAP ECC, S/4HANA, Microsoft Dynamics 365 e Intelisis.
举报内容
Aquí lo más importante es considerar una muestra de datos lo mas completa posible apegada a la realidad, y de la misma forma considerar información real, información que es la que se usa en el proceso, no podemos inventar los datos con los que se probaran las aplicaciones pues los resultados serán NO fiables.

已翻译

赞

4 Interpret and communicate results effectively

Once you have collected and analyzed your data, you need to interpret and communicate your system testing metrics results in a way that is clear, concise, and actionable. You need to understand what the metrics mean, how they relate to your goals and criteria, and what implications they have for your system design decisions and actions. You also need to present your results in a format that is easy to understand and compare, such as tables, charts, or dashboards. For example, you may use SMART (Specific, Measurable, Achievable, Relevant, and Time-bound) criteria to interpret your results, and use KPIs (Key Performance Indicators) to communicate your results.

添加您的观点

5 Review and improve your metrics

System testing metrics are not static or fixed. They are dynamic and evolving, as your system design changes and improves over time. You need to review and improve your metrics regularly, to ensure that they are still valid, relevant, and useful for your system design evaluation. You also need to monitor and track your metrics over time, to identify any trends, patterns, or changes that may indicate problems or opportunities for improvement. For example, you may use PDCA (Plan, Do, Check, Act) cycle to review and improve your metrics, and use control charts or histograms to monitor and track your metrics.

添加您的观点

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?

添加您的观点

Systems Design

+ 关注

给文章评分

我们借助人工智能创建了此文章。您认为这篇文章怎么样？

很棒不太好

举报此文章

查看全部

How can you avoid measurement pitfalls when using system testing metrics in Systems Design?

1

2

3

4

5

6

1 Define your goals and criteria

2 Choose appropriate and balanced metrics

3 Collect accurate and consistent data

4 Interpret and communicate results effectively

5 Review and improve your metrics

6 Here’s what else to consider

Systems Design

给文章评分

感谢您的反馈

更多Systems Design相关文章

更多相关阅读内容

How can you avoid measurement pitfalls when using system testing metrics in Systems Design?

1

2

3

4

5

6

1 Define your goals and criteria

2 Choose appropriate and balanced metrics

3 Collect accurate and consistent data

4 Interpret and communicate results effectively

5 Review and improve your metrics

6 Here’s what else to consider

Systems Design

给文章评分

感谢您的反馈

查看其他技能