Functional Content Application Designs

 

Description

 

The output is a declarative and functional description of the planned content based portal applications. The output is derived from the respective requirements of the content blueprint. Functional requirements, functional content application design and the related technical design could make up together the blueprint of a spezific portal application.

The application designs includes structured and grouped content objects (iViews and services) needed to build up the defined content scenarios in the portal.

The description could also include

 

·         Application concept and overall functionality

·         Visual description of the applications

·         Layout of required portal pages

·         Detailed navigation features and worksets in the content areas in question

·         Drag&Relate scenarios

·         Interdependencies and eventing between iViews

 

The composed and structured content objects build up a portal application. The defined portal applications might be assigned to the appropriate roles/groups in order to establish the final portal content structure (see the deliverable “Portal Content Structure Definition”).

The documentation on the portal applications might also be used to define work packages for the involved implementation staff.

 

Process

 

The portal application composition is based on the integration concept of the content sources in question. For example, a unification integration might be needed in order to enable Drag&Relate operations within a portal application.

A starting point for creating portal applications might be identified business processes and user roles. Process steps that are carried out by identical users can be grouped together within a portal application page.

The portal user interface design and usability studies should also be taken into account when pages are created.

 

Additional Information

 

The application design process is not limited to content objects that grant access to pure core-business process functions. The integration of content objects from collaborative scenarios, or of generic information content objects, might also be necessary.

When designing pure text-based “intranet” content, a portal content application and a portal page might be analogous.