|
|
A Rigorous and Highly Effective Approach to Website Load Testing In this presentation, you will learn how to leverage the power of modern load testing tools to avoid misleading conclusions, and obtain accurate and reliable results by
applying a proven, rigorous, and methodical approach to the three phases of website load testing: planning, execution, and analysis.
|
Alberto Savoia, Keynote Systems
|
|
|
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
|
|
|
No Best Practices: How to Think About Methodology How do the things you hear at a conference relate to the choices you make on the job? If you really want to help improve how your projects work, don't be a passive transceiver of "best practices." Instead, be an active thinker who understands why methods work and when to apply them. James Bach illustrates how some often-recommended practices aren't necessarily helpful unless you use your skill and judgment to adapt them to your particular situation.
|
James Bach, Satisfice, Inc.
|
|
|
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
|
|
|
A Framework for Testing Real-Time and Embedded Systems What do we mean when we say local, remote, simultaneous, and distributed testing? Alan Haffenden of The Open Group explores the differences, and explains why the architecture of a distributed test execution system must be different from that of non-distributed systems. An overview of POSIX 1003.13 profiles and units of functionality helps advanced users build a good foundation for testing both their real-time and embedded systems.
|
Alan Haffenden, The Open Group
|
|
|
Managing Iterative Development: Avoiding Common Pitfalls The Rational Unified Process (RUP) advocates an iterative or spiral approach to the software development lifecycle, as this approach has again and again proven to be superior to the waterfall approach in many respects. But do not believe for one second that the many benefits an iterative lifecycle provides come for free. Iterative development is not a magic wand that when waved solves all possible problems or difficulties in software development. Projects are not easier to set up, to plan, or to control just because they are iterative. The project manager will actually have a more challenging task, especially during his or her first iterative project, and most certainly during the early iterations of that project, when risks are high and early failure possible.
|
Per Kroll, Rational
|
|
|
eXtreme Programming: Managing Agile Development Extreme Programming (XP) has captured the attention of the industry by challenging many cherished beliefs held about software development and management. Not only that, it's actually delivered against those challenges. As a development process, XP focuses on producing sound software architectures while delivering required functionality to customers on time and within budget. It uses iterative development along with other controversial yet effective techniques to get the job done. Robert Martin gives us the real scoop on why XP has enjoyed so many successes, and how it can and will continue to flourish in business development environments.
|
Robert Martin, Object Mentor, Inc.
|
|
|
Mentors, Models, and the Making of Managers: Special Panel Discussion Each of us has a story about how we came to be managers in software organizations. Many of us became managers because we were good developers. Some of us studied management in school. A few of us were groomed and mentored by the companies we work for, and some were tapped for management because we were the only warm body available. But now that we're here, what does it take to become an effective manager? Is being mentored and developed as a manager considered a luxury? Join this interactive panel and discuss the real-life issues and challenges of developing ourselves-and others-as software managers.
|
Moderator: Esther Derby ( Esther Derby Associates, Inc.)
|
|
|
Read My Lips: No New Models! These days, it seems everyone who wants to make a mark in the software world feels the need to invent a new model or methodology. While such models provide useful frameworks for structuring our thinking and practices, enough already! Karl Wiegers contends we don't need any more new and improved models for software engineering. Rather, we need to encourage a majority of developers to consistently and effectively apply the practices that have already been shown to work.
|
Karl Wiegers, Process Impact
|
|
|
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
|
