In this lecture,  we deal with Service Oriented Architecture Modelling Language (SoaML), that is a way to represent services in SOA. We see the notation and how it can be useful to represent services.

We also deal with service-oriented analysis to answer to questions: a) What services need to be built? b) What logic should be encapsulated by each service?  As such, the candidate services identified in the analysis phase are further modified in the design phase when considerations about implementation are considered as well.

Lecture slides

Further References

• How to model services with SoaML: VP Tutorial
• SoaML Specifications 1.0.1: (SoaML specifications) [PDF]
  
• Elvesæter, Brian, Arne-Jørgen Berre, and Andrey Sadovykh. "Specifying Services using the Service Oriented Architecture Modeling Language (SoaML)-A Baseline for Specification of Cloud-based Services." CLOSER. 2011 [PDF].
  
• Berre, A. J. "Service-oriented Architecture Modeling Language (SoaML)—Specification for the UML Profile and Metamodel for Services (UPMS). OMG Document." (2009) [PDF]

Additional Material about Domain Driven Design (DDD) for Microservices

We have looked at how to apply DDD for the analysis of the domain and identification of the microservices. It is an iterative process that allows to define bounded contexts and derive the microservices from the attribution of functionality to each boundary.

For a very quick summary about DDD and the Bounded Context (more extensive details in [1], [2]):

[1] Evans, Eric, and Eric J. Evans. Domain-driven design: tackling complexity in the heart of software. Addison-Wesley Professional, 2004. [URL]

[2] Vernon, Vaughn. Implementing domain-driven design. Addison-Wesley, 2013. [URL]