NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 1

NQA User Training Module 2b

NQA User Training Part 3 Training by ISCN Ltd. http://www.iscn.com/ TEAMWORK Project Management Server http://www.euteamwork.net:2000/ TEAMWORK Web Site http://www.euteamwork.net/ NQA User Training for Teamwork Training Module 2b

User – Module 2b - Working with HTML/XML Document Types, Version 2, Richard Messnarz, 10/02/04

This work is supported by the EU under the IST-2000-28162 Teamwork project

Page 1

The NQA user works inside the project working areas created by the NQA Administrator (nqaadmin). The NQA Admin created such working spaces based on the scenarios entered in the Wizard and imported to the server by the Configurator. Note: This training module is specifically for users applying HTML/XML forms.

Page 1 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 2

Contents • • • • •

Working with HTML/XML Document Types Document Objects Report (Form) Objects Linked Report (Form) Objects Reading, Editing, Publishing Files with Built In HTML Editor • Submission of Files • Additional Documents and Interlinking NQA User Training for Teamwork Training Module 2b

User – Module 2b - Working with HTML/XML Document Types, Version 2, Richard Messnarz, 10/02/04

This work is supported by the EU under the IST-2000-28162 Teamwork project

Page 2 of 26

Page 2

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 3

The NQA user would log into the system and see a project list (of those projects where he has access to). Also !!!, please note that if you log in the first time and do not see the user interfaces displayed here, you need to call VIEW – SWITCH NQA ON/OFF. The system offers both, a pure file view and an NQA user interface view. We assume that you switched on the NQA User Interface View. The user would either use the tree view on the left or the links in the main frame to select projects and sub-projects. Finally the user would select the project area to which he/she has to contribute.

Page 3 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 4

Once the NQA user selected the project working area this shows the available working scenarios. The user would now select the appropriate working scenario.

Page 4 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 5

Inside a scenario the user finds pre-defined document types and report types.

(a)

Documents

Documents - There is a standard user interface to offer documents. Documents fall under configuration management, can be linked with reports and other documents, can be down-loaded, edited, and uploaded, and submitted to a team. (b)

Reports

Reports - Reports usually are forms to be filled in, linked to a document, and submitted to a team. Linked Reports - same as with reports, plus the report is automatically linked by its creation back-ward and forward to a predefined set of reports and documents.

With entering a title and ADD a report template is selected by the system automatically and a further report is added to the list.

Page 5 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 6

Linked Reports - same as with reports, plus the report is automatically linked by its creation back-ward and forward to a predefined set of reports and documents. Enter a title, select the document to be linked in CONNECT-TO and select ADD. This creates a link forward and backward between the report and document. This type of linking is configured by the Configurator and offered to the users by the system .

Page 6 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 7

When you open a document or report you enter a SUBMISSION DIALOG which allows you to • • • •

to check out the document and change it to see all versions in a history to just view it (HTML and XML is directly displayed) to submit it to the configured list of recipient roles

With Version List you receive a history of all previous versions created/changed by the users in the team.

Page 7 of 26

NQA/TEAMWORK

NQA Server User

Transparency 8

Created Linked Reports show in the appendix (see Review Notes above).

Page 8 of 26

NQA 5.3

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 9

For HTML/XML documents/reports the system displays the content . With Version List you receive a history of all previous versions created/changed by the users in the team.

Page 9 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 10

Select CHECK OUT TO EDIT. The system supports version control. This means that if you want to change a document or report you need to check it out from version control. This leads to a situation where • other users connecting to this document will be informed that you are working on it at the moment and they cannot change it • you will receive a working copy which you can replace with a newer version • you will receive an editing related menu which allows to replace the file, change the status, link other documents, etc. When the user calls CHECK OUT TO EDIT the system first shows the existing list of versions (you might select an older version to continue work) and with OK checks out the selected version for editing. By default the latest version checked in the system is selected.

Page 10 of 26

NQA/TEAMWORK

NQA Server User

Transparency 11

To edit the HTML/XML file online (after Check Out) you call EDIT – HTML EDITOR.

Page 11 of 26

NQA 5.3

NQA/TEAMWORK

NQA Server User

Transparency 12

In the HTML EDITOR you have a graphical window and can • do formatting • create links • create tables • set colours • etc. and PUBLISH back to the server with the diskette logo in the top menu bar.

Page 12 of 26

NQA 5.3

NQA/TEAMWORK •

NQA Server User

NQA 5.3

Transparency 13

Once the user has uploaded the new version , the version needs to be checked into version control. The CHECK IN will • register the new version in the history • inform users that you have finished working on it and they can now again change the file (if needed) • receive a notification by email

Page 13 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 14

If the user does only want to check in the new version without submission of a task or notification to other team members he/she might choose EDIT – CHECK IN FOR DISTRIBUTION through the menu.

Page 14 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 15

If you choose the CHECK IN button the SUBMIT is called automatically. If you checked in via the menu or you want to submit again, you can press the SUBMIT button in the SUBMISSION DIALOG. This reads the recipient roles and automatically determines the users who play the roles. A submission list is generated.

Page 15 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 16

The submission list is displayed, the NQA user can add TASK information (button TASKS), check or uncheck recipients from the generated list, and SUBMIT. The submissions are logged and are accessible for control .

Page 16 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 17

NQA users might want to publish files which are not based on previously defined result templates. These documents can be stored in an ADDITIONAL DOCUMENTS folder which is created by default for each project area.

Page 17 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 18

Once the ADDITIONAL DOCUMENTS area has been selected, files can be uploaded with FILE – UPLOAD menu command.

Page 18 of 26

NQA/TEAMWORK

NQA Server User

Transparency 19

These additional documents can be linked to official deliverables with the LINK DOCUMENTS/OBJECTS function. This function is mostly used as follows: • publish a file into additional documents • select and check out an official document/report • call LINK DOCUMENTS/OBJECTS and select the additional file • confirm CREATE LINKS • check in the new version of the official document/report The new NQA 5.3 version also allows to set such links without a checkout and checkin.

Page 19 of 26

NQA 5.3

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 20

In the list of files offered for linking you select the additional file, scroll down, and choose CREATE LINKS.

Page 20 of 26

NQA/TEAMWORK

NQA Server User

Transparency 21

The interlinked file is shown in the appendix.

Page 21 of 26

NQA 5.3

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 22

If you publish an HTML document which linked a graphic, then• • •

upload the graphic as well see next slide: in the Tab description ensure that only the image name and no path is contained and then upload

Page 22 of 26

NQA/TEAMWORK Transparency 23

Page 23 of 26

NQA Server User

NQA 5.3

NQA/TEAMWORK

NQA Server User

Transparency 24

The published files will show like above. By clicking the i icon you can change attributes of the file e.g. the name.

Page 24 of 26

NQA 5.3

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 25

You can then edit the HTML document and insert the gif image as a link (INTERNAL LINK – as the gif image is then uploaded already).

Page 25 of 26

NQA/TEAMWORK

NQA Server User

NQA 5.3

Transparency 26

Summary of Lessons Learned For HTML Document Types

• You know how to create documents and reports • You know how to read, change, publish and submit documents or reports • You know how to upload and interlink documents not following NQA formats and guidelines

NQA User Training for Teamwork Training Module 2b

User – Module 2b - Working with HTML/XML Document Types, Version 2, Richard Messnarz, 10/02/04

This work is supported by the EU under the IST-2000-28162 Teamwork project

Page 26 of 26

Page 26