Please enable JavaScript.

Coggle requires JavaScript to display documents.

Software Engineering - Coggle Diagram

- - - - SOAP
      - WSDL
      - UDDI
      - REST
        
        Architectural style, identifying how resources in a network are defined, addressed and accessed
        
        Services stack
        
        Business logic
        
        Data layer
        
        Transport & communication
        
        Presentation
  - - - WS-* family
      - Feed/Stream Services
      - RESTful services
- - - - Terraform
        
        is declarative
    - - Virtualisation
        
        Container
        
        User space
        
        Shares hardware with host
        
        Virtual machine
      - Tools
        
        Packer
        
        Docker
      - Creates image (snapshot) of the machine state
    - - Kubernetes
    - - Tools
        
        Puppet
        
        Ansible
        
        is procedural (non dynamic)
        
        Chef
      - Goods
        
        Conventions
        
        Distribution
        
        Idempotence, runs as many times as you want
    - - Can be in general purpose languages
      - Preferably small, single responsible
- - - - Classic web features
      - Extensions nécessaires
      - Time to market
      - Assemblage > programming
    - - Diffusion d'info
      - Controle d'info
      - Auto documenting
      - E-commerce
    - - URI identified software system, defined in WSDL, activated by HTTP
      - Properties
        
        D'être décrit
        
        Easily discoverable
      - Roles
        
        Service provider
        
        XML accessible app running in server
        
        Process
        
        Create core functionality
        
        Create xml rpc or soap service wrapper
        
        Wsdl description or xmlrpc integration instructions
        
        Deploy services
        
        Register UDDI
        
        Service requester
        
        Caller with xml requests
        
        Process
        
        Find service using UDDI
        
        Retrieve wsdl or xmlrpc instructions
        
        Create xml-rpc of soap client
        
        Invoke services
        
        Service registry
      - Stack
        
        Transport
        
        Xml message
        
        Soap and rpc
        
        Service description
        
        Discovery
      - Xml rpc
        
        Ways of working
        
        Glue code
        
        Ex. Unix - windows
        
        Publishing services
        
        Subdivisions
        
        Data model
        
        Integer (int,i4)
        
        double
        
        Boolean
        
        String
        
        dateTime.iso8601
        
        Binaries (base64)
        
        Array(value+)
        
        struct(ANY)
        
        Request structures
        
        Combining http headers and xml content
        
        MethodCall(methodName,params(param(value+)+))
        
        Response structures
        
        methodResponse(fault | params...)
        
        Always 200 code, even in faults
        
        Soap
        
        Successor of xmlRpc
        
        Main parts
        
        Envelope specifications
        
        Data encoding rules
        
        Rpc conventions
        
        Interaction
        
        Client
        
        Opening http connection
        
        Soap request (method,params)
        
        Server
        
        Récupère
        
        Execute
        
        Soap response
        
        Specifications
        
        Http protocole
        
        Http post
        
        Message
        
        Envelope
        
        Header
        
        Body (optional)
        
        Fault (optional)
        
        Binding
        
        Serialising
        
        Enveloping
      - Wsdl
        
        Specification
        
        Critical pieces of information
        
        Les informations de l’interface décrivant toutes les fonctions publiques fournies
        
        Les types de données pour chaque message de requête/réponse
        
        Les informations sur le protocole de transport à utiliser
        
        Les informations sur les adresses des services spécifiés
        
        Elements
        
        Root
        
        definitions name="serviceName"
        
        Types
        
        Message
        
        PortType
        
        Binding
        
        Specifie comment portType operation est transmise
        
        Service
        
        Operation models
        
        One-way: le service reçoit un message. L’opération a un simple élément input.
        
        Request-response: Le service reçoit une requête et renvoie une réponse «operation » a un élément input et un élément output. Un élément « fault » peut aussi être spéciﬁé.
        
        Sollicit-response: Le service envoie un message et reçoit une réponse input, output et fault possible
        
        Notiﬁcation: Le service envoie un message. L’opération a unique élément output
        
        Défi
        
        Inter OS data typing
        
        Not here to define xml schema types
        
        Loose coupling
        
        Rest
      - UDDI
        
        Parties principales
        
        Spécification technique to define web serv
        
        Business registry
        
        Description
        
        Pages blanches
        
        Business entities
        
        Pages jaunes
        
        Business service
        
        Pages vertes (for bindings)
        
        Template
        
        Model
  - - - Client-server
        
        Client
        
        Use auto functionalities
        
        Know servers
        
        Types
        
        Léger
        
        Canal et serveur surchargés
        
        Good for legacy
        
        Lourd
        
        Fait des traitements
        
        Updates mean reinstalling
        
        Harder to manage
        
        Server
        
        Doesn't know clients
        
        Ensures auto functionalities
        
        3 tiers
      - P2P
        
        Each node has a copy
        
        App has all communication protocoles
        
        Types
        
        Décentralisé
        
        Semi centralisé
      - RPC
        
        Trying to scale OO object over network(ok for LAN, not for internet)
    - - Rules
        
        Well formed
        
        Doit commencer par une déclaration xml
        
        A unique root
        
        Case sensitivity
        
        nesting rules
        
        Emptiness rule
        
        Only one attribute/element and only one value
        
        Attributs & guillemets
        
        Valide
        
        Bien formé
        
        Conformity with a schema
        
        References a grammar
        
        namespaces allow many grammars
- - - - CCP
        
        The Common Closure Principle
        
        Single responsibility in components
        
        Group for maintenance
        
        Important at the beginning of development
      - CRP
        
        The Common Reuse Principle
        
        Interface segregation in generic version
        
        Split to avoid uneeded releases
      - REP
        
        Group for reusers
        
        The Reuse/Release Equivalence Principle
    - - "The morning after" syndrome
      - THE WEEKLY BUILD
        
        Integration on fridays
        
        For medium sized projects
      - ELIMINATING DEPENDENCY CYCLES
        
        Each team has a component
      - THE STABLE DEPENDENCIES PRINCIPLE