Wat we doen
09.15 Clean Architecture & Design
10.15 Architecture: The Real Software Crisis
11.15 Short break
11.30 Break-out sessions
13.15 Break-out sessions
14.00 Short break
14.15 Agility & Architecture
15.15 Specification Discipline
Robert Cecil Martin, colloquially known as "Uncle Bob", is best known for promoting several software design principles, and for being one of the authors of the Agile Manifesto. He was also the editor-in-chief of C++ Report magazine and served as the first chairman of the Agile Alliance.
Martin has authored numerous books and magazine articles, many of which describe the design principles he promotes. He is also an outspoken advocate of Software craftsmanship, Agile software development, and Test-driven development.
Today he will bring us 4 tracks:
Clean Architecture and Design
So we've heard the message about Clean Code. And we've been practicing TDD for some time now. But what about architecture and design? Don't we have to worry about that? Or is it enough that we keep our functions small, and write lots of tests? In this talk, Uncle Bob talks about the next level up. What is the goal of architecture and design? What makes a design clean? How can we evolve our systems towards clean architectures and designs in an incremental Agile way.
Architecture: The Real Software Crisis
As software applications continue to grow in size and complexity, the software engineering community faces an ever worsening crisis. Many, perhaps most, large software endeavours are constructed in ways that make them ever more difficult to change and maintain. Some have outright failed. Others are becoming intolerably expensive to continue. At the root of these problems is the poor architecture of this software. As a community we must learn and apply the principles of software architecture, and demand that those principles be followed, even in the face of short term schedule pressure. Attendees to this talk will learn the basis for good software architecture, and techniques for creating and preserving it.
Agility and Architecture
Do agile methods abandon architecture for speed? Do they replace good design decisions with mindless testing? Are agile methods just another way to hack-and-slash systems together without the appropriate discipline, due-diligence, and documentation? In this track Robert C. Martin describes how the principles of Agile Software Development lead to rich and robust architectures, high degrees of discipline, due consideration of design and architecture, and all appropriate levels of documentation.
The first bullet in the "XP Developer Bill of Rights" is: "Programmers have a right to know what is needed…" In other words, they have a right to know the requirements. But rights and responsibilities go hand in hand. The fact that we have the right to know what is needed means that we have the responsibility to find out what is needed. That means that programmers play a critical role in the specification of systems. We've learned, over the last few decades, that the best way to specify a system is with tests. So specification disciplines are test disciplines. What are those disciplines? What are the responsibilities that programmers have? What responsibilities do customers, product owners, business analysts, and QA have? Given that specification error is one of the primary reasons for project failure; what must craftsmen do to mitigate and eliminate such errors?
REGISTRATION - IMPORTANT NOTICE
To register for this event and get access to the Rabobank building we need your full name and e-mail address. If you sign up for this event you agree that this information will be shared with the Rabobank.