|
When Saying Yes Doesn't Help: Software Development as Codependent Behavior Vague requirements, undocumented design, poor code, and impossible schedules-these are the typical complaints of many developers. Whose fault is it? Of course, it is "their" fault-senior management, customers, users, etc. But, could we be part of the problem? Codependent behavior is defined as "a way of getting needs met that doesn't get needs met. We do all the wrong things for all the right reasons." When we agree to develop systems without understanding user needs, we teach others that participation in the project is not important. When we agree to absurd schedules, we teach others that our legitimate needs do not matter. In this compelling session, learn what codependency is, recognize codependent behavior in yourself and others, evaluate the negative effects of codependent behavior, and ways to respond more appropriately to unreasonable demands.
|
Lee Copeland, Software Quality Engineering
|
|
Process Improvement: Based on Models, Implemented in Reality Experience demonstrates that no matter the end product-financial services, insurance, beer, construction, etc.-the foundation for and focus on implementing process improvement remains consistent. Using models as the basis for improving processes makes success more likely; however, no single model has all the right answers. In this presentation, Barbara Ainsworth provides an overview and comparison of popular software process models: Software Engineering Institute's Software CMM® and CMMI®; Project Management Institute’s PMI Common Body of Knowledge; and Quality Assurance Institute's Bodies of Knowledge for Quality Assurance and Testing. See the influence of both the old and new quality masters-Juran, Crosby, Humphrey, and others-and learn from them how to get your process improvement initiative on the right track.
- An overview of popular software process models
|
Barbara Ainsworth, ProcessPlusOne
|
|
Customer Focused Business Metrics throughout the SDLC Focusing on the customer throughout the software development lifecycle (SDLC) is difficult to do. Teams often can become mired in technical problems, internal resource limitations, or other issues. Following the customer mantra of "Faster! Better! Cheaper!" Steve Wrenn offers measurement and process techniques that he has used to deliver projects on time, on budget, and, most importantly, meeting customers needs. By focusing on the development cycle from the outside in, his organization provides business-based metrics dashboards to monitor and adjust the project plan throughout the development project. Find out how their performance dashboard helps the team and the customer stay on course and drive directly to the targeted results. Discover an approach to determine what customers really want and match product development to customer expectations.
|
Steve Wrenn, Liberty Mutual Insurance Information Systems
|
|
Thinking Inside the Box The problem with urging outside-the-box thinking is that many of us do a less-than-stellar job of thinking inside the box. We often fail to realize the options and opportunities that are blatantly visible inside the box that could dramatically improve our chances of success. In this column, Naomi Karten points out how we fall victim to familiar traps, such as doing things the same old (ineffective) way or discounting colleague and teammate ideas. Thinking outside of the box can generate innovative and ingenious ideas and outcomes, but the results will flop when teammates ignore the ideas inside the box.
|
|
|
Testing your Web Site for Privacy, Quality, and Accesibility Today's business world relies heavily on transactions conducted through the web. Because of this, brand image and how a web site is rendered to customers has become increasingly important. A poorly functioning web site poses significant risk for web-based companies. This presentation discusses the challenges involved when testing to ensure the quality of your company's web site and to ensure that the components of the site function properly. With the ever-increasing web complexity, specific tools and processes are required to manage these challenges.
- Discover ways to ensure that your web site reflects your privacy policy
- Learn how to manage your web sites's links to ensure that they remain current and unbroken, and ensure that web content is accessible to users
- Learn about specific tools and processes to test and manage your web site
|
John Burg, IBM Global Services
|
|
Web Application Performance Testing with the Open Source Hyades Project What if you could build and run multi-user performance tests with a free, open source tool? Then, this coming Monday, you could validate multi-user application performance before deploying your application to your users, automate performance tests without spending money, and add additional features and capabilities to the
performance test tool as desired. Join Jeff Robbins to learn about two open source tools, Eclipse and Hyades.
|
Jeff Robbins, IBM Rational Software Group
|
|
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
|