403
edits
Protocol: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 48: | Line 48: | ||
And now, enjoy our protocol. | And now, enjoy our protocol. | ||
== Basics == | |||
Software permeates all areas of our lives. A map app on the smartphone is easier to use than carrying a paper map around. Sending a text message is faster than writing a letter. Software can greatly enhance an existing process - as in these two cases, navigation and communication. The framework we describe in language, and the resulting movement in you and in groups, can be described as a process that enables change. As software, this process will be capable of facilitating change much more effectively in the future. Every software can be considered as a building and thus also has an architecture. This architecture follows - as with any structure - certain design principles. We will focus our attention in this chapter, which is dedicated to our protocol, primarily on these principles. From these principles, it will become apparent how our structure will look in the future. | |||