-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Project workflow - number of instances of different types of artefacts #176
Comments
In a design project, the design team will evaluate artefacts produced at each stage of the design process (e.g. conceptualisation, authoring, implementation, enactment) . It is the results of these evaluations that will determine the number of design artefacts that a project contains; the number cannot usually be predicted in advance. |
A project that has been defined, then implemented, presents an empty instance of each artefact as shown in the image above. It would be useful to be able to add artefacts to the project. E.g. have another button 'Add LdS to project' to the left of 'Trash selected LdS'. Clicking this button should offer the user the chance to create a new LdS of any of the types included in the project template. This would avoid the project implementation being full of empty instances when first created. It would be helpful to be able to share a whole project (including all the LdSs it contains) with a group or several othe ILDE users, It would be useful to also have a menu item for 'All my projects' which displays the names of projects. Clicking each project should display the LdSs within each project. |
I created a workflow specifying e.g. 2 instances of several classes of design artefact.
When I instaiate (implement) this workflow, there is only one of each class in the project.
I want to be able to say a project can contain whatever the users want it to. Of course, we can guide them, but if they as designers need (say) 4 course maps and 5 iterations with Web Collage (and hence about 8 heuristic evaluations) to achieve their design goals, the ILDE should allow this.
The text was updated successfully, but these errors were encountered: