Course description

Service-oriented software engineering (SOSE) is a software engineering approach which utilises constructs and concepts conforming with the service-oriented computing paradigm for designing, modelling and developing service based systems. The course introduces principles behind service-oriented software engineering, and approaches and methods for efficient service production in service ecosystems using model-driven engineering paradigm (MDE). The emphasis of the course is on service design, composition and modelling principles instead of specific implementation technologies as the MDE aims on hiding the technological detail with automated transformations from more abstract models to implementations.

NEWS:

• There has been some querires on the course results. They are due soon, but you have not missed anything yet. My general impression is that almost all of the students who seriously completed the portfolio and exam  are likely to pass the course. Since the results are coming out too close to the renewal exam, I am going to organise an extra renewal exam on a later date. In some cases I need to ask correction on the portfolios, but the clocks get restarted only when you have received the advise on what needs to be done. In case you need your results for degree completition asap, please email or phone me about the issue.
• Created a new tab to hold Modelio tool hints 
• On Wednesday we will conclude the lectures. Requests of additional topics to cover or discussion points are wellcome. Remaining lecture and exercise times are suitable for gathering together to solve modeling problems and sharing experience on the tool usage.
•  
• Last Friday exercise session 21.2. 2014 10-12 
  • demo on Banking  system by Tuukka
  • Watch SoaML modeling "video" to see for example how some of the models get developed in parallel - more detailed ones are needed to provide the more abstract ones with vocabulary to choose from.
• There has been an unexpected amount of "null pointer" problems with the tool, creating some slow-down of the portfolio preparation. In addition, many of you have a heavy exam load on the portfolio deadline week. Therefore, it seems fair and practical to extend the portfolio deadline by a week, that is portfolios should be submitted at latest on Monday 10.3.  
  • Note that the intended size of exercises so far shown to me or proposed are fine and there are no signals intended here for larger modeling tasks, but just being practical with the task at hand. Furthermore, the created models do not need to be fully complete, as long as they go deep enough for the learning experience and you leave out elements that would just cause repetition of the same a few times over. When in doubt, feel free to check with me by email, visiting my office, or any other means practical.
• Please fill in a course feedback form after the exam and portfolio have been completed. You find it here.
• On Mo 10.3 morning:  As there has been a small number of queries on further extensions on portfolio deadlines, I make the the following (rather standard) rule announcement:
  • ​If your portfolio is late from the Mo 10.3 by 23.59 deadline, each 24 hours delay drops 1 point from the maximum number of points available for portolios. 
• ​Additional course examination will be available on 3.6. at 16.00 in B123. You may try rising your degree once.