Flag Counter

The concept

        We are dedicated redefine software development, introducing the framework (software development “methodology”) for software development, based on adaptive ontology, eliminating a Coding.
       This framework is called Calculus for Programming and based on implementation of the new (and only one of this kind in the industry) method of imperative programming for visual paradigm – Executable Pictograms.
        This framework intended to be delivered as a standard feature (in the form of Computing platform), enhancing group productivity tools by utilizing functionality of the specification-designing, presentation, design development and implementation in the ontology based, holistic way as an interactive WYSIWYG blueprint. This blueprint is delivered in the form of 3D interactive graphics with hypertext (plain 2D presentation of the document is optional). 
        The implementation of the adaptive ontology used, is called Calculus χπ.
        • Having a wrong tool and using it in the wrong way, it's hard to fix it. Instead, we prefer to have a visual language for calculus and visual calculus for programming. It’s how we rediscover a Programming, leaving the Coding in the past.
     Here we are talking about the software development. As of today, there is no any other theory or methodology supporting the use of ontology in the process of software development, eliminating Coding. Presentation of the process of development is supported by 3D graphics and a hypertext according to the methodology. We have a bunch of applications for modeling, e.g. UML. They cover needs for ontology, with the set of Frames, to collect data about the problem, to create a program, which is coded or/and synthesized in this case. All of them imply the use of coding, i.e. a calculus for coding is used. There is no specification, design and development of the frames (in the case of UML, we are not designing nor developing the frames by itself, we are just using them), which imply the use of the process of ontology designing, development and her adaptation, which we call Calculus for Programming. Contrary, the calculus for programming is employed in our methodology of the software development. Somebody can say, “Growing use of ontology”, in reality it means the growing use of only a word “ontology”. And nobody knows (but us) how “to eat it” (to integrate with it) and what the difference among the Programming and Coding is. Calculus for programming, defining a programming, which is derived and accumulated from a process of designing and developing of the ontology for specification of many problems and algorithms of calculations to solve them. And Calculus for Coding is derived from coding by itself, adding different layers of abstraction, thus creating different “programming” (i.e., in reality, coding) languages. Each time, when we are reasoning over code, we derive each time, the calculus for programming, to construct mentally a specification, of what it is created, to reason about it, thus reasoning about it become extremely obscured. And this is fundamentally wrong. Programming means we construct, present, design and develop a specification of a problem, embracing Calculus for Programming, based on adaptable ontology. We are constructing, presenting, designing and developing an interactive WYSIWYG 3D blueprint for every problem, which we solve on the computer in the environment of the group of developers and domain experts. And this is our Code (knowledge Code – enriched in this way by natural language), which could very conveniently serve as input for AI, to process the knowledge or to be applied to bring in a knowledge about computing to the Quantum Computer, or just serve as an interactive 3D blueprint, in the case we want to comprehend and contemplate the whole picture.
        Our concept is confirmed as a foundation for the billions of a billion-dollar computer and Internet of Things industry.