DevOps

Conference Presentations

Scripts on My Tool Belt

The aims of this presentation are to: convince you that "test automation" is more than automating test execution; show some examples of the kinds of things that can be accomplished with scripting languages, using simplified code samples; and make you aware of three different scripting languages (shells, perl, and expect).
Danny Faught, Tejas Software Consulting
Failure of a Dot Com-A Case Study

In the new economy, cliches such as "Internet time" can be disastrous. As the market emphasis shifts from first-to-market to first-to-profit, Internet start-ups are forced to scrutinize decisions which directly impact their business model. Learn the steps to failure taken by one dot-com company and the lessons learned from this failed endeavor. Explore the executive decisions made to speed time-to-market and customer acquisition, and discover how product schedules are adversely affected by attempts to retrofit an architecture and introduce tools.
Theresa Lanowitz, Gartner Group
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
Testing in the Extreme Programming World

Much attention has been given to the topic of lightweight development processes-especially eXtreme Programming (XP). Robert Martin explains the concept and significance of a paradigm that believes acceptance tests should be defined by customers, and requires developers to write the unit tests before they write the code. He then separates the difficulties from the benefits inherent in this relatively new discipline. By cutting through the controversy, he's able to address the essential issues such as environmental possibilities and the need for XP. But most importantly, he addresses the question: What is the relevance of software testing and testing professionals within XP?
Robert Martin, Object Mentor, Inc.
The Simplest Automated Unit Test Framework That Could Possibly Work

Everyone pays lip service to the importance of unit testing, but rarely do developers actually integrate unit testing into their daily routine. In the spirit of eXtreme Programming, this presentation offers a simple two-class framework for automating unit tests in three popular languages: C++, Java, and C. No GUI, no templates, just a fast and productive way of organizing and running suites of unit tests. You'll walk away wondering how you have done without this simple technique for so long.
Chuck Allison, Utah Valley State College
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.
Evolution of Automated Testing for Enterprise Systems

The key to accelerating test automation in any project is for a well-rounded, cohesive team to emerge that can marry its business knowledge with its technical expertise. This session is an in-depth case study of the evolution of automated testing at the BNSF Railroad. From record-and-playback to database-driven robust test scripts, this session will take you through each step of the $24 billion corporation's efforts to implement test automation.
Cherie Coles, BNSF Railroad
Communicate and Define the Value of Performance in Dollars and Cents

What is the real value of computing performance improvement? What is the real cost of computing performance degradation? This paper describes an approach used at The Boeing Company to answer these questions. The challenges of presenting technical analyses in "dollars and cents, bottom line" terminology, and sample visual formats for communicating computing performance information
clearly, completely and concisely will be discussed.
Nancy Acree, CAD/CAM Products and Services
Thinking About People, Process, and Product: A Principle that Works at Work

All projects involve the three P's: people, process, and product. People includes everyone who influences the project. Process is the steps taken to produce and maintain software. Product is the final outcome of the project. To keep these three in harmony, you must observe who is trying to do what to deliver what. Usually, two of the three P's are mandated, and the third one is chosen appropriately. Although this is common sense, it is not common practice. Dwayne Phillips discusses the issues and challenges that affect us all on every project. Learn about the ideas and questions to consider to help you work through these issues.
Dwayne Phillips, U.S. Department of Defense

Pages

CMCrossroads is a TechWell community.

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