Standards

Standards

Tambotka Howard

CSS/422

July 13, 2012

Keith Ellis

Standards

Team C Inc., is back again this time to talk about standards in software integration. One would use the software to integrate different information into one easy to find place making the information easy to access as well as use. One example of integration software would be two companies merging and wanting all the information combined. In order to do this, there must be rules to follow to make sure everything runs smoothly. Ground rules that we will discuss are establishing ownership, define the environment and defining the level of detail. Once we establish these ground rules and merge companies with let us say team B, everybody will be happy.

We must establish name for important data and functions. When our teams merge, we do not want to confuse one another by using names we already have. We have to come together and make a standard name for our important data and everyday functions. If the names make sense, we will use them and if not, then we need to sit down in the boardroom and figure this out. As long as we choose the standard name that best fit our business terminology, it should be a fast meeting. The spokesperson and the person merging the software should be the people taking ownership of this standard.

Standards to your different environments are must when you merge companies together. An execution environment is a routine that accepts commands as inputs and cause them to be executed. The development environment is where you can code the software and test it. This comes with hardware as well as software so we can code it in this environment. Operations environment is where we make the software easy to operate amongst all of the security in this environment. The development environment should be implemented last so we can take advantage of standards set for both operations and execution environments.

The level of detail standard is important because we all must agree on...