The Topological Functioning Model as a Reference Model for Software Functional and Non-functional Requirements

Nazaruka, Ērika; Osis, Jānis

doi:10.5220/0006811204670477

Cited by 4 publications

(7 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The goal of this research is to evaluate the suitability of a Topological Functioning Model (TFM) for referencing security requirements as well as perspectives of this model to be used as an aid for the analysis of potential security threats. This article continues the research started earlier [2], [3] and focuses on referencing security requirements. Previous articles ( [2] and [3]) focused on demonstrating the capabilities of the TFM as a central reference model for modelbased software development.…”

Section: Introductionmentioning

confidence: 85%

“…This article continues the research started earlier [2], [3] and focuses on referencing security requirements. Previous articles ( [2] and [3]) focused on demonstrating the capabilities of the TFM as a central reference model for modelbased software development. Thanks to the formal mathematical background of the TFM and mappings between the TFM and functional requirements and the TFM and elements of a logical design model, it was possible to extrapolate the same reference principles to the non-functional requirements, such as performance requirements.…”

Section: Introductionmentioning

confidence: 85%

“…Functional requirements within the TFM. Mappings from functional requirements (FRs) onto the TFM functional features can be one-to-zero, one-to-one, one-to-many, many-to-many, many-to-one, and zero-to-one [2], [3], [31]- [33]:…”

Section: A Formal Reference Modelmentioning

confidence: 99%

“…Then a mapping from a set of functional requirements to a set of functional features can be specified as a tuple (3), where properties of this mapping can also be indicated as Boolean variables isComplete for indicating completeness and isOverlapping for indicating overlaps [2], [3].…”

Section: A Formal Reference Modelmentioning

confidence: 99%

“…Thanks to the formal mathematical background of the TFM and mappings between the TFM and functional requirements and the TFM and elements of a logical design model, it was possible to extrapolate the same reference principles to the non-functional requirements, such as performance requirements. However, [2] and [3] did not address the main issue of this article about references to security requirements.…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Security Requirements Specification and Tracing within Topological Functioning Model

Nazaruka¹

2022

J. Complex Syst. Inform. Model. Q.

View full text Add to dashboard Cite

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.

show abstract

Section: Introductionmentioning

confidence: 85%

Section: Introductionmentioning

confidence: 85%

Section: A Formal Reference Modelmentioning

confidence: 99%

Section: A Formal Reference Modelmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Security Requirements Specification and Tracing within Topological Functioning Model

Nazaruka¹

2022

J. Complex Syst. Inform. Model. Q.

View full text Add to dashboard Cite

show abstract

The Formal Reference Model for Software Requirements

Nazaruka

Osis

2019

Communications in Computer and Information Science

View full text Add to dashboard Cite

Theory Driven Modeling as the Core of Software Development

Osis

Nazaruka

2021

Research Anthology on Recent Trends, Tools, and Implications of Computer Programming

View full text Add to dashboard Cite

Some experts opine that software is built in a primitive way. The role of modeling as a treatment for the weakness of software engineering became more important when the principles of Model Driven Architecture (MDA) appeared. Its main advantage is architectural separation of concerns. It showed the necessity of modeling and opened the way for software development to become an engineering discipline. However, this principle does not demonstrate its whole potential power in practice because of lack of mathematical accuracy in the very initial steps of software development. The sufficiency of modeling in software development is still disputable. The authors believe that software development in general (and modeling in particular) based on mathematical formalism in all of its stages and together with the implemented principle of architectural separation of concerns can become an important part of software engineering in its real sense. They propose the formalism by topological modeling of system functioning as the first step towards engineering.

show abstract

The Topological Functioning Model as a Reference Model for Software Functional and Non-functional Requirements

Cited by 4 publications

References 0 publications

Security Requirements Specification and Tracing within Topological Functioning Model

Security Requirements Specification and Tracing within Topological Functioning Model

The Formal Reference Model for Software Requirements

Theory Driven Modeling as the Core of Software Development

Contact Info

Product

Resources

About