You all have heard about RUP. Some of you may know RUP very well. But do you know that RUP is agile? Do you know that RUP is engineered to help you manage outsourced development? Do you know that RUP is prepared for the future of software development, including aspect-orientation and active software? Do you really know what RUP is all about?

Modern software development means object orientation, component based design, use case driven development, and the Unified Modeling Language (UML). These technologies are efficiently interwoven in the Rational Unified Process (RUP). The talk will touch upon these matters, but focus on some key questions:

You will learn from a father of these technologies something you didn't know, but you care a lot about.

Software development has matured from heuristic practice to an engineering discipline. Nowadays software engineers can benefit from a solid stock of basic research addressing specification, modelling, design and implementation techniques for sequential and concurrent systems. The software engineer faces dif- ferent system views manifesting themselves as data model, communication model, state transition model or process model. Software development must safely bridge system views on different levels of abstraction. Against this general background, we present a model for communicating components along with transformations refining the component's behaviour, interface and state. In the external view, a component forms a black box interacting with the environment by message passing whereas the internal view discloses the component's state.

We understand states as abstractions of communication histories and present methods for systematically transforming the component's behaviour into a statebased implementation. We conclude with a critical assessment of applying formal methods from academics to industrial software engineering.