Hinweis: Die aktuelle OOP-Konferenz finden Sie hier!
SIGS DATACOM Fachinformationen für IT-Professionals

SOFTWARE MEETS BUSINESS:
Die Konferenz für Software-Architekturen

München, 01. - 05. Februar 2016

Konferenz

Vortrag: Di 4.1
Datum: Di, 02.02.2016
Uhrzeit: 09:00 - 10:30
cart

Software Architecture as Systems Dissolve

Uhrzeit: 09:00 - 09:45
Vortrag: Di 4.1 1)
Sprecher:

 

The way we build systems is changing. From our history of monolithic systems, then distributed systems, to Internet connected systems, we are now entering the era of cloud-hosted, microservice based, pay-for-usage system development. What does the history of software architecture tell us about the challenges of this new environment? And how does our approach to software architecture need to evolve in order to meet them?

Target Audience: Architects, Developers, Project Leader, Manager, Decision Makers
Prerequisites: None
Level: Practicing

You will learn:

  • Understand the purpose and value of software architecture
  • Understand the possibilities and impact of cloud-hosted, microservice-based, and pay-for-usage systems development on Software Architecture

Extended Abstract:
Software architecture has been a mainstream discipline since the 1990s and in that time has become a recognised, widely researched and often valued part of the software engineering process. However architecture approaches must reflect the technologies and priorities of the systems we are building and in this regard its future has never looked more uncertain or more exciting. From our history of monolithic compile time architecture, to many tiered distributed systems, to Internet connected services, we are now entering the era of cloud-hosted, microservice-based, pay-for-usage systems development. In this new world the boundaries of “my” system are no longer so clear and our systems are dissolving into complex webs of independently owned and evolved services, with nothing more in common than a shared credit card for billing and an agreement on the format of network requests. What can the history of software architecture tell us about the likely challenges in this environment? And how must it develop in order to meet them?

 

Modeling vs. Coding

Uhrzeit: 09:45 - 10:30
Vortrag: Di 4.1 2)

 

The first O-O programming language was Simula, which was designed for simulation. Its authors believed that to write a program was to produce a model. Thus, programming was modeling, and the goal was understanding.
In contrast, the use of “coding” to refer to programming implies that programming is about symbol manipulation, and that its goal is to control a computer.

Target Audience: Architects, Developers, Project Leader
Prerequisites: Project Experience
Level: Practicing

You will learn:
Understand how the opposing forces modeling and instructing a computer have been the cause of controversy in the past, but will work together to make a better future.

Extended Abstract:
The first object-oriented programming language was Simula, which (as its name suggests) was designed for simulation. Its authors, Ole-Johan Dahl and Kristen Nygaard, believed that to write a program was to produce a model of some system. Thus, programming was modeling, and the goal was understanding. In contrast, the use of "coding" to refer to programming implies that programming is about symbol manipulation, and that its goal is to control a computer.
The tension between modeling and coding has been with object-orientation since the beginning. It has had an influence on nearly every topic that has arisen in the object-oriented community, from language design to program design, from patterns to refactoring, from architecture to process. Is our main goal modeling, or instructing a computer?
This talk will show how these opposing forces have been the cause of controversy in the past, but will also show how they can work together to make a better future.