|
|
|
Better Software Conference & EXPO 2006 Concurrent Sessions
Go To: Agile Development | Managing Projects and Teams | Measurement | Outsourcing | Plan-Driven Development |
Process Improvement | Quality Assurance | Security | Special Topics | System Requirements | Testing
View by Date
| Special Topics | | | Wednesday, June 28, 2006 11:30 AM |
Sarbanes and Oxley: Your New Partners in Software Development
Elle Ringham, Fidelity National Financial
Determining whether legal and contractual issues apply to your development efforts isn't always simple. There may be some obvious factors: a well-regulated industry, service level agreements, or state or federal agency oversight. However, other factors may not be so obvious. The new Sarbanes-Oxley Act is largely legally untested, subjecting your company to unknown legal issues. You have an eCommerce site that stores credit card information. Your portal collects personal information. You produce proprietary software . . . and more. Does Sarbanes-Oxley apply to you? Covering legal, compliance, and audit throughout the development lifecycle, Elle Ringham discusses the right questions to ask and what to do with the answers. She provides guidelines for working with stakeholders, attorneys, and auditors. Take away audit templates, metrics to help you, and sample reports you may need to produce.
� Legal and compliance issues within software development and QA
• Questions to ask and what to do with the answers you get
• Report the results of compliance tests |
| | | Wednesday, June 28, 2006 1:45 PM |
Web Services Interface Design: Pitfalls and Proven Techniques
Dave Mount, J-Soup Software, Inc
Designing Web services is all about the interface. Although tools for Web services development have advanced to the point where exposing application functionality is simple, the ease of building Web services does not diminish the need for careful planning and a highly functional design. Dave Mount opens his presentation by spinning the cautionary tale of slapping together a Web services interface on a poorly structured application. This scenario serves as a reference point for a subsequent discussion of the pitfalls of a poorly designed interface. Dave illustrates techniques for correcting problems and improving the Web services interface. Looking at high profile Web services provided by Google, eBay, and Salesforce.com, he shows how an external perspective that emphasizes consistency and conceptual clarity is key to Web services interface design.
� Web services designs that expose functionality while masking application messiness
• XML data types that improve data organization and maximize interoperability
• How to enforce security and avoid opening back doors to the underlying application |
| | | Wednesday, June 28, 2006 3:00 PM |
Building Traceable UML Models
Thomas Bullinger, ArchSynergy, Ltd.
While effective for modeling requirements, analysis, or design of a software system, UML diagrams are typically used in isolation or only for portions of a system. The resulting inconsistencies have the potential to create more confusion than clarity, negating the investment in the modeling process. Explore tips, tricks, and techniques to build a complete, traceable UML model for all aspects of a software application. Thomas Bullinger shares ways to gather behavioral requirements and map them into UML use cases. Learn to map use cases onto sequence or activity diagrams and extract them onto class diagrams. In a recursive process, each of the UML diagrams and associated descriptions is logically related to ensure a complete problem model and a consistent design solution.
� Create self-consistent UML models of requirements behavior and designs
• Manage change in UML models to reflect updates to requirements
• Use UML models to facilitate communications and learning |
| | | Thursday, June 29, 2006 9:45 AM |
Lightning Talks: A Potpourri of 5-Minute Presentations
Julie Gardiner, QST Consultants Ltd.
Lightning Talks are nine five-minute talks in a fifty-minute time period. Lightning Talks represent a much smaller investment of time than track speaking and offer the chance to try conference speaking without the heavy commitment. Lightning Talks are an opportunity to quickly present your single, biggest, bang-for-the-buck idea. Maybe you just want to ask a question, invite people to help you with your project, boast about something you did, or tell a short cautionary story. These things are all interesting and worth talking about, but there might not be enough to say about them to fill up a full track presentation. Use this as your opportunity to give a first time talk or to present a new topic for the first time. For more information on how to submit your Lightning Talk, visit www.sqe.com/lightningtalks.asp. Hurry! The deadline for submissions is May 8, 2006. |
| | | Thursday, June 29, 2006 11:15 AM |
Beat the Odds in Vega$: Measurement Theory Applied to Development and Testing
James McCaffrey, Volt Information Sciences, Inc.
James McCaffrey describes in detail how to use measurement theory to create a simple software system that predicts with 87% accuracy the results of NFL professional football game scores. So, what does this have to do with a conference about developing better software? You can apply the same measurement theory principles embedded in this program to more accurately predict or compare results of software development, testing, and management. Using the information James presents, you can extend the system to predict the scores in other sports and apply the principles to a wide range of software engineering problems such as predicting the Web site usage in a new system, evaluating the overall quality of similar systems, and much more.
� Why the statistical approach does not work for making some accurate predictions
• Measurement theory to predict and compare
• How to use rank order centroids to compare the quality of similar software applications |
| | | Thursday, June 29, 2006 1:30 PM |
Validation: What It Means in an FDA Regulated Environment
Chrys Kyee, Genentech Inc
Even though formal validation may not be required in unregulated environments, many mission-critical applications could benefit from performing some of the same activities required for FDA regulated systems. Validation provides documented evidence showing, with a high degree of assurance, that a system will consistently meet its predetermined requirements. FDA validation is required if the use of the computer system could potentially impact product quality, safety, or efficacy, or if the system is used to support a regulatory submission function. Learn how validation is accomplished by looking at a series of qualification exercises typically prescribed in a Validation Protocol. Take back with you templates for a typical Validation Protocol, including the System Development Review, Installation Qualification, Operational Qualification, Performance Qualification, and Revalidation. See how your review and test practices can benefit from aspects of the rigor required for regulated software.
� The scope of validation�who, what, when, how, and why
• Templates and a sample OQ script
• Good documentation practices as specified for FDA regulated software |
| | | Thursday, June 29, 2006 3:00 PM |
A Bug�s Life
Lloyd Roden, Grove Consultants
The quality of software is directly related to the number and severity of bugs in software when it goes into production. Inspired by the Disney� film of the same name, Lloyd Roden offers a light-hearted, humorous presentation with a serious message�neglect the bugs and they will take over! Learn about novel strategies to detect and fix bugs before they bite you. Find out ways to change your environment to make it less likely to attract bugs and easier to exterminate the ones that do invade your software. Explore the people issues that can cause unnecessary stress and concern for everyone involved in dealing with bugs in the development process. Take back a new attitude about bugs and a new energy to eradicate them in your house.
� How to find the different types of software bugs
• The environment where bugs are most likely to live
• People issues surrounding bugs |
| |
|
|
