ESciDoc Prototyping

Introduction

All interfaces coming up for the eSciDoc project are generated as static html pages:

Example

They do not contain any valid HTML, CSS or JS. Prototypes meet the following demand:

1. Visualization and discussion of new approaches/ideas
2. Technical evaluation
3. Functional evaluation
4. Usability evaluation
5. Documentation

Prototypes are generated with Axure RP Pro. Please mind that Axure prototype files of current Releases can not be opened in older versions.

Issues in R5

Abstract Prototype

Abstract prototypes should reflect the main motivation, intentions of a certain user/user group and reflect a rough workflow, based on the motivation. the APT should visualize the user goals and the relevant information entities needed to reach the goal. The abstract prototype should not make any suggestions on the user interface or page flow, and should be media-independent, as much as possible. Modeling an APT should help to focus on the user, his motivation/intention and his specific interests while acting. An APT is a visualization/cognitive tool to support further detailed use case specification and detailed functional prototypes.

Definition of Functional Prototype

Functional prototypes visualize all GUI elements, as precise as they appear after implementation:

1. all necessary/important pages that appear to the user
2. the page flow (Storyboard), where dynamic aspects can not be covered

Structure of Prototypes

The first page usually carries the name of the functional part. It shows a rough flow of important interface actions. The flow is not meant to rebuild the complete behaviour of the application. It shows:

• What actions are triggered: orange text
• What happens on the same page and what not: <page>
• When and on which pages messages appear: msg

Each other parent page of the tree refers to a use case with the corresponding name. It carries the rough flow of the case to see which pages the user enters and leaves. Child pages contain graphical interfaces.

On the bottom of pages you can find a general note about the page. Yellow note stickers contain specification text.

Specification attributes of interface elements or details:

1. Label (Axure mandatory)
2. Interactions (Axure mandatory)
3. Specification
4. ALT/Title Tag
5. eSciDoc Component/Colors

These attributes are used to provide interface development and development a clear description of how the interface should look/work.

PubMan Prototype

	Available Versions	Current Implementation
	R3 Prototype (Browsing & Display)	Finished
	R4 Prototype	Finished
	R4.1 Prototype	Finished
	R5 Prototype	http://qa-pubman.mpdl.mpg.de:8080/pubman/

VIRR Prototype

	Available Versions	Current Implementation
	VIRR R1	http://192.129.1.123:8080/virr_presentation/
	VIRR R2.1	http://dev-virr.mpdl.mpg.de:8080/virr

FACES Prototype

	Available Versions	Current Implementation
	FACES R1
	FACES R2	http://faces.mpdl.mpg.de (or http://faces.mpib-berlin.mpg.de/)
	FACES R3
	FACES R3.5

Pattern Library

	Available Versions	Current Implementation
	FACES R1
	FACES R2	http://faces.mpdl.mpg.de (or http://faces.mpib-berlin.mpg.de/)
	FACES R3
	FACES R3.5

Axure Files

All axure files are versioned in SVN here:

• PubMan R4
• PubMna R5
• VIRR R1
• VIRR R2.1
• FACES R1
• FACES R2
• FACES R3

Enhanced Scientific Documentation

Hypertext Markup Language

Cascading Style Sheets

Graphical User Interface

Publication Management

Virtueller Raum Reichsrecht

Apache Subversion