Section_J-Attachment_C.9_WCMS_Requirements_Matrix-20160930-V1.pdf

Internal Revenue Service

Solicitation Number: TIRNO-16-R-00026

IRS Integrated Enterprise Portal 1.5 (IEP 1.5)

WCMS Requirements Traceability Matrix

September 13, 2016

SECTION J-ATTACHMENT 9

IRS Enterprise Portals Program

IRS Enterprise Portals Program

Contract #: TIRNO-11-D-00041

Task Order #: 0013

WCMS Requirements Traceability Matrix

Work Product #: W.1321.4

Version #: 2.0

Date: 09/02/2016 Updated by IRS ETI

D.X.X.X

C.9 WCMS Requirements Matrix.xlsx Contents

The WCMS RTM contains the following sections:

A. Assumptions

B. Business & Orig PWS Req

C. IRS.gov Requirements

D. StayExempt Requirements

E. EITC & Marketing Express Requirements

F. Future Requirements

G. O&M Requirements

WCMS

Requirements Traceability Matrix (RTM): Contents

IRS 3 of 52

Req't ID Assumption Grouping Source

A.1 System shall have the same URL path as in OpenText today for static files. Apps - XMLBC XMLBC/SFBU

A.2 System shall create individual nodes for each new static file and will overwrite the existing static file.

Apps - XMLBC XMLBC/SFBU

A.3 Assuming XML BC is approved in the final VROM, the application will be ported into the CMS. The XML will continue to be generated as is today, external to the

CMS, but the content pages will be created and built in the CMS following XML conversion.

Apps - XMLBC XMLBC/SFBU

A.4 Process will be established to ensure content will be synced between environments

Environments Requirements Review 1

A.5 System shall support 7 environments: development (DEV), test(SIT), UAT(EITE), performance(PETE), content training, developer training, production

Environments Environments

A.6 Detailed requirements regarding content type descriptions, field descriptions, error messages, fields in a views display, fields in a views exposed filter will be captured during sprints grooming session or sprint 0.

Implementation N/A

A.7 The system shall maintain the same look and feel for all sites as in OpenText, except as needed by proposed WCMS

Migration UX/UD

A.8 English will be the default language Multilingual Requirements Review 1

A.9 Parent node has to be created before creation of child content Multilingual Requirements Review 1

A.10 Site Exit disclaimer administration is currently an elevated permission and will be managed by IRS as is today

Permissions Apps

A.11 System's user permissions shall be based by organization and role for initial release

Permissions Pub Model 1

A.12 System shall allow configuration of modules based on permission. Permissions Requirements Review 1

A.13 The language landing page selector will remain in the current position Presentation Multilingual

A.14 Current external search configuration will be maintained Search Search 2

A.15 The Service Level Objectives defined for the IEP program related to the CMS will remain and be used to determine the solution blueprint

SLO 7/28 RTM Review

A.16 Each site shall enable migrations to IRS.gov Subsites 8/30 RTM Review

Req't ID Historical ID Req't Description Business Category Requirement Source

B.1 1.1.1 System shall support flexible role-based access and the ability to define and manage custom roles and permission schemas.

Permissions CMS Business Rqmts

V7_2_Final

B.2 1.1.2 System shall enable IRS administration of delivered system settings and configurations such as user permissions, password management, roles, workflows, templates, reporting and search

(content management services).

Permissions CMS Business Rqmts

V7_2_Final

CMS Business Rqmts

V7_2_Final C1

B.3 1.1.3 System shall support IRS Password Management standards as defined in IRM 10.8.1 Information Technology (IT) Security, Policy and Guidance.

Security CMS Business Rqmts

V7_2_Final

B.4 1.2.1 System shall have the ability to create, modify and manage multiple workflows.

Permissions CMS Business Rqmts

V7_2_Final

B.5 1.2.2 System shall support ability to define new user roles that can be incorporated into custom workflow processes.

Permissions CMS Business Rqmts

V7_2_Final

B.6 1.3.1 System shall provide tools for flexible report creation and export, and full IRS access to system data.

Reporting CMS Business Rqmts

V7_2_Final

B.7 1.3.2 System shall provide real-time measurements of CMS use and access.

Reporting CMS Business Rqmts

V7_2_Final

B.7.1 1.3.2 System shall provide real-time measurements of usage of computing resources, which includes server resources.

Reporting CMS Business Rqmts

V7_2_Final

B.8 1.3.3 System shall provide ability to generate content inventory reports based on metadata.

Reporting CMS Business Rqmts

V7_2_Final

B.9 1.3.4 System shall enable integration of website usage metrics to offer visibility to CMS content managers.

Reporting CMS Business Rqmts

V7_2_Final & CMS

Business Rqmts

V7_2_Final 5.4.6

B.10 1.3.5 System shall provide the ability to export any report in a delimited format.

Reporting CMS Business Rqmts

V7_2_Final

B.11 1.3.6 System shall provide audit trail and versioning of changes. Audit CMS Business Rqmts

V7_2_Final

B.12 1.3.7 System shall provide reporting for the type and quantity of information published in the CMS including types of content used and the extent of use.

Reporting CMS Business Rqmts

V7_2_Final

B.13 1.3.8 System shall support all internal IRS auditing and reporting policies.

Reporting CMS Business Rqmts

V7_2_Final

B.14 1.4.1 System shall support the creation, management and use of content types, including new content types based on emerging technologies.

Content Management CMS Business Rqmts

V7_2_Final

B.15 1.4.10 System shall support flexible website navigation menus, allowing for multiple menus, menus based on taxonomy, and creation, reuse and removal of menus and menu items.

Taxonomy CMS Business Rqmts

V7_2_Final

B.16 1.4.11 System shall support use of standardized URL schema for all content assets.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.17 1.4.13 System shall provide capabilities to add custom help text to describe the purpose of each field in the system for all CMS data fields.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.18 1.4.14 System shall support flexible capabilities for management, search, and reuse of all content types including files, digital media assets, URLs and links.

Content Management CMS Business Rqmts

V7_2_Final

B.19 1.4.15 System shall support the ability to modify or hide the visual display within the CMS user interface of CMS buttons, controls, system objects and content types based on the user's permissions.

Presentation CMS Business Rqmts

V7_2_Final

B.20 1.4.16 System shall provide the ability to designate mandatory data entry fields.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.21 1.4.17 System shall support aggregation, grouping, and reuse of nodes based on taxonomy or metadata.

Taxonomy CMS Business Rqmts

V7_2_Final

B.22 1.4.18 System shall support dynamic programming of components based on web usage metrics (e.g. popular related content).

Presentation CMS Business Rqmts

V7_2_Final

B.23 1.4.2 System shall support the custom definition, reuse, and extension of content types that can be organized based on taxonomy, or metadata labels.

Content Management CMS Business Rqmts

B.24 1.4.3 System shall support aggregation, grouping, and reuse of content types and their modules or components to create new content types.

Content Management CMS Business Rqmts

V7_2_Final

B.25 1.4.4 System shall support interactive content components and the ability to install them as content types. An example is an installation of an interactive form component (including submittal forms and Web page comments), search component, or other service component.

Interactive

Components

CMS Business Rqmts

V7_2_Final

B.26 1.4.5 System shall support appropriate variable page level structure to meet business needs of IRS.

Presentation CMS Business Rqmts

V7_2_Final

B.27 1.4.6 System shall provide standardized and reusable page layout. Presentation CMS Business Rqmts

V7_2_Final

B.28 1.4.7 System shall support use of customizable page templates that may be authored and implemented by the IRS.

Presentation CMS Business Rqmts

V7_2_Final

B.29 1.4.8 System shall provide the ability to embed Semantic Web designations.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.30 1.4.9 System shall support and manage required metadata fields. Metadata CMS Business Rqmts

V7_2_Final

B.31 1.5.1 System shall provide custom user and system notifications for system events, workflow and other activities as determined by business rules.

Notifications CMS Business Rqmts

V7_2_Final

B.32 2.1.1 System shall support metadata and full text search functions within the CMS including filtering, sorting and exporting capabilities.

Metadata CMS Business Rqmts

V7_2_Final

B.33 2.2.1 System shall provide the capability to mitigate SEO content duplication problems.

Search CMS Business Rqmts

V7_2_Final

B.34 2.2.2 System shall provide the ability to link paginated pages into a contiguous whole.

Presentation CMS Business Rqmts

V7_2_Final

B.35 2.2.3 System shall provide the ability to embed HTML, XML markup including HTags.

Content Management CMS Business Rqmts

V7_2_Final

B.36 2.2.4 System shall be able to automatically generate and publish XML site maps.

XML Site Map CMS Business Rqmts

V7_2_Final

B.37 2.2.6 System shall ensure that metadata and content changes are reflected near real-time in CMS search.

Search CMS Business Rqmts

B.38 2.3.1 System shall support automated processes for secure file loading and data transformation.

Import/Export CMS Business Rqmts

V7_2_Final

B.39 2.3.2 System shall support the ability to import and export content items securely in industry standard formats (including comma delimitated and XML) both individually and in bulk.

Import/Export CMS Business Rqmts

V7_2_Final

B.40 2.4.1 System shall support the content creation, review, update, historical, archive and deletion phases of the IRS Publishing

Model.

Publishing CMS Business Rqmts

V7_2_Final

B.41 2.4.2 System shall support flexible structuring of content that can be aligned to IRS.gov content governance process. System shall support initiatives such as create once, publish everywhere.

Taxonomy CMS Business Rqmts

V7_2_Final

B.42 2.4.3 System shall support ability to use interactive content components as nodes. An example is the use of an interactive form component, search component, or other service component.

Interactive

Components

CMS Business Rqmts

V7_2_Final

B.43 2.4.4 System shall provide flexible page level requirements to support

IRS business processes for structured content, responsive design, and page level management.

Content Types CMS Business Rqmts

V7_2_Final

B.44 2.4.5 System shall have the ability to reuse nodes. Content Management CMS Business Rqmts

V7_2_Final

B.45 2.4.6 System shall support ability to have reusable content "widgets" or elements.

Content Management CMS Business Rqmts

V7_2_Final

B.46 2.4.7 System shall support reuse of navigation links. Navigation CMS Business Rqmts

V7_2_Final

B.47 2.4.8 System architecture shall support ability for automated update or removal of content, where feasible, and support cascading deletion operations.

Content Management CMS Business Rqmts

V7_2_Final

B.48 2.4.9 System shall support review processes for content so that content can be audited and certified using rolling inventory audits.

Audit CMS Business Rqmts

B.49 2.5.1 System shall provide ability to capture, access and extend multi-faceted metadata at each stage of the content development lifecycle on pages and with assets.

Metadata CMS Business Rqmts

V7_2_Final

B.50 2.5.2 System shall support the ability to create, read and update system generated and non-system generated metadata used to describe content types at each stage of the content development lifecycle.

Metadata should be automated, system generated to the extent possible.

Metadata CMS Business Rqmts

V7_2_Final

B.51 2.5.3 System shall provide flexibility for the integration of multiple, dynamic, version controlled information architecture layers.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.52 2.5.4 System shall provide flexibility for the integration of multiple, dynamic, version controlled semantic layers (taxonomy-driven).

Integration CMS Business Rqmts

V7_2_Final

B.53 2.5.5 System shall support the combination of CMS business rules and

CMS metadata model to execute CMS publishing routines in different combinations to different locales and delivery channels.

Publishing CMS Business Rqmts

V7_2_Final

B.54 2.6.1 System shall meet and comply with all federal accessibility guidelines. The current standard that must be complied with is

Section 508 of the Rehabilitation Act (which may be updated during this process to introduce new requirements that will likely mirror WCAG 2.0 (AA) accessibility guidelines.)

508 CMS Business Rqmts

V7_2_Final

B.55 2.6.2 System shall support all required accessibility standards by providing a compliant CMS user interface.

508 CMS Business Rqmts

V7_2_Final

B.56 2.6.3 Content that is produced from the system, for external users, shall support all required accessibility standards.

508 CMS Business Rqmts

V7_2_Final

B.57 2.7.1 System shall provide support for foreign language web content. Multilingual CMS Business Rqmts

V7_2_Final

B.58 2.7.2 System shall provide the ability to identify if a content item requires a translation and support the ability of IRS to synchronize

English and non-English versions of online content.

Multilingual CMS Business Rqmts

B.59 2.7.3 System shall support workflow functions associated with language translation and automate appropriate processes in the CMS

Multilingual CMS Business Rqmts

V7_2_Final

B.60 2.8.1 System shall provide CMS users the ability to preview content items prior to publishing, both in-context and out-of-context, as they will appear on the live site (WYSIWYG) using any device.

Preview CMS Business Rqmts

V7_2_Final

B.61 2.8.2 System shall provide in-context view, edit, add, and delete capability for page components within preview based on user permissions.

Content Types CMS Business Rqmts

V7_2_Final

B.62 3.1.1 System shall provide a CMS Web content repository that meets capacity, availability, performance, scalability and disaster recovery requirements.

Performance CMS Business Rqmts

V7_2_Final

B.63 3.2.1 System shall support ability of organization to maintain version control of published content in order to provide a historical record of changes to content that may pertain to legal requirements, legal review, or case law. Because content may be combined on a given "page," versioning should support page elements as well as the page itself where appropriate.

Versions CMS Business Rqmts

V7_2_Final

B.64 3.2.2 System shall store versions of content and maintain an audit log of content to provide a historical record of content changes that may pertain to legal requirements, legal review, or case law.

Versions CMS Business Rqmts

V7_2_Final

B.65 3.2.3 System shall provide ability to track multiple versions of content and compare historical versions along with the ability to identify changes to content and metadata.

Versions CMS Business Rqmts

V7_2_Final

B.66 3.2.4 System shall provide ability for CMS users or administrators to see what has been changed when comparing content versions.

Versions CMS Business Rqmts

V7_2_Final

B.67 3.2.5 System shall provide ability to revert back to and republish previous content versions.

Versions CMS Business Rqmts

B.68 3.2.6 System shall support intuitive editing, preview capabilities for content creation and have ability to restrict type of information entered based on user role.

Preview CMS Business Rqmts

V7_2_Final

B.69 3.3.1 System shall support backup operations that allow complete synchronization of database and static file assets.

Infrastructure CMS Business Rqmts

V7_2_Final

B.70 3.3.2 System shall support workflow for managing historical content. Publishing CMS Business Rqmts

V7_2_Final

B.71 4.1.1 System shall enable automatic, manual or scheduled near real-time publishing and un-publishing, archiving, and retention or deletion of content as determined by business rules.

Publishing CMS Business Rqmts

V7_2_Final

B.72 4.2.1 System staging/preview platform shall display published content for validation by IRS CMS system administrators prior to the content being presented via a content delivery network.

Preview CMS Business Rqmts

V7_2_Final

B.73 5.1.1 System shall ensure that IRS web properties are continuously available to site visitors without latency in providing timely information.

Publishing CMS Business Rqmts

V7_2_Final

B.74 5.1.2 System shall provide access to standardized reporting and performance monitoring to ensure adequate page response times, and reporting of pages that fall below identified performance thresholds.

Reporting CMS Business Rqmts

V7_2_Final

B.75 5.1.3 System shall support the ability to display published pages to site visitors

Presentation CMS Business Rqmts

V7_2_Final

B.76 5.1.4 Content published from the CMS should be standards compliant and compatible with browsers and devices used by 98% of

IRS.gov visitors

Browsers CMS Business Rqmts

V7_2_Final

B.77 5.1.5 HTML5 and XHTML shall meet W3C or the most current markup standards and be backwards compatible with browsers and devices used by 98% of IRS.gov visitors.

Browsers CMS Business Rqmts

V7_2_Final

B.78 5.1.6 System shall be scalable to ensure seamless performance as traffic increases.

Performance CMS Business Rqmts

B.79 5.1.7 System shall display appropriate exit disclaimers based on IRS business rules.

Exit Disclaimers CMS Business Rqmts

V7_2_Final

B.80 5.1.8 System shall allow creation of customized error messages for site visitors.

Error Handling CMS Business Rqmts

V7_2_Final

B.81 5.2.1 System shall support responsive design web experience that allows CMS to create content once and publish everywhere (e.g.

COPE) regardless of device or browser type. (e.g. MOBILE)

Responsive Design CMS Business Rqmts

V7_2_Final

B.82 5.3.2 System shall support the ability to generate page components, such as headers and footers, that can be populated on pages developed outside the CMS (i.e., applications).

Presentation CMS Business Rqmts

V7_2_Final

B.83 5.4.2 System shall integrate with required existing IRS applications. Integration CMS Business Rqmts

V7_2_Final

B.84 5.4.3 System shall support ability to push content through secure standard protocols or pull content using secure standard protocols.

Security CMS Business Rqmts

V7_2_Final

B.85 5.4.4 System shall support capability to install tools or application components that allow for future integration of new tools.

Integration CMS Business Rqmts

V7_2_Final

B.86 5.4.5 System shall support the installation of social media integration tools.

Integration CMS Business Rqmts

V7_2_Final

B.87 5.4.7 System shall integrate with the DigitalGov Search API. Search CMS Business Rqmts

V7_2_Final

B.88 5.4.8 System shall comply with Executive Order 13571 to provide the ability to survey customers to establish and monitor service benchmarks.

Survey CMS Business Rqmts

V7_2_Final

B.89 C4 User guides and in context user documentation, and the ability to update the system user guides and documentation in a standardized way shall be provided.

Training CMS Business Rqmts

V7_2_Final

B.90 C5 User acceptance testing shall occur iteratively throughout the development process to allow for corrective action prior to CMS delivery.

Implementation CMS Business Rqmts

B.91 C-64 System shall allow XML Bulk Content to be managed in the CMS App - XMLBC XMLBC/SFBU

B.92 C8 System performance and end-to-end monitoring shall be in place to measure all SLA requirements.

SLA CMS Business Rqmts

V7_2_Final

B.93 C9 Contractor shall provide train the trainer CMS training and training materials which ensure the IRS is capable of using all functionality provided within the CMS.

Training CMS Business Rqmts

V7_2_Final

B.94 E1 System shall provide multiple environments to support the needs of the IRS including at least production, performance, development, training, disaster recovery and testing.

Environments CMS Business Rqmts

V7_2_Final

B.95 E2 System shall be scalable to accommodate increases/decreases in traffic, capacity and utilization.

Scalability CMS Business Rqmts

V7_2_Final

B.96 E3 System shall support near real-time and scheduled content synchronizations between environments.

Environments CMS Business Rqmts

V7_2_Final

B.97 E4 System shall support multiple sites including domains, subdomains or sites.

Hosting CMS Business Rqmts

V7_2_Final

B.98 E5 Environments shall have quality and change control processes/technology in place to enable coordination with IRS.

Quality/Change

Control

CMS Business Rqmts

V7_2_Final

B.99 H121 System shall provide the URL normalization functionality URL Normalization CMS Enhancements

B.100 H20 The CMS technology platform shall provide the following content and infrastructure features: Use pre-packaged connectors to import and export IRS content and data systems that provide source content in XML and PDF formats for aggregated content views on the new IRS.gov.

Import/Export TO2 PWS 2.1.2.9b

B.101 H21 The CMS shall provide the capability to search the CMS content repository.

Search TO2 PWS 2.1.2.9c

B.102 H22 The CMS shall provide formatted content to other IRS systems, in a usable format, via either a central repository or a specific data flow to those systems.

Import/Export TO2 PWS 2.1.2.9d

B.103 H23 The CMS shall integrate with the IRS Enterprise Identifier. Permissions TO2 PWS 2.1.2.9e

B.104 H24 The CMS shall generate e-mail system alerts to IRS employees as configured within the CMS.

Notifications TO2 PWS 2.1.2.9f

B.105 H25 The CMS shall allow IRS administrators to add, view, modify or delete content administrators using the CMS interface.

Permissions TO2 PWS 2.1.2.9g

B.106 H26 The CMS shall provide the capability to manage links to external sites and, to the extent possible, alert content managers when external links become broken.

References TO2 PWS 2.1.2.9h

B.107 H30 The Contractor will ensure that high priority content changes can be made whenever the connectivity between the IRS network infrastructure and the CMS is not available.

Publishing TO2 PWS 2.1.2.9l

B.108 H31 The Contractor shall enable content reuse from content created within the CMS or imported from an external source.

Content Management TO2 PWS 2.1.2.10

B.109 H32 The system shall support the creation and management of granular content types, as specified in the IRS information model standard. For example, the system shall provide the capability to manage granular types not only at the “object” level (e.g., a news article) but at the content element level (e.g., a definition field).

Content Management TO2 PWS 2.1.2.10a

B.110 H34 System shall enable the creation of compound documents, information maps, and Web pages out of the content units specified in the information model.

Content Management TO2 PWS 2.1.2.10c

B.111 H41 System shall allow an entire document or object, as a whole, to be repurposed into another format.

Transformation TO2 PWS 2.1.2.10e

B.112 H43 System shall enable templates to auto-populate specified metadata fields based on user role, content type, or other business rules.

CMS User Experience TO2 PWS 2.1.2.11a

B.113 H44 System shall support networked and hierarchical taxonomies as controlled vocabularies and aggregate data up to different levels of the taxonomy

Taxonomy TO2 PWS 2.1.2.11b

B.114 H45 System shall allow for management of, and updates to, controlled vocabularies for each field, either within the content management system or through the ingestion of a file managed in an external tool.

Taxonomy TO2 PWS 2.1.2.11c

B.115 H47 System shall provide the capability to integrate a third-party tool that helps facilitate defining meta tags.

Metadata TO2 PWS 2.1.2.11e

B.116 H49 System shall support English, Spanish, Chinese, Vietnamese, Korean and Russian content.

Multilingual TO2 PWS 2.1.2.12a

B.117 H50 The system shall associate all versions of the same object in different languages to the authoritative source content in English.

Multilingual TO2 PWS 2.1.2.12b

B.118 H51 The system shall notify content owners and managers when the source content is modified and updated.

Multilingual TO2 PWS 2.1.2.12c

B.119 H52 The system shall provide the Digital Asset Management strategies, technologies, and processes required to deliver dynamic digital assets in the new IRS Web environment. The CMS shall provide the Ability to capture, store, retrieve, approve, distribute, transmit and manage rich multi-media content such as video, film, audio, large images, and graphics.

Media Assets TO2 PWS 2.1.2.13

B.120 H55 The system shall support utilities for IRS to develop and post dynamic, interactive information to the new IRS Web environment

(e.g., simple business rules-driven decision support tools for Web visitors).

Publishing TO2 PWS 2.1.2.15

B.121 H56 The system shall support utilities that leverage re-usable frameworks and solutions to support multiple applications with similar functionality.

Content Management TO2 PWS 2.1.2.15a

B.122 H57 The system shall allow for connections to an external content repository for viewing, selecting, and ingesting content into the

CMS for management as CMS objects.

Import/Export TO2 PWS 2.1.2.16a

B.123 H58 The system shall accommodate the expected 20% annual growth rate for content objects within the scope of CMS management.

Scalability TO2 PWS 2.1.2.16b

B.124 H59 The system shall allow for separate content repositories within

CMS to support public content.

Content Management TO2 PWS 2.1.2.16c

B.125 H63 The system shall support versioning and tracking capabilities of the IRS Website to enable a roll-back of the site to a given date and time for back-up/restore situations and to provide evidence of content that existed on the site for liability purposes.

Content Management TO2 PWS 2.1.2.16g

B.126 H65 The system will support a process for migrating content from desktop publishing packages such as Microsoft Word that optimizes the generated Hyper Text Markup Language (HTML) and appropriately applies design and layout requirements

Content Management TO2 PWS 2.1.2.17b

B.127 H66 The system shall perform a spell check for required manual text entry fields.

Spell Check TO2 PWS 2.1.2.17c

B.128 H67 The system shall provide advanced search on all content and metadata elements on ingested content.

Search TO2 PWS 2.1.2.17d

B.129 H70 The system shall provide formal validation of content ingested via

XML Document Type Definition or schema.

Content Management TO2 PWS 2.1.2.17g

B.130 H72 The system shall provide the IRS with the ability to monitor status and activity of content managers using the CMS.

Permissions TO2 PWS 2.1.2.18b

B.131 H73 The system shall provide the IRS with the ability to override standard workflow steps to expedite publishing of content when necessary.

Workflow TO2 PWS 2.1.2.18c

B.132 H76 The Contractor shall provide full details of any technology associated with the CMS and the application development environment, including:

a. operating system

b. application server

c. databases

d. other add-ons required to meet objectives.

Reporting TO2 PWS 2.1.2.19

B.133 H77 The Contractor shall provide train-the-trainer training and documentation to IRS.

Training TO2 PWS 2.1.2.20a

B.134 H79 The Contractor shall provide train-the-trainer training and support joint development of documentation with IRS that provides plain language, detailed, modular instructor and student guides.

Training TO2 PWS 2.1.2.20c

B.135 H80 The Contractor shall provide train-the-trainer training and support joint development of documentation with IRS that provides training modules that reflect content administration requirements as they relate to the structure and hierarchy of the CMS.

Training TO2 PWS 2.1.2.20d

B.136 H81 The system shall provide Records Retention capabilities that satisfy requirements of the e-Gov Act of 2002.

Records Retention TO2 PWS 2.1.2.21

B.137 H83 The Contractor shall configure the CMS and all of the associated development and staging platforms to meet IRS requirements

Migration TO2 PWS 2.2.2.2

B.138 H84 The Contractor shall migrate existing content to the new solution based on design, layout, information architecture, and other configuration requirements, including navigation layers, headings, associated images, tables, and supporting documents (e.g., PDFs).

Migration TO2 PWS 2.2.2.3

B.139 H85 The system shall support the application of changes during the transition from the IRS information architecture standards to support content structure, organization, tagging; page display;

navigation; and search and demonstrate that all features operate as required prior to implementation of the new IRS Website into production.

Migration TO2 PWS 2.2.2.4

B.140 H87 The Contractor shall provide information and documentation related to the capability to help facilitate defining meta tags.

Metadata TO2 PWS 2.2.2.6

B.141 H88 The Contractor shall complete all content management items on the Transition Phase Operational Readiness checklist and receive

IRS approval to transition into production status.

Migration TO2 PWS 2.2.2.7

B.142 M1 System shall provide the ability to reuse existing content and migrate content from legacy systems with support for automation and transformation of data where required as well as bulk transfer of files.

Migration CMS Business Rqmts

V7_2_Final

B.143 M4 System shall provide tools and processes for seamless migration and minimal downtime.

Migration CMS Business Rqmts

V7_2_Final

B.144 P1 System shall not store any Personally Identifiable Information (PII) of general (unauthenticated) website visitors and is subject to an

IRS Privacy Impact Assessment.

Security CMS Business Rqmts

V7_2_Final

B.145 Portal H23 The system shall accommodate search, language selection, role selection (audience identification) located on the top right of each page. Required languages are English, Spanish, Chinese, Korean, Russian, and Vietnamese.

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.146 Portal H24 The system shall accommodate the section that defines the IRS brand that includes name “Internal Revenue Service” and tagline.

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.147 Portal H25 The system shall accommodate the section that defines the

Website’s main navigation area.

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.148 Portal H26 The system shall accommodate:

Various components/areas that highlight different content and information on IRS.gov. or

Combination of components, text and form fields.

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.149 Portal H27 The system shall accommodate the section located on the bottom of every page that contains helpful links for users.

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.150 Portal H28 The system shall accommodate the following page elements:

Navigation Structure

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.151 Portal H34 The system shall support the following page element: Image element

Media Assets TO3 PWS 2.1.1.2, 2.1.1.6

B.152 Portal H36 The system shall support the following page element: Application

(used for embedding application code within IRS.gov layout and navigation structure

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.153 Portal H37 The system shall support the following page element: Poll element

(one-question pulse gatherer), which may be incorporated into a feature or highlight element. Will send responses to database and allow for displaying results within poll element

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.154 Portal H38 The system shall support the following page element: Survey element (multi-question opinion gatherer), which may be incorporated into the main body. Will send responses to database and allow for displaying reports via report element

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.155 Portal H39 The system shall support the following page element: Report element (used to aggregate and display data)

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.156 Portal H4 The system shall support embedding applications for display purposes (at the very least) in order to provide a consistent experience for site visitors.

Presentation TO3 PWS 2.1.1.1

B.157 Portal H40 The system shall support the following page elements: Frequently

Asked Questions (FAQ) (used to generate list of FAQs).

Presentation TO3 PWS 2.1.1.2, 2.1.1.6

B.158 Portal H51 The system shall support the IRS ability to make modifications to the presentation layer (instructions, form field labels, etc.).

Presentation TO3 PWS 2.1.3.1

B.159 Portal H57 The system shall include a navigation structure that reflects the hierarchy of the new IRS.gov information architecture model.

Presentation TO3 PWS 2.1.5.4

B.160 Portal H6 The system shall support the same functionality and features as the current site.

Migration TO3 PWS 2.1.1.1

B.161 Portal H7 The Contractor shall incorporate any required changes based on user experience evaluation throughout the development of the

Web presentation design as consistent with the program’s software development lifecycle methodology standards.

Taxpayer Experience TO3 PWS 2.1.1.1

B.162 S1 The System shall provide a secure environment that complies with all required federal laws, rules, regulations, standards and IRS specific security requirements as specified herein and in accordance with contract attachments; ensure the necessary redundancy, resiliency, and contingency capabilities to ensure service availability that meets IRS current and future needs.

Security CMS Business Rqmts

V7_2_Final

B.163 S2 The System shall provide security controls that protect all services, information, infrastructure, and information processing resources against threats, attacks, or failures of systems.

Security CMS Business Rqmts

V7_2_Final

B.164 S3 The System shall provide security controls required to protect

Federal information and information systems from unauthorized access, use, disclosure, disruption, modification, or destruction in order to provide confidentiality, integrity, and availability in accordance with the Federal Information Security Management

Act.

Security CMS Business Rqmts

V7_2_Final

B.165 S4 The System shall support the ability to integrate with IRS security systems that are external to the CMS.

Security CMS Business Rqmts

V7_2_Final

B.166 S5 The System shall support and meet IRS security requirements as defined in the Security Reusable Program Level Requirements.

Security CMS Business Rqmts

V7_2_Final

B.167 S6 The system shall support delivery of content and other interactions as defined in OMB Policy M-15-13, Policy to Require

Secure Connections across Federal Websites and Web Services.

Security CMS Business Rqmts

V7_2_Final

B.168 SA1 The System shall provide features, functionality and capabilities that meet Federal Enterprise Architecture Framework (FEAF), Event Driven Architecture (EDA), industry performance and interoperability standards, and applicable industry best practices, supporting multiple sites and parent domain URLs. System shall have flexibility and modular base to integrate with other systems.

Integration CMS Business Rqmts

B.169 SA2 The System shall support application component architecture for extending functionality.

Information

Architecture

CMS Business Rqmts

V7_2_Final

B.170 SA3 The System shall support federal guidelines for open CMS systems.

Open Source CMS Business Rqmts

V7_2_Final

B.171 SA4 The System shall be platform-agnostic. Hosting CMS Business Rqmts

V7_2_Final

B.172 SA6 The System shall be extendible through the use of third-party-developed components (including COTS and GOTS).

Integration CMS Business Rqmts

V7_2_Final

B.173 SA7 The System shall allow IRS to implement and configure business rules, in near real-time, for automated actions based on system events.

Permissions CMS Business Rqmts

V7_2_Final

B.174 SA8 The System shall integrate with other IRS web platforms and applications without any loss of functionality to the external systems.

Integration CMS Business Rqmts

Req't ID Req't Description Business Category Requirement Source

C.1 System shall expose APIs for use by external systems API 7/27 RTM Review 2

C.2 System shall provide a reporting view to replace the 90-day unpublish report.

The view will include content that is about to expire within a specified timeframe, beginning 90 days.

App - 90 Day Unpublish

Report

Apps 1

C.3 System shall provide the report of expiring content based on user role and organization

App - 90 Day Unpublish

Report

7/22 IRS Email

C.4 System shall allow existing files to be overwritten for new or modified Static

Files manually

App - Static File Bulk

Upload

XMLBC/SFBU

C.5 System shall allow existing files to be overwritten for new or modified Static

Files through the Static File Bulk Upload process

App - Static File Bulk

Upload

XMLBC/SFBU

C.6 System shall allow XML Bulk Content to be managed in the CMS App - XMLBC XMLBC/SFBU

C.7 The system shall make the header and footer fragments available on a nightly basis for use by applications hosted externally to the CMS

Application Existing Functionality

C.8 System shall provide a flag that will allow specific content items to be marked historical

Content Management Pub Model 2

C.9 System shall default specific content entities to historical. Content Management Pub Model 2

C.10 System shall allow linking to any published and unpublished content items within WYSIWYG editor

Content Management Content Strategy 2

C.11 System shall require the revision log message for each new draft created for content for all content types

Content Management Pub Model 2

C.12 System shall provide links to the expiring content page in the email notification.

Content Management Pub Model 2

C.13 System shall allow content creator or editor to be transferred to another IRS

CMS user

Content Management Reporting/Analytics 2

C.14 System shall allow cloning of content during content authoring process Content Management 7/27 RTM Review 2

C.15 The system shall be able to perform automated migrations between non-production environments

Environments

C.16 System shall redirect broken links to a HTTP 403 and 404 search page Error Handling Pub Model 2

C.17 System shall follow IEP naming convention for environments Hosting Hosting 2

C.18 Sites shall be permissioned independently Hosting Hosting 2

C.19 The system will provide the capability to export the tax law QA content into

XML for retrieval

Import/Export Existing Functionality

C.20 The system shall provide IRS users with the development tools and platform to make modifications to the WCMS application.

IRS Development

C.21 The system shall provide remote workstation access to IRS to leverage the development tools

IRS Development

C.22 The solution shall leverage, and configure as necessary, the IEP operational tools for incident management, configuration management and log analysis.

IRS Development

C.23 For content migration, content publish, historical and unpublish dates will be maintained

Migration Pub Model

C.24 Current content organizations field will be used for initial build-out Migration Pub Model 1

C.25 System shall maintain content ownership when migrated into WCMS by mapping both content and users to organizations

Migration Reporting/Analytics 2

C.26 Comments pages will be built in WCMS as forms; they will maintain existing look and feel and functionality incorporating changes requested by IRS

Migration Apps

C.27 Generated Static File Links on the website will continue to point to the PDF Migration XMLBC/SFBU

C.28 URL redirects shall be implemented for the URL that will be changed due to

WCMS migration.(ex. Foreign language naming structure)

Migration Multilingual

C.29 The following OpenText content types or components (6 items) will be migrated to WCMS as Content Types: Free File Fillable Code, Glossary, IRS

Link, Standard, Tax Law Q, Content Lists

Migration Content Mapping

C.30 The following OpenText content types (7 items) will be migrated to WCMS as

Media Bundles: IRS Image, IRS Video, Bulk Static File, FIOA Static File, Newsroom Static File, Published Product Static File, Static File

Migration Content Mapping

C.31 The following OpenText content types (4 items) will be migrated to WCMS as

Blocks: Callout, Rotating Spotlight, Display Views, Smart/Content Lists

Migration Content Mapping

C.32 The system will be migrated to updated WCMS platform. Migration Hosting

C.33 As part of the migration, a minimum of three page templates will be developed: Standard Page Template, Tax Law QA Page Template, Free File

Fillable Code Page Template

Migration Content Mapping

C.34 As part of the WCMS migration, OpenText Display Views will be migrated into

Block Views with templates: Banner (all), Filing and Payment, Footer, Forms and Pubs, Free File Fillable List, Free File Fillable Popup, Global Navigation, Highlight/Feature, Hot Topics/Tools, News, Related Items, Right Vertical

Navigation, Rotating Spotlight, Social Media, Tax Law QA - Search -

Categories, Tax Law QA - Search (all)

Migration Content Mapping

C.35 System shall include a permission to allow multilingual content managers to only edit content, but not create from scratch

Multilingual Pub Model 4

C.36 System shall default to display English version of the content when other language versions are not available

Multilingual Multilingual

C.37 System shall use the industry standard naming convention for multilingual content (Spanish, English, Russian, Chinese, Vietnamese, Korean)

Multilingual Multilingual

C.38 System shall translate site visitor-facing elements. Multilingual 7/22 IRS Email

C.39 System shall provide a taxonomy-driven language block that will be placed on pages with translated versions of content

Multilingual 7/27 RTM Review

C.40 System shall add a link to the language landing page selector pointing back to the English homepage

Multilingual 7/27 RTM Review

C.41 System shall allow linking to translated version of the content Multilingual Multilingual

C.42 System shall provide a flag to indicate that the English content has been changed and other translations are outdated.

Multilingual 7/22 IRS Email

C.43 System shall notify translation content owners when the translation outdated flag is checked for the updated version via email.

Multilingual 7/22 IRS Email

C.44 System shall include either the Comment field or a separate field tied to the alert that would allow the user modifying the English content to describe the changes they made in the notification.

Multilingual 7/22 IRS Email

C.45 System shall be capable to provide an email notification to CMS users notifying of content that has met the threshold to expire.

Notifications Pub Model 2, 7/22 IRS

Email

C.46 System shall provide CMS users the ability to select recipient of email notifications

Notifications 7/22 IRS Email

C.47 System shall provide CMS users the ability to opt-in to receive email notifications for content they select.

Notifications 7/27 RTM Review

C.48 System shall reroute emails in the lower environments to specified email addresses.

Notifications Pub Model 2

C.49 System shall send an email notification to users when their password is about to expire

Notifications 7/27 RTM Review 2

C.50 System shall provide a notification upon login to users when their password is about to expire

Notifications 7/27 RTM Review 2

C.51 System shall provide a block to allow users to add to cms-managed application pages to notify site visitors of outages

Notifications 7/27 RTM Review 2

C.52 System shall allow content to belong to multiple organizations in the organization field.

Permissions Pub Model 1

C.53 System shall allow users to belong to multiple organizations . Permissions Requirements Review 1

C.54 System shall allow specific users to edit content across all organizations. Permissions Requirements Review 1

C.55 System shall only allow users to tag content to an organization that they belong to.

Permissions Pub Model 1

C.56 System shall only allow content to be modified by users within organization that the content belongs to.

Permissions Pub Model 1

C.57 System shall allow CMS Administrator to check for site-wide broken links. Permissions Pub Model 2

C.58 System shall allow the IRS to manage and create roles and organizations Permissions 7/27 RTM Review

C.59 The system shall give direct control to designated OLS staff to add/modify/view/delete CMS editor accounts and permissions

Permissions CMS Enhancement

C.60 System shall define dynamic placement of components within templates Presentation Content Strategy 1

C.61 The system shall allow IRS to design and specify page layouts. Presentation 7/28 RTM Review

C.62 System shall enable manual overrides of the placement of content items in components/blocks at the field level.

Presentation Content Strategy 1

C.63 System shall provide capability to visually indicate historical content to the end users (taxpayers) on the website

Presentation Pub Model 2

C.64 The "Like", "Share" (Add This)" and Print buttons will continue to be included on content pages

Presentation Existing Functionality

C.65 System shall provide an accordion style list. Presentation 7/27 RTM Review 2

C.66 System shall enable automatic publishing for content set to publish at a specific date and time.

Publishing Pub Model 4

C.67 System shall allow authenticated users to view unpublished content Publishing Pub Model 4

C.68 System shall move content to moderation state Archived when it expires. Publishing Model Pub Model 1

C.69 System shall default specified content that are not flagged historical to expire in 1 year after being published.

Publishing Model Pub Model 1

C.70 System shall unpublish content that is in moderation state Archived. Publishing Model Pub Model 1

C.71 System shall provide an "intentionally unpublished" state for content that is manually unpublished by IRS

Publishing Model 7/28 RTM Review

C.72 System shall enable permissioning to restrict ability to mark content as historical at the role level.

Publishing Model Pub Model 2

C.73 System shall allow historical content to remain published without expiring. Publishing Model Pub Model 2

C.74 System shall archive content that is not re-validated before expiration date Publishing Model Pub Model 2

C.75 System shall allow users to view all redirects and FURLs for a page Redirects 7/27 RTM Review 2

C.76 System shall alert users if a broken link is present upon save. References Pub Model 2

C.77 System shall allow content to be queried by defined fields Reporting Reporting/Analytics 1

C.78 System shall allow export of reports generated using pre defined exposed filters in production. Available export format are CSV, excel, XML, JSON, PDF.

Reporting Reporting/Analytics 1

C.79 System shall provide a paginated view that will allow content managers to view content by organization

Reporting Reporting/Analytics 1

C.80 System shall provide a paginated view that will allow content managers to view all the content by user

Reporting Reporting/Analytics 1

C.81 System shall provide a paginated view that will allow content managers to view all content that is about to be unpublished within a specified range

Reporting Reporting/Analytics 1

C.82 System shall allow CMS administrators to run a report of CMS user activity Reporting Reporting/Analytics 1

C.83 System shall provide a link to the expiring content views page in the notification by organization upon login for content that will expire beginning

14 days as a reminder.

Reporting Pub Model 3

C.84 The download event code (Auto tracker) will continue to be included on all pages to send event traffic to Google Analytics

Reporting Existing Functionality

C.85 System shall use email addresses that are not attributable to a specific individual for CMS user accounts

Security Security

C.86 System shall use CMS user's real name (first name, last name. If users share the same name, system will append number to the end) while tagging user actions in the system e.g. revision logs, workflows

Security Security

C.87 System shall provide ability to check SEO during content authoring process SEO 7/27 RTM Review 2

C.88 The Foresee ASCI Survey code will be migrated to the WCMS instance and referenced from each page

Survey Existing Functionality

C.89 System shall add descriptions, keywords as metatags from taxonomy for search engine optimization (SEO)

Taxonomy Taxonomy 1

C.90 System shall allow newly created vocabulary to be used for content tagging. Taxonomy Taxonomy 2

C.91 System shall allow multiple taxonomy groupings for content instances. Taxonomy Content Strategy 2

C.92 System shall display a field to allow content area classification for each content type and media entity

Taxonomy Content Strategy 2

C.93 System shall create new vocabulary and taxonomy terms based on current

Channels except UAC channel.

Taxonomy Taxonomy 3

C.94 System shall create new vocabulary and taxonomy terms based on folder structure for content in UAC channel.

Taxonomy Taxonomy 3

C.95 System shall enable creating relationships between terms and different vocabularies.

Taxonomy Taxonomy 2

C.96 System shall work with IRS COE environment including browser. Environments IRS RTM Feedback

C.97 System shall have unique domain name for every environment. Environments IRS RTM Feedback

C.98 System shall ensure IRS.gov sub-sites not impact the support, enhancements or operations of IRS.gov.

IRS Sub-sites IRS RTM Feedback

C.99 System shall ensure IRS.gov and all sub-sites have site-specific functionality. IRS Sub-sites IRS RTM Feedback

C.100 System shall ensure IRS.gov and all sub-sites have site-specific configuration. IRS Sub-sites IRS RTM Feedback

C.101 System shall ensure each site have separate permissions. IRS Sub-sites IRS RTM Feedback

C.102 System shall ensure that IRS.gov remains uncompromised in the event of a sub-site outage, bug or security issue.

IRS Sub-sites IRS RTM Feedback

C.103 System shall enable tabbed user interface page elements to be added by the

IRS.

Presentation IRS RTM Feedback

C.104 System shall provide long term custom report of CMS user activity. Reporting 8/30: RTM Review

C.105 System will allow for data entry fields to have a challenge-response to prevent spam.

Security 8/30: RTM Review

C.106 System shall secure all published content made available to the public via

HTTPS.

Security 8/30: RTM Review

C.107 The system shall maintain the current static file location under /pub/ for the transition to WCMS.

SFBU 9/1 RTM Review

Comments/Notes Tab B Req X-Ref

B.87

IRS to define the timeframe B.8

8/30: Example: report shows number of nodes expiring on a day by day and month by month basis

B.31

This will require customization.

8/29: Published Date in transaction files will be mapped to Posting Date that Picklist will pick up.

B.160

9/1: Static files…