When making technical designs we usually emphasize the structure of the data to be handled (control block structure), and the segmentation of the programs to be realized.
Depending upon the level of knowledge and experience of those who are eventually to build the program, the level of detail subsequently will be more or less extensive. For the experienced programmer it will suffice to summarize the desired functionality per module and CSECT. For the less experienced ones it may be necessary to explicitly design the structure of each subroutine.
For you Bixoft can make a technical design for any of the following kinds of programs:
The last three categories (callable services, compatibility modules, and transparent conversions) can be implemented as non-reusable, reusable, re-entrant, or even refreshable modules.
You can realise all this and even more with the help of experienced assembler programmers. And without any requirements regarding your current staff of application programmers!
That's why we advocate the prudent application of programs. Keeping always in mind, that whenever the target can be achieved by other means that must always be considered thoughtfully.
Remarks? Questions? More information? Select the topic of your choice or e-mail us with your questions.
|Symposium: extending the life cycle of legacy applications|
|Bixoft Homepage||What's new?|
|Introduction / Sitemap||Why assembler|
|Courses||Sample code snippets|
|Maintenance||Public License Proposal|
|Pre-compilers||Books & sites|
|Profile A.F. Kornelis|
This site is a member of WebRing.
You are invited to browse the list of mainframe-loving sites.
|Dinos are not dead. They are alive and well and living in data centers all around you. They speak in tongues and work strange magics with computers. Beware the dino! And just in case you're waiting for the final demise of these dino's: remember that dinos ruled the world for 155-million years!|
[ Join Now | Ring Hub | Random | | ]