Materials and Procedures

The architectural model portrays one perspective or view of the system. It could

demonstrate how a system is decomposed into modules, how run-time processes interact, or the

various ways system components are distributed across a network. It’s also a representation of an

entire system from the perspective of a related set of concerns and is used to describe the system

from the viewpoint of different stakeholders such as end-users, developers, project managers,

and testers. The researchers will adopt the 4+1 Architectural View Model (4+1 AVM) shown in

Figure 3 as the architectural framework of this study.

Fig 3. The 4+1 Architectural View Model

According to Simon (2019), Philippe Kruchten proposed the 4+1 AVM in 1995 to

organize the description of a software architecture using a set of concurrent "views," each
addressing specific concerns for specific stakeholders. Jayawardene (2017) added that 4+1 AVM

is used to describe the architecture design of software-intensive systems using multiple

concurrent views. Because each end-user, developer, system engineer, and project manager have

a unique perspective on the system, viewpoints are used to describe it from their point of view.

There are four views in the 4+1 AVM namely; logical, process, development, and physical view.

Furthermore, selected use cases or scenarios are used to illustrate the architecture, which serves as

the '+1’ view which serves as the system's functionality or capabilities. The scenario view is what

guides all the other views (Comartin, 2019). Different diagrams such as Unified Modeling

Language (UML) diagrams can be used to describe each view (Jayawardene, 2017).

Logical View
The logical view, also known as the structural view, is the object model of the design and

is concerned with the functionality of the system as it pertains to end-users (Jayawardene, 2017).

When looking for service boundaries, this architecture is extremely useful. The emphasis should

be on describing the problem that must be solved. The logical view depicts the system as a

decomposition of distinct functional areas and should provide terms of services to its end-users.

To demonstrate all of the proposed web portals’ functionalities, including all of its

features and problems that must be resolved, the researchers will create a UML class diagram to

model the web portal's objects, a UML object diagram to show the relationship between web

portal objects, a UML star machine diagram to show the order of states undergone by an object

within the web portal, and a UML composite structure diagram to provide a logical overview of

all web portal components.

Process View
 The process view is concerned with the system's dynamic elements and focuses on the

system's run-time behavior. It describes the system processes and how they interact. The process

view addresses concurrency, distribution, integrator, performance, and scalability. The process

view's primary goal is to depict how processes will be exchanged between business entities

(Pokala, 2021) or how those processes will communicate with one another (Hussain, 2016).

In order to determine how the proposed web portal processes will interact with one

another during run-time behavior, the researchers will make a UML sequence diagram to

describe how and in what order a group of objects works together and illustrates the sequence of

messages between objects in an interaction in the web portal, a UML communication diagram to

shows the interactions between the objects or roles associated with lifelines and the messages

that pass between lifelines in the web portal, a UML activity diagram to describe what must

happen in the system being modeled and to represent the flow from one activity to another in the

web portal, UML timing diagram to describes how an object underwent a change from one form

to another in the web portal, and UML interaction overview diagram to an overview of the flow

of control in the web portal.

Development View
The development view, also known as the implementation view, serves as the foundation

for requirement allocation, work allocation to teams or even team organization, cost evaluation

and planning, project progress monitoring, and reasoning about software reuse, portability, and

security. It serves as the foundation for developing a product line (Raghavan, 2017). This view

depicts the system from the developer's perspective. One of the main areas of focus is the

organization of software modules in the development environment (Jayawardene, 2017).

the researchers will create a UML component diagram to describe the organization and wiring of

the physical components as well as a UML package diagram to show the organization and

arrangement of various model elements in the web portal. These diagrams will also be used by

the researchers to allocate work and determine the cost of the web portal's evaluation, planning,

and security.

Physical View
The physical view, also known as the deployment view, depicts the system as seen by a

system engineer. The physical view is concerned with the topology of software components as

well as their physical connections. Comartin (2019) stated that this viewpoint is service

deployment. Raghavan (2017) added that it describes the mappings of software onto hardware and

reflects its distributed aspect, as well as the static organization of software in its development

environment.

For the researchers to be able to map the topology and physical connection of the

proposed web portal, a UML deployment diagram, and network topology will be used. The UML

Deployment diagram will be used to depict the execution architecture of a web portal, which will

include nodes such as hardware or software execution environments, as well as the middleware

that connects them. The network topology will be used to define the layout, structure, and shape

of a network, both physically and logically.

Scenario View
The scenario view, also known as the use-case view, consists of use-cases or scenarios

that are used to illustrate the architecture description. According to Hussain (2016), this view

demonstrates the validation and illustration of system completeness. The scenario view describes
the sequences of interactions between objects and processes. They are used to identify

architectural aspects as well as to demonstrate and evaluate the architectural design. They can

also be used as a starting point for testing architectural prototypes (Jayawardene, 2017).

To elaborate, illustrate or describe the proposed web portals’ architecture description as

well as the system completeness, and interaction between objects and processes, the researchers

will create and use a UML use-case diagram and user story map. UML use-case diagram will be

used to summarize the details of the residents and their interactions with the web portal.

Whereas, user story map will be used for identifying the features of a system underdeveloped,

capturing what a resident does or needs to do and how they wish to interact with or use the web

portal. 

Reference
Jayawardene, P. D. (2017, September). 4+1 Architectural view model in Software. Java
Revisited. Retrieved November 16, 2021, from https://medium.com/javarevisited/4-1-
architectural-view-model-in-software-ec407bf27258
Simon, D. (2019, February). History of the 4+1 Architectural View Model. Dev Cycles.
Retrieved November 16, 2021, from https://devcycles.io/2019/02/28/history-of-the-4-1-
architectural-view-model/
Comartin, D. (2019, July). 4+1 Architectural View Model. Code Opinion. Retrieved November
16, 2021, from https://codeopinion.com/41-architectural-view-model/
Raghavan, G. (2017, March). Architectural Blueprints – The “4+1” View Model of Software
Architecture. Brain Kart. Retrieved November 17, 2021, from
https://www.brainkart.com/article/Architectural-Blueprints---The----4-1----View-Model-
of-Software-Architecture_11289/
Hussain, B. (2016, November). 4+1 View Model of Software Architecture. Scribd. Retrieved
November 17, 2021, from https://www.slideshare.net/bashcode/41-view-model-of-
software-architecture
Pokala, P. (2021, January). 4+1 View Model of Architecture. Integrate. Retrieved November 17,
2021, from https://pokalablog.wordpress.com/2021/01/05/41-view-model-of-architecture/