Zubair
Member
Since working with NICE RTI, I have a set of rules which I used, to make a robotic solution which would be structured and also easy to understand if another individual looked at it.
Firstly I would split everything up into different files for example.
All business entities in 1 file, screen elements in 1 files, Logic in 1 files, and functions which are used in multiple logics I made a separate file called general logic, and I also have a main file where the robotic solution would mainly call from.
So an example of my structure would be something like this
-MAIN
-GENERALLOGIC
-BL_COMMON
-BE_COMMON
-SE_COMMON
The files would be referenced also in the order I have put them, as each layer would call from the layer below. I use naming conventions on the files e.g BL,BE, SE etc to make the files easier to read and so people can tell what sort of stuff would be in there.
If anyone wants to know more, feel free to ask
Firstly I would split everything up into different files for example.
All business entities in 1 file, screen elements in 1 files, Logic in 1 files, and functions which are used in multiple logics I made a separate file called general logic, and I also have a main file where the robotic solution would mainly call from.
So an example of my structure would be something like this
-MAIN
-GENERALLOGIC
-BL_COMMON
-BE_COMMON
-SE_COMMON
The files would be referenced also in the order I have put them, as each layer would call from the layer below. I use naming conventions on the files e.g BL,BE, SE etc to make the files easier to read and so people can tell what sort of stuff would be in there.
If anyone wants to know more, feel free to ask