Dependencies among Architectural Views Got from Software Requirements Based on a Formal Model

Abstract

-A system architect has software requirements and some unspecified knowledge about a problem domain (e.g., an enterprise) as source information for assessment and evaluation of possible solutions and getting the target point, a preliminary software design. The solving factor is architect's experience and expertise in the problem domain ("AS-IS"). A proposed approach is dedicated to assist a system architect in making an appropriate decision on the solution ("TO-BE"). It is based on a formal mathematical model, Topological Functioning Model (TFM). Compliant TFMs can be transformed into software architectural views. The paper demonstrates and discusses tracing dependency links from the requirements to and between the architectural views.

Comparing Transformation Possibilities of Topological Functioning Model and BPMN in the Context of Model Driven Architecture

“…The approach provides ways of obtaining TFM from the knowledge about a business system [24]- [27]; derivation of use case diagrams from TFM [28]; transformations of TFM to the most popular UML [29] design models on PIM level, e.g., Class diagram, Sequence diagram, Communication diagram [30]- [32]; formalizing tracing links between modelling artefacts [33]; and other opportunities for formalized software development.…”