VON Caregiver Portal System Requirements Specification

Transcription

1 VON Caregiver Portal Phase Two Version 2.3 Prepared for VON Canada by Navantis Inc. August 15, 2008

2 Document History Date Author Description of Change Version 3 April 2008 Mariana Buzu Document created in outline form April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Updates to the document April 2008 Mariana Buzu Included the templates, accessibility section, wireframes and annotations created by Bryce. 1.0 Updates to the document. 18 April 2008 Mariana Buzu Updated the wireframes for Homepage and Alerts. 1.1 Added a data validation table for Alerts UC. Updates per conference call discussion. 21 April 2008 VON Team Reviewed and revised the SRS April 2008 Mariana Buzu Updated the SRS April 2008 Mariana Buzu Updated the SRS. 1.3 Inserted UI designs. Change the date of when the French content is due to May 23, Added a requirement to turn the Audit Log on. Added a Sign Off page. Removed the UI Design illustrations. 2

3 Date Author Description of Change Version 24 April 2008 VON Team Reviewed and revised the SRS April 2008 Mariana Buzu Accepted all the changes April 2008 Mariana Buzu Updated the Sign Up page to allow users to use either their address or name/nickname as a username. 1.4 Updated the My Site page to allow users to delete recipients. Update Profile use case: Updated the wireframe. Added an alternative flow of events Delete a Recipient to the Update Profile use case. Updated the values for the I have cared for this person since dropdown. Contact Us and Ask our Experts use cases: Added a column for the French address. Expert Blog: Added a note that all the blogs will be displayed on one page and categorized by bloger 16 May 2008 Mariana Buzu Discussion Boards section: Added a screenshot t hat shows the built in functionality for scheduling alerts. 1.5 Sign up for alerts UC: Slight changes to the Data Validation table. Updated the validation requirement for the password field. 18 July 2008 Milton Howe Enter details for Phase July 2008 Milton Howe Changes following customer feedback August 2008 Milton Howe Updates to correct inconsistencies with implementation 15 August 2008 Milton Howe Update placeholder content in Caregiver Journal Section

4 Contents 1 Introduction Solution Vision Business Objectives Project Implementation About This Document Purpose of Document Intended Audience Requirements Documentation Approach System Features Use Case Model Actors, Security and Permissions Actors User Access Permissions Workflow Content Approval Workflow Branding Guidelines Interface Design Look and Feel Master Pages, Layouts, Web Part Zones and Navigation Content for the Caregiver Portal Metadata Architecture Functional Pages Sign Up For A User Account Login Reset Forgotten Password Change Password This Page Update Profile Contact Us Ask Our Experts Respond to a Survey Sign Up for Alerts Generic Templates SharePoint Web Content Management (WCM) Pages Printer Friendly

5 14.2 Font Size Control RSS Feed What s New Calendar Related Links Unique for You/Links Homepage Simple Search, Advanced Search and Search Results Expert Blog FAQ Community Resources My Site Discussion Board Caregiver Journal Templates & Forms Administration Features Disable Inactive Users Temporarily Disable the Portal Application Reports Web Analytics SharePoint Out-of-the-Box Reports Audit Logs Track Changes Made to Content Pages Statistics About Registered Users Learning Module Help Non Functional Requirements Technologies to be used Multi-Language Variations (English and French) Accessibility Checklist and Notes Screen Resolution Minimum Browser Support Friendly URLs Performance Scalability Appendix Accessibility Remediation Future Features Document Approval

6 Table of Figures Figure 1 - Use Case Model Figure 2 Content Approval Workflow Figure 3 Standards Cover Figure 4 Master Pages, Layouts, Web Part Zones and Navigation Figure 5 Sign Up/Login Figure 6 Workflow for Resetting a Forgotten Password Figure 7 - Forgot Your Password / Password Reset Pages Figure 8 - This Page Figure 9 - Profile Figure 10 Contact Us Figure 11 Ask Our Experts Figure 12 Survey Figure 13 Alerts Figure 14 Generic Template Figure 15 Generic Templates Figure 16 Calendar Figure 17 Event Details Figure 18 Homepage Figure 19 Simple Search with link to Advanced Search Page Figure 20 Search Results Figure 21 Advanced Search Figure 22 Blog Landing Page Figure 23 Blog Post Figure 24 FAQ Figure 25 Community Resources Figure 26 My Site Figure 27 My Site (including the Alert section) Figure 28 - Caregiver Journal List Fields Figure 29 - Caregiver Journal Categories Figure 30 - Cargeiver Journal - Home view Figure 31 - Caregiver Journal - Calendar View Figure 32 - Caregiver Journal - Feelings & Emotions View Figure 33 - Caregiver Journal - Categorical View Figure 34 - Caregiver Journal - Edit Entry Figure 35 - Caregiver Journal - Entry Tips List Edit Figure 36 - Caregiver Journal - Print-friendly View Figure 37 - Caregiver Journal - Delete Journal Figure 38- Downloadable Templates Library Columns

7 Figure 39 - Thumbnails Picture Library Figure 40 - Caregiver Self-Assessment Form Figure 41 - Discussion Board Figure 42 - Discussion Board Figure 43 - Discussion Board Figure 44 Web Analytics Report Figure 45 Usage Report Figure 46 Audit Settings Figure 47 Summary Data About Registered Users Figure 48 Detailed Data About Registered Users Figure 49 Help Figure 50 Quota Templates

8 1 Introduction 1.1 Solution Vision The goal of this project is to build an integrated health/community/services, web based, and community of practice support environment for family and friend caregivers across Canada. This is a new portal, designed to meet the needs of the caregivers. It will be an extension of the VON portal strategy. The VON Caregiver Portal will be a virtual space where all family and friend caregivers can get the information, resources and support systems they need to provide better quality care to their families/friends. It will also be a space where caregivers can seek support for themselves. The VON Caregiver Portal will be composed of two areas: 1. A Public Facing Website, which welcomes people and shares the vision of the VON Caregiver Portal. The website provides information about the portal and information about VON and allows new Caregivers to easily register so they can access the Registered User Extranet. The website is managed using a content management system which gives VON the power to easily maintain the information presented by the site. 2. A Registered User Extranet, which contains Caregiver information, Care Recipient Information, discussion boards, links for you, ask an expert and online learning tools. 1.2 Business Objectives The business objectives of the portal are to: 1. Improve the information available to caregivers of all ages, as they care for their family members and friends (community resources, clinical, financial, legal, physical and emotional); 2. Provide caregivers with resources to support them on their caregiving journey and to connect with the caregiver community; 3. Develop and provide a comprehensive, representative and accessible pan-canadian webspace for caregivers; and 4. Conduct an evaluation and provide evidence of the effectiveness of the portal. 1.3 Project Implementation The new portal will be based on the Microsoft SharePoint (MOSS) 2007 platform. The project is planned to be delivered in two phases: Phase 1 is scheduled to launch on June 11, 2008 and Phase 2 is scheduled to launch on 31 August,

9 2 About This Document 2.1 Purpose of Document The software requirements specifications document is intended to facilitate the establishment of a common understanding of the specifications of the system amongst the various project stakeholders: Analysis and Design Discipline Implementation Discipline Test Discipline The functional specifications document also serves as the primary artifact establishing the extended team s current understanding of the scope of the project. 2.2 Intended Audience The intended audience spans the entire spectrum of project stakeholders, among which are included the: Project Sponsor Steering Committee End User/UAT Community Software Architecture Team Software Development Team Quality Assurance Team 2.3 Requirements Documentation Approach The document is describing the functionality from an end-users perspective. The first section of this document covers the functional requirements while the second section covers the non-functional requirements. This document uses a few different approaches to capture system requirements. The documentation methods have been chosen to ensure that the necessary information is captured and presented for each page without overburdening the reader with information which is not useful. Each of the feature requirements within this document may contain the following sections: Screen mockup Requirements description Business Requirements (These will be referenced in the Business Requirements / Features Specification Matrix) User Workflow/Use Case (where necessary) Validation table Metadata table 9

10 In the case of out of the box functionality which is being used from existing software, (in our case Microsoft Office SharePoint Server 2007), use cases will not be created as they will be of no value since the functionally already exists and is well documented. The VON Canada Caregiver portal will have these types of pages: 1. Functional Pages these are pages which contain forms or other pieces of user functionality. An example of a Functional Page is the Create a Profile page. Requirements Documentation Approach: Use Cases and Wireframes. 2. SharePoint Web Content Management (WCM) Pages these are pages which are built in SharePoint and are used for displaying content. The focus with these pages will be to document which pieces of content are editable, to capture which standard SharePoint webparts should be used and how they should be configured. An example of one of these pages is the About Us page. Requirements Documentation Approach: Annotated wireframes. 3 System Features The following table lists the features of the VON Caregiver Portal and cross-references them to the requirements in the Invitational document dated March 3, Feature Invitational # Page # User Goal/Feature Additional Notes Generic Pop-up Windows Ability to open secure environment sections as a separate pop-up window without losing the originating page for navigation Upon closing the secure environment, the user returns to the originating page on the VON Caregiver Portal. Time Stamp Ability for all user entered information to be date and time stamped. We suggest using modal pop-up when you need to use a pop. A modal pop-up is a control in ASP.Net AJAX tool kit. 10

11 Feature Invitational # PUBLIC FACING FEATURES: Functional Pages Create User Account Page # User Goal/Feature Additional Notes Ability for caregivers to self-register for journal, learning/education modules, and discussion boards. this page Ability to launch an from within the application to submit feedback. Contact Us page The proposed system shall have the ability to incorporate and embed questions (page specific) that allow the user the opportunity to respond. These responses will be stored in the database allowing further evaluation. Sign Up for Newsletter WCM pages Homepage The homepage for the site Sitemap Design and delivery of a site map. A sitemap showing all of the content of the site on one single page. Search and Search Results Ability to conduct a search of the site through pre-defined categories or likely queries. Expert Blog Ability to host VON administered expert Blogs. RSS Ability to host a RSS feed. Calendar FAQ Ability to upload national and provincial events related to caregiving This functionality will not be turned off before September. A list of upcoming events that can be viewed as a list or in a calendar. A template for creating FAQ 11

12 Feature Content Management Workflow Content Management: file formats, versioning Invitational # Page # User Goal/Feature Additional Notes Content management system that shall include: 1.1. Management of files, image media, audio files, electronic documents, and web content 1.2. Requires features to ease the tasks required to publish web content 1.3. Ability to track and manage multiple versions of a single instance of content 1.4. Ability to publish the content to a repository to support access to the content Ability to provide audio clips Ability to support streaming video. Database driven Sources for content to be in a database content structure to manage the information. Static Content Ability to convey static content. Download Forms Ability to download forms for printing. Related Links Ability to embed links to other web sites. What s New Printer Friendly Font Size Control RSS Feed (Frequently Asked Questions) pages. Pages created in the Content Management System will go through an approval process before they are published to the public site. 12

13 Feature EXTRANET FEATURES: Invitational # Page # User Goal/Feature Additional Notes Functional Pages Login Ability to launch extranet (user id and password required) applications from the Caregiver Portal with single sign on. Reset Forgotten Password Change Password Update a Profile Ask our Experts Respond to a Survey Sign Up for Alerts 4 7 The ability to pop-up questionnaires (e.g. user satisfaction) at any time, on a schedule or after a specific number of accesses Ability to send alerts and notifications via regarding new information posted to portal. WCM pages My Site Discussion Board 3 5 The following details the mandatory contractual deliverables/functionality of the successful proponent with respect to the Discussion Board. 1. Ability to provide secure discussion board facilities. 2. Ability to create multiple discussion boards across various functional themes. 3. Ability to have unlimited number of user-ids and passwords. 4. Ability to have users self- A page where registered users can view information which is relevant to them. 13

14 Feature Invitational # Page # User Goal/Feature Additional Notes register (must be registered to enter content). 5. Ability for registered participants to create discussion threads. 6. Ability for the administrator to populate discussion topics. 7. Ability for the administrator to remove inappropriate content. Learning / Education Unique for You Caregiver Electronic Journal Forms and Templates Repository Provide access to secure journal, online learning/education modules, and discussion boards for caregivers. (userid and password) Single secure sign on which will allow caregivers to capture goals and activities around lifestyle, respite, sleep patterns, nutrition (goal setting tools) Ability to have users selfregister (must be registered to enter content) Ability to capture and store (textual) general comments that are date and time stamped related to the caregiver s: 7.1. feelings and emotions 7.2. Lifestyle: Diet and nutrition 7.3. Respite 7.4. Sleep 2 4 Support the development of a repository of 10 forms/self assessment tools to capture personal health 14

15 Feature Invitational # Page # User Goal/Feature Additional Notes information that can then be retained on personal hard drive. Ability to house downloadable forms that can be saved to the local hard drive. Administration Manage Content Portal administration functionality to administer the database driven content (web page labels, warning and error messages, FAQs, etc.). Reports/Evaluation Metrics 4 7 The ability to capture data for evaluation purposes. Number of visits to the portal broken down by pages/threads per user and over all users Number of records and amount of data entered to the portal during a session by a user The date and time of access to the portal and to each of its major functions by a user The duration of the usage of the portal and of each portal function by the user Access profiles Types of searches performed Types of links engaged Ability to generate variety of IT Administration reports (such as but not limited to): 1.1. File storage amounts 1.2. Number of concurrent users 1.3. Number of registered users 1.4. Number of hits (hourly profile) 1.5. Number of visits beyond top level 1.6. Profile of how far within the site a visitor has gone Maintain an audit log of user logins 15

16 Feature Invitational # Page # User Goal/Feature Additional Notes identifying session dates and session times. Disable Inactive Profiles Temporarily Disable the Interactive Functionality Ability to review self-registration data (for discussion board and learning/education modules) Ability for VON IT to purge inactive (for more then 1 year) caregiver profiles/registrations Ability to temporarily disable the interactive portal application functionality for individual users (or all users) with a user friendly informational message. Help Help Creation of Help screens and content related to at least 5 functions, such as: 1.1. self-registration process (including password resets) 1.2. starting a discussion board thread 1.3. creating a profile 1.4. others TBD 16

17 4 Use Case Model Create User Account this Page Anonymous User Contact Us Login Reset Forgotten Password Signed-In User Change Password Manage Profile Ask Our Experts Respond to a Survey Sign Up for Alerts Figure 1 - Use Case Model 17

18 5 Actors, Security and Permissions 5.1 Actors Actor Anonymous User Registered User Content Creator Content Approver Blog Author Discussion Board Moderator Administrator Description An anonymous user who is accessing the public website. A user who has signed-in to the portal. A user who can create content within the portal. A user who is responsible for approving content created by content creators. A user who is responsible for authoring content on the blog. A user who can manage the discussion board. This includes creating discussion topics and moderating postings. They cannot delete a discussion board. The latter can be done by Administrators only. A user who has access to everything in the system. 5.2 User Access Public Facing Site The public facing site will be accessible to anonymous user over the internet. Extranet Site The Extranet portion of the site will only be accessible to registered users. Editing the Site Editing the site will be performed by internal VON Canada users. The exact details of how the sites will be set-up and how users will access their various functionality will be detailed in the Architecture document. 5.3 Permissions The following table defines the user permissions to the functionality of the Caregiver Portal. Action Anonymous User Registered User Content Creator Content Approver Blog Author Discussion Board Moderator Administrator Accessing the Site Access public pages of the website x x x x x x x Search content and view search results x x x x x x x Sign up for a user account/register x a page x x x x x x x Contact us x x x x x x x View blog x x x x x x x View Related Links x x x x x x x Sign Up for x x x x x x x 18

19 Action Anonymous User Registered User Content Creator Content Approver Blog Author Discussion Board Moderator Administrator Newsletter View Calendar x x x x x x x View Help x x x x x x x Generate printer friendly pages x x x x x x x Change the font size x x x x x x x Subscribe to an RSS feed x x x x x x x Login x x x x x x Reset forgotten password x x x x x x Change password x x x x x x Access My Site x x x x x x Update profile x x x x x x Ask our experts x x x x x x Respond to a survey x x x x x x Sign up for alerts x x x x x x Participate in discussion boards x x x x x x View Unique for You x x x x x x Online Learning x x x x x x Content Management Edit content on an existing page x x x Create a new content page x x x Approve edited and new content x x Author content for expert blog x x x x Edit and delete content for expert x x blog Create discussion board topic x x Delete discussion board topic x x Delete discussion board posting x x Administration Temporarily disable the portal x application Disable a user account x View reports x 19

20 6 Workflow 6.1 Content Approval Workflow All pages will go through a content approval workflow. Content will be created by a content author and then submitted to one level of content approval before they are published. This applies to both the creation of new pages and to the modifications of existing pages, as well as to both English and French pages. It should be noted that if an approver is the content creator, their content will need to go through the same workflow. The following diagram illustrates the document creation to publication process. No Create Edit/Review Ready to publish, sign off and approve Approved? Yes Publish Figure 2 Content Approval Workflow As illustrated in the diagram above, the content approval workflow will follow this process: Step User Action Result 1 Content Creator Creates content and submits it for approval Content is submitted to Group of Approvers 2 Content Approver (One of the approvers from the Group of Approvers) Approves the content. Content is published. If content is rejected by a Content Approver it will be sent back to the Content Creator and will be marked as rejected. The Content Creator will be able to edit the content further and re-submit it for approval. 20

21 7 Branding Guidelines The branding of the site will reflect the values presented to us in the VON Graphic Standards document. The following bullets summarize the vision for the User Interface: Consistency is slightly more important then flexibility Accessibility Ease of Use Fast (modular) Small chunks of information 3 and 5 are magic number Figure 3 Standards Cover 21

22 8 Interface Design Look and Feel For the design, please refer to the VON Canada team site at: ared%20documents%2fdesigns&view=%7bbab26cdf%2d1138%2d42c6%2d84e9%2d10cdb2b1b8a8% 7d. 22

23 9 Master Pages, Layouts, Web Part Zones and Navigation Figure 4 Master Pages, Layouts, Web Part Zones and Navigation 23

24 10 Content for the Caregiver Portal Navantis will receive the English content to be published on the VON Caregiver Portal on April 25 th. In addition to this, Navantis needs the VON team to review the text displayed on the interface (e.g., instructions, labels) and send the list of all changes that you would like us to make to it before April 25 th. The date when the French content will be delivered is May 23 th, The French version will also include a translation of all the application pages (e.g., Login, Retrieve password, etc.) so that Navantis can create corresponding pages for the French version. VON will provide word documents for the content that will be used to create web pages and word or PDF files for any files that need to be uploaded to the portal. VON will also fill out the metadata for the content to be published and provide instruction (within the content) if any links to other files need to be included. All documents will be managed separately. VON will track all changes made to the content after April 25 th and will be responsible for applying these changes manually before the launch of the portal. 11 Metadata Architecture Metadata architecture refers to the structure of the content within the portal (i.e., the properties used to classify and organize the content). The metadata architecture helps improve the user experience while searching for information. (The site architecture supports the users who browse, while metadata architecture supports the users who search.) The recommended approach is to use a fixed list of tags, not a free text. It is important to note that we can meta tag whole documents, not parts of a document. Here is the list of metadata that will be used to classify and organize the content on the VON Canada Caregiver portal: Description We recommend that you include a description for every web page, with the exception of discussion boards and blogs. This description will show up in the SharePoint search results, as well as in the Google search results. Region o Alberta o British Columbia o Manitoba o New Brunswick o Newfoundland and Labrador o Northwest Territories o Nova Scotia o Nunavut 24

25 o Ontario o Prince Edward Island o Quebec o Saskatchewan o Yukon Territory o All Health condition o Acquired Brain Injury o Alzheimer s and related dementias (Creutzfeldt-Jakob, Lewy body Dementia, Frontotemporal Dementia/Pick's Disease, Vascular Dementia) o Amyotrophic Lateral Sclerosis - ALS o Arthritis o Cancer (breast, cervical, colorectal, lung, prostate, skin, etc.) o Developmental disability (Cerebral palsy, Downs Syndrome, FASD, etc.) o Diabetes o Frailty o Hearing loss o Heart Conditions (ischemic heart disease, Congestive heart failure, heart attack, cerebrovascular disease, high blood pressure, etc.) o Infectious conditions (HIV/AIDS, Tuberculosis, Hepatitis, etc.) o Lung Conditions (asthma, Chronic Obstructive Pulmonary Disease (COPD), Cystic fibrosis, sleep apnea, etc.) o Mental Health (Schizophrenia, Mood disorders (depression and bipolar disorder), Anxiety disorders, Eating disorders, and Personality disorders) o Multiple Sclerosis - MS o Nervous system conditions (Epilepsy, Huntington s, Parkinson s, aphasia o Pain o Physical disability o Stroke o Vision loss o All Stage of caregiving o Less than 2 years o Long term care giver (2 years and up) o End of Life/Palliative o After care giving o All Age o 18 years or under o o

26 o o 65+ o Over 70 o All Relationship o Spouse/partner o Child o Parents o Other family relationships o Friend o Support caregiver o All Setting of the care o Home o Hospital o Long Term Facility o Hospice o All Caregiving tasks o Personal Care o Household Work o Coordination of Care o Support o Nursing Care o All Type o FAQ o Article o Tutorial or How to Guide o Press Release o Fact Sheet o Tools and Resources o Report o Events o All Employment Status o Employed o Unemployed o All Culture o African (e.g. Somali, Uganda, Zimbabwe) 26

27 o o o o o o o o o o o o o o o Arab/West Asian (e.g., Armenian, Egyptian, Iranian, Lebanese, Moroccan) Caribbean (e.g. Haitian, Jamaican) Chinese Filipino First Nations (e.g. North American Indian) Inuit Japanese Korean Latin American/South American (Mexican, Columbian, Guyanese) Métis South Asian (Indian, Sri Lankan, Pakistani) South East Asian (Indonesia, Thai, Malaysian) White (Caucasian) Other All The default value for each of these categories will be All. 12 Functional Pages Functional pages are pages within the site which contain forms or other pieces of user functionality. Each of these pages is unique Sign Up For A User Account UC Actor: Anonymous User Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 4, 2008 April 11, 2008 April 16, 2008 Use Case Summary Anonymous users can sign up for a user account in order to access the additional features of the VON Caregiver portal. The information collected during the sign up process (e.g., province or territory) will be used by the system to automatically create a partial profile for the user. The user will be able to complete this profile after singing in. Business Rules The username will be based on the address or name/nickname. 27

28 Each profile must have a unique name/nickname and address. The system will create a unique id (GUID) for the user Login ID in active directory. The name or nickname will be used to identify the user in the site (e.g. Welcome John ). Users will be able to change their username (i.e., address) if needed. User passwords must be at least 8 characters. Pre-Conditions None Post-Conditions The user has a partially completed profile on the site and can now sign-in the VON Caregiver Extranet. Primary Flow of Events 1. The user clicks on the Register Now link. 2. The system presents the user with a form (see Figure 5 Sign Up). 3. The user fills in the form and clicks on the Sign up button to submit it. 4. The system verifies that the address entered by user is not already in use and that all the other validation requirements have been successfully met. Upon successful validation the system, creates a partial profile for the user and takes the user to My Site (see Figure 26 My Site). 5. The use case ends. Alternative Flow of Events Address Already Taken 4a. The system finds that the address entered by user is already in use in the system. 4b. The system prompts the user to enter a different address and also offers the user the Forgot your password? link to help users who have already created an account and subsequently forgot about it to reset their password. 4c. The use case returns to the primary flow of events at step 3. 28

29 Wireframes Figure 5 Sign Up/Login 29

30 Data Validation for Sign Up for a User Account Page # Label Type Format/Values (Default in bold) 1 Name or a Nickname Text box N/A A name or nickname must be entered. The name/nickname must be unique. 2 address Text box N/A The address is syntactically valid. (Note that this will not determine whether the address exists or not). The address is unique. 3 Confirm Text box N/A Same validation rules as above Address and the entered in this field should match the address entered in the item above. 4 Password Text box N/A The password must match the Validation Rules Req. Tab. Error Messages/Notes Order Yes 1 Please enter a name or nicknam regular expression complexity from the web.config setting Von.CaregiverPortal.PAssword Complexity e.g. This expression ^.*(?=.{8,})(?=.*\d)(?=.*[a- z])(?=.*[a- Z])(?=.*[@#$%^&+=]).*$ for enforcing the following: Must be at least 8 characters Must contain at least one one lower case letter, one upper This name or nickname is alread use. Please specify another name valid - user@domain.com. Please nickname. Yes 2 This address is not syntact enter the address. This address is already in u Please specify another addr Yes 3 The addresses that you en do not match. Please try again. Yes 4 The password you entered do match the complexity requirem You need to have one upper ca letter, one special character an number, and the length should less than 8 characters. 30

31 # Label Type Format/Values (Default in bold) Validation Rules Req. Tab. Order case letter, one digit and one special character Valid special characters are Error Messages/Notes 5 Confirm password 6 Province / Territory 7 Note about Acceptable Use Policy Text box N/A Same validation rules as above and the password should match the password that was entered in the field above. Dropdown List Alberta British Columbia Manitoba New Brunswick Newfoundland and Labrador Northwest Territories Nova Scotia Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Territory None Yes 6 Yes 5 The passwords do not match. Ple again. checkbox to acknowledge that yo accept the terms of our acceptab Checkbox N/A Must be selected Yes 7 Please check the Acceptable Use policy. 8 Note about Read only N/A N/A N/A Privacy Policy text 9 Sign Up Button N/A N/A N/A 8 31

32 12.2 Login UC Actor: Registered user Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 4, 2008 April 10, 2008 April 16, 2008 Use Case Summary The Login page allows users to login to the VON Caregiver Extranet. In addition, the Login page explains the benefits of signing up for a user account. Business Rules None. Pre-Conditions None. Post-Conditions The user is logged in to the system and can access the areas of the site which are only accessible to registered users. Primary Flow of Events 1. The user clicks on the Sign In link. 2. The system presents the user with a login form (see Figure 5 Sign Up/Login). 3. The user enters their address and password and clicks on the Login button. 4. The system validates that the address and password are correct and logs the user into the system. The system takes the user to their My Site page (see Figure 26 My Site). 5. The use case ends. Alternative Flow of Events 3a. User Can t Remember Password 3a1. If the user cannot remember their password, they click on the Forgot your password? link on the login page. 3a2. The system takes the user to the Re-Set Forgotten Password page (see 12.3 Reset Forgotten Password). 3a3. The use case ends. 3b. User s Account Has Been Disabled 3b1. The user enters the right username and password; however, his account has been disabled either due to non use or because the Administrator needs to investigate some issues with his accouont. 3b2. The system displays the following message for English users, Your account is currently not available or has been disabled. If you believe you should have access to this page or directory please visit the Contact page [insert link]. Contact caregiving@von.ca and include the address you are 32

33 trying to access. The system displays the following message for French users, TBD. Wireframes Please see previous use case. Data Validation for the Login page # Label Type Format/Values (Default in bold) Validation Rules Req. Tab. Order 1 address or Text box N/A None Yes 1 name/nickname 2 Password Text box N/A None Yes 2 Notes 3 Remember my address or name/nickname 4 Forgot Your Password? 5 Login Button N/A A match was found in the system. Checkbox N/A None No 3 Link N/A None N/A 4 N/A 5 The address/name/nickn ame or password that you entered is incorrect. Please try again Reset Forgotten Password UC Actor: Registered user Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 4, 2008 April 10, 2008 April 16, 2008 Use Case Summary Users who have forgotten their passwords will be able to set up a new password. The following diagram describes the workflow for resetting a password. Once the users notify the system that they forgot their password, the system will generate a random password and send it to the user by . When the user logs in to the site with this system generated password, the system will force the user to change the password. 33

34 Password Reset Workflow I have forgotten my password. User Goes to Password Reset Request User Fills out Password Reset Request form Is form information valid? Is the user part of the system? YES NO Error. Option to correct error User Fills out Password Reset Request form User Redirected to User is instructed to check Confirmation Password Reset instructions sent by I ll go check my User checks Message sent to address specified for the account with new system Generated password, instructions and a link to secure page on system where the user can reset their password. Link takes user to Login User logs in with new system generated password so that they can see the password reset form Is login correct NO YES SECURE Password Reset Form User Fills out Password Reset form Error. Option to correct error User Fills out Password Reset Request form Is form information valid? Does the password meet the system password criteria YES NO Error. Option to correct error User Fills out Password Reset form Confirmation Password has been reset Great. My password is now reset. Now I can access the VON Caregiver Extranet. Figure 6 Workflow for Resetting a Forgotten Password 34

35 Business Rules The password generated by the system will expire in 5 days (5 days is the default value; this value will be configurable). Users will be forced to change their password after they log in. The password generated by the system should include at least one number, one upper case character and one special character. The password will be at least 8 characters long. Pre-Conditions None. Post-Conditions None. Primary Flow of Events 1. The user clicks on the Forgot your Password? link. 2. The system presents the user with a password retrieval form (see Figure 7 - Forgot Your Password / Password Reset Page). 3. The user enters their address and clicks on the Continue button. 4. The system validates that there is a user account for that address. (The assumption for the primary flow of events is that a profile is found.) 5. The system generates a random password for the user and sends an to the user containing the generated password and a link to the password reset page. 6. The user receives the sent by the system and clicks on the Password Reset link contained in the The system presents the user with the Password Reset page (see Figure 7 - Forgot Your Password / Password Reset Pages). Note: The user will be forced to change their password. 8. The user fills out the form and clicks on the Save button. 9. The system validates the information that was entered and upon successful validation it displays a confirmation message: The password was changed in a modal pop up. 10. The user closes the modal pop up. 11. The system takes the user to the My Site page. 12. The use case ends. 35

36 Wireframes Figure 7 - Forgot Your Password / Password Reset Pages 36

37 Data Validation for Forgot your Password Form # Label Type Format/Values (Default in bold) Validation Rules Req. Tab. Order Error Messages/Notes 1 address Text box N/A address exists in the system. Yes 1 This address does not exist in the system. Please check the address and try again If you do not have an account, please Register. 2 Continue Button N/A N/A N/A 2 Data Validation for the Password Reset Form # Label Type Format/Values (Default in bold) 1 Enter your current password 2 Choose a new password Text box N/A Current password is correct Text box N/A The password Validation Rules Req. Tab. Order must match the regular expression complexity from the web.config setting Von.CaregiverP ortal.password Complexity e.g. This expression ^.*(?=.{8,})(?=. *\d)(?=.*[a- z])(?=.*[a- Z])(?=.*[@#$%^ Error Messages/Notes Yes 1 The current password is not correct. Please re-enter the current password. Yes 2 The password you entered doesn t match the complexity requirement. You need to have one upper case letter, one special character and one number and length should be no less than 8 characters. 37

38 # Label Type Format/Values (Default in bold) Validation Rules Req. Tab. Order &+=]).*$ for enforcing the following: Must be at least 8 characters Must contain at least one one lower case letter, one upper case letter, one digit and one special character Valid special characters are Error Messages/Notes 3 Confirm your new password Text box N/A Password entered in items 2 and 3 must match. 4 Save Password Button N/A N/A N/A 4 Yes 3 The passwords do not match. Please re-enter the new password and confirm your new password fields Change Password UC Actor: Registered user Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu 38

39 Date April 4, 2008 April 10, 2008 April 16, 2008 Use Case Summary Registered users will be able to change their passwords, if they desire to do so. Business Rules None. Pre-Conditions The user is logged into the Extranet. Post-Conditions None. Primary Flow of Events 1. The user clicks on the Change Password link, which is available on the My Site page. 2. The system presents the user with the reset password form (see Figure 7 - Forgot Your Password / Password Reset Pages). 3. The user fills out the form and clicks on the Save button. 4. The system validates the information that was entered and upon successful validation it displays a confirmation message: The password was changed in a modal pop up. 5. The user closes the modal pop up. 6. The system takes the user to the My Site page. 7. The use case ends. Wireframe For the wireframe and data validation for the Password Reset page, please refer to the Reset Password use case This Page UC Actor: Anonymous user, Registered user Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 9, 2008 April 14, 2008 April 16, 2008 Use Case Summary If a user finds a page interesting they can a link to that page easily by using the this page feature. The icon will be on most of the pages and it will allow users to create an message containing a link to the page and a brief custom message. 39

40 Once the VON Caregiver Portal is launched, this feature can be leveraged to bring traffic to the portal. Business Rules Users will be able to enter multiple addresses. Commas will be used to separate multiple addresses. When users mouse over the icon, the system will display the following tool tip, this page. If the link is to a public page, then when the recipient of the clicks on the link, the system will open up the page. If the link is to an authenticated page, then when the recipient of the clicks on the link, the system will display the Login page. The following text will be displayed at the top of the Login page, You are trying to access an authenticated page. If you have an account, please login to access the page. If you don t have an account, please sign up for one in order to access the page. Pre-Conditions None. Post-Conditions None. Primary Flow of Events 1. The user clicks on the this page icon. 2. The system presents the user with the this page form (see Figure 8 - This Page) in a modal pop-up. 3. The user fills in the information on the form and clicks on the Send button to submit the form. 4. The system validates the information that was entered and upon successful validation it sends the message to the address(es) specified on the form. If the user has selected the Send a copy to me option the system also sends a copy to the user. The system will also display a confirmation message, Thank you. Your message has been sent. in a modal pop-up. 5. The use case ends. Alternative Flows of Events 3a. Close the this page Form 3a1. The user clicks either on the Close Window icon in the top right corner or on the Cancel button. 3a2. The system closes the this page form without sending an , and returns the user to the page they were viewing. 3a3. The use case ends. 3b. Send a Copy to Me 40

41 If the user has selected the Send a copy to me checkbox, the system will send a copy of the message to the user. 41

42 Wireframes 42 Figure 8 - This Page

43 Data Validation for the This Page # Label Type Format/Values (Default in bold) To section: 1 address Text box N/A The address is syntactically valid. (Note that this will not determine whether the address exists or not). Validation Rules Req. Tab. Order From section: 2 Name Text box N/A Data has been entered into this field. 3 Address Text box This field will be prepopulated for registered users. 4 Your personal message The address is syntactically valid. (Note that this will not determine whether the address exists or not). Text box N/A Data has been entered into this field. No more than 1000 characters 5 Send a copy to Checkbox N/A None No 5 me 6 Submit Button N/A None N/A 6 7 Cancel Link N/A None N/A 7 Error Messages/Notes Yes 1 This address format is not valid - user@domain.com. Please re-enter the address. Yes 2 Please enter your name in the name field. Yes 3 This address format is not valid - user@domain.com. Please re-enter the address. Yes 4 Please enter a personal message. The personal message cannot exceed 1000 characters Update Profile UC Actor: Registered User 43

44 Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 9, 2008 April 15, 2008 April 16, 2008 Use Case Summary Registered users will be able to update their profiles within My Site. The information specified in the profile will be used to customize the links and content displayed on the My Site page. The profile completeness will provide a rough measure of how much of the profile has been completed. Each field that is filled out will constitute 10%. (There is no need for more complicated rules, as this is intended primarily to get users to fill out their profile). Business Rules Each field that is filled out is 10%. Pre-Conditions The user is logged into the Extranet. Post-Conditions The system updates the profile completeness. Primary Flow of Events 1. The user navigates to My Site. 2. The system presents the user with the My Site page, which displays in the middle of the page the user s profile information (see Figure 9 - Profile). 3. The user fills out the Your Information section and clicks on the Save button. 4. The system saves the information specified by the user. 5. The user fills out the Recipient 1 section and clicks on the Save button. 6. The system saves the information specified by the user. 7. If the user is taking care of more than one person, then they will click on the Add Another Care Recipient button. 8. The system opens a Recipient 2 section. 9. The user fills out the Recipient 2 section and clicks on the Save button. 10. The system saves the information specified by the user. 11. The user repeats steps 7-10 as many times as needed. 12. The use case ends. Alternative Flows of Events 3a. Delete a Recipient 3a1. The user clicks on the Delete Recipient link. 44

45 3a2. The system displays the following message, Are you sure you want to delete this recipient? 3a3. If the users selects Yes, the system deletes the recipient. If the user selects No, the system doesn t make any changes. The system continues to display the My Site page. 3a4. The use case ends. 45

46 Wireframes Figure 9 - Profile 46

47 Data Validation for the Update Profile Page # Label Type Format/Values (Default in bold) Your Information: Validation Rules Req. Tab. Order Error Messages/Notes 1 Your Name or a Nickname Text Box Pre-populated with the value specified in the Sign Up (for a user account) form. 2 Address Text Box Pre-populated with the value specified in the Sign Up (for a user account) form. A name or nickname must be entered. The name / nickname must be unique. An must be entered. The address is syntactically valid. 3 Your Picture or Text Box N/A None No 3 Icon 4 Browse Button N/A N/A N/A 4 Yes 1 Please enter a name or nickname. This name or nickname is already in use. Please specify another name or nickname. Yes 2 Please enter an address. This address format is not valid - user@domain.com. Please re-enter the address. 5 Year of Birth Dropdown List 6 Language Dropdown List Select one Select one English French None No 5 None No 6 47

48 # Label Type Format/Values (Default in bold) 7 Your Province / Territory 8 Employment Status Dropdown List Dropdown List Select one Alberta British Columbia Manitoba New Brunswick Newfoundland and Labrador Northwest Territories Nova Scotia Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Territory Select one Employed Unemployed Retired Validation Rules Req. Tab. Order None No 7 None No 8 9 Save Button N/A N/A N/A 9 Error Messages/ Notes Recipient 1: 10 Name or Nickname Text Box 11 Year of Birth Dropdown List 12 Our Relationship Dropdown List Recipient N (E.g., Recipient 1) Select one Select one Spouse/partner Child Parents Other family relationships Friend I Support a caregiver None No 10 None No 11 None No 12 48

49 # Label Type Format/Values (Default in bold) 13 Province / Territory Dropdown List 14 Their residence Dropdown List Select one Alberta British Columbia Manitoba New Brunswick Newfoundland and Labrador Northwest Territories Nova Scotia Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Territory Select one Live in their own Home Share a home with you Hospice Hospital Long Term Facility Other Validation Rules Req. Tab. Order None No 13 None No 14 Error Messages/ Notes 15 I have cared for this person since Dropdown List Select one None No 15 49

50 # Label Type Format/Values (Default in bold) 16 Health Multi Select One Conditions Select List Acquired Brain Injury Alzheimer s and related dementias Amyotrophic Lateral Sclerosis - ALS Arthritis Cancer Developmental disability Diabetes Frailty Hearing loss Heart Conditions Infectious conditions Lung Conditions Mental Health Multiple Sclerosis Nervous system conditions Pain Physical disability Stroke Vision loss Validation Req. Tab. Rules Order None No Save Button N/A N/A N/A 17 Error Messages/Notes 18 Add another Care Recipient Button N/A N/A N/A 18 50

51 12.7 Contact Us UC Actor: Anonymous User, Registered User Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Mariana Buzu Date April 9, 2008 April 14, 2008 April 16, 2008 Use Case Summary The Contact Us form will allow users to ask questions or provide feedback. The feedback received through the Contact Us form will be directed to a mailbox or multiple mailboxes based on the description (i.e., Help us answer you option) selected by the user. Business Rules None Pre-Conditions A mailbox has been set up for every category (i.e., Help us answer you option) and every category has been pointed to a mailbox, as indicated below. It should be noted that Administrators will be able to add additional categories, if needed. Content Related Technical Category English Mailbox French Mailbox caregiving@von.ca soigner@von.ca Even though we ll set up the system to direct all inquires to the same mailbox, we recommend that you maintain the categories. They are designed to help you manage the messages that you ll receive. In the future, if you receive many s, it may be useful to have the flexibility to direct the s for each category to separate addresses. Post-Conditions A user responsible for responding to the questions will send an answer to the question. Primary Flow of Events 1. The user clicks on the Contact Us link. 2. The system opens the Contact Us form (see Figure 10 Contact Us). 3. The user fills out the form and when done, clicks on the Submit button. 4. The system validates the data that was entered and upon successful validation it displays a confirmation message: Thank you for your comments and/or questions. Your opinion is important to us. We will make an effort to respond to your concern or question within 72 hours. Not all questions will be answered personally. If the issue continues, please contact us again. The system sends the feedback to the appropriate mailbox based on the description/category selected by the user. 5. The use case ends. Alternative Flows of Events 51

52 None 52

53 Wireframes 53 Figure 10 Contact Us

54 Data Validation for Contact Us page # Label Type Format/Values (Default in bold) Validation Rules 1 Your Name Text box N/A Data has been entered into this field. 2 Your Text box N/A The Address address is syntactically valid. 3 Subject Text box N/A Data has been entered into this field. 4 Message Text box N/A Data has been entered into this field. Req. Tab. Order Error Messages/Notes Yes 1 Please enter your name. Yes 2 The address is not syntactically valid - user@domain.com. Please re-enter the address. Yes 3 Please enter a subject. Yes 4 Please enter a message. 5 Help us answer you 6 Please use to send me information about other offerings. 7 Please do not use this data to send me information about other offerings. Dropdown List Checkbox Checkbox Select one Content related Technical By default, the checkbox will not be selected. By default, the checkbox will not be selected. An option other than select an appropriate description has been selected. None No 6 None No 7 8 Submit Button N/A N/A N/A 8 Yes 5 Please select an option from the Help us answer you dropdown list Ask Our Experts UC Actor: Registered User 54

55 Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Date April 14, 2008 April 16, 2008 Use Case Summary The Ask Our Experts feature will allow registered users to send questions to blog experts. Not all the submitted questions will be answered in a blog, because some of the questions may have been addressed already in the FAQ section or in a previous blog posting. There will be a note about this at the top of the Ask Our Experts form. The system will send the questions received via the Ask Our Experts form to the appropriate mailbox based on the description (i.e., Help us answer you option) selected by the user. A user responsible for managing these mailboxes will then forward these messages (either manually or automatically by setting up rules) to the appropriate blog expert and the blog expert will choose whether or not they want to answer the questions on their blog. The distribution of messages to the blog experts will be done outside the VON Caregiver Portal system. This feature will most probably be launched in the September iteration. However, it should be built for the June iteration because it needs to be part of the usability testing. Administrators will be able to turn this feature on or off. For the June deployment this feature will be turned off. Business Rules None. Pre-Conditions A mailbox has been set up for every category (i.e., Help us answer you option) and every category has been pointed to a mailbox, as indicated below. It should be noted that Administrators will be able to add additional categories, if needed. Category Mailbox French Mailbox Family matters Taking care of yourself Daily care Health information Health condition information Accessing supports and services Caregiving transitions Working as part of the health care team Caregiving and working Legal financial issues Cultural and spiritual issues caregiving@von.ca soigner@von.ca 55

56 Advocacy Other (please specify) Post-Conditions A user responsible for managing the mailboxes will forward the questions/messages that have been received (either manually or automatically by setting up rules) to the appropriate blog expert and the blog expert will choose whether or not they want to answer the questions on their blog. Primary Flow of Events 1. The user clicks on the Contact Us link. 2. The system opens the Contact Us form (see Figure 11 Ask Our Experts). 3. The user fills out the form and when done, clicks on the Submit button. 4. The system validates the data that was entered and upon successful validation it displays a confirmation message that the form was submitted. The system sends the feedback to the appropriate mailbox based on the description/category selected by the user. 5. The use case ends. Alternative Flows of Events None 56

57 Wireframes 57 Figure 11 Ask Our Experts

58 Data Validation for Ask Our Experts page # Label Type Format/Values (Default in bold) Validation Rules 1 Your Name Text box N/A Data has been entered into this field. 2 Your Text box Address This field will be pre-populated with the user s address. The address is syntactically valid. 3 Subject Text box N/A Data has been entered into this field. 4 Message Text box N/A Data has been entered into this field. Req. Tab. Order Error Messages/Notes Yes 1 Please enter your name. Yes 2 The address is not syntactically valid - user@domain.com. Please re-enter the address. Yes 3 Please enter a subject. Yes 4 Please enter a message. 5 Help us answer you Dropdown List Select one Family matters Taking care of yourself Daily care Health information Health condition information Accessing supports and services Caregiving transitions Working as part of the health care team Caregiving and working Legal financial issues Cultural and An option other than select an appropriate description has been selected. Yes 5 Please select an option from the Help us answer you dropdown list. 58

59 # Label Type Format/Values (Default in bold) spiritual issues Advocacy Other (please specify) 6 Please use Checkbox By default, the to send me checkbox will not information be selected. about other offerings. 7 Please do not use this data to send me information about other offerings. Checkbox By default, the checkbox will not be selected. Validation Rules Req. Tab. Order None No 6 None No 7 8 Submit Button N/A N/A N/A 8 Error Messages/Notes 12.9 Respond to a Survey UC Actor: Registered User Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Date April 17, 2008 April 22, 2008 Use Case Summary The Alert or Message section on the My Site may include a message, urging registered users to take a brief survey. The survey is anticipated to include 5-10 questions around the user s experience with the site. Business Rules Each alert or message about the survey will have a start and an expiry date. The alert will be displayed to users every 5 th time that a user logs into the system during the duration of the alert/message. The alert or message about the survey will continue to be displayed to users even if they fill out the survey (for more details about how we propose to handle this, please refer to the alternative flow of events). There can be only one alert or message at a time. 59

60 All the survey responses will be tied to the user (i.e., they will not be anonymous). In phase II users will be able to cross reference the survey data with the user profile data (e.g., demographics). For more details, please refer to the Appendix. Users will not be able to answer a survey multiple times. However, they will be able to edit their answers, if needed. Pre-Conditions A survey has been created and an alert or message has been set up and posted about the survey. Post-Conditions The survey data is added to the survey results. Primary Flow of Events 1. The user clicks on the Survey link. 2. The system displays the Survey page (see Figure 12 Survey) in the same window. Note: We recommend that you display the survey in a full page, not a modal pop-up. Although we could discuss the later approach if you prefer using a modal pop-up. 3. The user fills out the survey and clicks on the Submit button. 4. The system saves the responses and displays the aggregated results to the survey, as illustrated on the right side of the wireframe below. 5. The use case ends. Alternative Flows of Events 1a. Edit the Survey If the user has already responded to the survey, the next time that they click on the Survey link the system will display the survey pre-populated with the answers that were specified. The user will be able to change any of the answers before the survey expires. 3a. Cancel 3a1. The user clicks on the Cancel link. 3a2. The system takes the user back to the page from where they came. 60

61 Wireframes 61 Figure 12 Survey

62 12.10 Sign Up for Alerts UC Actor: Registered User Version 0.1 Outlined Detailed Finished Author Mariana Buzu Mariana Buzu Date April 17, 2008 April 22, 2008 Use Case Summary Registered users will be able to opt in or opt out of receiving alerts about new additions to the: Event Calendar What s New VON Expert Blog Discussion Board Content Business Rules alerts will be sent on a weekly basis. alerts will be configured to send updates about new changes made to the event calendar, what s new, VON expert blog, discussion board and content. The alert will be in plain text. The system will send one alert for each alert created by the user (i.e., if the user subscribed to 5 alerts, every week they will get 5 s). However, users can create 1 alert that notifies them about changes to the Event Calendar, What s New, VON Expert Blog, Discussion Board and the Content. The queries will be connected by And. Pre-Conditions None Post-Conditions Every week the system will send one alert for each alert specified by the user, provided new items were added to the scope (i.e., Event Calendar, What s New, etc.) of the alert. Primary Flow of Events 1. The user clicks on the Subscribe to content alerts by link. 2. The system displays the Alerts page (see Figure 13 Alerts). 3. The user specifies the name of the alert they would like to create, the keyword(s) they would like to use for configuring the alert and the scope for the alert Event Calendar, What s New, VON Expert Blog, Discussion Board and/or the Site. The user clicks on the Save Alert button when they are done. 4. The system saves the alert and lists it in the Your Alerts section. 62

63 5. The use case ends. Alternative Flows of Events 4a. Delete Alert 4a1. The user clicks on the Delete link next to the alert they would like to remove. 4a2. The system removes the alert from the list and stops sending s for that alert. 63

64 Wireframes Figure 13 Alerts 64

65 Data Validation for Alerts page # Label Type Format/Values (Default in bold) Validation Rules Configure the Alert: 1 Name of Alert Text box N/A A name should be entered 2 Keywords to search for Text box N/A At least one keyword should be entered. Req. Tab. Order Error Messages/Notes Yes 5 Please specify a name for the alert. Yes 6 Please specify a keyword. Configure the Scope of the Alert: 3 I would like to receive an alert when an event is added to the Event Calendar 4 I d like to know when new announcements are added to What s New 5 I would like to receive an alert when a new post is added to the VON Expert Blog 6 Tell me when someone adds a post to the Discussion Boards Multiple keywords will be connected by And. At least one checkbox in this section must be checked. Checkbox N/A None No 3 Checkbox N/A None No 4 Checkbox N/A None No 5 Checkbox N/A None No 6 Please specify the scope of the alert. 65

66 # Label Type Format/Values (Default in bold) Validation Rules Req. Tab. Order 7 I would like to Checkbox N/A None No 7 receive an alert when new content is added to the Site. Error Messages/Notes 8 Save Alert Button N/A N/A N/A 8 Your Alerts: 9 Delete Link N/A N/A N/A 9 13 Generic Templates The following section describes the custom templates that Navantis will build for you so that you can create content pages. 66

67 67 Figure 14 Generic Template 1

68 Figure 15 Generic Templates

69 14 SharePoint Web Content Management (WCM) Pages The majority of the pages within the VON Caregiver Portal will be built using a series of layouts which are populated with content. This section of the document describes these layouts, and documents the standard SharePoint components and sites that will be built Printer Friendly Description The Print icon will open the browser's print dialog box. The user will select a print device and the browser will send to it a printer-friendly version of the page which will not include the header and the navigation. Requirements: All of the pages of the VON Canada Caregiver portal site will have a separate stylesheet that eliminates page elements that are not desirable and optimizes the content for printing. <link rel="stylesheet" type="text/css" media="print" href="print.css" /> 14.2 Font Size Control Description The Font size control will provide users with three choices of font size. The smallest font size will be the default and there will be two larger versions. Requirements: The system will remember the font size setting for the duration of the session (i.e., the system will remember the setting when users move from page to page) RSS Feed Description The RSS feed will be enabled for the following features: What s new Upcoming Events Discussion Boards Blog 14.4 What s New Description What s new is a webpart that will be displayed on the home page (in the back end, it s a list) and that displays the latest feature articles, caregiver stories or web casts. 69

70 Requirements: Each what s new item will have a title, a short description, a full description and metadata tags. The short description will be limited to 250 characters. The what s new section will show the latest 3 items. The newest item will be displayed at the top. For each item in the what s new section the system will display the title and the short description. The title will embed a link to the full record. When users click on this link the full record will open in a new page in the same browser. If needed, users will be able to add images using the rich text control. Old what s new items will not be deleted. They will always be available to the administrator. Wireframe Please see the home page Calendar Description The Calendar will display national and regional events. Requirements: On the home page, the calendar will be set up to display a maximum of 3 events in a list format. By clicking on an event users will be able to see a detailed page for the event. Users will be able to link to a Calendar view. In this view users will be able to scroll and view both future and past events. Old events will not be purged. The calendar will be editable from the list, not from the home page. Users will be able to export an event to their calendar from the Event Detail page. o When users click on the Add to ical Calendar link, the system will automatically opens the event in Outlook. Users will be able to edit the event and save it. o When users click on the Add to Outlook link, the system will prompt the user to either download or open the event as an ICS file. We recommend that you tag events with metadata (e.g., province or territory, health condition). Wireframe 70

71 Figure 16 Calendar 71

72 Figure 17 Event Details 72

73 14.6 Related Links The Related Links section will be displayed on the public facing website. It will display links related to the content displayed on the page. Content authors will be able to drag and drop the Related Links webpart to any page where they would like to include it. The webapart will read the metadata of the content displayed on the page, do a query for this metadata and display randomly or by relevance 5 of the top 20 results (all these values will be configurable as described in the last paragraph of this section). This will ensure that every time when a user comes to the page, they will see different links. It is possible that there might be less than 5 results. In that case the system will display all the results. If there are no results, then the system will not show the Related Links webpart. It should be noted that users will not be able to modify the query that pulls the related links. The style of this webpart is illustrated on the Generic Template 1 wireframe. Please note that there will be only one style for this webpart. Administrators will be able to configure the following settings for Related Links: How many results should be displayed in this section? Should the results be displayed randomly or by relevance? If randomly, randomized from what (e.g., top 10, top 20) Unique for You/Links Description The Unique for You/Links section is similar to the Related Links section, with the exception that it will be displayed on the Extranet Site only and that it will query profile metadata, not content metadata. This section will display links based on information specific to the registered user and the people they are taking care of. Requirements The system will search the document library using the profile metadata properties. This section will display randomly or by relevance 5 of the top 20 results (all these values will be configurable as described in the last paragraph of this section). This will ensure that every time a user comes to this page, they will see different links. If there are less than 5 results, the system will show all the results. If there are no results, then the system will not show the Links for You webpart. Users will not be able to modify the query that pulls the related links, nor the style of the webpart. Administrators will be able to configure the following settings for Related Links: How many results should be displayed in this section? Should the results be displayed randomly or by relevance? If randomly, randomized from what (e.g., top 10, top 20). 73

74 14.8 Homepage 74 Figure 18 Homepage

75 14.9 Simple Search, Advanced Search and Search Results All content will be searchable. By default SharePoint is set up to search sites and people. The Search People functionality will be turned off Simple Search The simple search will be available on every page. Figure 19 Simple Search with link to Advanced Search Page Search Results SharePoint honours permissions and the search results include only the items that a user has permission to see. Given that we want the search to return matching results from Discussion Boards, even though the Discussion Boards can be accessed by Registered users only, we ll need to configure the system to return these results. Users will be prompted to sign in if they don t have an account to see the full discussion. We recommend using metadata and best bets to make it easier for users to find relevant results. Search term should be turned on (it s not turned on by default). During the requirements gathering sessions we talked about letting users filter the search results. Due to the time constraints we will not be able to implement this functionality in phase I. 75

76 Figure 20 Search Results 76

77 Advanced Search 77 Figure 21 Advanced Search

78 14.10 Expert Blog The expert blogs will be built using the standard blog functionality built into MOSS. It will be a roll-up page that shows the postings and summaries. The will include multiple blogs that will be displayed on one page and categorized by bloger. There will be one blog per author Search blogs Blogs will be searchable. They will be a scope on the advanced search. User authentication is NOT required to search and view a blog Permissions User authentication is required to comment on a post User authentication is required to ask a question Blog Categories The blog will initially be set-up with the following categories: TBD Using the blog functionality built into SharePoint it is very easy for blog authors to add, remove and edit categories as required Blog Feed The blog will have an RSS feed which users can subscribe to. 78

79 Figure 22 Blog Landing Page 79

80 80 Figure 23 Blog Post

81 14.11 FAQ 81 Figure 24 FAQ

82 14.12 Community Resources There will be two levels of community resources: National and Provincial. The resources will provide links to health condition specific organizations, government organizations, caregiver specific information and other types of data. All links will be enabled to open in a new web browser. 82

83 83 Figure 25 Community Resources

84 14.13 My Site Description My Site is a page dedicated to the content associated with the currently logged in user. The information on this page will include the ability to: Update the profile Change the password View and access Unique for You/Links Ask an Expert View top 5 discussions that have the most activity Subscribe to receive alerts Access a personal Caregiver Journal Access the Forms and Templates Repository Requirements The public view will be disabled. All information on the My Site page will be private (i.e., accessible by the registered user only). The ability to upload documents to My Site will be disabled. 84

85 Figure 26 My Site 85

86 Figure 27 My Site (including the Alert section) 86

87 14.14 Discussion Board The discussion board will be built using the standard discussion board functionality which is built into SharePoint which will be modified slightly. (Discussions are simply another type of a SharePoint list.) Search Discussions Discussion boards will be searchable. They will be a scope on the advanced search Dropdown Menus The standard discussion board has an Actions and a Settings dropdown menus, these should only appear for administrative users, they should not be visible for regular users New Threads Any registered can add a discussion thread (click on New) View Options Anonymous users can view discussion boards. Users will be able to choose between Flat and Threaded view options, they should not see options to Modify this view or Create view Pictures Users will be able to set images for their profiles. 87

88 14.15 Caregiver Journal Description Registered users will have access to a personalized Caregiver Journal in which they can record personal notes about their caregiving journey. Users will be able to create, edit and delete entries in their Caregiver Journal. Requirements The Caregiver journal will be a customized MOSS List with the following columns: 88

89 English Name French Name Data Type Size Input Control Title Titre Single Text Line 255 chars Date Date Date/Time Textbox with Calendar Category Catégorie Choice Dropdown List Journal Entry Today, I feel... Entrée de journal Aujourd'hui, je me sens... Multiple Lines of Rich Text Multiple Lines of Rich Text 15 lines Description Déscription Required Textbox Title of the journal entry. Titre de l entrée de journal. Yes Rich Text Editor* 4 lines Rich Text Editor* Date of the journal entry was created. The Categories allows you to adapt your journal entry to sort later to reflect on your experiences. We have suggested a few categories to use. You can also create your own categories. Try to be as specific as possible. Use words and phrases that have meaning to you to help you sort later. This space is for you to record your thoughts and experiences as a caregiver. Not sure where to begin, check out the journal tips for questions to get you started This space is for you to describe your overall mood, feelings, and emotions. Try to be as specific as possible. Use words and phrases that have meaning to you. Date à laquelle l entrée de journal a été créée. Les catégories vous permettent d adapter votre entrée de journal afin de pouvoir retracer plus tard le fil de vos expériences. Nous avons suggéré un nombre limité de catégories. Vous avez cependant la possibilité de créer vos catégories personnelles. Essayez de les délimiter avec la plus grande précision. Utilisez des mots et des phrases dont le sens vous aidera à organiser vos idées. Cet espace est laissé pour que vous puissiez enregistrer vos réflexions et vos expériences d aidant(e) familial(e). Si vous ne savez où commencer, vérifiez les suggestions du journal relatives aux questions qui vous aideront à débuter. Cet espace vous permet de décrire votre état d esprit, vos sentiments et vos émotions. Essayez de le faire avec la plus grande précision possible. Utilisez des mots et des phrases qui ont un sens pour vous. Today, I ate... Aujourd'hui, Multiple 4 lines Rich Text This space is for you to describe Décrivez ici vos habitudes alimentaires. No Yes Yes No No 89

90 Last night, I slept... The last time I felt I had a respite break was... j'ai mangé... La nuit dernière, j'ai dormi... La dernière fois que j'ai eu un répit remonte à... Lines of Rich Text Multiple Lines of Rich Text Multiple Lines of Rich Text Created By User ID Syste m Modified By User ID Syste m Editor* 4 lines Rich Text Editor* 4 lines Rich Text Editor* your eating habits. For many caregivers, finding time to care for themselves can be difficult. Healthy eating is one way to take care of yourself. If you find it hard to take care of yourself, please see your health care provider. This space is for you to describe your sleeping habits. For many caregivers, they experience sleepless nights. To keep healthy, track your sleeping habits. If you are experiencing sleep problems, please see your health care provider. This space is for you to record your sense of respite or when you last felt you had a break. Many caregivers do not plan for respite breaks. However, many caregivers think respite is essential to their own well being. If you are feeling like you need a break, talk to your health care provider. Pour beaucoup d aidant(e)s, trouver le temps d avoir soin de soi peut être difficile. Une alimentation saine est une des manières de prêter attention à soi. Si cela vous est pénible, n hésitez pas à consulter votre fournisseur de soins. Décrivez dans cet espace vos habitudes de sommeil. Un grand nombre d aidant(e)s souffrent d insomnie. Pour vous garder en santé, surveillez vos habitudes de sommeil. Si vous ne parvenez pas à trouver le sommeil, n hésitez pas à consulter votre fournisseur de soins. Dans quelles activités trouvez-vous un répit et à quand remonte la dernière fois que vous avez eu l occasion de vous ménager une pause? Beaucoup d aidant(e)s ne planifient aucune distraction. Ils estiment cependant que le répit est essentiel à leur bien-être. Si vous estimez avoir besoin d un répit, parlez-en à votre fournisseur de soins. N/A Name of creator of journal entry. Nom de l auteur(e) de l entrée de journal. N/A Name of modifier of journal entry. Nom de l auteur(e) de la modification apportée à l entrée de journal. * Rich text editor interface available only on certain browsers, i.e. Internet Explorer for Windows versions 6, 7, 8. No No Yes Yes Figure 28 - Caregiver Journal List Fields 90

91 The system will create a single Caregiver Journal and Journal Category list for each registered user. New journals are created with the following "welcome" entry: Welcome to My Caregiver Journal. This is your private space to record your thoughts and experiences as a caregiver. Research has show caregivers who journal regularly experience less stress and emotional conflict that those caregivers who do not. Think of this space as a positive way to care for your physical and emotional health. The Journal has several different features to help you organize your thoughts and experiences. The category field will help you to view your journal later to reflect on your experiences. We have suggested a few categories to use. You can also create your own categories. Try to be as specific as possible. Use words and phrases that have meaning to you. After the main body of the journal entry, it includes spaces to describe your overall mood, feelings, and emotions; your eating habits; your sleeping habits; and your sense of respite. Many caregivers struggle to care for themselves while caring for others. This space is a way for you to focus on yourself in a healthy way. If you are having difficulties in any of these areas, please see your health care provider. You can also print or delete your journal from the site. Finally, the Journal is intended for your personal use. It is not intended to capture personal information about the person you are care for as a caregiver. We recommend that you keep it private. The information collected in this section of the portal will not be used or viewed by VON for any purpose. Happy Journalling! Users will be able to customize the list of Categories. Users will be able to print the contents of the journal using the browser. No explicit facility is provided for exporting the journal to other formats and/or saving it locally for the user. Such functionality is out of scope in this development phase and could be addressed in a future phase of the project Journal Categories Users will be able to select a category for each post. Users will be able to customize this category list and add, edit and remove entries from the list. The list will be populated with the following default set of categories: English Family Matters Français Questions de famille 91

92 Self Care Caregiving and Work My Caregiving Story Autonomie en matière de santé Prestation de soins informels et travail Mon vécu d aidant(e) 92

93 Figure 29 - Caregiver Journal Categories Views Users will have access to a number of views in addition to the default views for the Journal list: 93

94 Entries summary by Date The Entries summary by Date view will be a generic MOSS list view of all entries showing only the Title, Category and Date, and sorted (by default) by Date descending. 94

95 Latest Entries Details The Latest Entries view will be the default view when navigating to the Caregiver Journal. The home view will show the Title, Date, Category and Entry Details columns for the five most recent entries. Figure 30 - Cargeiver Journal - Home view Calendar 95

96 The Calendar view will be ported from the similar view available to MOSS Calendar lists and will include the same navigation: Figure 31 - Caregiver Journal - Calendar View 96

97 Today I Feel, Today I Ate, Last Night I Slept, Respite Break There will be a view for each of the four named columns which will emphasize the particular column data in the list. Shown here is the Today I Feel view; the other three are similar: Figure 32 - Caregiver Journal - Feelings & Emotions View 97

98 Categorical The Categorical view will show a list of all entries grouped by Category. The user may select each category group for collapse or expansion to focus the view on a particular group or groups. Figure 33 - Caregiver Journal - Categorical View 98

99 Navigation The Caregiver Journal will have a unique left-hand navigation area consisting of a small calendar control ported from the MOSS Calendar list, and the following shortcut links to the features and views associated with the Journal: Back to MySite Takes the user out of the Caregiver Journal area and returns to the MySite page. Add New Entry Presents the new Journal Entry screen with a blank entry area (see Create/Edit Journal Entry) View Latest Entries Presents the customized main landing (Home) view consisting of the five most recent Journal entries View by Month Presents the Calendar view, defaulted to showing the current month. Today, I Feel... Presents the Today I Feel view, showing the text in the Feelings & Emotions column. Today, I Ate... Presents the Today I Ate view, showing the text in the lifestyle column. Respite Presents the Respite view, showing the text in the respite column. Last Night I Slept Presents the Last Night I Slept view, showing the text in the Sleep column. Modify Categories Presents the Category List screen where the user can add, modify or remove items from the category list (see Journal Categories). Print Journal Prints the Journal (see Print Caregiver Journal Users can print the contents of their journal. When the user selects Print Journal from the main navigation, the system will transform the journal contents into a printer-friendly format similar to the MOSS RSS View, which the user can then print. 99

100 Figure 36 - Caregiver Journal - Print-friendly View Delete Caregiver Journal). Delete Journal 100

101 Presents the delete confirmation page (see Print Caregiver Journal Users can print the contents of their journal. When the user selects Print Journal from the main navigation, the system will transform the journal contents into a printer-friendly format similar to the MOSS RSS View, which the user can then print. Figure 36 - Caregiver Journal - Print-friendly View 101

102 Delete Caregiver Journal) Create/Edit Journal Entry Users will use a MOSS entry form to create and edit entries in their journals. The system will display each list field by Name, and include the appropriate UI control and the field Description as listed in the Caregiver Journal List Fields section. 102

103 Figure 34 - Caregiver Journal - Edit Entry Journal Entry Tips List There will be a single, system-wide list which stores Journal Entry "Tips". These tips will appear on the Journal entry screen, in a panel on the right-hand side. Each time the screen loads, a single Tip will be 103

104 chosen at random and displayed to the user. A button will be provided for the user to display another randomly-chosen Tip. Administrative users will have read/write access to the Tips list, allowing them to add, edit, and remove individual entries. Figure 35 - Caregiver Journal - Entry Tips List Edit 104

105 Print Caregiver Journal Users can print the contents of their journal. When the user selects Print Journal from the main navigation, the system will transform the journal contents into a printer-friendly format similar to the MOSS RSS View, which the user can then print. Figure 36 - Caregiver Journal - Print-friendly View 105

106 Delete Caregiver Journal Users wishing to purge their entire journal will select Delete Journal from the Caregiver Journal navigation panel to be taken to the Delete Caregiver Journal page. The Delete Journal page will contain a shortcut link to the Print Journal function and the Delete Journal function. Users wishing to delete the journal will have to confirm their intention by selecting a checkbox before clicking Delete. Upon deleting the Journal the system will return the user to the MySite page. The system will recreate the Journal like it were a new one, with the sample entry, should the user wish to restart recording his/her journal. 106

107 Figure 37 - Caregiver Journal - Delete Journal Templates & Forms Description Registered users will have access to a repository of interactive forms which they may fill out and print 107

108 and/or save the results on their local machine, and downloadable templates which they may fill out using office productivity software (e.g. Microsoft Office and others) and/or print and fill out manually Templates & Forms Index Page Access to the Downloadable Templates and Interactive Forms will be via a single page accessible from the MySite menu. There will be a section for Downloadable Templates followed by one for Interactive Forms. The system will generate a button with a link to download each template or to bring up each interactive form. The button will consist of a title, description and thumbnail for each item. 108

109 109

110 Downloadable Templates Collection The Downloadable Templates will reside in a customized document library with the following fields: Field Name Data Type Size Title Single Text Line 255 chars Filename Single Text Line 255 chars Description Multiple Text Lines 6 lines Thumbnail URL Created By User ID System Modified By User ID System Figure 38- Downloadable Templates Library Columns The Thumbnail field will contain a URL pointing to the appropriate image in the Thumbnails picture library Thumbnails Picture Library The Thumbnails Picture Library will be a MOSS Picture Library containing thumbnails for each of the Downloadable Templates and Interactive Forms. 110

111 Figure 39 - Thumbnails Picture Library 111

112 Interactive Forms Registered users will be able to fill out Interactive Forms and receive feedback from the system based on the selected responses. Users will have the option of saving the form and response to their local machine for printing and/or future reference. In this phase of the project, one Interactive Form is envisaged: the Caregiver Self-assessment Caregiver Self-assessment The Caregiver Self-assessment Form is a User Quiz which asks the user to assess one of four levels of severity to each of six criteria. The system then tabulates a score and presents the score as well as some explanatory material about the user's score and other possible results. 112

113 Figure 40 - Caregiver Self-Assessment Form 113

114 114 Figure 41 - Discussion Board 1

115 Figure 42 - Discussion Board 2 115

116 This screenshot shows the built in functionality for scheduling alerts. Figure 43 - Discussion Board 3 116

117 15 Administration Features 15.1 Disable Inactive Users We recommend that you disable an account, and not delete it from the system. The accounts don t take a lot of space and furthermore, if a user participated in discussions, we can t delete the threads they created and the threads need to be associated with the user. o o The system will automatically send an to users whose account has been inactive for 1 year (this value will be configurable; the default will be set to 1 year) and ask them to login in to refresh their account, or the account will be disabled in X days (this value will be configurable; the default will be set to 30 days). There will be a configuration setting for whether or not to delete the My Site content (the default will be set to delete My site ). The wording for the is: We notice that you have not used your account for over 12 months. To keep your account open, please login to renew your account or it will expire in 30 days. This message will be editable, if needed Temporarily Disable the Portal Application Administrators will be able to create user friendly informational message in both English and French for the following HTTP errors. When one of these errors occurs, the system will display the appropriate message. HTTP Errors Error # Error Code Static Html Error Page Message 401 Unauthorized You might not have permission to view this page using the information you supplied. Please ensure that you are logged-in. You can login below. How to Create an Account: If you do not have an account you can create one below. 403 Forbidden Technical Information If you believe you should have access to this page please visit the Contact page [insert link]. Report This Error Contact and include the address you are trying to access 117

118 400 Bad Request The page cannot be found Error Payment Required 404 Not Found 405 Method Not Allowed 406 Not Acceptable 407 Proxy Authentication Required 408 Request Timeout 409 Conflict 410 Gone 411 Length Required 412 Precondition Failed 413 Request Entity Too Large 414 Request-URI Too Large 415 Unsupported Media Type 416 Requested Range Not Satisfiable The page you are looking for might have been removed, had its name changed, or is temporarily unavailable. Please try the following: If you typed the page address in the Address bar, make sure that it is spelled correctly. Open the [insert web address] home page or sitemap [insert link] and then look for links to the information you want. Search the website [insert link to search page] Click the Back button to try another link. Report This Error Contact and include the address you are trying to access 417 Expectation Failed Technical Information (for support personnel) others TBD Error # Error Code Static Html Error Page Message 500 Internal Server Error The page cannot be displayed 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout There is a problem with the page you are trying to reach and it cannot be displayed. 505 HTTP Version not supported Please try the following: Open the [insert web address] home page or sitemap [insert link] and then look for links to the information you want. 118

119 Click the Refresh button, or try again later. Search the website [insert link to search page] Click the Back button to try another link. Report This Error Contact and include the address you are trying to access Technical Information (for support personnel) Error # Error Code Maintenance window message Static Html Error Page Message The site is temporarily unavailable due to maintenance. Please try the following: Click the Refresh button, or try again later. Report This Error Contact and include the address you are trying to access Technical Information (for support personnel) caregiving@von.ca 119

120 16 Reports 16.1 Web Analytics We recommend that you use Google Analytics: to view data about how many users accessed the site, how far within the site visitors have gone, the types of links they access, how much time they spend on each page and other similar data. Google Analytics offers a host of compelling features and benefits for everyone from senior executives and advertising and marketing professionals to site owners and content developers. It allows you to learn how visitors interact with your website and identify the navigational bottlenecks that keep them from completing your conversion goals. Here is the list of reports that Google Analytics provides. 1. Marketing Optimization a. Unique Visitor Tracking i. Daily Visitors ii. Visits & Pageview Tracking iii. Goal Conversion Tracking iv. Absolute Unique Visitors v. Visitor Loyalty vi. Visitor Recency b. Visitor Segment Performance i. New vs Returning ii. Referring Source iii. Geo Location iv. Geo Map Overlay v. Network Location vi. Language vii. User-defined viii. Domains 2. Content Optimization a. Ad Version Testing i. Overall Ad A/B Testing ii. Source Specific Testing iii. Keyword Specific Testing b. Content Performance i. Top Content ii. Content Drilldown iii. Content by Titles iv. Dynamic Content v. Depth of Visit vi. Length of Visit c. Navigational Analysis c. Marketing Campaign Results i. Campaign Conversion ii. Source Conversion iii. Medium Conversion iv. Referral Conversion v. Campaign ROI vi. Source ROI vii. Medium ROI d. Search Engine Marketing i. All CPC Analysis ii. AdWords Analysis iii. AdWords Keyword Positions iv. Overall Keyword Conversion v. CPC vs Organic Conversion vi. Keyword Considerations i. Entrance Bounce Rates ii. Top Exit Points iii. Site Overlay iv. Initial Navigation v. All Navigation d. Goals & Funnel Process i. Goal Tracking ii. Goal Conversion iii. Defined Funnel Navigation 120

121 iv. Defined Funnel Abandonment v. Reverse Goal Path vi. Goal Verification e. Web Design Parameters i. Browser Versions ii. Platform Versions iii. Browser & Platform Combos 3. E-Commerce Analysis a. Commerce Tracking i. Revenue & Transactions ii. Conversion Rate Graph iii. Average Order Value iv. Transaction List b. Loyalty & Latency i. New vs Returning ii. Time to Transaction iii. Visits to Transaction c. Revenue Sources i. Referring Sources ii. Languages iii. Organizations iv. User-defined v. Top Cities vi. Country Drilldown vii. Affiliations iv. Screen Resolutions v. Screen Colors vi. Languages vii. Java Enabled viii. Flash Version ix. Connection Speed x. Hostnames d. Product Merchandising i. Product Performance ii. Product Categories iii. Product Country Correlation iv. Product City,Region Correlation v. Product Keyword Correlation vi. Product Source Correlation One of your requirements was to provide a report that shows the number of concurrent users (e.g., how many people are using the journal at the same time). We ll need to check with your selected hosted environment to find out if they can provide this data. As illustrated in the screenshot below, you can view the data by day or by hour. 121

122 Here is an example of a google analytics report. Figure 44 Web Analytics Report Google analytics is currently a free hosted service. It is our understanding that the analytics tracking is done by inserting an external JavaScript file into the master pages so it appears site wide SharePoint Out-of-the-Box Reports SharePoint provides many reports and the ones that you requested below are supported by it. Types of searches performed (Navantis will turn on the search logs). Usage Report: o Number of visits to the portal broken down by pages/threads per user and over all users (this data will be available in both SP and Web Analytics); o Number of records and amount of data entered to the portal during a session by a user. File storage amounts; 122

123 Number of registered users. Here is an example of a site usage report. Figure 45 Usage Report 16.3 Audit Logs The following screenshot illustrates how granular we can control the auditing. Please note that we can t pick specific document libraries and/or lists. These settings apply to a site collection. 123

124 Figure 46 Audit Settings The Audit Log will be turned on Track Changes Made to Content Pages Changes made to content pages will be tracked by means of version history. This feature comes out-ofthe-box with SharePoint Statistics About Registered Users Administrators will have access to statistical data about registered users (e.g., how many caregivers liver in a certain province, how many are employed, how many care recipients per care giver, etc.). Given that there is only one report about registered users, we recommend that we provide you with the capability to export summary and detailed data about registered users. This will allow you to analyze the data in any way that you need to. Below is a description of how this will work. When users click on the Report link (this link will be in the Site Administration section), the system will display a page where users will be able to specify the criteria they would like to use to generate the report. The table below lists these criteria. Data Validation for Search Criteria for Generating the Report 124

125 # Label Type Format/Values (Default in bold) 1 Province or Dropdown All Territory List Alberta British Columbia Manitoba New Brunswick Newfoundland and Labrador Northwest Territories Nova Scotia Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Territory 2 Age Dropdown List 3 Employment Status 4 Experience providing care Dropdown List Dropdown List 18 years or under Over 70 All Employed Unemployed Retired All Less than 2 years Long term care giver (2 years and up) End of Life/Palliative After care giving All Validation Rules Req. Tab. Order None No 1 None No 2 None No 3 None No 4 When users click on the Generate button, the system will prompt the users either to open or save the report. If the user chooses to open the report, then the system will display the report in SSRS, and if the user chooses to save the report, then the user will be prompted to specify a location where to save the data. The data will be saved in an Excel format. The Excel file will have two tabs. The first tab will include summary statistics about the registered users, as illustrated below. 125

126 Summary Statistics About Registered Users Province or Territory: Alberta British Columbia Manitoba New Brunswick Newfoundland and Labrador Northwest Territories Nova Scotia Nunavut Ontario Prince Edward Island Quebec Saskatchewan Yukon Territory Unspecified All Employment Status: Employed Unemployed Retired Unspecified Age: 18 years or under Over 70 Unspecified Experience Prviding Care: Less than 2 years Long term care giver (2 years and up) End of Life/Palliative After care giving Unspecified Language Preference: English French Unspecified Signed up for the Newsletter? Yes No Number of Caregivers Note: Because most of the fields in the profile are optional, we have added a line item "unspecified" for most categories. This item will list the number of caregivers who have not specified this information in their profile. Figure 47 Summary Data About Registered Users 126

127 The second tab will display detailed data, as illustrated below. This will allow Administrators to analyze the data in any way that they find it useful. All Data About Registered Users Note: We'll display one row per caregiver. Caregiver Year of Birth Caregiver Experience providing care Caregiver Language Preference Caregiver Province Caregiver Employment Status Caregiver signed up for the Newsletter? Care Recipeint Name Care Recipeint Year of Birth Care Recipeint relationship to Caregiver Care Recipeint Province Care Recipeint Health Conditions Care Recipeint Residence I have cared for this person since 1965 New French Ontario Employed No Recipient Parent British Columbia ALS Pain Home 2007 Recipient Child British Columbia Astma Home 2002 Figure 48 Detailed Data About Registered Users 127

128 17 Learning Module The learning module will be available on the public facing portal to all the users who log into the system. The learning module will include self-screening tools, PowerPoint presentations, exercises and in the future it may include a plug in to video learning modules. The system will not track what modules have been accessed and it will not save any results from self-screening exercises. 18 Help The help screen will be accessible by clicking on the Help link in the top right corner of any page. When users click on the Help link, the system will display a help screen in a separate window. On the left side of the screen the system will display the list of all the help topics that are available, while on the right side of the screen it will display the help landing page. Users will have the option to navigate through the help content by using the topic links in the left navigation pane. It should be noted that where possible we ll provide instructions in the wireframes to minimize the need for help. The table below lists the help topics that will be available in the system. The help topics will present simple to understand instructions. Help Landing page How to sign up, how to reset a password How to start a discussion thread. How to update a profile. How to ask the Blog Expert a question. How to manage the journal. 128

129 Figure 49 Help 129

130 19 Non Functional Requirements 19.1 Technologies to be used There are several applications involved in this project that have their own inherit features, interfaces and designs. The description of their baseline functionality is beyond the scope of this document, which will focus on any extension, customization or enhancement made to these products above and beyond their core functionalities. These applications are: Server Products: o Windows 2003 Server SP2 o Microsoft Office SharePoint Server 7.0 SP1 o Microsoft.Net framework V2.0 o SQL Server 2005 SP2 o Internet Security and Acceleration Server 2006 (optional) Development tools: o Microsoft Visual Studio 2005 and Microsoft Team System 2005 o Microsoft Office SharePoint Designer 2007 o Graphic design tools and other utilities. Navantis will ensure that the latest stable version of these applications is used Multi-Language Variations (English and French) Navantis will create and deploy French and English logic in the solution, but will not be responsible for the instantiation of any of that content. We will use a feature of MOSS 2007 called variations to create this functionality. The URLs will be dependent on how Variations in MOSS 2007 works. The system will be configured to allow the publication of English pages without the publication of corresponding pages in French Accessibility Checklist and Notes W3C WAI 1.0 Priority 1 checkpoints A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents. In General (Priority 1) Notes 1.1 Provide a text equivalent for every nontext element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including The master pages, controls and webparts that are created by Navantis will meet this guideline. 130

131 symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. Decorative Graphic <img src="decoration.gif" alt="" /> Picture <img src="photo.jpg" alt="picture of Bryce Johnson" /> Content Authors using the CMS capacities of the site will need to be vigilant to ensure that this very important guideline is met. 2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. The master pages, controls and webparts that are created by Navantis will meet this guideline. 4.1 Clearly identify changes in the natural language of a document s text and any text equivalents (e.g., captions). English and French pages will be separate. The natural language of the document will be declared. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" " <html xmlns=" xml:lang="en-ca" lang="en-ca"> <head> <title>4.1 Clearly identify - natural language</title> </head> <body> <p>english</p> <p><span lang="fr-ca">français</span></p> </body> </html> 131

132 6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. The system should be readable without the documents stylesheet. It may not be an optimal reading experience however. This is a technical limitation of SharePoint. 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. There are no equivalents in the system all content is dynamic 7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. The interfaces of the system will meet this guideline. If authors in the future add images or content using the CMS they will need to adhere to this guideline Use the clearest and simplest language appropriate for a site s content. The writing team will need to be aware of this guideline when reviewing and approving content. And if you use images and image maps (Priority 1) Notes 1.2 Provide redundant text links for each active region of a server-side image map. There are no server side image maps in the system. 9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. There are no server side image maps in the system. And if you use tables (Priority 1) Notes 5.1 For data tables, identify row and column headers. Data tables have not been identified as part of the system templates. If data tables are added to the site they will be content and will need to be optimized by the site authors 5.2 For data tables that have two or more Data tables have not been identified as part of 132

133 logical levels of row or column headers, use markup to associate data cells and header cells. the system templates. If data tables are added to the site they will be content and will need to be optimized by the site authors And if you use frames (Priority 1) Notes 12.1 Title each frame to facilitate frame identification and navigation. The frames that are used in the system, like the IFRAME in the modal popups will have appropriate titles. And if you use applets and scripts (Priority 1) Notes 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. A majority of the sites functionality is enabled by scripting. It is not practical to use the system without scripting enabled. Most sites online today use some for of scripting. And if you use multimedia (Priority 1) Notes 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. If the content authors plan to use video on the site the site owners will need to consider the creation of a descriptive video audio track. 1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. If the content authors plan to use video on the site the site owners will need to consider the creation of closed captions. And if all else fails (Priority 1) Notes 133

134 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. Although this is a possible option it would not be advisable as maintaining multiple content repositories can be difficult. W3C WAI 1.0 Priority 2 checkpoints A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents. In General (Priority 2) Notes 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text]. The interfaces of the site will meet this guideline. If authors in the future add images using the CMS they will need to adhere to this guideline. 3.1 When an appropriate markup language exists, use markup rather than images to convey information. This should not be a problem. 3.2 Create documents that validate to published formal grammars. This is a difficult guideline to meet using SharePoint 3.3 Use style sheets to control layout and presentation. Not 100% of the interfaces will be presented using CSS. 3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. The stylesheets will use PX, % or EM relative units NOT inches, centimenters or points which are absolute units. 3.5 Use header elements to convey document structure and use them The templates are being designed to have a strong header element. If authors in the future add 134

135 according to specification. additional headings using the CMS they will need to adhere to this guideline. 3.6 Mark up lists and list items properly. The templates are being designed to use list elements properly. If authors in the future add additional headings using the CMS they will need to adhere to this guideline. 3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. When the content authors are inputting content they will need to be aware of this guideline. There are no quotes in the templates 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. There have not been any alternatives planned for dynamic content. There will only be dynamic content. 7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). The interfaces of the system will meet this guideline. If authors in the future add images or content using the CMS they will need to adhere to this guideline. 7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. There are no plans to auto refresh pages with the templates Navantis is designing. 7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. Server side redirects will be used if any redirection is needed Until user agents allow users to turn off spawned windows, do not cause popups or other windows to appear and do not change the current window without informing the user. Any popup or new windows will be spawned by user input. We will use title attributes on the hyperlink anchors that inform blind users that a new window will be opening. <a href= # onclick= (); title= This will open a new window >link</a> 11.1 Use W3C technologies when they are There are no plans for the use of non-w3c client 135

136 available and appropriate for a task and use the latest versions when supported. side technologies. There is talk of video content but it has not been determined how it will be delivered. The site will also offer document downloads in PDF Avoid deprecated features of W3C technologies. The development team will strive to meet this guideline Divide large blocks of information into more manageable groups where natural and appropriate. The writing team will need to be aware of this guideline when reviewing and approving content 13.1 Clearly identify the target of each link. This will not be an issue. The content and design team will use clear, easy to understand link label Provide metadata to add semantic information to pages and sites. There are plans to use extensive metadata on the pages Provide information about the general layout of a site (e.g., a site map or table of contents). A sitemap is part of the templates being created Use navigation mechanisms in a consistent manner. The navigation is simple and will be used consistently And if you use tables (Priority 2) 5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). Notes This should not be a concern for the users of the system but it may not be possible to comply 100% with this guideline based on the technical limitations of SharePoint 5.4 If a table is used for layout, do not use The templates will meet this guideline. 136

137 any structural markup for the purpose of visual formatting. And if you use frames (Priority 2) Notes 12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. There are no plans to use frames beyond single IFRAMEs And if you use forms (Priority 2) Notes 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. The development team will strive to meet this guideline. Explicity relationships are prefered 12.4 Associate labels explicitly with their controls. The development team will strive to meet this guideline. Explicit Label <label for="firstname">name</label> <input type="text" id="firstname"> And if you use applets and scripts (Priority 2) Notes 6.4 For scripts and applets, ensure that event handlers are input deviceindependent. This should not be a problem for the users of the system but it may not be possible to comply 100% with this guideline. 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. The only moving content may be video and the controls of the video player will allow for pausing of content. 8.1 Make programmatic elements such as scripts and applets directly accessible or This should not be a problem for the users of the system but it may not be possible to comply 100% 137

138 compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] with this guideline 9.2 Ensure that any element that has its own interface can be operated in a deviceindependent manner. This should not be a problem for the users of the system but it may not be possible to comply 100% with this guideline 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. This should not be a problem for the users of the system but it may not be possible to comply 100% with this guideline For more details please refer to the Accessibility Remediation Appendix Screen Resolution The site will be designed for a screen resolution 1024x768. The site will work at 800x600 with minimal side scrolling Minimum Browser Support The site will be designed for IE 6, IE 7 and Firefox 2 for web site visitors Friendly URLs Friendly URLs will be constructed into the solution for all top level sections. By default all pages in a MOSS site are preceded by "Pages" e.g By using variations for languages the url will look like this: Performance The actual load time of the page will depend on the page size and the resources that are used (e.g., images), the user s connection speed, and the server load at the time of the request. Every effort will be made to reduce this time by using a modular approach in building and configuring the Caregiver Portal and by using caching techniques Scalability The portal will be designed to support: 1,000 concurrent users. It should be noted that by concurrent users VON refers to active users in a session, not to the generally accepted definition of concurrent users, which defines concurrent users as the total number of people using a given resource at the same time. 138

139 It should be noted that anonymous users hardly use any disk space. The Internet Information Server (IIS) just maintains a session ID for each active user. This session ID is GUID (Global Unique Identifier). The user remains active, typically, for around 20 minutes since the last activity, after which the session is terminated. For authenticated users we will maintain the following: 1. Profile information. 2. Profile photo 3. alerts 4. Blog entries 5. Journal (in the future) 6. Other features added in the future All this information adds up over time. However, we could use site quotas as illustrated below: Figure 50 Quota Templates 100,000 caregiver electronic journals per calendar year. 139

140 20 Appendix 20.1 Accessibility Remediation Priority Provide a text equivalent for every non-text element 2.1 Ensure that information does not rely on colour perception 4.1 Identify language changes in text 6.1 Ensure that documents can be read without style sheets 6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes 7.1 Avoid causing the screen to flicker 14.1 Use the clearest and simplest language appropriate 1.2 Provide text links to emulate server-side image maps 9.1 Use client-side image maps rather than server-side image maps where possible 5.1 For data tables, identify row and column headers 5.2 For complex data tables, use mark-up to associate data cells and header cells 12.1 Add titles to frames 6.3 Ensure that pages are usable without support for scripts, applets, or other programmatic objects 1.3 Provide an auditory description of the visual information in multimedia presentations 1.4 For multimedia, ensure that timing of alternative descriptions is synchronised with the presentation 11.4 If you cannot make a page accessible, provide an equivalent accessible page Priority Ensure that images have sufficient contrast for people with colour deficient vision 3.1 When an appropriate markup language exists, use markup rather than images to convey information 3.2 Create documents that validate to published formal grammars 3.3 Use style sheets to control layout and presentation 3.4 Use relative rather than absolute units 3.5 Use header elements to convey structure 3.6 Mark up lists and list items using the proper HTML tags 3.7 Use quotation mark-up for quotations, but not for formatting 6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page 7.2 Avoid causing content to blink 7.4 Do not periodically auto-refresh pages 7.5 Do not use mark-up to redirect pages automatically 140

141 10.1 Do not generate pop-ups or other windows and do not change the current window without informing the user 11.1 Where possible, use appropriate W3C technologies of the latest supported versions 11.2 Avoid deprecated features of W3C technologies 12.3 Break up large blocks of information where appropriate 13.1 Clearly identify the target of each link 13.2 Provide information about pages and sites in metadata 13.3 Provide information about the general layout of a site 13.4 Use navigation mechanisms consistently 5.3 Ensure that information laid out using tables make sense when linearised, or provide an alternative equivalent 5.4 Do not use structural mark-up to format information laid out using tables 12.2 Describe the purpose of frames and how they relate to each other if it is not obvious by their titles alone 10.2 Properly position the labels of form controls 12.4 Associate labels explicitly with their controls 6.4 Use input device-independent event handlers in scripts and applets 7.3 Avoid movement in content 8.1 Ensure that scripts and applets are accessible [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.] 9.2 Ensure that user interfaces are device-independent 9.3 Use logical event handlers in scripts Guidelines introduction Navantis' analysis and validation of websites and web applications is based on the Ontarians With Disabilities Act (ODA) guidelines. The ODA, in turn, has adopted the Web Content Accessibility Guidelines 1.0 Priorities 1 and 2 from the Web Accessibility Initiative (WAI). WAI 1.0. The additional information has not been endorsed by the World Wide Web Consortium (W3C). In case of any perceived contradictions, WAI statements and explanations should be accepted as definitive in all cases. The Web Content Accessibility Guidelines 1.0 are copyright 1999 W3C (MIT, INRIA, Keio), All Rights Reserved. Priority 1 The guidelines under the WAI Priority 1 must be followed for a site to be accessible. Creating a website and/or web application that complies with these guidelines will enable all disabled groups (as targeted by the ODA) to use the site. For some user groups, this is the bare minimum required to make it possible for them to access the information. 1.1 Provide a text equivalent for every non-text element Full WAI text: "Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic 141

142 objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video." Text equivalents of any non-text elements on a website must be made available to users. The text equivalents must contain the same information as the non-text elements that they are describing. Text here refers to "real text", that is, ASCII or Unicode characters. Images that are illustrations of text - for example, titles, headings, logos, buttons - are not "real text" and must, therefore, have text descriptions. Examples of non-text elements include: Images, including: o Artwork o Photographs o Coloured fills or spacers o Drawings of text used for titles, headings, logos or buttons - Although these elements may look like text, they are not and must have a text equivalent. o Image maps: An image map is an image that is made of several other images, each of which is a separate link or graphical button. o ASCII art: ASCII is the name of a common character encoding system used by computers. ASCII art, therefore, is an image that is created using these text characters. Similar to the way that a newspaper picture is made up of tiny dots that when viewed far enough away make a picture, ASCII art is an image made up of text characters that when viewed together create a picture. As text, however, the picture does not make sense and thus needs a text description that explains what is being represented. Animations Movies Sounds: For example, downloadable or streaming spoken audio, audio cues, alert tones and the audio track on a video. Programmatic objects: Programmatic objects are non-html pieces of functionality, such as scripts or applets, that provide dynamic or interactive behaviour. For example: pop-up menus coded in DHTML, scrolling "tickers" and interactive applications such as tax calculators or games written in Java or Macromedia Flash. As these elements are not directly accessible to all users, equivalent information or functionality provided in text format is necessary. This information can be provided in a variety of ways using HTML, including "alt" and "longdesc". Rationale Many users cannot access any media other than text. Blind users cannot see the screen, so they must have text equivalents for images; otherwise they may not be able to understand or navigate the site that they are using. If titles, buttons, links or other important information are presented as images the user will not be able to understand or navigate through the site. Charts, pictures, graphs and photographs will be useless and meaningless to blind users without equivalent text descriptions. Screen readers are the tool used most often by blind and visually impaired users. A screen reader interprets the text contents of the screen and outputs this either to a speech synthesiser or a Braille display. Screen readers can read text equivalents of non-text elements, if they are 142

143 available. If not, then the screen reader can only tell the user that the element is there but nothing else. In the case of deaf users, they cannot hear any audio information, such as warning sounds or narration. Providing text equivalents of audio will allow the deaf users to understand what they cannot hear. Another reason for having text equivalents is that some users will turn off images in their browser to save time or money if they have old computer equipment, slow internet connections or metered telephone connections. 2.1 Ensure that information does not rely on colour perception Full WAI text: "Ensure that all information conveyed with colour is also available without colour, for example from context or markup" While colour can be a useful way of presenting information, it should not be used as the only way to communicate meaning. By using labels, style effects, etc., you can communicate information more effectively to users who cannot differentiate colours easily. Rationale Some users cannot easily perceive colour differences, in particular colour-blind users or those who work on monochrome or old monitors. If understanding information is dependent upon a user being able to distinguish between colours, then these users will be left out. If the user can't distinguish between the colours and there are no labels on the buttons, they can't make the correct choice. For other users, it may simply be a question of hue and contrast. Some colours are similar in hue or contrast and when they are used as text and background colours, they become difficult to read. Colours with sufficient contrast should be used for the page text and background. 4.1 Identify language changes in text Full WAI text: "Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions)." Natural language refers to spoken, written or signed languages, such as English, French, Braille and American Sign Language. The predominant natural language should be declared in the HTML code of a webpage. Any text, including text equivalents like ALT text or audio/video captions, that is presented in a language other than the predominant natural language should also be declared. Rationale 143