# 1 Introduction

## 1.1 Purpose
The software described in this document is the http://getreal.ous.edu website and associated support pages. This document describes requirements for Rev2, summer of 2007. The scope of the Get Real website is limited to attracting and encouraging Oregon high school students to take coursework leading toward a baccalaureate degree in computer science (CS) at one of the seven Oregon University System campuses.

## 1.2 Scope
The Get Real website aims to provide a high school teen-friendly set of web pages that are easy to navigate and provide sufficient depth and information about careers in computer science. The goal is to encourage more Oregon students to choose computer science and related majors, eventually increasing the number of computer science graduates from Oregon universities. Benefits for using the site include personal and career information from a broad spectrum of CS professionals, CS course information from OUS campuses, timely information, and a call to action for students to prepare for a CS career.

## 1.3 Product overview

### 1.3.1 Product perspective
This product is an update of the existing Get Real website version 1. The new site will be version 2. A future version 3 may be needed to incorporate ideas learned from version 2. The Get Real site runs as an extension of the OUS site and is hosted on OSU servers.

### 1.3.2 Product functions
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 pages 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
Users are typical Oregon high school students, grades 9 to 12, in all high schools across Oregon. Two potential groups of viewers exist: students interested in CS seeking more in-depth information about a CS career, and college-bound students not necessarily interested in CS who might be attracted to a CS career with the right information. A third group might be students interested in diverse careers 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. The site should work and be tested against IE, Firefox, and Netscape.

## 1.4 Definitions
[N/A]

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

# 3 Requirements

## 3.1 Functions
The Get Real website will include sections such as Exploring College, Jobs & Money, Real People, Women in Computing, Resources, I’m Looking For..., and Articles. New sections will include High School Courses, Search for additional information, Professional Organizations, RSS feeds of current CS information, Ask a Grad or Prof – FAQ, and Consider a CS Minor.

## 3.2 Performance requirements
The Get Real site should be hosted on a server that can provide adequate response time. High school students tend to have short attention spans, so a slow server would not be satisfactory for this application.

## 3.3 Usability requirements
Design changes to all existing pages should shorten paragraphs and add bullets and charts to accommodate faster page reading and shorter reader attention spans. The site should be visually attractive with color, photos, diagrams, and charts to break up the text.

## 3.5 Logical database requirements
[N/A]

## 3.6 Design constraints
Constraints include space, bandwidth for video streaming, and limited availability of Chancellor’s Office resources.

## 3.7 Software system attributes
- **Security**: Copyright and other security measures for Get Real should be the same as the OUS site.
- **Maintainability**: Web design conventions should be consistent with the standards and conventions used on the OUS site.

## 3.8 Supporting information
[N/A]

# 4 Verification

## 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

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

## 5.2 Acronyms and abbreviations
[N/A]