{"id":4414,"date":"2026-01-19T11:47:43","date_gmt":"2026-01-19T03:47:43","guid":{"rendered":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/architecture-centric-development\/"},"modified":"2026-01-26T16:02:09","modified_gmt":"2026-01-26T08:02:09","slug":"architecture-centric-development","status":"publish","type":"docs","link":"https:\/\/guides.visual-paradigm.com\/tw\/docs\/mastering-uml-2-5-a-use-case-driven-approach-to-agile-modeling\/module-5-agile-architecture-and-implementation-workflows\/architecture-centric-development\/","title":{"rendered":"Architecture-Centric Development:"},"content":{"rendered":"

Using the five views of architecture (Use Case, Design, Process, Implementation, Deployment) as primary artifacts for system evolution<\/strong><\/h2>\n

Architecture-centric development places the system architecture<\/strong> at the heart of the project\u2014not as a static blueprint created once at the beginning, but as a living, evolving set of artifacts<\/strong> that guide every iteration, reduce risk, enable parallel work, and keep models, code, and reality in alignment. In an Agile, use-case-driven approach, architecture is treated as the primary mechanism for conceptualizing<\/strong>, constructing<\/strong>, validating<\/strong>, managing<\/strong>, and evolving<\/strong> the system incrementally.<\/p>\n

UML 2.5<\/a> supports this through the well-known 4+1 views<\/strong> model (originally proposed by Philippe Kruchten), which organizes architectural description into five interlocking views<\/strong>. Each view is a projection of the system tailored to the concerns of specific stakeholders, and together they form a coherent, traceable whole. These views are not separate documents<\/strong>\u2014they are overlapping, interconnected perspectives of the same underlying model<\/strong> (the semantic backplane in tools like Visual Paradigm). Changes in one view propagate consistently to others.<\/p>\n

The Five Views and Their Roles<\/h3>\n
    \n
  1. Use Case View<\/strong> Describes system behavior as seen by external actors<\/strong> \u2014 the functional requirements, goals, and value delivered. It is the driver<\/strong> of the entire architecture. Primary audience: End users, product owners, analysts, testers.<\/li>\n
  2. Design View<\/strong> (also called Logical View) Captures the vocabulary<\/strong> of the problem and solution spaces: classes, interfaces, collaborations, subsystems, and mechanisms that realize use cases. Focuses on functional structure<\/strong>. Primary audience: Developers, architects.<\/li>\n
  3. Process View<\/strong> Addresses concurrency<\/strong>, threads<\/strong>, processes<\/strong>, synchronization<\/strong>, and runtime flows<\/strong> \u2014 how the system behaves dynamically under load. Tackles non-functional requirements such as performance, scalability, throughput, and fault tolerance. Primary audience: Performance engineers, DevOps, architects.<\/li>\n
  4. Implementation View<\/strong> (Component View) Describes the physical organization<\/strong> of software: components, libraries, executables, files, modules, and their assembly into releasable units. Focuses on configuration management<\/strong>, build<\/strong>, and release<\/strong>. Primary audience: Developers, build engineers, configuration managers.<\/li>\n
  5. Deployment View<\/strong> Maps software artifacts to hardware topology<\/strong>: nodes (servers, devices, containers, cloud instances), communication paths, and distribution strategy. Addresses deployment<\/strong>, installation<\/strong>, scalability<\/strong>, and operational concerns<\/strong>. Primary audience: DevOps, infrastructure teams, operations, security.<\/li>\n<\/ol>\n

    These five views interact continuously<\/strong>: a change in the Use Case View ripples through Design \u2192 Process \u2192 Implementation \u2192 Deployment. In Agile, the views evolve incrementally<\/strong> \u2014 starting lightweight in early sprints and gaining fidelity as risks are addressed and understanding deepens.<\/p>\n

    Practical Examples of Using the Five Views for System Evolution<\/h3>\n

    Here are numerous real-world-inspired examples showing how the five views serve as primary artifacts across different projects:<\/p>\n