193x Filetype XLS File size 0.12 MB Source: www.sonoma-county.org
Sheet 1: Full requirement list cat'd
Requirement Number | Category | Sub-Category | Requirement Description | Application (GUI): 1= Required 2= Highly Desired 3= Nice to Have 0= Not applicable to the Application Interface |
Published Web Page: 1= Required 2= Highly Desired 3= Nice to Have 0= Not applicable to the Published Web Page |
Capability: F = Provided fully functional and out of the box or with configuration (no custom development required) CU = Customization/Software Enhancement CR = Custom Report Development Required TP = Third-party Software required to fully provide requirement (third-party software must be proposed) N = Not included in this proposal |
Vendor's Explanation or Comments | ||||
1.02 | Business Requirements | Access and Security | Security is implemented at both individual and group levels (role based). Security allows varying access levels: read/write/God and varying scope: dept, site, folder, file, role, user, group, sub-groups. | 2 | 0 | ||||||
1.04 | Business Requirements | Access and Security | 3rd-party audit (Qualys, Hack-Safe), disaster, SAS 70, ISO 17799 | 2 | 0 | ||||||
1.05 | Business Requirements | Access and Security | Able to distribute content management to multiple authors for different sections of the same page, with each author having her/his own level of authorization and workflow (object level security). Objects may include page sections, pages, or entire sites. | 2 | 0 | ||||||
1.06 | Business Requirements | Access and Security | Authorized users shall be able to log into the system from any computer, anywhere, on any device. | 2 | 0 | ||||||
1.07 | Business Requirements | Publishing and Workflow | Provides cross browser compatibility for administration and publishing (Mozilla, Explorer). | 2 | 0 | ||||||
1.09 | Business Requirements | Access and Security | Uses a decentralized management model with departments able to manage their own authorization levels. | 2 | 0 | ||||||
1.10 | Business Requirements | Access and Security | Option for a central administrator to approve department users and scope before activation user access. | 3 | 0 | ||||||
1.11 | Technical Requirements | Active Directory Integration | User authentication and authorization can be integrated with Active Directory. | 2 | 3 | ||||||
1.12 | Technical Requirements | Active Directory Integration | Option to disassociate Active Directory. | 3 | 3 | ||||||
1.13 | Business Requirements | Access and Security | Configurable user auditing tool capable of tracking users navigation throughout the sites under control of the WCMS, including user name, date/time stamp, description of activity, page(s) modified or viewed and duration. | 2 | 0 | ||||||
1.15 | Technical Requirements | Ability to configure alternative TCP/IP ports (reverse proxy, etc). | 2 | 2 | |||||||
1.16 | Technical Requirements | Access and Security | Solution to provide capability to report faults to system administrators in real time, content administrators and (appropriate message for) visitors. | 2 | 3 | ||||||
1.17 | Technical Requirements | Content Management and Validation | Utility to facilitate page, folder and/or site comparisons. | 3 | 0 | ||||||
2.01 | Business Requirements | Publishing and Workflow | Image resize capability. | 2 | 2 | ||||||
2.02 | Business Requirements | Publishing and Workflow | Ability to set reminders to review published content by interval or date. | 2 | 0 | ||||||
3.01 | Business Requirements | Content Management and Validation | Ability to audit user content prior to publishing - validate section 508, WCAG, WAI, County guidelines, spelling, etc. | 2 | 0 | ||||||
3.03 | Technical Requirements | Ability to configure specific W3C and WCAG versions for Document Type Definition (DTD). | 2 | 0 | |||||||
3.05 | Business Requirements | Content Management and Validation | Section 508 compliance: Ability to upgrade to new compliance standards as they are implemented and audit at configurable levels | 2 | 2 | ||||||
3.06 | Business Requirements | Content Management and Validation | W3C compliance: Ability to upgrade to new compliance standards as they are implemented and audit at configurable levels | 2 | 2 | ||||||
3.07 | Business Requirements | Content Management and Validation | WAI compliance: Ability to upgrade to new versions as they are implemented and audit at configurable levels | 2 | 2 | ||||||
3.08 | Business Requirements | Content Management and Validation | WCAG compliance: Ability to upgrade to new compliance standards they are implemented and audit at configurable levels | 2 | 2 | ||||||
3.10 | Technical Requirements | Streaming Media | System capable of delivering Real Simple Syndication (RSS). | 2 | 2 | ||||||
3.12 | Business Requirements | Social Media | System capable of consuming content from social networking sites into selected county web pages. | 2 | 2 | ||||||
3.13 | Technical Requirements | Social Media | System capable of archiving content published to social media sites and provide audit trails (who, what, when) | 2 | 2 | ||||||
3.14 | Technical Requirements | Social Media | System capable of restricting use to authenticated users to approved social networking sites and tool. | 2 | 2 | ||||||
3.15 | Technical Requirements | Social Media | System capable if delivering content to social networking sites via CMS interface including protected social network accounts | 2 | 2 | ||||||
3.16 | Technical Requirements | Social Media | System capable of consuming content from external sites into selected county web pages | 2 | 2 | ||||||
3.17 | Business Requirements | Publishing and Workflow | Ability to create surveys/polls, track results, reports | 2 | 2 | ||||||
3.18 | Business Requirements | Publishing and Workflow | The solution may provide collaboration tools: white board and instant messaging. It may also provide for forums, blogs. | 2 | 2 | ||||||
3.19 | Technical Requirements | Content Management and Validation | Content capable of being rendered through a variety of protocols such as: Wireless Application Protocol (WAP), Extensible Markup Language (XML), and Extensible Hypertext Markup Language (XHTML). | 0 | 2 | ||||||
3.21 | Technical Requirements | Publishing and Workflow | WYSIWYM authoring, what you see is what you mean, ability to interpret content as you intend it to be understood. | 2 | 0 | ||||||
3.22 | Technical Requirements | Publishing and Workflow | WYSIWYG: Ability to see (preview) content as it will appear before it is published. | 2 | 0 | ||||||
3.26 | Technical Requirements | Access and Security | Supports scanning of uploads or is compatible with major virus/malware scanning applications. | 2 | 2 | ||||||
3.29 | Business Requirements | Data Maintenance | Easily compare historical versions with differences highlighted. | 3 | 0 | ||||||
3.30 | Business Requirements | Content Management and Validation | Audit trail of changes, who made them, and produce report of changes. | 2 | 0 | ||||||
3.32 | Technical Requirements | Content Management and Validation | System to support addition of external functionality through custom scripting, querying databases outside of WCMS, etc | 2 | 0 | ||||||
3.33 | Business Requirements | Content Management and Validation | Ability for a content contributor to pull in web service (e.g., authentication services, current appointment services, account validation services, profile services, etc.) as an object and use it within a given template. Once page is published, the service should be called from the deployment server (server published to) and displayed within the page, and the service should function properly (not have been altered by the WCMS). | 2 | 2 | ||||||
3.34 | Business Requirements | Publishing and Workflow | Ability to facilitate Section 508 compliance with workflow, prompts etc. | 2 | 0 | ||||||
3.35 | Technical Requirements | Content Management and Validation | Ability to validate links on our servers or the internet. | 2 | 0 | ||||||
3.36 | Business Requirements | Content Management and Validation | Ability to upload multiple files, folders. | 2 | 0 | ||||||
3.37 | Technical Requirements | Data Maintenance | Ability to integrate with document management systems (OnBase, SharePoint, etc.). | 3 | 0 | ||||||
3.40 | Technical Requirements | Content Management and Validation | Ability to manage links and destinations from a central link respository. | 2 | 0 | ||||||
3.41 | Business Requirements | End-User Function | WCMS is functional and usable to authors who have basic word processing skills. | 2 | 0 | ||||||
4.02 | Business Requirements | End-User Function | Ability to create secure online forms with no programming skills. | 2 | 0 | ||||||
4.04 | Business Requirements | Publishing and Workflow | Online forms are capable of creating, receiving, and pushing data to/from multiple sources. Data is capable of being posted to a third-party database, being sent via email, or transferred to other web applications. | 2 | 2 | ||||||
4.05 | Business Requirements | Publishing and Workflow | Calendaring tool for creation and maintenance of public countywide and department calendars. | 2 | 2 | ||||||
4.06 | Business Requirements | Publishing and Workflow | Calendar has export features compatible with popular 3rd party calendaring tools (e.g. Outlook, iCalendar) | 0 | 2 | ||||||
4.07 | Business Requirements | Publishing and Workflow | System has export features compatible with popular 3rd party address books (e.g. Outlook) | 0 | 2 | ||||||
4.10 | Business Requirements | Publishing and Workflow | Ability to schedule publishing at future dates and times including link management. Ability to predetermine expiration dates and time published content and/or pages including link management. | 2 | 2 | ||||||
4.11 | Technical Requirements | Content Management and Validation | Incorporate a search engine capable of functioning with fuzzy logic or language-friendly terms. | 2 | 2 | ||||||
4.12 | Technical Requirements | Content Management and Validation | Ability to create "Related resources" or reference links related to search results as well as current page. | 3 | 3 | ||||||
4.13 | Business Requirements | End-User Function | Supports personalization for end-users. | 3 | 3 | ||||||
4.14 | Business Requirements | Publishing and Workflow | Offers subscription and notification services via email with options for frequency and summary/detail preferences. Include opportunity for contributors to describe changes at the time of publication (to allow automation of meaningful notifications). | 2 | 2 | ||||||
4.15 | Technical Requirements | Publishing and Workflow | Offers RSS and aggregation services. Include opportunity for contributors to describe changes at the time of publication (to allow automation of meaningful notifications). | 2 | 2 | ||||||
4.18 | Technical Requirements | Publishing and Workflow | Ability for configurable event notification via email. | 2 | 0 | ||||||
4.19 | Business Requirements | Content Management and Validation | Programming: Ability to reference existing data using standard naming constructs (variables from within a page/template, include files). | 3 | 0 | ||||||
4.20 | Business Requirements | Publishing and Workflow | Content Providers: Ability to reference existing data using easily recognized county standards. | 2 | 0 | ||||||
4.21 | Business Requirements | Publishing and Workflow | Ability to display maps, architectural drawings and other graphic presentations without compromising response time or user experience. | 2 | 2 | supp. Questionaire: how do you do this? | |||||
4.22 | Technical Requirements | Publishing and Workflow | Ability to extract data simultaneously from multiple sources for presentation on a single web page. | 2 | 0 | supp. Questionaire: how do you do this? | |||||
4.23 | Business Requirements | Publishing and Workflow | Tools to facilitate self-editing functions: including but not limited to spell check, including master and site-level dictionaries. | 2 | 0 | ||||||
4.24 | Business Requirements | Publishing and Workflow | grammar check. | 3 | 0 | ||||||
4.25 | Business Requirements | Publishing and Workflow | acronym management | 3 | 0 | ||||||
4.26 | Business Requirements | Publishing and Workflow | multi-lingual spell check. | 3 | 0 | ||||||
4.28 | Business Requirements | Publishing and Workflow | Solution to include a staging state where content in development can be previewed ("production-equivalent environment). | 2 | 0 | ||||||
5.04 | Technical Requirements | Publishing and Workflow | Provide optional caching at various scopes (full page, content, object, element). | 3 | 0 | ||||||
5.11 | Technical Requirements | Access and Security | Ability to configure maximum number of concurrent administrative sessions. | 2 | 0 | ||||||
5.12 | Technical Requirements | Publishing and Workflow | Configurable search engine which allows extensible search of servers outside the WCMS solution. | 3 | 0 | ||||||
6.01 | Web Hosting | Web Hosting | Internet outbound access bandwidth should start at 50 mbps minimum with dynamic burst capability up to near OC-48 backbone (current expectation). | 2 | 2 | ||||||
6.03 | Web Hosting | Provide the following usage statistics, including but not limited to: browser and versions, unique visits vs sessions, bounce rates, paths used, enter/exit pages, time on page, etc, | 3 | 2 | |||||||
6.07 | Web Hosting | Diverse high speed OC-48 paths to the Internet with automatic IP address block rerouting (BGP4) | 2 | 2 |
no reviews yet
Please Login to review.