@inproceedings{BenekenMarschallRausch2005, author = {Beneken, Gerd and Marschall, F. and Rausch, A.}, title = {A Model Framework Weaving Approach, In: Proceedings of the First Workshop on Models and Aspects - Handling Crosscutting Concerns in MDSD at the 19th European Conference on Object-Oriented Programming (ECOOP 2005)}, series = {19th European Conference on Object-Oriented Programming (ECOOP 2005)}, booktitle = {19th European Conference on Object-Oriented Programming (ECOOP 2005)}, year = {2005}, abstract = {Nowadays, in software development usually various models and description fragments are created. Some of these artifacts describe the core of the application, such as the data model or the user interaction model. Other artifacts describe cross-cutting concerns, such as security or the requirement: "every change of data has to be confirmed by the user, before it is written into the database". During the development process these artifacts are combined, transformed, and finally implemented manually or even automatically. For instance a designer may combine a model of a dialog component specifying an action, that changes data, with a common description of a generic confirm dialog. The integrated dialog description may be afterwards implemented by a programmer. The manual combination of both artifacts and the transformation of the combined description into code are errorprone and hard to change. Industry basically tests or actually uses two approaches for the combination today: 1. At the level of code and execution Aspect-Oriented Programming (AOP) is used [KLM+97]. An aspect defines a cross-cutting concern and the weaving instructions. A code weaver provides the actual weaving at compile or runtime. 2. At the level of design models and analysis models Model-Driven Software Development (MDSD) is used [KWB03]. A model in MDSD is a first class development artifact. Thus models are significantly more abstract than the implementation of code. However, these models cannot be executed. Hence, a abstract model is transformed into another, typically more detailed. A series of such transformations results in executable code. Thereby, a model transformer or a code generator reads some of the artifacts. The other artifacts and the combination rules are implemented in transformation rules or code generation templates (or somewhere else in the transformation / generation approach).}, language = {en} } @book{Petkovic2005, author = {Petkovic, Dusan}, title = {3. Auflage - Microsoft SQL Server 2005: A Beginner's Guide}, publisher = {McGraw- Hill Osborne Media}, address = {Columbus, Ohio}, isbn = {0-07-226093-9}, publisher = {Technische Hochschule Rosenheim}, year = {2005}, abstract = {Deploy and manage SQL Server 2005 with easeLearn to use all the powerful features available in SQL Server 2005 from this straightforward, hands-on guide. Set up SQL Server 2005, automate system administration tasks, execute simple and complex database queries, and use the robust analysis, business intelligence, and reporting tools. Troubleshooting, data partitioning, replication, and query optimization are also covered. With SQL Server 2005: A Beginner's Guide, you'll be able to set up a secure, reliable, and productive data management platform in no time. Essential Skills for Database Professionals - Install and customize SQL Server 2005 - Create, alter, and remove database objects with Transact-SQL statements - Use SQL Server as a native XML database system - Tune your database system for optimal performance - Use the new SQL Server Management Studio tool for executing and analyzing ad hoc queries - Retrieve data from more than one source using join operations and SELECT statements - Secure your database using two different authentication modes--Windows and mixed - Restore databases using transaction logs and backup and recovery methods - Streamline system administration tasks using the SQL Server Agent service tool - Analyze and manage information stored in a data warehouse with Microsoft Analysis Services}, language = {en} }