Managed Business Consulting, Inc. consultants are well versed in Object Oriented consulting on real world projects. With years of experience in the leading methodologies including OMT, Booch, Jacobson, and UML, we can help you with your projects by using a proven approach. Our consultants have successfully used Object Oriented Analysis and Design (OOAD) on projects from the early requirements gathering phase all the way through System production and deployment.

The real advantage of using an Object Oriented approach is simple. All of the elements of the application become real world Objects that can be described with respect to their state. They also have actions that are performed on them that become the procedures and functions (or Methods) for the Object. When Objects collaborate with one another, these Methods are called to perform the desired action. If there is an action that needs to be performed that has no corresponding Method, then a new Method may need to be added. Through this simplified approach, the development and refinement of the system can be accomplished in a relatively short time, leaving more time for integration and testing.

Some of the most useful artifacts and benefits from a good Object Oriented Analysis and Design include:

Use Case Diagram

The Use Case diagrams of the system define the system boundaries by defining what external Systems (or users) interact with the System . These diagrams also define the expected inputs and outputs from the System so that everyone can agree on what interfaces to the system are necessary as well as what responses are expected from the System for any identified stimulus. As simple as this appears, it is typically one of the most challenging aspects to any project and a primary reason for project failures and budget overruns.

Scenario Diagram

The Scenario diagrams further refine the Use Cases by detailing the processes down to the Object level. This helps to decompose very complex processes into manageable steps that become the Method calls between Objects. It also leads to definition of variable types for each Object and can uncover missing requirements or incorrect assumptions. The Scenario diagrams become the basis for Object and System testing later since they in effect, implement the Use Cases identified for the system. With a complete set of Scenario Diagrams, the process moves forward to Class diagrams.

Class Diagram

The Class diagrams are a more abstract view of the Objects that were defined in the Scenario diagrams. By using abstraction, the number of Classes defined may be substantially less than the actual Objects by finding functional commonality and similar Attributes that can be leveraged in the System design. When the System is implemented, the Objects simply use the defined Classes and add any particular Methods or Attributes they require. This helps to reduce the overall System maintenance by capturing the basic structure for multiple Objects into a single Class that can be more easily modified.

Reduced Time-To-Market

A tightly integrated design tool that supports the necessary diagrams described in the previous sections is an essential element in the process of developing a good Object Oriented design. Through the use of such tools, our consultants not only capture the design elements, but also capture the documentation for each element, from the diagrams down to the individual attributes for each design element.

News Updates

Database Solutions

Customer Information Management System

Managed Business Consulting, Inc. has started working with Office Paper Systems, Inc. to design and build a new Microsoft based customer information management system that will provide more accurate the information for day-to-day operations as well as provide better tracking and reporting on operations. This new system will allow Office Paper Systems, Inc. to manage the increase in business and the need to provide real-time data that is critical to making business decisions.

Read more in the News section.