Development Lifecycle for SQL Server Modeling CTP Applications
[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 various steps in the design, development, and management of a model-driven .NET Framework application. Although the developmental steps are numbered as though one person will start with the first and end with the last step, this process can involve multiple people, and iterative development may cause certain stages to be repeated in a particular order any number of times.
Lifecycle for Model-driven Applications
The following stages are typically involved.
.NET Language Development. Build a new language by using the “M” language and tools.
Designing Models and Domains using "M". Design models in “M”, including how to use the system-provided domains in SQL Server Modeling Services.
Loading Domain Models with Data. Use “M” and other data access technologies to insert data values into your models.
Versioning Data with Modeling Services Folders. Handle changes to data values within a model once the model is deployed to Modeling Services.
Managing Data in SQL Server Modeling Services. Use schemas to manage models, folders to manage values, and SQL Server 2008 administration practices.