Application Modeling

Application Modeling is the activity of concretizing Use Cases as application behavior and constructing an Application Model. It clarifies the mappings from Use Case Scenarios to participants, Roles, responsibilities, Collaborations, Interactions, state transitions, Events, Services, and Operations.

SimpleModeling constructs a Use Case Realization Model from a Use Case Scenario in the Literate Model. A Collaboration describes the structure of participants, Roles, and responsibilities, while an Interaction provides a concrete execution example. AI proposes mappings to Services, Operations, Events, StateMachines, and related elements; people approve their meaning and correspondence. CBD Support assists with evidence, differences, Traceability, and conformance to execution examples.

Domain Modeling emphasizes the static aspects of problem-domain meaning, structure, rules, and boundaries, while Application Modeling emphasizes the dynamic aspects of Use Case realization. They are not exclusive static and dynamic Models; they organize the same SimpleModeling Model according to different Purposes and Concerns.

Application Modeling is not Model Realization. Application Modeling constructs semantic executable structures from Use Cases; Model Realization connects the approved Executable Model to programs and an execution foundation through CML, Cozy, generative AI, and Textus.