requirements

Conference Presentations

Requirements Are Requirements Are Requirements - Not!

"This isn't what I need," states Customer Bob. "But it's what you said you wanted," replies Engineer Joe. "It's not right. I need something else." We've all encountered this classic users-don't-know-what-they-want scenario. The fact that software professionals continue to have this same experience over and over again suggests that we're overlooking the real reasons for the user/engineer disconnect. This presentation contrasts the different uses of the term "requirements" as it explores the possible solutions to improving understanding between business people and technical people.

Robin Goldsmith, GoPro Management, Inc.
Get Real! Creating Realistic, Actionable Project Schedules

The preparation of a realistic, practical project schedule is an essential management function for obtaining stakeholder commitment, setting expectations, and communicating within the team and organization what is achievable. Doing this preparation well is another challenge-one that must be conquered. Rex Black helps participants see the bigger project scheduling picture by focusing on issues such as constituent tasks, the underlying dependencies between them, and the risks attached to the completion of those tasks.

Rex Black, Rex Black Consulting Services, Inc.
Applying Development Best Practices to Automated Testing

Test automation is a specialized form of software development where executable code is produced for the validation and testing process. Many best practices have been identified to allow developers to code more quickly, efficiently, and correctly, but few test automators have adopted these practices. Learn about several of these "best practices"-including code reviews and coding standards-that can be applied to automated test development. Discover how you, as an automated test developer, can capitalize on the benefits provided by these practices.

Andy Tinkham, Spherion Technology Architects
Requirements-Driven Automated Testing

Studies have shown that over fifty percent of software defects are attributed to poorly defined requirements. From a process improvement perspective, it is imperative that project managers establish a more effective and efficient way of defining and tracking business requirements. Jeff Tatelman describes a "how to" approach for developing a practical automated regression testing process using a traceability matrix and business event scenarios. Learn how requirements-based testing-coupled with a data-driven approach to test automation-can solve problems that plague most software development projects.

Jeff Tatelman, Spherion Technology Architects
Achieving eBusiness Quality by Design

Testing can identify software defects, but it cannot prevent them. This presentation examines the opportunity for testers to engage in achieving eBusiness quality from the beginning of the development lifecycle. Architectural process and application of patterns can have a significant impact on eBusiness quality. Yet testing technology and testers' efforts have largely focused in the opposite direction-on deriving tests from the "as-built" system. Learn how to architect testable Web applications and develop test designs and test in parallel with the design and development of your Web-based application.

Sam Guckenheimer, Rational Software Corporation
Establishing Best Testing Practices in Your Organization

The path to best testing practices begins with communication. By building relationships with a product's key players-developers, analysts, and end users-your test team can achieve a higher level of both quality and customer satisfaction. Discover the link between effective communication and implementing critical step-by-step test processes such as test conditions, test case design, test data construction, and reporting.

Michelle Lynn Baldwin, Booz, Allen & Hamilton
Test Progress Reporting Using Functional Readiness

Are you looking for a way to effectively set the expectations of senior management? The Functional Readiness Matrix (FRM) is a decision-making tool that offers a simple way to represent test progress based on the functional areas or features of an application. By enabling the test team to track actual test progress against the implementation goals established early on, the FRM allows for the presentation of valid test metrics to management in a way they can understand.

Robyn Brilliant, Fannie Mae
The Dangers of Use Cases Employed as Test Cases

Use cases are a great way to organize and document a software system's functionality from the user's perspective. However, they have limited uses for testers. They are great vehicles to accomplish some tasks, and not so great for others. Understand what you're trying to accomplish by testing before deciding if use cases can help-and be cognizant of the challenges they present. They are useful to testers, but not for every situation.

Bernie Berger, Test Assured, Inc.
Testing an eCommerce Shopping Cart Site

Karen Johnson takes attendees through a shopping session that recreates a number of possible scenarios-and highlights what can go wrong. She'll also explain how to prevent defects from going live on your production Web site. From securing transactions to managing cart contents, this talk is a must for anyone involved in the eCommerce arena.

Karen N. Johnson, Peapod, Inc.
Managing the Test Effort Using Requirements-Based Testing Metrics

It's difficult to quantify the true state of a test effort. Often, it's measured by quantity of work combined with deadline compliance. But if this is the case, then the true level of quality remains unknown. The Requirements-Based Testing (RBT) process offers a set of metrics that can be utilized throughout the development cycle. These metrics can provide an accurate picture of the test effort at any given time.

Gary Mogyorodi, Bit Inc.

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.