New England Software Symposium
March 10 - 12, 2006 - Boston, MA
View the event details here ».
Ian Roughley is a speaker, author, and consultant based in Boston, MA, where he runs From Down & Around, Inc., a consultancy specializing in architecture, development, and process improvement services. For more than 10 years, he has been helping clients ranging in size from Fortune 10 companies to start-ups.
Focused on a pragmatic and results-based approach, he is a proponent for open source, as well as process and quality improvements through agile development techniques.
Ian is a committer on the XWork and WebWork projects; member of the Apache Struts PMC; and speaks at conferences in the United States and abroad. He is also a Sun Certified Java Programmer and J2EE Enterprise Architect and an IBM Certified Solutions Architect.
This presentation introduces the features of Struts2, and the framework differences between it and Struts, by iteratively migrating a simple application in 8 steps.
The presentation covers topics including running Struts and Struts2 in the same web application, configuration differences, Struts2 Tags, dependency injection, interceptors, validation, using models and data conversion.
Many companies and most, if not all, software today utilizes open source. Whether it is databases, application servers, frameworks or libraries, these projects are fast becoming a standard commodity for building business-related functionality upon and speeding up development time. Sometimes technology evaluations are done, but frequently the library is simply slipped into the code base to address an urgent requirement - often without evaluating the technology beyond the immediate need.
In this talk I will address this and many other facets that need to be considered when utilizing open source in your project – how open source evaluation should be different from other product evaluation; guidelines for implementing corporate procedures; the benefits of companies contributing back into the open source community; and legal aspects that every developer should be aware of.
Code coverage is generally viewed as a metrics that managers use to chart progress, a number that has to be blindly attained. In this talk we discuss everything that you, the developer, need to know to make it more than a number and part of a process that will improve code quality.
We will cover what code coverage is and what it can do for you; how it can be incorporated into your development and build processes; and how to interpret the results. Finally, alternate usage scenarios will be discussed that will help you better understand the application you are building.