• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Content management system requirements checklist
 

Content management system requirements checklist

on

  • 2,241 views

A requirements checklist for reference purpose.

A requirements checklist for reference purpose.

Statistics

Views

Total Views
2,241
Views on SlideShare
2,236
Embed Views
5

Actions

Likes
0
Downloads
42
Comments
1

1 Embed 5

http://www.linkedin.com 5

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1 previous next

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • This has been plagerised from the Australian Queensland Government. Please acknowledge your source in your presentation, as this is not your own work.

    http://www.qgcio.qld.gov.au/SiteCollectionDocuments/Architecture%20and%20Standards/Information%20Standards/Toolbox/Internet/Tools%20and%20checklists/cms_require.doc
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Content management system requirements checklist Content management system requirements checklist Document Transcript

    • Lecture Notes – Content Management System Requirements Checklist – Prepared by Sukh SandhuPage | 1 (Check whichever is applicable) Web Development Capabilities Mandatory Highly Desirable Desirable (but Optional) Development and Quality Assurance Must support a develop, stage and deploy framework Must support branching to allow for co- development of parallel site Must support the concept of separate user environments for development Must support concurrent development of assets (e.g. asset locking) Must be an open architecture Must provide a way for contributors to QA their own work Must provide a way to snapshot current development for standards review. Must provide private work areas for non- disruptive Web development Must have ability to compare a file to any of its previous versions Must provide for commenting
    • Must have HTML merge capability Must have global search and replacePage | 2 Must have automated content scheduling (for both publishing and archiving) Asset Support Capability Must be able to support database assets Must be able to automatically sync database and file system content Must support existing file system assets to eliminate content retrofit Must support rules-based search against all meta-tagged assets Must fully support streaming media Must provide portal-style in-line asset commands for personalisation Must have the ability to deliver content in different formats (ie PDF, word, audio, video) Workflow Must have a clearly defined procedure that ensures that records are identified and captured into a recordkeeping system Must support designated agency approvals
    • processes Must contain a graphical user interface to build workflowsPage | 3 Must support iterative loop backs for rejected changes Must support flexible workflow definition to capture existing process Must support task-based workflow (ie creation, editing, approval) Must support metadata integration for configurable ‘smart’ workflows Must support modifiable task attributes Must support nested workflows Must support rules-based Workflow Registration Must allow users to view tasks assigned to them Must have the ability for Managers to monitor tasks and initiate follow-ups Must allow automated notifications of tasks to be performed Project Management Must support parallel development streams Must support instant creation of separate
    • development environment. Must support reporting via standard reports or customisable reportsPage | 4 Must support workflow tracking and monitoring Versioning and Rollback Capability Ability to version complete sites not just components Ability to rollback to previous version of sites Ability to log and monitor changes to site components Ability to rollback to previous version of site components Must display status of files and folders Must have change tracking and the creation of audit trails Templating Must support content for re-use During content entry, contributors must be able to manipulate content elements Must be able to support customised components within the page generation
    • engine Ability to standardise content according to business rulesPage | 5 Must separate Form from Content Must support pre-generated pages for increased scalability and performance Must support on-the-fly pages Must support the nesting of templates Must support variable binding Must have metadata management facilities Must support the ability for users to add to templates Must provide browser based GUI Must provide URL-Based Templating Deployment Capability Must provide high security during deployment Must be able to flexibly re-map directories during deployment Must support transactional deployment for rollback for both database and filesystem assets Must be able to deploy files, databases and code synchronously
    • Must be able to schedule automatic deployment to production server Must be able to move database tables fromPage | 6 staging to production Must support incremental and transactional deployment for database and filesystem assets Third party Integration and Customisation Must support industry standard authoring tools Must supports all app servers & e- Commerce engines Must be able to customise application for integration Must support automatic link checking Must support automated split-up of long documents Must have full attribute and content searching Open to any personalisation technology Must be able to leverage existing enterprise resources through seamless process and application integration
    • Reliability, Availability, and Security Must support 128-bit encryption, peer to peer authenticationPage | 7 Must contain functions to make the most efficient use of available storage space Must support load balancing, system failover and session management capabilities Must support role-based privileges in development Must support reporting (including usage analysis) User Interfaces Must be able to support seamless integration with Microsoft Office Tools (Word, Excel, etc.) and Lotus Notes applications Must have an easy to use interface with user id, password and role Users must have the ability to personalize their interface Must allow non-technical contributors to contribute with minimal training Must support a file system interface - supports any front end editing tool Must be scalable to meet growing volume
    • of users Must have Agency platform compatibility Must have Agency browser supportPage | 8