Goals
Allow candidates to register for an examination with one of the following gender selections
Male
Female
Custom Gender
User must type a value
Prefer not to identify
Due to the end-of-support for the existing method of interacting with Authorize.net used by the current registration process, we will be implementing the payment process via the Authorize.net hosted pages functionality. This is no risk to downstream processing of payments with this change as it is currently the mechanism used for online product sales in ASWBCentral that are processed by CSC>
Background and strategic fit
ASWB needs to ensure that it continues to support the changing social environment that Social Worker interact in. As part of this, the current registration process does not allow Candidates the opportunity to select a gender type consistent with their social declarations, Due to technological limitations of the current online registration system, a new interim system must be implemented to support this need. While this is opportunity to improve the current registration process, the need for timely development and minimal impact to staff and Candidates familiar with the online registration process, it has been decided that IT will develop a new site which addresses the immediate business need, but keeps the existing registration process (page navigation, field labels, error message, validation logic) intact. A visual refresh of the registration process will be included in this effort as the existing registration site utilizes the old ASWB.org color scheme and layout. This will be replaced with the visuals of the ASWBCentral site.
It should also be understood that other than the visual refresh, there will be no effort migrate the registration process or data into the ASWBCentral system. The majority of this work effort will be eliminated when the ASWBCentral specific project for exam administration is begun.
Terminology
Term | Definition | AKA |
|---|---|---|
Approval | The record of authorization received from a Jurisdiction that an applicant may site for the ASWB examination | |
Registration | The collection of Candidate information and payment allowing the user to sit for the ASWB examination |
Assumptions
The new registration process will utilize the ASWBCentral layout and styling in all aspects
The new registration process will interact solely with the legacy ASWBSQL2 and Datapath databases for all data actions
Actors
Actor / Role Name | Description | Objective | Type |
|---|---|---|---|
Candidate / Applicant | A individual who has received approval from their Jurisdiction to sit for the ASWB examination | To complete registration for the ASWB examination | User |
Jurisdiction | A locality granted the authority to grant approvals to individuals to site for the ASWB examination | User | |
Legacy local database | The ASWB database located on the ASWBSQL2\ASWBSQL2 SQL server instance. This is the database that CSC directly interacts with for all standard job tasks | Stores reference values, existing approvals and completed registrations | System |
Legacy online databases | The ASWBOnline database located on the Datapath server. This is the database that the online registration process directly interacts with for registration activities. | Stores reference values, existing approvals and completed registrations | System |
Pearson Vue | The entity responsible for the administration of the ASWB examination to successfully registered candidates | Stores a list of Candidates and associated data used to administer the exam and allow for psychometric reporting of results. | System |
Requirements
The following is a list of general requirements that apply to all related user stories unless specifically stated otherwise
The system is expected to handle all errors gracefully, providing a clear and concise message on the cause of the error. This includes but is not limited to:
Data of an incorrect type being submitted. For example, alphabetic characters entered into a numeric only field
Attempts to access a page of the registration process without successfully completing previous pages during the current visit. For example, attempting to access the Terms and conditions page, without first completing the Demographic information page
All data captured should be stripped of non-Ascii characters before attempting to process or save the data.
The system must require a valid SSL connection with the Candidate for all parts of the exam registration process. In the event that a secure connection can not be established, the Candidate must be prevented from continuing.
All interactions with the database must be through parameterized queries/procedures to maintain security of the system.
Only those validations and verifications listed within the user story must be applied and must be exactly as directed regardless of known changes to similar functions within the ASWBCentral system.
This will allow for reduced testing as it will ensure that all conditions within the new system meet the current system requirements.
User Stories
Title | Status | Notes |
|---|---|---|
As a system, I must allow the selection of a ASWB member jurisdiction | DRAFT | |
As a system, I must determine the appropriate fields to display on the Basic Information page | DRAFT | |
As a system, I must capture demographic information provided by a candidate | DRAFT | |
As a system, I must determine the exam registration fee and the amount due for an exam registration | DRAFT | |
As a candidate I must agree to the Exam terms and conditions | DRAFT | |
As a system, I must direct a user to the Authorize.net hosted page for payment | DRAFT | |
As a system, I must handle responses from the Authorize.net hosted pages | DRAFT | |
As a system, I must store the registration data to the database | DRAFT | |
DRAFT | ||
As a system, I must allow staff to enter extended gender details | NOT STARTED | |
As a system, I must transmit a properly formatted record to Pearson Vue | NOT STARTED | |
Test Cases
The following is a list of test cases that have been identified by IT, and will be validated during the registration process
System | Scenario | Purpose | |
|---|---|---|---|
| 1 | Web | Registration for candidate | “Happy Path” test case to verify basic functionality and data is being accessed and written correctly. This test will be run for each exam level. |
| 2 | Web | Registration for candidate w/ custom gender | Verify that custom gender option is being saved. |
| 3 | Web | Registration for Candidate where SSN matches approval from full SSN state | |
| 4 | Web | Registration for Candidate where SSN does not match approval from full SSN state | |
| 5 | Web | Registration for Candidate where approval from partial SSN state | |
| 6 | Web | Registration for Candidate where approval from no SSN state | |
| 7 | Web | Registration for Candidate where approval from Personal ID state | |
| 8 | Web | Registration for Candidate where SIN matches approval from full SIN state | |
| 9 | Web | Registration for Candidate where SSN does not match approval from full SIN state | |
| 10 | Web | Registration for Candidate where approval from partial SSN state | |
| 11 | Web | Registration for Candidate where approval from no SSN state | |
| 12 | Web | Registration for Candidate who has ADA on approval and wants to use it | |
| 13 | Web | Registration for Candidate who has ADA on approval and does not want to use it | |
| 14 | Web | Registration for Candidate who wishes to have ADA and but not on file | |
| 15 | Web | Registration for Candidate who has ESL on approval and wants to use it | |
| 16 | Web | Registration for Candidate who has ESL on approval and does not want to use it | |
| 17 | Web | Registration for Candidate who wishes to have ESL and but not on file | |
| 18 | Web | Registration for Candidate where state does not allow ESL | |
| 19 | Web | Registration for candidate who has open registration | |
| 20 | Web | Registration for candidate who has a previous registration | |
| 21 | Web | Registration for candidate who has Voucher | |
| 22 | Web | Registration for candidate who has Excused test | |
| 23 | Web | Registration for candidate who has Paper & Pencil | |
| 24 | Web | User credit card declined | Ensure that registration is not finalized if CC is unsuccessful |
| 25 | Legacy system | Register candidate with custom gender | |
| 26 | Legacy system | View registration with custom gender | |
| 27 | Legacy system | Create Pearson Vue nightly file |
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
|---|---|
Timeline
Status: DRAFT
* A project meeting will occur at the end of each sprint to provide all stakeholders with updates on the project, walkthrough of completed items, and discussion of project deliverables.
Technical Review (IT)
Areas Affected
TBD