OOP 2014
"Software Meets Business"
Call for Papers

Complexity: Managing Today’s Challenges

OOP 2014, February 03 - 07, 2014
ICM - International Conference Center Munich

Dear Colleagues,

We would hereby like to invite you to submit proposals for presentation for the OOP 2014 conference to be held from February 03 to 07, 2014 in Munich, Germany. We are planning on five days of in-depth information on a variety of topics.
On the first and the last day we’ll have half-day (2.5 hours net) and full-day (5 hours net) tutorials.
Session slots during the conference will be 90, 60, or 45 minutes.

Your proposals should either be technical oriented or targeted to project leader / decision makers; we expect a wide range of interests to be present at the conference and on the exhibition floor. The main target groups of the conference are software architects and (technical) project leaders working in an enterprise environment. The participants expect to gain an excellent overview of the state-of-the-art in modern software engineering. The focus is on promising concepts for the future and as well as cutting edge techniques that are suitable for everyday practical use.

This year’s conference motto is “Complexity: Managing Today’s Challenges”. The OOP program strives to answer the following questions: what kinds of tools, architectures, and techniques support building systems that can cope with frequent changes in an uncertain environment; which designs and languages will enable quality in a product in the face of today’s complex requirements; and how do management techniques, social skills, and (agile) processes help or hinder leading projects towards success despite their unpredictable nature?

We’re seeking for submissions on the following topic areas, ideally emphasizing the theme complexity:

  • Software Architecture: Design and development best practices, Design and code quality management, Architecture evaluation, assessment, and testing, Refactoring, Reengineering, and management of technical debt, Architecture governance and management, Systems integration, Experience reports, success and war stories
  • Re-Architecting Legacy Software: Challenges in software modernization, brown field development, maintaining domain knowledge, modularization strategies, long-term technical debt, reverse and re-engineering in the large, managed evolution
  • Enterprise Architecture: Cloud-Architecture, SOA, EAM, Security-Architecture, Large-Scale Systems, System Integration, Distributed Systems
  • Managing Complex IT Projects and Products: Advantages and disadvantages of Lean IT, necessary requirements, change management, the role of traditional PM disciplines like stakeholder- or risk management, the role of PMI,  quality management in the agile context
  • Soft Skills are the new Hard Skills: sustainable Growth, Organizational Culture & Trust, Human Decision Context, Balancing Passion for Change with Respect for Tradition, Unleashing Everyone's Leadership Potential
  • Requirements Engineering: Reuse, Variant Management, Lean Requirements Engineering, Traceability, Modeling, Test Case Generation, Visualization, Acceptance Test, Behavior Driven Development, Specification by Example
  • Testing & Quality: Test management and strategies, Large scale agile testing, lean testing, Technical debt and code quality management of large code bases, Testing non-functional requirements, Model-based testing, Test automation, Test infrastructures, Test architectures, Testing in the cloud, mobile testing, Testing of big systems and big data, Multicore software testing
  • Agile, Lean, Scrum & Kanban: success and failure stories of agile implementations; agile beyond software development; handling complexity with agile methods; activities for retrospective meetings; new practices based on agile principles
  • Technologies: Java & JavaEE, Continuous Deployment, MDSD & DSL, Mobile, Embedded, NoSQL & NewSQL, Big Data

In all of these areas, we particularly welcome case studies especially describing experiences in practice from all application domains including, but not limited to transportation (aerospace, train, automobile,…), telecommunications, finance, insurance, industrial automation, mobile computing, government, as well as medical and life sciences.

In case you are interested in making a presentation that fits well to the above description, please submit your proposal(s) using the online form:


Instructions for submissions (Submission deadline: July 1st, 2013) 

Presentations can be in German or English:
      Please write your submission in the language you choose for your presentation.
The submission should contain the following information:

  • Type: session (90, 60, or 45 min), tutorial (half day or full day)
  • Title of presentation
  • Abstract (max. 550 characters): Explain general highlights, the technologies/concepts the session is covering. Provide as much detail as needed for the delegates to decide on participating in your session.
  • Learning outcomes: 1-3 reasons why a participant should choose this particular session and what would be the lessons learned. Special attention should be paid on the core target groups: Thus, what will be the learning outcomes for a software architect or (technical) project leader in the enterprise environment.
  • Process / mechanics: rough agenda for the session, session style (lecture, interactive, demo)
  • Target Audience (e.g. developers, managers, …)
  • Prerequisites required of attendees (e.g. basic knowledge in ..., familiarity with ..., … )
  • Level: introductory, practicing, expert
  • Short biography of the speaker (no more than 300 characters including technical background and past speaking experience); degree of familiarity with the suggested topic (multiple years, some practical experience, applied in prototypes, profound understanding)

Acceptance Criteria
We will use the following criteria for evaluating the submissions:

  • Quality of content and innovativeness: The sessions should be relevant and if possible enable the participants to apply the learning in their daily work. Conceptual submissions are possible, but in order to be accepted they should be outstanding. Experience reports or extended case studies in regular presentation are good pre-conditions for acceptance.
  • Presentation form: We prefer interactive sessions allowing the audience to get engaged and to actively participate.
  • Speaker: The sessions should be presented in an interesting, vivid, and entertaining way. Speakers who can prove these skills have a higher chance for acceptance.
  • Attractiveness for participants: Sessions with clear goals and outcomes for the participants (especially within the core target groups) will be rated higher as well as sessions focusing on this year’s theme. 

Notification of Acceptance
The decisions regarding which proposals will be included in the final program won’t be made before the end of August. In some cases, we may contact you for additional information before making our final decision.

Thank you very much in advance for contributing to the success of OOP 2014 by submitting your proposal. If you have any questions, do not hesitate to contact us at any time. Please feel free to pass on this call for papers to your colleagues.

Best regards,

Technical Chair
Jutta Eckstein (oop@jeckstein.de)

Speaker Coordinator
Wolfgang Reuter (wolfgang.reuter@sigs-datacom.de)

Track Chairs:

  • Frank Buschmann (Software Architecture)
  • Stefan Tilkov (Re-architecting Legacy Software)
  • Nicolai Josuttis (Enterprise Architecture)
  • Thorsten Janning (Managing Complex IT Projects & Products)
  • Olaf Lewitz (Soft Skills are the new Hard Skills)
  • Susanne Mühlbauer (Requirements Engineering)
  • Peter Zimmerer (Testing & Quality)
  • Bernd Kolb (Technologies)
  • Marc Bless (Agile, Lean, Scrum & Kanban)

PDF Download (Call for Papers OOP 2014)

Empfehlung an diese E-Mail-Adresse senden:




Ihre eigenen Angaben:





Diese Seite empfehlen Sie weiter: