Abstract
Abstract - The paper discusses application of the topological functioning model (TFM) of the system for its automated transformation to behavioural specifications such as UML Activity Diagram, BPMN diagrams, scenarios, etc. The paper addresses a lack of formal specification of causal relations between functional features of the TFM by using inference means suggested by classical logic. The result is reduced human participation in the transformation as well as additional check of analysis and specification of the system.
Highlights
Software engineering means analysis and modelling of systems and corresponding software
The metamodel is described at the MOF (Meta Object Facility) metalevel M2, and represents the topological functioning model (TFM) as an instance of the metaclass TFMTopologicalFunctioningModel that includes at least two functional features of the metaclass TFMFunctionalFeature
The functional features can be associated with several goals, the metaclass TFMUserGoal, which are established by direct users of the business or software system [18]
Summary
Software engineering means analysis and modelling of systems and corresponding software. The computation independent viewpoint should consider both software and system, providing the correspondence of the software model to the system model [9], [10]. In author’s opinion, determination of cause-and-effect (causal) relations between functional features of the TFM of business is still an issue. There are open questions on the scope of relations, their necessity and sufficiency as well as temporal characteristics Besides it is not clear enough how causality of the TFM of the system should be reflected in software models. This paper discusses theoretical foundations of cause-andeffect relations of the TFM by considering logical and mathematical characteristics of causal implication.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have