Information Architecture

User Experience
Site Content
Site Structure
Visual Design

User Experience

1. Audience Definition

1.1. Student-Athletes (SA). New or returning Cal student-athletes are allowed to create, verify, and update information. This is our primary user group.
1.2. Compliance Office Administrators (COA). Cal staff members of the Compliance Office are authorized to view and verify information. Upon verification, they should be allowed to update some information. Also, they should be able to run reports.
1.3. Faculty Representatives Office Administrators (FROA). Cal staff members of the Faculty Representative Office are authorized to view and verify information. They should have all the same privileges as the COA.
1.4. Administrator (ADM). A Cal staff member will have full authority over, control of and access to the system including the database, all the SA information, and system backups.

2. Scenarios

2.1. SA Scenario 1. Bill, a student-athlete who plays for the Cal basketball team, is re-registering for the new school year. At the beginning of the semester and right in the comfort of his own home, Bill starts his web-browser and navigates to the CalStARS website. He logs in using his student ID (CalNet ID) and passphrase. He browses through all the information and decides to update his local address. He also adds a new entry for a job he will be starting next week. He jumps to the NCAA website to see if any of the NCAA regulations for Division I have changed. Afterwards, he jumps back to the CalStARS site and "signs" the forms to indicate that he has read and consented to the regulations. After verifying that all of the information had been updated and the forms signed, Bill logs out of the CalStARS site, ready and eager to start the new basketball season.
2.2. SA Scenario 2. Sally is an incoming freshman and an avid swimmer. She is ecstatic about studying at Cal and joining the women's swim team. Sally logs on to the CalStARS website, using her newly obtained CalNet ID and passphrase. She browses through the home page and realizes that there are many forms that need to be completed and begins by filling out the Student-Athlete Statement. However, halfway through the form, her roommate runs into the room excited about going to their first college party. Sally jumps at the chance to go out and decides to save the information she has filled out so far and log out of the system. The next day, Sally logs back into the system to continue filling out the rest of the forms. As she grabs another cup of coffee, she vows to complete and submit all of them in one sitting.
2.3. FROA Scenario. Betty, an administrator with the Office of Faculty Representatives, needs to generate a roster of the men's basketball team and their contact information. She logs onto the CalStARS website and generates the Submission Status Report on the men's basketball team to check the status of all the players. She notices that some of the athletes have not signed all the forms. She contacts the coach, Mark, and lets him know of the situation. Three days later, right before the staff meeting, Betty logs back onto the system and runs the report again. This time, all of the students of the men's basketball team have filled out all the proper forms. She is happy that she has an up-to-date report showing the submission status and can now discuss next week's agenda in the meeting.
2.4. ADM Scenario. After the hectic months of the school year, Frank, a Compliance Office administrator, needs to perform annual data maintenance functions. He logs onto the CalStARS website and runs several reports to verify that all student-athletes have filled out and signed all the necessary forms. Frank clicks on a button to "advance to the next school year" which sets the application to the new school year and saves all information to date. Now, the application shows a new template of student information where the general/permanent information is retained. This step also creates new forms for the school year, which incoming or returning student-athletes will need to fill out, update, and sign. He suddenly realizes that he needs to run a report from the prior school year. So, he selects the appropriate school year and generates the report. With the report in hand, Frank logs out of the system and heads out for a department meeting.

3. Actor-Goal List

Actor	Goal	Actor	Goal
SA	Play sports Meet NCAA & UC requirements Keep information Sign valid forms	Student-Athlete Registration System (SA Section)	Manage security Add users Modify users Capture "signatures" Maintain databases
COA/FROA	Verify "Recruitment" status Review SA information	Student-Athlete Registration System (Reports Section)	Manage security Display SA data Run reports Modify user information
ADM	Know when SA changes data Reset system	Student-Athlete Registration System (ADM Section)	Manage security Send notifications Save historical data Reset for new cycle

4. Use Case Diagram

^top

Site Content

The Compliance Office will be responsible for providing and maintaining the contents of the site. Specifically, NCAA rules and regulations will be directly linked to provide the most up-to-date information; there are currently ten forms that need to be converted to electronic documents.

1. Content Grouping and Labeling

1.1. Home. Shall be named 'index' with an appropriate file extension in all lower camel case naming convention. (e.g. index.htm)
1.2. SA Group. All pages directly related to student registration information and forms shall be named with an 'sa' prefix and matching descriptive form names. Also, the pages shall end with an appropriate file type extension. For example, a form to complete student housing information shall be named 'saHousing.jsp.'
1.3. ADM Group. All pages directly related to administration functions shall be named with an 'adm' prefix and matching descriptive function names. Also, the pages shall end with an appropriate file type extension. For example, a function to allow administrators to login shall be named 'admLogin.jsp.
1.4. Reports. Reports shall be named with an 'rpt' prefix and matching descriptive function names. Also, the pages shall end with an appropriate file type extension. For example, a report on submission status shall be named 'rptSubmissionStatus.jsp.

2. Functional Requirements

For a complete list of the requirements, refer to the Requirements section of this document. Specific objects noted in parenthesis '()' are tentative design specifications. Also, numbers noted in brackets '[]' are references to the Requirements section.

2.1 Index Page

Item	Function	Requirement
Student-Athlete Registration (button)	Takes to SA Login	[1.1]
Administrator Registration (button)	Takes to ADM Login	[1.1]

2.2 SA Login Page

Item	Function	Requirement
CalNet ID (input)	Takes User ID	[1.1.1]
Passphrase (input)	Takes User password	[1.1.1]
Submit (button)	Validates against CalNet system	[1.1.1]
Cancel (button)	Clears fields and sends back to Index Page	[1.1.1] User should be able to cancel out of actions

2.3 Student-Athlete Home Page

Item	Function	Requirement
Form Completion Status (text field)	Display of form completion (saved & signed) status	[2.4] Gives feedback
Form Completion Checkbox (checkbox image) per form	Displays checked status when form saved & signed	[2.5] Gives feedback
Form Name (embedded links) per form	Displays form and linked to forms	[2] Gives global access
"Work in progress..." (text)	Indicates saved form status	[2.5]
NCCA Rules & Regulations	Linked to NCAA website	[2.7.6 & 7] Access most up-to-date NCAA rules & regulations
Date field (text)	Display current date & current school year	[2.1]

2.4 Student-Athlete Form Page

Item	Function	Requirement
(No Browser Bar Window)	Keep users locked in pages	[2.6] Limits user mistakes
Cancel (button)	Clears all fields and sends back to SA Home	[2.6] Users should be able to exit
Save (button)	Saves data and stays within current page	[2.5] Users should be able to save periodically
Submit (button)	Saves data and sends to Confirmation Page	[2.3]
"back to main..." (embedded link)	Saves data and sends to SA Home	[2.6]

2.5 Student-Athlete Signature Form Page

Item	Function	Requirement
Read & Consent (checkbox)	Meets e-signature verification standard	[2.3]
Sign (button)	Satisfies two-step e-signature and send to SA Home	[2.3]
Do Not Sign (button)	Cancels e-signature (not "signed") and send to SA Home	[2.5]

2.6 Administrator Login Page

Item	Function	Requirement
User ID (input)	Takes User ID	[1]
Password (input)	Takes User password	[1]
Submit (button)	Validates against system and assigns Administrator User Levels	[1]
Cancel (button)	Clears fields and sends back to Index Page	[1] User should be able to cancel out of actions
"Forgot Password" (embedded link)	Sends Password to User's Email	[1] Double authentication
Reset System (button)	Runs scripts to backup current database and reset database for new school year	Operational requirement to keep data for 6 years (Applies only to System Administrator)

2.7 Administrator Home Page

Item	Function	Requirement
Dates (drop-down list)	Gives school year option and defaults to current year	[4]
Sports (drop-down list)	Gives sports option	[4] & [5]
Reports (embedded links)	Gives access to reports	[5]
Results Table (embedded links)	Gives access to individual student, after query	[4.3]

2.8 Administrator Report Page

Item	Function	Requirement
Print (button)	Send to printer	[5.4]
Close (button)	Cancel report mode and send to Administrator Home	[5] User should be able to exit

^top

Site Structure

1. Site Structure Listing

index.htm	saNCAADrugTestResults.jsp
saLogin.jsp	admLogin.jsp
saHomePage.jsp	admHomePage.jsp
saPermanentInfo.jsp	rptSubmissionStatus.jsp
saEducation.jsp	rptRecruitVerification.jsp
saCompensation.jsp	rptRecruitScholarship.jsp
saFinancialAid.jsp	rptDataUpdates.jsp
saHousing.jsp	saNCAAEligibility.jsp
saVehicle.jsp	saNCAABuckleyAmendment.jsp
saReleaseAuth.jsp	saNCAAScoreAffirmation.jsp
saCalDrugTestConsent.jsp	saNCAADrugTestConsent.jsp

2. Architectural Blueprints

3. Global and Local Navigation System

3.1. Top-level global navigation system shall control any navigation within the Web presentation.
3.2. Single local level navigation system within each section shall control any navigation within the section.
3.3. Embedded links to navigate to and forth from the NCAA site from the Student-Athlete's Home Page Section.

^top