Share via

Modeling Process

  • Article

[This content is no longer valid. For the latest information on "M", "Quadrant", SQL Server Modeling Services, and the Repository, see the Model Citizen blog.]

This topic describes the modeling process itself: Designing models and applications in parallel, updating your models in SQL Server and in the Modeling Services database, and versioning existing models. This topic does not discuss the coding patterns and shared Modeling Services shared domains. For more information about “M” and Modeling Services patterns, see Applying Common Modeling Patterns.

Overview

This topics in this section describe the fundamentals of model-driven application design and development. This section is designed to cover all the possible steps in the model-driven application development process, but which topics are of interest depends on your particular needs.

  • Designing Models and Applications in Parallel. When you create a new application, it is often best to design the application and its models in parallel. As the application adds new features and requirements, you can adjust the models to support those changes. The SQL Server Modeling CTP provides a language, Microsoft code name “M”, and tools that support this process.

  • Updating Models in the Database (SQL Server Modeling CTP). When you develop a data-driven application, you might need to iterate the data model and the code that uses the data model. In order to test the data model, the current version of the schema must be loaded into the database. As the application evolves, the data model evolves to support new features and fixes.

  • Versioning Existing Model Schemas. As you develop an application, your models change to support new features and functionality. This type of versioning is schema versioning. This topic examines the challenges and potential solutions for updating models to a newer schema version.

See Also

Concepts

Designing Models and Applications in Parallel
Applying Common Modeling Patterns