Abstract
Software intensive systems are systems strongly depending on supporting software. The software is typically large, complex, and it as a rule interacts with human users.
The failure of the software implies failure of the system usually causing substantial losses. It is, such systems are critical.
The prospective redevelopment all at once of the software is no feasible solution. It is shown that such software should usually be service oriented. The interfaces of services should be user oriented (well understood by users and the users can use it easily). The services should be of two basic types: application services and architecture (enabling to develop an architecture) services. We present the most important infrastructure services as basic service-oriented design patterns.