Jageshwar Tripathi

1. Decision Framework for NFRs Here’s a step-by-step process you can follow: Elicit and quantify the quality attributes / NFRs Gather from stakeholders (business, operations, security, compliance) what qualities they need: e.g., “system must respond within 2 seconds 95% of time”, “uptime 99.9%”, “must support 1000 concurrent users”, “must be maintainable by small team for 10+ years”, etc. For each NFR, aim for a measurable target (so you can trade-off). Use a structured taxonomy: e.g., from ISO/IEC 25010:2011: reliability, performance efficiency, security, maintainability, portability etc. jageshwartripathi.blogspot.com Assess constraints and context What is the environment? (Bare-metal, K8s on OpenStack, VMware Cloud) — you know your deployment scenarios. What is legacy/obsolescence risk? What existing systems are you integrating with? What is the budget/time-to-market? What organisational capabilities (DevOps, SRE, monitoring) are in place? What regulato...

 Diagram: Code: @startuml !include <archimate/Archimate> <style> element {     HorizontalAlignment: left;     MinimumWidth: 180;     Padding: 20; } note {     BackgroundColor: #FFFFCC;     RoundCorner: 5;     MaximumWidth: 250; } </style> left to right direction title "ArchiMate 3.2 Valid Serving Relationships" ' Strategy Layer Serving Relationships rectangle "Strategy Layer Serving" {     Strategy_Capability(cap1, "Capability 1")     Strategy_Capability(cap2, "Capability 2")     Rel_Serving(cap1, cap2, "serves")     note on link         Capability serving another         Capability     end note } ' Business Layer Serving Relationships rectangle "Business Layer Serving" {     Business_Service(bs1, "Customer Service")     Business_Process(bp1, "Fulfill Customer Request")     Rel_Serving(b...

  Diagram: Code: @startuml !include <archimate/Archimate> <style> element {     HorizontalAlignment: left;     MinimumWidth: 180;     Padding: 20; } note {     BackgroundColor: #FFFFCC;     RoundCorner: 5;     MaximumWidth: 250; } </style> left to right direction title "ArchiMate 3.2 Valid Triggering Relationships" ' Business Layer Triggering Relationships rectangle "Business Layer Triggering" {     Business_Event(be1, "Order Received")     Business_Process(bp1, "Process Order")     Rel_Triggering(be1, bp1, "triggers")     note on link         Event triggering a Process         (most common pattern)     end note          Business_Process(bp2, "Validate Order")     Business_Process(bp3, "Fulfill Order")     Rel_Triggering(bp2, bp3, "triggers")     note on link ...

Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 20 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > title "ArchiMate 3.2 Valid Flow Relationships" left to right direction ' Business Layer Flow Relationships rectangle "Business Layer Flows" {     Business_Process ( bp1 , "Order Process" )     Business_Process ( bp2 , "Payment Process" )     Rel_Flow ( bp1 , bp2 , "Order data" )     note on link         Flow between Business Processes     end note         Business_Function ( bf1 , "Sales Function" )     Business_Function ( bf2 , "Delivery Function" )     Rel_Flow ( bf1 , bf2 , "Sales information" )     note on link     ...

 Diagram Code @startuml !include < archimate / Archimate > < style > element {     HorizontalAlignment : left ;     MinimumWidth : 180 ;     Padding : 25 ; } note {     BackgroundColor : #FFFFCC ;     RoundCorner : 5 ;     MaximumWidth : 250 ; } </ style > left to right direction title "ArchiMate 3.2 Realization Relationships" rectangle "Business Layer" {     Business_Service ( service_customer_support , "Customer Support Service" )     Business_Process ( process_support , "Support Process" )     Rel_Realization ( process_support , service_customer_support , "Realization" )     note on link     Support Process realizes Customer Support Service.     end note     Business_Role ( role_manager , "Manager Role" )     Business_Collaboration ( collab_management , "Management Collaboration" )     Rel_Realization ( col...

 Diagram Code: @startuml !include <archimate/archimate> <style> element {     HorizontalAlignment: left;     MinimumWidth: 200;     Padding: 25; } note {     BackgroundColor: #FFFFCC;     RoundCorner: 5;     MaximumWidth: 250; } </style> left to right direction title "ArchiMate 3.2 Valid Assignment Relationships" rectangle "Business Layer Assignments" {     Business_Actor(actor_employee1, "Employee 1")     Business_Role(role_manager1, "Manager Role 1")     Rel_Assignment(actor_employee1, role_manager1, "Assignment")     note on link     An Employee can be assigned to a Manager Role.     end note          Business_Role(role_team_member1, "Team Member Role 1")     Business_Process(process_project_management1, "Project Management Process 1")     Rel_Assignment(role_team_member1, process_project_management...

 Diagram: Code: @startuml !include <archimate/archimate> <style> element {     HorizontalAlignment: left;     MinimumWidth: 180;     Padding: 25; } note {     BackgroundColor: #FFFFCC;     RoundCorner: 5;     MaximumWidth: 250; } </style> left to right direction title "ArchiMate 3.2 Valid Aggregation Relationships" rectangle "Business Layer Aggregations" {     Business_Actor(actor_organization, "Organization")     Business_Actor(actor_department, "Department")     Rel_Aggregation(actor_organization, actor_department, "Aggregation")     note on link     Business Actors can aggregate other Business Actors.     Organization aggregates Departments.     end note          Business_Collaboration(collab_project, "Project Team")     Business_Collaboration(collab_workgroup, "Work Group")     Rel_Aggreg...