12ICSQ

12th International Conference on Software Quality

Software Division of
The American Society for Quality

Home ] Up ] 13ICSQ Program ] Sponsor & Exhibitor Opportunities ] Special Needs ] Dallas Info ] Hotel/Airline/Rental Car/Driving Directions ] Paper & Tutorial Presenter Information ] Volunteers Opportunities ] ICSQ History.htm ] Contact Us ] About ASQ ]

 

Home
Up
Tutorial Descriptions
Tuesday Presentations
Wednesday Presentations
Tim Lister
John Musa
Alain Abran
Scott Ambler
Kevin Daily
Alec Dorling
Liz Keim
Tom McCabe
Linda Westfall

 

Scott Ambler - Invited Speaker

Scott Ambler is a Senior Consultant with  Ronin International, Inc. since its inception in 1999.  He actively works with Ronin clients on large-scale software development projects and on software process improvement (SPI) efforts around the world. 

Scott is Canadian and still lives in Canada although he spends a large portion of his time consulting in the United States and Europe.  He has worked in the IT industry since the mid 1980s and with object technology since the early 1990s. He has written several books and white papers on object-oriented software development, software process, Agile Modeling (AM), and other topics.

Scott is a Senior Contributing Editor with Software Development magazine.  

 

1.1.1       Agile Modeling Agile Modeling (AM)

1.1.2       Enterprise Unified Process (EUP)

In the Autumn of 1999, Scott initially proposed a new instantiation of the Unified Process within the pages of Software Development that eventually evolved into the EUP.  You can read about it in Ronin's white paper Enhancing the Unified Process and in the four books that Scott co-edited with Larry Constantine:

1.1.3       Object-Oriented (OO) Development

Most of the development work that Scott does involves object and component technology, usually Java but not always.  Scott is the author of two books written for developers about object-oriented development, The Object Primer 2/e (2001), read about it in Ronin's white paper The Object Primer: An Introduction to Techniques for Agile Modeling, and the award-winning Building Object Applications That Work (1997). He is also the author of Process Patterns (1998) and More Process Patterns (1999) which describe a prescriptive methodology for large-scale, object-oriented development. Scott also shares many of his writings online as well, so feel free to browse.

1.1.4       Object Persistence

Scott has been involved with several large projects where the persistence of objects was a primary concern. He has written about his techniques for doing so in The Object Primer 2/e (2001), describing the development of a business application, and in Mapping Objects to RDBS, Design of a Robust Persistence Layer, and Data Refactoring white papers.  Scott is still amazed that the object community still has not embraced the fact that we need to include physical data modeling within our processes and data models as first class artifacts.  

1.1.5       Java and EJB Development

Scott has been developing in Java since 1995 and with Enterprise JavaBeans (EJB) since 1999.  He's been lucky enough to co-author two books, The Elements of Java Style (2000) and Mastering EJB 2/e (2002), with a great bunch of folks.  He is also the author of The AmbySoft Inc. Coding Standards for Java.

Agile Modeling and Software Quality

Agile software development has taken the development world by storm.  Although its detractors may tell you that itís a fad the reality is that it is here to stay.  In this presentation I will overview of the values and principles of agile software development (www.agilealliance.org) and then focus in on the Agile Modeling (AM) methodology (www.agilemodeling.com), a chaordic process for effective modeling and documentation.  AM presents challenges for anyone trying to validate the resulting artifacts for two reasons:  First, AM is practices-based but not prescriptive providing developers the freedom to do the right thing instead of what some burdensome process tells them to create.  Second, one of its underlying philosophies is that models and documents just need to be good enough.  Donít worry; these issues can easily be overcome.  Iíll describe techniques for validating agile models and documents, arguing that quality assurance professionals will need to rethink some of their current practices if they wish to be effective in this new world order.