Topological Functioning Model Research Articles

Security Requirements Specification and Tracing within Topological Functioning Model

Specification and traceability of security requirements is still a challenge since modeling and analysis of security aspects of systems require additional efforts at the very beginning of software development. The topological functioning model is a formal mathematical model that can be used as a reference model for functional and non-functional requirements of the system. It can also serve as a reference model for security requirements. The purpose of this study is to determine the approach to how security requirements can be specified and traced using the topological functioning model. This article demonstrates the suggested approach and explains its potential benefits and limitations.

Extracting TFM Core Elements From Use Case Scenarios by Processing Structure and Text in Natural Language

Abstract Extracting core elements of Topological Functioning Model (TFM) from use case scenarios requires processing of both structure and natural language constructs in use case step descriptions. The processing steps are discussed in the present paper. Analysis of natural language constructs is based on outcomes provided by Stanford CoreNLP. Stanford CoreNLP is the Natural Language Processing pipeline that allows analysing text at paragraph, sentence and word levels. The proposed technique allows extracting actions, objects, results, preconditions, post-conditions and executors of the functional features, as well as cause-effect relations between them. However, accuracy of it is dependent on the used language constructs and accuracy of specification of event flows. The analysis of the results allows concluding that even use case specifications require the use of rigor, or even uniform, structure of paths and sentences as well as awareness of the possible parsing errors.

The Knowledge Frame System based on Principles of Topological Functioning Model

Abstract Understanding of domain phenomena and their interrelations is necessary for successful software development. The knowledge frame system based on principles of Topological Functioning Modelling (TFM) can be used for this purpose at the Computation Independent level within Model Driven Development. Research on knowledge formats showed that inferring in the closed world paradigm and similarity to the object-oriented paradigm made frames an attractive candidate to the knowledge representation format. Frames can hold information necessary for generation of the TFM. The knowledge system based on the principles of the TFM does not allow inferring ambiguous facts and leads to the more complete discovery of knowledge.

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

Abstract The approach called “Topological Functioning Model for Software Engineering” (TFM4SE) applies the Topological Functioning Model (TFM) for modelling the business system in the context of Model Driven Architecture. TFM is a mathematically formal computation independent model (CIM). TFM4SE is compared to an approach that uses BPMN as a CIM. The comparison focuses on CIM modelling and on transformation to UML Sequence diagram on the platform independent (PIM) level. The results show the advantages and drawbacks the formalism of TFM brings into the development.

Obtaining and Visualization of the Topological Functioning Model from the UML Model

Abstract A domain model can provide compact information about its corresponding software system for business people. If the software system exists without its domain model and documentation it is time-consuming to understand its behavior and structure only from the code. Reverse Engineering (RE) tools can be used for obtaining behavior and structure of the software system from source code. After that the domain model can be created. A short overview and an example of obtaining the domain model, Topological Functioning Model (TFM), from source code are provided in the paper. Positive and negative effects of the process of TFM backward derivation are also discussed.

The Model Transformation for Getting a UML Class Diagram from a Topological Functioning Model

Abstract The approach called Topological Functioning Modeling for Model Driven Architecture (TFM4MDA) uses a Topological Functioning Model (TFM) as a formal Computation Independent Model (CIM) within the Model Driven Architecture (MDA). The object of this research is the construction of a UML class diagram on the Platform Independent Model (PIM) level in conformity with the TFM. Nowadays this transformation is executed manually. Manual creation of models is time-consuming and there is a risk of making mistakes. These drawbacks increase expenses and reduce efficiency of TFM4MDA approach. That is why automation of transformation is useful. The paper presents an algorithm for the transformation which is written in a pseudocode and can be implemented as a tool.

The Perspective on Data and Control Flow Analysis in Topological Functioning Models by Petri Nets

Abstract The perspective on integration of two mathematical formalisms, i.e., Colored Petri Nets (CPNs) and Topological Functioning Model (TFM), is discussed in the paper. The roots of CPNs are in modeling system functionality. The TFM joins principles of system theory and algebraic topology, and formally bridges the solution domain with the problem domain. It is a base for further automated construction of software design models. The paper discusses a perspective on check of control and data flows in the TFM by CPNs formalism. The research result is definition of mappings from TFMs to CPNs.

Relationships between UML Sequence Diagrams and the Topological Functioning Model for Backward Transformation

Abstract The software system needs to be analyzed and designed before the program code is written. A Computation Independent Model (CIM) and a Platform Independent Model/ Platform Specific Model (PIM/PSM) from Model-Driven Architecture (MDA) will be partially considered in this paper. A Topological Functioning Model (TFM) will be considered as a formal CIM, and UML sequence diagrams - as a behavioral PIM/PSM of the software system. The paper presents a short overview of the TFM and sequence diagrams with their constructs, as well as the example of transformation from the sequence diagrams to the TFM.

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.

Ensuring Domain Conformity by Means of the Topological Functioning Model

Abstract The paper focuses on an open question about ensuring conformity among a domain of system knowledge, an analysis domain, a software design domain, and code. Principles of Model Driven Engineering are used in the research, namely, formal specifications of domains and support of conformity among these specifications with the help of traceability mechanism. Topological Functioning Model (TFM) has a mathematical mechanism for supporting traceability, and, thus, conformity. The main results demonstrate that the TFM holds the central place in a chain of trace links between specifications, and analysis of these links enables verification of domain conformity. The results are theoretical and require additional practical experiments.

Notion of causal relations of the topological functioning model

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.

Automated Derivation of Use Case Model from Topological Functioning Model

Automated Derivation of Use Case Model from Topological Functioning ModelThe first important step in Model Driven Architecture software development is qualitative analysis and specification of structure and behavior of business and its supporting information system as well as software requirements. We continue the research on achieving a qualitative software requirements model, Use Case Model (UCM), based on a formal business model, Topological Functioning Model (TFM), by using formal model transformations. This paper discusses the results of implementation of the transformation from TFM to UCM by using Query/View/Transformation Relations supported by mediniQvt.

Implementing a Topological Functioning Model Tool

This paper recognizes the computation independent nature of a Topological Functioning Model (TFM) and suggests it to be used as the Computation Independent Model (CIM) within Model Driven Architecture (MDA). To step towards the completeness of MDA and enable the automation of system analysis the Topological Functioning Model for Model Driven Architecture (TFM4MDA) method is considered. A project of implementing TFM4MDA as a TFM Tool is suggested to enable artificial intelligence in system analysis and software development. By applying language processing methods in combination with textual use case analysis and using Topological Functioning Model (TFM) as CIM a workable solution can be developed. The main components of the tool are a TFM Fetcher for system’s informal description analysis, TFM Editor and TFM Transformer for TFM to UML transformation. Solution’s compatibility to MDA standards is also considered, thus providing a formal method to automatically acquire a CIM from description of a business system in form of textual use cases, and that could be applied to implement a system analysis tool for this task. This paper discusses the implementation challenges and considers implementing the tool by using the leverage of the Eclipse platform and its MDA conformable frameworks.

Reconciling software requirements and architectures within MDA

Reconciling software requirements and architectures within MDAIn the software development world little guidance and few methods are available for reconciling software requirements and architecture which satisfies those requirements. In fact none of these methods use formal basis for the reconciling process. The main goal of this paper is to define an approach by which it is possible to reconcile software requirements and architectures within model driven architecture. Model driven architecture considers system from three viewpoints. Each viewpoint has its own model by which the viewpoint is modelled. It is possible to use topological functioning model of system to reconcile software requirements and architectures and to make formal transformation from computation independent model into platform independent model. The use of topological functioning model provides possibility for traceability between software artefacts, e.g. between requirements and architecture elements. By using case study we have proven that it is possible to reconcile requirements and architectures by using topological functioning model. The software architecture in this case is modelled by using topological class diagrams. At the end of the case study we have shown how we can introduce more formalism into UML diagrams by transforming topology from topological functioning model to class diagrams.

Use of Business Models within Model Driven Architecture

Use of Business Models within Model Driven Architecture Model Driven Architecture is a framework dedicated for development of large and complex computer systems. It states and implements the principle of architectural separation of concerns. This means that a system can be modeled from three different but related to each other viewpoints. The viewpoint discussed in this paper is a Computation Independent one. MDA specification states that a model that shows a system from this viewpoint is a business model. Taking into account transformations foreseen by MDA, it should be useful for automation of software development processes. This paper discusses an essence of the Computation Independent Model (CIM) and the place of business models in the computation independent modeling. This paper considers four types of business models, namely, SBVR, BPMN, use cases and Topological Functioning Model (TFM). Business persons use SBVR to define business vocabularies and business rules of the existing and planned domains, BPMN to define business processes of both existing and planned domains, and use cases to define business requirements to the planned domain. The TFM is used to define functionality of both existing and planned domains. This paper discusses their capabilities to be used as complete CIMs with formally defined conformity between planned and existing domains.