CRC Modeling Team

In the early days of software development, a programming team would ask the client to write a specification describing exactly what they wanted the program to do. Once they had completed the specification, the client’s part of the job was over. The programmers would go back to their office and write the program based on the specification. After some period of time (usually lengthy) they would deliver the final result to the client. This might seem like a reasonable approach, but the results were often disappointing for the client. Later, the Object-Oriented Programming, which makes a close association with the client much easier because objects in the program correspond so closely with objects in the real world. First the client defines the objects that are important in the real world situation, which as we noted is called the problem domain or business domain then the programmer translates these objects into objects in the program. The approach we’ll describe for an initial approach to finding user requirements is called CRC where CRC stands for Class-Requirements-Collaborators.