JohnNilsson/On aspects vs full models

## On aspects vs full models
When discussing a particular subset of a system one can usually produce some light and useful UMLish diagrams of the topic on a whiteboard.

Displaying the true system model of the related components would be overwhelming and not usefull at all though.

I'm thinking that these ephermal aspects should be our true representation of the system implementation.

Instead of producing files with classes containing all related functionality ever thought of for that part of the model we should produce small snippets of design aspects relevant to the design session that created them.
	When discussing a particular subset of a system one can usually produce some light and useful UMLish diagrams of the topic on a whiteboard.

	Displaying the true system model of the related components would be overwhelming and not usefull at all though.

	I'm thinking that these ephermal aspects should be our true representation of the system implementation.

	Instead of producing files with classes containing all related functionality ever thought of for that part of the model we should produce small snippets of design aspects relevant to the design session that created them.