Abstract
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.
Highlights
The common case in software development projects is a refinement of software specifications after the end product is ready to be delivered
Conformity of specifications is meant as a description showing which constructs of the system specification have corresponding constructs in the software specification and code, which constructs are optional, and which constraints are kept within the specifications
The main challenge is formalism of computation independent models (CIMs), because these models deal with informal knowledge sources and are semiformal at most
Summary
The common case in software development projects is a refinement of software specifications after the end product is ready to be delivered. In order to solve this challenge, Model-Driven Engineering (MDE) suggests using specifications as a source and a base for production of code. This means that transformations of composed specifications into code should be automated. Besides the transformation and composition of the CIM specifications, traceability of requirements and their sources from code to specifications and vice versa is an open question. This paper discusses application of a Topological Functioning Model (TFM) as a formal CIM of both systems “as-is” (problem) and “to-be” (solution) and tracing of conformity from this CIM to platform independent model to platform specific model to code (Section III). Conclusions discuss the obtained results and directions of future research
Sign-in/Register to view highlights & summary 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 callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
