No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
==== Types of Models ==== | ==== Types of Models ==== | ||
'''Behavioral Models''': Illustrate how components interact and respond to events. Partially represented in MDriven with [[Training:UML – State machines|UML – State machines]] | * '''Architectural Models''': Describe the high-level structure and components of a system. | ||
* '''Behavioral Models''': Illustrate how components interact and respond to events. Partially represented in MDriven with [[Training:UML – State machines|UML – State machines]] | |||
'''Data Models''': Represent data structures, relationships, and constraints. In MDriven, these are represented by the [[Documentation:Class diagrams|Class Diagram]]. | * '''Data Models''': Represent data structures, relationships, and constraints. In MDriven, these are represented by the [[Documentation:Class diagrams|Class Diagram]]. | ||
* '''Process Models''': Depict workflows, business processes, or system behaviour over time. | |||
'''Process Models''': Depict workflows, business processes, or system behaviour over time. | |||
==== Model Driven Architecture and Model-Driven Development ==== | ==== Model Driven Architecture and Model-Driven Development ==== | ||
| Line 28: | Line 26: | ||
==== Examples of Models in MDriven ==== | ==== Examples of Models in MDriven ==== | ||
'''State diagrams''' for modeling system behaviour. | * '''UML (Unified Modeling Language)''' diagrams (e.g., class diagrams, sequence diagrams). | ||
* '''State diagrams''' for modeling system behaviour. | |||
See also: | |||
Revision as of 05:00, 21 May 2024
Definition of a Model
A model refers to an abstract representation of a system, process, or concept. It is a simplified and structured representation of a real-world entity, system, or phenomenon.
Models capture essential aspects, relationships, and behaviour without unnecessary details.
Models serve as a means of communication and understanding among stakeholders (developers, architects, users, etc.).
Purpose of Models
Abstraction: Models abstract complex systems into manageable components.
Analysis: They allow analysis, validation, and verification before actual implementation.
Documentation: Models document design decisions, requirements, and system behaviour.
Visualization: They provide visual representations for better comprehension.
Types of Models
- Architectural Models: Describe the high-level structure and components of a system.
- Behavioral Models: Illustrate how components interact and respond to events. Partially represented in MDriven with UML – State machines
- Data Models: Represent data structures, relationships, and constraints. In MDriven, these are represented by the Class Diagram.
- Process Models: Depict workflows, business processes, or system behaviour over time.
Model Driven Architecture and Model-Driven Development
Read more here about different software development strategies using models: BestPractices:Model Driven
Examples of Models in MDriven
- UML (Unified Modeling Language) diagrams (e.g., class diagrams, sequence diagrams).
- State diagrams for modeling system behaviour.
See also: