Information Technology Reference
In-Depth Information
Act 1. Identify
Tasks
Act 4. Model DC
Knowledge
Act 2. Model Tasks
as Dependencies
Act 3. Capture
Dependencies
Act 5. Use
Intelligibility-
related Services
Act 6. Evaluate
Services
[Missing
Dependencies]
[YES]
[NO]
Fig. 8.12
Methodological steps for exploiting intelligibility-related services
subtype relationships, i.e.
render2D
render
and
render3D
render.
We can
also define hierarchies of modules e.g. 2DImage
Image.
Act. 3
Capture the dependencies of digital objects.
This can be done manually,
automatically or semi-automatically. Tools like PreScan [
123
] can aid this
task. For example if we want to render a 2D image then we must have an
Image Viewer and if we want to render a 3D image we must have the 3D
Studio application. In our example we can have dependencies of the form
landscape.jpeg
>
render
2
D
ImageViewer
,
illusion.3ds
>
remder
3
D
3D
_
Studio
etc.
Act. 4
Modelling community knowledge.
This activity enables the selection
of those modules that are assumed to be known from the designated
communities of users. In our example suppose we want to define two pro-
files; A DigitalImaging profile containing the modules {
Image Viewer
,
3D Studio
}, and an Ordinary profile containing the module {
Image
Viewer
}. The former is a profile referring to users that are familiar with
