Writing up the specifications for the different modules
Now that we are equipped with the four-layer map of the information system that we want to build and the norms and standards to kickstart entities’ technical implementation, we only need to close this chapter with a more detailed design of each of the modules that are going to be built and assembled.
Overall system specifications
Before we dive into the specifications for the different modules that the information system will be made with, a few considerations apply to the overall system. For example, all modules with web exposition will be in the demoeditor.org
domain. Most of the time, you will notice that I only talk about relative URLs starting with /api
; this is done on purpose, as we are going to do as much as we can to delay the application of absolute URLs, in order to reduce the coupling with the domain exposition as much as possible. When calling URLs from services, we will use relative URLs as well.