Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
didattica:magistrale:bpdcc:ay_1920:main [2019/09/30 16:15] a.morichetta [Exams] |
didattica:magistrale:bpdcc:ay_1920:main [2020/09/17 16:55] (current) |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== News ===== | ===== News ===== | ||
| <WRAP center round important 95%> | <WRAP center round important 95%> | ||
| - | * <wrap em>**October 2nd first lecture**</wrap> | + | * <wrap em>**October 24th - The class of today will be not carried out**</wrap> |
| + | * <wrap em>**October 14 - Only the Wednesday class will be provided for this week**</wrap> | ||
| </WRAP> | </WRAP> | ||
| ---- | ---- | ||
| Line 40: | Line 41: | ||
| <WRAP round 95% center box> | <WRAP round 95% center box> | ||
| - | *Evolution of Enterprise Systems Architectures | + | * **What Is Software Architecture? ** |
| + | * 1.1 What Software Architecture Is and What It Isn’t | ||
| + | * 1.2 Architectural Structures and Views | ||
| + | * 1.3 Architectural Patterns | ||
| + | * 1.4 What Makes a “Good” Architecture? | ||
| + | * **Why Is Software Architecture Important?** | ||
| + | * 2.1 Inhibiting or Enabling a System’s Quality Attributes | ||
| + | * 2.2 Reasoning About and Managing Change | ||
| + | * 2.3 Predicting System Qualities | ||
| + | * 2.4 Enhancing Communication among Stakeholders | ||
| + | * 2.5 Carrying Early Design Decisions | ||
| + | * 2.6 Defining Constraints on an Implementation | ||
| + | * 2.7 Influencing the Organizational Structure | ||
| + | * 2.8 Enabling Evolutionary Prototyping Contents | ||
| + | * 2.9 Improving Cost and Schedule Estimates | ||
| + | * 2.10 Supplying a Transferable, Reusable Model | ||
| + | * 2.11 Allowing Incorporation of Independently Developed Components | ||
| + | * 2.12 Restricting the Vocabulary of Design Alternatives | ||
| + | * 2.13 Providing a Basis for Training | ||
| + | * **The Many Contexts of Software Architecture** | ||
| + | * 3.1 Architecture in a Technical Context | ||
| + | * 3.2 Architecture in a Project Life-Cycle Context | ||
| + | * 3.3 Architecture in a Business Context | ||
| + | * 3.4 Architecture in a Professional Context | ||
| + | * 3.5 Stakeholders | ||
| + | * 3.6 How Is Architecture Influenced? | ||
| + | * 3.7 What Do Architectures Influence? | ||
| + | * **Understanding Quality Attributes** | ||
| + | * 4.1 Availability | ||
| + | * 4.2 Interoperability | ||
| + | * 4.3 Modification | ||
| + | * 4.4 Performance | ||
| + | * 4.5 Security | ||
| + | * 4.6 Testability | ||
| + | * **Architectural Tactics and Patterns ** | ||
| + | * 13.1 Architectural Patterns | ||
| + | * 13.2 Overview of the Patterns Catalog | ||
| + | * 13.3 Relationships between Tactics and Patterns | ||
| + | ***Evolution of Enterprise Systems Architectures** | ||
| * Traditional Application Development | * Traditional Application Development | ||
| * Enterprise Applications and their Integration | * Enterprise Applications and their Integration | ||
| * Workflow Management | * Workflow Management | ||
| * Enterprise Services Computing | * Enterprise Services Computing | ||
| - | *Understanding SOA | + | ***Understanding SOA** |
| * Integration of Applications and Data | * Integration of Applications and Data | ||
| * Agility, Flexibility, and Alignment | * Agility, Flexibility, and Alignment | ||
| Line 51: | Line 90: | ||
| * What Is Service-Oriented Architecture? | * What Is Service-Oriented Architecture? | ||
| * What Is a Service? | * What Is a Service? | ||
| - | * Designing SOA for business | + | * **Designing SOA for business** |
| * Starting with the Business | * Starting with the Business | ||
| * Designing Service Interfaces | * Designing Service Interfaces | ||
| Line 57: | Line 96: | ||
| * Composing Services | * Composing Services | ||
| * Using Services to Build Enterprise Solutions | * Using Services to Build Enterprise Solutions | ||
| - | * Blockchain & Ethereum | + | * **BPM Platform Camunda** |
| - | * Theoretical Background | + | * Overview |
| + | * Architecture | ||
| + | * Modeler | ||
| + | * Engine | ||
| + | * Runtime | ||
| + | * Logging | ||
| + | * Security | ||
| + | * **Blockchain & Ethereum** | ||
| + | * What Is Blockchain and Why Should I Care? | ||
| + | * Blockchain-Based Applications | ||
| + | * Blockchain Functionality | ||
| + | * Blockchain Non-functional Properties | ||
| + | * Blockchain Architecture Design | ||
| + | * Varieties of Blockchains | ||
| + | * **Fundamental Properties of Blockchain** | ||
| + | * Decentralization | ||
| + | * Ledger Structure | ||
| + | * Consensus Protocol | ||
| + | * Block Configuration | ||
| + | * Auxiliary Blockchains | ||
| + | * Anonymity | ||
| + | * Incentives | ||
| + | * **Model-Driven Engineering for Blockchain Applications** | ||
| * Ethereum | * Ethereum | ||
| * Smart Contracts | * Smart Contracts | ||
| + | * Remix IDE | ||
| * Experiments | * Experiments | ||
| + | * From choreography model to Blockchain | ||
| + | |||
| </WRAP> | </WRAP> | ||
| ---- | ---- | ||
| Line 77: | Line 141: | ||
| * {{book.png?60x85}} **Business Process Management. Concepts, Languages, Architectures**. Weske, Mathias 2007, ISBN: 9780321155559 | * {{book.png?60x85}} **Business Process Management. Concepts, Languages, Architectures**. Weske, Mathias 2007, ISBN: 9780321155559 | ||
| * {{soabook.jpeg?60x85}} **Applied SOA service-oriented architecture and design strategies**. Michael Rosen, Boris Lublinsky, Kevin T. Smith, Marc J. Balcer, ISBN: 0470223650. | * {{soabook.jpeg?60x85}} **Applied SOA service-oriented architecture and design strategies**. Michael Rosen, Boris Lublinsky, Kevin T. Smith, Marc J. Balcer, ISBN: 0470223650. | ||
| + | * {{:didattica:magistrale:bpdcc:ay_1920:real_book.jpeg?60x85}} **Real-Life BPMN (4th edition): Includes an introduction to DMN (English Edition)** Jakob Freund and Bernd Rücker | ||
| + | * {{:didattica:magistrale:bpdcc:ay_1920:softwarearchitectureinpractice.png?60x85}} **Software Architecture in Practice** Len Bass, Paul Clements and Rick Kazman | ||
| </WRAP> | </WRAP> | ||
| ---- | ---- | ||
| Line 86: | Line 152: | ||
| * 03/06/2020 - 11:00 | * 03/06/2020 - 11:00 | ||
| * 24/06/2020 - 11:00 | * 24/06/2020 - 11:00 | ||
| - | * 8/07/2020 - 11:00 | + | * 08/07/2020 - 11:00 |
| * 22/07/2020 - 11:00 | * 22/07/2020 - 11:00 | ||
| - | * 9/09/2020 - 11:00 | + | * 09/09/2020 - 11:00 |
| * 30/09/2020 - 11:00 | * 30/09/2020 - 11:00 | ||
| Line 95: | Line 161: | ||
| <WRAP box round center 95%> | <WRAP box round center 95%> | ||
| **Exam rules**: | **Exam rules**: | ||
| - | *** Software Project:** Groups of maximum 2 people will have to choose an open problem or follow the assigned one, and provide a complete software solution with artifacts. The project need to be discussed with the teacher by mail, sending a small description of the requirements and final goal. | + | *** Software Project:** Each student has to choose an open problem or follow the assigned one, and provide a complete software solution with artifacts and a brief report. The project proposal need to be discussed with the teacher by mail, sending a small description of the requirements and final goal. |
| - | ***Oral exam + Project Presentation** A report have to be delivered before the oral part. | + | ***Written exam** The student has to pass the written exam concerning the theory part of the course in order to be admitted at the project presentation |
| </WRAP> | </WRAP> | ||
| <WRAP box round center 95%> | <WRAP box round center 95%> | ||
| ** Exam Results ** | ** Exam Results ** | ||
| </WRAP> | </WRAP> | ||
| + | |||
| + | |||
| + | |||
| | | ||
