Overview of architecture description based on views Sample Clauses

Overview of architecture description based on views. For D4.2 we have chosen to use model views to explain the architecture. The most common view model is the 4+1 view model of Xxxxxxxx [Xxxxxxxx, 1995]. Here, the ‗+1 view‘ refers to scenarios (and potentially also use cases), which help understand the alignment between other views. This approach of using views, or view points, also helps explain the architecture from the perspective of the customer/end-user, the designer and the creator (Figure 17). Logical-Conceptual View Development VIew Scenarios Process VIew Physical View Figure 17 Xxxxxxxx 4+1 Architectural View Model For PICOS we have slightly adapted the model by changing the description of the views, as shown in Table 7 below. Xxxxxxxx PICOS Development View Building Block View Physical View Deployment View Logical-conceptual View Trust, Privacy and IdM View Process View PICOS Use Cases Table 7 Mapping from Xxxxxxxx to PICOS view model Whilst the mapping from Local-conceptual View to Trust, Privacy and IdM View is slightly unusual, we justify the action on the basis that both describe core internal/external functionality. Similarly, we map Process View to the set of PICOS use cases since their common ground is processes, activities and workflows (Figure 18). Building Block View Privacy, Trust and IdM VIew Scenarios Deployment View PICOS Use Cases Figure 18 PICOS Architectural View Model In the remainder of this sub-section we describe the three main views formally, before moving on to a more details description in sub-sections 8.2, 8.3 and 8.4.