| Principal theme | Prerequisite knowledge | Approaches the learning objectives | Reaches the learning objectives | Deepends the learning objectives |
|---|---|---|---|---|
| Service ecosystem architecture overview and concepts |
Can identify problems inherent in distributed, global systems (coordination protocols, no shared state, discrepancy in tools, languages, protocols, practices used). Suitable background available from Distributed systems, Software architectures. |
Can identify key business processes involved (contracting, outsourcing, breaches, sanctions, compensation, knowledge flows). Can identify key infrastructure services (interoperability support, service selection, monitoring of contractual state, trust, privacy, negotiation, knowledge bases involved). Can identify and describe challenges for the collaboration support infrastructure and architecture • business alignment styles, • autonomy, • problems of use (technical, societal), and • role of the software engineering. |
Is able to describe at least one case study where identified business processes exists and identify the level of automation supported. | Is able to identify goals where the automatic behaviour of the agents involved are not technically validated or where societal requirements hinder the adoption of the solutions. |
| Basic concepts for business thinking |
Can identify and describe business strategies terminology including enterprise architecture, business model, business process model, IT alignment,< value net, supply chain. Can describe a few networked systems and scenario. |
Can describe how business concepts act as requirements for the infrastructure functions. | Is able to identify goals where the automatic behaviour of the agents involved are not technically validated or where societal requirements hinder the adoption of the solutions. | |
| Key infrastructure services | Programming, modeling, operating systems |
Can describe key infrastructure services (service discovery and selection, eContracting, monitoring, business transactions, reputation services) Can describe the purpose and at least one implementation scenario of each key service. |
Can describe the purpose and some implementation scenarios for key services. |
Is able to compare interoperability support infrastructures in terms of dependability and extendability. Is able to evaluate the systemic trustworthiness / dependability of an architecture. Identify secuirty threates of the architecture and informally estimate the performance of the architecture. |
| Technologies for implementing key services; Analysis and maturity evaluation; Business-infrastructure alingment | Data structures, object-oriented programming, large software projects; knowledge and application of CMM (software engineering course); Software engineering project level experience on developing and evolving large software systems |
Can describe the principles of reflective systems and multiagent systems. Is able to classify systmes with the help of categories defined bby a maturity model. |
Can describe how two out of the key system patterns can be utilised in the implementation of the ecosystem infrastructure services. Can analyse strengths, weakenesses, opportunities and threats (SWOT) for at least one technical case study in a given business scenario. |
Is able to identify coarse security threats of the architecture and informally estimate the performance of the architecture. Is able to select and justify the selection of integrated, unified or federated archiecture for the business case at hand. Is able to design architectures according to different design principles for the same collaboration situation and compare these designs with the help of maturity models. |