You have an I.T. department. They have programmers. They develop software. Your company has policies regarding how software is to be coded. These are your published programming standards. But how do you know whether or not your software developers are following those standards?
Now you can. The compliance monitoring capability of our model-driven tools can be utilized towards monitoring software coding standards
Another scenario:
You have engaged an outside software house to develop software for you. There is a detailed Service Level Agreement recognizing what the software quality standard should be. The company is delivering software in a timely manner, and the application seems to be running well. But do you know what kind of code you are getting from them?
How we enforce standards
The following schematic illustrates our model-driven approach:
Consortium of I.T. Software Quality (CISQ)
Our interest in software quality goes far beyond just programming standards. As a member of OMG (Object Management Group), we are member of the Consortium of IT Software Quality (CISQ) that is co-sponsored by the Software Engineering Institute (SEI) at Carnegie Mellon University and the Object Management Group (OMG) to combine their industry-leading strengths in developing software-related standards and appraiser licensing programs. The standards process is co-managed by the two organizations, bringing together IT leaders worldwide, and headed by Dr. Bill Curtis, co-author of the Capability Maturity Model (CMM) standard.
“For several years IT executives have complained that there are no industry standards for measuring the quality of business application software,” said Dr. Richard Soley, CEO of OMG, in a statement to eWeek. “CISQ will enable us to benchmark the effectiveness of internal development, evaluate the quality of applications acquired from external sources, and predict the quality and cost of IT services to the business."
