Rules and freedoms: why CORBA and Java technologies are selected

Welcome to this regular section on Java and CORBA technology. This first phase will provide an overview of Java and CORBA technologies and help you decide how best to make them work for you. Future columns will provide hands-on guidance and code for Java and CORBA programming.

In 1855, Joshua Chamberlain, a 26-year-old professor of rhetoric at the University of Bowdoin, spoke in a speech about the relationship between rules and freedoms and the dangers of imbalances. The rule of no freedom is despotism, and freedom without rules is chaos.

The management of the company's information systems department may result in excessive regulation or excessive freedom. An example of an excessive rule is that it applies only to the management directives of one vendor, so that your system is expanding or is having problems integrating with potential corporate partners. If you have too much freedom, individuals or development groups will choose technology based on them, so it can be difficult to expand or integrate if these tech gurus encounter topics such as their "unfamiliar" preference for equity. Developers may be affected by the changing business environment.

Strive to achieve environmental balance

A variety of environmental factors determine the rules that our systems must follow. Systems that exist in a business environment should be long-lived enough to create value for companies and customers. Systems that continue to create long-term value for an organization must be able to cope with frequent changes. Mergers, acquisitions, new management and market forces are changing the system's environment, as well as the needs of users who complete business processes using the system. Change is a constant and must be added to the evaluation equation. Of course, we can't predict the future, but we can analyze trends and try to design our systems so that they can accept a lot of potential change or system expansion, while minimizing the impact on the organization.

To make the right decisions and evaluations, we need to understand the rules that govern the environment and the freedom that our applications should have in that environment. The most important rule to understand is that our systems are in an evolving organization, both in companies, in government and in educational organizations, which dominate technical issues in business matters. Many architectural and platform evaluations have missed out on the main problem. They typically put two or more technologies together and then compare the technical features list. At the time of completion, most participants would agree, because they were unwilling to quarrel with the group's loudest, toughest and most powerful factions. Obviously, this is not the most effective way to make a choice.

Identify key business issues

Translating business issues into actual assessments of organizational needs means that you should focus on the following issues:

Technical force within the organization

Does not inhibit the programmer's development environment

runtime environments that do not limit applications

Licensing and legal issues for the runtime Environment and development environment (can be said to be rules of the rules)

Can find experienced developers

To find a reasonably charged, knowledgeable consulting firm.

Impact on the customer of the Organization

Impact on vendors or technical partners

The culture and strategy of the Organization

Organization's Superior Management Alliance

Are the tycoons talking about mergers or acquisitions?

Who's the decision-maker?

These business problems are often more important than other issues, such as the concurrent model of one thread per session or the concurrency model of each requesting one thread. You can walk into your boss's office and give him a technical view that can fill a software workshop, but unless you emphasize the needs of your organization, your point of view will be very hollow.