> For the complete documentation index, see [llms.txt](https://bpmflow.gitbook.io/project/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bpmflow.gitbook.io/project/engineering-models/4+1-architecture-models.md).

# 4+1 Architecture Models

 In this chapter all technical information will be shown in detail.\
 The information is in the **4+1 architectural model** format\
&#x20;(<https://en.wikipedia.org/wiki/4%2B1_architectural_view_model>).

![](/files/-LHEk5O3vAgLkyj2hDT9)

4+1 is a view model designed by Philippe Kruchten for "describing the architecture of software-intensive systems, based on the use of multiple, concurrent views". The views are used to describe the system from the viewpoint of different stakeholders, such as end-users, developers and project managers. The four views of the model are logical, development, process and physical view. In addition selected use cases or scenarios are used to illustrate the architecture serving as the 'plus one' view. Hence the model contains 4+1 views.\
&#x20;Source:\
&#x20;<https://en.wikipedia.org/wiki/4%2B1_architectural_view_model>

{% content-ref url="/pages/-LHEkD-qwxkpvcmwi1Uh" %}
[Logical View](/project/engineering-models/4+1-architecture-models/logical-view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LHEkF5dIxJDXd8\_jFJ9" %}
[Development View](/project/engineering-models/4+1-architecture-models/development-view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LHEkFcvd9BOm6Cqof8U" %}
[Process View](/project/engineering-models/4+1-architecture-models/process-view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LHEkG3ZgKocJba4DF-Z" %}
[Physical View](/project/engineering-models/4+1-architecture-models/physical-view.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LHEkWLgEtCOa3v0v88Z" %}
[Scenarios](/project/engineering-models/4+1-architecture-models/scenarios.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bpmflow.gitbook.io/project/engineering-models/4+1-architecture-models.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.