Categories
Career

As a software engineering tech lead, how would you draw boundaries for what your application should support?

The good things about software is that the boundaries can be defined for you or you can define the boundaries.

To be in position to draw the boundaries, I suggest using the principles of enterprise architecture, most specifically domain driven design.

First, to establish boundaries, you ought to define the tangible elements of your application. It is composed of:

  • It is located in a given business domain. For example Human Resources, Procurement, Order Fulfillment, IT Service Management, etc.
  • It fulfills a set of capabilities, in which the deriving processes defines business activities executed automatically by the application or by a human using the application. For example “Authenticate Users”, “Perform Customer Due Diligence”, “Manage Saving Accounts”, “Archive Medical Dossier”, etc.
  • It manipulates a set of data. For example “Person”, “Organization”, “Patient”, “Access Controls”, “Assets”, etc.
  • It will also be used by certain roles embodied by employees, customers or partners. For example “Customer Support Agent”, “Application System Administrator”, “Public User”, “Sales Agent, “Relationship Manager”, etc.
  • Finally there will a be set of underlying components such as technical accounts, database, configuration files, message queues/topics, certificates that belongs to the application, and the virtual/physical infrastructure.

The recipe for defining the boundaries of your application consist in identifying the direct, explicit and, if possible unique, responsibility upon the aforementioned elements.

To give you another example:

  • An application in the domain “Know your Customer”, catering for the capabilities “Customer Data Collection”, having the responsibility of the capabilities “Upload Documents”, “Categorise Documents”, “Manage Document Expiry”, “Search Customer Dossier”, “Verify Customer Dossier”, is responsible, as master data system, of Customer Identification Data and Customer Identification Documents. The functions and the data can only be triggered and managed by someone in the company having the roles defines for the application “Customer Due Diligence Officer” and the user as “Data Owner”. And this machine would run on four EC2 instances.
  • It means that the application consumed other applications (including external ones) as services. These are beyond the boundary of your application. These services would be responsible of user authentication (e.g. Active Directory), the central logging system (graylog), the monitoring and alerting system (Zabbix), using a Master Data System for importing customer basic product infor (ERP like SAP), etc.

This clear definition of boundaries are absolutely necessary for a proper DevOps implementation, because they directly indicate where the responsibilities of your teams lies in term of SLA, support model, finance, skills to maintain, documentation, etc.

By Yannick Huchard

Technology is my Business, Complexity is my playground, Strategy is my algorithm, precision execution, proven results.

I am devoting my life to knowledge, craft, and empowering people who want to do better for themselves and their surroundings.

About Yannick Huchard · Talks & Media

Leave a Reply