# 1 Introduction
[NULL]

## 1.1 Purpose
The software described in this document is the Get Real website and associated support pages. This document outlines the requirements for the second revision (Rev2) of the website, initially created in the summer of 2006, with updates planned for summer 2007. The primary purpose of the Get Real website is to attract and encourage Oregon high school students to pursue a baccalaureate degree in computer science (CS) at one of the seven Oregon University System campuses.

## 1.2 Scope
The scope of the Get Real website is to provide a high school teen-friendly set of web pages that are easy to navigate while offering sufficient depth and information about careers in computer science. The website targets two main groups of students: those already interested in CS and those who might be attracted to a CS career with the right information. The ultimate goal is to increase the number of computer science graduates from Oregon universities by encouraging more students to choose computer science and related majors.

## 1.3 Product overview
[NULL]

### 1.3.1 Product perspective
This product is an update of the existing Get Real website version 1, with the new site being version 2. The website operates as an extension of the OUS site and runs on OSU servers, maximizing search engine visibility.

### 1.3.2 Product functions
The major features of the Get Real website include pages such as Exploring College, Jobs & Money, Real People, Women in Computing, Resources, I’m Looking For..., and Articles. Proposed new sections include High School Courses, Search for additional information, Professional Organizations, RSS feeds of current CS information, Ask an Engineer, Ask a Prof – FAQ, and Consider a CS minor in other professions.

### 1.3.3 User characteristics
The primary users are Oregon high school students, grades 9 to 12. The website targets students interested in CS careers and those who might be persuaded to consider CS with the right information. A third group includes students interested in diverse fields where a CS minor could be beneficial.

### 1.3.4 Limitations
Constraints for the website include space, bandwidth for video streaming, and limited availability of Chancellor’s Office resources. There are no user documents or development assumptions and dependencies.

## 1.4 Definitions
[N/A]

# 2 References
For web page development at the Capital Center, use the local site files for Dreamweaver. Adhere to CSS and other style conventions established in Get Real version 1. [Additional references are not provided.]

# 3 Requirements
[NULL]

## 3.1 Functions
The Get Real website will provide information on computer science offerings from Oregon universities, career opportunities, profiles of CS professionals, resources for women in computing, and more. New features will include high school course recommendations, search functionalities, professional organization links, RSS feeds, and FAQs.

## 3.2 Performance requirements
The website should be hosted on a server that provides adequate response time to accommodate the short attention spans of high school students. The current OUS site is an example of the desired rapid response time.

## 3.3 Usability requirements
The website should be teen-friendly, with a focus on graphic design changes, more white space, pictures, and easier navigation. The site should be broken into readable chunks of information with visually attractive elements like color, photos, diagrams, and charts.

## 3.5 Logical database requirements
[N/A]

## 3.6 Design constraints
Design constraints include adherence to CSS and style conventions from version 1, space limitations, bandwidth for video streaming, and limited resources from the Chancellor’s Office.

## 3.7 Software system attributes
The website should maintain consistent web design conventions with the OUS site. Security measures should align with those of the OUS site. There is a need to track and evaluate website traffic and make content, design, and navigation changes based on this evaluation.

## 3.8 Supporting information
[N/A]

# 4 Verification
[NULL]

## 4.1 Functions
[N/A]

## 4.2 Performance requirements
[N/A]

## 4.3 Usability requirements
[N/A]

## 4.5 Logical database requirements
[N/A]

## 4.6 Design constraints
[N/A]

## 4.7 Software system attributes
[N/A]

# 5 Appendices
[NULL]

## 5.1 Assumptions and dependencies
There are no development assumptions or dependencies.

## 5.2 Acronyms and abbreviations
[N/A]
