Scribd Logo
Upload

Welcome to Scribd!

  • 4 views

    Session 5

    Uploaded by

    68jx6yxrrp
    The document describes a software system for managing client accounts, orders, and funds. It includes a mobile app and CRM/HRM package for employees and clients. The system allows users to open accounts, enter client data, check documents and funds, update statuses, create and track exchange orders, and enter inputs. The document recommends using a service-oriented architecture with internal APIs to access sensitive client data from multiple sources, as well as composite and SOAP APIs for data exchange between services.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content

    You might also like

    Session 5

    Uploaded by

    68jx6yxrrp
    4 views1 page
    The document describes a software system for managing client accounts, orders, and funds. It includes a mobile app and CRM/HRM package for employees and clients. The system allows users to open accounts, enter client data, check documents and funds, update statuses, create and track exchange orders, and enter inputs. The document recommends using a service-oriented architecture with internal APIs to access sensitive client data from multiple sources, as well as composite and SOAP APIs for data exchange between services.

    Original Description:

    Γγιη

    Original Title

    session 5

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document describes a software system for managing client accounts, orders, and funds. It includes a mobile app and CRM/HRM package for employees and clients. The system allows users to open accounts, enter client data, check documents and funds, update statuses, create and track exchange orders, and enter inputs. The document recommends using a service-oriented architecture with internal APIs to access sensitive client data from multiple sources, as well as composite and SOAP APIs for data exchange between services.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    4 views1 page

    Session 5

    Uploaded by

    68jx6yxrrp
    The document describes a software system for managing client accounts, orders, and funds. It includes a mobile app and CRM/HRM package for employees and clients. The system allows users to open accounts, enter client data, check documents and funds, update statuses, create and track exchange orders, and enter inputs. The document recommends using a service-oriented architecture with internal APIs to access sensitive client data from multiple sources, as well as composite and SOAP APIs for data exchange between services.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 1

    MODEL:

    Account
    Client
    Supporting documents
    Funds
    Order
    Inputs

    VIEW:
    Computer software for employees
    Mobile app for clients
    CRM & HRM package

    CONTROL:
    Open an account
    Enter client’s data
    Check supporting documents
    Update client status
    Verify the funds
    Update client status
    Check the reconciliation outcome
    Create an exchange order
    Update order status
    Create the bank receipt
    Enter the input
    Update the order status

    In my opinion a SoA should be used.

    APIs:
     Internal APIs: for the clients’ data, the funds, the income statements and other
    sensitive data
     Composite APIs: when someone interacts with a client and wants to get data from
    many different sources
     SOAP: a messaging protocol used to exchange structured data between web
    services. SOAP APIs use the XML format for data exchange, and they typically require
    more bandwidth and processing power than REST APIs. SOAP APIs support more
    advanced features like transaction, security, and reliability

    You might also like