1 / 21

Design Components are Code Components

Knows How To. I Know How To. Thread-Level Code. Design Components are Code Components.

kert
Download Presentation

Design Components are Code Components

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Knows How To I Know How To Thread-Level Code Design Components are Code Components There is no abstraction between Design Components and Code Components. What you design is directly made into code. No matter how complicated the Component, it is isolated and encapsulated at the lowest CPU-thread level. Designers Design Component Programmers Code Component

  2. I Know How To SnEn I Know How To Automatically Instantiates The Snippet Engine automatically instantiates all Nodes when they are needed the first time. The programmer does not have to worry about how or when to get their Node into existence. Nodes may delete themselves when finished. Is Needed For First Time Is Automatically Created Nodes Exist only Logically Node Exists In RAM and On Disk

  3. Knows How To I Know How To Programmers Are Focused Programmers are focused on only generating their Node’s code. They are coding a single CPU-thread, independent and autonomous, to ensure a designed purpose is accomplished. Dependencies on other Nodes which must execute first are automatically handled by the Snippet Engine. Thus, the programmer's attention is directly focused on only the lines of code within their own execution thread. Code Component Design Component

  4. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To Commands In and Out Data and State Interact Interact Interact Interact Interact Interact Relationships Same Interface Access Methods All Nodes use the exact same Command Interface and Data Store access methods. All that the programmer needs to know is the format of the command packets and data records, which are defined during the Design Phase. All Nodes Interact With Each Other The Same Way Opened

  5. CPU CPU Asserted Using Same Mechanism Nodes have no calling sequence like a function. All Nodes are asserted into execution using the exact same mechanism. Asserting a Node to do its job is simple and is always done in the same way. This simplicity dramatically reduces the number of software interfaces that must be defined, programmed, tested, and documented. All Nodes Interact With Each Other The Same Way asynchronous asynchronous GO GO

  6. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To CPU CPU Accomplished Asynchronously Nodes are not called like a section of code, rather they are told to accomplish their task asynchronously. Nodes are asserted because their designed purpose is required, and they may be asserted in any order. Interdependencies between Nodes are automatically handled by the Snippet Engine. asynchronous asynchronous GO GO will wait for all pieces

  7. I Know How To CPU CPU I Know How To Commands In and Out Data and State Relationships Easy To Handle Ramifications Variables are passed between Nodes by either sending commands, or by setting up a designed shared RAM context. Thus the programmer is relieved of having to understand ramification complications when key variables change. All a programmer needs to do is to "post" the changes to the Node which knows how to handle the changes. Since the receiving Node is executed as a separate thread, the programmer can literally "post and forget". asynchronous asynchronous GO GO Change The World Oh No! I changed the world!

  8. I Know How To I Know How To Commands In and Out Commands In and Out Data and State Data and State Relationships Relationships Opened Fetch Data Directly Nodes which need to fetch data from other Nodes may do so directly, without posting commands. Data Stores reside in Shared RAM. Because all Nodes both store and retrieve data in exactly the same way, the programmer uses a standardized code-template to directly fetch data from any other Node. If necessary, a Node's Data Store may be locked and then unlocked by any other Node. This type of coupling is very fast. at nanosecond speeds Opened

  9. Reduced Number of Interfaces All Nodes have only one State-variable, and this variable can have only five different values. This dramatically reduces the number of software interfaces, which dramatically reduces the number of test cases, which dramatically reduces the volume of documentation required in the project's life cycle. The More Interfaces and Choices With Only One Interface and 5 Choices The More Complicated The Software The Simpler The Software The Heavier The Burden and Cost The Lighter The Burden and Cost

  10. I Know How To I Know How To Certified Bug-Free Commands In and Out Data and State Relationships Certified “Bug-Free” Each Node can be independently tested, and most Nodes may even be certified to not have any bugs. The concept of code having hidden bugs is a result of not being able to test all software conditions. However with Snippet Nodes, because they are narrow scopes of autonomous logic with their own data store, it is possible to isolate a Node's execution-context in order to conduct stand-alone-testing which will test all software conditions. Nodes may be certified “bug-free”. Stand-a-lone Testing Of All Software Conditions

  11. Maintenance and Enhancements Nodes are self contained, which helps in maintenance and future enhancements.

  12. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To Ready On The Shelf To Be Reused Immediately Reusable Most Nodes are immediately reusable in future projects. Thus, the cost of future software development projects is dramatically reduced.

  13. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To CPU CPU CPU CPU More CPUs means more GO More CPUs The Faster Will Run Nodes may execute on any available microprocessor. Since each Node is its own thread of execution, the entire application may be massively solved in parallel by executing on computers with large numbers of microprocessors. The more available microprocessors, the faster the program will run. asynchronous asynchronous GO GO will wait for all pieces

  14. I Know How To I Know How To I Know How To I Know How To I Know How To Integration Is “Automatic” A new Node's integration into the application is “automatic”. There is no need for a separate Integration Phase. In order to thoroughly test a Node, the programmer will include all of the other Nodes needed. Programming is best performed starting with the lowest level Nodes, and working upwards. Thus, Nodes are fully integration-tested each time a stand-alone-test is conducted. Programming Is Done From The Bottom - Up

  15. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To Faster With More Programmers Because the project is developed from the bottom-up and each Node is independently stand-alone-tested, the more programmers assigned the faster the project will be finished. This allows the software managers to effectively manage the cost and delivery schedule. Adding More Programmers Actually Helps Programming Is Done From The Bottom - Up

  16. I Know How To I Know How To I Know How To I Know How To I Know How To Even Low-Level Nodes Use GUI Any Node may use the application’s User Interface to interact with the user. Thus even low-level code may have its own debugging, diagnostics, error reporting, and context help GUI.

  17. I Know How To I Know How To I Know How To Any Node Talks To Any Node Any Node may talk to and synchronize with any other Node running anywhere in the world. To the programmer, sending a command or data packet directly to a Node running on another computer is done the same way as sending the packet to a “local Node”. Thus, any execution thread may directly communicate with any other execution thread, even on a completely different computer. Creating applications that share synchronized data and capabilities between networked computers is very easy. Internet Local Nodes Can Send And Receive Commands and Data To Other Nodes Running Anywhere In The World. CPU-Threads on Different Computers Can Directly Synchronize and Augment Their Capabilities. Essential for Games, Robotics, and Mission Control Having a Distributed Database GUI

  18. I Know How To Nodes Are The Database Servers Each client-browser can communicate directly with its own Node, so that, each client-submenu can individually and concurrently work directly with only the small portion of the whole Database it is using. Each client-access-transaction is automatically distributed.

  19. I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To I Know How To Scalability I

  20. I Know How To I Know How To I Know How To I Know How To I Know How To Scalability II

  21. More Servers means more GO I Know How To I Know How To CPU CPU CPU CPU More CPUs means more GO More CPUs means more GO Scalability III Internet

More Related