Software Architecture or Design

Tutorials

Mark Meretzky, New York University

Mon, 06/02/2014 - 8:30am

Join Mark Meretzky to learn how to create Android apps using the Eclipse IDE on Mac, PC, or Linux. The apps Mark demonstrates are composed of objects written in Java, plus a screen layout in XML. Find out how the Java code manipulates the XML to present a user interface including buttons, sliders, and other widgets. Draw text and graphics, respond to a touch or keystroke, and recognize a swipe or pinch. Three important design patterns involve views, which are visible areas on the screen. (1) A listener is an object whose methods are called in response to a stimulus.

ME Acceptance Test-Driven Development: Mastering Agile Testing SOLD OUT

Nate Oster, CodeSquads, LLC

Mon, 06/02/2014 - 8:30am

On agile teams, testers can struggle to keep pace with development if they continue employing a waterfall-based verification process—finding bugs after development. Nate Oster challenges you to question waterfall assumptions and replace this legacy verification testing with acceptance test-driven development (ATDD). With ATDD, you “test first” by writing executable specifications for a new feature before development begins.

MO Essential Test-Driven Development

Rob Myers, Agile Institute

Mon, 06/02/2014 - 1:00pm

Test-driven development (TDD) is a powerful technique for combining software design, unit testing, and coding in a continuous process to increase reliability and produce better code design. Using the TDD approach, developers write programs in very short development cycles. The developer first writes a failing automated test case that defines a new function or improvement, then produces code to pass that test, and finally refactors the new code to acceptable standards. The developer repeats this process many times until the behavior is complete and fully tested.

TA Requirements Engineering: A Hands-On Practicum

Erik van Veenendaal, Improve Quality IT Services BV

Tue, 06/03/2014 - 8:30am

Identifying, documenting, and communicating requirements are key to all successful IT projects. Common problems in requirements engineering are How do we discover the real requirements?, How do we document requirements?, and How do user stories, use cases, and epics fit into requirements? Erik van Veenendaal answers these questions and more while helping you improve your skills in requirements engineering for both traditional and agile projects. With practical case studies and hands-on exercises, Erik illustrates requirements issues and solutions.

TC Leadership and Career Success—On Purpose NEW

James Whittaker, Microsoft

Tue, 06/03/2014 - 8:30am

Line up all the successful people in the world. Take away the pedigreed and the prodigies—you know the people who are going to succeed no matter what. Remove the brown-nosers and right-time-right-place lottery winners. And who do you have left? People who succeeded on purpose. Study these folks carefully, and you’ll find theirs paths to the top have common themes. James Whittaker exposes the career strategies of the ultra-successful and analyzes them in detail.

TF Software Design for Testability

Keith Stobie, Salesforce.com

Tue, 06/03/2014 - 8:30am

Testability is the degree to which a system can be effectively and efficiently tested. This key software attribute indicates whether testing (and subsequent maintenance) will be easy and cheap—or difficult and expensive. In the worst case, a lack of testability means that some components of the system cannot be tested at all.

TN Innovation Thinking: Evolve and Expand Your Capabilities NEW

Jennifer Bonine, tap|QA, Inc.

Tue, 06/03/2014 - 1:00pm

Innovation is a word frequently tossed around in organizations today. The standard cliché is “Do more with less.” People and teams want to be innovative but often struggle with how to define, prioritize, implement, and track their innovation efforts. Jennifer Bonine shares the Innovation Types model to give you new tools to evolve and expand your innovation capabilities. Find out if your innovation ideas and efforts match your team and company goals. Learn how to classify your innovation and improvement efforts as core (to the business) or context (essential but non-revenue generating).

Keynotes

K2 For Maximum Awesome

Joe Justice, Scrum, Inc

Wed, 06/04/2014 - 10:15am

An agile hardware and engineering company of 500 collaborators in twenty countries, Team WIKISPEED uses test-first development practices, is run by Scrum teams, and produces road legal cars, micro-houses, and social-good projects. Joe Justice shares how their 100-MPG road car was created in just three months through object-oriented design, iterative development, and agile project management.

K3 An Agile Throwdown: Munich Takes on the Columbus Agile Benchmark Study

Michael Mah, QSM Associates, Inc.

Thu, 06/05/2014 - 8:30am

Agile has not only gone mainstream, it’s gone global. Data on agile team performance, time-to-market, and quality have emerged in the past decade. In 2012, a group of Columbus, Ohio, companies—business, IT, and financial services firms—participated in the first ever “Columbus Agile vs. the World” study. They collected velocity, schedule, effort, staffing, and quality data which were compared against QSM’s Software Lifecycle Management (SLIM) database. Analysis revealed delivery was 31 percent faster with 75 percent fewer defects than industry norms. Enter Munich, Germany.