Checklist for Decision Makers

OOo Marketing Project Please view the guidelines before contributing.
Categories: Art Conference (OOoCon) Draft ideas and materials Marketing Pages: Major OOo Deployments New releases Info To Do List Quick and Easy Activities Marketing Volunteers List Market Share Analysis Marketing to Developers Press Coverage The Case for Switching Why.OpenOffice.org Marketing Activities Record MarketingCampaign_Q3-2007 OOo Conferences Checklist for Decision Makers User Perception Research Strategic Marketing Plan Pages: Strategic Marketing Plan SMP To Do Projects on this Wiki: (edit list) Art Project * Application Framework Documentation Education Project * Marketing Project * Native Language Confederation * Product Releases Security Team Universal Network Objects User Experience Project Website Project Writer Project
Marketing.OpenOffice View or edit this template.

Category:Draft marketing ideas and materials 

Introduction

This checklist contains a list of the key requirements to consider when evaluating office software products, split between Mandatory (must have) and Optional (nice to have). Each requirement has a very brief description of why it is important in italics. The requirements are listed in typical priority order (most important first), although clearly each decision maker will need to check whether these are appropriate in their particular circumstances

Mandatory

• must support the main five office applications (spreadsheet, word processing, presentations, graphics, and database)
• must have a familiar user interface
• must be able to read and write all commonly available file formats
• must integrate easily with other typical desktop applications (email, web browser) to avoid lock-in to one supplier
• must be available on all leading computing platforms to allow you to change platforms in future
• must store files in an ISO approved file format to ensure your ownership of your intellectual property in your office documents
• source code must be freely available for inspection
• must be capable of adding functionality seamlessly with a simple extensions mechanism
• must be capable of being translated by local volunteer teams into minority / endangered languages