Estilos e Vistas da Arquitetura de Software

Software Architecture Styles

• Software architectures are a set of structural and organizational decisions that define the design and operation of a software system.
• They play a fundamental role in the software engineering process, acting as a plan that guides development, evolution, and maintenance of a system.
• Key architectural components include: Components (or Modules): These are independent parts of the system that perform specific functions, like libraries, services, classes, or other software elements.
• Conexões (or Conectores): These represent interactions between components, such as function calls, APIs, messages, or events.
• Restrições e Regras: These are guidelines defining how components and connectors interact to ensure the system meets desired requirements

Software Architecture Views

• Architectural views represent the architecture from different perspectives:
• Logical View: Focuses on system behavior and functionalities.
• Physical View: Describes the hardware infrastructure where the software will run.
• Development View: Shows how the software is organized for construction and maintenance.
• Process View: Considers system execution, concurrency, and communication aspects.

Importance of Software Architecture

• Provides a Foundation for Decision Making: Helps in making decisions about technologies, frameworks, programming languages, and design patterns.
• Enhances Evolution and Maintainability: Facilitates adding new features, correcting errors, and adapting to changes.
• Improves Communication: Creates a common model for developers, managers, clients, and other stakeholders to understand and collaborate.
• Supports Quality Assurance: Helps in meeting quality requirements, such as performance, scalability, reliability, and security.

Software Architecture Creation Process

• Understanding Requirements: Gathering and analyzing functional and non-functional requirements.
• Modeling: Representing the architecture with diagrams and documents explaining its structure and behavior.
• Architectural Style Selection: Choosing appropriate architectural styles (e.g., client-server, microservices, monolithic) based on requirements.
• Evaluation: Employing techniques to assess the effectiveness of the proposed architecture.
• Documentation and Communication: Documenting and presenting the architecture to ensure everyone understands and can contribute.

Relation with Software Engineering

• Architecture connects all stages of the software development life cycle.
• It influences requirements analysis, design, implementation, testing, and maintenance phases.

Architectural Styles

• Different architectural styles exist for specific needs:
• Monolithic: Application logic is organized as a single unit, making it easy to develop but complex to maintain and scale.
• Microservices: Architecture is composed of small, independent services enabling continuous delivery but creating complexity in communication management.
• Service-Oriented (SOA): Re-usable services communicate via standardized protocols facilitating easier integration across platforms but can have increased communication overhead.
• Layered: Organizing application logic into separate logical layers.
• Client-server: Dividing an application into separate clients and servers.
• Component-Based: Separating system into a core and separate modules for extended functionality.
• Event-Driven: Components respond to events rather than predefined sequences.
• Distributed Systems: Splitting data and processes into locations to achieve fault tolerance and scalability.
• Domain-Driven Design (DDD): Aligning architecture with business domain, leading to better maintainability.
• Hexagonal/Clean Architecture: Separating concerns of data access from application logic.
• Interpreter: Converts high-level code into executable instructions.
• Publish-Subscribe: Components are connected by events.
• Model-View-Controller (MVC) and Model-View-Presenter (MVP): Architectures for separation of UI and business logic.
• Space-Based: Distributes data and processes into different spaces.
• CQRS (Command Query Responsibility Segregation): Separates data modification and retrieval.
• Pipe-and-Filter: Passing data through a sequence of independent filtering processes.
• Shared Repository: Placing the shared data in a central location.

Cloud-Based Architecture

• Cloud Computing: Provides on-demand IT resource capability as a service.
• Advantages: Scalability, cost-effectiveness, and reduced infrastructure costs.
• Disadvantages: Vendor lock-in, security concerns, and possible latency issues.

Fog Computing

• Fog Computing: Processes data near the user thereby decreasing latency and network traffic.
• Advantages: Improved data processing speeds and reduced bandwidth usage.

Cloud-Fog Hybrid Architecture

• Combines both cloud computing and fog computing advantages, using fog computing near the data source and cloud computing for processing and storage needs.
• A combination of these paradigms allows more distributed processing power with a balance of responsiveness from near data sources and scalability of cloud computing.