Joseph W. Yoder (The Refactory, inc - EUA)
Joseph Yoder is a founder and principal of The Refactory, Inc., a company focused on providing training, mentoring and consulting for software architecture, design, implementation, consulting, and of most facets of software development. Joe specializes in architecture, analysis, and design in the following areas: C#/.NET; Java; Smalltalk; Patterns; Agile Methods; Testing; Adaptable Systems; Refactoring; Reuse; and Frameworks. Joe has presented many talk/keynotes, tutorials, workshops, and published papers at global conferences. Joe is an accomplished author, having written a few dozen published papers, including being an author of the Big Ball of Mud pattern, which illuminates many fallacies in the approach to software architecture. Additionally, Joe has trained and mentored developers on various types of software applications.
Joseph W. Yoder evolved from the Software Architecture and Patterns group at the University of Illinois. Joe has worked on various projects during his career that has incorporated many technologies. These range from stand-alone to client-server applications, web applications, web services, cloud computing, service oriented architecture, multi-tiered, various databases, object-oriented, frameworks, humancomputer interaction, collaborative environments, and domain-specific visual-languages. In addition these projects have spanned many domains, including Medical Information Systems, Ordering, Import, Invoicing, Print, Shipping, Warehouse Management, Manufacturing, Medical Examination, Statistical Analysis, Scenario Planning, ClientServer Relational Database System for keeping track of shared specifications in a multiuser environment, Telecommunications Billing System, and Business & Medical Decision Making.
Title: Microservices for Agility: "Advantages and Challenges"
Keynote Abstract: As systems become more complex, teams can become burdened with technical debt and other architectural challenges which slows down development; ultimately not being as agile and as nimble as desired. Therefore, good agile teams need to address both people and technical skills. The proper application of the Microservices architectural style as a distributed and reactive architecture can assist teams to adapt and evolve to changing requirements at a good pace. This talk will present how the proper application of the Microservices architectural style along with agile practices can enable teams to evolve systems reliably and at a good pace, maintaining the overall goals of agility during a rapid growth period. This talk will also present technical, cultural and procedural challenges along with advantages and tradeoffs of the Microservices architectural style.
Dirk Riehle (Friedrich-Alexander University Erlangen-Nürnberg)
Prof. Dr. Dirk Riehle, M.B.A., is the Professor of Open Source Software at the Friedrich-Alexander University of Erlangen-Nürnberg. Before joining academia, Riehle led the Open Source Research Group at SAP Labs, LLC, in Palo Alto, California (Silicon Valley). Riehle founded the Open Symposium, now the international conference on open collaboration. He was also the lead architect of the first UML virtual machine. He is interested in open source and inner source software engineering, agile software development methods, complexity science and human collaboration, and software system architecture, design, and implementation. Prof. Riehle holds a Ph.D. in computer science from ETH Zürich and an M.B.A. from Stanford Graduate School of Business. He welcomes email at firstname.lastname@example.org, blogs at http://dirkriehle.com, and tweets as @dirkriehle.
Title: Why Industry Will Want to Finance your Software Engineering Research"
Keynote Abstract: A subset of our research is almost completely industry-funded, and yet it is delivering high- quality publications. This research is based on what we call “the handbook method” (lacking a better term for now). Using this method, Ph.D. students first perform theory-building research using qualitative methods, which generates a handbook (the theory), and then evaluate the theory using evaluation case studies with industry partners, in which they apply the handbook. In this talk, I will explain the method using open source governance in companies as the example.