Eliciting Design Decisions in a Service-Oriented Architecture
|has title::Eliciting Design Decisions in a Service-Oriented Architecture|
|Master:||project within::Software Engineering|
|Student name:||student name::Rakesh Sewgolam|
|Second reader:||has second reader::Qing Gu|
The use of Service-Oriented Architectures (SOA) by organizations has become very popular and is still expected to grow. According to Gartner analysts, SOA will be used in more than 80 percent of new mission-critical operational applications and business processes by 2010. Despite its popularity, SOA is still by many considered as relatively new and underdeveloped. The purpose of this research is to provide practicing architects with more knowledge on SOA design. More specifically, this research will focus on SOA and design decisions. The following main research question has been formulated: Is it possible to isolate design decisions that describe a "good SOA"? This main research question is divided in the following sub questions: 1. What defines SOA? 2. Which different SOA types can be described? 3. Which SOA design patterns can be found in literature? 4. Which SOA design decisions can be found in existing company projects? 5. What defines a “good” SOA?