Spreadsheet: 1217bbee-31ba-4eb1-84bc-e6e5cb8b25ff
Sheet: Requirements

* Functional Area | Req. ID | Requirement Description | *  Requirement Type | * Requirements Source
Welcome page | 1 | The system shall be accessed via a link of the TECPDS site | Functional | [NAME]
Welcome page | 1.1 | The welcome page shall contain content on the following topics: o Training objectives o Training benefits o Definitions of roles (practitioners, administrators) | Functional | UT Health Stakeholders and SMEs
Welcome page | 1.2 | The welcome page shall contain the following links: o Link to download a PDF of the Core Competencies document o Link to the system requirements and links to download necessary software o Link to the privacy statement o Link to accessibility standards | Functional | UT Health Stakeholders
Welcome page | 1.3 | The welcome page shall display a copyright notice | Functional | [NAME]
Welcome page | 1.4 | The welcome page shall contain the points of entry to the Practitioner and Administrator modules | Functional | UT Health Stakeholders
Modules - General | 2 | There shall be separate modules: Practitioners; Administrators | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1 | In both the Administrator and Practitioner modules, there shall be two paths available for learners: Certificate and Review | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.1 | The Certificate path will require a learner to log in to take the training | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.2 | The Certificate path will allow a learner to create a Professional Development Plan
Modules - Certificate/Review | 2.1.3 | The Certificate path will allow a learner to obtain a Certificate for the determined clock hours | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.4 | The Certificate path will allow a learner to take a survey on the effectiveness of the training | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5 | If a learner selects the Certificate path, the system shall capture the following information for the learner: [NAME] module Start Date/Time • Training module Completion Date/Time • Session Start Date/Time • Session End Date/Time • Lessons Completed | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.1 | The system shall capture the date (MM/DD/YYYY) and time (HH:MM:SS) a learner initiates the introduction lesson of a training module | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.2 | The system shall capture the date (MM/DD/YYYY) and time (HH:MM:SS) a learner completes all lessons of a training module. | Functional | UT Health Stakeholders
 | 2.1.5.2.1 | This does not include the Professional Development Plan, obtaining the Certificate, or taking the Survey | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.3 | The system shall capture the date (MM/DD/YYYY) and time (HH:MM:SS) a learner initiates a new training module session. | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.4 | The system shall capture the date (MM/DD/YYYY) and time (HH:MM:SS) a learner logs off a training module session. | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.5 | The system shall have a flag field for each module lesson to indicate whether the learner has completed the lesson or not. | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.5.5.1 | The system shall trigger a lesson flag field to be checked in the database upon a learner completing a lesson. | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.6 | The Review path will not allow a learner to create a Professional Development Plan | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.7 | The Review path will not allow a learner to obtain a Certificate for the determined clock hours | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.8 | The Review path will not allow a learner to take a survey on the effectiveness of the training | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.9 | The module lessons contained in both the Certificate and Review paths will be the same | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.9.1 | The Review path will not contain knowledge checks within the Core Competency lessons. | Functional | UT Health Stakeholders
Modules - Certificate/Review | 2.1.10 | The Certificate/Review path page will contain the following:  - explanation of the Review path  - explanation of the Certificate path, including information on logging in with [NAME] account  - information on the training clock hours  - information on the ability to create a Professional Development Plan  - information on the ability to obtain a Certificate  - information on the option to take an external survey | Functional | UT Health Stakeholders
Modules - General | 2.2 | A module shall contain the following lessons:  - Introduction  - Lesson for each core competency area      - There are 9 Core Competency Areas for Practitioners      - There are 6 Core Competency Areas for Administrators | Functional | UT Health Stakeholders
Modules - General | 2.2.1 | The system shall allow learners to access any lesson in a training module at any time--they do not need to progress linearly | Functional | [NAME]
Modules - General | 2.3 | The learner shall have the ability to navigate in and out of the system | Functional | ICF, UT Health Stakeholders, and SMEs
Modules - General | 2.3.1 | The system shall allow learners who selected the Certificate path to restart the training from the point last visited. | Functional | SMEs
Modules - General | 2.3.2 | The system shall allow learners to restart the training from the beginning of that lesson. | Functional | SMEs
Modules - General | 2.3.3 | The system shall allow learners to restart the training from any lesson in the module. |  | UT Health Stakeholders
Modules - General | 2.4 | The system shall display the amount of time needed to complete the training module | Functional | SMEs and ICF
Modules - General | 2.4.1 | The system shall display the learner's progress through the training module as a whole | Functional | SMEs and ICF
Modules - General | 2.5 | Each lesson shall take an average of 20 minutes to complete | Usability | SMEs ([NAME], [NAME], [NAME])
Modules - General | 2.6 | The system shall track and store when a lesson has been completed | Functional | UT Health Stakeholders and SMEs
Modules - General | 2.6.1 | The system shall graphically demonstrate a completed lesson | Functional | UT Health Stakeholders and SMEs
Modules - General | 2.7 | The system shall display a tab outlining each page contained within a lesson. | Functional | UT Health Stakeholders
Modules - General | 2.7.1 | The system shall highlight the current page in the outline | Functional | ICF, UT Health Stakeholders, and SMEs
Modules - General | 2.7.2 | The system shall display the learner's progress in a lesson | Functional | UT Health Stakeholders
Modules - General | 2.7.3 | Links to pages past the further most point shall be greyed out in the outline | Functional | [NAME]
Modules - General | 2.7.4 | The outline will include specific titles for each page | Functional | UT Health Stakeholders
Modules - General | 2.8 | The system shall display a tab with the narration for each page | Functional | ICF, UT Health Stakeholders and SMEs
Modules - General | 2.9 | The system shall display a tab with references for each page, noting portions of the Core Competencies document relevant to the content on that page | Functional | ICF, UT Health Stakeholders and SMEs
Modules - General | 2.10 | The system shall allow learner to print full transcripts of each lesson and the presentation as slides with images | Functional | UT Health Stakeholders and SMEs
Modules - General | 2.11 | Each lesson shall contain interactive content, including the following approaches for text, graphic, and animation:  - Animated Line Art  - 2/3-D Ilustrations  - Photos  - Digital videos  - Static Graphic  - Graphic Build  - Label  - Pop-up Text  - Text Build | Functional | [NAME]
Modules - General | 2.11.1 | Upon a learner selecting to initiate a digital video the system shall adjust it to the size of the screen | Usability | SMEs and [NAME]
Modules - General | 2.11.2 | When interactive content is loading, the system shall alert learners to the progress of the load by displaying a progress bar or percentage | Usability | UT Health Stakeholders and SMEs
Modules - General | 2.11.3 | Any individuals depicted in interactive content shall be culturally diverse and cheerful | Usability | SMEs
Modules - General | 2.12 | The system shall have an audio file for each lesson | Functional | ICF, UT Health Stakeholders and SMEs
Modules - General | 2.12.1 | The audio file and interactivity of each lesson shall start automatically upon the system loading the lesson | Functional | [NAME], [NAME]
Modules - General | 2.13 | The system shall display the last page of a lesson, upon the completion of the lesson | Functional | [NAME]
Modules - General | 2.14 | The system shall allow learners to pause and move backward within a lesson | Functional | [NAME]
Modules - General | 2.15 | The system shall prevent learners from skipping within a lesson past the forward most point viewed in the presentation | Functional | [NAME]
Modules - General | 2.16 | Breadcrumbs shall be provided on every page | Functional | SMEs
Modules - General | 2.17 | The system shall display a navigation menu on the left of the page throughout a module | Functional | ICF, UT Health Stakeholders, and SMEs
Modules - General | 2.17.1 | The navigation menu shall contain the titles and duration of each lesson | Functional | ICF and SMEs
Modules - General | 2.18 | The content of the lessons shall be written at the 6-8th grade reading level | Usability | UT Health Stakeholders
Modules - General | 2.19 | Text shall be displayed in a large font size in easy-to-read colors | Usability | SMEs
Modules - Introduction | 3 | The introduction lesson for both administrator and practitioner modules shall contain the following information: • Explanation of navigation o Explanation of screen layout o Explanation of icons used throughout the training o Clarify that learners can start and stop the training • What to expect out of trainings o Training objectives o Explanation of hierarchy within each core competency lesson training  Different categories of competencies • Including a translation between former core skills/knowledge and new core competencies  How this will apply to levels of practice (Beginner, Intermediate, Advanced) o Inform learners they can expect questions/knowledge checks in each module core competency lesson, if they have selected the Certificate path, but that they are not being tested o How to use the time of reflection section in each lesson • How to use the Texas Core Competencies for Early Childhood Practitioners and Administrators document • Resources to find additional training o Text about the TECPDS training section o A link to the TECPDS training landing page • Expectation of time o Reiterate that if a learner has selected the certificate path, they should expect at the end of the training module to obtain a Certificate for training clock hours to-be-defined, the ability to create a Professional Development Plan, and the option to take an external survey. | Functional | UT Health Stakeholders and SMEs
Modules - Introduction | 3.1 | The knowledge check and Time of Reflection sections shall have an icon representing the section in a lesson
Modules - Core Competencies | 4 | Each core competency area shall be its own lesson in the training modules | Functional | [NAME]
Modules - Core Competencies | 4.1 | Lessons shall contain links to bookmarked areas of the following documents:  - Core competencies document,   - Pre-K guidelines,  - Infant and [NAME] guidelines, and  - Licensing guidelines | Functional | UT Health Stakeholders
Modules - Core Competencies | 4.2 | The visual and interactive structure of the lessons shall be consistent across core competency areas | Usability | [NAME] and [NAME]
Modules - Core Competencies | 4.3 | Each core competency area lesson shall contain concrete examples in a non-text format | Usability | [NAME]
Modules - Core Competencies | 4.4 | Each lesson shall include a "time of reflection" | Functional | ICF and UT Health Stakeholders
Modules - Core Competencies | 4.4.1 | The times of reflection shall consist of a list of questions displayed to the learner without a response prompt | Functional | ICF and UT Health Stakeholders
Modules - Core Competencies | 4.5 | Each lesson shall include a knowledge check | Functional | ICF, UT Health Stakeholders, and SMEs
Modules - Core Competencies | 4.5.1 | The knowledge check shall consist of a set of questions at the end of the lesson that give the opportunity to select a response | Functional | ICF, UT Health Stakeholders, and SMEs
Modules - Core Competencies | 4.5.1.1 | The number of questions shall depend on the content of the lesson. However, the goal will be to have 3 to 5 questions, with the understanding that all necessary learning objectives shall be covered. | Functional | UT Health Stakeholders
Modules - Core Competencies | 4.5.2 | If learners respond incorrectly to a question once, the system shall display a hint; twice, the system shall display the correct answer | Functional | [NAME]
Modules - Core Competencies | 4.5.3 | The system shall not store the knowledge check responses | Functional | UT Health Stakeholders
Modules - Core Competencies | 4.5.4 | If a learner selected the Review path, the module lessons shall not display the knowledge check slides in the lesson | Functional | UT Health Stakeholders
Modules - Survey | 5 | The system shall provide the ability for a learner, who selected the Certificate path, to take a survey, administered external to the system by third party vendor such as survey monkey | Functional | UT Health Stakeholders and SMEs
Modules - Survey | 5.1 | The system shall display the option for a learner to take a survey upon completion of all lessons within a module | Functional | UT Health Stakeholders and SMEs
Modules - Survey | 5.1.1 | The learner shall have the ability to opt out of the survey | Functional | UT Health Stakeholders
Modules - Survey | 5.1.2 | The option to take a survey shall be displayed after the Certificate is generated | Functional | UT Health Stakeholders
Modules - Survey | 5.2 | The survey shall consist of no more than 5 questions and a comments section | Functional | SMEs
Modules - Professional development plan | 6 | The system shall provide the ability for a learner to document a professional development plan | Functional | UT Health Stakeholders
Modules - Professional development plan | 6.1 | The system shall display a professional development plan page upon a learner completing all lessons of a training module | Functional | UT Health Stakeholders and SMEs
Modules - Professional development plan | 6.1.1 | The system shall only display the Professional Development Plan page if the learner selected the certificate route | Functional | UT Health Stakeholders
Modules - Professional development plan | 6.2 | The professional development plan shall allow learners to document the competencies for which they would like to seek further training, as well as, their professional goals | Functional | UT Health Stakeholders and SMEs
Modules - Professional development plan | 6.3 | The system shall allow a learner to print their professional development plan | Functional | SMEs
Modules - Professional development plan | 6.4 | The system shall not capture and store any professional development plan data entered | Functional | UT Health Stakeholders
Modules - Professional development plan | 6.5 | The system shall allow a learner to save their professional development plan as a PDF file | Functional | UT Health Stakeholders
Modules - Professional development plan | 6.6 | The system shall allow a learner to email their professional development plan to the email address captured at registration | Functional | UT Health Stakeholders
Modules - Certificate | 7 | The system shall provide the ability for a learner to obtain a certificate for completion of a training module | Functional | UT Health Stakeholders and SMEs
Modules - Certificate | 7.1 | The system shall display the certificate following completion of all core competency lessons and a response (completion or opt out) to the professional development plan | Functional | UT Health Stakeholders and SMEs
Modules - Certificate | 7.1.1 | The system shall only display the Certificate if the learner selected the certificate route | Functional | UT Health Stakeholders
Modules - Certificate | 7.2 | The certificate shall include the learner's name, the name of the Core Competency training module completed, the date training was completed, the source of the training, the Core Competency Area, “Professionalism and Ethics”, and the Rule noting Child Care Licensing Minimum Standards | Functional | UT Health Stakeholders
Modules - Certificate | 7.2.1 | The system shall auto-populate the learner's name when generating the certificate | Functional | UT Health Stakeholders
Modules - Certificate | 7.3 | The system shall allow the learner to print the certificate in a printer-friendly format | Functional | UT Health Stakeholders and ICF
Modules - Certificate | 7.4 | The system shall allow the learner to save the certificate as a PDF | Functional
Modules - Certificate | 7.5 | The system shall allow the learner to email themselves the certificate to the email address used during registration | Functional
Modules - Certificate | 7.5.1 | The system shall email the certificate to the email address submitted during registration | Functional
Login | 8 | The system shall use role based authorization to allow access to the training module when a learner has selected the certificate path
Login | 8.1 | The system shall allow two types of users: learners; system administrators | Security | UT Health Stakeholders
Login | 8.1.1 | The system shall provide the ability to designate a user as a system administrator | Security | [NAME] and ICF
Login | 8.1.1.1 | The UTHealth LDAP servers shall manage the login authentication for system administrators
Login | 8.2 | The system shall require learners to register upon selecting the certificate route | Security | [NAME]
Login | 8.2.1 | The system shall require the following data elements be submitted by a learner to register for a training module:  - first name, last name, email address, role | Security | [NAME]
Login | 8.2.2 | A Novell Access Manager network device performs the authentication against a third party identify provider (IDP), such as Google | Security | UT Health Stakeholders
Login | 8.2.3 | The system should receive an entitlement string in the HTTP header from the Novell Access Manager indicating successful authentication
Login | 8.2.4 | The system registers the email as the username during the registration process
Login | 8.2.5 | After the initial registration, the system shall allow learners the ability to log-in using just their [NAME] credentials
Login | 8.2.6 | During authentication, the system will check the user table to determine whether the learner has a valid account
Login | 8.2.7 | If authentication is successful, the learner is directed to the introduction lesson of the training module
Login | 8.2.8 | If authentication is unsuccessful, the learner is returned to the login page
Login | 8.2.8.1 | A warning will be displayed notifying the learner the information entered was incorrect
Login | 8.3 | The system shall store the following data for learners: • Last name • First name • email address • role | Security | UT Health Stakeholders and ICF
Reporting | 9 | The system administrator shall have the ability to generate canned exports in CSV format. | Functional | UT Health Stakeholders and ICF
Reporting | 9.1 | The system shall provide the ability to generate an export file with the following data elements: • Average time frame to complete a training module • Average length of session • Number of visitors, by learner type • Number of trainings completed | Functional | UT Health Stakeholders and ICF
Technical | 10 | The system shall leverage the existing infrastructure | Environment | [NAME]
Technical | 10.1 | The system shall reside at the UTHealth data center | Environment
Technical | 10.2 | The system shall reside on Microsoft Internet Information Servers (IIS) version 7 | Environment
Technical | 10.3 | The system shall store all data in the Microsoft SQL Server version 2005 clusters | Environment
Technical | 11 | The latest version of the following web browsers shall be supported, unless another version is noted: • Internet Explorer 8+ • Firefox • Chrome • [NAME] | Environment | [NAME]
Technical | 12 | The system shall be compliant with American Disabilities Act/Section 508 accessibility standards | Environment | UT Health Stakeholders and ICF
Technical | 13 | The system shall use the TECPDS global template for formatting | Environment | UT Health Stakeholders