Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software architecture_, SA (D. E. Perry and A. L. Wolf. Foundations for…

- - - - provide some insights (cro. uvidi ) for SA
        
        style and materials
        
        multiple views
        
        arhitectural views
        
        processing views
        
        WHAT
        
        emphasizes the data flow through the componnents and some aspects of the connections among the components with respect to the data
        
        connection views
        
        WHAT
        
        emphasizes the relationship between components and the state of communication
        
        data views
        
        WHAT
        
        emphasizes the processing flow, with less emphasis on the connectors
        
        style and engineering
        
        arhitectural styles
    - - network-based arhitecture style #
        
        client - side
        
        Facebook
        
        Flux
        
        :question::
        
        hybrid style
        
        Representational state transfer, REST
        
        About
        
        arhitecture
        
        3 more items...
        
        :question:
        
        behaviors
        
        1 more item...
        
        standards
        
        3 more items...
        
        example software
        
        1 more item...
        
        TERMS
        
        statelessness
        
        1 more item...
        
        URL
        
        2 more items...
        
        APPLICATION STATE
        
        1 more item...
        
        hierarchical style
        
        Client-Server, CS
        
        About
        
        def through components
        
        2 more items...
        
        derivats
        
        Remote Session, RS
        
        Layered-Client-Cache-Stateless-Server, LC$SS
        
        Client-Cache-Stateless-Server, C$SS
        
        Client-Stateless-Server, CSS
        
        Layered-Client-Server, LCS
        
        replication styles
        
        Cashe
        
        Replicated repository, RR
        
        classification methidology
  - - - rationale
        
        configuration
        
        WHAT
        
        collections of interacting components and connectors
        
        structure of arhitectural relationships among components, connectors, and data during a period of system run-time
        
        WHAT
        
        provides the underlying basic for the architecture in terms of the system constraints, which most often derive from the system requirements
      - form
        
        :question:
        
        properties
        
        WHAT
        
        defined in terms of preoperties of , and the relationships among , elemnts - that is, the constraints on the elements
      - elements
        
        WHAT
        
        form
        
        defined by the properties of the elements and the relationships among the elements
        
        present a model that defines a software arhitecture as set of arhitectural elements that have a particular form
        
        element types
        
        connecting elements
        
        connectors
        
        WHAT
        
        enable communication between componenets by transferring data elements from one interface to another without changing the data
        
        an abstract mechanism that mediates communication, coordination, or cooperation among componenets
        
        WHAT
        
        perform transformations
        
        data elements
        
        datum
        
        an elemnt of information that transferred from a component, or received by a component, via a connector
        
        WHAT
        
        processing elements
        
        componnents
        
        WHAT
        
        an abstract unit of software instructions and internal state that provides a transformation of data via its interface
        
        1 more item...
        
        WHAT
        
        those that contain the information that is used and transformed
- - - - Multiple Page Application, MPA
      - Single Page Application, SPA
    - - Remote Procedure Calls
- - - - process control
      - pipes and filters
      - interpreters
      - object-oriented
        
        variants
        
        Microsoft's Component Object Model, COM
        
        About
        
        An interface is a “named” collection of methods having a
        predefined purpose and call/return protocol
        
        A collection of rules and restrictions on how objects may be both used and managed
      - repositories
      - implicit invocation
      - layered
        
        variant
        
        N -Tier, 3 -Tier
        
        Domain Driven Design, DDD
    - - microservice arhitecture
        
        testing
        
        security
        
        external API
        
        communication style
        
        cross cutting concerns
        
        deployment
        
        decomposition
        
        core
        
        microservice
        
        monolithic
      - Web services
      - service contract
        
        published technical interface
    - - technology
        
        Django
        
        Android
        
        Ruby
        
        Ruby on Rails
        
        ASP.NET
      - Model - View - Controller, MVC Pattern
        
        What ?
        
        Model, M
        
        Structures you data in a reliable form and prepares it based on controller's instructions
        
        Controller, C
        
        Takes in user commands, sends commands to the model for data updates, sends instructions to view to update interface
        
        View, V
        
        Displays data to user in easy-to-understand format, based on the user's actions
        
        Variant
        
        Model - View - View Model, MVVM
        
        Model - View - Presenter, MVP
        
        Model - View - Adapter, MVA
        
        Hierarchical Model - View - Controller, HMVC
    - - domain
        
        Domain Driven Design, DDD
        
        Description
        
        An object-oriented architectural style focused on modeling a business domain and defining business objects based on entities within the business domain
      - deployment
        
        N - Tier
        
        3 - Tier
        
        Client/Server
        
        variations
        
        systems
        
        Client-Queue-Client systems
        
        application
        
        Application servers
        
        Peer-to-Peer (P2P) applications
        
        Description
        
        Segregates the system into two applications, where the client makes requests to the server. In many cases, the server is a database with application logic represented as stored procedures
      - structure
        
        Layered Architecture
        
        Description
        
        Partitions the concerns of the application into stacked groups (layers)
        
        Object - oriented
        
        Description
        
        A design paradigm based on division of responsibilities for an application or system into individual reusable and self-sufficient objects, each containing the data and the behavior relevant to the object
        
        Component-Based
        
        tehnology
        
        Microsoft .NET
        
        Description
        
        Decomposes application design into reusable functional or logical components that expose well-defined communication interfaces
      - communication
        
        Message Bus
        
        variations
        
        Internet Service Bus, ISB
        
        Enterprise Service BUS, ESB
        
        Description
        
        An architecture style that prescribes use of a software system that can receive and send messages using one or more communication channels, so that applications can interact without needing to know specific details about each other
        
        Service-Oriented Arhitecture, SOA
        
        Description
        
        Refers to applications that expose and consume functionality as a service using contracts and messages
- - - - an architecture that focuses on a separation of the functionality into many independent systems, making the complete logical system a collaboration of many smaller software systems
    - - autonomous web application
      - each SCS is owned by one team