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

Abstract Prototype

The abstract prototype gives a description of all steps needed to meet a functional requirement/use case. It describes a condition where functional requirements are met. It does not need to take any visual frontend elements into consideration. Thus it refers to the goal to be met, not to the way it is achieved (referring to cognitive abilities, mental model).

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. Status
5. Target Release (New file now)
6. Assigned To (Covered by Jira)
7. Path/File
8. ALT/Title Tag
9. eSciDoc Component

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

PubMan Prototype

Publicly Available	Latest Version	Current Implementation
Searching	Searching	PubMan on eSciDoc 2
Submission	Submission
Easy Submission	Easy Submission
Quality Assurance	Quality Assurance
Browsing & Displays	Browsing & Displays
Export	Export

VIRR Prototype

Publicly Available	Latest Version	Current Implementation
	VIRR R1	In development

FACES Prototype

Publicly Available	Latest Version	Current Implementation
	FACES R1	FACES R1 FACES R1 (Alternative Location)
	FACES R2	In development

Axure Files

All axure files are versioned in SVN here:

• Searching
• Submission
• Easy Submission
• Quality Assurance
• Browsing and Displays
• Export
• VIRR
• VIRR Alternative
• FACES R2

Enhanced Scientific Documentation

Hypertext Markup Language

Cascading Style Sheets

Graphical User Interface

Error Management and Project Management Software

Publication Management

Virtueller Raum Reichsrecht

Apache Subversion