|
|
Objective Measures from Model-Based Testing Many businesses are looking for the right project measures as they relate to project planning, scheduling, and performance. Mark Blackburn gives guidance on defining, collecting, and analyzing measures derived from a model-based testing method. These measures and their use are described in terms of an information model adapted from the ISO/IEC 15939, Software Engineering-Software Measurement Process. The model-based method associated with these measures involves modeling requirements and mapping modeled requirement variables, referred to as object mappings, to interfaces of the target test system.
- Fundamental units of measure derived from model-based artifacts
- Graphical representations of measures and how to use them to estimate project duration
- Real-time project data used to predict the completion of an ongoing project
|
Mark Blackburn, Software Productivity Consortium
|
|
|
Test Metrics: A Practical Approach To Tracking and Interpretation You can improve the overall quality of a software project through the use of test metrics. Test metrics can be used to track and measure the efficiency, effectiveness, and the success or shortcomings of various activities of a software development project. While it is important to recognize the value of gathering test metrics data, it is the interpretation of that data which makes the metrics meaningful or not. Shaun Bradshaw describes the metrics he tracks during a test effort and explains how to interpret the metrics so they are meaningful to the project and its team members.
- What types of test metrics should be tracked
- How to track and interpret test metrics
- The two categories of test metrics: base and calculated
|
Shaun Bradshaw, Questcon Technologies Inc
|
|
|
Beyond GUI: What You Need to Know about Database Testing Today's complex software systems access heterogeneous data from a variety of back-end databases. The intricate mix of client-server and Web-enabled database applications are extremely difficult to test productively. Testing at the data access layer is the point at which your application
communicates with the database. Tests at this level are vital to improve not only your overall test strategy, but also your product's quality. Mary Sweeney explains what you need to know to test the SQL database engine, stored procedures, and data views. Find out how to design effective automated tests that exercise the complete database layer of your applications. You'll learn about the most common and vexing defects related to SQL databases and the best tools available to support your testing efforts.
|
Mary Sweeney, Exceed Training
|
|
|
High Volume Test Automation Most test design starts from the premise that extensive testing is not possible--too may tests, not enough time. What if we could generate millions of tests, execute them, and evaluate them automatically. This would dramatically change your approach to test planning. Learn how to perform this style of automation using free scripting tools (such as Ruby or Python) that are reasonably priced and easy to learn. Also, to use the system test automation tool you already use (but in a different way) or collaborating with your developers to build test diagnostics and execution support into the software. Cem Kaner describes several examples of high volume automated testing, lays out a structure for thinking about this style of testing, and suggests ideas for trying it in your shop.
|
Cem Kaner, Florida Institute of Technology
|
|
|
State of the Practice in Application Development: A Basis for Benchmarking This presentation explains why knowing broad industry trends regarding application development is not enough to ensure a successful project. AD should be tightly bound to businesses. Existing measures need to be reviewed and service levels for usefulness in measuring attainment of goals that directly support each line of business need to be considered. Read on as the author details these and other important points.
|
Robert Solon, Gartner Inc
|
|
|
High-Maturity Measurement This article will teach you how to: identify current problems with your organization's Level 3 implementation that will inhibit Level 4 implementation, explain the practices that are essential to implementing Level 4
and the basic quantitative management principles, describe how projects are planned at Level 4, and the purpose
of project and organizational goals, and describe the problems with and proper use of control charts and other statistical methods.
|
Beth Layman, TeraQuest Metrics Inc
|
|
|
Techniques for Measuring Software Quality A software defect is any flaw or imperfection in a software work product. A software defect is the result of a mistake in the design of a software process. In this article you will learn and gain an understanding of the software measurement processes, practices, and methods for: managing the quality of software products, improving the quality of software processes and procedures, and applying quantitative principles to your work for measuring quality.
|
James Rozum, Union Switch & Signal Inc
|
|
|
Improving Measurement Capability Following CMM can lead to improvements in: productivity, early detection of defects, reduction in time to market, and a reduction in post-release defects. Some indirect benefits can include: minimized risk through increased management visibility and tracking, and a framework for improvement and objective assessment/comparison.
|
Beth Layman, TeraQuest Metrics Inc
|
|
|
12 Steps to a Successful Metrics Program Software metrics are an integral part of the state-of-the-practice in software engineering. More and more customers are specifying quality metrics reporting as part of their contractual requirements. Companies are using metrics to better understand, track, control, and predict software projects and products. This paper explains the basic concepts of metrics and measurement theory and how those
concepts relate to software.
|
Linda Westfall, The Westfall Team
|
|
|
Paradigms Lost, Paradigms Tossed: New Perspectives for Test Management A paradigm is a set of rules and regulations that does two things: it establishes or defines boundaries; and it tells you how to be successful inside the boundaries. This paper discusses why paradigms are important and how they relate to test management.
|
Harry Robinson, Microsoft Corporation
|
