Server-Side Requirements for Content Delivery

Content model
1. Analyze the content types your site requires. Focus on domain-driven content types, not on
technical ones.
2. Specify what kind of content users should be able to submit. Define special content types for
user-generated content.
3. Establish what relationships hold between content elements. Express this through associations
between content types.
4. Add attributes for classification purposes (tags, categories) to all content types. Make sure you
meet the requirements that the intended search functionality has on meta information.
5. Specify how users will be able to get involved in content classification (tags, folksonomies,
ratings).
CONTENT TYPE HIERARCHY
TAXONOMY BASED ON KEYWORDS AND CATEGORIES
DECOUPLING OF EDITED CONTENT AND USER CONTRIBUTIONS
Navigation and search
1. Set up an initial navigation hierarchy. Content editors will later be able to adapt the navigation
hierarchy as they see fit, but an initial hierarchy is necessary to get you started.
2. Think about possible examples of dynamic content linking.
3. Specify the search functionality for your site (full-text search, keyword search, category-based
search, fuzzy search).
DECOUPLING OF CONTENT AND NAVIGATION (2.2)
DYNAMIC CONTENT LINKING (2.3)
TAXONOMY BASED ON KEYWORDS AND CATEGORIES (2.4)
Personalisation
1. Define what user segments will exist, and the extent to which content editors will have to define
criteria for grouping users into segments. User segments form the targets for the personalisation
strategies that apply.
2. Define the personalisation strategies for your site.
3. Define possible algorithms that underlie these personalisation strategies. Examples include
recommendation strategies and algorithms for assigning users to user segments.
4. Decide what monitoring is required for the personalisation efforts.
CONTENT FILTERS
Additional functionality
1. Check what additional functionality your site requires (community support such as forums or
chat rooms, shop software, etc.).
2. Analyze the requirements on operations (reports, statistics, etc.).

Client-Side Requirements for Content Delivery

Page design
1. Define the necessary page types. A page type for each domain-motivated content type is the
norm,
plus page types for search forms and the like.
2. Design wire frames for the all page types, outlining how the pages are in principle composed
from smaller page elements.
3. Engage a web designer to provide sample pages (preferably in XHTML with the necessary CSS
sheets) for the different page types. Several sample pages are necessary if different views are
required (for example for different output channels, such as standard browsers and mobile
devices). Make sure these sample pages meet the layout requirements for your site.
Client-side functionality
1. Decide on realistic assumptions about browser technology, taking the target users expected
software infrastructure into account.
2. Specify the client-side functionality (later to be implemented with Ajax technology) for all page
types.
SENSIBLE CLIENT-SIDE INTERACTION
SELF-CONTAINED PAGES
Non-Functional Requirements for Content Delivery
Performance requirements
1. Analyze the performance requirements that hold for your site, especially the average and the
maximum response time (assuming an average and a maximum number of users).
Availability requirements
1. Analyze the required average availability.
2. Analyze what down times and what content freeze intervals are acceptable during relaunch
periods.
Scalability requirements
1. Analyze the expected number of concurrent users at present.
2. Analyze the expected number of concurrent users in the future.
Maintenance requirements
1. Get an idea of features you may have to add to the site in the long run. More generally, get an
idea of how the site might evolve in the future. This will give you a feel for the importance of
maintainability.
Security requirements
1. Analyze security requirements for authentication, privacy, etc. based on the sites Criticality.
Requirements for Content Management
Workflow
1. Analyze what workflows are desired for the content editing process (four-eye workflow, etc.).
2. Analyze the extent to which content validation has to be integrated into these workflows.
WORKFLOW-BASED VALIDATION (2.5)
User Participation

1.

Analyze how user-generated content should be managed, and what approval

processes should be in effect.

INPUT CHANNEL FOR USER-GENERATED CONTENT (