Difference between revisions of "WG211/M3Consel"
(Created page with "Category:WG211 <HTML> <HEAD> <title>Charles Consel</title> </head> <body bgcolor="white"> Title: A proposal for Domain-Specific Software Engineering <br>Speaker: Charles ...") |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
| − | + | Charles Consel | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Title: | Title: | ||
A proposal for Domain-Specific Software Engineering | A proposal for Domain-Specific Software Engineering | ||
<br>Speaker: Charles Consel | <br>Speaker: Charles Consel | ||
<p> | <p> | ||
| − | Slides: [[ | + | Slides: [[Media:dagstuhl06.ppt|dagstuhl06.ppt]] |
| − | < | + | <br> |
Abstract:<br> | Abstract:<br> | ||
Domain-Specific Software Engineering | Domain-Specific Software Engineering | ||
| Line 20: | Line 14: | ||
This talk advocates the key role of domain expertise in the development of members of a program family. In this situation, we believe that a domain-centered approach should not be limited to a specific development step or software layer. Instead, we propose a domain-centered approach that is a continuum between modeling, programming and implementation. | This talk advocates the key role of domain expertise in the development of members of a program family. In this situation, we believe that a domain-centered approach should not be limited to a specific development step or software layer. Instead, we propose a domain-centered approach that is a continuum between modeling, programming and implementation. | ||
| − | |||
| − | |||
Latest revision as of 15:00, 16 December 2011
Charles Consel
Title:
A proposal for Domain-Specific Software Engineering
Speaker: Charles Consel
Slides: dagstuhl06.ppt
Abstract:
Domain-Specific Software Engineering
Traditionally, software development does not rely on an in-depth knowledge of the target domain. Instead, domain-specific knowledge is integrated in the software development process in an ad hoc and partial fashion, without much formal basis or tools. In doing so, software systems are takled in isolation, making conceptual or implementation factorization difficult. Yet, it is fundamental to observe that programs often belong to a family. In this family, they share commonalities and expose specific variations.
This talk advocates the key role of domain expertise in the development of members of a program family. In this situation, we believe that a domain-centered approach should not be limited to a specific development step or software layer. Instead, we propose a domain-centered approach that is a continuum between modeling, programming and implementation.
