Course Information

PV217 Service Oriented Architecture

Extent and Intensity

2/0/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).
Asynchronous teaching

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Martin Štefanko (lecturer)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Fri 27. 9. to Fri 20. 12. Fri 10:00–11:50 Virtuální místnost

Prerequisites

Knowledge about object-oriented programming in Java is required for the creation of microservices. No prior knowledge about SOA or microservices is required.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 32 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- understand the differences between several architectural styles: monolith, SOA, microservices;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- usage of Domain Driven Design (DDD) for designing services in a microservice architecture;
- review major standards in the area: from the old WSDL-*, to REpresentational State Transfer (REST) concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major microservice and SOA patterns in terms of security, reliability, maintainability of the implemented solutions;
- discuss the major patterns for the migration from monolithic systems to microservices;
- practice with the creation of microservices using the Quarkus framework to better understand the concepts seen during the lectures;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a microservices-based system;
- design a service starting from the analysis phase by using Domain Driven Design (DDD);
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- understand issues related to reliability and scalability of microservices-based system;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation. Monolith vs SOA vs Microservices;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
• Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer - Discoverability;
• Representational State Transfer (REST) & OpenAPI;
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design - Microservices Domain Driven Design (DDD) ;
• Microservices: task granularity, services organization, component sharing, message exchange, main principles. Technologies for microservices implementation. Adopting the Quarkus framework to create microservices;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• Newman, S. (2021). Building microservices. 2nd Edition. O'Reilly Media, Inc. ISBN 978-1492034025
• Newman, S. (2019). Monolith to microservices: evolutionary patterns to transform your monolith. O'Reilly Media. ISBN: 978-1492047841
• Richardson, C. (2018). Microservices patterns: with examples in Java. Simon and Schuster. ISBN: 978-1617294549
• Martin Štefanko and Jan Martiška: Quarkus in Action, Manning publishing, 2024. ISBN 9781633438958

Teaching methods

Please note that Autumn 2024 lectures will be given *remotely* in the form of video recordings. During the semester, students will be expected to submit their solution to several exercises related to the implementation of microservices in Quarkus. The final colloquium will be based on a discussion of the content of the course and the discussion of the exercises submitted.

Assessment methods

Final oral colloquium on the topics of the course. During the semester, students will need to submit some assignments based on the Quarkus framework covering the different aspects seen during the course.

Language of instruction

English

Study support

https://is.muni.cz/auth/el/fi/podzim2024/PV217/index.qwarp

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Martin Štefanko (lecturer)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 12:00–13:50 A319

Prerequisites

Knowledge about object-oriented programming is required for the creation of microservices.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 66 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- understand the differences between several architectural styles: monolith, SOA, microservices;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- usage of Domain Driven Design (DDD) for designing services in a microservice architecture;
- review major standards in the area: from the old WSDL-*, to REpresentational State Transfer (REST) concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major microservice and SOA patterns in terms of security, reliability, maintainability of the implemented solutions;
- discuss the major patterns for the migration from monolithic systems to microservices;
- practice with the creation of microservices using the Quarkus framework to better understand the concepts seen during the lectures;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a microservices-based system;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;
- understand issues related to reliability and scalability of microservices-based system;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation. Monolith vs SOA vs Microservices;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
• Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer - Discoverability;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design - Microservices Domain Driven Design ;
• Microservices: task granularity, services organization, component sharing, message exchange, main principles. Technologies for microservices implementation. Adopting the Quarkus framework to create microservices;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Final oral colloquium on the topics of the course. Students will need to pass a presentation done in teams that will consist on the creation of a microservices-based system.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Martin Štefanko (assistant)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 12:00–13:50 A320

Prerequisites

Knowledge about object-oriented programming is required for the creation of microservices.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 66 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;
- understand the differences between several architectural styles: monolith, SOA, microservices;
- practice with the creation of microservices to better understand the concepts seen during the lectures;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;
- know how to implement a microservices-based system;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation. Monolith vs SOA vs Microservices;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;
• Microservices: task granularity, services organization, component sharing, message exchange, main principles. Technologies for microservices implementation. Using Quarkus to create microservices;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Final oral colloquium on the topics of the course. Students will need to pass a presentation done in teams that will consist on the creation of a microservices-based system.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Martin Štefanko (assistant)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Tue 14. 9. to Tue 7. 12. Tue 10:00–11:50 A217

Prerequisites

Knowledge about object-oriented programming is required for the creation of microservices.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 65 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;
- understand the differences between several architectural styles: monolith, SOA, microservices;
- practice with the creation of microservices to better understand the concepts seen during the lectures;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;
- know how to implement a microservices-based system;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation. Monolith vs SOA vs Microservices;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;
• Microservices: task granularity, services organization, component sharing, message exchange, main principles. Technologies for microservices implementation. Using Quarkus to create microservices;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Final oral colloquium on the topics of the course. Students will need to pass a presentation done in teams that will consist on the creation of a microservices-based system.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Martin Štefanko (assistant)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Tue 8:00–9:50 A319

Prerequisites

No prerequisites are compulsory.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 65 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;
- understand the differences between several architectural styles: monolith, SOA, microservices;
- practice with the creation of microservices to better understand the concepts seen during the lectures;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;
- know how to implement a microservices-based system;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation. Monolith vs SOA vs Microservices;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;
• Microservices: task granularity, services organization, component sharing, message exchange, main principles. Technologies for microservices implementation. Using Quarkus to create microservices;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Final oral colloquium on the topics of the course. Students will need to pass a presentation done in teams that will consist on the creation of a microservices-based system.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

Bruno Rossi, PhD
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 8:00–9:50 A319

Prerequisites

No prerequisites are compulsory. It is recommended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 65 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Written/oral final examination. Students will need to pass a presentation (case-study based) done in teams towards the end of the course.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Eva Hladká, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 17. 9. to Mon 10. 12. Mon 8:00–9:50 A319

Prerequisites

No prerequisites are compulsory. It is recommended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 33 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Written/oral final examination. Students will need to pass a presentation (case-study based) done in teams towards the end of the course.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Eva Hladká, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 18:00–19:50 A319

Prerequisites

No prerequisites are compulsory. It is recommended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 33 fields of study the course is directly associated with, display

Course objectives

The objectives of the course are to give the students a set of skills necessary to understand and work in the context of Service Oriented Architectures (SOA), namely:
- review several issues in the business adoption of SOA in an IT context;
- give an understanding of the several definitions of SOA (as an architectural style, as an IT paradigm, ...);
- review approaches for Service Oriented Analysis and Design and how they differ from Object Oriented analysis and Design;
- review major standards in WSDL-*, together with SOAP and REST concepts;
- present concepts such as orchestration, choreography, atomic transactions, message exchange patterns;
- review major patterns in SOA in terms of security, reliability, maintainability of the implemented solutions;
- review major parts of the SOA architecture, such as Enterprise Service Bus (ESB) and solutions provided by different vendors;

Learning outcomes

At the end of the course students will be able to:
- explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
- understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
- compare SOA with other architectural paradigms;
- analyse requirements towards the creation of a service;
- design a service starting from the analysis phase;
- understand the problematics in service design and analysis;
- understand the problematics in service implementation;
- being able to classify and make reasoned decision about the adoption of different SOA platforms;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Written/oral final examination. Students will need to pass a presentation (case-study based) done in teams towards the end of the course.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Eva Hladká, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 8:00–9:50 B410

Prerequisites

No prerequisites are compulsory. It is recommended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 33 fields of study the course is directly associated with, display

Course objectives

At the end of the course students will be able to: explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
compare SOA with other architectural paradigms;
analyse requirements towards the creation of a service;
design a service from the analysis phase;
understand the problematics in service design;
understand the problematics in service implementation;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Written/oral final examination. Students will need to pass a presentation (case-study based) done in teams towards the end of the course.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Eva Hladká, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Wed 8:00–9:50 C511

Prerequisites

No prerequisites are compulsory. It is recommended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 33 fields of study the course is directly associated with, display

Course objectives

At the end of the course students will be able to: explain the meaning of the "Service Oriented" paradigm both from the business and technical point of view;
understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies;
compare SOA with other architectural paradigms;
analyse requirements towards the creation of a service;
design a service from the analysis phase;
understand the problematics in service design;
understand the problematics in service implementation;

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

required literature
• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

recommended literature
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

Frontal lectures.

Assessment methods

Written/oral final examination. Students will need to pass a presentation (case-study based) done in teams towards the end of the course.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Bruno Rossi, PhD (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Eva Hladká, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 12:00–13:50 A218

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 32 fields of study the course is directly associated with, display

Course objectives

The students shall learn the meaning of the "Service Oriented" paradigm both from the business and technical point of view. They shall understand the applicability of SOA design patterns and the meaning of the major SOA implementation technologies. Furthermore, they shall become confident with the application of implementation technologies to support the SOA paradigm.

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition;
• Basics of SOA - Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures - Anatomy of SOA - How components in an SOA interrelate. Principles of service orientation;
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services;
• SOA Design Patterns: patterns for performance, scalability, and availability; Service Consumer patterns; Service integration patterns; SOA anti-patterns;
SOAP - Message exchange Patterns - Coordination - Atomic Transactions - Business activities - Orchestration - Choreography - Service layer abstraction - Application Service Layer - Business Service Layer - Orchestration Service Layer;
• Representational State Transfer (REST);
• Business-centric SOA - Deriving business services - service modelling - Service Oriented Design - Entity-centric business service design - Application service design - Task centric business service design;
• SOA Technologies - SOA Tooling - SOA Vendors;

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005
• ROTEM-GAL-OZ, Arnon, E. BRUNO and U. DAHAN. SOA patterns. Manning, 2012, 296 pp. ISBN 978-1-933988-26-9. info
• KRAFZIG, Dirk, Karl BANKE and Dirk SLAMA. Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional, 2005, 408 pp. ISBN 978-0-13-146575-6. info

Teaching methods

frontal lectures.

Assessment methods

Written and oral examination.

Language of instruction

English

Further Comments

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Parag Kulkarni, Ph.D., DSc. (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Vlastislav Dohnal, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Wed 30. 10. 10:00–11:50 G331, Wed 6. 11. 10:00–11:50 G331, Wed 13. 11. 10:00–11:50 G331, Wed 20. 11. 10:00–11:50 G331, Wed 27. 11. 10:00–11:50 G331

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 32 fields of study the course is directly associated with, display

Course objectives

The course is organized into 4 modules, which explain At the end of the course students should be able to:
work with SOA basics;
understand and explain SOA values;
understand model of SOA management.

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Basics of SOA – Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures – Anatomy of SOA- How components in an SOA interrelate. Principles of service orientation
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services. Messaging with SOAP –Message exchange Patterns – Coordination –Atomic Transactions – Business activities – Orchestration – Choreography - Service layer abstraction – Application Service Layer – Business Service Layer – Orchestration Service Layer
• Business-centric SOA – Deriving business services- service modelling - Service Oriented Design – Entity-centric business service design – Application service design – Task centric business service design
• SOA technology aspects: Web services and SOA aspects, key elements of transfer to SOA plan.
• Model of SOA implementation management: meaning and necessity of SOA management model.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005
• SOA Compass - Bieberstein et al - Pearson
• Enterprise SOA - Woods and Mattern - O'reilly

Teaching methods

lectures, presentations by professionals in the domain.

Assessment methods

Written and oral examination.

Language of instruction

English

Further comments (probably available only in Czech)

Study Materials
The course can also be completed outside the examination period.
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Parag Kulkarni, Ph.D., DSc. (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

prof. RNDr. Luděk Matyska, CSc.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Timetable

Mon 16. 4. 12:00–13:50 B204, Wed 18. 4. 8:00–9:50 B204, Fri 20. 4. 8:00–9:50 B204, Mon 23. 4. 12:00–13:50 B204, Wed 25. 4. 8:00–9:50 B204, Fri 27. 4. 8:00–9:50 B204, Mon 30. 4. 12:00–13:50 B204, Wed 2. 5. 8:00–9:50 B204, Fri 4. 5. 8:00–9:50 B204, Mon 7. 5. 12:00–13:50 B204, Wed 9. 5. 8:00–9:50 B204, Fri 11. 5. 8:00–9:50 B204

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 32 fields of study the course is directly associated with, display

Course objectives

The course is organized into 4 modules, which explain At the end of the course students should be able to:
work with SOA basics;
understand and explain SOA values;
understand model of SOA management.

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Basics of SOA – Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures – Anatomy of SOA- How components in an SOA interrelate. Principles of service orientation
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services. Messaging with SOAP –Message exchange Patterns – Coordination –Atomic Transactions – Business activities – Orchestration – Choreography - Service layer abstraction – Application Service Layer – Business Service Layer – Orchestration Service Layer
• Business-centric SOA – Deriving business services- service modelling - Service Oriented Design – Entity-centric business service design – Application service design – Task centric business service design
• SOA technology aspects: Web services and SOA aspects, key elements of transfer to SOA plan.
• Model of SOA implementation management: meaning and necessity of SOA management model.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

Teaching methods

lectures, presentations by professionals in the domain.

Assessment methods

Written and oral examination.

Language of instruction

English

Further Comments

Study Materials
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

RNDr. Stanislav Michelfeit (lecturer), RNDr. Zdenko Staníček, Ph.D. (deputy)

Guaranteed by

prof. RNDr. Václav Matyáš, M.Sc., Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: RNDr. Zdenko Staníček, Ph.D.

Timetable

Fri 1. 4. 10:00–15:50 G101, Fri 15. 4. 10:00–15:50 G101, Fri 6. 5. 10:00–15:50 G101, Fri 20. 5. 10:00–15:50 G101

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 36 fields of study the course is directly associated with, display

Course objectives

The course is organized into 4 modules, which explain At the end of the course students should be able to:
work with SOA basics;
understand and explain SOA values;
understand model of SOA management.

Syllabus

• Module 1: Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Module 2: SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services.
• Module 3: SOA technology aspects: Web services and SOA aspects, key elements of transfer to SOA plan.
• Module 4: Model of SOA implementation management: meaning and necessity of SOA management model.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

Teaching methods

lectures, presentations by professionals in the domain.

Assessment methods

Written and oral examination.

Language of instruction

English

Further Comments

Study Materials
The course is taught annually.

PV217 Service Oriented Architecture

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

RNDr. Stanislav Michelfeit (lecturer), RNDr. Zdenko Staníček, Ph.D. (deputy)

Guaranteed by

prof. RNDr. Václav Matyáš, M.Sc., Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: RNDr. Zdenko Staníček, Ph.D.

Timetable

Fri 16. 4. 8:00–13:50 D3, Fri 30. 4. 8:00–13:50 D3, Fri 7. 5. 8:00–13:50 D3, Fri 21. 5. 8:00–13:50 D3, Wed 26. 5. 9:00–17:50 B007, Fri 28. 5. 9:00–17:50 B007

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 36 fields of study the course is directly associated with, display

Course objectives

The course is organized into 4 modules, which explain At the end of the course students should be able to:
work with SOA basics;
understand and explain SOA values;
understand model of SOA management.

Syllabus

• Module 1: Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Module 2: SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services.
• Module 3: SOA technology aspects: Web services and SOA aspects, key elements of transfer to SOA plan.
• Module 4: Model of SOA implementation management: meaning and necessity of SOA management model.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

Teaching methods

lectures, presentations by professionals in the domain.

Assessment methods

Written and oral examination.

Language of instruction

English

Further Comments

Study Materials
The course is taught annually.

PV217 Service Oriented Architecture

The course is not taught in Spring 2013

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

Parag Kulkarni, Ph.D., DSc. (lecturer), Ing. Leonard Walletzký, Ph.D. (deputy)
Mgr. Jitka Kitner (assistant)

Guaranteed by

doc. RNDr. Vlastislav Dohnal, Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: Ing. Leonard Walletzký, Ph.D.
Supplier department: Department of Computer Systems and Communications – Faculty of Informatics

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 32 fields of study the course is directly associated with, display

Course objectives

The course is organized into 4 modules, which explain At the end of the course students should be able to:
work with SOA basics;
understand and explain SOA values;
understand model of SOA management.

Syllabus

• Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Basics of SOA – Characteristics of SOA - Comparing SOA to client-server and distributed internet architectures – Anatomy of SOA- How components in an SOA interrelate. Principles of service orientation
• SOA business aspects: standards of Web services, implementation SOA using Web services, business aspects of SOA and Web services. Messaging with SOAP –Message exchange Patterns – Coordination –Atomic Transactions – Business activities – Orchestration – Choreography - Service layer abstraction – Application Service Layer – Business Service Layer – Orchestration Service Layer
• Business-centric SOA – Deriving business services- service modelling - Service Oriented Design – Entity-centric business service design – Application service design – Task centric business service design
• SOA technology aspects: Web services and SOA aspects, key elements of transfer to SOA plan.
• Model of SOA implementation management: meaning and necessity of SOA management model.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

Teaching methods

lectures, presentations by professionals in the domain.

Assessment methods

Written and oral examination.

Language of instruction

English

Further Comments

Study Materials
The course is taught annually.
The course is taught: every week.

PV217 Service Oriented Architecture

The course is not taught in Spring 2009

Extent and Intensity

2/0. 2 credit(s) (plus extra credits for completion). Type of Completion: k (colloquium).

Teacher(s)

RNDr. Stanislav Michelfeit (lecturer), RNDr. Zdenko Staníček, Ph.D. (deputy)

Guaranteed by

prof. RNDr. Václav Matyáš, M.Sc., Ph.D.
Department of Computer Systems and Communications – Faculty of Informatics
Contact Person: RNDr. Zdenko Staníček, Ph.D.

Prerequisites

No pre-requisities are compulsory. It is recomended to have earned credits in SSME obligatory subjects.

Course Enrolment Limitations

The course is also offered to the students of the fields other than those the course is directly associated with.

fields of study / plans the course is directly associated with

there are 37 fields of study the course is directly associated with, display

Course objectives

At the end of the course students should be able to:
work with SOA basics and SOA reference model;
understand and explain SOA values, SOA methods;
understand model of SOA management
understand the business dimension of SOA.

Syllabus

• The course is organized into 4 modules, which explain SOA basics, SOA philosophy, SOA technology, and SOA governance.
• Module 1: Introducing service oriented architecture (SOA): SOA definition and concepts, Web services definition.
• Module 2: SOA business aspects: standards of services and SOA reference architecture, implementation SOA using Web services, business aspects of SOA and Web services.
• Module 3: SOA technology aspects: Web services, services and SOA aspects, key elements of transfer to SOA plan. SOA specific methodologies.
• Module 4: Model of SOA implementation management: meaning and necessity of SOA management model. Planning and realisation of SOA projects. SOA governance.

Literature

• Thomas Erl: Service-Oriented Architecture (SOA): Concepts, Technology and Design, Prentice Hall PTR, August, 2005

Assessment methods

lectures, presentations by professionals in the domain. Written and oral examination.

Language of instruction

English

Further Comments

The course is taught annually.
The course is taught: every week.

• Enrolment Statistics (recent)