View source for Computation-Independent Model (CIM)

A '''Computation-Independent Model (CIM)''' is a high-level representation of a system's business requirements, goals, and rules without specifying any details about the system's technical implementation. It is part of the Model-Driven Architecture (MDA) approach defined by the Object Management Group (OMG), which is a software design methodology that separates the specification of system functionality from its implementation on a specific platform.

The MDA approach includes three primary models:
*Computation-Independent Model (CIM): This model represents the system's business context, capturing its requirements, constraints, and high-level processes without any technical details. The focus is on understanding the problem domain, stakeholders' needs, and business rules.
*Platform-Independent Model (PIM): This model captures the system's functional behavior, structure, and interactions without specifying any platform-specific details. The PIM represents a more detailed and technical view of the system but remains independent of any specific implementation technology.
*Platform-Specific Model (PSM): This model maps the platform-independent model to a specific technology platform, such as a programming language, middleware, or hardware architecture. The PSM includes all the details necessary for implementing the system on the chosen platform.

The primary purpose of a Computation-Independent Model (CIM) is to provide a clear understanding of the business context and requirements that drive the system's development. It allows stakeholders to focus on the problem domain and reach a consensus on the system's goals and rules before diving into technical details and implementation concerns.

Key benefits of using a Computation-Independent Model (CIM) include:
*Improved communication: CIMs facilitate communication between stakeholders, such as business analysts, domain experts, and developers, by providing a common language and understanding of the problem domain.
*Early validation of requirements: Creating a CIM enables stakeholders to validate and refine requirements early in the development process, reducing the risk of misunderstandings and costly changes later on.
*Easier maintenance and evolution: By separating business requirements from technical implementation, CIMs make it easier to adapt and maintain the system as business needs evolve or new technologies become available.
*Enhanced reusability: CIMs can serve as reusable assets for similar projects or systems, allowing organizations to leverage their domain knowledge and expertise across multiple projects.

In summary, a Computation-Independent Model (CIM) is a high-level representation of a system's business requirements and context, focusing on the problem domain without specifying any technical implementation details. It is a crucial part of the Model-Driven Architecture approach, promoting improved communication, early validation of requirements, easier maintenance, and enhanced reusability in software development projects.


== See Also ==
*[[Model Driven Architecture (MDA)]] - The broader framework within which Computation-Independent Model is a layer, focusing on system specification from computation-independent, platform-independent, and platform-specific models.
*[[Platform Independent Model (PIM)]] - Another layer within the MDA framework that describes the system's operation but omits the technical details, making it a close relative to CIM.
*[[Platform Specific Model (PSM)]] - Yet another layer within the MDA that describes how the system uses a specific computing platform, offering a more detailed perspective than CIM.
*[[Unified Modeling Language (UML)]] - A standard language often used to create CIMs as well as other types of system models.
*[[Systems Modeling Language (SysML)]] - Another language for creating models of systems, which might be used to develop CIMs, especially for systems engineering applications.
*[[Business Process Modeling]] - A methodology for representing the steps required to achieve a business objective, sometimes used in conjunction with or as a part of CIMs.
*[[Enterprise Architecture]] - The broader framework that defines the structure and operation of an organization, potentially using CIMs for certain types of analysis.
*[[Agile Methodology]] - A project management and software development methodology that might use lighter versions of models like CIM for requirements gathering and analysis.