IT Governance Tips...
Documentation
It is not surprising that the majority of code maintained in corporate America is maintained by someone other than the original author. As a baseline a source code's readability should be supported by using meaningful names for variables, methods functions, etc. Proper comments and documentation within the code will directly result in a decreased cost of maintenance in the long run.
Making message schemas deterministic
Allowing unknown or open content within SOA web service messages poses both a security and reliability risk to the system and the infrastructure that provides the service. Service definitions and schemas should always define specifically what is allowed in the content and never allow unspecified content.
Making sure exception blocks are used and exceptions are properly handled
Exception handling is an important part of any Java application. It is not always clear how and what to do when an exception occurs, for example catching the exception may give the impression that it is being handled, however if it is suppressed the exception can lead to undesirable results.
Making sure transaction return codes are verified before continuing
Legacy development platforms like COBOL often use technologies like CICS to manage transactions, whenever these systems return control back to the calling application the return status or codes must be checked immediately to determine the success of the transaction and act appropriately, this will help avoid a potentially catastrophic outcome.
Weekly tips sent right to your inbox! Subscribe below