June 22, 2016

CMS Implementation – Business and functional requirements The scope of these requirements is relegated to the implementation of SiteFinity and is focused on items that will go-live on January 1, 2017. Strategic Priorities The following strategic priorities were identified by Chancellors Horrell and Elliman and accepted by the IT Cabinet on June 13, 2016. The CMS implementation will be co-led by OIT and UCOMM. OIT co-chair representative is Eric Howell and the UCOMM co-chair representative is Karen Klimczak. The user experience is the priority for the CMS implementation. For CU Denver: 1. 2. 3. 4. 5. 6.

The number one priority is prospective students and driving applications, admissions and enrollment. The second priority is current students and ensuring retention and persistence. Provide parents with information to support prospective and current students. Other priorities include transfer student information, information for business and community influentials to enhance opportunities for partnerships, information and services for alumni as well as potential donors. Provide easy access to research activities and information. Represent faculty and staff on the site.

For CU Anschutz Medical Campus: 1. 2. 3. 4. 5. 6.

The number one priority is current students and ensuring retention and persistence. The second priority is prospective students and driving applications, admissions and enrollment. A third priority is the ability to find a doctor and medical services and easy connection to our affiliates and clinical partners. A fourth priority is information and resources for potential donors. A fifth priority is the ability to provide easy access to research activities and information. Other priorities include transfer student information, information for business and community influentials to enhance opportunities for partnerships, information and services for alumni and potential donors, and promoting the destination healthcare concept.

An integrated experience is considered important as well as the ability to easily locate each campus. Easy navigability to priority components is critical. The web professionals group and the CMS advisory committee in conjunction with OIT and UCOMM will explore how to further ensure the easy accessibility to both campuses for users. This may include creating more overt cues from ucdenver.edu to the Anschutz homepage, bifurcating ucdenver.edu, or other potential solutions. Discussion will continue around the bifurcated front page in the weeks ahead as there has been a recent effort to focus the UCDENVER.EDU main page on CU Denver. The following requirements are not in priority order. Input from the web professionals group and the CMS advisory committee will inform importance and inclusion in scope.

CMS Implementation – Business and functional requirements | June 22, 2016

Business Requirements Req #

Business-Level Requirements

Description

BR1

Mobile first and functional across devices

Priority given to mobile technical requirements. Our target audience (1428 year olds at CU Denver, identify relevant age group for CU Anschutz) consists of heavy mobile users. The site needs to be responsive to these devices, including disability assistance.

BR2

Serve prospective students

The new site will focus on serving prospective students/families by driving applications, admissions, transfer opportunities and enrollment.

BR3

Support retention and persistence of students

The new site will focus on providing currents students/families the information and ability to locate the university resources they need to succeed academically and personally, including Canvas, email and other relevant technologies.

BR4

Serve faculty and staff

The site provide faculty and staff the resources to teach, research, work and communicate with internal and external constituents.

BR5

Serve donors and alumni

Easily convey information to enhance giving opportunities and relationships with alumni and donors.

BR6

Streamlined & personalized content

Content needs to be streamlined and personalized based on the visitor’s location. Also it must shorten the path users need to use to find information, be better organized with fewer clicks needed.

BR7

Prospective students need to be able to easily apply for admission

Site must make our primary calls to action (e.g. apply, visit us, tour, get info, enroll, etc.) more persistent and prominent on the site.

BR8

Information should be focused on the end user

User experience is a priority and the information users search for and find should meet their intended purpose.

BR9

Provide news and information

The site extends the content contained in the CU Denver and CU Anschutz Today blogs (http://cudenvertoday.org; http://cuanschutztoday.org/) by incorporating it throughout the site.

BR10

Make all site content easy to find

Combine search responses from the current SharePoint 2010 and soon to be implemented SiteFinity CMS to provide consistent end user experience.

BR11

Ease of content update

CU Denver and CU Anschutz will use the Sitefinity content management system (CMS) to manage page templates and website content. User testing of these tools will inform their development.

BR12

External system communication

Link into relevant portals and content outside of the SiteFinity internet site. Examples include Canvas, webmail and single-sign-on types of items.

CMS Implementation – Business and functional requirements | June 22, 2016

BR13

Show site usage and performance

Through the use of analytical tools, assess site performance in the areas of content relevance/quality and usability.

BR14

Serve patients

Easily find a doctor and medical services and easy connection to our affiliates and clinical partners

BR15

Serve researchers

Provide easy access to research activities and information.

BR16

Serve business and community members

Easily convey information for business and community influentials to enhance opportunities for partnerships, research, student hiring and tech transfer.

Functional Requirements Category: Req #

BR#

In Scope X

Description FR1

Personalize content for the end user

5

FR2

Degree program list

2, 3

FR3

News and events

9

X

FR4

Calendar

5&9

X

FR5

Site search

10, 14

X

FR6

Accessibility

1

X

FR7

Increase site performance

1

X

FR8

Creation of the customer journey for prospective students

2, 7

X

FR9

Make finding campus locations easy

10

X

FR10

Accurate single source tuition tables

8

X

FR11

Easy to find admissions information for parents and the community

4

X

FR12

Easy access to relevant topics like internships, summer courses and housing opportunities for CU Denver. Each campus will have different relevant topics in this functional requirement.

10

X

FR13

Represent transfer opportunities for CU Denver

2

X

CMS Implementation – Business and functional requirements | June 22, 2016

Out of Scope

X

Functional Requirements Category: Req #

BR# Description

FR14

In Scope

Represent institutional statistics – display statistics in a dynamic fashion which is data driven Curated social media content and ability to share published content directly with social media platforms

6 12

X

FR16

Faculty content type

3

X

FR17

Easy integration with our portals for various information like CUSIS information – Integration with other digital properties/services

12

FR18

Uniform/unified look and feel throughout the site

7, 1, 2, 5

X

FR19

Easy to use interface and navigation

2, 3, 5, 10, 14, 15, 16

X

FR20

Keep user interface effective, test during development

1

X

FR21

Show users what we want them to see on any given page and follow best practices in this area – will likely entail permissioning adjustments

11

X

FR22

Control page structure available to customers with preset page layouts

11

X

FR23

Modify editor controls for content users

11

X

FR24

Utilize a reusable content library

11

X

FR25

Keep content fresh by prompting users for content updates as well as utilize training as in FR29

9

X

FR26

Allow for easy rollup of content onto pages with dynamic section summaries

11

X

FR27

Track analytics for site performance in relation to marketing

13

X

FR28

Track analytics for site performance in relation to usability

13

X

FR29

Provide training for SiteFinity and leverage Lynda.com in areas like copy development, photography and video

11

X

FR30

Support easy to create forms

11

X

FR31

Ability to adjust permissions centrally as needed

11

X

FR32

Provide easy access to research activities and information

15

X

FR15

CMS Implementation – Business and functional requirements | June 22, 2016

Out of Scope X X

X

Functional Requirements Category: Req #

BR#

In Scope

Description

Out of Scope

FR33

Set up pre-requisite training modules before access to the site is given to users

9

X

FR34

Implement CMS SEO tools to boost site visibility

10

X

FR35

Video structured content for video embeds, tracking and mobile views

8

X

FR36

Employee directory – pull content from the directory to find people in the institution within one search source

10

X

FR37

Blog functionality

3

X

FR38

Sitewide Google analytics

13

X

FR39

Tag manager or pixel management

13

FR40

Integrate/connect with WebDam photo management system

11

FR41

Email from the CMS while adhering to CANSPAM legislation

FR42

Courses and class lists pulled from source system for use as dynamic content

CMS Implementation – Business and functional requirements | June 22, 2016

X X

X