Abstract

This paper introduces a case study that involves data leakage in a bank applying the so-called Thinging Machine (TM) model. The aim is twofold: (1) Presenting a systematic conceptual framework for the leakage problem that provides a foundation for the description and design of a data leakage system. (2) The aim in (1) is developed in the context of experimentation with the TM as a new methodology in modeling. The TM model is based on slicing the domain of interest (a part of the world) to reveal data leakage. The bank case study concentrates on leakage during internal operations of the bank. The leakage spots are exposed through surveying data territory throughout the bank. All streams of information flow are identified, thus points of possible leakage can be traced with appropriate evidence. The modeling of flow may uncover possible hidden points of leakage and provide a base for a comprehensive information flow policy. We conclude that a TM based on the Heideggerian notion of thinging can serve as a foundation for early stages of software development and as an alternative approach to the dominant object-orientation paradigm.

Highlights

  • In software engineering, models have a central role in achieving a high level of reliability in the design, development, and deployment of systems

  • We study the prospect that data has leaked along several points of the flow path, and we propose a flow-based model that facilitates the identification of leakages

  • As mentioned previously, presenting a systematic conceptual framework for the data leakage problem is developed in the context of experimentation with a Thinging Machine (TM) as a new methodology in modeling, alongside other methodologies such as object orientation

Read more

Summary

INTRODUCTION

Models have a central role in achieving a high level of reliability in the design, development, and deployment of systems. In this context, we are interested in utilizing a conceptual model, the Thinging Machine (TM); reviewed ), for the specification of the early phase of the life cycle of development in software systems. Our aim is twofold: 1) Presenting a systematic conceptual framework for the leakage problem that provides a foundation for the description and design of a data leakage system. 2) The aim in (1) is developed in the context of experimentation with TM as a new methodology in modeling side by side with other methodologies such as object orientation. We will discuss the justification for pursuing such a venture later

Background about Information Leakage
Aim and Approach with Regard to Information Leakage
Aim with Regard to Exploring a New Modeling Methodology
THINGING MACHINE
BANK AS A THING
BANK AS A CASE STUDY
LEAKAGE SUBMACHINES
27 Rejection 28 Create
CONCLUSION
Findings
Messenger
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call