Positioning of Architectures

Positioning of Architectures

The discussion relating to the positioning of architectures alongside the dimensions of aggregation and abstraction is given herein, together with its influence on granularity and concreteness. Three levels of detail are highlighted by the aggregation dimension, which includes the market level, party level, and system level. On the other hand, the abstraction dimension identifies the number of features within architecture. Further, granularity and aggregation decrease and increase based on the location of the architecture within the abstraction and aggregation dimensions. A focused analysis of the abstraction and aggregation dimensions will result in a better understanding of the management of complex interoperability by architectures among various e-business organizations and e-business systems.

On the aggregation dimension, the market level, system level, and party level scopes of architecture are separated. The size of the architecture is the primary factor determining the levels. The market level is the largest, whereby inter-organizational architectures manage multiple parties. The party level of aggregation dimension handles architectures within the organizations that do not touch parties outside the business, while the system level is a single system within a party that functions by facilitating particular business operations (Tutaj et al., 2021). On the other hand, the abstraction dimension relates to architecture’s number of features. For instance, a specific area can be identified by architecture as an e-payment system; for that matter, it would be more abstract than XPay E-payment Server Version. Notably, architecture will be more concrete and less abstract when the e-business system within the architecture is more specific. An example of aggregation and abstraction dimensions can be that of viewing a map whereby an individual starts with a continental level, then a national level, which can be equated to the market level, then scaling down to city or county levels, which can be equated to party levels and finally into even smaller regions such as the neighborhood which can be equated to the system level.

Granularity and concreteness are important aspects in the positioning of architecture. They are used to advance the details of abstraction and aggregation dimensions. Particularly, granularity is applied in detailing the scope or size of architecture (Mascate & Vasconcelos, 2020). For example, the aggregation dimension’s market level tends to be more granular as compared to architectures drawn from the part level aspect of the same dimension. On the other hand, concreteness works contrary to abstraction, whereby it is applied in an opposite way as in abstraction. Notably, when architecture contains more details, the level of concreteness increases, and as a result, the level of abstraction will reduce.

When handling architecture at the market level, it is recommended and acceptable to utilize an architecture that is relatively more in aggregation and abstraction. Notably, this is so because, at the lower levels, more details can be provided. For the system level, more concreteness and granularity should be encouraged to ensure it is clear to see all details. For successful management of the BOAT framework, it is important to use the abstraction and the aggregation levels as blueprints. The abstraction and aggregation dimensions form an important basis for understanding how architectures help in managing operations between various e-business organizations and e-business systems. For example, they can help understand how PayPal operations work using e-business. Essentially, the company, a smart e-business that facilitates payments for businesses, has attached a bonus system to its customer checkout, which motivates customers to use the platform for payments.

References

Mascate, M., & Vasconcelos, A. (2020). E-Business Reference Modelling Framework for SMEs: An Enterprise Architecture-based Approach. In ICEIS (2) (pp. 693-700).

Tutaj, J., Rutkowska, M., & Bartoszczuk, P. (2021). Enterprise business architecture as a tool for sustainable development in an enterprise-case study. Procedia Computer Science, 192, 5050-5057.

ORDER A PLAGIARISM-FREE PAPER HERE

We’ll write everything from scratch

Prompt:

Explain how the positioning of architectures along the aggregation dimension (market-level, party-level, and system–

Positioning of Architectures

level) and abstraction dimension determines granularity and concreteness, respectively. Use examples to illustrate.