Visão Geral

Este Curso Introduction to Solution and Software Architecture apresenta aos alunos os fundamentos da arquitetura de soluções e software. Dentro da visão estratégica mais ampla que a Arquitetura Empresarial (EA) fornece, há uma necessidade de fornecer estrutura e orientação em torno dos recursos de arquitetura de solução mais táticos que são desenvolvidos para garantir que sejam consistentes com a estratégia mais ampla de EA.

Objetivo

Após realizar este Curso Introduction to Solution and Software Architecture você será capaz de:

• Capacidade de discutir o que é arquitetura
• Descrever a arquitetura de soluções empresariais e seus elementos principais
• Descrever a arquitetura de software
• Discuta os atributos de qualidade da arquitetura de software
• Explique como o desenvolvimento baseado em arquitetura é realizado
• Descrever como a documentação da arquitetura é realizada

Publico Alvo

• Compreensão básica do desenvolvimento de software.

Pre-Requisitos

• Arquitetos
• Desenvolvedores
• Designers
• Analistas

Materiais

Conteúdo Programatico

Architecture Primer

1. Architects
2. Architects and Architecture
3. Group Discussion
4. Enterprise Architecture Definitions (Wikipedia)
5. More Enterprise Architecture Definitions
6. A Rose By Any Other Name
7. Enterprise, Solution, and Technical Architectures
8. City Planners
9. City Planning and EA
10. Examples of Enterprise Architecture
11. Solution Architecture
12. Examples of Solution Architecture
13. Solution Architecture Example: SOA for Insurance
14. Technical Architecture
15. Examples of Technical Architecture
16. Technical Architecture Example
17. Architecture Is Not Only Design

Solution Architecture Overview

1. Understanding Solution Architecture
2. The Solution Architect
3. The Solution Architecture Context
4. Introducing Architecture Domains
5. Identifying the Architecture Domains
6. Diving into the Domains
7. Solution Architecture Realization Process
8. Requirements and Deliverables
9. Divide and Conquer

Solution Architecture Styles

1. Catalog of Architectural Styles
2. Asynchronous Messaging
3. Message Oriented Middleware (MOM)
4. Example MOM implementation Platforms
5. MOM Messaging
6. MOM Qualities
7. Publish/Subscribe Messaging
8. Point-to-Point Messaging (P2P)
9. MOM Related Standards
10. MOM Example
11. Service Oriented Architecture (SOA)
12. Service-Oriented Interaction Model
13. SOA Characteristics
14. Microservices
15. Microservices Architecture
16. Microservices vs Enterprise Service Bus (ESB)
17. Many Flavors of Web Services
18. Understanding REST
19. Principles of RESTful Services
20. SOAP and RESTful Web Services

Defining the Cloud

1. A Bit of History
2. Cloud Computing at a Glance
3. Electrical Power Grid Service Analogy
4. The NIST Perspective
5. Five Characteristics
6. On-demand Self-Service (NIST Characteristic)
7. Broad Network Access (NIST Characteristic)
8. Resource Pooling (NIST Characteristic)
9. Rapid Elasticity (NIST Characteristic)
10. Measured Service (NIST Characteristic)
11. The Three Cloud Service Models: IaaS, PaaS and SaaS
12. The Four Cloud Deployment Models (NIST)
13. The NIST Cloud Definition Framework
14. A Hybrid Cloud Diagram
15. Cloud Services
16. Managed vs Unmanaged Services
17. Shared Responsibility Model
18. The AWS (Simplified) Service Stack

Patterns

1. What are Patterns?
2. Elements of a Pattern
3. Pattern Levels
4. Pattern Types
5. How to Start Using Patterns?
6. Common Architectural Patterns
7. Layers Pattern
8. Example: Retail Layered Architecture
9. Object-Oriented Design Patterns
10. OO Design Patterns
11. Structural Design Pattern: Facade Pattern Example
12. Enterprise Integration Patterns
13. Messaging Systems: Overview
14. Example Pattern: Pipes and Filters
15. Example: Monitoring Credit Bureau
16. EAA Patterns
17. Model-View-Controller (MVC) Pattern
18. SOA Patterns
19. Example: Saga Pattern
20. Business Process Patterns
21. Example: Synchronizing Merge Pattern
22. Configuration Management Patterns
23. New Patterns Continue to Emerge
24. Group Discussion: Patterns

Solution Architecture Adoption

1. Adopting Solution Architecture
2. Architecture Adoption Best Practices
3. Architecture Adoption – Phase 1
4. Identify your business drivers
5. Get Educated
6. Articulate a Value Proposition
7. 4. Define one or more scenarios
8. Architecture Adoption – Phase 1
9. Architecture Adoption – Phase 2
10. Produce a Road Map
11. Gain Stakeholder Buy-in
12. Architectural Adoption – Phase 2
13. Architectural Adoption – Phase 3
14. Establish Governance
15. Invest in Infrastructure
16. Execute a Pilot Project
17. Scoping the Pilot Project
18. Scoping the Pilot Project (cont’d)
19. Roll Out to the Enterprise

The Software Development Process

1. Section A Software Development Methodologies
2. Waterfall Development Methodology
3. Iterative Development Methodology
4. Low Ceremony/High Ceremony
5. Comparison of Some Software Methodologies
6. The Spirit of the Rational Unified Process: Well-Defined Software Engineering
7. Two Dimensions of the RUP Process
8. Dynamic Dimension of RUP: Life-cycle Phases & Milestones
9. Static Dimension of RUP: Modeling Elements
10. Static Dimension of RUP: Disciplines
11. Spirit of RUP: Iterative & Risk-Driven Approach
12. The Life-cycle of Projects Using the Rational Unified Process: Inception Phase
13. Inception Phase (Cont…)
14. Elaboration Phase
15. Elaboration Phase (Cont…)
16. Develop Executable Architecture
17. Construction Phase
18. Construction Phase (Cont…) Typical tasks in the Construction Phase
19. Transition Phase
20. Transition Phase (Cont…)
21. The Open Unified Process
22. Four Core Principles of OpenUP
23. OpenUP Teams
24. OpenUP Basic Elements
25. The Eclipse Process Framework (EPF) Ecosystem
26. The EPF Composer

Quality of Service (QoS) Requirements

1. Qualities of Service and Design
2. Performance: Requirements
3. Performance: Response Time Pattern
4. Performance: Transaction Time Patterns
5. Performance: Throughput Pattern
6. Scalability
7. Scalability: Capacity Patterns
8. Reliability & Availability
9. Mean Time Between Failures (MTBF)
10. Availability: Pattern
11. Extensibility
12. Maintainability
13. Manageability
14. Security
15. Cultural Adaptability
16. Portability
17. Testability
18. Usability
19. Upgradeability
20. Recoverability
21. Recovery Time Objective (RTO)
22. Recovery Point Objective (RPO)
23. Prioritizing Quality of Service Requirements
24. Inspecting QoS Requirements for Trade-off Opportunities
25. Quality of Service Testing

Supporting QoS Requirements

1. Tactics
2. Availability Tactics
3. Supporting System's High Availability
4. The CAP Theorem
5. Mechanisms to Guarantee a Single CAP Property
6. Modifiability Tactics
7. Horizontal and Vertical Scalability
8. Leveraging Cloud Scaling Services
9. Performance Tactics
10. Achieving the Performance You Need
11. Security Tactics
12. Single Sign-On (SSO) with Federated Identity Management
13. OpenID
14. OpenID Communication Diagram
15. OAuth 2.0
16. OAuth 2.0 Communication Diagram
17. OpenID Connect
18. OpenID Connect Communication Diagram
19. Operational Security in the Cloud
20. DevOps Security Concerns
21. Testability Tactics
22. Achieving Testability with Test-Driven Development and Continuous Integration
23. Typical Setup for OSS-based Continuous Integration
24. Responsive Web Design (RWD) Support for Usability

Requirements Workflow

1. Requirements Workflow
2. What Is A Requirement?
3. Requirements Gathering
4. What Is Requirements Management?
5. Requirements Management
6. Timing of Requirements Workflow
7. The Cost Of Requirement Errors
8. The Game Plan Towards Building Quality Software
9. Problem Analysis and Understanding User Needs
10. Problem Analysis Steps
11. Business Models
12. Gather Requirements
13. Interviewing
14. Requirements Workshop
15. Brainstorming
16. Storyboarding
17. Use Cases
18. Prototyping
19. Recall: Inception Phase
20. Example of Use Cases
21. Recall: Elaboration Phase
22. Example of a Use Case Diagram
23. Delivery

Analysis Workflow

1. Analysis Workflow
2. Motivation
3. Analysis Deliverables
4. Good Analysis Characteristics
5. Analysis in the Rational Unified Process
6. Analysis Workflow Steps
7. Class Analysis
8. What is an Analysis Class?
9. Analysis Class Relationships
10. Use Case Analysis
11. Interaction Diagrams
12. Example Analysis Sequence Diagram
13. Example Analysis Collaboration Diagram
14. Architectural Analysis
15. Packages
16. Package Practicality
17. Example Package Diagram
18. Post Analysis

Design Workflow

1. Analysis and Design
2. Design Time
3. Design in RUP
4. Design vs. Analysis Model
5. One Model Or Two?
6. Design Workflow
7. Design Classes
8. Design Class Refinement
9. Design Class Refinement
10. Class Removal
11. Refining Relationships
12. Example Design Class Diagram
13. Use Case Design
14. Example Design Sequence Diagram
15. Construction

Software Architectural Styles

1. Client-Server Computing
2. Client-Server Pros/Cons
3. Case Study
4. Client-Server Example
5. Tiered Architectures
6. Single-tier Architecture
7. Single-tier Pros/Cons
8. Single-tier Example
9. Two-tier Architecture
10. Two-tier Pros/Cons
11. Two-tier Example
12. Three-tier Architecture
13. Three-tier Pros/Cons
14. Three-tier Example
15. N-Tier Architecture
16. N-Tier Pros/Cons
17. N-Tier Example

Designing Modern Applications

1. Web 2.0
2. Rich Internet Client Applications
3. Single Page Applications (SPA) with AngularJS
4. Two-way Data Binding (the AngularJS Way)
5. Other Client Side MV(C) Frameworks
6. \"Rich Client\" - \"Thin Server\" Architecture
7. Mobile Platforms
8. Types of Mobile Applications
9. Native Mobile Applications
10. Mobile Web Applications
11. Hybrid Mobile Applications
12. Hybrid App Tools and Frameworks
13. RIA as a Driving Force to Turn the \"Thin Server\" into Microservice(s)
14. So, How Can Microservices Help Me?
15. The Data Exchange Interoperability Consideration
16. Microservices in Their Purest Form: AWS Lambdas
17. The Microservices Architecture Design Principles
18. Decentralized Processing
19. Crossing Process Boundary is Expensive!
20. Managing Microservices
21. Traditional Enterprise Application Architecture (Simplified)
22. Microservices Architecture Example (Simplified)
23. Design for Failure
24. Fault Injection During System Testing