RSS feed

Linkedin Profile

Tags:
programming
seattle
things that bug me
wall art

Posts by month: 10/08 (2)
08/08 (1)
06/08 (2)
05/08 (1)
03/08 (3)
02/08 (1)
01/08 (2)
12/07 (2)
11/07 (1)
07/07 (1)
05/07 (2)
02/07 (1)
01/07 (1)
12/06 (1)
11/06 (1)
10/06 (1)
08/06 (1)
07/06 (1)
06/06 (2)
05/06 (1)
04/06 (2)
02/06 (1)
01/06 (2)
12/05 (3)
11/05 (2)
09/05 (5)
08/05 (5)
07/05 (7)
06/05 (3)
05/05 (6)
04/05 (8)
03/05 (7)
02/05 (7)
01/05 (6)
12/04 (2)
11/04 (3)
10/04 (5)
09/04 (3)
08/04 (5)
07/04 (5)
06/04 (4)
05/04 (4)
04/04 (9)
03/04 (4)
02/04 (3)
01/04 (5)
12/03 (1)
11/03 (14)
10/03 (8)


A visual language for separating concerns
2005-01-27

The screen shot below is taken from a designer I built using the latest DSL Tools CTP for Visual Studio. The language/diagram is tentatively called a concern map

Concern map screen shot

The designer lets a programmer make a basic box and arrow diagram (see the black boxes below), representing significant concerns within a system (layer, sub-system, anything of interest). The magic is in the little green boxes - these contain expressions which bind the black box to real artefacts in the IDE (think classes, methods, documents, whatever).

That's the idea, at least. I've already got the heavy lifting done for binding to code constructs by writing query expressions. In this case, the green boxes will contain XPath : I've implemented the underlying query capability by disassembling from IL (for code, classes, methods etc) and PDB (for file info) to an XML representation, which can be XPathed, and one day XQueried.

The next step is to integrate this with the concern map designer, so a programmer can double click one of the boxes and load up the related classes, methods etc. in the IDE. Luckily the DSL tools make the designer source available, and I've managed to hijack the click events on the canvas. Expect a prototype next week.

Back to weblog