HydroWeb - Hints/Assessments
General Remarks - Hints on Web Report
The last week of HydroWeb has started alreday, all teams and most team members are active and
fighting with Mike11, the exercise and the reports.
I had a view on the team pages, there is still potential to
improve the Web based reporting of the team activities.
Please remind, idea of engineering reports is to document your work
for other experts in a way they can follow your decisions and all results
are fully reproducable.
There is still time to do so, but time is running ;-)
As the course is on
Web based Collaborative Engineering, it is no problem,
if your Mike11 model is not perfect.
You are 7-8 experts in each team you can work in parallel
to speed up the progress of your teams.
While some team members are working on the Web documents,
others can work on the Mike11 exercise. Web documents
are shared and allow synchronous editing by several persons!
There is no need to block each other by waiting
for activities of sub groups or other team members. Critical work packages
should have always the priority. In case of problem:
There is always a "hotline" (called supervisor)
available.
Please take care of the time schedule,
end of the team work is this Friday!
Work package 3 is based on work package 2. The result of WP2 is a model which considers all constraints of WP1 and WP2. WP3 is a study on this model concerning some parameters. Three parameters are selected:
You can organize WP3 by performing the three sub tasks
in parallel, maybe by different team members.
WP3.1 and WP3.2 require four resp. three simulation runs with different
parameters. WP3.3 at least two simulation runs with and without
the minimized cross section width. The results of the simulations
runs has to be analyzed, compared and finally evaluated
from the numerical, physical and engineering point of view.
Please feel free to contact the supervisor in case of questions and problems in WP3.
The final team reports of your teams have to be Web reports. A Web report is a document, which is located on a Web server and can be read and edit within a Web browser without any additional, locally installed software. A Web report consists of several linked components and can integrate different conventional and interactive multi-media components. Please do not use standard office packages such as LibreOffice or MicrosoftOffice. The idea is to gain experiences in Web based documentation and not in editing and copy&paste from Office package files such as Word files.
In HydroWeb we recommend to use the features of GoogleSite pages or/and GoogleDrive documents to design and write the team reports - most team are using convential types/structures/features of reports (only). For each semantic unit (e.g work package sub task) you can use one page/doc and link them by several reading paths including links to the report list and model list. This should be done in collaboration of all team members. You can do such kind of reporting in parallel as well as in editing sharing mode.
We know that most of you are shaped by (Microsoft) office products; this is indeed one way to write documents. But why not try another, more innovative way? Most important: Put the paper based way of thinking aside, there is not anymore just one sequence of pages and chapters and the 2D dimension of the media paper. You can do much more - if you like. Try and see. It would be interesting to evaluate such kind of Web based documentation in comparison to traditional way or reporting. Please take the reporting part as a challenge to get experiences in Web based collaborative engineering and reporting, not just as an obligation in an academic exercise ;-)
A short answer on the question:
What would be your collaboration approach, prerequisites and tools,
if you would to do the same course again in one month
with the same team composition?
These proposed components are only proposals to give you an idea, how your report(s) might be composed and structured. Please feel free to define and use your own team report components and structure!