S
Steven Kelly
For those going to XP 2005 (Sheffield, UK, June 18-23) and interested
in modeling, the following workshop may be of interest:
Agile Development with Domain Specific Languages
Scaling up Agile - is Domain-Specific Modeling the key?
Alan Cameron Wills and Steven Kelly
http://www.dsmforum.org/events/ADDSL05/
This workshop will investigate the application of Domain Specific
Languages within Agile development. A Domain Specific Language (DSL)
is designed to express the requirements and solutions of a particular
business or architectural domain. SQL, GUI designers, workflow
languages and regular expressions are familiar examples. In recent
years, Domain-Specific Modeling has yielded spectacular productivity
improvements in domains such as telephony and embedded systems. By
creating graphical or textual languages specific to the needs of an
individual project or product line within one company, DSM offers
maximum agility. With current tools, creating a language and related
tool support is fast enough to make DSM a realistic possibility for
projects of all sizes.
Topics to be tackled include:
Process and Roles surrounding DSM
DSL users and DSL designers - are they separate?
Does DSM affect the development process?
How effective is DSM for high-level design of big projects?
- Or is it better at focused aspects inside a design?
How do you design a DSL?
Identifying variable aspects of the domain
- do you make a model or do you look at existing code?
Gradual evolution or big upfront design? - optimizing investment
Maintaining compatibility as the language evolves
Creating the execution platform from existing systems
Ecology of DSLs
Designing a DSL from fragments of others
DSL repositories and markets
Return on Investment
When to use DSM
Are DSLs syntactic sugar on a framework API?
The development cycle
Testing in terms of the DSL and its abstractions
Debugging a DSL
Choosing a type of DSL
Graphical, textual, interactive
Uses of the DSL in an agile process; user roles
Defining DSLs
Grammars and editing tools
Constraints and validation
Generating code and artifacts
Generating or mapping code and other artifacts
DSLs used for validation and testing
Composing aspects of multiple DSLs
To join, please send one or two pages describing your interest in the
topic and ideas to (e-mail address removed)
Looking forward to seeing you there!
Steven Kelly and Alan Cameron Wills
in modeling, the following workshop may be of interest:
Agile Development with Domain Specific Languages
Scaling up Agile - is Domain-Specific Modeling the key?
Alan Cameron Wills and Steven Kelly
http://www.dsmforum.org/events/ADDSL05/
This workshop will investigate the application of Domain Specific
Languages within Agile development. A Domain Specific Language (DSL)
is designed to express the requirements and solutions of a particular
business or architectural domain. SQL, GUI designers, workflow
languages and regular expressions are familiar examples. In recent
years, Domain-Specific Modeling has yielded spectacular productivity
improvements in domains such as telephony and embedded systems. By
creating graphical or textual languages specific to the needs of an
individual project or product line within one company, DSM offers
maximum agility. With current tools, creating a language and related
tool support is fast enough to make DSM a realistic possibility for
projects of all sizes.
Topics to be tackled include:
Process and Roles surrounding DSM
DSL users and DSL designers - are they separate?
Does DSM affect the development process?
How effective is DSM for high-level design of big projects?
- Or is it better at focused aspects inside a design?
How do you design a DSL?
Identifying variable aspects of the domain
- do you make a model or do you look at existing code?
Gradual evolution or big upfront design? - optimizing investment
Maintaining compatibility as the language evolves
Creating the execution platform from existing systems
Ecology of DSLs
Designing a DSL from fragments of others
DSL repositories and markets
Return on Investment
When to use DSM
Are DSLs syntactic sugar on a framework API?
The development cycle
Testing in terms of the DSL and its abstractions
Debugging a DSL
Choosing a type of DSL
Graphical, textual, interactive
Uses of the DSL in an agile process; user roles
Defining DSLs
Grammars and editing tools
Constraints and validation
Generating code and artifacts
Generating or mapping code and other artifacts
DSLs used for validation and testing
Composing aspects of multiple DSLs
To join, please send one or two pages describing your interest in the
topic and ideas to (e-mail address removed)
Looking forward to seeing you there!
Steven Kelly and Alan Cameron Wills