# 1 Introduction
[NULL]

## 1.1 Purpose
This document describes the requirements for Revision 2 of the http://getreal.ous.edu website. The purpose of the software is to attract and encourage Oregon high school students to take coursework leading toward a baccalaureate degree in computer science (CS) at one of the seven Oregon University System (OUS) campuses.

## 1.2 Scope
The software product to be produced is the Get Real website, Revision 2.

The website will 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 will include:
*   Personal and career information from a broad spectrum of CS professionals.
*   CS course and other information from OUS campuses.
*   Timely and up-to-date information that encourages readers to return to the site.
*   A call to action and plans for students to follow to prepare for a CS career.

## 1.3 Product overview
[NULL]

### 1.3.1 Product perspective
This product is an update (Revision 2) of the existing Get Real website (Revision 1). The site runs as an extension of the OUS site (getreal.ous.edu) on OSU servers. Being part of the OUS domain is intended to maximize search engine hits.

The Get Real site should work and be tested against Internet Explorer, Firefox, and Netscape browsers.

There are no special hardware, software, or communications interface requirements.

### 1.3.2 Product functions
Major features of the Get Real website include the following pages and subsections:

*   Exploring College
*   Jobs & Money
*   Real People
*   Women in Computing
*   Resources
*   I’m Looking For...
*   Articles
*   High School Courses
*   Search for additional information
*   Professional Organizations
*   RSS feeds of current CS information
*   Ask an Engineer, Ask a Prof – FAQ
*   Consider a CS minor in other professions

### 1.3.3 User characteristics
The users are typical Oregon high school students, grades 9 to 12. Three potential groups of student viewers exist:

1.  Students interested in CS seeking more in-depth information about a CS career.
2.  College-bound students not necessarily interested in CS who might be attracted to a CS career with the right information from the site.
3.  Students interested in careers as diverse as protein research, weather prediction, neurobotics, medicine, law, or other sciences where a CS minor could be beneficial.

Feedback from high school students on the previous version of the site indicated the following characteristics and preferences:
*   Students not generally interested in CS are less tolerant of a site that is not visually engaging. They desire more white space, pictures, easier navigation, and content broken into more readable chunks to avoid "walls of text." They want a site that "spoke to them" with color, photos, diagrams, and charts.
*   Students who are interested in CS and engineering focused on the college comparison chart and the "Real People" section, indicating an attraction to pictures and structured personal stories.

### 1.3.4 Limitations
The supplier's options are limited by the following items:
*   Available server space.
*   Bandwidth for video streaming.
*   Limited availability of Chancellor’s Office resources.

## 1.4 Definitions
[N/A]

# 2 References
*   Adherence to CSS and other style conventions established in Get Real version 1 is required.
*   Development files are located at `~cn-capctr/share/Get_Real_website/~`. Dreamweaver check in/out feature must be used.
*   www.engineergirl.org is an example of a youth-oriented site that shows women in exciting engineering careers and has good use of white space on the pages.
*   University of Washington CS videos provide examples of "real people" profiles: http://www.cs.washington.edu/education/ugrad/prospective/download.html
*   WICS UO: www.cs.uoregon.edu/groups/wics/
*   University of Pennsylvania list of women in computer architecture: www.cis.upenn.edu/acg/wicarch.html

# 3 Requirements
[NULL]

## 3.1 Functions
*   **Exploring College**: Provide a listing of the computer science offerings from Oregon University System campuses and other Oregon colleges.
*   **Jobs & Money**: Offer answers to the questions: “how can I contribute to society and how much money can I make with a computer science degree?”
*   **Real People**: Provide a section outlining recent CS graduates and more experienced professionals in CS and related careers. The content should show real people using their CS knowledge in diverse fields. The use of video or audio should be supported to help convey personal messages.
*   **Women in Computer Science**: Profile women computer scientists and engineers who work to solve problems and are actively involved in their communities, raising families, and enjoying hobbies. It may include a list for girls interested in contacting recent grads or women CS professionals.
*   **Resources**: Allow users to explore a wide range of pre-college technology programs and courses for high school students.
*   **I’m Looking For...**: Provide a list of focused questions and answers with links to content inside the Get Real site. Topics include money, people, and colleges.
*   **Articles**: Provide a list of links to articles outside the Get Real site, such as “50 best jobs in America, Dream Jobs 2007, etc.”
*   **High School Courses**: Show recommended curricula for high school students interested in CS and related careers. This page should provide pointers to curricula recommendations from OUS campuses and other university sources, such as the ACM.
*   **Search for additional information**: Provide an internal search of the Get Real site and an external search of CS-related outside sites such as OUS campuses and articles on CS.
*   **Professional Organizations**: Provide a listing with links to ACM, IEEE, and key subgroups such as SIGGRAPH, with pointers to the student sections of these organizations.
*   **RSS feeds of current CS information**: Provide selected articles from the chancellor’s office daily communications distribution, fed to RSS subscribers on the Get Real site. This feature requires weekly editing of URLs.
*   **Ask a Grad or Prof – FAQ**: Provide a Q&A format for users to get feedback from the Oregon University System. Answers shall be posted in an FAQ section. A blog format is also an acceptable implementation.
*   **Consider a CS Minor**: Provide information for students in medicine, law, business, and other professions to show the value of having a CS minor.

## 3.2 Performance requirements
The Get Real site shall be hosted on a server that can provide adequate response time, comparable to the rapid response time of the main OUS site (www.ous.edu).

## 3.3 Usability requirements
Maintaining a teen-friendly site is of the highest importance. To accommodate faster page reading and shorter reader attention spans, the site design must:
*   Incorporate graphic design changes, more white space, pictures, and easier-to-navigate pages.
*   Break information into more readable chunks, avoiding "walls of text."
*   Use color, photos, diagrams, and charts to break up text and make the site visually attractive.
*   Shorten paragraphs and use bullets and charts where possible.
*   Consider using interactive elements, such as an interactive table menu, for more detailed information, leaving the main pages short and to the point.

## 3.5 Logical database requirements
[N/A]

## 3.6 Design constraints
*   The website must be compatible with Internet Explorer, Firefox, and Netscape.
*   The design must adhere to CSS and other style conventions established in Get Real version 1.
*   Web design conventions should be consistent with the standards and conventions used on the OUS site.

## 3.7 Software system attributes
*   **Security**: Copyright and other security measures for the Get Real site shall be the same as those for the main OUS site.
*   **Maintainability**: The system must provide the ability to track and evaluate the "hits" and time spent on the website over time to allow for content, design, and navigation changes as needed based on this evaluation.

## 3.8 Supporting information
There are no user documents for this system.

# 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
[N/A]

## 5.2 Acronyms and abbreviations
*   **CS**: Computer Science
*   **OUS**: Oregon University System
*   **SRS**: Software Requirements Specification
*   **FAQ**: Frequently Asked Questions
*   **ACM**: Association for Computing Machinery
*   **IEEE**: Institute of Electrical and Electronics Engineers
*   **SIGGRAPH**: Special Interest Group on Computer Graphics and Interactive Techniques
*   **RSS**: Really Simple Syndication
*   **CSS**: Cascading Style Sheets
*   **WICS**: Women in Computer Science
