Workshop was organised to do three things:
- enable U&I Projects to produce outputs for the eFramework
- to help the eFramework team to validate its own elicitation processes
- to introduce participants to "Project X", the Innovation Base (IB)
So the proposition may be: can systems development language be applied to the description of a social learning research problem?
- organisation
- motivation
- what is the wow factor (impact)
The workshop opened with a defense of and justification for the use of modeling languages to reduce ambiguity, increase precision, allow interchange, re-use and forward engineering (CASE).
Drawing tools can be used, but do little to increase precision. Topic mapping tools are better. Language-based modeling (UML, etc) is best suited.
We were invited to begin Modeling the IB (Innovation Base). The Innovation Base is seen as a bridge to the eFramework. This led to an exposure of assumptions underlying the eFramework and an observation that points of view are crucial to understanding abstraction. The developer's perspective holds the system layer to be less abstract than the use case, but the end user will view the use case as precise and concrete and will see the system layers as abstract.
I drew some pictures and took some pictures. Chapter and verse is here.
Our Problem
How to support the U&I programme to form a sustainable community of practice around the UIDM requires:
- Community formation service(s)
- Community participation service(s)
- User needs elicitation services
Comments